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

[Former Member]

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

[stefan_grube]

Try parameter:

XMBWS.NOSOAP = true

Even this is not documented, it should work.

Regards

Stefan

[Former Member]

Hi there,

That parameter setting sounds very interesting......let me see what it does.....I will get back to you, thanks

Lynton

[Former Member]

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

[Former Member]

Just note in the above code it shows the parameter with a "" before and after it.(XMBWS.NOSOAP=true*)....I was trying to make it BOLD in the forum but it failed to do so.....just know that the parameter is fine and uncommented in the config..

Thanks

Lynton

[stefan_grube]

I have tested it by my own now. Seems that the parameter has no effect at all. I don't know why, but as the parameter is not documented, we cannot claim this as a bug.

I am sorry, in that case you cannot use J2SE adapter for plain HTTP messages, as there is now adapter for this.

Regards

Stefan

[former_member181985]

Hi,

SAP implemented HTTP adapter engine in ABAP stack.

Hence there will be no HTTP Adapter in J2SE adapter engine.

However you can develop your own HTTP adapter in Java using SAP standards, but it is a tedious and time consuming process.

Thanks,

Gujjeti