sideBySideDeploy
This operation is designed to allow for production redeployment (side by side deployment) to WebLogic servers. This operation deploys the application in versioned mode. Undeployment of all but one version is completed before the deployment commences. The Weblogic-Application-Version
property is set in the manifest by the plugin. If you prefer to use your own Weblogic-Application-Version
value, please create a workflow with the undeploy and deploy operations instead, and set Weblogic Deployment Max # of Versions
to 1 and Weblogic Versioned Deployment
to true.
Deploys an EAR or WAR file 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_NAMES
FDWLS_PARTITION
,FDWLS_RESOURCE_GROUP
FDWLS_RESOURCE_GROUP_TEMPLATE
.
If all values are specified, they are used in the order listed above.
Prior to WebLogic 12.2.1, only FDWLS_SERVER_OR_CLUSTER_NAMES
was used. Read about the deployment options of 12.2.1 at https://blogs.oracle.com/WebLogicServer/entry/domain_partitions_for_multi_tenancy.
Property Replacement on Deploy
Let's say you want to override adf connections.xml file for specific environment instance deployment.
- Create a file called something like
connections-overrides.xml
and source control it along with your application. This file should be in same folder asconnections.xml
. In this file you can use properties where you need to replace environment instance or project specific values. Enter properties in the following notation:${{PROPERTY_NAME}
}. See Property Replacement Support. - Define the required properties on your deploy workflow, and set the scope to either Environment Instance or Project as appropriate.
- Edit your deploy instance and associate your deploy workflow to it, if not already done.
- Your workflow properties will now appear on either the environment instances or projects depending on the scope, and you can provide values for them.
- In your deploy workflow, edit the deploy step and set the
Override File Pattern
(FDWLS_INP_OVERRIDE_FILE_PATTERN
)
property. The value is in formatactual_file=override_file
. For example,connection.xml=connections-overrides.xml
. - At deploy time, the WebLogic deploy step will run property replacement against the override file using the properties you have defined, and then replace the original file prior to deploying artifact to WebLogic domain.
This can be done for any other files as well. For example, you can override web.xml, weblogic.xml, weblogic-application.xml
files similarly. Alternatively, you can create separate override files for each environment as well and define Override File Pattern
as expression to control which override file is used based on current environment from workflow execution.
Blog Posts
Environment/Instance 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 |
| <