Skip Headers
Oracle® Fusion Middleware Administrator's Guide for Oracle Identity Manager
11g Release 2 (11.1.2)

Part Number E27149-04
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

22 Using Enterprise Manager for Managing Oracle Identity Manager Configuration

Oracle Identity Manager stores the configuration files in MDS. Most of the configurations are exposed as MBeans. Therefore, you can control the configuration values by using Enterprise Manager. In some instances, might have to export the complete files to file system, make the necessary changes, and then import the files back into the repository, as described in the following sections:

22.1 Using MBeans for Configuration Changes

To change configuration settings by using Mbeans:

  1. When the administrative server and at least one Oracle Identity Manager managed server is running, login to Oracle Enterprise Manager Fusion Middleware Control by using the URL in the following format:

    http://ADMINSTRATION_SERVER:PORT/em

  2. Navigate to Identity and Access, oim. Right-click and navigate to System MBean Browser.

  3. Under Application Defined MBeans, navigate to oracle.iam, Application:oim, XMLConfig, Config.

    All the configuration files are in this location.

22.2 Exporting and Importing Configuration Files

To export or import configuration files:

  1. When the administrative server and at least one Oracle Identity Manager managed server is running, login to Oracle Enterprise Manager Fusion Middleware Control by using the URL in the following format:

    http://ADMINSTRATION_SERVER:PORT/em

  2. Navigate to Identity and Access, oim. Right-click and navigate to System MBean Browser.

  3. Under Application Defined MBeans, navigate to oracle.mds.lcm, Server:oim_server1, Application:oim, MDSAppRuntime.

  4. To export the configuration files:

    1. Click the Operations tab, and then click exportMetaData.

    2. In the toLocation field, enter /tmp or the name of another directory.

    3. Select createSubDir as false.

    4. In the docs field, enter the complete file location as the Element.

    5. Also select false for excludeAllCust, excludeBaseDocs, and excludeExtendedMetadata. Then, click Invoke.

      This exports the file specified in the docs field to the directory specified in the toLocation field.

  5. To import the configuration files:

    1. Click importMetaData.

    2. In the fromLocation field, enter /tmp or the name of the directory in which you have the configuration files.

    3. Select createSubDir as false.

    4. In the docs field, enter the complete file location as the Element. For example, /db/oim-config.xml.

    5. Also select false for excludeAllCust, excludeBaseDocs, and excludeExtendedMetadata. Then, click Invoke.

      This imports the file specified in the docs field to MDS in the toLocation field.