J2SE Adapter + Remote connection by XI PROXY

Hi,
1. When you use a decentralized Adapter Engine (called also J2SE Adapter Engine), you use the following URL address in order to start the Graphical User Interface (GUI) associated to A.E: <i>http://localhost:8200/adapter.html</i>
2. You also have the possibility to use directly your own IP address instead of "localhost"... Thus you could use something like that: <i>http://999.88.77.666:8200/adapter.html</i>  (remote URL)
3. If you use another IP address than yours, then you have the possibility to have a remote connection to another AE installed on another workstation... GREAT !
BUT it's seems this tips is limited by a firewall action: I could only call "Target AE " if this tool is on the same network than mine... (<i><u>cf. point (0)</u></i> )
                              Firewall
                                 ||          
  <======= Network 1 ==========> || <======= Network 2 =======>
                                 ||
(0)  "My PC"  ---> "Target AE"  ||
                                 ||
(1)  "My PC"  ----------------->||     "Target AE" 
                                 ||         T
(2)               XI <---------------------+ 
                                 ||
                                 ||
(3)  "My PC"                    ||     "Target AE" 
         |                       ||         T
         |                       ||         |
         +-------> XI ----------------------+ 
                  PROXY ?        ||
                                 ||          
  <======= Network 1 ==========> || <======= Network 2 =======>
                                 ||
                              Firewall
>> Exactly, my problem is the following one:
- I have 2 networks separated by a firewall
- This firewall is only openned between XI and the Target AE (<i><u>cf. point (2)</u></i> )
- When I use directly my tips from "My PC" to "Target AE", I cannot reached it(according to me it's because of Firewall)... (<i><u>cf. point (1)</u></i> )
THUS I would like to use the "openned door" between XI and "Target AE", in order to a have a complete remote connection from "My PC" to "Target AE" by passing across XI... (<i><u>cf. point (3)</u></i> )
Not especially by using a scenario or a BPM, but directly by using HTTP address and / or a <b>PROXY</b> on XI. This Proxy will be used to call directly the "Target AE" by specifying an URL: <i>http://999.88.77.666:8200/adapter.html</i> 
>> Is it possible to define a PROXY on XI in order to do such a connection between "My PC" and "Target AE"?
Any help and any idea are welcome!
Regards.
Mickael

Hi Mickael,
Your Problem is more an Network Problem than an xi problem.
With a ABAP Proxy and a HTTP Request it maybe works when you develop something like a browser. You must send a HTTP GET Request to the Target.
Maybe you develop a J2EE application that is able to show the site in a iframe. But this i think is a redirict and will also block form your firewall.
The easyiest way is to call your admin and he open ther ports for your Plain J2SE Adapter Engine
Regards,
Robin

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

  • J2SE Adapter Registration

    I've tried to get an answer for this question long time ago, but no one ever answered.
    How to register J2SE adapter with XI ?
    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.
    thanks
    SKM

    Tony,
    You do not need FTP server to use file adapter. I've installed and configured a J2SE Adapter Engine on my laptop.
    I was able to use sender adapter but not the receiver adapter. I've followed all kinds of documentation, asked Qs in the forum but never got any feed back.
    After you install plain J2SE AE on your laptop, you have to configure SLDAccess service. Once it is connected to SLD, you can see the adapter engine name in the XI technical systems.
    Then you can configure FileAdapters by copying the existing one. Go through the Adapter documention in the installed directory.
    Hope this helps.
    Regards
    SKM

  • 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
    <b>"ERROR CALLING THE RESTART ADAPTER"</b>
    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
    <b>#
    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
    #</b> *************************************************************************************************************
    <b>#
    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
    #</b> *************************************************************************************************************
    URL of file adapter if a loopback JMS to File should be configured
    XI.TargetURL=//localhost:8210/file/receiver
    <b># uncomment the following settings if needed (independent on JMS provider)
    JMS.QueueConnectionFactoryImpl.user=xisuper
    JMS.QueueConnectionFactoryImpl.password=xxx
    #</b>
    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
    <b># 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}
    #</b> *************************************************************************************************************
    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,

  • 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

  • Where to find J2se Adapter

    Hi Friends,
       I guess the J2se adapter has to be installed or configured locally.Please correct me if iam wrong. Can anybody here tell me where i could find this software so that i could download it and use?..
    Thanks in advance.
    Regards,
    Tamilarasan.

    Hi Tamilarasan,
    I think you can find it here:
    https://websmp106.sap-ag.de/swdc
    then this path:
    - Support Packages and Patches
    - - SAP NetWeaver
    - - -  SAP NETWEAVER
    - - - - SAP NETWEAVER 04
    - - - -  Entry by Component
    - - - - - XI Adapter Engine J2SE
    - - - - - - XI CONNECTIVITY SE 3.0
    - - - - - - - OS independent
    Regards,
    michal

  • 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)

  • 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 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.

  • 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

  • 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 Error

    Hi everyone,
    I am facing couple of issues with J2SE adapter engine.
    1. First Issue
    Config in SLDaccessor -
    file adapter java class
    classname=com.sap.aii.messaging.adapter.ModuleSLDaccessor
    SLD.host=<HOST>
    SLD.port=50xxx
    SLD.user=user
    SLD.password=pass
    SLD.adapterEngineName=AdapterEngine
    Config in Sender File Channel
    file adapter java class
    classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
    version=30
    mode=FILE2XMBWITHROWCONVERSION
    XI.SLDConfiguration=SLDaccessor
    #XI.TargetURL=http://<HOST>:<50xxx>/sap/xi/engine/?type=entry
    XI.TargetURL=<fromSLD>
    XI.QualityOfService=EO
    XI.Client=001
    <Other parameters like InterfaceName / FCC>
    If I use XI.SLDConfiguration=SLDaccessor and XI.TargetURL=<fromSLD>, I get an error of HTTP 401 unauthorized.
    If I ignore the SLDaccessor, the message is processed successfully.
    Am I missing anything in the above configuration?
    The user id user is having the roles of SAP_SLD_CONFIGURATOR and SAP_XI_APPL_SERV_USER.
    2. Second Issue
    In RWB -> Component Monitoring -> J2SE Adapter Engine, there is an error coming up - Unable to establish connection to "https://<LocalHost>:50001/rtc"
    The port is wrong ... it should be 8200. My question is, from where to fix this?
    Any help will be highly appreciated.
    Thanks,
    Neetesh

    Hi Neetesh,
    After copying tech_adapter on your local machine douple click on run_adapter.bat and then open internet explorer and enter http://l<ocalmachine_ip_address>:8200/adapter.html
    After doing this you will get logon popup, enter user & password and configure the adapters.
    Secondly you can see the port in SLDAPICUST if I am not mistaken. (not very sure)
    Compare your configuration with below one
    file adapter java class
    classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
    version=30
    mode=FILE2XMB
    Integration Engine address and document settings (example, see docu)
    XI.TargetURL=http://<host>:8000/sap/xi/engine?type=entry
    XI.User=testuser
    XI.Password=pass123
    XI.QualityOfService=EO
    #XI.SenderParty=
    XI.SenderService=LocalSystem
    #XI.ReceiverParty=
    XI.ReceiverService=LocalSystem
    XI.Interface=IM_J2SE
    XI.InterfaceNamespace=http://abc.com/j2se/test
    ##File Adapter specific parameters (example, see docu)
    file.type=BIN
    #file.type=TXT
    file.encoding=UTF-8
    file.sourceDir=c:/sender
    file.sourceFilename=sender1.xml
    #file.processingMode=test
    file.processingMode=delete
    #file.processingMode=archiveWithTimeStamp
    #file.archiveDir=./temp_archive
    #file.retryInterval=20
    file.pollInterval=30
    Regards,
    Sarvesh

  • 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

Maybe you are looking for