Chat now with support
Chat with Support

Identity Manager 8.0 - Configuration Guide

One Identity Manager Software Architecture Working with the Designer Customizing the One Identity Manager Default Configuration Checking Data Consistency Compiling a One Identity Manager Database Working with Change Labels Basic System Configuration Data
One Identity Manager Authentication Module Database Connection Data Configuration Parameters for System Configuration Setting up the Mail Notification System Enabling More Languages for Displaying and Maintaining Data Displaying Country Information Setting Up and Configuring Schedules Password Policies in One Identity Manager Reloading Changes Dynamically TimeTrace Databases Machine Roles and Server Functions Files for Software Update Operating Systems in Use System Configuration Reports Using Predefined Database Queries Managing Custom Database Objects within a Database
The One Identity Manager Data Model Granting One Identity Manager Schema Permissions Working with the User Interface
Object definitions for the User Interface User Interface Navigation Forms for the User Interface Statistics in the One Identity Manager Extending the Launchpad Task Definitions for the User Interface Applications for Configuring the User Interface Icons and Images for Configuring the User Interface Language Dependent Data Representation
Process Orchestration in One Identity Manager
Declaring the Job Server One Identity Manager Service Configuration Handling Processes in the One Identity Manager
Tracking Changes with Process Monitoring Conditional Compilation using Preprocessor Conditions One Identity Manager Scripts Maintaining Mail Templates Reports in the One Identity Manager Custom schema extensions Transporting One Identity Manager Schema Customizations Importing Data Web Service Integration SOAP Web Service One Identity Manager as SPML Provisioning Service Provider Searching for Errors in the One Identity Manager Processing DBQueue Tasks One Identity Manager Configuration Files

HTTPLogPlugins Log File

If the HTTPLogPlugin is configured in the One Identity Manager Service, a log file with HTTP is created with One Identity Manager Service requests. The file is written in Apache HTTP Server Combined Log Format.

Example Entry

172.19.2.18 - - [03/Feb/2005:14:55:48 +0100] "GET /resources/JobService.css HTTP/1.x" OK - "http://<server name>:<port>/status/LogWriter/Config""Mozilla/5.0 (Windows; U; 5.1; en-US; rv:1.7.5) Gecko/20041108Firefox/1.0"

Table 363: Meaning of each Entry
Entry Meaning
172.19.2.18 IP address before the request.
- Client user name using IDENT protocol (RFC 1413)-
- Client user name conforming to HHTP authentication
[03/Feb/2005:14:55:48 +0100] Time that the request is processed on the server
GET /resources/JobService.css HTTP/1.x" Request
OK Status code-
- Size of data sent back to the browser
"http://<server name>:<port>/status/LogWriter/Config" URL from which the page can be accessed
"Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.5) Gecko/20041108Firefox/1.0" Browser name
Related Topics

Displaying One Identity Manager Application Server Status

Displaying One Identity Manager Application Server Status

The application server can be reached over a browser under:

http://<server>/<application name>

https://<server>/<application name>

TIP: You can open the web server's status display in Job Queue Info. Select the menu item View | Server state in the Job Queue Info and display the web server's state on the Web servers tab by using Open in browser in the context menu.

You will see different status information. Status information for the application server are displayed as performance counters.

In addition, API documentation is available here.

Processing DBQueue Tasks

The tasks queued in the DBQueue are the result of triggering, modifications to configuration parameters (for example, changes to a configuration parameter concerning inheritance) or executing scheduled tasks. The DBQueue Processor processes tasks in the DBQueue. The DBQueue Processor uses several slots for executing tasks in parallel.

Detailed information about this topic

Configuring the DBQueue Processor for Test and Development

Configuring the DBQueue Processor for Test and Development

DBQueue ProcessorA number of Use the staging level of the One Identity Manager database to specify whether a test database, development database or a live database is being dealt with. configuration settings are controlled by the staging level. If you modify the database staging level the configuration settings are changed.

To modify a database staging level

  1. Select the category Base Data | General | Databases in the Designer.
  2. Select the database and change the value of the property Staging level to "Test environment", "Development system" or "Development system".
  3. Select the Database | Commit to database... and click Save.
Table 364: DBQueue Processor Database Settings for Development, Test and Live Environments
Setting Database Staging Level
Development Environment Test Environment Live Environment
Maximum DBQueue Processor runtime 20 minutes 40 minutes 120 minutes
Maximum number of slots for DBQueue Processor 3 5 Maximum number of slots according to the hardware configuration

The DBQueue Processor configuration settings are configured for normal operations and must not be modified normally. The number of configuration settings is reduced in the case of test and development environments because there may be more databases on one server.

If you have to change the settings for test or development environments on performance grounds, you must modify the following configuration parameter settings in the Designer.

Table 365: Configuration Parameters for the DBQueue Processor
Configuration parameter Meaning
QBM\DBQueue\CountSlotsMax

This configuration parameter specifies the number of maximum slots available.

Enter the value 0 to use the maximum number of slots according to the hardware configuration.

QBM\DBQueue\KeepAlive

This configuration parameter regulates the maximum runtime of the central dispatcher. Tasks on slots currently in use are still processed when the timeout expires. Then the slot database schedules are stopped and the central dispatches exits.

The lowest permitted value for runtime is 5 minutes; the highest value is 720 minutes.

Related Topics
Related Documents