Creates or updates EIS Entries defined within properties files. The EIS entry applications will be updated at the end.

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 deploying to a cluster that does not make use of shared storage, this operation will fail to complete if any of the configured adapters have never been deployed previously. See the generateEISDeploymentPlans operation for information on using multiple plugin operations to create the deployment plans, sync them to all the servers, and then complete the redeployment of the adapter so that they take effect.

Blog Posts

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

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 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. 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 Example Properties File below.
• eisconfigurations.properties – This is the main properties file. The path to it is referenced by Properties File Path.
• 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
SOAJMS.TransactionSupport=LocalTransaction

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 files. The properties files 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.

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

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

Optional Properties

User-Specified Properties

Any number of properties of any kind may be applied to each EIS Entry. Use XADataSourceName or DataSourceName for EIS entry for Data Source. You can see such properties in the Outbound Connection Properties table in WebLogic console. Please use following format:

<EISNAME>.properties.username=weblogic
<EISNAME>.properties.password=welcome1
<EISNAME>.properties.PlatformClassName=oracle.toplink.platform.database.SQLServerPlatform

User-Specified Connection Pool Properties (Added in 4.5.141 Release)

Any number of connection pool properties (pool-params) of any kind may be applied to each EIS Entry. You can see such properties in the Connection Pool table in WebLogic console. Please use following format:

<EISNAME>.pool-param.initial-capacity=0
<EISNAME>.pool-param.max-capacity=201
<EISNAME>.pool-param.capacity-increment=1
<EISNAME>.pool-param.shrinking-enabled=true
<EISNAME>.pool-param.shrink-frequency-seconds=900
<EISNAME>.pool-param.highest-num-unavailable=0
<EISNAME>.pool-param.highest-num-waiters=0
<EISNAME>.pool-param.connection-creation-retry-frequency-seconds=0
<EISNAME>.pool-param.connection-reserve-timeout-seconds=-1
<EISNAME>.pool-param.test-frequency-seconds=0
<EISNAME>.pool-param.test-connections-on-create=false
<EISNAME>.pool-param.test-connections-on-reserve=false
<EISNAME>.pool-param.test-connections-on-release=false
<EISNAME>.pool-param.match-connections-supported=true