Creates or updates JMS Entries 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.

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

https://flexagon.com/2017/03/automating-the-creation-of-weblogic-configurations/

Environment/Instance Properties

Property Name	Property Code	Required	Description
Oracle Weblogic Home (WL_HOME)	`FDWLS_WEBLOGIC_HOME`	Yes	WebLogic Home Directory. (e.g. /u01/oracle/products/fmw/wlserver)
Weblogic Domain Name	`FDWLS_DOMAIN_NAME`	Yes	WebLogic Domain Name.
Weblogic Admin Listen Address	`FDWLS_ADMIN_LISTEN_ADDRESS`	Yes	The listener address of the WLS admin server. (e.g. localhost)
Weblogic Admin Listen Port	`FDWLS_ADMIN_LISTEN_PORT`	Yes	The port of the WLS admin server. (e.g. 7001)
Weblogic Admin SSL Connection	`FDWLS_ADMIN_USE_SSL`	No	Indicates whether the admin server is using SSL.
Weblogic Admin User	`FDWLS_ADMIN_USER`	Yes	The user name for the WLS admin server.
Weblogic Admin Password	`FDWLS_ADMIN_PASSWORD`	Yes	The password for `Weblogic Admin User`.
Weblogic Admin Domain Directory	`FDWLS_ADMIN_DOMAIN_DIRECTORY`	No	Weblogic Domain Directory for AdminServer. If not provided, `Weblogic Domain Directory` will be used.
Weblogic Domain Directory	`FDWLS_DOMAIN_DIRECTORY`	Yes	Weblogic Domain Directory.(e.g. `/u01/oracle/config/domains/soa_domain`)

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). If relative paths are given, they are assumed relative to the `FD_ARTIFACTS_DIR` directory. If this property is not specified, all properties files in the `FD_ARTIFACTS_DIR` directory will be processed.

Outputs

Output Name	Required	Description
FDWLS_OUT_IS_RESTART_REQUIRED	No	A `boolean` value that indicates whether the server needs to be restarted to finish applying the configuration changes. You could use this in a workflow condition.

Artifacts

This operation consumes properties-file artifacts.

Endpoint Selection

This operation will select all available endpoints associated to the environment instance 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 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.
jmsconfigurations.properties – This is the main properties file. The path to it is referenced by Properties File Path .
DEV/ jmsconfigurations.properties- optionally create a file here and override some properties with it per environment. The filename must match.
PROD/ jmsconfigurations.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 of the available properties. The name used in each of the lists will be the name used on the server.

Backslash in Properties file

If you want \ (backslash) in any property value, use \\ or \u005c. This is Java properties file load syntax.

SystemModuleList=Flex_JMSModule1
SubDeploymentList=Flex_JMSSubdeployment1
ConnectionFactoryList=CF1
QueueList=Q1
TopicList=T1
UniformDistributedQueueList=UDQ1
UniformDistributedTopicList=UDT1

Flex_JMSModule1.Targets=MS1

Flex_JMSSubdeployment1.SystemModule=Flex_JMSModule1
Flex_JMSSubdeployment1.Targets=Flex_JMSServer1

CF1.SystemModule=Flex_JMSModule1
CF1.JNDI=jms/CF1
CF1.Targets=MS1
CF1.XAConnectionFactoryEnabled=False
CF1.DefaultTargetingEnabled=True

Q1.SystemModule=Flex_JMSModule1
Q1.JNDI=jms/Q1
Q1.SubDeployment=Flex_JMSSubdeployment1
Q1.DeliveryMode=Persistent

T1.SystemModule=Flex_JMSModule1
T1.JNDI=jms/T1
T1.SubDeployment=Flex_JMSSubdeployment1

UDQ1.SystemModule=Flex_JMSModule1
UDQ1.JNDI=jms/UDQ1
UDQ1.SubDeployment=Flex_JMSSubdeployment1
UDQ1.Notes=Notes on UDQ1

UDT1.SystemModule=Flex_JMSModule1
UDT1.JNDI=jms/UDT1
UDT1.SubDeployment=Flex_JMSSubdeployment1
UDT1.Notes=Notes on UDT1

Properties File Format

Multiple JMS Properties can be defined in each properties file. Each properties file must start with one or more lists of JMS element types present in the file. Any number of element types is acceptable in each file, and any number of each type of element is acceptable as well.