Identity Manager r12.0 CR6 Bulk Loader Enhancement.

Document ID : KB000009460
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

The following document outlines enhancements provided in r12.0 Cumulative Release 6 (r12 CR6) the Bulk Loader for Identity Manager. Specifically, the ability to use Excel spreadsheets as feeder files and additional configuration capability.

Instructions:

README of Bulk Loader Feature Enhancement in CR6 release

The following features have been introduced to the Bulk Loader task in IM r12 CR6 release.

  1. Support of Microsoft Excel feeder file format.

    The support of feeder file in the Microsoft Excel format is added to the Bulk Loader's default CSV parser. The supported file extension has also been expanded from ".csv" only to both ".csv" and ".xls".

    A sample Excel feeder file may look like the following.

    Figure 1

  2. Support of Bulk Loader task configuration items.
    The following configuration items have been added to the Bulk Loader's search configuration screen.

    • Feeder File Format field

      Figure 2

      This field specifies whether the Bulk Loader is allowed to process feeder files that are only Excel format or either Excel or CSV formats.

    • Primary Object field

      Figure 3

      This field specifies the related IM object of the Bulk Loader's feeder files.
      The support IM object types are User, Group and Organization. When this field is set, its value will be used as the default value in the "What is the primary Object?" field in the Bulk Loader's Loader Actions Mapping screen as follows

      Figure 4

    • Unique Identification field

      Figure 5

      This field specifies which column field of the feeder file will be used as the unique identifier of the feeder object. When it is set, its value will be used to set the "What field will be used to uniquely identity the object?" field in the Bulk Loader "Loader Records Details" screen as follows.

      Figure 6

    • Action field

      Figure 7

      This field specifies which column field of the feeder file will be used to specify the action to be performed on the feeder object. When it is set, its value will be used to set the "What field represents the action to perform on the object?" field in the Bulk Loader "Loader Records Details" screen as follows.

      Figure 8  

    • Task Mappings

      Figure 9

      This section allows the users to map the feeder action values to the Identity Manager tasks. The mappings specified in this section will set the default values in the Bulk Loader's Loader Actions Mapping screen as follows.


      Figure 10

  3. Security scoping.

    Security scoping is enforced on the tasks the current administrator is entitled to. Only tasks that the current, logged in, administrator has access to, will be listed in the Identity Manager Tasks dropdown lists as shown below. This means that the available tasks for mapping will be dictated at the time the configuration is specified and will be limited by the scope of the administrator performing the configuration.


    Figure 11

    Figure 12

  4. Support of Bulk Loader feeder file custom attribute mapping from the Bulk Loader's search configuration screen.

    Figure 13

    This section allows the users to map custom attributes to the Identity Manager attributes which include physical names, well-known names and logical attribute names. Thus users can create custom names in the column headers of the feeder files, and the Bulk Loader will map the custom fields to IM attributes based on the mappings specified here during task execution. A sample feeder input file that uses custom attributes may look like the following based on the custom mappings specified above.

    Figure 14

  5. Support of Logical attributes

    In the previous versions of Bulk Loader, Logical Attributes are not fully supported in Bulk Loader tasks. Logical attributes support has been added for all feeder tasks. Users may supply values for the managed objects' logical attributes when using Bulk Loader to execute IM tasks.

  6. Figure 15