cancel
Showing results for 
Search instead for 
Did you mean: 

XI SOAP adapter vs webservice testing tools

Former Member
0 Kudos

Actually I have creted simple xslt mapping and managed to come up with exactly in the format of endpoint request format of the webservice.

here is the payload( I have created the SOAP Envelop, Header and body in the payload)

<?xml version="1.0" encoding="utf-8"?>

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:eb="http://www.ebxml.org/namespaces/messageHeader" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsd="http://www.w3.org/1999/XMLSchema">

<SOAP-ENV:Header>

<eb:MessageHeader SOAP-ENV:mustUnderstand="1" eb:version="1.0">

<eb:ConversationId>sucesss</eb:ConversationId>

<eb:From>

<eb:PartyId type="urn:x12.org:IO5:01">applevac.com</eb:PartyId>

</eb:From>

<eb:To>

<eb:PartyId type="urn:x12.org:IO5:01">webservices.sabre.com</eb:PartyId>

</eb:To>

<eb:CPAId>P4XC</eb:CPAId>

<eb:Service eb:type="sabreXML">session</eb:Service>

<eb:Action>SessionCreateRQ</eb:Action>

<eb:MessageData>

<eb:MessageId>mid:20001209-133003-2333@applevac.com</eb:MessageId>

<eb:Timestamp>2001-02-15T11:15:12Z</eb:Timestamp>

<eb:TimeToLive>2001-02-15T11:15:12Z</eb:TimeToLive>

</eb:MessageData>

</eb:MessageHeader>

<wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/12/secext" xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/12/utility">

<wsse:UsernameToken>

<wsse:Username>5555</wsse:Username>

<wsse:Password>password</wsse:Password>

<Organization>L5x5</Organization>

<Domain>DEFAULT</Domain>

</wsse:UsernameToken>

</wsse:Security>

</SOAP-ENV:Header>

<SOAP-ENV:Body>

<eb:Manifest SOAP-ENV:mustUnderstand="1" eb:version="1.0">

<SessionCreateRQ>

<POS>

<Source PseudoCityCode="P4XC"/>

</POS>

</SessionCreateRQ>

</eb:Manifest>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

I want XI to post just the payload and nothing else so....

I selected Do not use envelope in the adapter configuration because we have every thing( SOAP envelop, header and body in the payload) but it is not working as i am still getting the same error message before implementing this xslt.

Error Message:

<StackTrace>com.sabre.universalservices.base.session.SessionException: errors.session.USG_CONVERSATION_ID_REQUIRED at com.sabre.universalservices.gateway.control.SecurityInterceptor.executeOnRequest(SecurityInterceptor.java:116) at com.sabre.universalservices.base.interceptor.Interceptor.execute(Interceptor.java:113) at com.sabre.universalservices.base.interceptor.InterceptorChain.applyInterceptors(InterceptorChain.java:32) at com.sabre.universalservices.base.interceptor.InterceptorManager.process(InterceptorManager.java:121) at com.sabre.universalservices.gateway.control.WSGateway.onMessage(WSGateway.java:415) at com.sabre.universalservices.gateway.control.WSGateway.handleRequest(WSGateway.java:313) at com.sabre.universalservices.gateway.control.WSGateway.doPost(WSGateway.java:247) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter

Do you have any idea like XI will add anything to this pay load when it sends out to the webservice?

If i take the payload from the XI and try it in SOAPUI(tool to test webservice, you would know it already ) it works fine, I mean I was able to get the proper response but in XI it does not work.

Any help in this regards is highly appreciated.

we are using PI 7.0 and SP 9.

Message was edited by:

Venkat Marni

Message was edited by:

Venkat Marni

Accepted Solutions (0)

Answers (1)

Answers (1)

MichalKrawczyk
Active Contributor
0 Kudos

Hi,

>>>>com.sabre.universalservices.base.interceptor.

but this error does not come from XI... (from SOAP adapter)

so it has nothing to do with

check out this com.sabre application that you use

Regards,

michal

Former Member
0 Kudos

Thanks michal.

You are right the error is not coming from XI. But the actual problem is if I send the same payload using SOAPUI I am able to see the proper response message where as I get this error message when I send it thru XI.

So what I am suspecting is there may be some extra parameters/values (may be soap header, envelope etc) have been added to payload by SOAP adapter even though I selected "don't use SOAP envelope" in the adapter configuration.

where can I see the complete message after the receiver SOAP comm channel call, meaning just before leaving adapter and entering into SABRE(provider) landscape/internet.

Thanks,

Venkat

Former Member
0 Kudos

Hi,

Finally I could solve the problem.

I was actually trying to post the information from the http client at the sender and receiver side I am getting the error.

Later i have actually created the webservice for my sender interface in XI then post the info using the SOAPUI(3rd party tool) to post the info to XI and then Xi will communicate the webservice using SOAP adapter then I got the proper response from the webservice.

In this whole episode I guess there is some thing wrong in using a htp client but technically we should be able to use http client as XI will take the payload and use xslt mapping to come up with target interface soap message( but i do not know why XI failed in that).

thanks for all your help and hope this is clear.

thanks,

Venkat