Chat now with support
Chat with Support

Identity Manager 8.0 - Installation Guide

About this Guide One Identity Manager Overview Installation Prerequisites Installing the One Identity Manager Installing and Configuring the One Identity Manager Service Updating the One Identity Manager Installing and Updating a One Identity Manager Application Server Installing, Configuring and Maintaining the Web Portal Installing the Operations Support Web Portal Installing and Updating the Manager Web Application Logging into One Identity Manager Tools Troubleshooting Appendix: One Identity Manager Authentication Modules Appendix: Creating a One Identity Manager Database for a Test or Development Environment from a Database Backup Appendix: Manager Web Application Extended Configuration Appendix: Machine Roles and Installation Packages Appendix: Settings for a New SQL Server Database

Displaying the One Identity Manager Service Log File

Displaying the One Identity Manager Service Log File

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

  • 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

  • Select the Job server in the Service status view and select Open in browser in the context menu.

    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.

Table 32: Log File Color Code
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.

Changing the User Account or One Identity Manager Service Start Type

Changing the User Account or One Identity Manager Service Start Type

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

  1. Open the server's service administration and select the entry One Identity Manager Service in the list of services.
  2. Open service properties with the context menu item Properties.
  3. Change the start type on the General tab (if required).

    The start type "automatic" is recommended.

  4. Change the user account under which the service runs on the Login tab.
  5. Click Apply.
  6. Close the service's properties with OK.
  7. Start the service from the context menu item Start.

    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.

Related Topics

The One Identity Manager Service in a Cluster

The One Identity Manager Service in a Cluster

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.

Detailed information about this topic

Registering the One Identity Manager Service in a Cluster

Registering the One Identity Manager Service in a Cluster

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:

  • Service specific setting on the nodes where the virtual server sits are replicated on all other nodes! The service, therefore, always has the same configuration independent of the node on which it is actually started.
  • The service is always started only on the current node of the virtual server (the virtual server's current node). The service is stopped on all other nodes.
  • The service is booted and shutdown with the virtual server. If the cluster is not enabled, the service is stopped on all nodes.
  • Services on nodes are brought automatically in the required state (manual or stopped) before registration by the program.
Related Topics
Related Documents