Setting up Job servers in Designer
The One Identity Manager Service handles defined processes. To execute the processes, the One Identity Manager Service has to be installed on the One Identity Manager network server. For more detailed information, see the One Identity Manager Installation Guide.
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 depending on the server function.
-
Install the One Identity Manager Service.
-
Configure the One Identity Manager Service.
-
Start the One Identity Manager Service.
Each One Identity Manager Service within the network must have a unique queue identifier. The process steps are requested by the Job queue using exactly this queue name.
-
Enter this queue name in the One Identity Manager Service configuration file.
-
A Job server must be known in the One Identity Manager database for each queue.
You can set up Job servers in different ways. You can carryout the necessary steps in the Designer using the Job Server Editor. Start the Job Server Editor in Base data | Installation | Job server using the task Edit Job server in Designer.
Detailed information about this topic
- Editing a Job server
- Machine roles and server functions
- Job server statistic information
- Connection data for process generation
- Installing the One Identity Manager Service on the Job server
- Customizing the One Identity Manager Service configuration for a Job server
- Configuring the One Identity Manager Service
Editing a Job server
To edit a Job server
- Select the Base Data | Installation | Job server category in Designer.
- Enter a new Job server using Job servers | New.
- OR -
Select the Job server to be edited in the Job server overview.
- Edit the Job server's master data.
- Select View | Server functions and specify the server functionality.
- 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
- Job server properties
- Machine roles and server functions
- Overview of server functions
- Overview of machine roles
- Job server statistic information
- Connection data for process generation
Job server properties
|
|
NOTE: More properties may be available depending on which modules are installed. |
|
Property |
Meaning | ||
|---|---|---|---|
| Server | Job server name. | ||
| Full server name | Full server name in accordance with DNS syntax.
Example: <Name of servers>.<Fully qualified domain name> | ||
| Server is cluster | Specifies whether the server maps a cluster. | ||
| Server belongs to cluster | Cluster to which the server belongs.
| ||
| IP address (IPv6) | Internet protocol version 6 (IPv6) server address. | ||
| IP address (IPv4) | Internet protocol version 4 (IPv4) server address. | ||
| Coding | Character set coding that is used to write files to the server. | ||
| Parent Job server | Name of the parent Job server. | ||
| Executing server | Name of the executing server. The name of the server that exists physically and where the processes are handled.
This input is evaluated when One Identity Manager Service is automatically updated. If the server is handling several queues the process steps are not supplied until all the queues that are being processed on the same server have completed their automatic update. | ||
| Queue | Name of the queue to handle the process steps. Each One Identity Manager Service within the network must have a unique queue identifier. The process steps are requested by the job queue using exactly this queue name. The queue identifier is entered in the One Identity Manager Service configuration file. | ||
| Server operating system | Operating system of the server. This input is required to resolve the path name for replicating software profiles. The values Win32, Windows, Linux and Unix are permitted. If no value is specified, Win32 is used. | ||
| Service account data | One Identity Manager Service user account information. In order to replicate between non-trusted systems (non-trusted domains, Linux server) the One Identity Manager Service user information has to be declared for the servers in the database. This means that the service account, the service account domain and the service account password have to be entered for the server. | ||
| One Identity Manager Service installed | Specifies whether a One Identity Manager Service is installed on this server. This option is enabled by the procedure QBM_PJobQueueLoad the moment the queue is called for the first time.
The option is not automatically removed. If necessary, you can reset this option manually for servers whose queue is no longer enabled. | ||
| Stop One Identity Manager Service | Specifies whether the One Identity Manager Service has stopped. If this option is set for the Job server, the One Identity Manager Service does not process any more tasks.
You can make the service start and stop with the appropriate administrative permissions in the program "Job Queue Info". For more detailed information, see the One Identity Manager Process Monitoring and Troubleshooting Guide. | ||
| No automatic software update | Specifies whether to exclude the server from automatic software updating.
| ||
| Software update running | Specifies whether a software update is currently being executed. | ||
|
No direct database connection |
Specifies whether the Job server has a direct connection to the database. Enable this option if the Job server receives its processes through an application server. | ||
|
Connection data |
If the Job server has no direct connection to the database, enter the connection data for the application service. Designer You enter connection data in Base data | Security settings | Connection data. | ||
| Extended properties | Additional information about Job servers. The UID of the Job server and the details of creation and change (user, date) are displayed. These cannot be edited. | ||
| Server function | Server functionality in One Identity Manager. One Identity Manager processes are handled depending on the server function. | ||
| Machine role | Role of the Job server in One Identity Manager. Installation packages to be installed on the Job server are found depending on the selected machine role. |
Related Topics
- Overview of server functions
- Overview of machine roles
- Job server statistic information
- Connection data for process generation
- JobServiceDestination
Machine roles and server functions
A machine role describes the role a computer or server assumes in a One Identity Manager system. You can give each computer or server several roles. This means, one or more machine roles can be assigned. You select machine roles when One Identity Manager components are installed.
Machine roles are structured hierarchically. If you select a machine role at installation, all parent machine are also assigned.
An example of machine role structure
Server
Job server
Active Directory
If you select the Active Directory machine role during the installation, the Job server and Server machine roles are also assigned.
Some machine roles such as Web cannot be actively selected during the installation. These machine roles are automatically assigned when different web applications are installed with the Web Installer.
Machine roles for installing the One Identity Manager Service are linked with server functions. The server function defines the functionality of a server in One Identity Manager. One Identity Manager processes are handled depending on the server function. The server functions available are predefined when a server installed, based on the selected machine role.
Example for the connection between machine roles and server functions.
The Active Directory machine role is connected to the Active Directory Connector server function. Therefore, when you set up an Active Directory synchronization project after the machine role is installed, the server is available as synchronization server in One Identity Manager.
The installation packages and files to be installed on the computer or server are specified in a machine role. The information about the machine role, the installation package and the files is saved in the file InstallState.config during installation and are thus available for automatic software update.
|
|
NOTE: If you use the Software Loader to import new files into the One Identity Manager database, you should assign the files to a machine role. This ensures that the file are distributed by automatic software update. For detailed information about automatic software updates, see the One Identity Manager Installation Guide. |