Troubleshooting
The integration might experience connection, processing or messaging errors. This section provides common scenarios which can help you to troubleshoot errors, if any, and find possible solutions for:
Asynchronous Processes
The source application is the one sending out the message and the target application is the one receiving the message.
Example: Oracle Utilities Customer Care and Billing is sending a SP sync request message to Oracle Utilities Meter Data Management, Oracle Utilities Customer Care and Billing is the source application and Oracle Utilities Meter Data Management is the target application. The source queue is OUCCB2PersonSyncRequest and the target queue is OUMDM2PersonSyncRequest. The source error queue is OUCCB2PersonSyncRequestError and the target queue is OUMDM2PersonSyncRequestError.
Oracle Utilities Meter Data Management is sending a SP sync response message to Oracle Utilities Customer Care and Billing, Oracle Utilities Meter Data Management is the source application and Oracle Utilities Customer Care and Billing is the target application. The source queue is OUMDM2PersonSyncResponse and the target queue is OUCCB2PersonSyncResponse. The source error queue is OUMDM2PersonSyncResponseError and the target queue is OUCCB2PersonSyncResponseError.
Error 1: Source application sends out a message but the message does not reach the source queue.
To resolve this error, do the following:
• Navigate to the WebLogic Console to verify whether or not the message reached the source queue. Refer to the Monitoring the Queues Using the WebLogic Consolesection for more information
• Check the source application logs to see if any errors are encountered while trying to send the message out. Refer to Oracle Utilities Customer Care and Billing Error Logs or Oracle Meter Data Management Error Logs for more information on where to find the logs.
• Check the source application’s Server Configuration to ensure they are configured correctly. Refer to Oracle Utilities Customer Care and Billing Outbound Message Configuration or Oracle Utilities Meter Data Management Outbound Message Configuration.
Error 2: Source application sends out a message but the message does not reach the target queue.
To resolve this error, do the following:
Refer to the Monitoring Using WebLogic SOA Enterprise Manager section for more information.
• Verify that the BPEL processes are running.
If WebLogic SOA Enterprise Manager is not accessible or the BPEL processes cannot be seen found in the WebLogic SOA Enterprise Manger, restart the SOA managed server. It can be restarted from the WebLogic console.
• If WebLogic SOA Enterprise Manager is accessible but the BPEL process is not active, activate or start up the process from the WebLogic SOA Enterprise Manager.
• If the BPEL processes are running, verify that the message has faulted or encountered an error.
• If a technical error is encountered, the message is rolled back to the corresponding source error queue. Fix the error and move the message back to the source queue to retry.
• From WebLogic SOA Enterprise Manager, check the appropriate process instance flow trace to see the error details.
• Check the logs. Refer to the Monitoring Using WebLogic Logssection for more information.
Error 3: Source application sends out a message, message successfully processed by the integration, but the message does not reach the target application.
To resolve this error, do the following:
• In Weblogic SOA Enterprise Manager, check the process to see if the message was successfully processed by the integration layer.
Refer to the Monitoring Using WebLogic SOA Enterprise Manager section for more information.
• If a successful instance of the message was found in the WebLogic SOA Enterprise Manager, check the target queue to see if the message exists in the queue. Check the corresponding target queue of the process to see if there is a current or pending message stuck in the queue. The possible cause is that no consumers are listening to the target queue. Try restarting the target application.
Refer to the Monitoring the Queues Using the WebLogic Consolesection for more information.
• If there are still no consumers listening to the target queue after bouncing the application, check the target application’s JMS Configuration to make sure they are configured correctly. After changing the JMS configuration of the target application, restart the target application.
• Check the source application logs to see if any errors are encountered while trying to send the message out.
Refer to the Oracle Utilities Customer Care and Billing Error Logs or Oracle Meter Data Management Error Logs sections for more information on where to find the logs.
• If no message is stuck in the target queue, check the target application logs to see if any errors are encountered while trying to process the message received.
Refer to the Oracle Utilities Customer Care and Billing Error Logs or Oracle Meter Data Management Error Logs sections for more information on where to find the logs.
Synchronous Processes
The integration may experience issues with invoking the Oracle Utilities Meter Data Management web service. This section provides common scenarios which can help you troubleshoot errors and find possible solutions.
Error 1: Unable to invoke the webservice due to a PolicyEnforcement Exception or Invalid Security Policy attached to the Oracle Utilities Meter Data Management reference webservice.
This means the security policy attached to the composite process' Oracle Utilities Meter Data Management reference webservice is incorrect. Refer to the Security Policies section in the Installation Guide for more information.
To resolve this error:
1. Navigate to WebLogic SOA Server Enterprise Manager, and then navigate to SOA > SOA-Infra > CCB2-MDM2.partition.
2. Select the appropriate composite process in error.
3. Navigate to the Dashboard tab and click the Oracle Utilities Meter Data Management webservice reference.
4. Selcet the Policy Configuration tab to verify the security policy attached to the Oracle Utilities Meter Data Management web service.
5. Attach the correct security policy to the Oracle Utilities Meter Data Management reference webservice.
 
Error 2: Unable to invoke the webservice due to a 401 Unauthorized Error.
This means the service cannot be loaded because of an invalid user ID and/or password.
To resolve this error, do the following:
• Select the security policy name and click the Override Policy Configuration tab to check the csf-key linked to that policy.
• Check the define csf-key has the correct username and password defined.
1. Navigate to WebLogic SOA Server Enterprise Manager, and then navigate to SOA > SOA-Infra > CCB2-MDM2.partition.
2. Select the appropriate composite process in error.
3. Navigate to the Dashboard tab and click the Oracle Utilities Meter Data Management webservice reference.
4. Click the Policy Configuration tab to see the security policy attached to the Oracle Utilities Meter Data Management web service.
5. Select the security policy name and click the Override Policy Configuration tab to check the csf-key linked to that policy.
6. Check the csf-key defined. has the correct username and password defined.
7. Navigate to the security credential for the soa damian and verify the csf-key has the correct username and password defined.
For more information, refer to the Verifying the csf-key Generation section in the Installation Guide. The documentation is available on the Integrations page on Oracle Help Center.