Problem: Plain J2SE Adapter Engine

[Former Member]

Hello,

I have installed the Plain J2SE Adapter Engine.

On the Adpater Engine running a SOAP Adapter.

When i try to test the Adapter i become following error Message:

java.net.ConnectException: Connection refused: connect

at java.net.PlainSocketImpl.socketConnect(Native Method)

at java.net.PlainSocketImpl.doConnect(Unknown Source)

at java.net.PlainSocketImpl.connectToAddress(Unknown Source)

at java.net.PlainSocketImpl.connect(Unknown Source)

at java.net.Socket.connect(Unknown Source)

at java.net.Socket.connect(Unknown Source)

at java.net.Socket.<init>(Unknown Source)

at java.net.Socket.<init>(Unknown Source)

at com.sap.aii.messaging.net.ClientHttpImpl.call(ClientHttpImpl.java:146)

at com.sap.aii.messaging.adapter.SinglePayloadClient.doPost(SinglePayloadClient.java:222)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.aii.messaging.adapter.Zone.service(ModuleGUIBrowserEngine.java:1073)

at com.sap.aii.messaging.adapter.HTTPRequest.run(ModuleGUIBrowserEngine.java:371)

any idea?

Regards,

Robin

[stefan_grube · Accepted solution]

Hi Robin,

could you post the SOAP Adapter module settings?

Do you want to call a WebService from XI or do you want to use the SOAP Adapter as WebService for a local client?

Are all URLs correct? Do you need a proxy server? Are all User and Password for WebService, Proxy Server and XI set correctly?

Stefan

[Former Member · Accepted solution]

Hi Stefan,

SOAP Adapter module settings:

-

---

1. Bubble adapter java class

classname=com.sap.aii.messaging.adapter.ModuleBubble

#

1. This adapter instantiates a bubble bag for supporting

2. a xmb web service gateway. A bubble bag is a collection of Bubble

3. instances that form some processing chain of message objects.

#

1. Below parameter Bubble.Helper specifies the helper class that implements

2. the ModuleBubbleHelper interface. This class is used to instantiate

3. a bubble bag for this adapter.

#

#

1. Sets the bubble module helper that can instantiate your bubble bag

Bubble.Helper=com.sap.aii.messaging.adapter.ModuleBubbleHelperXMBWSImpl

#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

1. Below this line are the parameters specific to the ModuleBubbleHelperXMBWSImpl

#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

2. The configuration of this helper class is divided in two parts. The first part

3. specifies the adapter configuraton for Web-Service clients communicating with an

4. XMB server. The second part specifies the configuration for XMB clients

5. communicating with a WebService server. Either one or both parts can be configured

6. in a single configuration file.

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

1. Keeps the XMB headers in web service messages

XMBWS.KeepHeaders=true

1. Keeps the attachments in web service messages

XMBWS.KeepAttachments=false

1. Encodes the xmb headers into a special HTTP header string x-xmb_ws_encoded

XMBWS.UseEncoded=false

1. Part 1 (FromWS) : WS clients to XMB server ######

1. The target URL of XMB broker, to which the adapter sends XMB messages.

XMB.TargetURL=http://netweaver:8000/sap/xi/engine?type=entry

1. The port and path where the adapter waits for web service messages from clients.

XMBWS.WSPort=4444

XMBWS.WSPath=/soap/start

1. The following XMB attributes are used to fill default XMB messages.

XMB.SenderBusinessSystem=MOS_BS

XMB.SenderInterfaceNamespace=ns:moskau

XMB.SenderInterfaceName=MOSOut

XMB.QualityOfService=BE

-

---

now i have an other error message.

-

---

com.sap.aii.messaging.net.TransportException: HTTP 500 Internal Server Error

http-Response:

content-type: text/xml

content-length: 349

content-id: <soap-048c50d06eb911d9a8b6dabc0ab4bf68@sap.com>

<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Body><SOAP:Fault><faultcode>SOAP:Server</faultcode><faultstring>com.sap.aii.messaging.srt.BubbleException: Can't call the endpoint; Exception raised by com.sap.aii.messaging.net.TransportException: Content-Type not set</faultstring></SOAP:Fault></SOAP:Body></SOAP:Envelope>

at com.sap.aii.messaging.net.ClientHttpImpl.call(ClientHttpImpl.java:337)

at com.sap.aii.messaging.adapter.XMBTestClient.doPost(XMBTestClient.java:236)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.aii.messaging.adapter.Zone.service(ModuleGUIBrowserEngine.java:1073)

at com.sap.aii.messaging.adapter.HTTPRequest.run(ModuleGUIBrowserEngine.java:371)

-

---

[stefan_grube]

So you want to use the SOAP Adapter as Webservice and send data from a local client to XI.

In your configuration, User, Password and Client of the XI system are missing.

In XI 2.0 the config would be:

XMB.TargetURL=http://netweaver:8000/sap/xi/engine?type=entry

XMB.User=YourUser

XMB.Password=YourPassword

XMB.Client=YourClient

XMBWS.WSPort=4444

XMBWS.WSPath=/soap/start

XMB.SenderBusinessSystem=MOS_BS

XMB.SenderInterfaceNamespace=moskau

XMB.SenderInterfaceName=MOSOut

XMB.QualityOfService=BE

In XI 3.0 you would have:

XI.TargetURL=http://netweaver:8000/sap/xi/engine?type=entry

XI.User=YourUser

XI.Password=YourPassword

XI.Client=YourClient

XMBWS.WSPort=4444

XMBWS.WSPath=/soap/start

XI.SenderService=MOS_BS

XI.SenderInterfaceNamespace=moskau

XI.SenderInterfaceName=MOSOut

XI.QualityOfService=BE

XI.ContentType=text/xml

Stefan

[Former Member]

Now my config like yours for xi 3.0

But now i become always a java.lang.NullPointerException when i try to test the Adapter.

-

---

version=30

1. Bubble adapter java class

classname=com.sap.aii.messaging.adapter.ModuleBubble

#Bubble Helper class

Bubble.Helper=com.sap.aii.messaging.adapter.ModuleBubbleHelperXMBWSImpl

XI.TargetURL=http://netweaver:8000/sap/xi/engine?type=entry

XI.User=****

XI.Password=****

XI.Client=010

XMBWS.WSPort=4444

XMBWS.WSPath=/soap/start

XI.SenderService=MOS_BS

XI.InterfaceNamespace=moskau

XI.InterfaceName=MOSOut

XI.QualityOfService=BE

XI.ContentType=text/xml

-

---

Is there anything to config on XI 3.0 or have i forgotten anything?

Regards,

Robin

[stefan_grube]

Could you please describe the whole scenario? How do you call the SOAP Adapter? Where do you get the error message? Is it inside the adapter? Is there any message in the XI? Where should the message go to?

[Former Member]

[Client(WFETCH)] -> Sends SOAP Messages -> [Plain J2SE Adapter (SOAP)] -> Sends SOAP Messages -> [SAP XI 30]

When in the Config file "XMB.TargetURL=http://netweaver:8000/sap/xi/engine?type=entry" stand, than i become the response "<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Body><SOAP:Fault><faultcode>SOAP:Server</faultcode><faultstring>com.sap.aii.messaging.srt.BubbleException: java.lang.ArrayIndexOutOfBoundsException: 0 >= 0</faultstring></SOAP:Fault></SOAP:Body></SOAP:Envelope>"

When in the Config file Stands "XI.TargetURL=http://netweaver:8000/sap/xi/engine?type=entry" stand, than the wfetch become the error: "no socket connected"

In XI no messages arrived.

[stefan_grube]

The configuration seem to be correct now. Check, if you have the correct port number 8000, maybe you need a full qualified server name instead of netweaver. What happens, if you type the URL in your browser adress field? Can you ping the server, where the XI is installed?

[Former Member]

When i type the url in my browser, i see following xml message:

-

---

SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP:Header />

- <SOAP:Body>

- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<faultcode>SOAP:Client</faultcode>

<faultstring>Empty HTTP request received</faultstring>

<faultactor>http://sap.com/xi/XI/Message/30</faultactor>

- <detail>

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIProtocol</SAP:Category>

<SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>.........

-

---

I also can ping the XI Server which is in the same local network like "XI 3.0 Adapter Engine Standalone Version"

Is there anything else i have to configure before i see the messages in XI Monitoring ?

[Former Member]

With Support Package 10 for XI CONNECTIXITY SE 3.0 the Problem solved.

Thank you Stefan for your help.

Regards,

Robin

[stefan_grube]

Now I know, I have to ask for the support package first

Cheers

Stefan