Sets the file 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 | Required | Description |
---|---|---|
FD_ORACLE_MW_HOME | Yes | The oracle middleware home directory, which will contain subfolders such as oracle_common, wlsserver_10.3, coherence*, etc. |
FDADF_REPOSITORY_NAME | Yes | The name of the application's MDS repository. |
FDADF_MDS_FILE_PATH | Yes | The location of the file metadata store. |
Project Properties
Property Name | Required | Description |
---|---|---|
FDADF_PARTITION_NAME | No | The name of the partition for the application's customization and personalization data. |
User customizations will be stored under this partition. |
Inputs
Input Name | 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 setAppMetadataRepositoryFile operation must be executed on the same endpoint as the subsequent deployEAR operation so that the modified EAR is available for deployment.