Step 6: Changing the deployment targets and starting servers

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.

Starting the WebLogic Server on which the Endeca Server application is deployed automatically starts the Endeca Server. You can first start the Admin Server, change the deployment targets for the Endeca Server application, and then start the Managed Servers.

To change the deployment targets and start the servers:

Start the Admin Server. On host1, go to $DOMAIN_HOME/bin, and run:
```
startWebLogic.sh
```
Note: You may notice messages about the Cluster Coordinator failing to establish a connection to other machines running its service. These messages are expected and can be ignored. They indicate that the Cluster Coordinator is attempting to establish its quorum, but only one out of three configured Cluster Coordinator services are running at the moment. The messages will stop after you deploy two more Managed Servers that are running the Cluster Coordinator services.
Change the deployment targets. In the Administration Console, go to Deployments, click the application oracle.endecaserver, click the Targets tab, select Component (this selects both Endeca Server items under it), then select Change Targets:
In the Change Targets Assistant screen, change targets from the Admin Server to Managed Servers and select Yes.
Start the Managed Servers.
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
```
Note: If you use this method, the correlation of the Managed Server name and the machine host name on which it should be started is not enforced by the WebLogic Server scripts. Therefore, be careful to start Managed-2 on host2, and Managed-3 on host3.
On host1, which was not deployed with the unpack.* command, the start <Managed_Server_name>.* is not created. Therefore, use the following command to start the Managed Server in this case:
```
$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.
Verify the deployment of the WebLogic domain. Go to the Servers section of the Administration Console and check the state of the Managed Servers.

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.