Deploy Secondary Hubs on Windows

To configure a secondary hub as a tunnel client, you need a certificate that is generated by the tunnel server hub. If the tunnel server is not set up, you can install a hub with no tunnel. Later, you can configure the tunnel between the hubs with Admin Console or Infrastructure Manager.
uim901
To configure a secondary hub as a tunnel client, you need a certificate that is generated by the tunnel server hub. If the tunnel server is not set up, you can install a hub with no tunnel. Later, you can configure the tunnel between the hubs with Admin Console or Infrastructure Manager.
 
Follow these steps:
 
  1. On the secondary hub server, browse to your UIM Server home page:
    http://
    server_name_or_IP
    :<wasp_port>/uimhome
     
  2. Click the 
    Installers 
    tab. Under 
    Infrastructure Installers
    , download the 
    Windows Robot, Hub, Distribution Server
     package.
  3. Launch the 
    NimBUS Infrastructure 
    installer.
  4. Select one of the following modes:
    •  
      Automatic 
      search for a hub. If a hub is found, only a robot is installed. If a hub is not found, then a hub with no tunnel is installed. 
    •  
      Custom 
      install the hub in the same network as the primary hub.
    •  
      DMZ 
      install a tunnel hub that is separated from the primary hub by a firewall.
  5. Follow the prompts to complete the installation. Note the following points:
    • If
       
      no other hub is available, select an existing domain. All available domains are shown.
    • Specify the desired hub name and enter the hub license number.
      The above-mentioned licensing functionality is no longer applicable for CA UIM 9.2.0. From CA UIM 9.2.0 onward, hub/robot- and probe-level licensing requirements have been removed. Deploy the hub, robot, and distsrv versions released with CA UIM 9.2.0 to remove the license dependency. If you want to continue with the older versions of hub and probes that require an extension of the license, contact Support so that they can assist you in extending the license (if required).
    • Create a hub user account (the 
      Initial User
      ) for the hub. Specify a user name, or use the default, administrator. Supply a password for the account. When prompted to log in, enter the new user name and password.
    • (Recommended) Leave the First probe port field blank, unless you have a reason to specify it. The system assigns the first probe to port 
      48000
       (or the first available subsequent port). The port number increments by 1 for each additional assignment.
  6. If you are installing a tunnel server hub, the 
    Setting up Tunnel Server
     dialog prompts you to create an authentication password. This password is required when you set up the tunnel client.
    • In the 
      Generating Client Certificate
       dialog, enter the IP address of the primary hub, or the secondary hub tunnel client.
    • Save the generated certificate, and copy the file to the tunnel client server. You need this certificate when you set up the tunnel client.
  7. If you are installing a tunnel client hub:
    • Enter the IP of the tunnel server, the server port, and the password you created during tunnel server setup.
    • Browse for the certificate file. When the file is found, the certificate text displays.
Hub installation is complete. The hub is in an enabled, or started, status.
Next Steps
  • Set up queues and tunnels between hubs. See the Hub probe documentation on the Probes Documentation Space for more information. 
  • If you want to use Admin Console to manage this hub, its child robots, or probes, deploy the Probe Provisioning Manager (ppm) probe to the hub. Use either Admin Console or Infrastructure Manager to deploy the probe from your local archive.
Install_hub_win