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
-
In the Designer, select the Process Orchestration > Process components category.
-
In the Process Component Editor, select the process component.
-
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.
-
Save the changes.
To change the maximum number of instances of a process component
-
In the Designer, select the Process Orchestration > Process components category.
-
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.
-
Save the changes.
Related topics
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:
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