J2SE AE: SOAP

Hi, we have problem with J2SE receiver SOAP adapter. Communcation is working corect till the moment when adapter is receiving two messages per 1 second, see log:
08:44:41 (3835): Request transport message received at 8000/soaptest1
08:44:41 (3835): Request transport message received at 8000/soaptest1
08:44:41 (3836): Request message parsed
08:44:41 (3836): Request message parsed
08:44:41 (3837): Response message serialized
08:44:41 (3837): Response message serialized
08:44:41 (3838): Response transport message sent
08:44:41 (3838): Response transport message sent
The target Message Handler get message in wrong format:
<?xml version='1.0' encoding='UTF-8'?><SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header xmlns:xlink='http://www.w3.org/1999/xlink' xmlns:SAP='http://sap.com/xi/XI/Message/30' xmlns:wsse='http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd' xmlns:wsu='http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd'/><SOAP:Body><FROM_SAP_TO_CVG xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
<?xml version='1.0' encoding='UTF-8'?><SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header xmlns:xlink='http://www.w3.org/1999/xlink' xmlns:SAP='http://sap.com/xi/XI/Message/30' xmlns:wsse='http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd' xmlns:wsu='http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd'/><SOAP:Body><FROM_SAP_TO_CVG xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
<DATA xsi:type='xsd:string'>
payload message A
</DATA>
<DATA xsi:type='xsd:string'>
payload message B
</DATA>
</FROM_SAP_TO_CVG></SOAP:Body></SOAP:Envelope>
and Message Handler principle brake down.
Consolidating hardware of machine where AE is installed we didn't get better effect.
Do you have the same experince. Thanks

Hi Vladimir,
implement the newest patch for the J2SE adapter engine.
if this does not help, open an OSS ticket.
Regards
Stefan

Similar Messages

HTTP/S POST from J2SE adapter engine (NO SOAP)

Hi there,
We have a scenario at work where we have XI sending messages to the "lightweight" J2SE adapter engine in the DMZ....and from there the message is sent out to an HTTPS site that is obvioulsy outside of our network.
Currently I can see that the J2SE adapter engine support SOAP over HTTP/S......but how can I do a normal POST of the message NOT using SOAP to an external HTTP/S address?
I do not see any straight HTTP adapter in the J2SE adapter engine. I have a small java file that can connect and POST the message to the external website.
My question is how can I use this code easily in the J2SE adapter engine? I just want a simple HTTP
POST ...no SOAP.....
Is there some sort of EXIT or dispatcher that I can hook onto?
Any help or push in the right direction will be greatly appreciated
Regards
Lynton

Hi there,
You can see in the config file below that we did put it into the adapter config. It does not complain about the parameter BUT it still has the SOAP envelope / headers in the result message. Any ideas how we can get around this?
Thanks for the help
Lynton
# 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
#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
# Below this line are the parameters specific to the ModuleBubbleHelperXMBWSImpl
#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
# The configuration of this helper class is divided in three parts. The first part,
# Part 0, specifies the common parameters. The second part, Part 1, specifies the
# adapter configuraton for Web-Service clients communicating with an XMB server.
# The third part, Part 2, specifies the configuration for XMB clients
# communicating with a WebService server. For sender or inbound adapters, Part 0
# and Part 1 must be configured. For receiver or outbound adapters, Part 0 and
# Part 2 must be configured.
# This is a sample configuration file for a SOAP Outbound/Receiver Adapter
###### Part 0 (FromWS and ToWS) : common part ######
# Keeps the XMB headers in web service messages
XMBWS.KeepHeaders=false
# Keeps the attachments in web service messages
XMBWS.KeepAttachments=false
# Encodes the xmb headers into a special HTTP header string x-xmb_ws_encoded
XMBWS.UseEncoded=false
# Encodes the value of x-xmb_ws_encoded (see UseEncoded) in the request query string
XMBWS.UseQueryString=false
# Uses the specified xml encoding for the soap envelope encoding
#XMBWS.XMLEncoding=iso-8859-1
*XMBWS.NOSOAP=true*
###### Part 1 (FromWS) : WS clients to XMB server ######
# This part is configured for SOAP Sender or SOAP Inbound-Adapter)
# It is left empty in this configuraton file.
###### Part 2 (ToWS): XMB clients to WS server ######
# This part is configured for SOAP Receiver or SOAP Outbound-Adapter.
# The target URL for the web service, to which the adapter sends web service messages.
XMBWS.TargetURL=https://localhost:443
# The port and path where the adapter waits for XMB messages from clients.
XMBWS.XMBPort=8015
XMBWS.XMBPath=/bt
XMBWS.SSLcertificate=somecert.p12
XMBWS.SSLcertificatePassword=hello
XMBWS.SSLauthentication=true
# The default SOAPAction HTTP request header to the web Service server
XMBWS.DefaultSOAPAction=xmbws
# END

Standalone (J2SE) adapter - axis SOAP adapter - issue duplicate messages

All,
Perhaps you can help me. I've setup a scenario where an standalone (J2SE) adapter sends a file to SAP XI channel, configured on the central adapter engine, of type SOAP configured to use Axis servlet.
The connection is setup and the standalone adapter channel logs thre response from the SOAP channel which reads HTTP error 500, indicating a duplicate message.
SAP has identified this problem and proposes in the FAQ for Axis (note 1039369) to set on the SOAP channel module CallSapAdapter property ignoreDuplicate to true in the module processor.
I've implemented this as suggested however found the problem persists. I'm still receiving an HTTP 500 error.
Your help is much appreciated solving this problem.
Thanks
Harald

As there was a bugfix recently, make sure that you have installed the latest patch.
If this does not work, open an OSS ticket for this issue.
Stefan

Plain J2SE Adapter Engine - SOAP Adapter

Which reasons are there for using the soap adapter at the plain j2se adapter engine instead of the soap adapter at the central adapter engine (XI 3.0)? Which benefits are there? Which cases are known?

The J2SE adapter is a relict from XI 2.0
You may still use it, especially for migration from XI 2.0 to XI 3.0, but it is recommended to use the J2EE adapter engine.
Regards
Stefan

J2SE Soap Adapter

Hello Guru's,
I need to configure the SOAP adapter on the J2SE adapter plain for receiving messages. I have read the documentation about it and I need to do configure the following:
version=3.0
classname=com.sap.aii.messaging.adapter.ModuleBubble
Bubble.Helper=com.sap.aii.messaging.adapter.ModuleBubbleHelperXMBWSImpl
XMBWS.TargetURL=http://WebServiceHost:port/service-arguments
XMBWS.User=<username>
XMBWS.Password=<password>
XMBWS.DefaultSOAPAction=<default_soap_action>
XMBWS.KeepHeaders=<boolean>
XMBWS.KeepAttachments=<boolean>
XMBWS.UseEncoded=<boolean>
XMBWS.EncodingVersion=3
Specifies which version of the XI message format to use to code the message header in the HTTP header (see XMBWS.UseEncoded). The value 2 stands for the XI 2.0 message format and the value 3 stands for the XI 3.0 message format. The default value is 3.
XMBWS.UseQueryString=<boolean>
XMBWS.XMBPort=<port_no>
XMBWS.XMBPath=<path>
XMBWS.XMLEncoding=UTF-8 (standaard)
XI.AckFinal=<boolean> true / false
What I do not get is what the difference is between XMBWS.TargetURL=http://WebServiceHost:port/service-arguments and
XMBWS.XMBPort=<port_no>, XMBWS.XMBPath=<path>
Can someone explain it in other words (maybe with an example) then help.sap.com?
Hope to hear from you.
Best regards,
Guido
Edited by: G. Koopmann on Jun 24, 2008 9:04 AM

You have to distinguish between parameters starting with XI. and XMBWS.
You use the XMBWS. parameters for the direction XI -> J2SE adapter -> Webservice, the other parameters vice versa.
When you deploy (or unzip) your J2SE adapter, then you find following files in the folder: insoap and outsoap. Check them for details.
Regards
Stefan

XI 2.0 Standalone J2SE SOAP Adapter as client - SOAP:encodingStyle

Hi,
We're setting up the J2SE SOAP Adapter of XI 2.0 to talk to a synchronous web service provided by a webmethods platform.
When we generate the Request message using the WSDL and post it directly via the HTTP test tool the message is understood and a response message is returned.
Here is the Request:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <SOAP-ENV:Body>
          <m:callFP091 xmlns:m="http://destserver/FP091.flows" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
               <iw1_RECTPE xsi:type="xsd:string">String</iw1_RECTPE>
               <iw1_DLRCODE xsi:type="xsd:string">String</iw1_DLRCODE>
               <iw1_FRNCODE xsi:type="xsd:string">String</iw1_FRNCODE>
               <iw1_JOBNUM xsi:type="xsd:string">String</iw1_JOBNUM>
               <iw1_CHASIS xsi:type="xsd:string">String</iw1_CHASIS>
               <iw1_COLOUR xsi:type="xsd:string">String</iw1_COLOUR>
               <iw1_DESCRIP xsi:type="xsd:string">String</iw1_DESCRIP>
               <iw1_INVNUM xsi:type="xsd:string">String</iw1_INVNUM>
               <iw1_CAPAMT xsi:type="xsd:string">String</iw1_CAPAMT>
               <iw1_INTFRE xsi:type="xsd:string">String</iw1_INTFRE>
               <iw1_LOC_IND xsi:type="xsd:string">String</iw1_LOC_IND>
               <iw1_REGISTRATION xsi:type="xsd:string">String</iw1_REGISTRATION>
               <iw1_ENGINE_NUM xsi:type="xsd:string">String</iw1_ENGINE_NUM>
               <iw1_VIN_NUM xsi:type="xsd:string">String</iw1_VIN_NUM>
          </m:callFP091>
     </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
When we try to use the SOAP Adapter and pass it the following message from XI:
<m:callFP091 xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:m="http://destserver/FP091.flows"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" >
          <iw1_RECTPE xsi:type="xsd:string">E1</iw1_RECTPE>
          <iw1_DLRCODE xsi:type="xsd:string">3009838</iw1_DLRCODE>
          <iw1_FRNCODE xsi:type="xsd:string">333</iw1_FRNCODE>
          <iw1_JOBNUM xsi:type="xsd:string">123</iw1_JOBNUM>
          <iw1_CHASIS xsi:type="xsd:string">2</iw1_CHASIS>
          <iw1_COLOUR xsi:type="xsd:string">3</iw1_COLOUR>
          <iw1_DESCRIP xsi:type="xsd:string">4</iw1_DESCRIP>
          <iw1_INVNUM xsi:type="xsd:string">5</iw1_INVNUM>
          <iw1_CAPAMT xsi:type="xsd:string">6</iw1_CAPAMT>
          <iw1_INTFRE xsi:type="xsd:string">7</iw1_INTFRE>
          <iw1_LOC_IND xsi:type="xsd:string">8</iw1_LOC_IND>
          <iw1_REGISTRATION xsi:type="xsd:string">9</iw1_REGISTRATION>
          <iw1_ENGINE_NUM xsi:type="xsd:string">1</iw1_ENGINE_NUM>
          <iw1_VIN_NUM xsi:type="xsd:string">2</iw1_VIN_NUM>
</m:callFP091>
The SOAP adapter wraps the envelope and body around this message, provides an empty header but changes the SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" attribute to SOAP:actor='http://schemas.xmlsoap.org/soap/encoding/'.
The generated SOAP message is:
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Header/>
<SOAP:Body>
<m:callFP091 xmlns:m='http://196.11.134.83/FP091.flows'
SOAP:actor='http://schemas.xmlsoap.org/soap/encoding/'
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
          <iw1_RECTPE xsi:type='xsd:string'>E1</iw1_RECTPE>
          <iw1_DLRCODE xsi:type='xsd:string'>3009838</iw1_DLRCODE>
          <iw1_FRNCODE xsi:type='xsd:string'>333</iw1_FRNCODE>
          <iw1_JOBNUM xsi:type='xsd:string'>123</iw1_JOBNUM>
          <iw1_CHASIS xsi:type='xsd:string'>2</iw1_CHASIS>
          <iw1_COLOUR xsi:type='xsd:string'>3</iw1_COLOUR>
          <iw1_DESCRIP xsi:type='xsd:string'>4</iw1_DESCRIP>
          <iw1_INVNUM xsi:type='xsd:string'>5</iw1_INVNUM>
          <iw1_CAPAMT xsi:type='xsd:string'>6</iw1_CAPAMT>
          <iw1_INTFRE xsi:type='xsd:string'>7</iw1_INTFRE>
          <iw1_LOC_IND xsi:type='xsd:string'>8</iw1_LOC_IND>
          <iw1_REGISTRATION xsi:type='xsd:string'>9</iw1_REGISTRATION>
          <iw1_ENGINE_NUM xsi:type='xsd:string'>1</iw1_ENGINE_NUM>
          <iw1_VIN_NUM xsi:type='xsd:string'>2</iw1_VIN_NUM>
</m:callFP091>
</SOAP:Body>
</SOAP:Envelope>
This message has no SOAP:encodingStyle attribute and is therefore not understood by the WebMethods web service. Here is the error message from the web service:
[B2BCORE.0076.9201] SOAP Message Coder cannot decode message; no encoding style is specified
How do I configure the outbound SOAP adapter within the XI 2.0 J2SE adapter engine to add the SOAP:encodingStyle attribute to the outbound message?
I have tried playing around with the XMBWS.* parameters outlined in the adapter engine documentation but these don't seem to have any influence on the way the SOAP request message is formed.
Any suggestions would be appreciated.
Regards,
-Derek

Hi,
You could use the webMethods XI adapter to create the connection.
Best Regards,
Sander

How to configure Soap to RFC adapter in J2SE engine

Hello,
i want to configure a scenario using J2SE engine..
want to configure soap to rfc..
can anyone please help me out in configuring the scenario.
Thanks,
Soorya.

hi,
check the below link..
[http://help.sap.com/saphelp_nw04/helpdata/en/bf/27fd3b651f6a1ce10000000a11402f/content.htm]
[http://help.sap.com/saphelp_nw04/helpdata/en/6f/246b3de666930fe10000000a114084/content.htm]
*Reward Points its Useful*
Regards,
Prakasu

SOAP Adapter in XI 3.0 (Central Engine, not J2SE Adapter)

Hello,
I am trying to get the demo (flight availablity check) work via SOAP, so that it can be called from .NET. I created a communication channel with sender SOAP adapter (and adapter engine as Integration server, http://sap.com/xi/XI/Demo/Agency as interface namespace and FlightSeatAvailabilityQuery_Out as interface name)
When I post it to XI
http://xxxxxx:8000/sap/xi/engine?type=entry&version=3.0&Sender.Service=XX1_205&Interface=com.sap^FlightSeatAvailabilityQuery_Out&QualityOfService=BestEffort&ProcessingMode=p&MessageClass=RQ
with soapaction http://sap.com/xi/WebService/soap1.1
and
<?xml version="1.0" encoding="utf-8" ?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<FlightSeatAvailabilityQuery xmlns="http://sap.com/sapexamples">
<FlightID xmlns="">
<AirlineID>LH</AirlineID>
<FlightDate>2004-12-01</FlightDate>
</FlightID>
</FlightSeatAvailabilityQuery>
</soap:Body>
</soap:Envelope>
I get just
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
</SOAP:Body>
</SOAP:Envelope>
Any idea why this does not work. The plain HTTP adapter (to /sap/xi/adapter_plain) works ok.
Thanks
siva

Post your message to following URL:
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
port is the J2EE port 50000 in your example.
Check the newest manual for further details.
Regards
Stefan

Stupid error in J2SE Adapter !!!

Greetings,
I am trying a simple scenario sending data from my PC database to XI using J2SE JDBC Adapter (stack 09). The same problem also happen when sending file using File Adapter. I got the following error : Any help is welcome.
Wed Nov 03 08:17:19 GMT+03:00 2004 *****
08:17:19 (4209): Guaranteed Delivery database operation pending
08:17:25 (4212): JDBC adapter initialized successfully
08:17:25 (4202): JDBC adapter started
08:17:25 (4220): Sending message "a2d4a910-2b0f-11d9-a214-e9630a0e6b86" to Integration Engine... (message size: 535 bytes)
08:17:25 (4221): ERROR: Finished sending query result to Integration Engine with error "com.sap.aii.messaging.net.TransportException: HTTP 500 HTTP standard status code
http-Response:
content-type: text/xml
content-length: 1282
content-id: <[email protected]>
soapaction: 'http://sap.com/xi/XI/Message/30'
server: SAP Web Application Server (1.0;640)
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
</SOAP:Header>
<SOAP:Body>
<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsse="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" SOAP:mustUnderstand="1"><SOAP:faultcode>Client</SOAP:faultcode><SOAP:faultstring></SOAP:faultstring><SOAP:faultactor>http://sap.com/xi/XI/Message/30</SOAP:faultactor><SOAP:faultdetail><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="PARSER">ITEM_MISSING</SAP:Code><SAP:P1>/@versionMajor</SAP:P1><SAP:P2/><SAP:P3/><SAP:P4>ST: ST_XMS_MSGHDR30_MAIN</SAP:P4><SAP:AdditionalText>Attribute 'versionMajor' expected</SAP:AdditionalText><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>XML tag /@versionMajor missing in SOAP message header (SAP XI Extension)
Attribute 'versionMajor' expected
</SAP:Stack></SAP:Error></SOAP:faultdetail></SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
". Skip confirmation and proceed with next query
08:17:25 (4077): Retry mode - wait 10 sec, 0 msec interval before retry

Hi,
AFAIK, builer package shoud be under WEB-INF\classes directory or the context. It is under that direcory.
As far as adding the package to system classpath or Tomcat classpath, I dont want to do that as it would contaminate the classpath of other applications/contexts.
The applications server is supposed to automatically add WEB-INF\classes into the classpath of the context. And its working for other context.
There has to be other solution.
Regards
Amitabh

SOAP requests hang for 5 minutes. Why?

As a first step in using the SOAP features integrated in Java 6 I went through the JAX-WS 2.0 tutorial at http://java.sun.com/developer/technicalArticles/J2SE/jax_ws_2/.
I created the simple webservice as well as the client (I am not using the Netbeans IDE but I did the corresponding in my IDE).
I started the service in a local VM and started the local client application as well.
What's really odd is: the service and the client worked on first attempt (and I verified this by inserting println statements into the code), but the return of the result always hangs for pretty exactly 5 minutes (by when - I guess - some timeout strikes).
I.e. the client issues the request and the server-side gets called practically immediately, but the result is passed back to the client only 5 minutes later.
At first I had thought, that things didn't work, but when I got distracted and later returned to my screen I found, that my WebService requests had actually worked as designed.
But why does the return of the response take 5 minutes? Any ideas, anybody?
Michael

I've seen similar behavior, but not on every invocation. In my case:
1) Nightly backups were starting at 5:30PM every day - every request then timed out;
2) Our development servers were virtual machines - they were often slow to wake up.
Otherwise, the web services responded normally.

Problem: Plain J2SE Adapter Engine

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

Hi Stefan,
SOAP Adapter module settings:
Bubble adapter java class
classname=com.sap.aii.messaging.adapter.ModuleBubble
This adapter instantiates a bubble bag for supporting
a xmb web service gateway. A bubble bag is a collection of Bubble
instances that form some processing chain of message objects.
Below parameter Bubble.Helper specifies the helper class that implements
the ModuleBubbleHelper interface. This class is used to instantiate
a bubble bag for this adapter.
Sets the bubble module helper that can instantiate your bubble bag
Bubble.Helper=com.sap.aii.messaging.adapter.ModuleBubbleHelperXMBWSImpl
#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
Below this line are the parameters specific to the ModuleBubbleHelperXMBWSImpl
#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
The configuration of this helper class is divided in two parts. The first part
specifies the adapter configuraton for Web-Service clients communicating with an
XMB server. The second part specifies the configuration for XMB clients
communicating with a WebService server. Either one or both parts can be configured
in a single configuration file.
Part 0 (FromWS and ToWS) : common part ######
Keeps the XMB headers in web service messages
XMBWS.KeepHeaders=true
Keeps the attachments in web service messages
XMBWS.KeepAttachments=false
Encodes the xmb headers into a special HTTP header string x-xmb_ws_encoded
XMBWS.UseEncoded=false
Part 1 (FromWS) : WS clients to XMB server ######
The target URL of XMB broker, to which the adapter sends XMB messages.
XMB.TargetURL=http://netweaver:8000/sap/xi/engine?type=entry
The port and path where the adapter waits for web service messages from clients.
XMBWS.WSPort=4444
XMBWS.WSPath=/soap/start
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: <[email protected]>
<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)

J2SE adapter engine and SSL testing

Hi there,
We are currently doing a B2B scenario whereby SAP XI sends a message to the J2SE adapter engine in the DMZ and then that sends the message via HTTPS / SSL to the receiving service....
In order to test that the HTTPS / certificate etc worked I wrote a small Java application and dialled out of the network. I inserted the DER file into my CACERTS file on my local machine using the keytool as a "trusted certificate". The Java application worked 100% and did the SSL handshake fine and POSTED the data fine as well......
Now I am no expert in the J2SE adapter engine but decided to try testing the same SSL connection using the J2SE adapter engine from my LOCAL machine with me dialled out onto the Internet.
I logged into the J2SE adapter engine and imported the same DER file into the engine (actually inserted into the "truststore.jks" file). I them went into the "Test Environment" of the J2SE adapter and have been trying to test.....
I have a few questions:
1. Do I have to use a P12 or PFX file for this sort of communication? Reason I ask is that with the Java application all I needed was the DER file?
2. In the full blown scenario do I have to have SSL configured between XI and the J2SE adapter engine as well? Or can that stay as HTTP?
My basic config for the test is roughly:
WS.targetURL=https://someserver:4433/soap/someInbox
WS.SOAPAction=CustomSoapAction
SSLauthentication=true
Do I really need the following two?
SSLcertificate=somecert.p12
SSLcertificatePassword=somepassword
From my logic all I should need if the DER file loaded into the J2SE adapter which I have done......
Has anyone done successfull SSL / HTTPS testing from the J2SE adapter engine using the "Test Environment"?
Any advise would be greatly appreciated
Kind regards
Lynton

Hi
Not a answer to your question but why use the J2SE adapter engine in the DMZ and why not the J2EE Decentral Adapter Engine?
Regards
Bhavesh

J2SE File Sender Adapter Error

Hi Experts,
I am doing a scenario on J2SE. Like this: J2SE File Sender -> XI -> J2SE File Receiver.
On File Sender adapter, it has an error, like this "ERROR: Finished sending to Integration Engine with error u201Cjava.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Foundu201D. Skip confirmation and quit this loop"
And this is the full log:
D:\Thach\Input\xi_test.xml
16:51:45 (4052): Start processing u201CTXTu201D file u201CD:\Thach\Input\xi_test.xmlu201D size 190 in u201CEO mode
16:51:45 (4058): Start converting to XML format
16:51:45 (4061): Converted complete file content to XML format
16:51:45 (4062): Sending text message u201Ce1ffc9e0-71e5-11de-8306-0019d12044f1u2033 type u201Capplication/xmlu201D to Integration Engineu2026 (message size: 633 bytes, URL: u201Chttp://host:50200/sap/xi/engine?type=entryu201D)
16:51:45 (4076): ERROR: Finished sending to Integration Engine with error u201Cjava.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Foundu201D. Skip confirmation and quit this loop
16:51:45 (4077): Retry mode - wait 10 sec, 0 msec interval before retry
And this the content of xi_test.xml:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_Material_toPPS xmlns:ns0="http://gml.com/xi/XI/Tutorials">
   <Material>
      <Text>Test</Text>
   </Material>
</ns0:MT_Material_toPPS>
And this the configuration of J2SE File Sender:
mode=FILE2XMBWITHROWCONVERSION
XI.TargetURL=http://host:50200/sap/xi/engine?type=entry
XI.User=PISUPER
XI.Password=*********
XI.QualityOfService=EO
XI.SenderParty=
XI.SenderService=BS_PlainJ2SE_Sender
XI.ReceiverParty=
XI.ReceiverService=BS_FileRecv
XI.Interface=MI_Material_toPPS_OB
XI.InterfaceNamespace=http://gml.com/xi/XI/Tutorials
file.type = xml
file.sourceDir=D:
Thach
Input
file.sourceFilename=xi_test.xlm
file.processingMode=test
file.pollInterval=10
#Content conversion parameters in PlainJ2SE Adapter
xml.documentName = MT_Material_toPPS
xml.documentNamespace = http://gml.com/xi/XI/Tutorials
xml.structureTitle = Material
xml.processFieldNames = fromConfiguration
xml.fieldNames = Text
Please help to solve the issue.
Thanks so much,
vn thach

The URL of the Integration Server is wrong or you cannot access the server from the host, where the J2SE adapter is running:
XI.TargetURL=http://host:50200/sap/xi/engine?type=entry
If the Client of the Integration Server is not 000, then you have also to add that line:
XI.Client=XXX

SOAP adapter installation and activation

We have installed XI 3.0 SR1 and wish to enable the sender SOAP adapter to receive SOAP messages from a different (PeopleSoft) system. The documentation we have found really seems to be lacking in the area on installing and activating the SOAP adapter. We are fine with the configuration pieces, but first activating the SOAP adapter is our problem.
1) Is the SOAP adapter part of the Central Adapter Engine or do we need to install the Plain J2SE Adapter Engine on our XI server to get the SOAP adapter?
2) If the SOAP adapter is part of the Central Adapter Engine, how do I 'activate' it?
When I view the Adapter Monitor (http://<XIserver>:<J2EEport>/AdapterFramework/monitor/monitor.jsp) I see a line item for the SOAP adapter but it is grayed out. Also, when browsing J2EE with the Visual Admin Tool, I find the following adapters, but no SOAP...
SAP XI Adapter: BC
SAP XI Adapter: File
SAP XI Adapter: JDBC
SAP XI Adapter: JMS
SAP XI Adapter: Mail
SAP XI Adapter: Marketplace
SAP XI Adapter: RFC
SAP XI Adapter: XI
Any advice would be appreciated. We see our next option as either applying XI Support Packages which will hopefully correctly deploy the SOAP adapter in case this was an installation problem, or to install the Plain J2SE Adapter Engine. Thank you!

Hi Jeff,
XI 3.0 the SOAP Call goes to the Java Port 50000 plus instance number * 100. And the URL is different.
It goes to a servlet and the URL is:
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
without a party name it is:
http://host:port/XISOAPAdapter/MessageServlet?channel=:service:channel
Monitoring is in the SXMB_MONI or the Runtime workbench, the adpater monitor does not give you details.
Here is the link to the help docu:
http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
It is not too bad and as I said it works fine both ways.
Cheers
Stefan

Configuring the SOAP Adapter

Hi Folks,
I have a sceanrio where an AXIS client needs to talk to the XI SOAP Adapter.
How do I configure the SOAP adapter?
I tried to access the help docs for configuring the SOAP adapter. I understand that the adapter depends upon the plain J2SE Adapter Engine which should be available on port 8000.
But when I try to access
http://<hostname>:8000 I get an access denied error
Please help!
Thanks in advance,
Shailesh

Hi Shailesh,
Maybe your 8000 Port is in Use. So you can chance the port to 8200 or something else.
You Change port in "GUIBrowserEngine.properties" file.
And try to patch the Plain J2SE Adapter Engine with "SP 10 for XI Connectivity SE 3.0"
Regards,
Robin

J2SE AE: SOAP

Similar Messages

Maybe you are looking for