URL For J2SE Adapter Engine Configuration

Hi All,
I have to go for adapter configuration for that i need to go to Adapter Engine Configuration Screen. So can any one please tell me the URL for going to the particular screen.
Regards,
Rahul

Hi rahul,
I think URL for J2SE adapter engine is http://hostname:portname. Just check following link :
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/6f/246b3de666930fe10000000a114084/frameset.htm">J2SE ADAPTER ENGINE</a>
Regards,
Keith.

Similar Messages

Default port for J2SE Adapter Engine?

Hello all,
what is the default port for J2SE Adapter Engine? How do I restart this adapter engine?
Regards,
N.S

Swamy,
8200 is the default port. Also go through this help of how to start and stop the J2SE Adapter Engine:
http://help.sap.com/saphelp_nw04/helpdata/en/12/5dd23aaad7b3408dde3c1577fda5b3/frameset.htm
---Satish

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

URL for Central Adapter Engine

Hi,
It seems like our XI Server is unable to locate the Central adapter engine for doing an outbound RFC call. I am trying to call an RFC using the RFC adapter, and getting the following error:
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.nw4.netweaver</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>no_messaging_url_found: Unable to find URL for Adapter Engine af.nw4.netweaver</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine af.nw4.netweaver</SAP:Stack>
Where do we maintain the URL of the adapter engine ?
thanks,
Manish

I have the same problem since we changed the name of the database server - the server name reported in the error is the old name. I've checked all the properties in this thread, plus follwed through OSS note 764176 with no luck. All the properties reflect the new name, but testing the proxy (SPROXY) still fails with the error:
<CODE>INTERNAL.AE_DETAILS_GET_ERROR</CODE>
<ERRORTEXT>Error when reading the access data (URL, user, password) for the Adapter Engine af.xix.sapsbxcrmdb2</ERRORTEXT>
sapsbxcrmdb2 is the old database server name.
I found one location where this is displayed - in transaction SXI_CACHE (in the client of th integration server), Menu option GOTO -> Adapter Engine Cache. The column 'Adapter Engine Name' reflects the incorrect name. Where is this property stored?
I cleared this entry manually by selecting the row and clicking on the trash can icon. Later it was refreshed properly.
-Mike
Update: I found that the SOAP Reciever channel in my Integration Scenario had a hard-coded entry pointing to the old integration server name in the property 'Adapter Engine'. I changed this by selecting the 'Integration Server' in the drop down. This changed the error behavior (still doesn't work, but the above errors went away).
-Mike
Message was edited by: Mike Hatch
Message was edited by: Mike Hatch
Message was edited by: Mike Hatch

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,

Error while reading access data (URL, user,password) for the Adapter Engine

Hi,
Any idea on below message? I am doing file to file scenario and got the below tarce from sxmb_moni.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.pi1.piserver1</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>no_messaging_url_found: Unable to find URL for Adapter Engine af.pi1.piserver1</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine af.pi1.piserver1</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks
Balaji

It looks like the adapter engine is not able to register him self on SLD, you have to check in the SLD the "Exchange Infrastructure" domain, you have to verify restarting the J2EE the adapter engine update the entries in the SLD related to the specific XI Domain.
Launch Visual Administrator >> Server >> Services >> SAP AF CPA Cache
Enter the appropriate values for:
SLD.selfregistration.hostname (Use fully qualified hostname)
SLD.selfregistration.httpPort
SLD.selfregistration.httpsPort
Sandro

Configuration Steps for Decentralized Adapter Engine

Hi all,
What all configuration steps are required to make Adapter Engine as
Decentralized AE.
I have made required changes in SLD DataSupplier in Visual Administrator.
what more configurations have to be done? On SAP XI Server and Decentralized
Adapter Engine.
With regards
Prasad

Prasad,
After configuring SLD data supplier in Visual Admin, you need to the following
1) Configure the gateway service for the central integration server on adapter engine host.
2) Perform Initial adapter engine cache refresh
3) Trigger data transfer to SLD
4) Check the connection parameters in exchangeProfile
5) Create HTTP destination pmistore in java environment
you have to go through all these tests for decentralized adapter engine. If you have XI configuration guide, it has all these steps in detail for you to configure
--Archana

Configuring Process Integration Scenarios for Advanced Adapter Engine

Hello @all,
i've an asynchronous SOAP scenario and would like to configure an integrated configuration for Advanced Adapter Engine using a process integration scenario. In the documentation (Link below) it is described, that you can select local communication using AAE in the model configurator, but I couldn't find any hint. Any idea?
Documentation:
http://help.sap.com/saphelp_nw73/helpdata/en/48/ce987b18d3424be10000000a421937/content.htm
Thanks and kind regards
Andreas

Hi,
Use thse links:
Advanced Adapter Engine Configuration in PI 7.1
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/700058f0-b1a1-2a10-39a8-ab2627b87cfa?QuickLink=index&overridelayout=true&47047071760975
Sreeni.

Error while reading access data (URL, user, password) for the Adapter Engin

Hi all,
I encountered a red flag in sxmb_moni and when I click on the flag, I get the following message:
Error while reading access data (URL, user, password) for the Adapter Engine
Is there any way I can resolve this? thanks all
Regards,
IX

Possible reason is Adapter engine is not registered on SLD. Check in SLD.
You can also try restarting J2EE adapter engine and update SLD entries specific to XI domain.
Lauch Visual admin go to Server > services > SAP AF CPA Cache
Enter the appropriate values for:
SLD.selfregistration.hostname (Use fully qualified hostname)
SLD.selfregistration.httpPort
SLD.selfregistration.httpsPort
Finally, if all the above seem to be correct check the userID / pwd for user ID : PI*.

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

Receiver File Adapter J2SE Adapter Engine

Hi,
We have configured a receiver file adapter on a J2SE adapter engine through the administrator page of the J2SE adapter.
XI.httpPort=8222
XI.httpService=/file/Receive
and the rest of the adapter parameters.
I have configured a channel in ID as XI receiver adapter.
host: "hostname"
Service: 8222
Path Prefix: /file/Receive
The messages in sxmb_moni fail to be delivered with "HTTP error 404 Resource not found."
Through a browser I am also not able to make a connection to this url:
"host":8222/file/Receive
Getting Http error "501".
Please can someone shed some light on this problem.
Regards
Willie Hugo

>Through a browser I am also not able to make a connection to this url:
>"host":8222/file/Receive
>Getting Http error "501".
This is ok. Since get method not implemeted for this service.
Since from XI you are getting this error "HTTP error 404 Resource not found", can you logon to XI server at OS level and do a telnet test to check if the port is working.
cmd> telnet
telnet> open <J2SEAdpaterEngineHostName (or) IPAddress> 8222

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 / 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

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 adapter engine monitoring.

Hi,
I have setup GRMG monitoring for a J2SE adapter engine in our landscape. I have set up a HTTP RFC destination in SM59. In the HTTP RFC destination, type H, I have specified the "Target Host" (FQHN) the "Service No." (8200 default J2SE installation port) and a "Path Prefix" (/rtc). The security is set to Basic and I have used a PIRWBUSER that I have setup on the J2SE Adapter Engine with role Administator. In the GRMG template I insert the RFC destination.
I have also inserted the ID, ESR, RWB, SLD and the Central Adapter framework of the PI system in the GRMG template, then deployed the template on the monitoring server. I am able to successfully monitor the other components except for the J2SE adapter.
I have to concede that when I test the RFC destination to the J2SE adapter it does not work. I think the J2SE adapter is up, as I can connect to the administrator. Even when I put the url ("host:port/rtc") for the J2SE adapter in my browser, it then request to login. After I have logged in, it gives a error "The Page can not be found".
It would be most appreciated if someone can shed some light on this issue.
Regards
Willie Hugo

FTS SAP Basis,
Thanks for that advice. However once I have set the "Accept cookies" to "Yes", and once again I do a "Connection Test", the result I get "ICM_HTTP_CONNECTION_FAILED". Also remember when I try to connect to the URL "http://host:8200/rtc", it requests a login, but then display "The page can not be displayed".
Any other suggestions are welcome.
Regards
Willie Hugo

URL For J2SE Adapter Engine Configuration

Similar Messages

Maybe you are looking for