Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Identity Manager 8.1.4 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Customizing the One Identity Manager base configuration One Identity Manager schema basics Editing the user interface
Object definitions for the user interface User interface navigation Forms for the user interface Statistics in One Identity Manager Extending the Launchpad Task definitions for the user interface Applications for configuring the user interface Icons and images for configuring the user interface Using predefined database queries
Localization in One Identity Manager Process orchestration in One Identity Manager
Setting up Job servers Configuring the One Identity Manager Service Handling processes in One Identity Manager
Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager
Using scripts Notes on message output Notes on using date values Using dollar ($) notation Using base objects Calling functions Pre-scripts for use in processes and process steps Using session services Using #LD-notation Script library Support for processing of scripts in Script Editor Creating and editing scripts in the Script Editor Copying scripts in the Script Editor Testing scripts in the Script Editor Testing script compilation in the Script Editor Overriding scripts Permissions for executing scripts Editing and testing script code with the System Debugger Extended debugging in the Object Browser
Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration SOAP Web Service One Identity Manager as SPML provisioning service provider Processing DBQueue tasks One Identity Manager Service configuration files

Editing process information for process steps

To edit process information for a process

  1. In the Designer, select the process in the Process Orchestration category.

  2. Start the Process Editor with the Edit process task.

  3. Click on the element for the process step in the process document.

  4. In the Process step properties view on the General tab, edit the following information.

    • Process information: Select how the process information should be logged.

      Permitted values are:

      • None: The process information is not logged.

      • Full process tracking: The process information is logged and displayed in the Manager.

      • Web Portal tracking: The process information is logged and displayed in the Manager and the Web Portal.

  5. In the Process step properties view on the Process tracking tab, enter the following information.

    • Depth of detail: Select the level of detail of the process information. You can choose from: basic information, extended information and full information.

      You use depth of detail to control how process information is displayed in the Manager's process view. Depending on the Manager's program settings, differing levels of detail are offered to the user on views of the process information. For more detailed information, see the One Identity Manager Operational Guide.

    • Process information: Enter the value template for the process information as VB.NET term. Use #LD notation for language-dependent definition of process information.

Related topics

Editing process information for events

IMPORTANT: At least one event process must have process tracking enabled in order to generate process information for events.

To edit process information for events

  1. In the Designer, select the process in the Process Orchestration category.

  2. Start the Process Editor with the Edit process task.

  3. Click on the element for the process in the process document.

  4. In the Events view, select the event and click .

  5. Enter the following information.

    • Event process information: Value template for the process information as VB.NET term. Use #LD notation for language-dependent definition of process information.

      If there no template is available, the information is evaluated as follows:

      <table> - <event> - <object display name>

If several processes point to one event, the event with a process information template is found that has the lowest generating order specified in its process configuration. This template is evaluated and shown in the process view in the Manager. For more detailed information, see the One Identity Manager Operational Guide.

Related topics

Recording messages in the process history

In the process history (JobHistory table), the processes being handled are logged. You can analyze the process history in Job Queue Info. For more detailed information, see the One Identity Manager Process Monitoring and Troubleshooting Guide.

To log messages to the process history

  • In the Designer, check if the Common | ProcessState configuration parameter is set. If not, set the configuration parameter.

  • In the Designer, check if the Common | ProcessState | ProgressView configuration parameter is set. If not, set the configuration parameter. Select the scope of logging through the configuration parameter option.

    Table 125: Permitted values of the “Common | ProcessState | JobHistory” configuration parameter
    Value Meaning
    NO No messages are logged in the process history.
    ALL All process steps being handled are logged in the process history.
    ERROR On failed process steps are logged in the process history.

    ERRORorSELECTED

    Failed process steps and process steps labeled with the Process history option are logged in the process history.

    SELECTED

    Only process steps labeled with the Process history option are logged in the process history.

  • Use the Common | ProcessState | JobHistory | TrimLongParameters configuration parameter to specify the length of process parameter values that are logged in the process history.

Log entries in the process history are exported from the One Identity Manager database at regular intervals. One Identity Manager provides various methods to do this. For more information, see Archiving and deleting records.

Process tracking for DBQueue Processor operations

In order to track inherited calculations as a result of changes to the system, the GenProcID is always passed to the DBQueue Processor operation. There may only be one entry in the DBQueue for each operation and object in case of follow-on operations. To map such processes, a new GenProcID is issued and used in subsequent processes. The conflicting processes and their GenProcID’s are saved in the DialogProcessSubstitute table.

When a new GenProcID is created for conflicting processes, the following rules apply:

  • Several of the same DBQueue Processor operations on one object are merged into one process (one GenProcID). This uses existing substitute processes if the number is identical to the predecessor (with respect to the root processes).

  • If further conflicts occur in the sequence, the GenProcIDs that have already been replaced are reset to the original and a new substitute is created.

  • A substitute is only valid for one set of original processes.

The QBM | DBQueue | GenProcIDReplaceLimit configuration parameter defines the limit for process substitutions. The maximum number of conflicting processes are mapped in the DialogProcessSubstitute table. If necessary, you can set the configuration parameter in the Designer and change the value.

Related topics
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation