Step 7: Changing 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.

1. 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.
2. Change the deployment targets for the Endeca Server Java application in WebLogic domain. In the Administration Console, select Lock & Edit, 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:
   

   Note: The version of the oracle.endecaserver application in this diagram may differ from the version of the Endeca Server you are actually installing.
3. In the Change Targets Assistant screen, change targets from the Admin Server to Managed Servers and select Yes.
   
4. Save the changes and click Activate Changes.
5. Change the deployment targets for the Data Enrichment Framework Java application, oracle.endeca.enrichment_framework, in WebLogic domain.
   To do this, repeat the steps 2- 4, but instead of selecting oracle.endecaserver, and /endeca-server, select oracle.endeca.enrichment_framework as a component for which you are changing targets.
6. 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>

   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.

7. Verify the deployment of the WebLogic domain. Go to the Servers section of the Administration Console and check the state of the Managed Servers.