How to Invoke a RESTful Web Service from Siebel: Part 1
Siebel EAI offers a flexibility to setup Outbound / Inbound communication using real time Web Services between Siebel and another external system. These real time Web services can be based on SOAP or REST architecture.
We would try to figure out the pros and cons of implementing the requirement using SOAP or RESTful architecture in next article. The evident fact is that even Oracle Fusion Middleware is deploying Siebel RESTful Webservices using SAI.
Browsing the significance of this fact, I would guide you through the steps of invoking an external system published RESTful Webservice through Siebel and it would work with any version of Siebel. If you want an external system to invoke Siebel published RESTful Web services, you need to apply a patch and it would work on 126.96.36.199, QF0135 & distributed generally as ACR 599.
The requirement is to invoke the published external system webservice URL from Siebel. URL will carry additional arguments i.e.siebel data values.
A Web Service response will be received and the data will accordingly update back Siebel database.
The first step and the tricky part is to form the URL dynamically in Siebel.
Let us take the example to understand the requirement.
For example: Assuming I am in Action BC and I need to pass the data to external system through a standard URL as soon as activity status is set as Active.
The External System accepts the below standard URL from Siebel
All parameters in above URL is the data dynamically populated at run time.
To implement this part of the requirement follow the below steps:
Go to Administration-RunTimeEvents – > click on Action Sets Link
Create a new Action set as below:
Configure the more info applet as below:
Put the value property as:
“http://www.sigmadynamics.com/schema/services/DecisionService/insert?”+”ROW_ID=”+[Activity Id]+”&PROD_ID=”+[Act Product Id]+”&AGREE_ID=”+[Agreement Number]+”&PROD_CODE=”+[Product Code]+”&ACT_DESCRIPTION=”+[Description]+”&ACT_ST_DATE=”+[Start Date]+”&ACT_EN_DATE=”+[End Date]+”&ACT_STATUS=”+[Status]
Value enclosed in  are the actual BC field names.
The above value property will help your construct the URL dynamically at run time.
Now this URL value will be stored in a profile attribute called “URL” and used later as a parameter in EAI HTTP Transport vanilla Business Service.
The next post will follow the use of this URL profile attribute to invoke the external system webservice.