Servers must know your server functionality in order to handle Epic specific processes in One Identity Manager. For example, the synchronization server.
You have several options for defining a server's functionality:
• Create an entry for the Job server in Designer under Base Data | Installation | Job server. For more information, see the One Identity Manager Configuration Guide.
Use this task if the Job server has already been declared in One Identity Manager and you want to configure special functions for the Job server.
NOTE: One Identity Manager must be installed, configured, and started in order for a server to execute its function in the One Identity Manager Service network. Proceed as described in the One Identity Manager Installation Guide.
To edit a Job server and its functions
1. In One Identity Manager, select the category Epic healthcare | Basic configuration data | Server.
2. Select the Job server entry in the result list.
3. Select Change master data.
4. Edit the Job server's master data.
5. Select Assign server functions in the task view and specify server functionality.
6. Save the changes.
For more information, see
NOTE:
- All editing options are also available in Designer under Base Data | Installation | Job server.
- More properties may be available depending on which modules are installed.
Table 16: Job Server Properties table
| Property |
Meaning |
| Server |
Job server name. |
| Full server name |
Full server name in accordance with DNS syntax. Example: . |
| Target system |
Computer account target system. |
| Language |
Language of the server. |
| Server is cluster |
Specifies whether the server maps a cluster. |
| Server belongs to cluster |
Cluster to which the server belongs.
NOTE: The properties Server is cluster and Server belongs to cluster are mutually exclusive |
| IP address (IPv6) |
Internet protocol version 6 (IPv6) server address. |
| IP address (IPv4) |
Internet protocol version 4 (IPv4) server address. |
| Copy process (source server) |
Permitted copying methods that can be used when this server is the source of a copy action. At present, only copy methods that support the Robocopy and rsync programs are supported. If no method is given, the One Identity Manager Service determines the operating system of the server during runtime. Replication is then performed with the Robocopy program between servers with a Windows operating system or with the rsync program between servers with a Linux operating system. If the operating systems of the source and destination servers differ, it is important that the right copy method is applied for successful replication. A copy method is chosen that supports both servers. |
| Copy process (target server) |
Permitted copying methods that can be used when this server is the destination of a copy action. |
| 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.
NOTE: Servers must be manually updated if this option is set. |
| Software update running |
Specifies whether a software update is currently being executed. |
| Server function |
Server functionality in One Identity Manager. One Identity Manager processes are handled depending on the server function. |
Related Topics
Specifying server functions
NOTE:
- All editing options are also available in Designer under Base Data | Installation | Job server. The server function defines the functionality of a server in One Identity Manager. One Identity Manager processes are handled depending on the server function.
- More server functions may be available depending on which modules are installed.
Table 17: Table
| Server Function |
Remark |
| Update Server |
This server executes automatic software updating of all other servers. The server requires a direct connection to the database server that One Identity Manager database is installed on. The server can execute SQL tasks. The server with the installed One Identity Manager database, is labeled with this functionality during initial installation of the schema. |
| SQL processing server |
The server can execute SQL tasks. Several SQL processing servers can be set up to spread the load of SQL processes. The system distributes the generated SQL processes throughout all the Job servers with this server function. |
| CSV script server |
The server can process CSV files using the ScriptComponent process component. |
| One Identity Manager Service installed |
Server on which a One Identity Manager Service is installed |
| SMTP host |
Server from which One Identity Manager Service sends email notifications. Prerequisite for sending mails using One Identity Manager Service is SMTP host configuration. |
| Default report server |
Server on which reports are generated. |
| One Identity Epic Connector |
Server on which the One Identity Epic connector is installed. This server executes synchronization with the One Identity Epic target system. |
Related topics
Master data for jobserver
EMPTemplate determines the access rights that a user has on an Epic System. The list of EMPTemplates are exported from the target system to the file EMPTemplate.csv.
EMPTemplate is loaded into the One Identity Manager by synchronization. You can assign and remove EMPTemplate from an user in One Identity Manager. However, you cannot edit the EMPTemplate in One Identity Manager.
To add EMPTemplate to an user, you can assign the EMPTemplate directly to the users. Or it can be added indirectly to departments, cost centers, location, business roles, or to the IT Shop.
After an EMPTemplate is assigned to an user, the following additional optional properties can be assigned to the EMPTemplate.
Table 18: Additional optional properties that can be assigned to the EMPTemplate
| Property |
Description |
| LoginType |
The applications for which this template should be applied automatically. |
| StartDate |
The date from which the user should begin to have access to this template. |
| EndDate |
The date after which the user should no longer have access to this template. |
Format of the CSV file EMPTemplate.csv
The CSV file EMPTemplate.csv has a specific format with the columns TemplateID and TemplateName.
The columns in the EMPTemplate.csv file are
Table 19: Columns in the EMPTemplate.csv file
| Column name |
Description |
| TemplateID |
EMPTemplate’s External ID
IMPORTANT:
Only ExternalID should be used. |
| TemplateName |
Describes the EMP Template name |
NOTE:
- If the TemplateName or TemplateID field has comma (,), it must be properly escaped with double quotes.
- Sample EMPTemplate report can be found in the EPC module’s Miscellaneous folder.
