Oracle Integration Cloud Service (OICS) – Part 2
In the previous blog on Oracle Integration Cloud Service, we guided you through building a basic integration, connecting with SOAP-based web services, and mapping data. Now, we’ll take it a step further by exploring advanced configurations to enhance your integration workflows. Now we will create an integration that utilises three generic SOAP web services for message transmission in Oracle Integration Cloud Service. You will configure WSDL files for each service, including:
- A request message
- A response message
- An enrichment response message
Once the WSDL setup is complete, you will use the mapper to connect data fields by dragging and dropping them from the trigger/source structure of one web service to the invoke/target structure of another. After mapping the data, you will activate the integration and monitor message interactions. Additionally, you will create a cloned version of the integration, allowing for further customisation as needed.
Cloning an Integration
Now that you have created the Hello World integration, you can proceed with cloning it. This process duplicates the integration flow, preserving all connections and data mappings. While you will assign a new name and version number to the cloned integration, the rest of the configuration remains unchanged. Once the cloning is complete, you can modify and customise the integration as needed in Oracle Integration Cloud Service.
- Choose Clone from the menu. The Clone Integration dialog will appear.
- Enter a unique name and version number different from the original integration, then select Clone.
| Field | Enter |
| Integration Name | Hello_World_Enrichment_A2f49138 |
| Identifier | Automatically generated from the integration name |
| Version | Enter, a different version number. For example, if you enter 2, the value is automatically changed. Identifier to 02.00.0000 to follow the required naming convention. |
| Package Name | Nothing to enter. |
| Description | This test case will demonstrate how to clone a completed integration. |
The following dialog appears:
The cloned integration is shown at the top, but it remains inactive.
- Select the integration to start making customisations. In this example, we will enhance the integration flow with response enrichment.
Take your expertise to the next level with our
Oracle Integration Cloud Service (OICS) Training
Add Enrichment to the Cloned Integration
- If the Technologies palette is not visible on the right, click the Show Palette icon.
- From the Technologies palette, drag the “SayHello_A2f_49_138” SOAP Connection onto the response arrow icon. A dialog will appear to create the enrichment response SOAP web service.
- Enter the following details and click Next.
| Field | Enter |
| What do you want to call your endpoint? | AddVisitTimeDetails |
Choose the “visitTimeStampDetails” operation, then click Next and Done.
A prompt will appear: “This will delete any impacted mapping(s). Are you sure you want to continue?”
Click Yes to proceed. The integration flow will look as follows:
4. Click Save.
Map Data Between Trigger/Source & Invoke/Target in Oracle Integration Cloud Service
- Select the Response Enrichment Mapping icon located between the trigger/source and invoke/target to open the mapper.
- Map the relevant source field to the invoke/target field
| Trigger/Source | Field Invoke/Target Field |
| sayHelloResponse > SayHelloReturn | visitTimestampReq > reqMsg |
Drag the trigger/source field onto the invoke/target field, ensuring the text of both fields aligns. If the mapping is successful, the UI will appear as shown:
- Click Save, then select Exit Mapper. The Response Enrichment Mapping icon will turn green, indicating it has been configured.
- Click the Response Mapping icon and remove the previous mapping (if it was not deleted in the earlier step).
- Click the Response Mapping icon to open the mapper once more. This step is necessary due to the enrichment response mapping you applied earlier.
- Map the specified trigger/source field to the invoke/target field.
| Trigger/Source Field | Invoke/Target Field |
| $ResponseEnrichmentApplicationObject >visitTimestampResp > respMsg | GreetResponse > Greeting |
Drag the trigger/source field over the invoke/target field, ensuring both texts align. If the mapping is successful, the UI will appear as shown:
- Click Save, then select Exit Mapper. The Response Mapping icon will turn green, indicating it has been successfully configured.
- Select Exit Integration.
- Click Activate to enable the integration.
- When prompted, click Yes to confirm and choose Enable tracing, including payload into Activity Stream, as shown in the dialog below.
The integration status will update to Active TRACE ENABLED, allowing visibility of message logs in the Monitoring screens as messages are processed through ICS.
- Click the information icon to view integration details. The endpoint URL provided here is necessary for testing the integration.
End Point URL : https://ics21-usoracle72468.integration.us2.oraclecloud.com/integration/flowsvc/soap/HELLO_WORLD_ENRICHME_A2F49138/v02/?wsdl
Test Cloned Integration in Oracle Integration Cloud Service
Please refer to the detailed steps in Lab1. The high-level steps are outlined below:
- Create a SOAPUI project using the ICS service endpoint URL provided above.
a. Modify the payload by including a value for FirstName.
b. Implement basic authentication with the credentials given to you.
c. Add Timestamp Details.
d. Test the service.
The request-response sample from SOAP UI should appear as shown below:
Monitoring Oracle Integration Cloud Service
- Navigate back to the Oracle Integration Cloud Service user interface.
- Select Monitoring in the top-right corner. You will see details for the Hello World Enrichment Use Case integration, along with any other activated integrations.
- Click the Runtime Health tab to view activity stream details regarding the message flow.
Conclusion
In this blog on Oracle Integration Cloud Service, we explored the process of cloning an integration, enriching a message with a SOAP web service, and mapping data between the respective web service data structures. We also covered how to activate and monitor the integration in Oracle Integration Cloud Service, ensuring that each step is seamlessly executed for efficient data management and integration monitoring.
