Creates or updates Datasources, EIS entries and JMS objects defined by properties files. The properties files will be processed for property replacement using $VARIABLE_NAME format.
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.
See the Appendix for more information about property replacement.
...
| Property Name | Property Code | Required | Description |
|---|---|---|---|
| Properties File Path | FILE_PATH_TO_PROPERTIES | No | Comma-separated list of paths to the properties file(s). |
Outputs
Output Name | Required | Description |
|---|---|---|
FDWLS_OUT_IS_RESTART_REQUIRED | No | A |
...
Multiple Property lists can be defined in each properties file. They can even hold JMS, DataSources and EIS entries in one file, but it is a best practice to use several files and name them according to their contents. 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. Each properties file must start with one or more lists of elements 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. The properties files will be processed for property replacement using $VARIABLE_NAME format. See Property Replacement Support for more information about property replacement.
...