Solution Overview
The technical aspects involved in the integration between Oracle Project Management and Oracle Utilities Work and Asset Cloud Service are:
• The integration layer consists of integration processes deployed on Oracle Integration Cloud.
• The integration processes interact with other applications using the following adapters:
• Oracle ERP Cloud Adapter to subscribe to project status event and to get Project Status.
• REST Adapter to interact with the Oracle Fusion ERP Cloud to fetch Project Manager Details, Budget Amount Details, and Financial Plan Types.
• Oracle Utilities Adapter to invoke Oracle Utilities Work and Asset Cloud Service REST API to create or update project and to send Task outbound message.
• REST Adapter to invoke the OU WACS ERPPM Common Error Handler integration flow to send errors notifications.
• The integration patterns used for the solution are:
Refer to the Integration Flows section for more information about each integration process.
One-way Asynchronous
The one-way asynchronous integration process:
1. Receives request message from the source application.
2. Transforms message from the source to the target format. Lookups are used for data translations.
3. Invokes target application to send the request message.
4. In case of any error, the scope level fault handler catches them.
5. The error instance can be re-submitted from Oracle Integration Cloud. Refer to the Error Handling section in Configuring Lookups, Error Handling, and Email Notifications for more details.
6. Email notification is optional in most cases. Configure the “notification.error.flag” property in the OUTL-BRT-WACS_ERPPM_ConfigProps lookup to ‘true’ to receive notification when errors are encountered and “notification.type.email” to ‘email’ to receive the notification via email.
7. The recipient(s) of the email notification is configured in the OUTL-BRT-WACS_ERPPM_Email_ID lookup.
Synchronous
The synchronous integration process:
1. Receives request message from the source application.
2. Transforms the message from from the source to the target format. Lookups are used for data translations.
3. Invokes target application to send the request message.
4. Upon succesful invocation of target application, receives the response message.
5. Transfomrs the message from target to source format. Lookups are used for data translations.
6. In case of any error, the global fault handler catches them.
7. Email notification is optional in most cases. Configure the “notification.error.flag” property in the OUTL-BRT-WACS_ERPPM_ConfigProps lookup to ‘true’ to receive notification when errors are encountered and configure “notification.type.email” property to ‘email’ to receive the notfictaions via email.
8. The recipient(s) of the email notification is configured in the OUTL-BRT-WACS_ERPPM_Email_ID lookup.