|
IMPORTANT: If you are working with an encrypted One Identity Manager database, see Notes on working with an encrypted One Identity Manager database. |
Use the Server Installer to install the One Identity Manager Service. The program executes the following steps:
Setting up a Job server.
Specifying machine roles and server function for the Job server.
Remote installation of One Identity Manager Service components corresponding to the machine roles.
Configuration of One Identity Manager Service.
Starts the One Identity Manager Service.
|
NOTE: The program executes remote installation of the One Identity Manager Service. Local installation of the service is not possible with this program. Remote installation is only supported within a domain or a trusted domain. |
For remote installation of One Identity Manager Service, you require an administrative workstation on which the One Identity Manager components are installed.
To install and configure One Identity Manager Service remotely on a server
Start the program Server Installer on your administrative workstation.
Enter the valid connection credentials for the One Identity Manager database on the Database connection page.
Specify the server on which you want to install One Identity Manager Service on the Server properties page.
Select a Job server from the Server menu.
- OR -
To create a new Job server, click Add.
Enter the following data for the Job server.
Property |
Description |
---|---|
Server |
Job server name. |
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. |
Full server name |
Full server name in accordance with DNS syntax. Example: <Name of servers>.<Fully qualified domain name> |
|
NOTE: You can use the Extended option to make changes to other properties for the Job server. You can also edit the properties later with Designer. |
Specify which roles the Job server is to have in One Identity Manager on the Machine roles page. Installation packages to be installed on the Job server are found depending on the selected machine role.
Specify the function of the server in the One Identity Manager environment on the Server functions page. One Identity Manager processes are handled depending on the server function.
The server's functions depend on which machine roles you have selected. You can limit the server's functionality further here.
|
NOTE: The initial service configuration is predefined already. If further changes need to be made to the configuration, you can do this later with the Designer. For detailed information about configuring the service, see the One Identity Manager Configuration Guide. |
To configure remote installations, click Next.
Confirm the security prompt with Yes.
Select the directory with the install files on Select installation source.
Select the file with the private key on the page Select private key file.
|
NOTE: This page is only displayed when the database is encrypted. |
Enter the service's installation data on the Service access page.
Data |
Description |
---|---|
Computer |
Server on which to install and start the service from. To select a server
|
Service account |
User account data for the One Identity Manager Service. To enter a user account for the One Identity Manager Service
|
Installation account |
Data for the administrative user account to install the service. To enter an administrative user account for installation
|
Click Next to start installing the service.
Installation of the service occurs automatically and may take some time.
Click Finish on the last page of Server Installer.
|
NOTE: The service is entered with the name One Identity Manager Service in the server service management. |
The One Identity Manager Service log file can be displayed in a browser.
You call up the log file with the appropriate URL.
http://<server name>:<port number>
The default value is port 1880.
To open the One Identity Manager Service log file in Job Queue Info
The One Identity Manager Service HTTP server for the Job server is queried and the various One Identity Manager Service services are displayed.
Figure 3: One Identity Manager Service Log File
The messages to be displayed on the web page can be filtered interactively. There is a menu on the website for this. Only text contained in the log file can be displayed in this case. If the message type is Warning, for example, messages with the Info message type cannot also be displayed if the relevant filter is selected.
The log output is color coded to make it easier to identify.
Color | Meaning |
---|---|
Green | Processing successful. |
Yellow | Warnings occurred during processing. |
Red | Fatal errors occurred during processing. |
|
NOTE: If you want to retain the color information to send by mail, you need to save the complete web page. |
When One Identity Manager Service is installed the service is already entered in the "Services" on the computer.
To customize login data and the way the service is started
The start type Automatic is recommended.
If the One Identity Manager Service cannot be started, a corresponding message is written to the server event log.
|
NOTE: If you change the One Identity Manager Service user account, you must save the service's configuration file in the service’s install directory again. |
|
NOTE: If you are working with an encrypted One Identity Manager database, see Notes on working with an encrypted One Identity Manager database. |
The idea of a cluster solution is to make the system highly available. The aim is to limit system failure to only a few seconds if a hardware or software component fails. This can be achieved with the installation of a Windows cluster solution (only possible with Enterprise servers). The following diagram shows such a solution.
Figure 4: Example of a Cluster Solution
This cluster is made up of 2 physical computers "Server A" and "Server B" that use the same disk array and have their own individual system hard drive. Every server has a Windows operating system. Both servers are installed identically so that in the case of failure one server can take over from the other.
All redundant system components are managed by the cluster manager. From an external point of view, the cluster is addressed as a single, virtual server "Server C". The service or user that is accessing the service is automatically connected to the physical server that is currently carrying out the work in the cluster.
If one of the servers fails, then the redundant server in the cluster automatically takes over. The virtual server remains the contact partner, only the physical server that is running, changes.
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy