Monitoring from Oracle Utilities Meter Data Management

This section provides information on the following:

• Oracle Meter Data Management Error Logs

• Oracle Utilities Meter Data Management Notifications

• Oracle Utilities Meter Data Management Connection Errors

Oracle Meter Data Management Error Logs

Errors related to the online integration invocation from Oracle Utilities Meter Data Management are stored in the MDM_ENVIRONMENT_NAME/system/logs folder.

Example: /V21020_MDM_SET13_DEV_LIN_WLS_ORA/logs/system

Errors related to batch integration invocation from Oracle Utilities Meter Data Management are stored in the $SPLOUTPUT/ MDM_ENVIRONMENT_NAME folder.

Example: /V21020_MDM_SET13_DEV_LIN_WLS_ORA/logs/system

For more information about errors and notifications, see the Oracle Utilities Meter Data Management documentation.

Oracle Utilities Meter Data Management Notifications

When Oracle Utilities Meter Data Management receives a request message from Oracle Utilities Customer Care and Billing, it will send a response back to Oracle Utilities Customer Care and Billing. It can send a positive response when the message is processed successfully or can send an error response when a business error is encountered.

When Oracle Utilities Meter Data Management receives the request message from the inbound Oracle Utilities Meter Data Management request queue, the message is parsed and converted to an XML document, check that the XML is valid and check that the XML has a valid inbound service.

• If there is an error encountered while processing the message, EJBException is thrown causing the message to be rolled back to the corresponding Oracle Utilities Meter Data Management request error queue and a To Do entry is created, if configured.

Example: If Oracle Utilities Meter Data Management receives a person sync request message from the Oracle Utilities Meter Data Management person sync request queue and an error is encountered, the message is moved to the Oracle Utilities Meter Data Management person sync request error queue.)

• If the message was processed successfully, the Business Object or Business Service or Service Script (BO/BS/SS) defined on Inbound Service is invoked. If an application error is encountered inside the BO/BS/SS processing, the message is not rolled back to the error queue. Only a To Do entry is created, if configured. Otherwise, the error is seen only in the spl-service.log file.

The inbound service is invoked to process the request message.

Regardless of whether To-Do was set up or not, the errors are logged in spl-service.log file.

Setup To Do Entry for JMS Message Error

Options

Define To Do Type for Inbound JMS Message Errors Option. Use To Do Type F1-INJMS (Inbound JMS Message In Error). This To Do Type is delivered with the application. Implementation can define a custom To Do Type if needed.

Inbound Service

For every Inbound Service used to process the different Sync Request and Billing Determinant Request, the Post Error checkbox must be set to “Yes”.

Oracle Utilities Meter Data Management Connection Errors

Information about errors can be found in log files. For information about error logs and their respective folders, see the section Oracle Utilities Meter Data Management Error Logs.