Changing the event log for the One Identity Manager Service
By default, the One Identity Manager Service only logs messages in the event log Application.
To use an event log with a different name
-
On the Job server, manually add the file for theOne Identity Manager Service to write to. You can use PowerShell, for example, to do this.
-
Run PowerShell as administrator on the Job server.
-
Run the following CmdLet:
New-EventLog -Source "Foobar" -LogName "<file name>"
-
Enter this file name in the One Identity Manager Service configuration file, in the module EventLogWriter as the name for the event log.
-
Restart the computer.
-
Restart the One Identity Manager Service.
HTTPLogPlugins log file
If the HTTPLogPlugin plug-in is configured in the One Identity Manager Service configuration file, a log file is generated with the HTTP queries of the One Identity Manager Service. The file is written in Apache HTTP Server Combined Log Format.
Example:
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 20: Meaning of each entry
|
172.19.2.18 |
IP address that sent the request. |
|
- |
Client user name using IDENT protocol (RFC 1413)- |
|
- |
User name of the client according to HTTP 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 |
For more information about configuring the One Identity Manager Service, see the One Identity Manager Configuration Guide.
Logging messages from target system connectors
By default, the messages from the target system connectors are logged in the One Identity Manager Service's log file. External processes are logged in the StdioProcessor log file (StdioProcessor.log).
The connectors for Active Directory, Oracle E-Business Suite, HCL Domino, SAP R/3, and SCIM additionally log the following information for a message:
-
TargetSystem: Target system ID of the connector.
-
Method: Method that caused the logging to start.
-
Number: Unique error number.
-
Message: Error message.
Example:
{ "Message": "Target:\"SCIM\" Method:\"OnConnect\" Number:\"2550101\" Message:\"Method OnConnect called.\"", "TargetSystem": "SCIM", "Method": "OnConnect", "Number": "2550101", "Message": "Method OnConnect called.", "SessionId": "SCIM-0B4926", "Parent": "Log Event: Logger='SystemConnector' Level=Debug Message='Connecting target system...' SequenceID=1213", "Indention": "\t" }
Related topics
Output of extended return values from individual process components
Individual process components have process tasks with parameters that supply extended return values (OUT).
The entire output of the parameter is written to the One Identity Manager Service log file when a error occurs. For example, the output text of the listed commands or programs can be returned when you run a command or a program using the CommandComponent process component.
To log return values
Related topics
