Add Hosts

To define your deployment, add secondary servers and configure them with specific roles that determine their function within the deployment.

For complete deployment role details, see Appendix - Deployment Roles and Related Processes in the Exalead CloudView Administration Guide.

When you add a new secondary server, you can duplicate an existing host's configuration. This creates the roles you require for a combined index and search host automatically. However, you can manually edit the host configuration as explained in the procedures below.

This task shows you how to:

See Also
Moving Exalead CloudView to Another Host
Appendix - Install and Data Directories

Add a New Secondary Server

  1. In the Administration Console, select Deployment > Roles.
  2. On the Roles page, click Add host.
    1. Enter the Host Name of the secondary server, for example, server002.exalead.com
    2. Enter the Install Name of the secondary server install, for example, secondary1.
    3. If required, modify the Base port, Host agent, and Last port with the new secondary server's port range.
  3. Click Accept.
  4. On the Add roles window, add the roles required for your deployment then click Accept.

    For more information, see the specific configuration steps for how to:

  5. Click Apply.
  6. Restart Exalead CloudView.

    For more information, see Restart Exalead CloudView on Hosts.

  7. Install Exalead CloudView on the new secondary server.

    For more information, see Installing Secondary Servers.

Copy a Secondary Server

  1. In the Administration Console, select Deployment > Roles.
  2. On the Roles page, click Add host.
    1. Enter the Host Name of the secondary server install, for example, server002.exalead.com
    2. Enter the Install Name of the secondary server install, for example, secondary2.
    3. Select Duplicate from host, then select the host name, for example, server001.exalead.com
  3. Click Accept.
    The roles are duplicated for the new host, except those that cannot be duplicated and are unique per build group.
  4. The new secondary server now has the required roles for a combined index and search host but you must configure them:
    • Modify roles that depend on other roles so they point to the role instance on this new secondary server. This ensures high availability.

      For example, modify the Search API role on the secondary2 host so it points to secondary2's Search server, instead of secondary1's.

    • In most cases, you do not need the Connector and Crawler servers. So you can delete them.

    For more information, see Configure Roles.

  5. Click Apply.
  6. Restart Exalead CloudView.

    For more information, see Restart Exalead CloudView on Hosts.

  7. Install Exalead CloudView on the new secondary server.

    For more information, see Installing Secondary Servers.