Creates or updates Work Managers defined by properties files. The properties files will be processed for property replacement using ${{VARIABLE_NAME}} format. See Property Replacement Support for more information about property replacement.
...
| Tip |
|---|
If you want to detect changes in WebLogic resource (properties) files and only deploy changed files, you can implement custom workflow as defined in Custom Workflow to detect changes in Properties Files. |
Blog Posts
...
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 Admin User. |
Weblogic Admin Domain Directory |
| No | Weblogic Domain Directory for AdminServer. If not provided, Weblogic Domain Directory will be used. |
Weblogic Domain Directory |
| Yes | Weblogic Domain Directory.(e.g. |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Inputs
Property Name | Property Code | Required | Description |
|---|---|---|---|
Properties File Path | FILE_PATH_TO_PROPERTIES | No | Comma-separated list of paths to the properties file(s). |
Outputs
Output Name | Required | Description |
|---|---|---|
FDWLS_OUT_IS_RESTART_REQUIRED | No | A |
Artifacts
This operation consumes properties-file artifacts.
...
This operation will select all available endpoints associated to the environment instance 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.
...
If Properties File Path is not specified, the FD_ARTIFACTS_DIR folder will be used. If a relative path is specified, the path will be relative to the FD_ARTIFACTS_DIR directory. WebLogic configuration files including JMS modules are backed up to FD_TEMP_DIR/configbackup before modifications. As with all files in the endpoint working directory, these files will be saved for 3 days before being deleted.
Example Folder Structure
...
Properties file can be named as per your requirements. See Example Properties File below.
myWorkManager.properties – This is the main properties file. The path to it is referenced by Properties File Path .
DEV/ myWorkManager.properties- optionally create a file here and override some properties with it per environment. The filename must match.
PROD/ myWorkManager.properties - optionally have several environments.
Sub folder names for environment overrides must be FlexDeploy environment code.
Example Property File
This sample file defines a Work Manager and all of the available properties.
| Tip | |
|---|---|
| title | Backslash in Properties fileIf you want \ (backslash) in any property value, use \\ or \u005c. This is Java properties file load syntax. |
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Example Work Manager Properties
| Code Block |
|---|
#Pound signs make comments. WorkManagerList=myWorkManager myWorkManager.Targets=AdminServer,SOA_Cluster myWorkManager.MaxThreads=5 myWorkManager.MinThreads=1 myWorkManager.CapacityCount=3 myWorkManager.StuckThreadBehavior=Manual myWorkManager.StuckThreadCount=23 myWorkManager.MaxStuckThreadTime=12 myWorkManager.ResumeWhenUnstuck=false myWorkManager.Notes=This work manager was made by FlexDeploy. #Pick at most one of these. #myWorkManager.FairShareRequest=50 #myWorkManager.ResponseTimeRequest=250 myWorkManager.ContextRequestList=contextRequest1,contextRequest2,contextRequest3 #you can provide UserName, GroupName, and/or RequestClassName for each Context Request in the list. myWorkManager.contextRequest1.UserName=weblogic myWorkManager.contextRequest2.GroupName=administrators myWorkManager.contextRequest3.GroupName=users myWorkManager.contextRequest3.RequestClassName=ImportantClass |
The example properties above create the following in Weblogic Console:
...
Properties File Format
Multiple Work Managers can be defined in each properties file. Each properties file must contain a WorkManagerList in order to be included.
...
Only the properties with * after them are required. The rest are optional.
Property Name | Default Value |
Notes | |||
Name | The name from the list is used by default. | ||
MaxThreads | <not set> | ||
MinThreads | <not set> | ||
CapacityCount | <not set> | ||
Targets* | <not set> | Required The targets for the Work Manager, constraints, and Request Classes. | |
Notes | <not set> | ||
StuckThreadsBehavior | Default | (Default | Ignore | Manual) Set to Manual to use the following 3 options. | |
StuckThreadCount | 0 | Only used when | |
MaxStuckThreadTime | 0 | Only used when | |
ResumeWhenUnstuck | true | Only used when | |
Pick at most one of the following: | |||
FairShareRequest | <not set> | Integer that will be used as a percentage of time (e.g. 50) | |
ResponseTimeRequest | <not set> | Integer that will be used as a target time to handle requests in milliseconds (e.g. 150) | |
ContextRequestList | <not set> | A comma-separated list of context request class case names (e.g. case1,case2) | |
contextRequestListname.UserName | <not set> | (e.g. myWorkManger.case1.UserName=weblogic) | |
contextRequestListname.GroupName | <not set> | (e.g. myWorkManger.case2.GroupName=Administrators) | |
contextRequestListname.RequestClassName | <not set> | (e.g. myWorkManger.case2.RequestClassName=ImportantClass) | |