Managing Deployment Plans About the Common Deployment Tasks in Fusion Middleware Control

10-30 Oracle Fusion Middleware Administrators Guide 5. You can view the description and values for the attributes. Table 10–2 describes the configuration attributes that are specific to MDS. Note that other attributes, such as ConfigMBean appear in the browser, but these are generic attributes for all MBeans. Table 10–2 MDS Configuration Attributes for Deployed Applications Attribute Description AppMetadataRepositoryInfo Read only. Describes the metadata repository partition where the application is deployed. AutoPurgeTimeToLive Automatically purge versions of metadata documents older than the given time interval, specified in seconds. Any unlabeled versions older than this time interval are automatically purged on any subsequent update from this application. If the value is not set, versions are not automatically purged. DeployTargetRepository The name of the target repository configured for the application. Deploying Applications 10-31 6. To view or modify an attribute, select the attribute. The attribute page is displayed. 7. If the attribute is not read-only, you can change the values. For example, for AutoPurgeTimeToLive, you can change the interval, by entering a new value in Value. 8. Click Apply. 9. Navigate up to ADFConfig the parent of MDSAppConfig and select it. ExternalChangeDetection Specifies that the MDS Repository is polled to determine if any metadata changes have been performed on other cluster nodes or by other applications. If changes are detected, notifications are sent to applications that share the repository. Multiple applications can share metadata that is deployed to a shared repository. Changes performed by one application to this shared metadata can be detected by the other application. To do this, both the applications should configure the shared repository as part of their application configuration. If the MDS Repository is being used by more than one application in the same JVM, then MDS polls for changes if any of those applications have ExternalChangeDetection set to true. This attribute should only be set to false if the application metadata is never updated or if it is used only by this application and on a single server node. This attribute is applicable only to database-based repositories. The default is true. ExternalChangeDetectionInterval The maximum time interval, in seconds, to poll the MDS Repository to determine if there are external metadata changes. This attribute is only valid if ExternalChangeDetection is enabled. If the MDS Repository is shared and being used by more than one application in the same JVM, MDS uses the lowest of the values specified in the different applications for this attribute. As a result, changing the value of this parameter in one application only has an effect if the new value is lower than any values specified in the other applications. The default is 30 seconds. MaximumCacheSize The maximum metadata cache size limit, in kilobytes. If the value is 0, caching is disabled. If no value is specified, there is no cache limit. In this case, cached data is stored indefinitely. ReadOnlyMode Changes the application to read-only mode, so that no updates can be made to the applications repository partition, including configuration and application metadata. RetryConnection Enables the application to retry the connection to the metadata repository after connection failure. SharedMetadataRepositoryInfo Read only. Specifies the MDS Repository partition used by the application. Note that an application can use more than one shared metadata repository. Table 10–2 Cont. MDS Configuration Attributes for Deployed Applications Attribute Description 10-32 Oracle Fusion Middleware Administrators Guide 10. In the Operations tab, click Save. 11. Click Invoke.

10.9.2 Changing the MDS Configuration Using WLST

You can change the MDS configuration of an application using WLST. The following example shows a WLST script that reads and then sets the ReadOnlyMode attribute: Getting ReadOnlyMode Attribute from MBean connectusername,password,hostname:port application = application_name attribute = ReadOnlyMode beanName = oracle.adf.share.config:ApplicationName=+ application +,name=MDSAppConfig,type=ADFConfig,Application=+ application +,ADFConfig=ADFConfig, beanObjectName = ObjectNamebeanName beans = mbs.queryMBeansbeanObjectName, None bean = beans.iterator.next.getObjectName custom value = mbs.getAttributebean, attribute print value Setting ReadOnlyMode Attribute from MBean attr = Attributeattribute, Boolean0 mbs.setAttributebean,attr value = mbs.getAttributebean, attribute print value Saving the Changes. This is required to persist the changes. adfConfigName = oracle.adf.share.config:ApplicationName=+ application + ,name=ADFConfig,type=ADFConfig,Application=+ application + , adfConfigObjectName = ObjectNameadfConfigName adfConfigMBeans = mbs.queryMBeansadfConfigObjectName, None adfConfigMBean = adfConfigMBeans.iterator.next.getObjectName mbs.invokeadfConfigMBean, save, None, None

10.9.3 Restoring the Original MDS Configuration for an Application

To restore the original MDS configuration for an application: 1. Navigate to the applications home page by expanding the farm, then Application Deployments. Then, select an application. The applications home page is displayed. 2. From the Application Deployment menu, choose System MBean Browser. The System MBean Browser page is displayed. 3. Expand Application Defined MBeans, then oracle.adf.share.config, then Server: name , then Application: name, then ADFConfig, and then ADFConfig. 4. Select the Operations tab.