Use Case :
This sample demonstrates how to use simple logging with a REST Adapter as a trigger in a request-response orchestrated integration. The REST Adapter is triggered when you specify a URL. A browser response is sent to you. A logging message is created and logged to the activity stream for viewing. You also track the integration and monitor message status
Knowledge : 👀
App Driven Orchestration ? : It enables you to create an integration that uses an event or business object to trigger the integration. In laymen's terms - you have to pass some inputs to trigger the app driven orchestration integrations.
Scheduled Orchestration ? : It enables you to create an integartion that uses a schedule to
trigger the integration instead of an adapter. After designing such integration, you can schedule when to run it.
- Advertisement -
Expected Input Value :
You will pass some message in place of " {message} " in URL
https://hostname:port/integration/flowapi/rest/ECHODEMO/v01/{message}
example:
https:// ion/flowapi/rest/ECHODEMO/v01/Invoking my first integration
Expected Output Value :
You will receive the following response in your browser:
{
"Message" : "Invoking my first integration.",
"Welcome" : "\"Welcome to OIC!!! Echo was successful.\""
}Lets see the development steps in detail :
Step 1: Go to your oracle integration home page & click on Integration
Step 2: Click on create button
Step 3: Select App Driven Orchestration integration pattern.
Step 4: Enter the below information and click Create button
Step 11: Enter the logger Name & click Create
Step 14:
Drag and drop *message from source to target and mapped it with *Message .
Step 15.1:
Drag and drop the *message from source to primary tracking field and click Save.
Step 2: Click on create button
Step 3: Select App Driven Orchestration integration pattern.
Knowledge : 👀
App Driven Orchestration ? : It enables you to create an integration that uses an event or business object to trigger the integration. In laymen's terms - you have to pass some inputs to trigger the app driven orchestration integrations.
Scheduled Orchestration ? : It enables you to create an integartion that uses a schedule to
trigger the integration instead of an adapter. After designing such integration, you can schedule when to run it.
- Advertisement -
Step 4: Enter the below information and click Create button
- What do you want to call your integration?[*mandatory] : Enter integration name of your choice (ex:EchoDemo)
- What does this integration do? [not mandatory] : Write a meaningful description so that other can understand the integration.
- Which package does this integration belong to? [not mandatory] : Enter a new or existing package name in which to place your integration.
Knowledge : 👀
Packages ? : You can group one or more integrations into a single structure called a package to easily import and export them to and from OIC service. Packages being optional, integration do not be a part of them. At least one integration is needed for a package to exist.
Step 5:
Click on "+" sign and select "Sample REST Endpoint". If this sample REST Endpoint connection is not showing then you can access this blog to know how to create this connection.
- Advertisement -
Step 6:
REST Endpoint configuration wizard will open. Enter the below information & click Next
- What do you want to call your endpoint?: Enter name of your choice (ex:echoRequest)
- What is the endpoint's relatives resource URI? : Enter "/{message}" (as show in below image). Hear {message} acts as dynmic input variable which value we will update while running the integration.
- Select any option that you want to configure: select the two options as show in below image
- click Next
Step 7: Skip this page, just click Next
- Advertisement -
Step 8:
Enter the below information and click Next
Enter the below information and click Next
- Select the response payload format: JSON Sample
{"Message":"","Welcome":""}
Sample JSON |
Step 9: REST adapter configuration completed, click Done
Step 10: Now click on " + " icon and search for Logger. Select the Logger icon
Knowledge : 👀
Logger ? : It Enables you to add log messages to the activity stream and diagnostic logs.- Advertisement -
Step 11: Enter the logger Name & click Create
Step 12: Enter the below information
- Log : select "Always" option [as shown in below image]
- Logger Message: click on edit button and drag and drop the *message from source(left side) to Expression (right side) as shown in below image and click validate and close it.
again click Validate and close.
- Advertisement -
Step 13: Now click on Edit button of map icon as shown in below image
Knowledge : 👀
Map ? : It Enables you to add ad-hoc mappers to the integration.Step 14:
Drag and drop *message from source to target and mapped it with *Message .
After this click on *Welcome to edit and enter some comment and then click on Save.
[Please see the below images for your reference]
Step 14.1: click on validate and close.
- Advertisement -
Step 15:
Now the last step is to configure the tracking. For this, in the upper right corner click the hamburger menu as shown in the below image.
Knowledge : 👀
Assigning Business Identifiers for Tracking Fields ? : Business identifiers enable you to track payload fields in messages during runtime.You must assign business identifiers before you can activate an integration.Step 15.1:
Drag and drop the *message from source to primary tracking field and click Save.
Step 16:
Click on Save and then close , your Sample Echo Integration is ready to Test.
to test this integration, please see the next blog
Very clear step wise instructions. Thanks for the much needed help. :)
ReplyDeleteWelcome KK:)
DeleteGreat! Very Helpful.
ReplyDeleteThanks Sushma :)
DeleteVery Good Explanation!!!
ReplyDeleteThanks
DeleteVery Good Explanation
ReplyDeleteThank You !
DeleteAmazing tutorials.
ReplyDeleteThanks KP :)
Deletecool brother
ReplyDeleteThanks Shehzad :)
Deleteit is explained so nicely and tips at each step is just what i needed :) thanks...great blog
ReplyDeleteThank You Meera for appreciating my work :)
Delete