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.
...
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 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.
...
This plugin operation typically consumes an artifact produced by the JDeveloper Plugin's applicationBuild operation. The Weblogic Plugin's deployEAR operation is then typically used to deploy the ear onto a WebLogic Server. This setAppMetadataRepositoryDB operation must be executed on the same agent as the subsequent deployEAR operation such that the modified EAR is available for deployment.