Creating a Backup of the Existing Entities Running the Horizontal Migration Utility

Importing and Exporting Data Using the Deployment Manager 5-11 EntityTypePluginsEntityType FilteringCriteria Attribute NamePLUGIN_NAMEName FilterFilter Attribute FilteringCriteria entityDetails entityDetails EntityTypeCustomResourceBundlesEntityType FilteringCriteria Attribute NameRES_NAMEName FilterFilter Attribute FilteringCriteria entityDetails MigrationDetails The configuration file supports three entity types: Jars, Plug-ins, and CustomResourceBundles. For each entity type, the following filters are supported: – Jars: Jar_Type or OJ_TYPE, Jar_Name or OJ_NAME – Plugins: PLUGIN_NAME or plugins.ID – CustomResourceBundles: Resource_Type or RES_TYPE, Resource_Name or RES_NAME ■ TEMP_LOCATION_TO_EXTRACT: Temporary location to keep the files temporarily before packaging for export 3. Run the exportMetaData.sh or exportMetaData.bat script. 4. Specify the following when prompted: ■ Oracle Identity Manager administrator user name to connect to Oracle Identity Manager ■ Oracle Identity Manager administrator password to connect to Oracle Identity Manager ■ JNDI URL to connect to Oracle Identity Manager: t3:localhost:PORT_NUMBER ■ LogFileLocation path where log file is to be generated 5. Verify the export list that is displayed. 6. When prompted for confirmation, enter YES. 7. Verify the export. All the listed items are exported to the destination provided as input. Check the contents of the ZIP package that is created at the destination. In the IMPORT mode, you run the importMetaData.sh or importMetaData.bat script, which is in the OIM_HOMEbin directory. To run the horizontal migration utility in IMPORT mode: 1. Before running the utility, run the client targets by using the following commands: ant fullbuild XellerateClient.view-install ant assemble-ear client-archive 5-12 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager 2. Run the importMetaData.sh or importMetaData.bat script after specifying the following input parameters in the utility script: ■ Username to connect to Oracle Identity Manager. ■ Password to connect to Oracle Identity Manager. ■ JNDI URL to connect to Oracle Identity Manager. ■ Context to connect to Oracle Identity Manager. ■ Path of the package to be imported. ■ Configuration file updated with the information about items to be imported. If this configuration is not used in import, then the entire content of the package is imported. ■ Temporary location where the package is to be extracted before importing. 3. Specify the following when prompted: ■ Oracle Identity Manager administrator username ■ Oracle Identity Manager administrator password ■ Server URL: t3:localhost:PORT_NUMBER 4. Verify the import list that is displayed. 5. When prompted for confirmation, enter YES. 6. Verify the import. All the items in the package are imported to the application. Check if the import utility creates the entries corresponding to all the package contents in the database tables if you have access to the schema. Otherwise, check the utility output log in the application to verify if all contents have been successfully imported.

5.4.3 Data Migration for Supported Entities

This section describes the migration of the following entities: ■ Custom Resource Bundle ■ Plug-ins

5.4.3.1 Custom Resource Bundle

Oracle Identity Manager stores localized versions of text strings that appear in the user interface in resource bundles. In addition to the default resource bundles, the custom resource bundles, which are stored in Oracle Identity Manager database, can be imported and exported by using the horizontal migration utility. The default packaged resource bundles are available in the following property files: ■ oim.earxlWebApp.warWEB-INFclassesxlRichClient_.properties ■ Agent_.properties for each feature in the deployment You can customize the default packaged resource bundles to create custom resource bundles.

5.4.3.2 Plug-ins

Plug-ins are stored in Oracle Identity Manager database. The horizontal migration utility migrates the binaries from plug-in database store of one deployment to another. Importing and Exporting Data Using the Deployment Manager 5-13

5.4.4 Horizontal Migration Report

After the horizontal migration utility is run, a report is generated that contains the following information: ■ All the entities migrated by using this utility ■ Status of overall export and import of metadata ■ Errors that occurred during the import of metadata The following is a sample report: Plugins : Failed to process element Plugin1. Exception details are java.io.FileNotFoundException: C:\Plugin1.zip The system cannot find the path specified at java.io.FileInputStream.openNative Methodat java.io.FileInputStream.initUnknown Sourceat java.io.FileReader.initUnknown Sourceat file.mainfile.java:13

5.5 Best Practices Related to Using the Deployment Manager

The following are some of the suggested practices and pitfalls to avoid while by using Deployment Manager: ■ Export System Objects Only When Necessary ■ Export Related Groups of Objects ■ Group Definition Data and Operational Data Separately ■ Use Logical Naming Conventions for Versions of a Form ■ Export Root to Preserve a Complete Organizational Hierarchy ■ Provide Clear Export Descriptions ■ Check All Warnings Before Importing ■ Check Dependencies Before Exporting Data ■ Match Scheduled Task Parameters ■ Compile Adapters and Enable Scheduled Tasks ■ Export Entity Adapters Separately ■ Check Permissions for Roles ■ Back Up the Database ■ Import Data When the System Is Quiet ■ Update the SDK Table ■ Remove Data Object Fields Before Importing Event Handlers as Dependencies

5.5.1 Export System Objects Only When Necessary

You should export or import system objects, for example, Request, Xellerate User, and System Administrator, only when it is absolutely necessary. Exporting system objects See Also: Working with the Plug-in Framework in the Oracle Fusion Middleware Developers Guide for Oracle Identity Manager for information about defining and using plug-ins