Oracle Integration Cloud Service

Lab Guide – ICS Hello World

Page 1 of 35
Contents
Prerequisites............................................................................................................................................................................ 3
Create Hello World Integration Flow ....................................................................................................................................... 3
Enrich Hello World Integration Flow..................................................................................................................................... 26
Test Cloned Integration......................................................................................................................................................... 34
Monitoring ............................................................................................................................................................................ 34

Page 2 of 35
Prerequisites
SOAP UI tool should be installed to test end to end integration flows.

Install SOAP UI
Install SOAPUI client from below location.

http://www.soapui.org/Downloads/soapui-nightly-builds.html

Objective
This lab explains the process of creating a basic integration. The lab introduces to the ICS user interface and shows how
to:

 Create an integration flow

 Integrate with SOAP-based web services
 Map elements between source and target applications
 Activate and test the integration

The flow that is created follows a request-response pattern. A source application issues a request to retrieve data from a
target application via Integration Cloud Service (ICS) and receives an immediate response.

Note: Since there are multiple attendees sharing a single ICS environment, please use the

<ClassID> <StudentID> information (will be provided to you by the instructor) as a suffix to uniquely identify following
integration artifacts:

 Connections

E.g. If your <ClassID> is 06 and your <StudentID> is 29, then you will name your connection as

RightNow Conn 06 29

 Integration flows

E.g. If your <ClassID> is 06 and your <StudentID> is 29, then you will name your integration flows as

Account Sync 06 29

Create Hello World Integration Flow

1. Click the Designer link at the top left corner of the ICS console UI:

Page 3 of 35
2. Click the Connections link

3. Click “Create” button and select “SOAP” Adapter(If you are not able to find, search for SOAP as per the screen given
below)

Page 4 of 35
4. Enter the following information into the New Connection - Information dialog box:

Field Enter

Connection Name Greetings <ClassId> <StudentId>

e.g. Greetings 06 29

Identifier Nothing to enter.

Automatically generated from the integration

name: ex: GREETINGS_06_29

Connection Role Trigger and Invoke

Use the default value Trigger and Invoke

Page 5 of 35
 Click on Create button.

5. Specify the email address as [email protected]. This field is optional.

6. In the “Connection Properties” section click on “Configure Connectivity” button and specify the WSDL URL and click
“OK”.
Get the Greeting Service WSDL URL from the Integration Labs En,,vironment Details page.

Your configuration section should look something like below:

7. In the “Security” section click on “Configure Security” button. Select the Security Policy as “No Security Policy” and
Click OK.

Page 6 of 35
8. Click on “Test” at the top right corner. And then click on Test on Confirmation window. If the connection is tested
successfully you will observe the connection completion shows up as 100%. Also you will observe a message “The
connection test was successful”.

9. Click “Save” and click on “Close” to close the window.

10. Click the Integrations link at the top left corner of the ICS console UI:

11. Click on New Integration button and select “Map Data” option on the following window.

Page 7 of 35
12. Enter the following information into the New Integration Information dialog box:

Field Enter

Integration Name Hello World <ClassId> <StudentId>

e.g. Hello World 06 29

Identifier Nothing to enter.

Automatically generated from the integration

name: ex: 06_29_HELLO_WORLD

Version Nothing to enter.

Use the default value of 01.00.0000

Page 8 of 35
13. Click on the Create button.
14. Drag the “Greetings <ClassID> <StudentID>” (e.g. Greetings 06 29) SOAP connection icon over the trigger area.

15. Fill in the Configure a SOAP Endpoint wizard page with the following information:

Field Enter

What do you want to call your connection? Greetings

Page 9 of 35
16. Click “Next”. Since there is only one “Port Type” and “Operation” they are shown selected automatically in this step.

Page 10 of 35
17. Click “Next”. Keep the default values and click “Next”. The Summary page shows the information configured till now
in the wizard.

Page 11 of 35
18. After reviewing the information click “Done”. Save your work by clicking on save icon. Exit canvas, to do next
steps.

What you have modeled serves as the web service interface for the integration flow so that external applications
can invoke this integration flow. Save and exit the integration flow.

19. Go back to the home page by click on Integration Cloud Home icon

20. Click the Designer link at the top left corner of the ICS console UI:

21. Click the Connections link

Page 12 of 35
22. Click “Create” button and select “SOAP” Adapter

23. Enter the following information into the New Integration Information dialog box:

Field Entry

Connection Name Say Hello <ClassId> <StudentId>

e.g. SayHello 06 29

24. Specify the email address as [email protected]

25. In the “Connection Properties” section click on “Configure Connectivity” button and specify the WSDL URL and click
“OK”.
Get the HelloWorld Service WSDL URL from the Integration Labs Environment Details page.

Your configuration section should look something like below:

26. In the “Security” section click on “Configure Security” button. Select the Security Policy as “No Security Policy” and
Click OK.

Page 13 of 35
27. Click on “Test” at the top right corner and click on Test button again on Confirmation window. If the connection is
tested successfully you will observe the connection completion shows up as 100%. Also you will observe a message
“The connection test was successful”.

Click “Save” and “Close”.

28. Now click on Integrations, click on “Hello World <ClassID> <StudentID>” (e.g. Hello World 96 06)Integration flow.

Page 14 of 35
29. Now search for “Say Hello <ClassID> <StudentID>” (e.g. Say Hello 06 29) connection in the Connections palette.
Drag and drop the “Say Hello 06 29” connection on to the invoke/target side of the integration flow.

30. Provide value for “What do you want to call your endpoint?” as “SayHello”.

31. Click on Next. Select the “Say Hello” operation as shown below.

Page 15 of 35
32. Click on Next and click Next. The summary page shown as below.

Page 16 of 35
33. Click on Done. After Configuring SOAP connections on trigger/source and Invoke/Target side your Integration Flow
should look something like this

This invoke/target SOAP Service is a web service endpoint – typically you will be using to connect to SaaS or on-
premises applications with which you want to integrate.
34. Next, map the message received from the trigger/source to a form that the invoke/target web service understands.
This is achieved through data mapping. To model this click on the Request Mapping button to invoke the mapper.

35. Map the following trigger/source field to the corresponding invoke/target field.

Trigger/Source Field Invoke/Target Field

GreetRequest/FirstName sayHello/name

36. Drag the trigger/source field over the invoke/target field, aligning the text of the trigger/source field with the text of
the invoke/target field. When the mapping is successful, the UI looks like this:

37. Click on Validate and click on Close to close the mapper.

Page 17 of 35
38. Map the response message. Click on the Response Mapping button to invoke the mapper.

39. Map the following trigger/source field to the invoke/target field.

Trigger/Source Field Invoke/Target Field

sayHelloResponse/sayHelloReturn GreetResponse/Greeting

40. Drag the trigger/source field over the invoke/target field, aligning the text of the trigger/source field with the text of
the invoke/target field. When the mapping is successful, the UI looks like this:

41. Validate the map and Close the mapper.

Page 18 of 35
42. After configuring the mapping of objects, it should appear as below.

43. Save the Integration

44. Configure the Business Identifier to track your message. Click on Actions menu(below Save option) and click on
Tracking menu item.

45. Drag and Drop the FirstName to the Tracking Field column, as shown below.

46. Change the name for the tracking field, if required. Click Done.

47. Note that Flow Progress Indicator shows that the integration is 100% complete.

Page 19 of 35
48. Click Save and click on Close.

49. Observe that integration status is shown as “Pending Activation”. That means the flow is ready for the activation.

50. Click the toggle button to activate the integration.

51. Select the option “Enable tracing” and “include payload” options for the detail log.

52. Note that the integration status is shown as “Active”.

Page 20 of 35
53. Click on the Info icon to verify that the Generic Web Service inbound SOAP endpoint is up and running. Note that

The endpoint URL you see may be different from what you see below. Please copy this URL to use in testing the ICS
endpoint using SOAP UI.

Steps for SOAP UI Test:

1. Create a SOAPUI project using the above end point URL of the ICS service.
a. Launch SOAP UI tool, create new SOAP project.

b. Provide the project name and the endpoint URL you have copied in the previous step. Click on OK, this
should create a client project that will trigger ICS flow.

Page 21 of 35
c. Expand HelloWorldGreeting-bindingGreeting>Request1

Update the value for FirstName.

d. Now you should add basic authentication using credentials. Select Auth tab in the Request1 window. Select
Add New Authorization option.

Page 22 of 35
e. Select Basic from the pop-up dialog box. Click OK.

f. Provide ICS authentication credentials respective to Username and Password.

g. Right click on the request pay load area and select “Add WSS UserName Token” option. Select “Specify
Password Type” to Password Text.

Page 23 of 35
 This should add WSS security header to the soap request, it should appear as below.
h. Right click on the request payload area and select “Add WS-Timestamp”. Provide a value for e.g. 10000.

Page 24 of 35
 i. Test the service. Click on button and execute the request. You should see a response as below.

Summary
This lab guided you through the process of creating your first integration flow using Integration Cloud Service. The lab
introduced you to the ICS user interface and guided you how to:

 Create a an integration flow

 Integrate with a SOAP-based web services
 Map elements between trigger/source and invoke/target elements
 Activate and test the integration

Page 25 of 35
Enrich Hello World Integration Flow

Objective
In this lab, you will customize the HelloWorld integration flow to enrich the response message. You will be adding
timestamp details to the response message.

Clone an Integration
You are ready to clone the Hello World integration you have created. Cloning an integration flow creates a new copy
with identical connections and data mappings. You give the cloned integration a new name and version number, but the
remaining configuration is same. You can customize the cloned integration after you create it.

1. From the menu, select Clone.

The Clone Integration dialog is displayed.

2. Provide a different name and version number from the initial integration, and click Clone.

Field Enter

Integration Name Hello World Enrichment 96 06

Identifier Nothing to enter.

Automatically generated from the integration name:

HELLO_WORLD_ENRICH_96_06

Version Enter, a different version number. For example, if you

enter 2, the value is automatically changed tod
02.00.0000 to follow the required naming
convention.

Package Name

Description This test case will demonstrate how

to clone a completed integration.

The dialog looks as follows:

Page 26 of 35
The cloned integration is displayed at the top. Note that it is not activated.

Page 27 of 35
 3. Click the integration to begin customizations. For this example, we will add response enrichment to the
integration flow.

Add Enrichment to the Cloned Integration

1. If the Technologies palette is not displayed on the far right, click the Show Palette icon.

2. From the Technologies palette, drag the “Say Hello <ClassId> <StudentId>” (e.g. Say Hello 06 29 SOAP

Connection) on to the icon response arrow.

Page 28 of 35
 The dialog is displayed for creating the enrichment response SOAP web service.
3. Provide the following information and click Next.
Field Enter

What do you want to call your endpoint? AddVisitTimeDetails

4. Select “visitTimeStampDetails” operation, click Next, Click Next and Done.

Page 29 of 35
 You will get a message “This will invalidate any impacted mapping(s). Are you sure you want to continue?”
Select Yes and proceed further.

The integration flow looks as follows.

5. Click Save.

Map Data Between

1. Click the Response Enrichment Mapping icon between the trigger/source and invoke/target to invoke the
mapper.

2. Map the following source field to the invoke/target field.

Trigger/Source Field Invoke/Target Field

sayHelloResponse > SayHelloReturn visitTimestampReq > reqMsg

Drag the trigger/source field over the invoke/target field, aligning the text of the trigger/source field with the
text of the invoke/target field. If the mapping is successful, the UI looks like this:

Page 30 of 35
3. Click Validate, then click Close. The Response Enrichment Mapping icon is displayed in green, indicating that it
has been configured.

4. Click the Response Mapping icon and delete the old mapping.(If the mapping was not deleted in previous step)

5. Click the Response Mapping icon to invoke the mapper again. This mapper requires updates because of the
enrichment response mapping you performed.

6. Map the following trigger/source field to the invoke/target field.

Trigger/Source Field Invoke/Target Field

$ResponseEnrichmentApplicationObject > HelloResponse > Greeting

Page 31 of 35
 visitTimestampResp > respMsg

Drag the trigger/source field over the invoke/target field, aligning the text of the trigger/source field with the
text of the invoke/target field. If the mapping is successful, the UI looks like this:

7. Click Validate , then click Close. The Response Mapping icon is displayed in green, indicating that it has been
configured.

8. Click Save and then click on Close.

9. Click the toggle button to activate the integration.

10. Select the Enable tracing checkbox, select Include Payload checkbox and click Activate to confirm. As shown in
the following dialog.

Page 32 of 35
The status of the integration is changed to Active TRACE ENABLED. This will allow you to have visibility to the
message logs in the Monitoring screens as the messages are processed through ICS.

11. Click the information icon to display details about the integration. The endpoint URL listed here is required for
testing the integration.

Page 33 of 35
Test Cloned Integration
Please follow the steps that are provided in detail in Lab1. High level steps are given here…

1. Create a SOAPUI project using the above end point URL of the ICS service.
2. Create a SOAPUI project using the WSDL endpoint.
a. Edit the payload by adding value to the FirstName.
b. Add basic authentication using credentials provided to you.
c. Add Timestamp Details
d. Test the service.

Request –Response sample from SOAP UI should look like this…

Monitoring
1. Return to the Oracle Integration Cloud Service user interface.

Page 34 of 35
 2. Click Monitoring in the upper left corner. Details about the Hello World Enrichment integration are displayed
along with any other integrations you have activated:

3. Click on the Integrations link to display the integration details.

Summary
In this lab, you have learnt how to:

 Clone an integration
 Enrich a message with a SOAP web services
 Map data between the data structures of each web service

Activate and monitor the integration

Page 35 of 35