Sets the database connection details for the application (EAR) metadata repository (MDS). EAR file must be present in artifacts folder and there must be only one EAR file in artifacts folder. This works similar to deploy command for WebLogic plugin that operates on EAR file in artifacts folder.
Middleware administrator must configure MDS repository on WebLogic domain and configure Repository Name and JNDI location on Environment Instance as indicated in table below.
This step generally would be added just before Deploy operation, so EAR file will be updated just prior to deploy with MDS details for target domain.
Environment/Instance Properties
| Property Name | Property Code | Required | Description |
|---|---|---|---|
| Oracle Middleware Home (MW_HOME) | FD_ORACLE_MW_HOME | Yes | The oracle middleware home directory, which will contain subfolders sub-folders such as oracle_common, wlsserver_10.3, coherence*, etc. |
| MDS(ADF) Repository Name | FDADF_REPOSITORY_NAME | Yes | The name of the application's MDS repository. |
| MDS(ADF) Repository JNDI Name | FDADF_MDS_JNDI_LOCATION | Yes | The JNDI location of Data Source for connection to MDS database repository. |
Project Properties
| Property Name | Required | Description | |
|---|---|---|---|
| MDS(ADF) Partition Name | FDADF_PARTITION_NAME | No | The name of the partition for the application's customization and personalization data. |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Outputs
Output Name | Required | Description |
|---|---|---|
Artifacts
This operation will consume an ADF EAR artifact from the artifact repository.
Endpoint Selection
This operation will select all available endpoints WLS Admin Server endpoint associated to the environment/instance.You must define only one Endpoint with WLS Admin Server resource type for specific Environment Instance.
Endpoint Execution
This operation will randomly execute on one of the endpoints identified during selection.
...