Step 5: Unpacking the WebLogic domain on Managed Servers

Before you can start the Managed Servers, unpack the WebLogic domain template on the machines that do not yet contain the WebLogic domain's configuration.

As a prerequisite to this task, make sure that the template you created previously with the pack.* script is copied to host2 and host3. In this procedure, it is assumed that the file is copied to C:/tmp directory on each of these machines.

You will unpack the WebLogic domain on host2 and host3 only (two of the three machines hosting Managed Servers), because the third Managed Server resides on host1, together with the Admin Server, and can access the WebLogic domain configuration on this machine.

Important: The paths and the domain names on the Managed Servers should be the same as the ones used on the Admin Server. For example, if you packed the domain that was located in the C: drive, you should unpack it also into the C: drive, replicating the entire path you used on the Admin Server.

To unpack the WebLogic domain:

On host2 and host3, run the following command:
```
$ORACLE_HOME/Middleware/wlserver_10.3/common/bin/unpack.sh
-domain=$DOMAIN_HOME
-template=/tmp/endeca_server_template.jar
```
where <domain_name> is the name of the WebLogic domain you initially created on the Admin Server, such as endeca_domain.

Note: When the script runs, it may notify you that duplicate Server listen ports exist in your WebLogic domain configuration. You can ignore this warning.
When the script runs successfully, the WebLogic domain's configuration is transferred to the machines on which you will start the Managed Servers.
On each machine, go to $DOMAIN_HOME/config, and verify the contents of EndecaServer.properties and EndecaCmd.properties.

It should be the same as you configured on the Admin Server.

Note: You may notice that on all machines, including on host2, and on host3, the host name listed in EndecaCmd.properties is host1. This is expected — it indicates that you can later run endeca-cmd from $DOMAIN_HOME/EndecaServer/bin on the Admin Server (host1) .

Now you are ready to start the Admin Server and all three Managed Servers.