| Oracle® Identity Manager Administrative and User Console Guide Release 9.0.3 Part Number B32450-01 |
|
|
View PDF |
| Oracle® Identity Manager Administrative and User Console Guide Release 9.0.3 Part Number B32450-01 |
|
|
View PDF |
The Deployment Manager is a tool for exporting and importing Oracle Identity Manager configurations. The Deployment Manager enables you to export the objects that make up your Oracle Identity Manager configuration. You use the Deployment Manager to exchange Oracle Identity Manager items between environments. 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.
Important:
To use Deployment Manager, JRE 1.4.2 must be installed on any computer that is running the Oracle Identity Manager Administrative and User Console.You can save some or all of the objects in your configuration. This lets you develop and test your configurations in a test environment, then import the finished items into your production environment. You can import and export an object and all of its dependent and related objects at the same time, or you can export parts of it.
This chapter covers the following topics:
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 enables you to build up your export file. Add objects by type, one type at a time, for example, user groups, 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. Once you add objects of one type, you can go back and add other objects to your XML files. When you have all the desired objects, the Deployment Manager saves them all at once into a single XML file.
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) the Deployment Manager will consider them as dependencies.
If the user defined fields contain no values (the fields are blank), the Deployment Manager will not considered them as dependencies.
To export a deployment:
In the Oracle Identity Manager Administrative and User Console menu, click Deployment Management, then click Export.
The Deployment Manager opens and the Export Wizard's Search Objects screen appears.
On the Search Objects, select an object type from the menu, and enter search criteria.
If you leave the criteria field blank, an asterisk automatically appears to find all the objects of the selected type
Click Search to find objects of the selected type.
To select an object, click its checkbox.
Click Select Children.
The Select Children screen appears. The Select Children screen displays the selected objects and any of their children.
Select the children to export.
To select or remove an item, click its checkbox.
Click Back to go to the Search Objects screen.
Click Select Dependencies.
The Select Dependencies screen appears. The Select Dependencies screen displays any objects required by the selected objects.
Select which dependencies to export.
To select or remove an item, click its checkbox.
Click Back to go to the Select Children screen.
Click Confirmation.
The Confirmation screen appears.
Make sure all desired items are selected, then click Add for Export.
After you click Add for Export, you can still add more items to this export file.
Click Back to go to the Search Objects screen.
The Add More screen appears.
Use the wizard to add more items, or finish and exit the wizard.
Select the desired radio button and click OK.
If you selected Add more, repeat Steps 2 through 7. Otherwise, the Export screen appears.
The Export screen displays your current selections for export. Your selections have icons next to them that indicate what types of objects are selected. The Summary information pane shows the objects you are exporting. In the Unselected Dependencies pane, any dependencies or children of the selected objects that you chose not to export are listed.
Make any adjustments to your export file as follows:
Click Reset to clear the form.
Click Legend to see icon definitions.
Click Add Object to restart the wizard and add more items to your export file.
To remove an object from the Current Selections list:
Right-click the object to remove and select Remove from the shortcut menu. If the object has child objects, to remove them all at the same time select Remove including children from the shortcut menu.
Click Remove to confirm. If the object is a child or dependency of a selected item, it is added to the Unselected Children or Unselected Dependencies list
To add an object back to the Current Selections list from the Unselected Children or Unselected Dependencies list, right-click the object and select Add. Click to confirm.
Click Export.
The Add Description dialog box appears.
Enter a description for the file.
This description is displayed when the file is imported.
Click Export.
The Save As dialog box appears.
Enter a file name.
You can browse to find a location.
Click Save.
The Export Success dialog appears.
Click Close.
You can import objects that were saved in an XML file using the Deployment Manager into your Oracle Identity Manager system. You can import all or part of the XML file, and you can import multiple XML files at once. The Deployment Manager checks to make sure the dependencies for any objects you are importing are available, either in the import or in your system. During an import, you can substitute an object you are importing for one in your system. For example, you can substitute a group specified in the XML file for a group in your system.
This section includes the following subsections:
Note:
Before importing data that contains references to menu items, you must first create the menu items in the target system.Under normal circumstances, you would import a Scheduled Task into your Oracle Identity Manager environment and later change the values to meet your production requirements. However, if you import the same Scheduled Task a second time into the same Oracle Identity Manager server, the Deployment Manager does not overwrite the attribute values in the database. Instead the Deployment Manager compares the attribute value of the re-imported XML file to any corresponding attribute values in the database.
The following table summarizes the Deployment Manager's behavior on Scheduled Task re-import.
| Does the Scheduled Task have attribute values in the XML file being imported? | Are there any corresponding attribute values in the database? | Deployment Manager Action |
|---|---|---|
| Yes | No | Store attribute values in the database |
| No | Yes | Delete existing attribute values in the database |
| Yes | Yes (Newer attribute values indicated by timestamp) | No change in the database |
| Yes (Newer attribute values indicated by timestamp) | Yes | Update the database with the newest attribute values |
In the Administrative and User Console menu, click Deployment Management, then click Import.
Choose a file.
The Import dialog box appears.
Click Open.
The File Preview screen appears.
Click Add File.
The Substitutions screen appears
To substitute a name, click in the New Name field adjacent to the item you want to replace, and enter the desired name.
You can only substitute items that exist in the target system.
Click Next.
If you are exporting an IT Resource Instance, then the Provide IT Resource Instance Data screen is displayed.
Otherwise you are redirected to the Confirmation screen.
Modify the values in the current resource instance and click Next, or click Skip to skip the current resource instance, or click <<New Instance>> to create a new resource instance.
The Confirmation screen appears.
Check that the information is correct.
To go back and make changes, click Back, or click View Selections.
The Deployment Manager Import screen displays your current selections.
The Import screen also displays icons next to your current selections. The icons indicate what types of objects are selected. The icons on the right indicate the status of the icons. The file names of any selected files, summary information about the objects you are importing, and substitution information is displayed on the left side of the screen. On the right, the Objects Removed from Import list displays any objects in the XML file that will not be imported.
Make any desired adjustments:
Click Reset to clear the form.
Click Legend to see icon definitions.
To remove an object from the Current Selections list, right-click the object to remove and select Remove from the shortcut menu, then click Remove to confirm.
If the object has child objects, to remove them all at the same time, select Remove including children from the shortcut menu.The item is added to the Objects Removed From Import list.
To add an item back to the Current Selections list, right-click it and select Add.
If the object has child objects, to add them all at the same time, select Add including children from the shortcut menu.
To make substitution, click Add Substitutions.
To add objects from another XML file, click Add File and repeat Steps 2. through 7.
Click Show Information to see information about your imported information.
The Information screen appears and shows basic information about your import.
To see more information, click the Show Info Level Messages checkbox, then click Show Messages. Click Close to close the Information screen.
To import the current selections, click Import.
A confirmation dialog box appears.
Click Import.
The import success dialog appears.
Click OK.
The objects are added to your Oracle Identity Manager system.
The following are some of the suggested practices and pitfalls to avoid while using Deployment Manager.
See also:
For details on best practices related to using the Deployment Manager, refer to the Oracle Identity Manager Best Practices Guide.Understand the limitations of the Deployment Manager to effectively use all its functionality.
Do not export system objects.
Group definition data and operation data separately.
Use logical names for form versions.
Enter meaningful descriptions when exporting.
Check all warnings before performing any imports
Check the required dependencies in the target system before performing any exports.
Understand how scheduled task attributes are affected by imports.
Compile adapters and enable scheduled tasks.
Export entity adapters separately with only essential mappings, and then manually create the required mappings.
Back up the database before importing it into the production environment.
Ensure that the correct version of the form is active during a UDF or form import
Perform imports during periods of low activity in the system.
