Creating Templates and Domains Using the pack and unpack Commands
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
This section provides information and examples for creating templates and domains using pack
and unpack
:
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 so by using the pack
command to create a Managed Server template (a .jar
file that, by default, contains only the files necessary to create a Managed Server domain directory), copying the template to the remote machine, and unpacking the template to create a domain directory customized for a Managed Server.
Note: You must create the Managed Server domain directory on the remote machine that matches the definition of the Managed Servers specified in the template.
The steps to create a Managed Server on a remote machine are as follows:
pack
command. A Managed Server template, by default, contains only those files necessary to create a Managed Server on a remote machine. For instructions, see How Do I: Use pack to Create a Managed Server Template.
You create a Managed Server template by executing the pack
command, with the -managed=true
option, on an existing domain that already includes the definition of one or more Managed Servers. This domain must also contain Managed Server definitions in the config.xml
file.
WL_HOME
\common\bin
directory. In this pathname, WL_HOME
is the product directory in which you installed WebLogic Server.pack -managed=true -domain=
full_path_to_domain
-template=full_path_to_template
.jar -template_name="template_name"
For a complete description 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 Installation Guide.
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.
WL_HOME
\common\bin
directory. In this pathname, WL_HOME
is the product directory in which you installed WebLogic Server.unpack -domain=
full_path_to_domain
-template=full_path_to_template
.jar
When you create a domain directory for Managed Servers 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_server1
and 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_server1.cmd
/startmy_managed_server1.sh
and startmy_managed_server2.cmd
/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.
http://download.oracle.com/docs/cd/E13222_01/wls/docs90/server_start/overview.html
In these command lines, my_managed_server
is the name of the Managed Server to be started and admin-url
specifies 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 using the Node Manager. For details, see "Using Node Manager to Control Servers" in Managing Server Startup and Shutdown at http://download.oracle.com/docs/cd/E13222_01/wls/docs90/server_start/nodemgr.html
.
![]() |
![]() |
![]() |