SOAP Adapter at XI 3.0 Central Adapter Engine

Hello,
I'm trying to use the SOAP Adapter with the Central Adapter Engine. It works with the J2SE-Adapter Engine, but not with the Central Adapter Engine.
I Get the Error: No response Available.
Perhaps someone can help me.

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

Similar Messages

Issue when receiving SOAP message with HTTPS on non-central adapter engine

Hi,
we have a central XI system (PI 7.1 EHP1 SP03) and a non-central adapter engine (XI 3.0) in the DMZ, both systems on HP-UX.
In the affected configuration scenario, a business partner is sending us IDocs (INVOIC.INVOIC01) over HTTPS with Certificate Authentication and without SOAP Envelope.
The configuration and security settings seem to be correct, because we've already received several messages successfully over this connection. Now, since several weeks no message arrives anymore in our system, while the business partner always gets a HTTP_OK_200 response. So the messages seem to be accepted by our system, but nothing is shown, neither in the MessageMonitoring or CommunicationChannelMonitoring of the Runtime Workbench, nor in the in the traces/logs of the NetweaverAdministrator (trace level = DEBUG for "com.sap.aii.adapter.soap").
I also removed the assigned user in the sender agreement which should cause a HTTP_500_error on sender side, but our business partner still got a "OK_200" notification and we didn't find any information in the trace of our system.
When using TCPGateway to trace the communication, I can see an arriving message and the response, but it's encrypted because of HTTPS.
1) Did anyone have similiar issues yet?
2) Are there any further possibilities to check if an incoming message at the SOAP adapter fails?
3) Which further trace settings can be done, to get most detailed informations about the soap traffic?
4) Is there a way to decrypt the message of the TCPGateway (e.g. with private key of server)?
I'm looking forward for any helpful hints or information!
Regards,
Juergen

Issue solved by SAP note 1115650 "J2EE Engine kernel.sda SP20 cumulative patch"

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

Non Central adapter engine error

Hi All, Here is my Scenario: Trying implement /configure Non-central adapter engine hosted separate (J2EE) server. This will be connected to XI server(Integration engine and SLD) from where messages are sent/received. When I try to post message from XI to Non_central adapter engine following is the message u201CThe requested protocol u201CXIu201D is currently unavailableu201D Then I realized there is a problem in Non-central adapter engine configuration, which will be connected to SLD and Integration engine. I can see technical system and business system in SLD for Non-central adapter engine. Following is the findings in NWA of same host where non-central adapter engine. 1) I see all J2EE services are running 2) Application u201Ccom.sap.aii.adapter.soap.libu201D is no started and status is u201Cfailed to startu201D. Later I tried to restart and following are the 4 error messages in sequence from trace file. a) Message: Access to XI AF MS resource failed. Date: 2010-07-02 Time: 22:05:15:273 Category: com.sap.aii.adapter.soap.ra.SPIManagedConnectionFactory Location: com.sap.aii.adapter.soap.ra.SPIManagedConnectionFactory.SPIManagedConnectionFactory() Application: Thread: Deploy Start Application Thread Data Source: j2ee\cluster\server0\log\defaultTrace_00.trc B) [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/com.sap.aii.adapter.soap.lib]. [EXCEPTION] com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/com.sap.aii.adapter.soap.lib]. at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:619) at com.sap.engine.services.deploy.server.application.StartTransaction.rollbackPart(StartTransaction.java:653) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:506) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) ... 8 more Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) C) Cannot bind "com.sap.aii.adapter.soap.lib";. [EXCEPTION] com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) d) Global operation [startApp] over [application] [sap.com/com.sap.aii.adapter.soap.lib] finished with errors for [16]ms on server [4796750 >>> without warnings << >> Errors <<< 1). Cannot bind "com.sap.aii.adapter.soap.lib";. -> Object with name com.sap.aii.adapter.soap.lib is already bound. 2). com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) Any of you have seen this kind of problem. Thanks Sam Edited by: sam robert on Jul 2, 2010 10:24 PM

Hi Sam,
1- What is your PI version?
2- Do you use a High Availability system?
3- Can you describe your scenario?
From the 503 error, here is a generic description:
The error message 503 Service unavailable Application stopped! is displayed.
Description:The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
u2022 Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
u2022 The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
u2022 Refer SAP Note 803145,807000,791655
Regards,
Caio Cagnani

Non Central adapter error

Hi All,
Here is my Scenario:
Trying implement /configure Non-central adapter engine hosted separate (J2EE) server. This will be connected to XI server(Integration engine and SLD) from where messages are sent/received.
When I try to post message from XI to Non_central adapter engine following is the message
u201CThe requested protocol u201CXIu201D is currently unavailableu201D
Then I realized there is a problem in Non-central adapter engine configuration, which will be connected to SLD and Integration engine. I can see technical system and business system in SLD for Non-central adapter engine.
Following is the findings in NWA of same host where non-central adapter engine.
1) I see all J2EE services are running
2) Application u201Ccom.sap.aii.adapter.soap.libu201D is no started and status is u201Cfailed to startu201D. Later I tried to restart and following are the 4 error messages in sequence from trace file.
a)
Message: Access to XI AF MS resource failed.
Date: 2010-07-02
Time: 22:05:15:273
Category: com.sap.aii.adapter.soap.ra.SPIManagedConnectionFactory
Location: com.sap.aii.adapter.soap.ra.SPIManagedConnectionFactory.SPIManagedConnectionFactory()
Application:
Thread: Deploy Start Application Thread
Data Source: j2ee\cluster\server0\log\defaultTrace_00.trc
B)
[ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/com.sap.aii.adapter.soap.lib].
[EXCEPTION]
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/com.sap.aii.adapter.soap.lib].
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:619)
at com.sap.engine.services.deploy.server.application.StartTransaction.rollbackPart(StartTransaction.java:653)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:506)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43)
at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274)
Caused by: com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";.
at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393)
at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122)
at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303)
at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502)
... 8 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343)
at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850)
at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695)
at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912)
at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487)
at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375)
C)
Cannot bind "com.sap.aii.adapter.soap.lib";.
[EXCEPTION]
com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";.
at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393)
at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122)
at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303)
at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43)
at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274)
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343)
at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850)
at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695)
at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912)
at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487)
at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375)
d)
Global operation [startApp] over [application] [sap.com/com.sap.aii.adapter.soap.lib] finished with errors for [16]ms on server [4796750
>>> without warnings <<<
>>> Errors <<<
1). Cannot bind "com.sap.aii.adapter.soap.lib";.
-> Object with name com.sap.aii.adapter.soap.lib is already bound.
2). com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";.
at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393)
at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122)
at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303)
at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43)
at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340)
at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274)
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343)
at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850)
at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695)
at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912)
at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487)
at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375)
Any of you have seen this kind of problem.
Thanks
Sam
Edited by: sam robert on Jul 2, 2010 10:24 PM

Hi Sam,
1- What is your PI version?
2- Do you use a High Availability system?
3- Can you describe your scenario?
From the 503 error, here is a generic description:
The error message 503 Service unavailable Application stopped! is displayed.
Description:The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
u2022 Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
u2022 The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
u2022 Refer SAP Note 803145,807000,791655
Regards,
Caio Cagnani

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

PI 7.11 Central Adapter Engine is not started

Hi Experts,
After active objects list, in the central adapter engine: ache update not yet started.
Looking for this error, is possible that is the RFC INTEGRATION_DIRECTORY_HMI because responde 403 forbidden,
Did you have any tips?
Thank you!
Bruno

Are you sure supplied credentials are valid for PIISUSER?
1) HTTP response does not contain a valid XML root tag or Error 'HTTP status code 400 Bad Request' while executing HTTP request (calling method 'get_status')
The error 'HTTP response does not contain a valid XML root tag' occurs when path prefix of the destination is '/dir/hmi_cache_refresh_service/ext'.
The error 'Error 'HTTP status code 400 Bad Request' while executing HTTP request (calling method 'get_status')' when path prefix is '/dir/CacheRefresh'.
Solution: Go to transaction sm59 and open destination of type 'H' INTEGRATION_DIRECTORY_HMI. Select "Connection Test". The connection test should return HTTP response 200.
Now go to "Logon & Security" tab and ensure that username and password are stored in the system. Fixing credentials should fix the problem.
Note: Credentials cannot be tested via "Connection Test" tool. If used credentials are wrong, the server simply returns login html page (using HTTP response code 200). As the login html page is not a valid cache refresh xml document, an error is shown in sxi_cache.

Purpose of having central adapter engine

What is the purpose of having Centeral Adapter Engine when any WAS 6.40 has an adapter engine that can communicate de-centrally with the IS?
Regards
chandrakanth.K

Hi Chandra,
The Adapter Engine is a separate software or software component that is automatically installed on the Integration Server. In this case, we will call it as central Adapter Engine. You can also install the Adapter Engine separately on another host. This is then a non-central Adapter Engine.
By installing the adapter engine centrally on Integration Server, all the components like adapter engine, integration engine, mapping runtime etc will be at single place which increases the preformance.
In the case of non central adapter engine, where we will install the adapter engine at another system(may be in another place) which decrease your total server performance.
thanks,
madhu

Non-central adapter engine not visable in integration builder

ls,
I have a pi system and a separate non-central adapter engine. After installing i did all the post actions including the following part:
5.13 Clearing the SLD Data Cache after Installing a Non-central Advanced Adapter Engine
When you have installed a non-central Advanced Adapter Engine, you need to manually clear the SLD Data Cache in the Integration Builder to make it visible and selectable in the communication channels.
Procedure
1.
After SAPinst has finished, open the Integration Builder of your PI system at http://<host>:<port>/dir/start/index.jspIntegration Directory and logon as a user with the ABAP role SAP_XI_CONFIGURATOR assigned.
2.
In the Integration Builder, choose Environment.
3.
From the drop-down list, choose Clear SLD Data Cache.
(as described in: Installation GuideAdapter Engine (Java EE) 7.1 Including Enhancement Package 1 on Windows: MS SQL ServerTarget)
However when creating a communication channel in the integration builder there is only the central adapter engine to choose in parameter tab screen.
I was hoping maybe some-one knows what else need to be done to make de non-central known as adapter engine.
thanks in advance
Peter

HI,
with user PIDIRUSER i was indeed able to refresh the af cache. Unfortunately without a positive
Under the runtime workbench (http://<host>:<port>0/rwb/index.jsp) tab sld registration i don't see the ae neither under non-central components. If i try to register i get:
Registration of Adapter Framework with SLD was successful
Registration of fix AF adapter services with the SLD was successful
Registration of dynamic CPA cache based AF adatper services with SLD was successful
but no AAE...although it is visible in the SLD under technical systems...

Configuration of JMS Adapter in Central Adapter Engine

Hi all,
I have configured Sender JMS Adapter in Central Adapter Engine with the following parameters:
Adapter type : JMS
Transport Protocol : WebSphere MQ (non-jms)
Message Protocol : JMS1.x
Adapter Engine : Integration Server
Queue Connection Factory java class :Com.ibm.mq.jms.MQQueueConnectionFactory
Queue java class : com.ibm.mq.jms.MQQueue
ipadd : localhost
port : 1414
Queue Manager name : TEST.QMGR
Channel Name : CH1
JMS Queue : LQ
CCSID : 437
Protocol : TCP/IP
JMS-compliant : WebSphere MQ(non-jms)
JMS Queue user : MUSR_MQADMIN
Mapping of message : Entire Message = JMS Payload
But the status is red with an error message Sender Details : NULL
Could you please tell me what went wrong?
Regards
Sathya

Hi,
Make sure that Websphere MQ server is running.
If u r comfortable with java, you can even write a Java code to acces the server and check if the JMS server is working fine. Some times there will be sample applications provided by Websphere MQ itself.
Once the java program works then it will be easy to debug the error over here.
Regards,
P.Venkat

File adapter on a Non-Central adapter issue.

Hi,
We are running PI 7.10 SP 7. We have installed and configured an additional local/non-central adapter in our DMZ.
We are able to see the local/non-central adapter engine in the RWB and also in IR.
We have configured the file adapter to use the local/non-central in IR. When we place a file in the path of the file adapter then we get the following error in the Channel Monitor of the RWB.
2009-01-15 11:40:51 Error File "
hostname\XIQ\EN_JIAFS_1000005455_20090114.txt" - archiving after processing failed - retry.
2009-01-15 11:40:53 Error Transmitting the message to endpoint http://hostname:8101/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.net.UnknownHostException: CTSAPXID01.
I think one of the issues is that the hostname has to be a full network name, but am not sure where this should be changed.
Any assistance in this regard will be highly appreciated.
Regards
Willie

Hi Michal,
Thanks for the help. That seems to work. However I have now another problem. When the file adapter is trying to archive or delete the file then an error is generated within the channel monitoring.
We have given full control to the user that the sap service for the non-central adapter is running on the service it is running on. See error below.
2009-01-16 15:34:09 Error File "
ENETUTIL01\XIQ\EN_JIAFS_1000005458_20090116_2.txt" - deleting after processing failed - retry.
Any idea around this?
Regards
Willie

PI: Non-Central to Central Adapter Engine

Hi all.
I've a question for you: I've a new Non-Central Adapter Engine and I need to change it in a Central Adapter Engine.
I hope that I didn't reinstall the PI Istance...
Could you help me?
Thanks you, PI Gurus...
Bye
Manuel

The systemist had installed the WAS again

Non-Central Adapter User Store

Hi,
We have SAP PI 7.10 SP6 installed. We also installed a non-central adapter in the DMZ. We would like the non-central adapter to use/share the ABAP user store of the central adapter engine.
To this end I have created 2 RFC destinations in NWA, I18NBackendConnection and UMEBackendConnection to point to the ABAP host and client of the integration server and the central adapter engine.
Please can you advise if this is all that is required and what the port is that this is taking please on as to have that port opened on the FW.
Any help is most appreciated.
Regards
Willie Hugo

Hi Abhishek,
Thanks for the prompt reply. I have tio stipulate that I have successfully connect the non-central adapter to the IS/Central adapter engine. I am able to see it as an additional adapter engine in RWB and in ID. I can also deploy an adapter to the non-central adapter engine. At this point it is a file adapter. We can drop files in the file adapter folder deployed on the non-central adapter engine and bring the transaction file into the IS. When it comes to monitoring the file adapter in the channel monitoring, I have to use a diffrent user name and password on the non-central adapter engine. This is where my problem lies. I would like to use the user store of the ABAP IS.
I am not sure the note would help with that?
Please can you confirm.
Regards
Willie Hugo

ADAPTER in the Central Adapter Engine

Hello
I have problem with my Adapter in the Central Adapter Engine. There are to adapter inside, a JMS and A JDBC. This two adpater have in the monitoring status green. But JMS adapter get no message in the system, and by the JDBC adapter the select is not getting Data, but the update make it the right update to the databank. Can somebody help or gives there a log on the system.
Regards Thomas Neuhaus

Hi Thomas,
I think you are using Message Monitoring transaction SXMB_MONI only.
Central Adapter Engine log:
Start Runtime Workbench (i.e. http://<xi_host>:<j2ee_port>/rwb/index.jsp)-> Message Monitoring -> select Component af... -> Display -> select Period -> Start
Regards,
Jiri

"Non-Central Adapter Engines" in RWB

Hi.
We install XI system and we changed host name according to notes 757692.
After then, We found one problem in RWB.
When we run Component Monitor in RWB, Adapter engine is in "Non-Central Adapter Engines".
Why Adapter engine is in "Non-Central Adapter Engines" node ?
Any ideas ?
Regards, Arnold.

Hello Sonali
This is most likely caused by errors registering the XI components in the SLD. Apply the notes below:
#764176 Error in XI due to inconsistent SLD contents
#1117249 Incomplete Registration of PI components in SLD
#1334053 No automatic PI 7.10 SLD Registration
Also search the forum for similar issues registering the adapter engine in the SLD components.
Regards
Mark

SOAP Adapter at XI 3.0 Central Adapter Engine

Similar Messages

Maybe you are looking for