The following sections describe the pack and unpack commands:
pack
The pack command 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.
The following table describes the files and directories that are included in both domain and Managed Server templates.
|
|||
|
Syntax
pack -domain=domain-template=template-template_name="template_name"[-template_author="author"][-template_desc="description"]
[-managed={true|false}][-log=log_file] [-log_priority=log_priority]
Parameter Descriptions
The following table describes the parameters that can be used with the pack command.
|
Specifies whether the template is to be used to create Managed Servers on remote machines. The default is
false. |
|
|
The priority setting for the log file. Use a log4j priority string. Valid log4j priority strings are
debug, info, warn, error, fatal. The priority string values correspond to the levels defined in the Level class. For more information, see http://logging.apache.org/log4j/docs/api/org/apache/log4j/Level.html. |
|
Example
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"
Related Topics
unpack
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:
- A domain template provided by BEA and packaged with your current installation
- A domain template created using the Domain Template Builder or WLST Offline
- A domain template created using the
packcommand - A Managed Server template created using the
packcommand. 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:
An 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\weblogic92\common\nodemanager\nodemanager.domains.
| Note: | By default, application files are not included in a Managed Server template created using the pack command. If an application in the domain from which you created a Managed Server template was deployed using external_stage mode, the Managed Server domain directory that you create with the unpack command will not contain any of the external_staged applications. Before you start the Managed Server, you will need to make sure that it has access to the externally staged application files. For more information, see Controlling Deployment File Copying with Staging Modes in Deploying Applications to WebLogic Server. |
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.
Syntax
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]
Parameter Descriptions
The following table describes the parameters that can be used with the unpack command.
|
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.
If no administrative users are defined in the template, you can create a new default administrator by specifying the
-user_name and -password parameters. If a default administrator and password are currently defined in the template, you can add a new administrative user by specifying the
-user_name and -password parameters. A valid username cannot include commas, tabs, or any characters in the following list:
< > # | & ? ( ) { }. Usernames are case sensitive. A valid password consists of a string of at least 8 case-sensitive characters. The
unpack command encrypts the password value.
|
|||||
|
|||||
|
The full path to the Java Home directory. When set, this identifies the default JVM used by the Administration Server for the domain.
|
|||||
|
|||||
|
The priority setting for the log file. Use a log4j priority string. Valid log4j priority strings are
debug, info, warn, error, fatal. The priority string values correspond to the levels defined in the Level class. For more information, see http://logging.apache.org/log4j/docs/api/org/apache/log4j/Level.html. |
|||||
Example
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
