立即与支持人员聊天
与支持团队交流

Identity Manager 9.2.1 - 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
Overview of the One Identity Manager schema Table types and default columns in the One Identity Manager data model Notes on editing table definitions and column definitions Table definitions Column definitions Table relations Dynamic foreign key Supporting file groups
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
Mapping processes in One Identity Manager Setting up Job servers
The One Identity Manager Service functionality Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager
Visual Basic .NET scripts usage Notes on message output Notes on using date values Tips for using PowerShell scripts 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 scripts in the 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 running scripts Editing and testing script code with the System Debugger Extended debugging in the Object Browser
One Identity Manager query language Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration One Identity Manager as SCIM 2.0 service provider Processing DBQueue tasks One Identity Manager Service configuration files

Changing the maximum number of instances for process tasks and process components

The One Identity Manager Service handles parallelization of processes by using the maximum number of instances allowed for process tasks and process components.

To change the maximum number of instances of a process task

  1. In the Designer, select the Process Orchestration > Process components category.

  2. In the Process Component Editor, select the process component.

  3. Select a process task and in the edit view on the Properties tab, adjust the Max instances value to the maximum number instances.

    Permitted values are:

    • -1: All instances of this process task are processed sequentially. Other process task instances of the same process component are not run simultaneously.

    • 0: The maximum number of instances given for the process component is used.

    • 1 or greater: The exact number of instances of a process task, which are processed simultaneously.

  4. Save the changes.

To change the maximum number of instances of a process component

  1. In the Designer, select the Process Orchestration > Process components category.

  2. In the Process Component Editor, select a process component and in the edit view on the Properties tab, adjust the Max instances value to the maximum number instances.

    Permitted values are:

    • -1: All instances of this process component are processed sequentially.

      It must be ensured that these components are run exclusively on one Job server, which means no other queue can exist to process these components.

    • 0: All instances of this process component can be processed simultaneously.

    • 1 or greater: The exact number of instances of a process component, which are processed simultaneously.

    NOTE: The value is only used if the maximum number of instances of a process task is set to 0. Otherwise, the value applies that is set for the process task.

  3. Save the changes.

Related topics

Properties of process components, process tasks, and parameter templates

Table 88: Process component properties

Property

Meaning

Display name

Name of component for displaying.

Component class

Component class.

Assembly name

Name of the component.

Description

Description of component functionality.

Remarks

Additional remarks about the process component.

Max. instances

This value specifies the maximum number of instances in which this process component is allowed to run in a queue in the Job server.

Permitted values are:

  • -1: All instances of this process component are processed sequentially.

    It must be ensured that these components are run exclusively on one Job server, which means no other queue can exist to process these components.

  • 0: All instances of this process component can be processed simultaneously.

  • 1 or greater: The exact number of instances of a process component, which are processed simultaneously.

NOTE: The value is only used if the maximum number of instances of a process task is set to 0. Otherwise, the value applies that is set for the process task.

Configuration

Definition of possible additional options for the component in XML syntax.

Table 89: Process task properties
Property Meaning

Name

Name of the process task.

Operating system class

Specifies the operating system on which the process task can be run. The Win32, Linux and ALL values are permitted, where the ALL value specifies that this process task is used on any operating system.

Exe type

Exe type for the process task.

Permitted values are:

  • Internal: Runs internally in the One Identity Manager Service.

  • External: Runs externally as its own process.

  • External32: Runs externally as its own 32-bit process.

Description

Description of the process task.

Max. instances

This value specifies the maximum number of instances that can be run by One Identity Manager Service in parallel per process task.

Permitted values are:

  • -1: All instances of this process task are processed sequentially. Other process task instances of the same process component are not run simultaneously.

  • 0: The maximum number of instances given for the process component is used.

  • 1 or greater: The exact number of instances of a process task, which are processed simultaneously.

Last step in the partial process tree

Specifies whether a process task is principally marks the end of a partial process tree.

Component

Process component to which the process task belongs.

Direct database connection required

Specifies whether a process task requires a direct database connection.

NOTE: Processes with process tasks that have the Direct database connection required option enabled must not be carried out by a Job server with the No direct database connection option enabled. Otherwise an error occurs.

Exclusive per object

Specifies whether the process task is run exclusively per object. If this option is enabled in a process task, only one process step with this process task can be run for a specific object. There is no parallel processing.

DBQueue does not wait

Specifies whether or not to wait until the process step has been processed before continuing to process DBQueue Processor tasks. It is only necessary to wait for process steps if a process step could change data that is relevant to the DBQueue Processor tasks.

Table 90: Parameter template properties
Property Meaning

Name

Name of the parameter.

Value template

Default template for finding values. When a parameter is added to a process step, the value template is taken from the parameter template. Define value templates in VB.Net syntax.

Value template (example)

Example of the value template.

Description

Description of the parameter.

Type

The IN, OUT and INOUT values are permitted.

Optional

Labels the parameter as a mandatory or optional parameter.

Hidden

Specifies whether the parameter is shown in the One Identity Manager Service log file and in the Job Queue Info program. Values for hidden parameters are shown as <HIDDEN>.

NOTE: The following users can view the hidden parameters in the Job Queue Info.

  • Administrative users

  • Users with the JobQueue_ShowHiddenParameters program function

Encrypted

Specifies whether the parameter is encrypted when it is passed.

Contains encrypted components

Specifies whether encrypted sequences are contained in this value.

Process task

Process task to which the parameter belongs.

Related topics

Setting up Job servers

The One Identity Manager Service handles defined processes. To run the processes, the One Identity Manager Service has to be installed on the One Identity Manager network server. For more information, see the One Identity Manager Installation Guide.

Each Job server within the network must have a unique queue identifier. The process steps are requested by the Job queue using exactly this queue name:

  • A Job server must be known in the One Identity Manager database for each queue.

  • Enter this queue name in the One Identity Manager Service configuration file.

Setting up a Job server requires the following steps:

  • Create an entry for the Job server in the One Identity Manager database.

  • Specify the machine roles and server functions for the Job server.

    Installation packages to be installed on the Job server are found, depending on the selected machine roles. The server function defines the functionality of a server in One Identity Manager. One Identity Manager processes are handled with respect to the server function.

  • Install the One Identity Manager Service.

  • Configure the One Identity Manager Service.

  • Start the One Identity Manager Service.

There are several methods for setting up a Job server:

  • For the initial schema installation with the Configuration Wizard, you already set up a Job server with the SQL processing server and Update server server functions. Use the Configuration Wizard to configure the service and install it on a server. For more information, see the One Identity Manager Installation Guide.

  • To configure further Job servers, use the Server Installer program.

    Using the Server Installer, you create the Job server with its machine roles and server functions in the database. Use the Server Installer to configure the service and install it on a server. For more information, see the One Identity Manager Installation Guide.

  • You can create Job servers in the Designer.

    Use the Designer, to create a Job server with the machine roles and server functions, configure the service on the server and install the service remotely.

  • Alternatively, you can use the installation wizard to install the service components on the server and then configure the service using the Job Service Configuration program.

  • If the Common | Jobservice | AutoCreateServerFromQueues configuration parameter is enabled, in response to queries from the One Identity Manager Service for unknown queues, new Job servers are created in the database. Information about machine roles and server functions is transferred to the database.

Detailed information about this topic

Editing the Job server

To edit a Job server

  1. In the Designer, select the Base Data > Installation > Job server category.

  2. Enter a new Job server using the Job servers > New menu item.

    - OR -

    Select the Job server to be edited in the Job server overview.

  3. Edit the Job server's main data.

  4. Select the View > Server functions menu item and specify the server functionality.

  5. Select the View > Machine roles menu item and assign roles to the server.

    The machine roles expected by a server function, are already assigned.

Detailed information about this topic
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级