Message Resubmission
This section explains the actions that users can take to fix transactions failing in the edge applications. Also, if there are any errors then this section explains how the failed messages can be resubmitted.
The error scenarios are divided into two categories:
• Business Errors
These are errors which occur in the Edge applications or in the Integration layer because of incorrect data setup. For these errors the message has to be resubmitted after the data has been corrected.
Example: Oracle Utilities Customer Care and Billing initiated FA and Order Type missing in the FS_Order_TypeCode DVM for Oracle Utilities Work and Asset Management v1.9.1.x column.
• Technical Errors
These errors are usually connection failures. It occurs when one of the three systems is unreachable. These messages are moved to the Exception Queue and can be resubmitted from the exception queue once the edge application is reachable.
Example: Oracle Utilities Customer Care and Billing initiated Order and Oracle Utilities Work and Asset Management v1.9.1.x server is down.
In case of Oracle Utilities Customer Care and Billing if the message reaches Oracle Utilities Customer Care and Billing and fails a ToDo is created. For Oracle Utilities Work and Asset Management v1.9.1.x and Oracle Utilities Mobile Workforce Management e-mail is sent out to the administrator and an Oracle Worklist application task is created.
Note: If the customer configures the fault policies for providers with retries, then the messages will not roll back into the error queue in case of errors.OOB delivered local fault policy files do not have any retries specified.
Business Errors
The business errors in the edge applications can be handled as follows:
Outgoing Messages Resend
CC&B Outgoing Messages Resend
Oracle Utilities Customer Care and Billing has message resend ability for outgoing messages.
Triggering Event
Creation, Update, or Cancellation of a field activity in Oracle Utilities Customer Care and Billing with a Dispatch Group that is associated to an external system (this is controlled by an algorithm on Dispatch Group).
Retry for Business Errors
If any of the target applications returns a business error while processing the inbound message, a negative acknowledgment is returned to Oracle Utilities Customer Care and Billing. The application can be configured to create a To Do Entry on negative acknowledgments.
• If the error is caused because of missing configuration information, the user can add or revise the configuration information and resend the original message by changing the status of the message back to Pending. This is done on the Oracle Utilities Customer Care and Billing Notification Download Staging page (using the Oracle Utilities Customer Care and Billing user interface). This sends another create, update or cancel message.
• If the error requires that something is changed on the field activity, the user can make updates to the data on the field activity in Oracle Utilities Customer Care and Billing to fix the business error. The update causes another outbound message (this time update) to be sent from Oracle Utilities Customer Care and Billing to the target application(s).
Oracle Utilities Work and Asset Management/Oracle Utilities Operational Device Management v2.1.x Outgoing Messages Resend
Oracle Utilities Work and Asset Management v2.1.x has message resend ability for outgoing messages.
Triggering Event
Creation, Update, or Cancellation of a Activity in Oracle Utilities Work and Asset Management for distributed work based on the activity type that is associated with an External system. Message is resent using the Resend button on the Activity page.
Retry for Business Errors
If the target application returns a business error while processing the inbound message, a negative acknowledgment is returned to Oracle Utilities Work and Asset Management
• If the error is caused because of missing configuration information, the user can add or revise the configuration information and resend the original message by clicking the Resend button on the Activity page. This sends another create, update or cancel message.
• If the error requires that something is changed on the Activity, the user can make updates to the data on the Activity in Oracle Utilities Work and Asset Management to fix the business error and click on the Resend button. The Resend causes another outbound message (this time update) to be sent from Oracle Utilities Work and Asset Management to the target application.
Incoming Messages Upload
Currently Oracle Utilities Customer Care and Billing and Oracle Utilities Work and Asset Management v1.9.1.x have ability to reload the messages which reach the Oracle Utilities Customer Care and Billing and Oracle Utilities Work and Asset Management v1.9.1.x staging tables but are not able to get into the application because of some configuration or data issues.
CC&B Message Upload
If an incoming field activity fails in Oracle Utilities Customer Care and Billing then an Oracle Utilities Customer Care and Billing ToDo is created and the message is stored in the XAI Upload staging.
• Navigate in Oracle Utilities Customer Care and Billing to the Main Menu > XAI > > XAI Upload Staging. Search for messages where XAI Upload Staging Status is in Error
• If there is a configuration issue in Oracle Utilities Customer Care and Billing, the configuration in Oracle Utilities Customer Care and Billing can be fixed and the message can be uploaded from the XAI Upload staging in Oracle Utilities Customer Care and Billing.
• If there is a data issue in the message, the xml message can be corrected in Oracle Utilities Customer Care and Billing XAI Upload staging and message uploaded from there.
• To upload the message, change the XAI Upload Staging status to Pending and save the message. This way XAI tries to upload the message again in Oracle Utilities Customer Care and Billing.
• For XAI Upload Staging to store the incoming error the Post Error flag has to be set on the XAI Inbound Service C1AddFAandCustomerContact (This service is used for adding field activity in Oracle Utilities Customer Care and Billing).
• The list of XAI Inbound Services for which the Post Error Flag has to be set on is as follows:
• C1RetCreateBillableChargeSA
• BillableChargeUploadMaintenance
• F1AutomaticToDoEntry
• C1CustomerContactMaintenance
• C1AddFAandCustomerContact
• C1FieldActivityMaintenance
• C1FACompletionFieldWork
• FAResponse
Oracle Utilities Work and Asset Management v1.9.1.x Message Upload
If an incoming service request fails in Oracle Utilities Work and Asset Management v1.9.1.x then an Oracle worklist task is created and e-mail sent out to the administrator. The message is also stored in the Oracle Utilities Work and Asset Management v1.9.1.x Interface tables.
Once the data is corrected the messages can be uploaded from the interface tables to the application tables in Oracle Utilities Work and Asset Management v1.9.1.x by running the batch program sdbp_ccb_service_req_interface.
Edge Application Errors – Resubmit from Integration
The BPEL Provider processes directly invoke the Edge application web services. If the Work Order calls fail in any of the edge applications then a ToDo is created in Oracle Utilities Customer Care and Billing and an e-mail notification and a worklist application entry is created for Oracle Utilities Mobile Workforce Management or Oracle Utilities Work and Asset Management v1.9.1.x.
Oracle Utilities Customer Care and Billing has failed messages upload capability using the XAI Staging Upload table. For Oracle Utilities Work and Asset Management v1.9.1.x and Oracle Utilities Mobile Workforce Management the message can be resubmitted from BPEL.
Note: The message in the Provider is already converted to the EBO model and has the COMMON column values where DVMs are used. If the data correction is addition of a new row in the DVM then the COMMON column value needs to be set in the Provider request xml.
Oracle Utilities Work and Asset Management v1.9.1.x Resubmit from Enterprise Manager
The error notification e-mail includes a link to the worklist task. The worklist task shows the Instance ID of the Oracle Utilities Work and Asset Management v1.9.1.x Provider in failure.
Resubmit a Message to Oracle Utilities Work and Asset Management v1.9.1.x from the Enterprise Manager
1. Login into the EM console.
2. Navigate to SOA, soa-infra and click the Instances tab and search for the instance ID in failure.
3. Click the instance and go to Oracle Utilities Work and Asset Management v1.9.1.x Provider link.
4. Click the Oracle Utilities Work and Asset Management v1.9.1.x Provider Flow tab. The flow of the BPEL process is displayed.
5. Click the first activity in ReceiveWorkOrder and copy the xml displayed in the activity to notepad or any other text editor.
6. Remove the ProcessWorkOrderReqMsg and part tag from the beginning and the end of the xml.
7. Add soap envelope tags at the beginning and the end of the remaining message as noted below:
Add: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
Add: <soap:Body>
Remove: <ProcessWorkOrderReqMsg><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="ProcessWorkOrder">
Do not change: <ProcessWorkOrderEBM xmlns:aia="http://www.oracle.com/XSL/Transform/java/oracle.apps.aia.core.xpath.AIAFunctions" xmlns:hashmap="http://www.oracle.com/XSL/Transform/java/java.util.HashMap" xmlns:xref="http://www.oracle.com/XSL/Transform/java/oracle.tip.xref.xpath.XRefXPathFunctions" xmlns:UtilityWorkOrder="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/WorkOrder/V1" xmlns="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/WorkOrder/V1">
….
….
…..
Do not change: </ProcessWorkOrderEBM>
Remove: </part></ProcessWorkOrderReqMsg>
Add: </soap:Body>
Add: </soap:Envelope>
8. Correct any data which needs to be corrected, if applicable. Now the corrected data can be submitted from the EM Console.
9. On the EM Console, go to SOA, soa-infra, default and select the process for the Oracle Utilities Work and Asset Management v1.9.1.x Provider named ProcessWorkOrderOUWAMUtilitiesProvABCSImpl.
10. Click the Test tab, enter security credentials and select the Input Arguments - XML View from the drop down.
11. Click Post XML Message at the bottom of the screen. Completing this action causes the Oracle Utilities Work and Asset Management v1.9.1.x Provider to resubmit the message to the Oracle Utilities Work and Asset Management v1.9.1.x system.
Oracle Utilities Mobile Workforce Management Resubmit from Enterprise Manager
The error notification e-mail contains a link to the worklist task. The worklist task has the Instance ID of the Oracle Utilities Mobile Workforce Management Provider in failure.
Resubmit a message to Oracle Utilities Mobile Workforce Management from the EM Console
1. Login to the EM console.
2. Go to SOA, soa-infra and click the Instances tab and search for the instance ID in failure.
3. Click on the instance and go to the Oracle Utilities Mobile Workforce Management Provider link. Then click the Oracle Utilities Mobile Workforce Management Provider Flow tab. The flow of the BPEL process is displayed.
4. Click on the first activity in the flow ReceiveOrder and copy the xml displayed in the activity to notepad or any other editor.
5. Remove the ProcessOrderReqMsg and part tag from the beginning and the end of the xml.
6. Add soap envelope tags at the beginning and the end of the remaining message as noted below:
7. Make the following modifications:
Add: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
Add: <soap:Body>
Remove: <ProcessOrderReqMsg><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="ProcessOrder">
Do not change: <ProcessWorkOrderEBM xmlns:aia="http://www.oracle.com/XSL/Transform/java/oracle.apps.aia.core.xpath.AIAFunctions" xmlns:hashmap="http://www.oracle.com/XSL/Transform/java/java.util.HashMap" xmlns:xref="http://www.oracle.com/XSL/Transform/java/oracle.tip.xref.xpath.XRefXPathFunctions" xmlns:UtilityWorkOrder="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/WorkOrder/V1" xmlns="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/WorkOrder/V1">
Do not change: <corecom:EBMHeader xmlns:Orderabo="http://splwg.com/ExtractFAInfo.xsd" xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
….
….
…..
Do not change: </ProcessWorkOrderEBM>
Remove: </part></ProcessOrderReqMsg>
Add: </soap:Body>
Add: </soap:Envelope>
8. Correct any data which needs to be corrected, if applicable. Now the corrected data can be submitted from the EM Console.
9. On the EM Console, go to SOA, soa-infra, default and select the process for the Oracle Utilities Work and Asset Management v1.9.1.x Provider named ProcessWorkOrderOUMWMUtilitiesProvABCSImplV2.
10. Click the Test tab, enter security credentials and select the Input Arguments - XML View from the drop down.
11. Click Post XML Message at the bottom of the screen.
Completing this action causes the Oracle Utilities Mobile Workforce Management Provider to resubmit the message to the Oracle Utilities Mobile Workforce Management system.
Technical Errors
Resubmit from JMS Error Queue
If there is a connection failure on the provider end, transactions are moved to a JMS Error queue per application. Log on to the Weblogic Console to monitor the JMS Queues and move messages from the Error Queue to the Main Queue once the reason for failure is resolved.
Note: If the customer configures the fault policies for providers with retries then the messages will not roll back into the error queue in case of errors.OOB delivered local fault policy files do not have any retries specified