Deprecated Features

This chapter describes features in DirX Identity that are obsolete and will not be supported in future DirX Identity releases.

Deprecated Export Features

The following export features from previous DirX Identity versions are obsolete because the collection and transport mechanism is more powerful and fully customizable.These features will be removed in one of the next versions.

The described import features are still valid.

Exporting Parts of the Configuration Database

You can export parts of the configuration database.These options exist:

  • Logical object tree - The logical DirX Identity object structure with all its links is evaluated and all detected objects are written to an LDIF file.You can write the file to any location, and you can import these files into the same or another configuration database.Use the Export Data function in the expert view to perform this operation.This function is useful when exporting a set of objects only a few times.

  • Structural object tree - Allows to export an object and all of its sub objects in the LDAP tree. No links are followed in this case. Use the Export Subtree function in the Expert View to perform this operation. This function is useful when exporting a set of object only a few times.

Exports can be done on any object which then acts as a starting point for the data extraction. Possible objects are scenarios, workflows and jobs including all of their sub-objects defined by links or in the LDAP tree structure. For more information about the Export context menu selections, see the section "Using the Context Menu".

You can use these features for backups or snapshots, which help to reset to a specific state of your configuration database. You can also use them to exchange logical or structural object trees, for example from a test environment to a productive environment. In the case of logical object trees a ToDo file is written which helps to identify parts of the object tree which may not fit. Possible objects in this category are C++-based Servers, services and messaging objects.

To perform an export/import sequence:

  1. Select the object you’d like to export in the expert view. Select Export Data or Export Subtree from the context menu. Alternatively you can create an object collection and export the related objects based on this collection.

  2. A file selection box opens which allows you to define the file name and the location of the file.

  3. To import such an LDIF file, select the root node of the Connectivity configuration tree and select Import Data from the context menu.

    Do not import data from previous or later versions of DirX Identity. Important attributes could be missing or are contained which will results in an error during the import operation or in strange behavior of the DirX Identity Manager after the import operation. Instead, import such workflows into your database, perform the upgrade installation including a migration.

  4. The file dialog opens again, and you can select the required file. Click Open to start the import procedure.

Be aware that an import of this information from the LDIF file only overwrites existing objects and attributes. New attributes or objects you created between the export and the import are not touched. Thus you perform a merge.

Import Data Features

In addition to former versions, now referenced Agent object are also exported during an Export Data procedure and therefore are transferred via Import Data to your target system. This is especially useful if you have created your own agents.

Additionally, you can define a mapping of dxmService-DN / dxmMetahubSyncServer-DN references. Assume we have a test and a production environment. Each environment has specific Services and MetahubSyncServer entries (because they run on different machines). You have developed a new workflow in your test environment, and you export it via Export Data to an LDIF file. Now you import it via Import Data to your production environment. As all dxmService-DN / dxmMetahubSyncServer-DN’s reference objects of the test environment, you have to correct all these references by hand to the appropriate objects.

To avoid this task during every import two mechanism are available. DirX Identity tries to find an object with the same display name. This works in all cases where a display name is available. Alternatively you can define a DN-mapping.

Use the file referenceDNmapping.tcl in install_path/Tools/Import. Here you can define an Tcl array indexed by the dn that contains the displayname of the corresponding object. The file contains already some sample entries. It is assumed, that the object with the given dn has the given displayname and that the object with this displayname in the target (production) environment is identical with the object in the source (test) environment.

For more information about the Import context menu selections, see the section "Using the Context Menu".

Integrating Workflows into a Scenario

Please note that workflows which are imported from one configuration database to another one do not automatically appear in a scenario. There are two ways to solve this issue:

  • Export and import the complete scenario. This includes all workflows contained in that scenario.

  • Insert the workflow into one of your scenarios. You can perform this step:

    • in the scenario object in the Expert View by adding workflows to a workflow line (be sure to take the right one)

    • with the function Assign from the context menu of a workflow line in the Global View.

Exporting the Entire Configuration Database

You can export the entire configuration database tree to a flat LDIF file (Export Configuration), and then re-import it with Import Data or Replace Configuration. All objects of the configuration database are exported.

You can use this function for backups or snapshots, which help to reset to a specific state of your configuration database.

Please be aware that an import of this information from the LDIF file with Import Data does only overwrite existing objects and attributes. New attributes or objects you created between the export and the import are not touched. Thus, you perform a merge. To replace the whole configuration tree you need to use Replace Configuration.

Do not import data from previous versions of DirX Identity. Important attributes could be missing which will results in strange behavior of the DirX Identity Manager.