Creates or updates the data sources that are 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. Best practice would be to use the WebLogic DataSource Name as the list identifier for datasources.

Blog Posts

• https://flexagon.com/2017/03/automating-the-creation-of-weblogic-configurations/
• https://flexagon.com/2016/11/save-time-and-headache-automate-your-weblogic-data-source-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.
WebLogic configuration files including Data Sources 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.

It is important to set up the properties files like the examples below.

Example Folder Structure

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

Example Property File

This sample file defines two simple data sources with a sub-set of the available properties.

DSList=DS1,DS2

DS1.DataSourceType=Generic
DS1.URL=jdbc:oracle:thin:@localhost:1521:xe
DS1.ConnectionClass=oracle.jdbc.OracleDriver
DS1.DSName=DS1
DS1.User=${{FLX_DB_USER_FDADMIN}}
DS1.Targets=MS1
DS1.JNDINames=jdbc/DS1
DS1.Password=${{FLX_DB_PASSWORD_FDADMIN}}
DS1.MinCapacity=0

DS2.DataSourceType=Generic
DS2.URL=jdbc:oracle:thin:@localhost:1521:xe
DS2.ConnectionClass=oracle.jdbc.OracleDriver
DS2.DSName=DS2
DS2.User=${{FLX_DB_USER_FDADMIN}}
DS2.Targets=MS1
DS2.JNDINames=jdbc/DS2
DS2.Password=${{FLX_DB_PASSWORD_FDADMIN}}
DS2.MinCapacity=0

# This format is also supported for datasource properties.
DS1.properties.oracle.net.CONNECT_TIMEOUT=30000
DS2.properties.key1=value1
DS2.properties.key2=value2
DS2.systemProperties.key3=value3
DS2.systemProperties.key4=value4

Example Gridlink DataSource Property File

This sample file defines a GridLink data source with a sub-set of the available properties. It could be combined with other data sources in one file, but is separate here for clarity.

DSList=testName1

testName1.DataSourceType=GridLink
testName1.ConnectionClass=oracle.jdbc.OracleDriver
testName1.DSName=testName1
testName1.Targets=AdminServer
testName1.JNDINames=test/karl1
testName1.TestConnectionsOnReserve=true
testName1.URL=jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=databaseserverhostname)(PORT=1521)))(CONNECT_DATA=(SID=fmt01)))
testName1.DatabaseName=fmt01
testName1.User=system
testName1.Password=*****
testName1.InitialCapacity=0
testName1.MaxCapacity=50

Properties File Format

Multiple data sources can be defined in the properties files. The properties files must start with a list of data sources present in the format DSList=ds1,ds2,ds3. Change ds1, ds2, ds3 to names that make sense for your project. Any number of data sources is acceptable. The properties files will be processed for property replacement using ${{VARIABLE_NAME}} format. See the Appendix for more information about property replacement.

If using multiple files, make sure that the lists contain unique values across files. Best practice would be to use the Weblogic Datasource Name as the list identifier for datasources.

Required Properties for Generic and Gridlink Datasources

At a minimum, each data source must contain these properties:

Required Properties for Multi Data Source DataSources

At a minimum, each data source must contain these properties:

Optional Properties for Generic and Gridlink DataSources

These properties are optional. If the property is unsupported by the version of WebLogic you are running, it will be ignored. If not specified in your properties file, the WebLogic 12c defaults shown below will apply. This is also true on updating databases, so it is important to include all the properties you use if modifying an existing environment. You may use as many or as few as you like per data source.

Optional Properties for GridLink DataSources

These properties are used only for GridLink DataSources. 

Optional Properties for Multi Data Source DataSources

These properties are used only for Multi Data Source DataSources.