Modifying System Properties Deleting System Properties

Administering System Properties 4-25

4.2.5 Deleting System Properties

To delete a system property:

1. Click the System Management tab and then click System Configuration.

2. On the left pane, search for the system property that you want to delete.

3. In the Property Name column of the search results table, select the system

property that you want to delete.

4. From the Actions menu, select Delete. A message is displayed asking for

confirmation. Click OK. 5. A message is displayed confirming that the system property has been deleted. Click OK. Note: You can delete a system property only if the data level of that system property is set to either 0 or 3. While deleting a system property, a message is displayed if the data level associated with the system property is not appropriate. For a description of the data levels, see Table 4–4, Data Levels Associated with a System Property . 4-26 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager 5 Importing and Exporting Data Using the Deployment Manager 5-1 5 Importing and Exporting Data Using the Deployment Manager The Deployment Manager is a tool for exporting and importing Oracle Identity Manager configurations. The Deployment Manager lets you export the objects that constitute the Oracle Identity Manager configuration. Usually, you use the Deployment Manager to migrate a configuration from one deployment to another, for example, from a test to a production deployment, or to create a backup of your system. You can save some or all of the objects in your configuration. This lets you develop and test your configurations in a test environment, and then import the tested objects into your production environment. You can export and import an object and all of its dependent and related objects at the same time. Alternatively, you can export and import each object individually. The Deployment Manager allows you to retrieve configuration information from the source system, store the information in an XML file, and then import the information from the XML file to the target system. In Oracle Identity Manager 11g Release 1 11.1.1, the Deployment Manager allows you to import data from the Oracle Identity Manager database, Meta Data Store MDS repository, or API repository. As a result, you can import all types of objects from these repositories, such as system properties, jobs, and scheduled tasks, which are not in the same repository. For example, you can import the scheduled tasks that are in the MDS repository instead of the database. An object exported from one type of repository is imported to the same type of repository. For example, if a scheduled task is exported from the MDS repository, then the scheduled task is imported to the same repository, which is MDS, in the target system. This chapter includes the following topics: ■ Features of the Deployment Manager ■ Exporting Deployments ■ Importing Deployments ■ Horizontal Migration of Entities ■ Best Practices Related to Using the Deployment Manager ■ Best Practices for Using the Horizontal Migration Utility Important: To use Deployment Manager, JRE 1.4.2 or a higher version must be installed on any computer that is running the Oracle Identity Manager Administrative and User Console. 5-2 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager ■ Troubleshooting

5.1 Features of the Deployment Manager

The Deployment Manager helps you to migrate Oracle Identity Manager deployments from one server environment to another, such as from a testing environment to a staging environment, or from a staging environment to a production environment. The Deployment Manager enables you to: ■ Update individual components of a deployment in different test environments ■ Identify objects associated with components to be exported, so that those resources can be included ■ Provide information about exported files ■ Add comments The Deployment Manager handles the following types of information: ■ Roles ■ Organizations ■ Access policies ■ Attestation processes ■ Authorization policies ■ User metadata ■ Roles and organization metadata ■ Scheduled tasks ■ Scheduled jobs ■ IT resources ■ Resource objects ■ Lookup definitions ■ Process forms ■ Provisioning workflows and process task adapters ■ Data object definitions ■ Rules ■ Notification templates ■ Generic Technology Connector GTC providers ■ Error codes ■ System properties ■ E-mail definitions ■ Event Handlers ■ Password policies ■ Generic Technology Connectors ■ IT resource definition Importing and Exporting Data Using the Deployment Manager 5-3 ■ Request templates ■ Request datasets ■ Approval policies ■ Event handlers ■ Password policies ■ Prepopulation adapters ■ Process definitions The following are limitations of the Deployment Manager: ■ Merge Utility : The Deployment Manager is not a merge utility. It cannot handle modifications done in both production and test environments. It replaces the object in the target system with that in the XML file. ■ Version Control Utility : The Deployment Manager does not track versions of imported files, and does not provide rollback functionality. You can only use it as a means to move data between environments. ■ Code Moving : The Deployment Manager does not move JAR files in the JavaTasks directory or other locations. ■ Custom Labels Move : The Deployment Manager does not move labels defined in the customResources.properties file or the property files in the connectorResources directory. You must do this manually.

5.2 Exporting Deployments

You can export objects from your Oracle Identity Manager system and save them in an XML file. The Deployment Manager has an Export Wizard that lets you create your export file. Add objects by type, one type at a time, for example, roles, then forms, then processes, and so on. If you select an object that has child objects or dependencies, you have the option to add them or not. After adding objects of one type, you can go back and add other objects to your XML files. When you have all the objects you want, the Deployment Manager saves them all at once in a single XML file. To export a deployment: 1. Login to Oracle Identity Manager Administration. Note: When user-defined fields are associated with a specific resource object, during the export process one of the following events can occur: ■ If the user-defined fields contain values entered information, then the Deployment Manager will consider them to be dependencies. ■ If the user-defined fields contain no values the fields are blank, then the Deployment Manager will not consider them to be dependencies.