weblogic.Deployer
is a Java-based deployment tool that provides administrators and developers command-line based deployment operations.
Note:
See the WLST Command Reference for WebLogic Server for information about performing deployment operations using the WebLogic Scripting Tool (WLST).
The following sections describe the weblogic.Deployer
utility:
To set up your environment to use the weblogic.Deployer
utility:
Install and configure the WebLogic Server software, as described in the Installing and Configuring Oracle WebLogic Server and Coherence.
Add the WebLogic Server classes to the CLASSPATH
environment variable, and ensure that the correct JDK binaries are available in your PATH
. You can use the setWLSEnv.sh
or setWLSEnv.cmd
script, located in the server/bin
subdirectory of the WebLogic Server installation directory, to set the environment.
Note:
On UNIX operating systems, the setWLSEnv.sh
command does not set the environment variables in all command shells. Oracle recommends that you execute this command using the Korn shell or bash shell.
If you are connecting to an Administration Server through a configured administration channel, you must also configure SSL on the machine on which you run weblogic.Deployer
. See Configuring SSL in Administering Security for Oracle WebLogic Server for instructions about configuring SSL.
java [SSL Arguments] weblogic.Deployer [Connection Arguments] [User Credentials Arguments] COMMAND-NAME command-options [Common Arguments]
Command names and options are not case-sensitive. See Commands and Options for detailed syntax and examples of using weblogic.Deployer
commands.
Caution:
Entering unencrypted passwords in weblogic.Deployer
commands, whether entered in a command window or a script, is a security risk because they can be viewed by others. For information about entering passwords securely, see "Securing the WebLogic Server Host" in Securing a Production Environment for Oracle WebLogic Server.
java [ -Dweblogic.security.TrustKeyStore=DemoTrust ] [ -Dweblogic.security.JavaStandardTrustKeyStorePassPhrase=password ] [ -Dweblogic.security.CustomTrustKeyStoreFileName=filename -Dweblogic.security.TrustKeystoreType=jks [-Dweblogic.security.CustomTrustKeyStorePassPhrase=password ] ] [ -Dweblogic.security.SSL.hostnameVerifier=classname ] [ -Dweblogic.security.SSL.ignoreHostnameVerification=true ] weblogic.Deployer [ User Credentials Arguments ] COMMAND-NAME command-arguments
If you have enabled the domain-wide administration port, or if you want to secure your administrative request by using some other listen port that is secured by SSL, you must include SSL arguments when you invoke weblogic.Deployer
. Table A-1 describes all SSL arguments for the weblogic.Deployer
utility.
Argument | Definition |
---|---|
-Dweblogic.security.TrustKeyStore=DemoTrust |
Causes This argument is required if the server instance to which you want to connect is using the demonstration identity and certificates. By default, |
-Dweblogic.security.JavaStandardTrustKeyStorePassPhrase=password
|
Password that was used to secure the Java Standard Trust keystore. If the Java Standard Trust keystore is protected by a password, and if you want to trust its CA certificates, you must use this argument. By default, the Java Standard Trust keystore is not protected by a password. |
-Dweblogic.security.CustomTrustKeyStoreFileName=filename
-Dweblogic.security.TrustKeystoreType=jks
|
Causes |
-Dweblogic.security.CustomTrustKeyStorePassPhrase=password
|
Password that was used to secure the custom keystore. You must use this argument only if the custom keystore is protected by a password. |
-Dweblogic.security.SSL.hostnameVerifier=classname
|
Name of a custom Host Name Verifier class. The class must implement the |
-Dweblogic.security.SSL.ignoreHostnameVerification=true |
Disables host name verification. |
java [SSL Arguments] weblogic.Deployer [-adminurl protocol://listen_address:port_number] [User Credentials Arguments] COMMAND-NAME command-options [Common Arguments]
Most weblogic.Deployer
commands require you to specify the -adminurl
arguments described in Table A-2 to connect to an Administration Server instance.
Table A-2 Connection Arguments
Argument | Definition |
---|---|
-adminurl [protocol://]Admin-Server-listen-address:listen-port |
Listen address and listen port of the Administration Server. To use a port that is not secured by SSL, the format is In order to use an adminurl with the HTTP protocol, you must enable the HTTP tunneling option in the Administration Console. For more information, see Setting Up WebLogic Server for HTTP Tunneling in Administering Server Environments for Oracle WebLogic Server. For instructions on enabling HTTP tunneling in the Administration Console, see Configure HTTP protocol in Oracle WebLogic Server Administration Console Online Help. To use a port that is secured by SSL, the format is To connect to the Administration Server via a configured administration channel, you must specify a valid administration port number: There is no default value for this argument. |
java [ SSL Arguments ] weblogic.Deployer [Connection Arguments] [ { -username username [-password password] } | [ -userconfigfile config-file [-userkeyfile admin-key] ] ] COMMAND-NAME command-options [Common Arguments]
Most weblogic.Deployer
commands require you to provide the user credentials of a WebLogic Server administrator.
Table A-3 User Credentials Arguments
Argument | Definition |
---|---|
-username username
|
Administrator username. If you supply the |
-password password
|
Password of the administrator user. To avoid having the plain text password appear in scripts or in process utilities such as If you want to use a specific configuration file and key file, rather than the default files, use the |
-userconfigfile config-file
|
Location of a user configuration file to use for the administrative username and password. Use this option, instead of the |
-userkeyfile admin-key
|
Specifies the location of a user key file to use for encrypting and decrypting the username and password information stored in a user configuration file (the |
java [ SSL Arguments ] weblogic.Deployer [Connection Arguments] [ { -username username [-password password] } | [ -userconfigfile config-file [-userkeyfile admin-key] ] ] COMMAND-NAME command-options [Common Arguments]
The common arguments described in Table A-4 can be used with any commands described in Commands and Options.
Table A-4 Common Arguments for weblogic.Deployer
Argument Name | Description |
---|---|
-advanced |
Prints full command-line help text for all |
-debug |
Display debug messages in the standard output. |
-examples |
Display example command lines for common tasks. |
-help |
Prints command-line help text for the most commonly used |
-noexit |
By default The |
-noversion |
Indicates that If you use this option, you cannot use versioned applications. |
-nowait |
|
-output <raw | formatted> |
(Deprecated.) Either |
-purgetasks |
Indicates that |
-remote |
Indicates that |
-timeout seconds |
Maximum time, in seconds, to wait for the deployment task to complete. After the time expires, |
-verbose |
Additional progress messages, including details about the prepare and activate phases of the deployment. |
-version |
Prints version information for |
The following sections describe the weblogic.Deployer
commands and command options used to perform deployment tasks with WebLogic Server:
Note:
weblogic.Deployer
commands are displayed in bold type to distinguish them from command options.
Attempt to cancel a running deployment task.
java [SSL Arguments] weblogic.Deployer Connection Arguments [User Credentials Arguments] -cancel task_id [Common Arguments]
Command or Option | Definition |
---|---|
task_id |
Identifier of the deployment task to cancel. Specify the identifier by using the |
The following command starts a deployment operation and specifies the task identifier, myDeployment
:
java weblogic.Deployer -adminurl http://localhost:7001
-username weblogic -password weblogic
-deploy ./myapp.ear -id myDeployment
If the deployment task has not yet completed, the following command attempts to cancel the deployment operation:
java weblogic.Deployer -adminurl http://localhost:7001
-username weblogic -password weblogic
-cancel -id myDeployment
Deploys or redeploys an application or module.
Note:
The -ACTIVATE
command, an alias for deploy, is deprecated.
java [SSL Arguments] weblogic.Deployer Connection Arguments [User Credentials Arguments] -deploy [[-name] deployment_name] [-source] file [-plan file] [-targets target_list] [-submoduletargets target_list] [-upload] [-stage | -nostage | -external_stage] [-planstage | -plannostage | -planexternal_stage] [-retiretimeout seconds] [-library [-libspecver version] [-libimplver version]] [-altappdd file] [-altwlsappdd file] [-securityModel] [-enableSecurityValidation] [-id task_id] [Common Arguments]
Command or Option | Definition |
---|---|
-name deployment_name
|
Deployment name to assign to a newly-deployed application or standalone module. Both the
|
-source file
|
Archive file or exploded archive directory to deploy. You can omit the |
-plan file
|
Deployment plan to use when deploying the application or module. By default, |
-targets target_list
|
Targets on which to deploy the application or module. The If you do not specify a target list with the deploy command, the target defaults to:
|
-submoduletargets target_list
|
JMS Server targets for resources defined within a JMS application module. See Using Sub-Module Targeting with JMS Application Modules and Using WLST to Manage JMS Servers and JMS System Resources in Administering JMS Resources for Oracle WebLogic Server. |
-upload |
Transfers the specified deployment files, including deployment plans and alternate deployment descriptors, to the Administration Server. Use this option when you are on a remote machine and you cannot copy the deployment files to the Administration Server by other means. The application files are uploaded to the WebLogic Server Administration Server upload directory prior to distribution and deployment. |
-stage | -nostage | -external_stage |
Staging mode to use when deploying or distributing an application:
|
-planstage | -plannostage | -planexternal_stage |
Staging mode to use when deploying or distributing a deployment plan independently of an application archive:
If you do not specify a staging mode, the deployment plan uses the value specified for application staging as the default. |
-retiretimeout seconds
|
Number of seconds before WebLogic Server retires the currently-running version of this application or module. See Redeploying a New Version of an Application. |
-library |
The deployment as a shared Java EE library or optional package. You must include the |
-libspecver version
|
Specification version of a Java EE library or optional package. This option can be used only if the library or package does not include a specification version in its manifest file. |
-libimplver version
|
Implementation version of a Java EE library or optional package. This option can be used only if the library or package does not include an implementation version in its manifest file. |
-usenonexclusivelock |
Deployment operation uses an existing lock, already acquired by the same user, on the domain. This option is helpful in environments where multiple deployment tools are used simultaneously and one of the tools has already acquired a lock on the domain configuration. |
-altappdd file
|
(Deprecated.) Name of an alternate Java EE deployment descriptor ( |
-altwlsappdd file
|
(Deprecated.) Name of an alternate WebLogic Server deployment descriptor ( |
-securityModel [ DDOnly | CustomRoles | CustomRolesAndPolicies | Advanced ] |
Security model to use for this deployment. |
-enableSecurityValidation |
Enable validation of security data. |
-id task_id
|
Task identifier of a running deployment task. You can specify an identifier with the |
See the following sections for examples of using the -deploy
command:
Prepares deployment files for deployment by copying deployment files to target servers and validating them.
A distributed application can be started quickly with the "Start" command. You can start the application in administration mode, or make it available to administration and client requests. While in administration mode, the application can be accessed only by internal clients through a configured administration port. External clients cannot access the application.
java [SSL Arguments] weblogic.Deployer Connection Arguments [User Credentials Arguments] -distribute [[-name] deployment_name] [-source] file [-plan file] [-targets target_list] [-submoduletargets target_list] [-upload] [-stage | -nostage | -external_stage] [-planstage | -plannostage | -planexternal_stage] [-library [-libspecver version] [-libimplver version]] [-altappdd file] [-altwlsappdd file] [-securityModel] [-enableSecurityValidation] [-id task_id] [Common Arguments]
Command or Option | Definition |
---|---|
-name deployment_name
|
Deployment name to assign to the distributed application or module. Both the
|
-source file
|
Archive file or exploded archive directory to distribute. You can omit the |
-plan file
|
Deployment plan to distribute with the application or module, used to configure the application. |
-targets target_list
|
Targets on which to distribute the application or module. The If you do not specify a target list with the distribute command, the target defaults to:
|
-submoduletargets target_list
|
JMS Server targets for resources defined within a JMS application module. See Using Sub-Module Targeting with JMS Application Modules and Using WLST to Manage JMS Servers and JMS System Resources in Administering JMS Resources for Oracle WebLogic Server. |
-upload |
Transfers the specified deployment files, including any specified deployment plans, to the Administration Server before distribution. Use this option when you are on a remote machine and you cannot copy the deployment files to the Administration Server by other means. The application files are uploaded to the WebLogic Server Administration Server upload directory prior to distribution. |
-stage | -nostage | -external_stage |
Staging mode to use when deploying or distributing an application:
|
-planstage | -plannostage | -planexternal_stage |
Staging mode to use when deploying or distributing a deployment plan independently of an application archive:
If you do not specify a staging mode, the deployment plan uses the value specified for application staging as the default. |
-library |
Identifies the deployment as a shared Java EE library or optional package. You must include the |
-libspecver version
|
Specification version of a Java EE library or optional package. This option can be used only if the library or package does not include a specification version in its manifest file. |
-libimplver version
|
Implementation version of a Java EE library or optional package. This option can be used only if the library or package does not include a implementation version in its manifest file. |
-altappdd file
|
(Deprecated.) Name of an alternate Java EE deployment descriptor ( |
-altwlsappdd file
|
(Deprecated.) Name of an alternate WebLogic Server deployment descriptor ( |
-securityModel [ DDOnly | CustomRoles | CustomRolesAndPolicies | Advanced ] |
Security model to be used for this application. |
-enableSecurityValidation |
Enable validation of security data. |
-id task_id
|
Task identifier of a running deployment task. You can specify an identifier with the |
The distribute
command operates similar to deploy
, but WebLogic Server does not start the application or module on target servers. See the examples links for "Deploy" command for more information.
Lists the deployment names for applications and standalone modules deployed, distributed, or installed to the domain.
java [SSL Arguments] weblogic.Deployer Connection Arguments [User Credentials Arguments] -listapps [Common Arguments]
Command or Option | Definition |
---|---|
-listapps
|
Lists the deployment names for applications and standalone modules deployed, distributed, or installed to the domain |
Displays the status of deployment tasks currently running in the domain.
java [SSL Arguments] weblogic.Deployer Connection Arguments [User Credentials Arguments] <-list | -listtask> [task_id] [Common Arguments]
Command or Option | Definition |
---|---|
task_id
|
Identifier of a deployment task to display. |
Redeploys a running application or part of a running application.
java [SSL Arguments] weblogic.Deployer Connection Arguments [User Credentials Arguments] -redeploy [[-name] deployment_name] [-plan file] [-targets target_list] [-submoduletargets target_list] [-upload] [-delete_files] [-retiretimeout seconds] [-id task_id] [-rmiGracePeriod seconds] [Common Arguments]
Command or Option | Definition |
---|---|
-name deployment_name
|
Deployment name of a deployed application or module. The |
-source file
|
Archive file or exploded archive directory to distribute, deploy, or redeploy. When used with the Note: Do not specify the To specify multiple files for a partial redeployment, omit the Note: To redeploy an entire Java EE module within an enterprise application, use the module-targeting syntax, |
-plan file
|
Deployment plan to use when distributing, deploying, or redeploying. When redeploying an application, the |
-targets target_list
|
Targets on which to redeploy the application or module. The Note: To redeploy an entire Java EE module within an enterprise application, use the module-targeting syntax, If you do not specify a target list with the redeploy command, the target defaults to:
If you do not specify a target list with the redeploy command, the application is redeployed on all of its current target servers. |
-submoduletargets target_list
|
JMS Server targets for resources defined within a JMS application module. See Using Sub-Module Targeting with JMS Application Modules and Using WLST to Manage JMS Servers and JMS System Resources in Administering JMS Resources for Oracle WebLogic Server. |
-upload |
Transfers the specified deployment files, including deployment plans and alternate deployment descriptors, to the Administration Server. Use this option when you are on a remote machine and you cannot copy the deployment files to the Administration Server by other means. The application files are uploaded to the WebLogic Server Administration Server upload directory prior to distribution and deployment. |
-delete_files |
Removes static files from a server's staging directory. java weblogic.Deployer -adminurl http://myserver:7001 -username weblogic -password weblogic -name myapp -targets myapp@myserver -redeploy -delete_files myapp/tempindex.html
Note:
|
-retiretimeout seconds
|
Number of seconds before WebLogic Server retires the currently-running version of this application or module. See Redeploying a New Version of an Application. |
-rmiGracePeriod seconds
|
The amount of time, in seconds, that the work manager accepts and schedules RMI calls until there are no more RMI requests arriving within the RMI grace period during a |
-id task_id
|
Task identifier of a running deployment task. You can specify an identifier with the deploy, redeploy, or undeploy commands, and use it later as an argument to the cancel or list commands. Make sure that the identifier is unique to all other running deployment tasks. The system automatically generates a unique identifier if you do not specify one. |
Makes a stopped (inactive) application available to clients on target servers. The start
command does not redistribute deployment files to target servers. Optionally, with the adminmode
option, starts the application in administration mode, which makes it available only via a configured administration channel. In order to issue a start
command, the files must already be available through a deploy
or distribute
command.
Note:
The activate
command, an alias for start
, is deprecated.
java [SSL Arguments] weblogic.Deployer Connection Arguments [User Credentials Arguments] -start [-adminmode] [-name] deployment_name [-appversion version] [-planversion version] [-targets target_list] [-submoduletargets target_list] [-retiretimeout seconds] [-id task_id] [Common Arguments]
Command or Option | Definition |
---|---|
-adminmode |
Start application in administration mode, not Production mode (which is the default). |
-name deployment_name
|
Deployment name of a deployed application or module. The |
-appversion version
|
Version of the application to start. |
-planversion version
|
Version of the deployment plan to use when starting the application. |
-targets target_list
|
Targets on which to start the application or module. The If you do not specify a target list with the start command, the target defaults to:
If you do not specify a target list with the start command, the command is performed on all of the application's current targets. |
-submoduletargets target_list
|
JMS Server targets for resources defined within a JMS application module. See Using Sub-Module Targeting with JMS Application Modules and Using WLST to Manage JMS Servers and JMS System Resources in Administering JMS Resources for Oracle WebLogic Server. |
-retiretimeout seconds
|
Number of seconds before WebLogic Server retires the currently-running version of this application or module. See Redeploying a New Version of an Application. |
-id task_id
|
Task identifier of a running deployment task. You can specify an identifier with the distribute, deploy, redeploy, start, or undeploy commands, and use it later as an argument to the cancel or list commands. Make sure that the identifier is unique to all other running deployment tasks. The system automatically generates a unique identifier if you do not specify one. |
Makes an application inactive and unavailable administration and client requests. All of the application's staged files remain available on target servers for subsequent start
, deploy
, redeploy
, or undeploy
actions. Optionally, choose to make the application unavailable to client requests by placing it in administration mode with the adminmode
option. While in administration mode, the application be accessed only through a configured administration channel.
Note:
The deactivate
command, an alias for stop
, is deprecated.
java [SSL Arguments] weblogic.Deployer Connection Arguments [User Credentials Arguments] -stop [-adminmode] [-name] deployment_name [-appversion version] [-planversion version] [-targets target_list] [-submoduletargets target_list] [-ignoresessions] [-graceful] [-rmiGracePeriod seconds] [-id task_id] [Common Arguments]
Argument or Option | Definition |
---|---|
-adminmode |
Indicates that a running application should switch to administration mode and accept only administration requests via a configured administration channel. If this option is not specified, the running application is stopped and cannot accept administration or client requests until is it restarted. |
-name deployment_name
|
Deployment name of a deployed application or module. The |
-appversion version
|
Version identifier of the deployed application. |
-planversion version
|
Version identifier of the deployment plan. |
-targets target_list
|
Targets on which to stop the application or module. The If you do not specify a target list with the stop command, the target defaults to:
If you do not specify a target list with the stop command, the command is performed on all of the application's current targets. |
-submoduletargets target_list
|
JMS Server targets for resources defined within a JMS application module. See Using Sub-Module Targeting with JMS Application Modules and Using WLST to Manage JMS Servers and JMS System Resources in Administering JMS Resources for Oracle WebLogic Server. |
-graceful |
Stops the application after existing HTTP clients have completed their work. If you do not specify the |
-rmiGracePeriod seconds
|
The amount of time, in seconds, that the work manager accepts and schedules RMI calls until there are no more RMI requests arriving within the RMI grace period during a |
-ignoresessions |
Immediately places the application into administration mode without waiting for current HTTP sessions to complete. |
-id task_id
|
Task identifier of a running deployment task. You can specify an identifier with the distribute, deploy, redeploy, start, stop, or undeploy commands, and use it later as an argument to the cancel or list commands. Make sure that the identifier is unique to all other running deployment tasks. The system automatically generates a unique identifier if you do not specify one. |
Stops the deployment unit and removes staged files from target servers.
Note:
The REMOVE
command, an alias for undeploy
, is deprecated.
Caution:
When you undeploy an application that contains application-scoped resources, the resources are deleted along with the application, which can potentially cause abandoned transactions or lost messages as a result of deleted JMS destinations. For more information, see Unregister Resource Grace Period in Developing JTA Applications for Oracle WebLogic Server.
You should only undeploy applications that you are certain you want to completely remove; to temporarily stop client access to applications, use the stop
command, described in Stop, instead.
java [SSL Arguments] weblogic.Deployer Connection Arguments [User Credentials Arguments] -undeploy [-name] deployment_name [-appversion version] [-planversion version] [-targets target_list] [-submoduletargets target_list] [-graceful] [-ignoresessions] [-rmiGracePeriod seconds] [-id task_id] [Common Arguments]
Command or Option | Definition |
---|---|
-name deployment_name
|
Deployment name of a deployed application or module. The |
-appversion version
|
Version identifier of the deployed application. |
-planversion version
|
Version identifier of the deployment plan. |
-targets target_list
|
Targets from which the application or module are undeployed. Note: Any target not included in the target list is not removed. The |
-submoduletargets target_list
|
JMS resources to be undeployed. Note: Any sub-module target not included in the target list is not removed. See Using Sub-Module Targeting with JMS Application Modules and Using WLST to Manage JMS Servers and JMS System Resources in Administering JMS Resources for Oracle WebLogic Server. |
-graceful |
Stops the application after existing HTTP clients have completed their work. If you do not specify the -graceful option, WebLogic Server immediately stops the application or module. See Taking a Production Application Offline. The module is undeployed after it is stopped. |
-rmiGracePeriod seconds
|
The amount of time, in seconds, that the work manager accepts and schedules RMI calls until there are no more RMI requests arriving within the RMI grace period during a |
-ignoresessions |
Immediately stops and undeploys the application without waiting for current HTTP sessions to complete. |
-id task_id
|
Task identifier of a running deployment task. You can specify an identifier with the distribute, deploy, redeploy, start, stop, or undeploy commands, and use it later as an argument to the cancel or list commands. Make sure that the identifier is unique to all other running deployment tasks. The system automatically generates a unique identifier if you do not specify one. |
Updates an application's deployment plan by redistributing the plan files and reconfiguring the application based on the new plan contents.
Note:
update
cannot be used to update an application's resource bindings. To update the resource bindings for an application, you must use the Redeploy command.
java [SSL Arguments] weblogic.Deployer Connection Arguments [User Credentials Arguments] -update -plan deployment_plan [-name] deployment_name [-appversion version] [-planversion version] [-targets target_list] [-submoduletargets target_list] [-upload] [-id task_id] [Common Arguments]
Argument or Option | Definition |
---|---|
-plan deployment_plan
|
Deployment plan to use for updating the application's configuration. The specified deployment plan must be valid for the application's target servers. For example, the plan cannot contain null variables for required resources unless those resources were previously defined in the associated desrciptors. Update operations update only those descriptors for which there is a changed, not null value in the deployment plan. If a plan that is used by an update operation contains null variables, the current values in the corresponding descriptors are not updated. |
-name deployment_name
|
Deployment name of a deployed application or module. The |
-appversion version
|
Version identifier of the deployed application. |
-planversion version
|
Version identifier of the deployment plan. |
-targets target_list
|
Targets on which to update the application or module. The If you do not specify a target list with the update command, the target defaults to:
If you do not specify a target list with the update command, the command is performed on all of the application's current targets. |
-submoduletargets target_list
|
JMS Server targets for resources defined within a JMS application module. See Using Sub-Module Targeting with JMS Application Modules and Using WLST to Manage JMS Servers and JMS System Resources in Administering JMS Resources for Oracle WebLogic Server. |
-upload |
Uploads a new deployment plan to the Administration Server before updating the application. |
-id task_id
|
Task identifier of a running deployment task. You can specify an identifier with the distribute, deploy, redeploy, update, start, stop, or undeploy commands, and use it later as an argument to the cancel or list commands. Make sure that the identifier is unique to all other running deployment tasks. The system automatically generates a unique identifier if you do not specify one. |
This section demonstrates an application's config.xml
file and the corresponding weblogic.Deployer
command to deploy the application.
Assuming:
mycluster
is a cluster name
D1C2S1
and D1C2S2
are server names
RemoteJMSServer1
and RemoteJMSServer2
are JMS server names
The application's config.xml
file would contain:
<AppDeployment Name="dd-remote-cluster" SourcePath="./udd-debug-deployment-on-remote-cluster-jms.xml" Targets="mycluster"> <SubDeployment Name="RemoteCluster" Targets="mycluster"/> <SubDeployment Name="D1C2S2" Targets="D1C2S2"/> <SubDeployment Name="RemoteClusterServers" Targets="D1C2S1,D1C2S2"/> <SubDeployment Name="RemoteClusterJMSServers" Targets="RemoteJMSServer1,RemoteJMSServer2"/> <SubDeployment Name="RemoteQueue1" Targets="RemoteJMSServer1"/> </AppDeployment>
The weblogic.Deployer
-deploy
command to deploy the application would be:
java weblogic.Deployer -adminurl t3://MySystem:10000 -username system -password system -name dd-remote-cluster -deploy "config\jms\udd-debug-deployment-on-remote-cluster-jms.xml" -targets mycluster -submoduletargets RemoteCluster@mycluster, D1C2S2@D1C2S2, RemoteClusterServers@D1C2S1, RemoteClusterServers@D1C2S2, RemoteClusterJMSServers@RemoteJMSServer1, RemoteClusterJMSServers@RemoteJMSServer2, RemoteQueue1@RemoteJMSServer1