Enabling Extended Logging of Process Steps
Success and error messages from process handling are written to the One Identity Manager Service log file. In order to test you processes, you can enable logging mode for process steps in the Job Queue Info. This writes progress messages from the process step with the severity level "debug" in a separate log. You can view the log in Job Queue Info as well as in the One Identity Manager Service log.
To enable process step logging mode
- In order to log messages on success and failure, Select the process step Job queue view and select Execution log | Create always in the context menu.
- In order to log messages only on failure, Select the process step in the Job queue view and select Execution log | On error in the context menu.
|
|
NOTE: You can set the log mode by default for separate process steps. To do this, edit the process step in the Process Editor. |
To display the log in Job Queue Info
- Select the process step in the Job queue view and select Execution log | Show in the context menu.
This displays the log in a separate window. If a process step was executed more than once, for example, if it is re-enabled more than once, several log are displayed.
To display the log in the One Identity Manager Service log file
- Select the Job server in the Server status view and select Open in browser in the context menu.
- The log is labeled with a link "Log written to Job_<UID_Job>_<yyyymmdd>_<Timestamp>.log". Click the link to display the log.
The files are stored in the One Identity Manager Service log directory.
Repository structure:
<log directory>\JobLogs\<first 4 digits of the UID_Job>\Job_<UID_Job>_<yyyymmdd>_<Timestamp>.log
To end log mode
- Select the process step in the Job queue view and select Execution log | Disable in the context menu.
Related Topics
Determining the State of the Server
This view gives you a faster overview of all the Job servers and Web servers available in the network. One Identity Manager Service configurations of each Job server stored in the database are used to get more detailed results of Job server status queries. This is especially required if the HTTP server port has been set individually or a Job server processes several queues.
|
|
NOTE: Configure and enable the schedule "Get configuration file from the Job server and write in the Job server configuration" in the Designer to load the One Identity Manager Service Job server configuration into the database. |
To determine the server status
- Select View | Server state from the menu.
To query the status of all the existing Job servers in the database
- Use F5.
To query the status of a single Job server
- Use Get status in the context menu.
|
|
NOTE: Set the HTTP port to be queried and the maximum response time in the program settings. |
If the server responds, the system time, the One Identity Manager Service version and the One Identity Manager Service account name are determined and displayed. The software update status as well as the current version of the software are also displayed.
|
|
TIP: Use Refresh server list or F6 to reload the list of servers. |
To display a Job server's services
- Select the Job server and select Open in browser .
The One Identity Manager Service HTTP server for the Job server is queried and the varying One Identity Manager Service services are displayed.
Related Topics
Displaying Entries in the DBQueue
When changes to inheritance relevant data, such as changes to assignments or when changes are made to certain system data, like changes to the user interface for a system user, the resulting data needs to be recalculated in the One Identity Manager. The requests are queued in the DBQueue and processed by the DBQueue Processor.
To display DBQueue entries
- Select View| DBQueue in the menu.
Calculation tasks in the table DialogDBQueue used for DBQueue Processor processing are displayed in this view. The number, sort order and name of the queued requests are displayed. The display is updated at fixed time intervals of 2 seconds.
Displaying Messages in the Database Journal
The database journal is used to store information, warning and error messages from different components of One Identity Manager, for example, DBQueue Processor, Configuration Wizard or One Identity Manager Service. Actions in the program "Job Queue Info", such as re-enabling process steps, are also written to the database journal.
To display items from database journal
- In the Job Queue Info, go to View | System log.
|
|
TIP: You can apply different filters to limit the information being displayed. Click the arrow in the column header and select a filter. The |
icon in the log toolbar shows whether a filter is active.| Icon | Meaning |
|---|---|
 |
Information is written to the error log/database journal. |
 |
A warning has been written to the database journal. |
 |
A error has been written to the database journal. |
|
|
TIP: Double-click a message to open more details in a separate dialog box. |
Figure 60: Detailed Information about a Message
The following information is displayed about a message. The range of information depends on the type of message.
| Detail | Description |
|---|---|
| Message | Logged message. |
| Program | One Identity Manager component from which the message was sent. |
| Host | Computer from which the action was started. |
| Logged in system user | System user that triggered the action. |
| Type |
Type of message. (W= Warning, I = Info, E = Error, T = Trace) |
| Date | Time and date of the log entry. |