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 target 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.
...
Project Properties
Property Name | Property Code |
|---|
Required
Description
FD_ORACLE_MW_HOME
Yes
The oracle middleware home directory, which will contain sub-folders such as oracle_common, wlsserver_10.3, coherence*, etc.
FDADF_REPOSITORY_NAME
Yes
(/em). When administrator creates MDS repository name will be assigned to MDS repository.FDADF_MDS_JNDI_LOCATION
Yes
The JNDI location of Data Source for connection to MDS database repository.
Project Properties
Required | Description | ||
|---|---|---|---|
MDS(ADF) Partition Name |
| No | The name of the partition for the application's customization and personalization data. |
Inputs
...
Input Name
...
Required
...
Description
Outputs
Required
Description
Artifacts
This operation will consume an ADF EAR artifact from the artifact repository.
...
This operation will select all available endpoints associated to the environment instance Target 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.
...
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.