cancel
Showing results for 
Search instead for 
Did you mean: 

Receiver Proxy via SOAP XI 3.0 protocol issue

Former Member
0 Kudos

Hi

We are on PI7.31 dual stack. I am working on a scenario where we send idocs from ECC --> PI --> GDS 2.1(Global Data Synchronization). GDS is part of MDM(if I am correct) and has it own PI7.11 Java engine. The scenario is developed using ICO on PI 7.31. ECC is pushing IDOCs using IDOC_AAE adapter to PI which is working fine. PI uses SOAP receiver adapter with XI3.0 message protocol to push data via proxy to GDS. The proxy, mappings are all pre - delivered SAP content.

Now in the Soap receiver channel we are seeing the below error

Failed to call the endpoint: Error in call over HTTP: HTTP 503 Service Unavailable

SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 503 Service Unavailable

SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 503 Service Unavailable

MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 503 Service Unavailable

Exception caught by adapter framework: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 503 Service Unavailable

We checked the url http://host:port/MessagingSystem/receive/JPR/XI and its working fine throwing below message when tested on browser

<StatusInfo>

<StatusMessage>MessagingServlet is active.</StatusMessage>

<Version>Messaging System 7.1</Version>

<Usage>

http://[host]:[port]/MessagingSystem/receive/[connection]/[protocol]

</Usage>

<RequestURL>

http://mysystem:50000/MessagingSystem/receive/JPR/XI

</RequestURL>

<Connection>

<Name>JPR</Name>

<Status>started</Status>

<Listener>registered</Listener>

</Connection>

<Protocol>

<Name>XI</Name>

<Status>EventHandler not available</Status>

</Protocol>

</StatusInfo>

We tried updating PI content for GDS, GDS core but did not work out.


We then check on NWA of GDS and see that the following applications are not working

com.sap.aii.adapter.soap.appsap.com Implicit stoppedProcess Infrastructure (PI)

com.sap.aii.adapter.soap.libsap.com Failed to startProcess Infrastructure (PI)

We tried to stop, restart the services but did not work. We restart the system, try to start the service but they are in the same state

We also noticed the following in the logs of NWA

error 2012-09-1212:47:51:979Global [startApp] operation of [sap.com/com.sap.aii.adapter.soap.lib] finished with errors for 28ms on server [1831850]. [

>>> Errors <<<

1). com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib".... [see details]com.sap.engine.services.deploy.server.TransactionManagercom.sap.engine.services.deploy.server.TransactionManagersap.com/tc~lm~itsam~ui~mainframe~wd error2012-09-1212:47:51:970Cannot bind "com.sap.aii.adapter.soap.lib".

[EXCEPTION]

com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib".... [see details]com.sap.engine.services.deploycom.sap.engine.services.deploysap.com/tc~lm~itsam~ui~mainframe~wd error2012-09-1212:47:51:968[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.ad... [see details]com.sap.engine.services.deploycom.sap.engine.services.deploysap.com/tc~lm~itsam~ui~mainframe~wd error2012-09-1212:47:51:963Access to XI AF MS resource failed.

Has any one faced this kind of situation..Can you please provide your suggestions

Guru

Message was edited by: Guru Dev

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Guru,

Some links below

http://scn.sap.com/docs/DOC-7694

http://wiki.sdn.sap.com/wiki/display/CK/Roadmap+GDS

http://www.stechno.net/sap-notes.html?view=sapnote&id=1450937

The issues seems to be some configuration issue on the GDS front. Was it working earlier any time?


Regards,
Sathya

Former Member
0 Kudos

Sathya

Thanks for the links. It did not much info about the issue. This is the first scenario for GDS. We have PI content and GDS Core as well as DDIC up to date.

Former Member
0 Kudos

Any tips?