libraryDeploy
- Karl Henselin
Deploy a library (EAR, WAR, or JAR) to Partition, Resource Group, Resource Group Template or WebLogic Cluster/Server. You must have built archive files as part of build workflow execution prior to running deploy.
The following properties are used to specify the location to deploy.
FDWLS_SERVER_OR_CLUSTER_NAMESFDWLS_PARTITION,FDWLS_RESOURCE_GROUPFDWLS_RESOURCE_GROUP_TEMPLATE.
If all values are specified, they are used in order indicated above.
Prior to WebLogic 12.2.1, only FDWLS_SERVER_OR_CLUSTER_NAMESÂ is used. Read about the deployment options of 12.2.1 at https://blogs.oracle.com/WebLogicServer/entry/domain_partitions_for_multi_tenancy.
Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Oracle Weblogic Home (WL_HOME) |
| Yes | WebLogic Home Directory. (e.g. /u01/oracle/products/fmw/wlserver) |
Weblogic Domain Name |
| Yes | WebLogic Domain Name. |
Weblogic Admin Listen Address |
| Yes | The listener address of the WLS admin server. (e.g. localhost) |
Weblogic Admin Listen Port |
| Yes | The port of the WLS admin server. (e.g. 7001) |
Weblogic Admin SSL Connection |
| No | Indicates whether the admin server is using SSL. |
Weblogic Admin User |
| Yes | The user name for the WLS admin server. |
Weblogic Admin Password |
| Yes | The password for |
Weblogic Application Install Directory |
| No | Base directory to install the WebLogic deployments from. Files will be copied here on Admin Server endpoint by WebLogic plugin prior to installation. For example:Â |
Weblogic Stage Mode |
| Yes | Staging mode for the application you are deploying. Valid values are stage, nostage, and external_stage. Recommended and default option is stage, in which case deployment archive files are only needed to be accessible by Admin Server and then Admin Server copies files to target managed server. |
Weblogic Deployment Timeout |
| No | Time in milliseconds that the plugin operation will wait for the server to respond. Plugin operation will return as soon as the server responds, but if the deploy doesn't complete before the timeout specified, the plugin operation will fail. If not defined, 300000 will be the value. |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Weblogic Application Name |
| Yes | The name of the application (EAR or WAR) to be deployed. |
Weblogic Server or Cluster Name(s) |
| Yes | WebLogic Server or Cluster name to deploy application. |
Weblogic Partition |
| No | WLS Partition - used in WLS 12.2.1+ |
Weblogic Resource Group |
| No | WLS Resource Group - used in WLS 12.2.1+ |
Weblogic Resource Group Template |
| No | WLS Resource Group Template - used in WLS 12.2.1+ |
Weblogic Versioned Deployment |
| No | Determines whether the plugin will deploy the artifact with a version label. If Plugin will modify |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Server or Cluster Name(s) |
| No | WebLogic Server or Cluster name for deploy operation. Overrides the |
Override File Pattern |
| No | Specify |
Artifacts
This operation consumes an application EAR, WAR, or JAR file artifact from the artifacts repository.
Endpoint Selection
This operation will select all available endpoints associated to the Target which have a resource type of WLS Admin Server. Since the admin server only runs on one server, it is expected that for a given domain, there will only be one endpoint with a resource type set to WLS Admin Server.
Endpoint Execution
This operation will execute on the Admin Server endpoint selected using the WLS Admin Server resource type.
Special Considerations
Locking occurs on the endpoint to ensure multiple configuration change are not concurrently being deployed at the same time for a domain. The lock files are located in {Base Working Directory for the endpoint}/locks with a file name of {Environment Code}_{WebLogic Domain Name>}.
- style