Shutdown of XI 3.0 Plain J2SE Adapter Engine.

How do I shutdown the XI 3.0 Plain J2SE Adapter Engine? Where should I go to do this?
Regards,
N.S

Hi N.S. -
If I recall correctly, you open a browser to http://<host>:8200 . 8200 is the default port. If not using the default port, you may need to investigate what that port is. Delivered initial user/pwd is sap/init.
There's a Shutdown Adapter Engine option once you get in. Of course, the j2se adapter engine must be running in order for you to do this.
Regards,
Jin

Similar Messages

"Performance" problems with the File adapter on Plain J2SE Adapter Engine

Hi,
At the moment I'm on a customer side to solve some XI issues for a few days. One of the issues is the performance of the Plain J2SE Adapter Engine, using the file adapter to transfer XML messages(already XI message format) from the legacy system to the Integration Engine. The File adapter has to deal with "large" XML messages(max at the moment is 65 Mb) and the engine fails with the following error when transferring the big XML file: "ERROR: Finished sending to Integration Engine with error "java.lang.OutOfMemoryError". Skip confirmation and quit this loop".
As far I got the information from the customer the memory use of the Plain adapter engine is set to 512Mb. This is maybe to low. But I don't know where to look for this, I only have the adapter web interface in front of me, no access to the OS it self via for example remote connection.
On the Integration Engine I know there is the ability to split large message with the file adapter(File Content Conversion), but I don't know this for the Plain Adapter Engine. Is there a possibility to do this also on the Plain Adapter Engine?
Thanks in advance for any input.
Greetings,
Patrick

Hi Sameer,
Thanks for your answers.
On the first solution, yes that is possible, we first decided to see if the legacy system can do the splitting, before starting developing a Java program.
On the second solution, as far as I know is this solution possible on the Integration Engine. But we are facing the problems on the Plain J2SE Adapter Engine. I went trough that documentation(link:
http://help.sap.com/saphelp_nw04/helpdata/en/6f/246b3de666930fe10000000a114084/frameset.htm ), to look for I similiar solution in the Plain Adapter Engine. So my question is, is this possible with the Plain Adapter? And if so, what kind of parameters I need to use to achieve this.
Regards,
Patrick

Installation and then Configuration of Plain J2se Adapter Engine

Hi All,
Actually we want to use JMS Adapter for that we had installed Plain J2SE Adapter Engine but after installing and following the initial steps of Adapter.pdf we are not able to access the Adapter Engine through URL.We are using the URL http://<hostname>:8200/MessagingSystem/receive/AFW/XI
this URL is there in our SLD but we are not able to access the page.
So Please can somebody help me to resolve this issue.
Thanks & Regards
Sathya

Hi Amol,
I am trying to send read data from MQSeries using JMS adapter. We are successful in opening the Adapter Engine and the GUI. We have cofigured the adpter as follows. But when we try to restart the adapter to get the changes get saved we are getting the following error
"ERROR CALLING THE RESTART ADAPTER"
Also status is shown is yellow and version is shown as not set.
Where ever I have changed the configuration data I have shown it in bold
JMS-Adapter Configurarion
This Configuration is a sample for a JMS sender channel (inbound, sends to XI IS)
Set XI message protocol version. This sample is designed for XI 3.0
version=30
JMS message receiver class
classname=com.sap.aii.messaging.adapter.ModuleJMS2Transport
set if a transacted JMS Session should be used (default: true)
#JMSSession.sessionTransacted=false
set delay in milliseconds before processing next message after an error (default: 0)
errorDelay=10000
#set delay in milliseconds before trying to reestablish the JMS Connection after a connection error (default: -1 (do not try to reconnect))
#reconnectDelay=10000
set the Message Formats you want to process (Formats only needed if they can not be evaluated at runtime)
TransportMessage Type can be set to TransportMessage of XMBMessage. It is used for sending and receiving Transport and XMBMessages
#TransportMessage.type=TransportMessage
TransportMessage.type=XMBMessage
uncomment and adjust parameters for Transformation Type (Binding of JMS-Transport Message),
insert your class here for an individual binding between JMS and Transport Message
uncomment the following line for using Bindings that belong to Tunneling
#transformClass=com.sap.aii.messaging.adapter.trans.JMSTunneling
uncomment the following line for using Bindings that belong to Single Payload Binding
transformClass=com.sap.aii.messaging.adapter.trans.JMSSinglePayloadBinding
ID Garbage Collector: For EO(IO) handling XI adapters store the JMS/XI message ID's in the ID logger
Uncomment the following lines and change the default values if you recognized "out of memory" problems due to
very large ..\tech_adapter\Data\*_ID.dat files which will be kept in the memory as well
eoExpirationAfterDays is the period of keeping the message ID in days. Afterwards the message ID might be used again
garbageCollectorInterval is the period in milliseconds when the ID garbage collector is started. It will however only
be started if messages are exchanged otherwise ID logs won't be created anyway
eoExpirationAfterDays=365
garbageCollectorInterval=86400000
#
the following parameters are used in some Bindings that belong to Single Payload Binding needing XMBHeader Information
uncomment and adjust parameters according your requirements. Please note, that the party identfier needs not to be
configured in case of A2A scenarios.
#XI.SenderParty=Sender
XI.SenderService=MQSeries
#XI.ReceiverParty=Receiver
XI.ReceiverService=MTX
XI.InterfaceNamespace=http://xitest
XI.Interface=MI_Out_File
XI.TraceLevel=1
XI.LoggingLevel=1
XI.QualityOfService=EO
XI.QueueId=ABCD
XI.ContentType=text/xml
# *************************************************************************************************************
#
URL of XI IS to send the messages to
XI.TargetURL=http://bwxi:50000/sap/xi/engine?type=entry
XI.User=XIAF
XI.Password=XIPASS
# *************************************************************************************************************
URL of file adapter if a loopback JMS to File should be configured
XI.TargetURL=//localhost:8210/file/receiver
# uncomment the following settings if needed (independent on JMS provider)
JMS.QueueConnectionFactoryImpl.user=xisuper
JMS.QueueConnectionFactoryImpl.password=xxx
#
uncomment and adjust parameters for loading JMS administrated objects via JNDI
uncomment and adjust parameters if not the default context should be used
#JNDI.InitialContext.property.1=java.lang.String {javax.naming.Context.INITIAL_CONTEXT_FACTORY}, java.lang.String com.sap.engine.services.jndi.InitialContextFactoryImpl
#JNDI.InitialContext.property.2=java.lang.String {javax.naming.Context.PROVIDER_URL}, java.lang.String localhost:50004
#JNDI.InitialContext.property.3=java.lang.String {javax.naming.Context.SECURITY_PRINCIPAL}, java.lang.String Administrator
#JNDI.InitialContext.property.4=java.lang.String {javax.naming.Context.SECURITY_CREDENTIALS}, java.lang.String sap
set the Lookup Names
#JMS.JNDILookupNameQueueConnectionFactory=jmsfactory/default/joetest
#JMS.JNDILookupNameQueue=jmsQueues/default/sapDemoQueue
uncomment and adjust parameters for loading JMS administrated objects from filesystem ***
#JMS.FileNameQueueConnectionFactory=SAPQueueConnectionFactory.ser
#JMS.FileNameQueue=SAPQueue.ser
uncomment and adjust parameters for creating SonicMQ JMS administrated objects ***
JMS.QueueConnectionFactoryImpl.classname=progress.message.jclient.QueueConnectionFactory
JMS.QueueConnectionFactoryImpl.constructor=java.lang.String localhost:2506
JMS.QueueImpl.classname= progress.message.jclient.Queue
JMS.QueueImpl.constructor=java.lang.String SampleQ1
# uncomment and adjust parameters for creating MQSeries JMS administrated objects ***
JMS.QueueConnectionFactoryImpl.classname=com.ibm.mq.jms.MQQueueConnectionFactory
JMS.QueueConnectionFactoryImpl.method.setHostName=java.lang.String BWXI
JMS.QueueConnectionFactoryImpl.method.setChannel=java.lang.String JAVA.CHANNEL
JMS.QueueConnectionFactoryImpl.method.setTransportType=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_TP_CLIENT_MQ_TCPIP}
JMS.QueueConnectionFactoryImpl.method.setQueueManager=java.lang.String QM_BWXI
JMS.QueueImpl.classname= com.ibm.mq.jms.MQQueue
JMS.QueueImpl.constructor=java.lang.String postcard
JMS.QueueImpl.method.setTargetClient=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_CLIENT_NONJMS_MQ}
# *************************************************************************************************************
uncomment and adjust parameters for using a dispatcher ***
#Dispatcher.class=com.sap.aii.messaging.adapter.ConversionDispatcher
#Dispatcher.namespace=namespace1
#namespace1.ConversionDispatcher.logPayload=true
#namespace1.Service.1=Plain2XMLService
#namespace1.Plain2XMLService.class=com.sap.aii.messaging.adapter.Conversion
#namespace1.Plain2XMLService.xml.conversionType=SimplePlain2XML
#namespace1.Plain2XMLService.xml.processFieldNames=fromConfiguration
#namespace1.Plain2XMLService.xml.fieldNames=a,b,c
#namespace1.Plain2XMLService.xml.fieldSeparator=;
#namespace1.Service.2=XSLTService
#namespace1.XSLTService.class=com.sap.aii.messaging.adapter.XSLTConversion
#namespace1.XSLTService.XSLTConversion.XSLTFileName=Data/DemoConversion.xsl
Can you please help me in resolving the error.
Regards,

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)

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

Null Pointer Exception in Plain J2SE Adapter Engine

Hi All,
I am able to start the J2SE Adapter Engine. But when ever i click any button on my JMS Adapter i am getting
Error stopping adapter: java.lang.NullPointerException
Error terminating adapter: java.lang.NullPointerException
Can somebody guide me why this error is comming or the possible reasons for the error.
Thanks in Advance.
rahul

Hi Rahul,
Please can you go through the thread
J2SE Adapter Engine / JMS Adapter
It does not talk about the error but the config need to be done for JMS. Hope this helps.
Regards
Vijaya

Unable to start the plain J2SE Adapter Engine

Hi All,
Eariler i was able to start the Adapter Engine. But i dont know what went wrong, i am not able to start the adapter engine.Is there any way to find out what went wrong?
Regards
Sathya
Message was edited by: Sathya Priya

Make sure you have write permissions to your log files and that you have permissions to start the Engine.
Also check your JAVA_HOME path by typing set in windows and env in unix systems.Make sure it points to your java installation directory lib and bin files.
Your ADAPTER_HOME should also contain all jars required or the absolute path to these jars need to be defined in your run_adapter_*. Not to sure if you are running windows or a unix box.
Regards
Robert

Plain J2SE Adapter Engine

Sap Guru's
I'm trying to configure an adapter to recieve text files out of a specified directory and integrate and convert them into a single xml file, with no further processing.
I get the following log:
Mon Oct 24 01:02:22 GMT-08:00 2005 *****
01:02:22 (4012): "Guaranteed Delivery" operation for 2 file(s) pending
01:02:22 (4023): File adapter initialized successfully
01:02:22 (4007): File adapter started
01:02:22 (4051): Process 1 file(s):
01:02:22 : c:\XItext\myfile.txt
01:02:22 (4052): Start processing "TXT" file "c:\XItext\myfile.txt" size 38 in "EO mode
01:02:22 (4062): Sending text message "6b29c560-446b-11da-be97-e3950a0a0222" type "application/xml" to Integration Engine... (message size: 38 bytes, URL: "http://cic040.cice.cic.ae:50000/sap/xi/engine?sap-client=000")
01:02:23 (4076): ERROR: Finished sending to Integration Engine with error "java.net.ConnectException: Connection refused: connect". Skip confirmation and quit this loop
01:02:23 (4064): File adapter processing complete
My target url is XI.TargetURL=http://cic040.cice.cic.ae:50000/sap/xi/engine?sap-client=000 ....
i have activated the adapter_plain in SICF..
Is this because i need to configure the adapter_plain and/or a pipleine URL and if so how do I configure them and check they're fine????

Dear Hans;
Thanks for you're help i changed the port to 8000 but i got a different error...
07:00:19 (4076): ERROR: Finished sending to Integration Engine with error "com.sap.aii.messaging.net.TransportException: HTTP 500 Pipeline specified in URL attribute (type) not existing
http-Response:
set-cookie: sap-usercontext=sap-client=000; path=/
content-type: text/xml
content-length: 985
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/"><faultcode>SOAP:Client</faultcode><faultstring>Pipeline specified in URL attribute (type) not existing</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">URL_PIPELINE_NOT_FOUND</SAP:Code><SAP:P1>/sap/xi/engine?sap-client=000</SAP:P1><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Pipeline ID which is expected as value of attribute "type" in the URL, does not exist in the Integration Engine (URL = /sap/xi/engine?sap-client=000)
</SAP:Stack></SAP:Error></detail></SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
". Skip confirmation and quit this loop
07:00:19 (4064): File adapter processing complete
I went to transaction SXMB_ADM but i can't seem to find a way to configure the pipeline id...
Also when i try to check the integration engine configuration the system tells me that its not configured yet....
2 Questions:
1. Do i need to configure the integration engine as im not using it for any kind of processing?
2. Given the error in the above log is it a pipeline configuration error and how do i solve it???
Thanks alot for youre help

Registering Plain J2SE adapter in IS

Hi,
I've been trying to use plain J2SE file adapter as receiver with no luck.
I've installed plain J2SE adapter on a windows 2000 server called tgrpser1, and XI is on another Windows 2000 server tgrpserxi.
SLDAccessor service is started with no error in tgrpser1.
When go to the SLD, the adapter engine shows up in the XI technical system but when I go to the Integration Directory to configure a file adapter as receiver for tgrpser1, the Adapter Engine has one value Integration Server.
Please help...
Thanks

I think I should it put this way.
I have a plain J2SE adapter engine running on tgrpser1 (it is not an FTP server), I've copied the file_receiver adapter to rec_File_adapter.
If the scenario is RFC -> XI -> File (on tgrpser1), how can I specify the rec_File_adapter in Integration Directory.
If I am not correct, what is the use of plain J2SE adapter engine file_receiver ?
Thanks

PLAIN J2SE ADAPTER

WHY PLAIN J2SE ADAPTER ENGINE IS SEPARATELY MAINTAINED FROM AN ADAPTER ENGINE?

Hi,
The Plain J2SE Adapter helps you to exchange messages with partners or even inside your own company to communicate to home grown systems it was the PCK of XI 2.0 and is mantained separately because in the Adapter Engine you have all the adapters you need and for partners that does not have XI or custum systems that does not have a way of comunication you use the Plain J2SE this is why is mantained separately becuase you use it to exchange messages with Adapter engine that runs in XI.
It is recomended by SAP to use the PCK (Parner Connectivity Kit)

J2SE Adapter Engine / JMS Adapter

We need to connect to MQ Series 5.3 (Websphere MQ) from the XI (3.0 SP16) box.
1)Is J2SE adapter engine needs to be enabled/configured in order to use JMS Adapter? Cant we use J2EE JMSAdapter instead of J2SE JMS Adapter?
2) Where can I download the JMS Adapter libraries, for installation?
Ours is unix-based installation.
I have gone thru the thread
Installation and then Configuration of Plain J2se Adapter Engine
and the SAP Note: 747601 that talks about J2EE JMSAdapter MQSeries libraries.
TIA,
Steve

Hi Steve,
Check these ~
http://help.sap.com/saphelp_nw04/helpdata/en/6f/246b3de666930fe10000000a114084/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/03fd85cc-0201-0010-8ca4-a32a119a582d
J2Se adapter
Installation and then Configuration of Plain J2se Adapter Engine
Hope this helps,
Regards,
Moorthy

Using plain j2se adapter

Hi Experts,
This is regarding j2se adapter engine.
I dont have any idea to use j2se adapter engine.
I checked this URL: http://<IPAddress>:8200 , changing the ip but it is not working.
How can I check whether it is installed in my system ?
Thanks
Rabi

Hi,
Please go through this blog i hope this will helpful.
http://www.****************/Tutorials/XI/J2EEAdapterEngine/plain.htm
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b09b204b-614e-2a10-13bd-df540fdb4bd6?QuickLink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d09c8ff5-150e-2b10-2189-82d725ef9f29?QuickLink=index&overridelayout=true
http://www.riyaz.net/sap/file-to-file-scenario-using-j2se-engine/563/
reagrds,
ganesh.

Plain J2SE adapter and SLD configuration

Hi all,
I'm trying to configure Plain J2SE Adapter to be connected to SLD for purpose of automatic registering to SLD. I followed the description in PDF manual, but I still get following error:
Error creating adapter services for
J2SE_AE_server2.dummy.com_8200 com.sap.lcr.api.cimclient.LcrException: CIM_ERR_FAILED:
SAP_BusinessSystem.CreationClassName="SAP_BusinessSystem",Name="AdapterSenderService"
referenced by association SAP_SenderAdapterForBusinessSystem.Antecedent=ref"SAP_XIAdapterService.CreationClassName=\"SAP_XIAdapterService\",
Name=\"file_sender2is\",SystemCreationClassName=\"SAP_XIAdapterEngine\",SystemName=\"J2SE_AE_server2.dummy.com_8200\"",
Dependent=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"AdapterSenderService\"" does not exist.
Do I need to setup something special in SLD ? I thought the registration should work without adding of any BusinessSystems to SLD ... I suppose it should work as autoregistering in SLD via the user parameter SLD.user mentinoed in the config file SLDaccessor.properties.
Any ideas ?
Thank you in advance.
Regards
Tom

Hi Tomas,
After the PI installation we have to do post installation step, if not done pls refer this SAP help to configure it..
http://help.sap.com/saphelp_nwesrce/helpdata/en/98/fa9b6ec510404dbcfebf35cb107c04/frameset.htm
Hope it helps..
Thanks,
Kumar.

Ping error in RWB for J2SE Adapter Engine

Hi,
we have several external J2SE adapter engines and they function great other than from a monitoring perspective. In RWB "Ping Status" I'm getting the following:
HTTP request failed. Error code: "401". Error message: "Authorization Required"
Suggestions?
Cheers,
Mattias

This is not an answer to your question.
I've tried to get an answer for: how to register J2SE adapter with Integration Server ?
I tried using SLDAccess service on J2SE adapter with no luck (with this J2SE Adapter Engine is registered in the SLD). My J2SE adapter was never available in the configuration means, in the communication channel ex: file adapter, for the adapter engine drop down all I have is Integration Server, my J2SE adapter was never listed there.
If you know an answer please post.
thanks
SKM

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

Shutdown of XI 3.0 Plain J2SE Adapter Engine.

Similar Messages

Maybe you are looking for