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

<u>This is not an answer to your question.</u>
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<u></u>

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

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

  • Error in RWB - Component Monitoring - Adapter Engine

    Hi,
    After we install an Additional Application Server Instance, we are facing an issue with the Runtime Workbench, specifically with the Adapter Engine status.
    On the RWB we're have this error:
    Ping Status: Unable to establish connection to
    "http://<Additional AS Host>:<Central Instance JAVA Port>/AdapterFramework/rtc"
    All the time it's pointing to the Additional AS with the Primary AS Java Port.
    We are using a central SLD in PIP system.
    We already reviewed, the point 8.12 of the "SAP NetWeaver PI 7.1 Including SAP EHP 1 - Troubleshooting Guide"
    Any idea to solve this?
    Regards,
    GCC PI

    Hi GCC,
    Please change in the http://<host>:<j2ee_port>/exchangeProfile this settings:
    Exchange Profile
    Connections:
    - com.sap.aii.connect.directory.name
    - com.sap.aii.connect.landscape.name
    - com.sap.aii.connect.repository.name
    RuntimeWorkbench:
    - com.sap.aii.rwb.server.centralmonitoring.r3.ashost
    Please change the value in the:
    Config Tool -> cluster-data -> Global Server -> Configuration ->
    Services -> com.sap.aii.af.cpa.svc ->
       SLD.selfregistration.hostName
       SLD.selfregistration.httpPort
       SLD.selfregistration.httspPort
    Also see notes: #1113161 - Links in Component Monitoring not working
    and #764176 - Error in XI due to inconsistent SLD contents
    After that, please restart the j2ee engine.
    Regards,
    Luis Diego

  • 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

  • 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" ?>
    - <!--  Call Adapter
      -->
    - <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

  • Error when reading the access data for the Adapter Engine

    We are getting the following error in XI. It started on Jan 22 and resolved on Jan 23 automatically. Nothing has been changed and we don't able to understand how problem started and how it resolved:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
      <SAP:P1>af.xpd.dbcixpd</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>3: Unable to find URL for Adapter Engine af.xpd.dbcixpd</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine af.xpd.dbcixpd</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Pls suggest if anyone has gone thru same problem.
    Regards
    Amar

    I got the same problem while using RFC lookup.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <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.tx1.netweaver</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>3: Unable to find URL for Adapter Engine af.tx1.netweaver</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine af.tx1.netweaver</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Any idea ,when we get this error usually.

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

  • 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

  • Help!Cache status of object for Central Adapter Engine is incorrect

    this problem cconfused me several days!
    version:PI 7.1
    after i activate the communication channel, the cache not update for central adapter engine
    problem: in cache status overview, the update for central adapter engine not yet started, but notification is ok.
                     the update for integration server and mapping run time are all correct.
    then when i display wsdl for sender agreement(SOAP sender),  show message:Cache status of object abcd123 for Central Adapter Engine is incorrect
    if i ignore this message, error message popup:dapter Engine af.xid.sapittest for communication channel abcd123 not registered in SLD
    who can help me solve this problem.
    thank you in advance.

    Hi cheng,
    Kindly check if you have set theparameter 'com.sap.aii.connect.integrationserver.sld.name' in your
    Exchange Profile, since it's not set by default. Open note #1278563 and follow the procedures.
    And you may check the following notes:
    #1031321 - Self-Registration of Adapter Engine and RWB fails
    #1334053 - No automatic PI 7.10 SLD Registration (Here you'll see the note 764176 which you have already applied and also the note #1117249).
    In RWB, is the adapter Engine "red light"? If yes, what is the specific error?
    Regards,
    Caio Cagnani

  • "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
    <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,

  • 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

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

Maybe you are looking for