Sender instance of Siebel iWay Adapter supports the following transport protocols.
We can choose any of the above transport protocol depends on the requirement, feasibility and load of the business data. Workflow should be created if we choose any transport protocol. Business Data is being sent/receive through the workflow only. Siebel iWay Adapter supports both asynchronous and Asynchronous communication.
All the three functionalities included in the Siebel iWay Adapter to support different kind of requirements with Siebel system.
1)Advantages of File System transport protocol:
1. Allows Sequential and Parallel processing.
2. Allows Asynchronous and Synchronous communication.
3. Get the acknowledgment from target system without any BPM. For normal File adapter BPM is required to get the File Acknowledgment.
We can see other options also along with above advantages for all 3 transport protocols as mentioned in below tables.
2)Advantage of HTTP transport protocol:
We have more security features availble in this protocol which are not available in normal HTTP Adapter.
For Hyper Text Transport Protocol (HTTP), type values as defined in the following
table which lists and describes each parameter.
If we choose the ‘HTTP’ transport protocol
a) Need to supply the HTTP PORT and Synchronization TYPE only.
b) Need to provide the HTTP URL in Siebel workflow.
c) Siebel iWay Adapter for HTTP transport protocol in Sender instance directly connects to PI/XI as like the normal HTTP adapter.
3)Advantage of MQ transport protocol:
We have acknowledgement feature is available in this protocol.
For IBM MQSeries (MQ), type values as defined in the following table which lists and
describes each parameter .
and also MQ series client parameters i.e client name ,port,channel, user name ,pwd are available in this protocol as like normal JMS adapter.
Business Case for Outbound scenario:
In this example I show how the contact of the customer has been created in SAP Once it has in created in Siebel i.e, Siebel to SAP outbound interface configuration and testing.
As soon as contact has been created in Siebel, the business data is being transferred from Siebel to SAP through the interface configured in XI/PI. Here I explain with File transport protocol of sender instance of Siebel iWay adapter.
Steps in Integration Builder:
1)Import the XSD which is generated through Siebel iWay explorer under the External definitions.
For example : Shown the Equipment master XSD for example purpose.
2) Import the ZCUSOMER_CREATE IDOC from SAP under imported objects.
3) Create the message interfaces, message mapping and Interface Mapping as per the requirement.
1) Configure Integration scenario, Assign business system or business service as per the landscape.
2) Create Sender Agreement, Receiver Agreement, Interface Determination, Receiver determination as per landscape.
3) Create the IDOC adapter for receiver instance which can connect to the SAP System and assign the channel in the receiver agreement.
4) Create the iWay Siebel Adapter for Sender instance and assign it to Sender Agreement.
a) Selected the ‘File’ Transport protocol.
b) Once the contact has been created in the Siebel, the workflow in Siebel triggers and copies the data into above mentioned Polling location.
c) Adapter polls the Siebel data and send it for processing in Integration Engine (PI/XI).
1) Contact creation in Siebel System
2) We can see one Custom button “Send to SAP “in the above Siebel application. Internally Siebel workflow created under that button.
Once we enter the data in the above application , have to click the “Send to SAP” button which internally called the Siebel workflow.
3)Series of steps in workflow would be executed and copies the data into File polling location.
4) Sender Siebel XML file in SXMB_MONI.
5) Contact created in SAP system.
6) If we configure the Synchronous scenario, the following shows the Response Siebel XML.