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

Maintenance Mode

A web application can be switched to Maintenance mode to perform maintenance.

Running sessions are not affected in maintenance mode. However, no new sessions are permitted. Users viewing the web application are displayed the contents of the file Maintenance.html which is in the root directory of the web application. You can freely edit this file to show users details about maintenance work.

Maintenance mode is enabled by adding the file Maintenance.mode to the directory App_Data of the web application (and is disabled by deleting it). Maintenance mode can also be switched on the Runtime Monitor page.

You can use maintenance mode to allow an automatic update at a specified time.

Manual Updating

Use of the update process described above is preferred. You can, however, update the web application manually by copying updated files into the bin folder of the web application.

Note that each write access to the web application's bin folder causes the web application to restart. This means, all active sessions of the application are closed and all files unsaved are lost. For this reason, you should only run a manual update of the web application if there are no active sessions.

Only files in the web application's bin folder are controlled by automatic update.

Related Topics

Monitoring with Help from Performance Counters

Monitoring with Help from Performance Counters

When you install a web application, performance counters are registered, which provide information about the state of the application.

Performance indicators can be installed later.

NOTE: Prerequisites for this are that the web application is installed on a Windows Server and has sufficient permissions to offer performance counters. It may be necessary to add the application pool user account to the local group Performance monitoring user for this. Apart from this, the web application must be running in order to select the performance indicators.

To post-install performance indicators

  1. Open the Web Designer Configuration Editor.
  2. Click Web settings and Create Windows performance indicators.

    After this is successfully completed, an installation prompt is displayed.

  3. Confirm the prompt with OK.

To view performance counters

  1. Log in to the server on which the web application is installed.
  2. Start Windows's performance monitor.
  3. Select Performance monitor on the left-hand side of the dialog box.
  4. Click in the performance monitor view.
  5. Mark One Identity ManagerWeb Portal in the Add Counters dialog box under Available counters and open the entry.

    This displays performance indicators for the web application. The following indicators are available.

    • AJAX calls: Number of asynchronous handled HTTP queries
    • Objects: Number of active database objects
    • Exceptions: Number of exception that have occurred
    • Forms: Number of active forms
    • HTML requests: Number of HTML page requests
    • PID: Number of process IDs
    • Contexts: Number of active module objects
    • Sessions: Number of active sessions
    • Session total: Total number of sessions since the application started
  6. Enter any new performance indicators you wish and select the web application under Instances of selected object:.

    TIP: You can only view web applications which are currently running. If you install a new web application, it may take a few minutes before the list of available web applications including the new one is available.

Installing the Operations Support Web Portal

Installing the Operations Support Web Portal

Before installation ensure that the minimal hardware and software prerequisites are fulfilled on the server.

NOTE: The Operations Support Web Portal is an extension of the default Web Portal and uses its CSS files. A compiled and running Web Portal is prerequisite for usage.

To install the Operations Support Web Portal

  1. Install the Web Portal.
  2. Copy the folder "Modules\QER\dvd\AddOn\Operations Support Web Portal" to the Web Portal folder. You can rename the folder to "OperationSupport", for example.
  3. Copy the following files into the Web Portal's "bin" folder.
    1. Modules\QER\install\bin\QER.WebRuntime.WebApi.dll

    2. Modules\QBM\install\bin\QBM.CompositionApi.Web.dll

  4. Ensure that the MIME type for JSON is configured in the IIS.
    1. .json = application/json

    For more information, refer to https://technet.microsoft.com/en-us/library/2761b1cf-cb53-40b2-80a1-f0c97030d7d6.

The installation is complete and you can call the Operations Support Web Portal under https://ihr.server.domain/IdentityManager/OperationSupport/.

Related Documents