Monitoring from Oracle Utilities Operational Device Management

This section describes the following:

• Oracle Utilities Operational Device Management Error Logs

Oracle Utilities Operational Device Management Error Logs

Monitoring the error logs is possible only in on-premises applications only. Applications on cloud cannot access the error logs.

The following error logs can be monitored for Oracle Utilities Operational Device Management:

• Errors related to the online integration invocation from Oracle Utilities Operational Device Management are stored in the ODM_ENVIRONMENT_NAME/logs/system folder.

For example: V231_ODM_PERF_BLD10_LIN_ORA_WLS/logs/system\

• Errors related to batch integration invocation from Oracle Utilities Operational Device Management are stored in the $SPLOUTPUT/ODM_ENVIRONMENT_NAME folder.

For example: /spl/sploutput/V231_ODM_PERF_BLD10_LIN_ORA_WLS

For more information about errors and notifications, see the Oracle Utilities Operational Device Management documentation.

Notifications

When Oracle Utilities Operational Device Management sends a request message out to Oracle Utilities Meter Data Management, it expects a response back. It can get a positive response when the message is processed successfully or can get an error response when a business error is encountered in the integration or from the target application.

• If there is an error encountered while processing the message, a fault will be thrown causing the message to be rolled back and a To Do entry is created, if configured.

For example: If Oracle Utilities Operational Device Management receives a contact sync response message and an error is encountered, the message will transition to an Error state.

• If the message was processed successfully, the business object or business service or service script (business object/BS/SS) defined on Inbound Web Service is invoked. If an application error is encountered inside the business object/BS/SS processing, the message will not be rolled back to the error queue. If configured, only a To Do entry is created. Otherwise, the error will only be seen in the spl-service.log file.

Note: The Inbound Web Service is invoked to process the response message. Regardless of whether To-Do was set up or not, the errors are logged in spl-service.log file.

Connection Errors

The log files provide detailed information about errors and reasons for failure.

For more information about error logs and their respective folders, refer to the Oracle Utilities Operational Device Management Error Logs section.