In some domains, you may want to run a managed server on a machine that is remote from the administration server for the domain. You can do this by performing the following steps:
packcommand. A managed server template, by default, contains only those files that are necessary for creating a managed server on a remote machine.
For more information, see How Do I Create a Managed Server Template.
You create a managed server template by executing the
pack command on an existing domain that includes the definition of one or more managed servers and contains managed server definitions in the
pack -managed=true -domain=
domainis the full or relative path of the domain from which the template is to be created.
.jaris tthe full or relative path of the template, and the filename of the template to be created.
template_nameis a descriptive name for the template, enclosed in quotes.
pack -managed=true -domain=C:\bea\user_projects\domains\mydomain -template=C:\bea\user_templates\mydomain_managed.jar -template_name="My Managed Server Domain"
For more information about the parameters of the
pack command, see pack.
|Note:||All WebLogic Server instances within a domain must run the same version of the WebLogic Server software. For more information about installing WebLogic Server, see the.|
|Note:||The IP address and port number of the remote machine must match the definition of the managed servers specified in the managed server template.|
For information about creating managed server templates, see How Do I Create a Managed Server Template.
WL_HOMEis the product directory in which installed WebLogic Server is installed).
domainis the full or relative path of the domain to be created.
.jaris the full or relative path of the managed server template that you copied to the machine in step 3.
unpack -domain=C:\bea\user_projects\domains\myManagedDomain -template=C:\bea\user_templates\mydomain_managed.jar
When you create a domain directory for managed servers by using the
unpack command, it contains a customized start script for each managed server targeted to the current remote machine.
For example, if you create a domain that contains two managed servers,
my_managed_server2, and you target the servers to machine
m1, when you create the managed server domain directory on machine
m1, four custom start scripts are created:
startmy_managed_server2.sh. You can use these scripts to start the corresponding managed servers. Alternatively, you can use the
startManagedWebLogic script with the required parameters.
In these commands,
my_managed_server is the name of the managed server to be started and
admin-url is the listen address (host name or IP address) and port number of the machine hosting the administration server. For your convenience, the
startManagedWebLogic_Readme.txt file provides a list of all the managed servers and the
admin-url for the domain.
|Note:||You can also start managed servers by using the node manager. For more information, see.|