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.

If using multiple files, make sure that the lists contain unique values across files.

See the Appendix for more information about property replacement.

...

Blog Posts

• https://flexagon.com/2018/04/yes-you-can-create-work-managers-reliably-with-flexdeploy/

Target Properties

Project Properties

Inputs

Outputs

Artifacts

This operation consumes properties-file artifacts.

Endpoint Selection

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.

Endpoint Execution

This operation will execute on the Admin Server endpoint selected using the WLS Admin Server resource type.

Special Considerations

If Properties File Path is Path is not specified, the FD_ARTIFACTS_DIR folder 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 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.

• jmsconfigurations

  myWorkManager.

  properties –

  properties – This is the main properties file. The path to it is referenced by Properties File Path.

• DEV/

  jmsconfigurations

  myWorkManager.properties- optionally create a file here and override some properties with it per environment. The filename must match.

• PROD/

  jmsconfigurations

  myWorkManager.

  properties 

  properties - optionally have several environments.

  • Sub folder names for environment overrides must be FlexDeploy environment code.

Example Property File

This sample file defines a few simple JMS objects with a sub-set Work Manager and all of the available properties. The name used in each of the lists will be the name used on the server.

Anchor
Example Example

...

Example Work Manager Properties

#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.contextRequest2contextRequest3.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.

...

The properties files will be processed for property replacement using ${{VARIABLE_NAME}} format. See Property Replacement Support for more information about property replacement.

Property Definitions

Only the properties with * after them are required. The rest are optional.