Monitoring from Oracle Utilities Customer Care and Billing
This section provides information on the following:
Oracle Utilities Customer Care and Billing Error Logs
Errors related to the online integration invocation from Oracle Utilities Customer Care and Billing are stored in the CCB_ENVIRONMENT_NAME/logs/system folder.
Example: V24_V24020_CCB_SOA12C_CERT_LIN_ORA_WLS /logs/system
Errors related to batch integration invocation from Oracle Utilities Customer Care and Billing are stored in the $SPLOUTPUT/ CCB_ENVIRONMENT_NAME folder.
Example: /spl/sploutput/V24020_CCB_SOA12C_CERT_LIN_ORA_WLS
Oracle Utilities Customer Care and Billing Notifications
When Oracle Utilities Customer Care and Billing 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 (Oracle Utilities Meter Data Management).
When Oracle Utilities Customer Care and Billing receives the response message from the inbound Oracle Utilities Customer Care and Billing response queue, the message is parsed and converted to an XML document, check that the XML is valid and 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 Customer Care and Billing response error queue and a To Do entry is created, if configured.
Example: If Oracle Utilities Customer Care and Billing receives a person sync response message from the Oracle Utilities Customer Care and Billing person sync response queue and an error is encountered, the message is moved to the Oracle Utilities Customer Care and Billing person sync response error queue.
• If the message is 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 response 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
Message 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 Response, Billing Determinant Response and Replacement Reads Request, the Post Error checkbox must be set to Yes.
Oracle Utilities Customer Care and Billing 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 Customer Care and Billing Error Logs.