To Import XSD file along with WSDL file in ED

[Former Member]

Dear All,

I am doing a scenario web service1 —XI—RFC—web service2. Web service1 sends request to XI and XI sends to RFC and RFC response to web service2 and web service2 response (acknowledge) back to XI and XI sends back to web service1.

My client (web service2) has given me the web service (WSDL) file along with XSD file.

In the wsdl file there are number of elements and complex types.

<xs:element name="GetCustomer">

<xs:complexType>

<xs:sequence>

<xs:element name="authentication" type="xx:AuthInfo"/>

<xs:element name="CompanyName" type=" xx:AuthInfo "/>

</xs:sequence>

</xs:complexType>

</xs:element>

The type (xx:AuthInfo and xx:AuthInfo) are defined in XSD file.

My questions are

1) Do I have to import the XSD file in ED or not.

2) How do I map this XSD

3) As WS1, RFC and WS2 all are synchronous MT do I have to use BPM for it.

4) Can some one help with any docs please..

Thanks in advance

[former_member187339]

Hi,

>>Do I have to import the XSD file in ED or not

If you are having the wSDL files then you can take the structure from there itself. Just import the wsdl files in IR. You can also use XSD.

>>How do I map this XSD

XSD are same as Message Types. So create a MM and choose your XSD.

>>As WS1, RFC and WS2 all are synchronous MT do I have to use BPM for it.

Yes you have to because you are taking the responce from RFC and going to give it to WS2.

BPM steps:

1) receive (open sync bridge)

2) transformation 1

3) send (snyc)

4)transformation 2

3) send (close sync bridge)

https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken]

Regards

Suraj

[Former Member]

I'm not sure I fully understand the question that you are asking, but you certainly can import the XSD file as an external definition to make life easier.

Namespace -> Interface Objects -> External Definitions : Create new

You can then import the XSD file. In order to map, you need to create a message mapping and define your source and target message. Here is a good blog on mapping:

/people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping