Process components and their process tasks form a framework that all process steps can be based on. The tables Jobcomponent, JobTask, and Jobparameter define the complete range of One Identity Manager’s own process components and process task with the associated parameters.
Process tasks are used to carry out single basic jobs at system level, for example, adding directories. A process component consists of one or more process tasks and its parameters.
When a process is created, the parameter templates for the process task are copied and entered in the process step. This means that every process step that uses this process task can pass other parameter values. The original is not altered.
NOTE:The information available for the process components and their process tasks is added when the schema is installed and cannot be edited.
To obtain a complete overview of process components and their process tasks and parameters
To display individual process components and their process tasks and parameters
The following table contains short descriptions of the process components.
NOTE: Additional process components may be available depending on which modules are installed.
Table 87: Short descriptions of process components
AutoUpdateComponent |
This process component maps the One Identity Manager Service built-in-tasks. |
CommandComponent |
This process component runs any command. |
DelayComponent |
This process component controls the start time of the following process steps. |
FileComponent |
This process component creates, deletes, copies, and modifies file and directories and also their access permissions.
The RSync program is a prerequisite for using the process component on Linux operating systems.
Under Windows, some of the process components' process functions required the program XCalcs to edit permissions. You can find this in the your server installation resource kit. |
FtpComponent |
This process component can transfer file by FTP. |
HandleObjectComponent |
This process component runs default and custom events for database objects. Each assigned default process is generated as in the front-ends. The component also makes it possible to initiate so called CustomEvents for triggering object related generation of a special process. |
LogComponent |
This process component is used to log messages, for example, in the result log. |
MailComponent |
This process component can send emails. |
PowerShellComponent |
This process is used for calling Windows PowerShell. Version 2.0 of Windows PowerShell must be installed. |
PowershellComponentNet4 |
This process is used for calling a .NET 4 Windows PowerShell. A version of Windows PowerShell later than 2.0 must be installed. |
ProjectorComponent |
This process component contains tasks for synchronizing and provisioning data with the One Identity Manager database. |
ReportComponent |
This process component can create reports and export them in various file formats. |
ScriptComponent |
This process component run the scripts from the assemblies. |
SFtpComponent |
This process component can transfer files by SFTP. |
SQLComponent |
This process component runs SQL queries and can be used to determine the number of data records and the existence of data records. |
ZipComponent |
This process component creates or unpacks ZIP files. |
Detailed information about this topic
The exe type of a process task defines whether processing takes place within the One Identity Manager Service or in an external process.
To display process task exe types of a process component
-
In the Designer, select the Process Orchestration > Process components > <process component> category.
On the process component's overview form, you can see all the process tasks with their exe types.
To change the exe type 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 exe type value.
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.
-
Save the changes.
Related topics
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