Creates or updates EIS Entries defined within properties files. The properties files will be processed for property replacement using $VARIABLE_NAME format. See the Appendix for more information about property replacement.

If deploying to a cluster that does not make use of shared storage, consider placing the syncEISToCluster operation in the workflow after the createOrUpdateEISEntries operation.

Environment/Instance 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 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 FILE_PATH_TO_PROPERTIES 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. Each EIS Adapter plan file is backed up to FD_TEMP_DIR/configbackup before it is modified. As with all files in the endpoint working directory, these files will be saved for 3 days before being deleted. It is important to set up the properties files like the examples below.

Example Folder Structure

• Properties file can be named per your requirements. See Properties File Format.
• eisconfigurations.properties – This is the main properties file. The path to it is referenced by FILE_PATH_TO_PROPERTIES.
• DEV/ eisconfigurations.properties - optionally create a file here and override some properties with it per environment. The filename must match.
• PROD/ eisconfigurations.properties - optionally have several environments.
  • Sub folder names for environment overrides must be FlexDeploy environment code

Example Property File

This sample file creates 3 EIS entries with properties. Property names can be gathered from the Weblogic console, WLST, Oracle's documentation, or existing plan.xml files.

 EISList=SOADB,SOAJMS,SOARODB
 SOADB.Adapter=DbAdapter
 SOADB.JNDI=eis/db/SOA
 SOADB.properties.XADataSourceName=jdbc/ebs01

 SOAJMS.Adapter=JmsAdapter
 SOAJMS.JNDI=eis/jms/SOAJMS
 SOAJMS.properties.ConnectionFactoryLocation=jms/ConnectionFactoryName

 SOARODB.Adapter=DbAdapter
 SOARODB.JNDI=eis/db/SOASOARODB
 SOARODB.properties.XADataSourceName=jdbc/ebs02

Properties File Format

Multiple EIS Entries can be defined in the properties file. The properties file must start with a list of EIS Entries present in the format EISList=eis1,eis2,eis3. Change eis1, eis2, eis3 to the names of the EIS Entries for your projects. Any number of EIS Entries is acceptable. The properties files will be processed for property replacement using $VARIABLE_NAME format. See Property Replacement Support for more information about property replacement.

Required Properties

Each EIS Entry must contain the following required properties

The ConnectionFactoryInterface is an optional property. If not specified in your properties file, the default value will apply. The default value varies by adapter name.

User-Specified Properties

Any number of properties of any kind may be applied to each EIS Entry. Please use this format:

 <EISNAME>.properties.username=weblogic
 <EISNAME>.properties.password=welcome1