Modify startManagedWebLogic.sh after unpacking to 2nd host

After packing a WebLogic domain on the first host and unpacking it on the second host, I noticed an interesting behavior.

After this was done, I attempted to start up a managed server on the second host on the command line via the startManagedWebLogic.sh script. For example:

nohup $DOMAIN_HOME/bin/startManagedWebLogic.sh wls_soa1 >> $DOMAIN_HOME/servers/wls_soa1/logs/wls_soa1.out &

The managed server did not start up because it could not communicate with the AdminServer.

It turns out that the unpack command replaces the ADMIN_URL in startManagedWebLogic.sh, which assumed that the AdminServer is running on the second host:

if [ "${ADMIN_URL}" = "" ] ; then
    ADMIN_URL="t3://soahost2:7001"
    export ADMIN_URL
fi

You must manually update startManagedWebLogic.sh and replace the ADMIN_URL to reflect the actual host which is running the AdminServer.