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.
Middleware administrator must configure MDS repository on WebLogic domain and configure Repository Name and MDS File Path 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.
This is not recommended configuration for MDS in production environment, you should use Database based MDS repository.
|Oracle Middleware Home (MW_HOME)|
The oracle middleware home directory, which will contain sub-folders such as
oracle_common, wlsserver_10.3, coherence*, etc.
|MDS(ADF) Repository Name|
The name of the application's MDS repository.
|MDS(ADF) File Path|
The location of the file metadata store.
|MDS(ADF) Partition Name|
The name of the partition for the application's customization and personalization data.
Defaults to the name of the EAR file, minus the extension. User customizations will be stored under this partition.
This operation will consume an ADF EAR artifact from the artifact repository.
This operation will select all available endpoints associated to the environment instance 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 operation will randomly execute on one of the endpoints identified during selection.
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.