cancel
Showing results for 
Search instead for 
Did you mean: 

Invoking a Web Service using XI 2.0

Former Member
0 Kudos

Hi all,

I am attempting to create a scenario where an SAP application invokes a web service through XI 2.0.

I have created an ABAP proxy to allow my ABAP to start the call process and have set up the message interfaces within the Integration Directory.

I want XI to receive a call from this proxy and then act as the client to an existing Web Service.. calling it and bringing back a response... but it doesn't look like I can import the existing WSDL as a I would have expected.

So... instead I have exported the Message Interface for the "out of XI" portion of the interface as a WSDL and have asked the Web Service provider to amend their service according to this XI generated WSDL.

My difficulty now is how to use the SOAP adapter. Within the Integration Directory I presumably need to define the endpoint with XI Connectivity but I am not sure how to fill in the URL address of the SOAP adapter...

Any help on how to configure the actual SOAP adapter to fulfill this requirement would be great too.

I have looked around the boards to see if I could work this out from previous posts but without success so far.

It's a synchronous scenario and basically should look like...

ABAP Proxy->XI->SOAP Adapter->Web Service->XI->ABAP Proxy

Many thanks,

Gordon

Accepted Solutions (0)

Answers (2)

Answers (2)

stefan_grube
Active Contributor
0 Kudos

Hi Gordon,

here is an example for SOAP-Adapter config:

# Bubble adapter java class
classname=com.sap.aii.messaging.adapter.ModuleBubble

#
# Sets the bubble module helper that can instantiate your bubble bag
Bubble.Helper=com.sap.aii.messaging.adapter.ModuleBubbleHelperXMBWSImpl


###### Part 0 (FromWS and ToWS) : common part ######

# Keeps the XMB headers in web service messages
XMBWS.KeepHeaders=false

# Encodes the xmb headers into a special HTTP header string x-xmb_ws_encoded
XMBWS.UseEncoded=false

# The target URL for the web service, to which the adapter sends web service messages.

# The address is part of the WSDL

XMBWS.TargetURL=http://www.extensio.com:8080/ExtensioInfoServer/servlet/rpcrouter

# Proxy configuration from SAP

XMBWS.proxyHost=PrOxY
XMBWS.proxyPort=8080


# The port and path where the adapter waits for XMB messages from clients.
XMBWS.XMBPort=8400
XMBWS.XMBPath=/soap/stockquote

# The default SOAPAction HTTP request header to the web Service server

# The SoapAction is part of the WSDL

XMBWS.DefaultSOAPAction=

Of course you have to set URL, proxy and SOAP-action to your belongings.

You define the endpoint as:

"http://<Adapter-Server>:<XMBPort><XMBPath>"

in this example:

"http://localhost:8400/soap/stockquote"

Stefan

Former Member
0 Kudos

hey gordon...

this wud help..

1. Invoke web services using sap Xi…

/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi

Look through these blogs:

/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services

(Xi exposed webservices)

/people/sriram.vasudevan3/blog/2005/03/18/points-to-ponder-over-while-considering-webservices-implementations-vis-a-vis-eai

(web service implmentation)

/people/siva.maranani/blog/2005/05/23/communication-between-sap-system-webservice-using-proxies

(commn between sap and web sevices using proxies)

and

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

regards...

vishal