In this step, you change the deployment targets from the Admin Server to Managed Servers and start all servers in the WebLogic domain for the Endeca Server.
To change the deployment targets and start the servers:
startWebLogic.sh
On host2 and host3, the unpack.* script created scripts to start Managed Servers with the names you specified. You can run:
$DOMAIN_HOME/bin start<Managed_Server_name>.sh
For example, once in this directory, you can run:
start Managed-2.sh
$DOMAIN_HOME/bin startManagedWeblogic.sh <managed_server_name> <admin_server_url> <WebLogic Server console password>
Note that you can also use this command on each machine hosting a Managed Server, instead of the start <Managed_Server_name>.*.
Once the commands run successfully, you should see the state of the Managed Servers change to RUNNING.
After you have successfully installed and deployed an Endeca Server cluster, you can verify its status. You can also optionally add additional machines to its WebLogic domain (so that you can start additional Endeca Server instances), and, if you have previously created an Endeca Server data domain in the Endeca Server installed on a single machine, you can migrate this data domain to the Endeca Server cluster.
For information on all these tasks, see Verifying a cluster installation and deployment.