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.
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"
|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|
|-||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|
The application server can be reached over a browser under:
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.
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.
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
|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.
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.
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.