Creating Templates and Domains Using the pack and unpack Commands
The following sections describe the pack
and unpack
commands:
Creates a template archive (.jar
) file that contains a snapshot of either an entire domain or a subset of a domain.You can use a template that contains a subset of a domain to create a Managed Server domain directory hierarchy on a remote machine.
When you create a domain template, all files and directories in the source domain are included, with the following exceptions:
servers
directory.Note: If you configured additional security data, such as for users, groups, or roles, through the WebLogic Server Administration Console or other online tools, the security data is stored in the LDAP server and is not included in the template. You must first export the data and then import it into the target domain.
-managed=true
option, the following files and directories are included by default:.cmd
, .sh
, .xml
, .properties
, and.ini
..pem
extension defined in the SSL configuration for your domainbin
directorylib
directorysecurity
directory that are not created automatically during template creation. For example, DefaultAuthenticatorInit.ldift
and DefaultRoleMapperInit.ldift
are not included by default.config
directorypack -domain=
domain
-template=template
-template_name="template_name"
[-template_author="author"
][-template_desc="description"
]
[-managed={true|false}][-log=log_file
] [-log_priority=log_priority
]
The following table describes the parameters that can be used with the pack
command.
The full path to the domain from which the template is to be created. |
|
The full path and filename of the template to be created. The template filename must include the |
|
Descriptive name for the template. Quotes are required only if the value for this parameter contains spaces. |
|
The name of the author of the template. Quotes are required only if the value for this parameter contains spaces. |
|
Description of the template. Quotes are required only if the value for this parameter contains spaces. |
|
Specifies whether the template is to be used to create Managed Servers on remote machines. The default is When this parameter is set to |
|
The priority setting for the log file. Use a log4j priority string. Valid log4j priority strings are |
Executing the following command using a domain named mydomain
in the directory C:\bea\user_projects\domains
creates a template file named mydomain.jar
in the directory C:\bea\user_templates
. The name of the template is specified as My WebLogic Domain
.
pack -domain=C:\bea\user_projects\domains\mydomain
-template=C:\bea\user_templates\mydomain.jar -template_name="My WebLogic Domain"
Creates a full domain or a subset of a domain used for a Managed Server domain directory on a remote machine. You may use unpack
only with a template compatible with your current installation. The template can be any of the following:
pack
commandpack
command. A Managed Server template, by default, contains only the files necessary for creating a Managed Server domain directory.When you use the unpack
command with a domain template, it creates a domain containing all of the application and resource files defined in the template. It also creates necessary start scripts, and certain security and configuration files.
When you use the unpack
command with a Managed Server template, it creates a Managed Server domain directory that includes the following:
config_bootstrap.xml
file (based on the config.xml
in the template)nm_password.properties
fileSerializedSystemIni.dat
fileAn entry for the Managed Server domain directory is also created in the NM_HOME
/nodemanager.domains
file, where NM_HOME
designates the Node Manager installation directory for the product installation on the remote machine. By default, this directory is located in WL_HOME
/common/nodemanager
, for example, C:\bea\weblogic90\common\nodemanager\nodemanager.domains
.
For more information about using the pack
and unpack
commands to create a Managed Server domain directory, see Creating and Starting a Managed Server on a Remote Machine: Main Steps.
unpack -template=
template
-domain=domain
[-user_name=username
]
[-password=password
] [-app_dir=application_directory
]
[-java_home=java_home_directory
] [-server_start_mode={dev|prod}]
[-log=log_file
] [-log_priority=log_priority
]
The following table describes the parameters that can be used with the unpack
command.
The full path and filename of the template being used to create the domain. |
|
The username and password for the default administrator as currently defined in the template. This username/password combination is used to boot the Administration Server and connect to it. If you specify a new password for the default administrator, the password will be reset to the value specified. Note: If a password for the default administrator is not defined in the template, you must specify one. If no administrative users are defined in the template, you can create a new default administrator by specifying the If a default administrator and password are currently defined in the template, you can add a new administrative user by specifying the A valid username cannot include commas, tabs, or any characters in the following list: A valid password consists of a string of at least 8 case-sensitive characters. The Note: These parameters are not valid if you are creating a domain using a Managed Server template. |
|
The full path to the directory used to store the applications defined in the template. Note: This parameter is only valid if the template supports a separate applications directory. |
|
The full path to the Java Home directory. When set, this identifies the default JVM used by the Administration Server for the domain. Note: This parameter is not valid if you are creating a domain using a Managed Server template. |
|
The start mode for the Administration Server: development or production. Note: This parameter is not valid if you are creating a domain using a Managed Server template. |
|
The priority setting for the log file. Use a log4j priority string. Valid log4j priority strings are |
Executing the following command using a template named mydomain.jar
in the directory C:\bea\user_templates
creates a domain named my_new_domain
in the directory C:\bea\user_projects\domains
.
unpack -template=C:\bea\user_templates\mydomain.jar -domain=C:\bea\user_projects\domains\my_new_domain