Skip to Content

Introduction of Siebel iWay Adapter

Introduction of  Siebel iWay Adapter – PART1 – PART1

Sender instance of Siebel iWay Adapter and about its protocols 

Sender instance of Siebel iWay Adapter  – PART2 – PART2 

This blog is presented about the reciver instance of Siebel Adapter and its protocols.

It supports the following transport protocols.

1) Siebel JDB (Java Data bean connection)

2) File

3) HTTP

4) MQ

We can choose any one of the above transport protocol depends on the requirement. Workflow should be created if we choose any transport protocol except Siebel JDB protocol.

 Siebel JDB protocol behaves differently when compare to remaining 3 protocols. This protocol is available in only receiver instance of Siebel iWay Adapter. This protocol can update the Siebel database directly. No need to create the Workflow in Siebel system.

For *Siebel Java Data Bean (JDB), *type values as defined in the following table, which

lists and describes each parameter.

JDB

For File System, type values as defined in the following table which lists and describes

the parameter.

File

For MQ Series, type values as defined in the following table which lists and describes

the parameters.

MQ

For Hyper Text Transport Protocol (HTTP), type values as defined in the following

table which lists and describes the parameter.

HTTP

<u>Business case for Inbound Interface :</u>

In this example I explain how the Asset information is created in Siebel Application.

Asset information is being sent from Legacy system. As soon as File posted in the polling location, Asset information is going to be updated in Siebel Application using configured PI/XI inbound interface.

I explain the same interface with different protocols (JDB, File, and HTTP).

<u>Steps in Integration Repository:</u>

1) Legacy system data structure.

File_DT

2) Generated schema through Application Explorer for Siebel Business Object (Asset-insert).

!https://weblogs.sdn.sap.com/weblogs/images/36503/ReceiverXSD.jpg|height=300|alt=ReXSD|width=578|src=https://weblogs.sdn.sap.com/weblogs/images/36503/ReceiverXSD.jpg|border=0

3)   Message mapping between sender file structure and Siebel receiver structure.

Map

4) Create the outbound and Inbound Interfaces and Interface Mapping.

<u>Steps in Integration Directory :</u>

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 File adapter for sender instance and assign the channel in the sender agreement.

4) Create the iWay Siebel Adapter for Receiver instance.

<u>i) Using JDB Connection Transport protocol :</u>

JDB

<u>ii) Using File transport protocol </u>

File

<u>iii)Using HTTP Transport protocol:</u>

HTTP

<u>Testing:</u></p><p><u>1) XML File in Legacy System</u>:</p><p><? Xml version=”1.0″ encoding=”UTF-8″?></p><p><ns0:Equipement_File_MT xmlns:ns0=”http://EqipmentDetails_Creation“></p><p>   <Asset>00000000010000334</Asset></p><p>   <Product>300000004</Product></p><p>   <Serial_Number>TGF1111</Serial_Number></p><p>   <Sold_to_Party_Owner>10000001</Sold_to_Party_Owner></p><p>   <status>AVLB</status></p><p></ns0:Equipement_File_MT></p><p> </p><p>2) Created the Asset in Siebel application. </p><p>!https://weblogs.sdn.sap.com/weblogs/images/36503/Siebel%20Appl.jpg|height=227|alt=sei|width=573|src=https://weblogs.sdn.sap.com/weblogs/images/36503/Siebel%20Appl.jpg|border=0!</p><p> </p><p>3) Response XML from Siebel if we configure synchronous interface.</p><p>!https://weblogs.sdn.sap.com/weblogs/images/36503/ReceiverXML.jpg|height=207|alt=Response|width=551|src=https://weblogs.sdn.sap.com/weblogs/images/36503/ReceiverXML.jpg|border=0!</body>

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply