|
|
This section describes how to deploy resource adapters after you start the servers in your cluster. For information about how to set up and start your clustered deployment, and which adapters are deployed by default in your ProductName domains, see Configuring a Clustered Deployment.
After you start the servers in your cluster, you can deploy resource adapters by using one of the following methods:
The weblogic.Deployer utility is a Java-based deployment tool that provides a command-line interface to the WebLogic Server deployment API. For information, see weblogic.Deployer Utility.
The following example demonstrates how to deploy the sample DBMS adapter, which you received with your ProductName software, into a cluster named MyCluster. The cluster contains two managed servers: MyServer1 and MyServer2. The following table describes the cluster configuration.
Use the following command to deploy the DBMS adapter in this example cluster.
| Note: | The following code listing represents a single command. It is shown here on multiple lines for the sake of readability. On your command line, however, it must be entered as one physical line. |
java -classpathWL_HOME\lib\weblogic.jar weblogic.Deployer
-adminurl t3://127.0.0.5:7005 -userusername-passwordpassword-upload -stage
-sourceWL_HOME\adapters\dbms\lib\BEA_WLS_DBMS_ADK.ear
-name BEA_WLS_DBMS_ADK
-targets BEA_WLS_DBMS_ADK.rar@MyCluster
-activate
In the preceding command line:
-adminurl—Specifies the URL for the administration server in the cluster.-user—Specifies the username used for authentication by the administration server. -password—Specifies the username used for authentication by the administration server.-upload—Uploads the EAR file to the administration server. You can omit this option when you run the weblogic.Deployer utility on the administration server. However, it is required when you are not running the weblogic.Deployer utility on the administration server. -stage—Instructs the WebLogic Server deployment facility to stage the EAR file to all managed servers prior to activation.-source—Specifies the location of the EAR file for the resource adapter. (WL_HOME represents the directory in which you installed ProductName, for example C:\bea\weblogic81\integration.)-name—Specifies the name of the enterprise application for the resource adapter, which should be the same as the logical name for the adapter. This is a unique identifier for a resource adapter.-targets—Specifies the subcomponents contained in the previously specified EAR file for the adapter. This is a comma-separated list of subcomponents. (There are no spaces between the items in the list.) This sample command specifies that the RAR is deployed to the cluster.
| Note: | The RAR component from the EAR—not the design-time Web application—is the target for deployment. |
For details about valid target components, see WebLogic Integration Deployment Resources..
-activate—Activates the application in the domain.
For the procedure to start the WebLogic Server Administration Console (and the administration server, if necessary), see Overview of WebLogic Server System Administration.
DeploymentsApplications) the Applications node in the domain in which you want to deploy an adapter.The WebLogic Server wizard is displayed in the main console window. It guides you through the process of configuring and deploying your adapter.
WL_HOME\adapters\dbms\lib\BEA_WLS_DBMS_ADK.ear
In the preceding line, WL_HOME represents the directory in which you installed ProductName, for example, C:\bea\weblogic81\integration.
| Note: | When you configure an exploded application or component directory, WebLogic Server deploys all components it finds in and below the specified directory. |
-targets and -stage options in Using the weblogic.Deployer Command-Line Utility.For information about using the WebLogic Server Administration Console to deploy applications, see Enterprise Applications in the Adminstration Console Online Help.
|