The One Identity Manager Service log file can be displayed in a browser.
To display the One Identity Manager Service log file in a browser
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 varying 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 filter interactively. There is a menu on the website for this. Only text contained in the log file can be displayed in this case. If, for example, the message type is set to "Warning", no "Info" messages can be shown even if the appropriate filter is chosen.
The log output is color coded to make it easier to identify.
|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 an appropriate 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 Advice for 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.
Once registered, the One Identity Manager Service is governed by cluster handling for site resilience and load balancing. The service is installed on a virtual server which simulates the cluster. All computer related operations and service data operate, transparently, with the virtual server and not the real computer (cluster nodes). This also applies to clients that contact the service through the server name, for example RPC (ORPC, DCOM), TCP/IP (Winsock, Named Pipes), HTTP.
Because the service is in the context of the virtual server, note the following facts: