PO message processing error at SOAP Adapter

Hello All,
After an PO scenarion setup and performing one messageprocessing in found following error at RW Message Monitoring:
Exception caught by adapter framework: SOAP: response message contains an error XIServer/UNKNOWN/ModuleUnknownException - com.sap.aii.af.mp.module.ModuleException: either no channelID specified or no channel found for the specified party, service, and channel name, MessageServlet(Version $Id: //tc/aii/30_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#13 $) at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:412) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_
Please could someone tell me where the problem is?
Regards,
Jochen

Hi Jochen
Check if thse threads can help you
Now based on error description -
Refer this SAP Note - 856597 QUestion no 1 -for SOAP adapter configuration- i.e URL
Also have a look into this thread-
SOAP Problem
SOAP Error when testing messages.
*************Reward points if helpfull*************

Similar Messages

Error receiving AS2 message from partner: B2B-50037: B2B inbound message processing error

B2B/SOA 11.1.1.6.0
We are setting a new trading partner and when we started document transmissions we are getting errors on the inbound messages: B2B-50037: B2B inbound message processing error.
The attachment shows the relevant lines from the soa log and diagnostic log files. Here is the error detail that shows:
[URI: /b2b/httpreceiver] Error -: B2B-50037: B2B inbound message processing error[[
Error -: B2B-50037: B2B inbound message processing error
        at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:3143)
        at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1650)
        at oracle.tip.b2b.transport.InterfaceListener.onMessageLocal(InterfaceListener.java:403)
        at oracle.tip.b2b.transport.InterfaceListener.onMessage(InterfaceListener.java:214)
        at oracle.tip.b2b.transport.basic.TransportServlet.doPost(TransportServlet.java:754)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
        at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
        at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
        at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
        at java.security.AccessController.doPrivileged(Native Method)
        at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
        at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
        at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
        at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
        at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
        at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
        at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
        at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
From the b2b_wire_message we get these Protocol_Transport_BINDINGS:
ChannelName=TransportServlet
Reverse-Via=LIN-ISA1
AS2-To=accobra.....
Date=Fri, 26 Sep 2014 05:46:17 +0000
AS2-Version=1.2
AS2-From=K.......
Disposition-Notification-Options=signed-receipt-protocol=optional, pkcs7-signature; signed-receipt-micalg=optional, sha1
Disposition-Notification-To=http://<ip&port>/as2in
Message-ID=<[email protected]>
MSG_RECEIVED_TIME=Fri Sep 26 00:46:17 CDT 2014
ECID-Context=1.0050z5j^buc6yGn6wnZf6G0002f60007bt;kXjE1ZDLIPGIj2QCYV8QoKSSmLRO_PQT_IS
Content-Type=application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7m
Proxy-Client-IP=172.17.25.101
MIME-Version=1.0
User-Agent=e-integration AS2 Server V 6.1.8
X-Forwarded-For=172.17.25.101
Content-Length=3602
Host=nalinsoa05.abd.ad.acco.com
x-weblogic-cluster-hash=QoZzGUzdcjBD5fGIE8Uos5abiHI
EDIINT-Features=multiple-attachments, CEM
Connection=Keep-Alive
X-WebLogic-KeepAliveSecs=30
X-WebLogic-Request-ClusterInfo=true
The message creates a wire message, business message, and an application message.
What doesn't happen is no MDN gets sent back to the partner. It should be a synchronous MDN.
We have double checked the certificates on both ends and they are OK.
The document and Agreement get recognized OK:
Refer To Message
Refer To Message
Sender Type
AS2 Identifier
Sender Value
K. . .
Receiver Type
AS2 Identifier
Receiver Value
accobr. . .
Sender
K. . . l
Receiver
ACCO . . .
Agreement Id
K. . .l_EDI_X12_4010_856_856Def_Inbound
Agreement
K. . .l_EDI_X12_4010_856_856Def_Inbound
Document Type
856
Document Protocol
EDI_X12
Document Version
4010
Message Type
REQ
Direction
INBOUND
State
MSG_ERROR
Acknowledgement Mode
SYNC
Response Mode
ASYNC
Send Time Stamp
09/26/2014 12:46:17 AM
Receive Time Stamp
09/26/2014 12:46:17 AM
The error is vague enough to provide little or no help in locating the root cause of the issue.
Any assistance in providing information on how to get this working would be greatly appreciated.
We do have dozens of other AS2 partners working in this instance just foe reference. We are just having issues with this new partner setup.
Thank you.
Regards,
Ken

Ken,
I am observing the Ack Mode is set as "SYNC" . This is selected by default. This option is available in the channel configuration section
If the usecase is not SYNC, please change as ASYNC and test. It should work.

B2B-50037: B2B inbound message processing error

We are trying to implement B2B with Customer EDI X12 850 Inbound with SOA
Application server Version 11.1.1.4.0 (weblogic)
Hitting the following error in the logs
MDS-00013: no metadata found for metadata object "/soa/b2b/EDI_X12/4010/850/New/8504010Viterra.ecs"
Was successful in overcoming all the usual obstacles of finding the TP, Document Type, protocol etc...However hitting the above error. 8504010Viterra.ecs is a custom spec builder document we created and "8504010Viterra.ecs" was browsed from the windows PC into the Document Type B2B set up. I am willing to use a seeded ecs file but do not know how to find one for X12 850 4010 version....?
Went through one SR that asks you upload a group ECS file but that did not help in our case....Following was the SR
"B2B-50037 B2B INBOUND MESSAGE PROCESSING" Error with EDIX12 And DEF 830 VER 200\0 [ID 1357136.1]
Please help
Now at the agreement level, if we set the translate to No and Validate to No then B2B completes normally but we do want B2B to translate the file so that we can get it in XML form for us to transform and process it in BPEL
Any help or hint is really appreciated!

Anuj
THANK YOU SO MUCH!!! I cannot thank you enough for this
I was playing around so much with the document type, the protocol version etc. that i must have inadvertently messed up the repository. I took the export of the data as you suggested, purged the design repository and reimported the zip. I also had to restart the server since the ftp was not kicking in...& wholla! the message got translated into XML and went into the queue
Thanks again
Gopal Iyer
Edited by: ghiyer on Nov 10, 2011 10:07 AM

B2B-50037: B2B inbound message processing error java.lang.NullPointerException

Can anyone help me with this problem.
I'm new here.
Oracle SOA Server version 11.1.1.6.0
Got this error message after I put Ignore Correlation true.
diagnostic.log:
[2013-08-12T14:05:26.668+02:00] [MS_KETEN_SOA_01] [NOTIFICATION] [] [oracle.soa.b2b.engine] [tid: DaemonWorkThread: '17' of WorkManager: 'wm/SOAWorkManager'] [userId: <anonymous>] [ecid: 0000K1mQe8WAdL9_rdH7iY1I2CVn0000Lc,0] [APP: soa-infra] Engine: processIncomingMessageImpl: Message id = 0A253556140726AA60A000003E11ADD0-1 FromParty = JD0021_OTA Doctype = ScanDocumenten version = 1.0
[2013-08-12T14:05:26.712+02:00] [MS_KETEN_SOA_01] [ERROR] [] [oracle.soa.b2b.engine] [tid: DaemonWorkThread: '17' of WorkManager: 'wm/SOAWorkManager'] [userId: <anonymous>] [ecid: 0000K1mQe8WAdL9_rdH7iY1I2CVn0000Lc,0] [APP: soa-infra]     [[
        at oracle.tip.b2b.msgproc.Acknowledgment.createAckMsg(Acknowledgment.java:659)
        at oracle.tip.b2b.msgproc.Acknowledgment.asyncOutgoingAck(Acknowledgment.java:290)
        at oracle.tip.b2b.msgproc.Request.handleAck(Request.java:652)
        at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:3019)
        at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1650)
        at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:4042)
        at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3718)
        at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3205)
        at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:677)
        at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:211)
        at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
[2013-08-12T14:05:26.720+02:00] [MS_KETEN_SOA_01] [ERROR] [] [oracle.soa.b2b.engine] [tid: DaemonWorkThread: '17' of WorkManager: 'wm/SOAWorkManager'] [userId: <anonymous>] [ecid: 0000K1mQe8WAdL9_rdH7iY1I2CVn0000Lc,0] [APP: soa-infra] Error -: B2B-50037: B2B inbound message processing error[[
Error -: B2B-50037: B2B inbound message processing error
        at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:3143)
        at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1650)
        at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:4042)
        at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3718)
        at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3205)
        at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:677)
        at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:211)
        at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)

It is a Defect 17324828 has been created. Details for this defect maybe viewed in Oracle Support Portal , we will update you the status as soon as we have more information.
I found ,Bug 16713853 : BTMLR: IGNORE CORRELATION AS TRUE IN ADMIN COFIGURATION GIVES NULLPOINTER ERROR for this issue in 11G , As of now development team is still working to fix this , i will raise a New BUG and involve development team for this issue

EDIFACT D98A Inbound Message Processing Error

Hi
I have been setting up an EDI B2B G/W using 11g B2B PS3 (Host & Partner). I have created the ECS, XSD and XML files using the B2B Document Editor and have completed the partner setup for D98A Purchase Order.
I had the issues when I posted the PO where the Host is unable to pick up the agreements and I was getting B2B-51507 Payload Validation Error and the message was failling at the B2B Host.
Later I changed the payload in-line with the below thread and removed the Internal Properties
https://forums.oracle.com/forums/thread.jspa?messageID=11039032#11039032
upon which the messages was sent to RemoteTP but failed with B2B-50037: B2B inbound message processing error
When I analyzed further I could see the InternalPropertes sent by the Host to the RemoteTP are with empty values.
I would like to understand the point of removing the InternalProperties and why B2B Host is not sending it in the right format to the other B2B.
I am pasting the file that is been received at the RemoteTP which failed with B2B-50037: B2B inbound message processing error
<?xml version="1.0" encoding="UTF-8"?><Transaction-CONTRL xmlns="urn:oracle:integration:b2b:9FF110DDDB0C424F8B4C5A0F73EF6547" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="1.0" Standard="EDIFACT" Version="D3" CreatedDate="2013-05-31T13:41:20" CreatedBy="XEngine_2133" GUID="{65236268-C9EF-11E2-BC04-E4115BAD2692}"><Internal-Properties><Data-Structure Name="Interchange"><Lookup Name="InterchangeControlVersion">1</Lookup><Lookup Name="InterchangeReceiverID"> </Lookup><Lookup Name="InterchangeReceiverQual"></Lookup><Lookup Name="InterchangeSenderID"> </Lookup><Lookup Name="InterchangeSenderQual"></Lookup><Lookup Name="Standard">EDIFACT</Lookup><Property Name="InterchangeSyntaxVersion">1</Property><Property Name="ReleaseCharacter">0x3f</Property><Data-Structure Name="Group"><Lookup Name="GroupID">CONTRL</Lookup><Lookup Name="GroupReceiverID"> </Lookup><Lookup Name="GroupReceiverQual"></Lookup><Lookup Name="GroupReleaseNumber">3</Lookup><Lookup Name="GroupSenderID"> </Lookup><Lookup Name="GroupSenderQual"></Lookup><Lookup Name="GroupVersion">D</Lookup><Property Name="GroupID">CONTRL</Property><Data-Structure Name="Transaction"><Lookup Name="TransactionID">CONTRL</Lookup><Lookup Name="TransactionMessageReleaseNumber">3</Lookup><Lookup Name="TransactionMessageVersionNumber">D</Lookup></Data-Structure></Data-Structure></Data-Structure></Internal-Properties><Segment-UNH><Element-0062>#ControlNumber(Transaction)#</Element-0062><Composite-S009><Element-0065>CONTRL</Element-0065><Element-0052>D</Element-0052><Element-0054>3</Element-0054><Element-0051>UN</Element-0051></Composite-S009></Segment-UNH><Segment-UCI><Element-0020>1051</Element-0020><Composite-S002><Element-0004> </Element-0004></Composite-S002><Composite-S003><Element-0010> </Element-0010></Composite-S003><Element-0083>4</Element-0083></Segment-UCI><Loop-Group_3><Segment-UCF><Element-0048>1051</Element-0048><Composite-S006><Element-0040> </Element-0040></Composite-S006><Composite-S007><Element-0044> </Element-0044></Composite-S007><Element-0083>4</Element-0083></Segment-UCF><Loop-Group_4><Segment-UCM><Element-0062>1</Element-0062><Composite-S009><Element-0065>ORDERS</Element-0065><Element-0052>D</Element-0052><Element-0054>98A</Element-0054><Element-0051>AA</Element-0051></Composite-S009><Element-0083>4</Element-0083><Element-0085>18</Element-0085></Segment-UCM></Loop-Group_4></Loop-Group_3><Segment-UNT><Element-0074>5</Element-0074><Element-0062>#ControlNumber(Transaction)#</Element-0062></Segment-UNT></Transaction-CONTRL>
Has anyone encountered such issues? Is there any additional properties that are needed to be configured?
Regards
RD

Hi Anuj
this is the stack trace
<02-Jun-2013 12:50:47 o'clock BST> <Error> <oracle.soa.b2b.engine> <BEA-000000> <Error -: B2B-50037: B2B inbound message processing error
Error -: B2B-50037: B2B inbound message processing error
at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:3283)
at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1764)
at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:4179)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3855)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3328)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:610)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:192)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
the xml i posted is the one that is logged by the remote TP in the trace logs before the error occurrence,
Regards
RD

Communicating message processing errors to trading partner

Hi,
We have configured B2B to receive OAG inbound messages.
How can we communicate inbound message processing errors to the remote trading partner?
I found that we can use oag CONFIRM_BOD_004 message for that? How do we that? Do we need to create a separate agreement with the trading partner for the confirm_bod or is there any way to bind it to existing agreement?
Is CONFIRM_BOD_004 the only way of informing the trading partner or there are some other ways of doing it?
Thanks in Advance.
Anil

Hi Anil,
Oracle B2B can send two kind of acknowledgements to partner to intimate whether received message processed successfully -
1. Exchange level ack - This is supported with specific exchange protocols (AS2, ebMS, RNIF etc.) only. Generic exchange does not have this capability. To understand, how it behaves in case of inbound error, please refer section "D.5 Inbound Exception Handling Scenarios" at-
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10229/app_except.htm#BCEIEEFF
2. Functional Ack - This is supported as part of document protocol's specification. For e.g. 997 in EDI X12, CONTRL in EDIFACT and CBOD (Confirm BOD) in OAG. Oracle B2B can handle Functional ACK automatically but you have to create a document definition for the same and deploy the respective agreement. Remember, Functional Ack is generally used to communicate to partner whether received message passed the business validation.
You may refer below blog to understand difference between functional ack and exchange ack -
http://www.b2bgurus.com/2009/02/document-vs-exchange-level.html
Remember that this blog is intended for 10g so please ignore any settings defined there.
You may define at an agreement level whether FA is required and if yes then whether Oracle B2B will handle it or middleware will send it to B2B to pass it to TP. You may refer section "Step 4: Select validation, translation, and functional acknowledgment options" at -
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10229/bb_agree_flow.htm#CEGDGCAH
Regards,
Anuj

Message processing failed, FTP Receiver Adapter error...

Hello all,
We have a Idoc to File(FTP) scenario using PI.
When PI try to send the file out to the FTP site, we get the following message in the communication channel monitoring and the file never reach the FTP site:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error when getting an FTP connection from connection pool: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: ConnectException: Connection timed out: connect
When we look at the detail display, we can see that the connection as been establish with the FTP site but the adapter is unable to deliver the file...
Any Idea why?
Thanks in advance.

Hi ,
There are two things that you can do
1- check the connection of FTP from command prompt. If it is acceebile from command prompt then check for authorization that wether you have access to post the file at FTP or not (Full access READ , WRITE and EXCECUTE)
2- in your adpater change the connection mode from Per file transfer to "Permanent".
Please feel free to reply on this thread if you are not able to.
Thanks

PI 7.3 AEX - XI 3.0 message protocol in the SOAP adapter.

Hello,
My client's landscape is on SAP PI 7.3 AEX(Java only installation) and SAP ECC 6.0 EhP4.
I have configured a HTTP-Proxy scenario. For the proxy messages to go into the SAP ECC system, I have configured a SOAP Receiver adapter in PI 7.3 AEX.
I have created a service interface in ESR in PI 7.3 and generated the proxy in the SAP ECC system.
I have configured the SOAP receiver to use the XI 3.0 protocol and by using the Addressing Type as 'URL Address'. The URL that I am using is " http://<SAP_ECC_server>:PORT/sap/xi/engine?type=entry ".
When I try to test the scenario, the messages are not reaching the target ECC destination and in the SOAP Receiver communication channel, I am getting the following error:
Information:                Delivering to channel: SOAP_RECEIVER
Information:                MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
Information:                SOAP: request message entering the adapter with user Guest
Error:                          SOAP: call failed: java.io.IOException: unable to create a socket Information                 SOAP: sending a delivery error ack ...
Now, in my client estate there is also a SAP PI 7.11 system, I have replicated the service interface in the ESR on 7.11 and regenerated the proxy in SAP ECC. When I now run the scenario, it works.
Just stressing here on the point that, the abap proxy generated from SAP PI 7.3 ESR did not work(but worked when I generated the abap proxy from SAP PI 7.11 ESR) when configured using the XI protocol on the SOAP adapter.
ALso, I have gone through the 'Note 1247043 - Release Restrictions for EHP 1 for SAP NetWeaver PI 7.1'.
Is the behaviour I am facing a release restriction on SAP PI 7.3
Need suggestions from anyone who has tried configuring this scenario, is there anything that I have missed?
I am happy to share more info if required...
Thanks in advance,
Best Regards,
Karthik

HI Karthik,
Did you able to resolve this in PI 7.3??
Even i am also facing the same issue in receiver soap adapter for abap server proxy:
SOAP: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket
Please let me know how did u resolve this?
Thanks,
Prasanthi

Error Https SOAP Adapter:NoSuchAlgorithmException: No such algorithm: RSA

Hi,
I'm using a SOAP Adapter Receiver to integrate a file to an External WS (with HTTPS). But when I tried to execute It I got the following error:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Unable to encrypt preMasterSecret: java.security.NoSuchAlgorithmException: No such algorithm: RSA: iaik.security.ssl.SSLException: Unable to encrypt preMasterSecret: java.security.NoSuchAlgorithmException: No such algorithm: RSA
SOAP: call failed: iaik.security.ssl.SSLException: Unable to encrypt preMasterSecret: java.security.NoSuchAlgorithmException: No such algorithm: RSA
I think It is a problem with the creation of the secure channel of HTTPS.
Any tip is very welcome!!
Thanks
Martin

http://java.sun.com/j2se/1.4.2/docs/guide/security/jce/JCERefGuide.html#AppA
there is not much info to find about who provides for RSA.RSA is already implemented in the Crypto-Provider by Sun. You don't have to laod a special provider.
The following sample is just enough:
Cipher cipher = Cipher.getInstance("RSA");Jan

Mapping related errors in SOAP Adapter scenario

Hello Friends
I have done this several times and in this particular case I am getting some errors.
Here is the scenario
External --- (SOAP) --- XI -
(RFC) -
SAP TABLE.
Program
I have created an XSD (External definition) to get the data to XI using SOAP Adapter.
I have done the mapping and everything looks Ok to me. I even restarted my XI server. All other scenarios are working except for this particular scenario in question.
When I looked at <SXMB_MONI> I see the xml string coming in correctly with proper tags and data as expected.
However, it is failing with some mapping errors.
Here is the error message I got in SXMB_MONI
Any help will be greatly appreciated.
<Trace level="1" type="T">Interface Mapping http://cincom.com/config AddConfigDNA</Trace>
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_AddConfigDNARequest_</Trace>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:283) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</Trace>
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_AddConfigDNARequest_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd</Trace>
<Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_AddConfigDNARequest_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns1:ZBAPI_ADD_CONFIG_DNA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:283) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy177.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7701) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2376) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1700) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8061) at com.sap.mw.jco.JCO$Server.work(JCO.java:8181) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8128) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</Trace>
<Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <SAP:Payload xlink:href="cid:[email protected]">
<SAP:Name>MainDocument</SAP:Name>
<SAP:Description>Main XML document</SAP:Description>
<SAP:Type>Application</SAP:Type>
</SAP:Payload>
</SAP:Manifest>
</SOAP:Body>
</SOAP:Envelope>

Hi Ram,
This error is due to error in message mapping.The map rules you have specified for the Node: "ZBAPI_ADD_CONFIG_DNA" is not getting satisfies due to which it is unable to create the Node who occurance is mandatory.Check if map rule specified for this particular Node.
Thanks,
Bhargav.
Note:Award Points if found useful

ABAP-Proxy to SOAP: Error in SOAP Adapter

Hi!
I would like to implement ABAP-Proxy to SOAP scenario.
Unfortunately my SOAP receiver channnel has the following error:
SOAP: call failed: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200 OK
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: No SOAP Envelope but 1 definitions; HTTP 200 OK: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200 OK
Furthermore the call of /sap/bc/soap/rfc of business system B is erroneous
http://<server system B>:8000/sap/bc/soap/rfc
Here I get the error: HTTP 500 Internal Server error
Can some one help me to solve this problem?
Thank you very much!
regards
Holger

Hi,
Are you using the webservice exposed by SAP or it is third party webservice. Can you explain your complete scenario? What is the url you have given in your receiver SOAP Channel? Was that no configured earlier?
If at all you are using the SAP webservice, the wsdl link should be.
http://<server>:<http port>/sap/bc/soap/wsdl11?services=BAPI_MATERIAL_EXISTENCECHECK&sap-client=200
The target url you will be able to see in the wsdl itself also
amit

Following message failing in sender soap adapter

Hi all,
The message below fails when it is sent to our adapter with a 500 error from a webmethods server. however if I pull the soap message out of the mime, and use our client test tool, it posts fine.
What is wrong with the message below?
Message-ID:<28413146.1155935375732.JavaMail.webmethods@exshaw>
MIME-Version: 1.0
Content-Type: multipart/related; type="text/xml"; boundary=X-K12456234-X
X-K12456234---X
content-type: text/xml;charset=UTF-8
content-transfer-encoding: 7bit
Content-ID: <SES>
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/1999/XMLSchema"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance">
<SOAP-ENV:Header xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"></SOAP-ENV:Header>
<SOAP-ENV:Body>
<nr1:ServiceAcknowledgementRequest xmlns:nr1="http://sap.com/xi/SAPGlobal/Global">
        <MessageHeader>
                <ID schemeID="0240">74000003400000000020060329170547</ID>
                <CreationDateTime>2006-03-29T17:05:47Z</CreationDateTime>
                <SenderParty>
                        <InternalID schemeID="PartnerID" schemeAgencyID="SSR_100">6000000011</InternalID>
                </SenderParty>
                <RecipientParty>
                        <InternalID schemeID="PartnerID" schemeAgencyID="SSR_100">0000000236</InternalID>
                </RecipientParty>
        </MessageHeader>
        <ServiceAcknowledgement>
                <ID schemeAgencyID="SSR_100" schemeAgencySchemeAgencyID="ZZZ">7400000340</ID>
                <BuyerID>7400000340</BuyerID>
                <CreationDateTime>2006-03-29T17:03:55Z</CreationDateTime>
                <Note>Service Entry Sheet#1</Note>
                <Item>
                        <ID>10</ID>
                        <Quantity unitCode="EA">5.0</Quantity>
                        <Product>
                                <TypeCode>1</TypeCode>
                                <Note>Test Service</Note>
                        </Product>
                        <Price>
                                <NetUnitPrice>
                                        <Amount currencyCode="USD">1.0</Amount>
                                     <BaseQuantity unitCode="EA">1.0</BaseQuantity>
                               </NetUnitPrice>
                       </Price>
                       <PurchaseOrderReference>
                               <ID>2000000742</ID>
                               <ItemID>1</ItemID>
                       </PurchaseOrderReference>
                </Item>
        </ServiceAcknowledgement>
</nr1:ServiceAcknowledgementRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
X-K12456234---X

Hi Richard,
I think, it is because of the Autorization Problem..i.e
Webservice is not able to execute by SOAP adapter.. So Security Roles etc..
Check this SAP SOAP Note for FAQ-856597 (Question No 1)
A similar symptom is mentioned in this note....
Regards,
Abhy

ERROR IN SOAP ADAPTER

Hi Guys,
I am trying to send a SOAP message to an external webservice to use a proxy.
I put host and gate in receiver soap adapter.
When i execute i have the next error:
SOAP:Call Failed
SOAP:error occured:java.io.IOException: invalid content type for SOAP: TEXT/PLAIN
Has anyone got a suggestion as to how I may resolve this problem?
Thanks very much,
Antonio

Hi Antonio,
Basically the issue is with the response that the webservice is returning, it may not be a valid reposne..use the TCP-Monitor tool from SAP to see the request/response message flowing...
Please do a search onsdn itself on your issue...you should get lots of threads talking about the same problem in the XI forum...
Thanks,
Renjith

Error in SOAP Adapter Response

I am getting the following Error in SOAP Response
... but when i tried the with ALTOVA XML SPY its working fine..
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>soap fault: Registration Method error</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>

hi,
check the XML that you send to the WS
if the server returned this soap fault it might mean that XML was not correct .
also take a look at the default.trc log file from visual administrator-> server -> services -> log viewer -> locations -> com -> aii -> bc -> soap
regards
kummari
Edited by: kummari on Jul 29, 2008 5:40 AM

Messages failing in the SOAP adapter with the errror

HI
I am getting the below error in the SOAP adapter monitoring . can any body tell what does "No route to host: Connect" mean .
could some one help us on resolving this .
Error Exception caught by adapter framework: No route to host: connect
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: No route to host: connect: java.net.NoRouteToHostException: No route to host: connect. Setting message to status failed.
Error The message status set to FAIL.
Error Returning synchronous error message to calling application: com.sap.aii.af.ra.ms.api.RecoverableException: No route to host: connect: java.net.NoRouteToHostException: No route to host: connect.
thanks and regards
sandeep

Hi!
First please confirm whether you are working on XI or PI 7.1 ?
because in XI you need to generate WSDL manaually via Tools>Define Web service-Giving Input..and in XI you need to test the SOAP scenario from external tool like Altova xml spy tool kit or else SOAP client tool.
In PI 7.1::
You can publish directly the web service in the SERVICE REGISTRY from sender agreement onwards.
once it is published you can check the status on your interface in service registry as CONFIGURED..Okay
Here you can test directly in service registry...
According to your error check ocne agan even though you gone through all the steps..
1. Check whether the SOAP service is active or not in SICF>SAP>bc>XI>Service-->SOAP.
2. sicne after generating wSDL u can get one url right that URL itself acts as a gateway to enter the source data into XI..
lets give to the source team to try with XI super uID adn PWD as authentification.
3. Also please STOP ur communication Channel and start once again.
4. Please check whether the WEB Service is configured correctly or not.
Regards::
Amar Srinivas Eli

PO message processing error at SOAP Adapter

Similar Messages

Maybe you are looking for