XI3.0: SOAP-Adapter Exception
Hi All,
I'm trying to send a message to a web service via the SOAP adapter.
Unfortunately the SOAP adapter throws the following exception:
<i>
SOAP: error occured: com.sap.aii.messaging.srt.BubbleException: Failed to call the endpoint: HTTP 0 null [null "null"]; nested exception caused by: java.net.SocketException: Connection timed out:could be due to invalid address
</i>
It seems to be that the configured URL does not reach the SOAP adapter.
We use the central J2EE Adapter Engine.
Any hints?
How do I sitch on detailed tracing or logging for the SOAP Adapter? The Audit Log does not contain very much information.
I hope anybody is able to help.
Regards,
Marc
Hi Alessandro,
we solved the problem.
The problem was caused by a firewall. The used port was blocked there. We just reconfigured the firewall and all went fine.
In the meantime I learned somthing about the error message.
"Failed to call the endpoint: HTTP 0 null"
This means that the adapter called the configured endpoint. The "HTTP 0 null" is the result code and error text of the http call. So it returned with error code "0" and it has no associated error text "null".
Another hint that may help you is the OSS note 761921. This note describes how to get an adapter trace.
Hope this reply helps.
Regards,
Marc
Similar Messages
-
Hi Everyone,
I tried to implement the following scenario SOAP--> XI --> IDOC(R/3). I created all the necessary objects,mapping, Channels. When tried to check the SOAP adapter with http://<hostname>:50000/XISOAPAdapter/MessageServlet?channel=:<service name>:<channelname>, i got the reply as Message STATUS OK.
But when i checked the http://<hostname>:50000/XISOAPAdapter/HelperServlet?action=FindChannel&%20channel=:<service name>:<channelname>. i got the following error
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
- <detail>
- <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context>XIAdapter</context>
<code>ADAPTER.SOAP_EXCEPTION</code>
- <text>
- <![CDATA[
java.lang.Exception: <b>invalid channel</b> (party:service:channel) = <null>
at com.sap.aii.af.mp.soap.web.HelperServlet.processFindChannel(HelperServlet.java:364)
Then i used the "MESSAGE Interface" created by SAP to created a new channel and made respective setting. Even then i am getting the same error.
Can any one tell me how to proceed.
Thank you
BhaskarHi Everyone,
It is my mistake, I entered the space between the "Find Channel" and "Channel" in the following URL
http://<hostname>:50000/XISOAPAdapter/HelperServlet?action=FindChannel&%20channel=:<service name>:<channelname>
By removing that it worked fine.
Regards
Bhaskar -
Receiver SOAP Adapter Exception
Hi,
I have a SOAP-Receiver set up in directory. Tested the WS using SoapUI 3.5 tool and got a proper response.
Now when i test the same in RWB, i get the following exception:
- <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: Server was unable to process request. ---> Object reference not set to an instance of an object.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I checked the Communication Channel monitor, it shows the same error message above but on the 'MessageContent' tab i do not see my payload, instead i only see a soap document.Actual Payload from RWB,
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_PORequest xmlns:ns0="http://bancousa.com/sapr3/fi/transdata/PegasoFactura">
<PORequest>
<RequestCFD version="1.0">
<Comprobante version="2.0" subTotal="199467.00" total="231381.72" formaDePago="Pago en una sola exhibicion">
<Emisor rfc="MMM041206JDA">
</Emisor>
<Receptor rfc="AMG0608239L9" nombre="AGENCIA MX-5, S.A. DE C.V.">
<Domicilio calle="BLVD. PEDRO INFANTE" colonia="DESARROLLO URBANO PLAN 3 RIOS" municipio="CULIACAN" estado="SINALOA" pais="MEXICO" codigoPostal="80220" noExterior="2619"/>
</Receptor>
<Conceptos>
<Concepto cantidad="1" noIdentificacion="JM1BL1S50A1256617" descripcion="VALOR DE LA UNIDAD BASICA" valorUnitario="196102.00" importe="196102.00" unidad="PIEZA">
<Parte cantidad="1" descripcion="AT2-AUTOMATIC TRANSMISSION" valorUnitario="0.00" importe="0.00" unidad="PIEZA">
</Parte>
<Parte cantidad="1" descripcion="WHEEL LOCKS" valorUnitario="0.00" importe="0.00" unidad="PIEZA">
<InformacionAduanera numero="95137889000191" aduana="LAZARO CARDENAS" fecha="2010-04-20">
</InformacionAduanera>
</Parte>
</Concepto>
<Concepto cantidad="1" descripcion="GASTOS DE TRASLADO" valorUnitario="2200.00" importe="2200.00" unidad="PIEZA">
</Concepto>
<Concepto cantidad="1" descripcion="SEGURO DE TRASLADO" valorUnitario="1165.00" importe="1165.00" unidad="PIEZA">
</Concepto>
</Conceptos>
<Impuestos totalImpuestosTrasladados="31914.72">
<Traslados>
<Traslado impuesto="IVA" importe="31914.72" tasa="16.00"/>
</Traslados>
</Impuestos>
<Addenda>
<AddendaEmisor>
<RequestForPayment>
<AddendaEmisorFactAuto moneda="MXN" claveVehicular="590108" colorExterior="4K BLANCO CRISTAL PERLADO" colorInterior="B59 NEGRO" financiera="banco FINANCIAL SERVICES" descripcionAuto="2010/BANCO 4 CILINDROS" numSerie="JM6BL15739A1256617" leyendaDocto="PAGO EN UNA SOLA EXHIBICION" noReferenciaInterno="1000000262MX102005" nombreVendedor="BANCO DE MEXICO DE R.L. DE C.V."/>
</RequestForPayment>
</AddendaEmisor>
</Addenda>
</Comprobante>
<Transaccion id="1000000262MX102005"/>
<TipoComprobante nombre="Factura de Autos" clave="EMMV">
</TipoComprobante>
<Sucursal nombre="MATRIZ">
</Sucursal>
</RequestCFD>
</PORequest>
</ns0:MT_PORequest>
This is how my payload shows in SoapUI:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:emis="http://www.pegasotecnologia.com/webservices/emision/">
<soap:Header/>
<soap:Body>
<emis:emitirCFD>
<!Optional:>
<emis:PoRequestCFD>
<RequestCFD version="1.0">
<Comprobante version="2.0" subTotal="199467.00" total="231381.72" formaDePago="Pago en una sola exhibicion">
<Emisor rfc="MMM041206JDA">
</Emisor>
<Receptor rfc="AMG0608239L9" nombre="AGENCIA MX-5, S.A. DE C.V.">
<Domicilio calle="BLVD. PEDRO INFANTE" colonia="DESARROLLO URBANO PLAN 3 RIOS" municipio="CULIACAN" estado="SINALOA" pais="MEXICO" codigoPostal="80220" noExterior="2619"/>
</Receptor>
<Conceptos>
<Concepto cantidad="1" noIdentificacion="JM1BL1S50A1256617" descripcion="VALOR DE LA UNIDAD BASICA" valorUnitario="196102.00" importe="196102.00" unidad="PIEZA">
<Parte cantidad="1" descripcion="AT2-AUTOMATIC TRANSMISSION" valorUnitario="0.00" importe="0.00" unidad="PIEZA">
</Parte>
<Parte cantidad="1" descripcion="WHEEL LOCKS" valorUnitario="0.00" importe="0.00" unidad="PIEZA">
<InformacionAduanera numero="95137889000191" aduana="LAZARO CARDENAS" fecha="2010-04-20">
</InformacionAduanera>
</Parte>
</Concepto>
<Concepto cantidad="1" descripcion="GASTOS DE TRASLADO" valorUnitario="2200.00" importe="2200.00" unidad="PIEZA">
</Concepto>
<Concepto cantidad="1" descripcion="SEGURO DE TRASLADO" valorUnitario="1165.00" importe="1165.00" unidad="PIEZA">
</Concepto>
</Conceptos>
<Impuestos totalImpuestosTrasladados="31914.72">
<Traslados>
<Traslado impuesto="IVA" importe="31914.72" tasa="16.00"/>
</Traslados>
</Impuestos>
<Addenda>
<AddendaEmisor>
<RequestForPayment>
<AddendaEmisorFactAuto moneda="MXN" claveVehicular="590108" colorExterior="4K BLANCO CRISTAL PERLADO" colorInterior="B59 NEGRO" financiera="banco FINANCIAL SERVICES" descripcionAuto="2010/BANCO 4 CILINDROS" numSerie="JM6BL15739A1256617" leyendaDocto="PAGO EN UNA SOLA EXHIBICION" noReferenciaInterno="1000000262MX102005" nombreVendedor="BANCO DE MEXICO DE R.L. DE C.V."/>
</RequestForPayment>
</AddendaEmisor>
</Addenda>
</Comprobante>
<Transaccion id="1000000262MX102005"/>
<TipoComprobante nombre="Factura de Autos" clave="EMMV">
</TipoComprobante>
<Sucursal nombre="MATRIZ">
</Sucursal>
</RequestCFD>
</emis:PoRequestCFD>
</emis:emitirCFD>
</soap:Body>
</soap:Envelope> -
SOAP Adapter: Exception in method process
Hello Experts,
We are getting from time to time on the Receiver SOAP Communication Channels the folowing error:
Delivery of the message to the application using connection AFW failed, due to: Exception in method process.
We are getting this error on both types of messages - sync and async.
I did a search on SDN and Notes, but didn't found any description or solution for this error.
Can someone please help with this error?
Thanks in advance!Here are some details extracted from the log:
Date : 07/30/2008
Time : 8:44:15:783
Message : Error during processing local bean: localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
Severity : Error
Category :
Location : com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(String , ModuleData)
Application : sap.com/com.sap.aii.af.app
Thread : output
Datasource : 1217412862462:/usr/sap/xxx/xxx/j2ee/cluster/server1/log/defaultTrace.trc
Message ID : 001CC4B7988E00A5000268B100000CB3000453381549AFAE
Source Name : com.sap.aii.af.mp.ejb.ModuleProcessorBean
Argument Objs :
Arguments :
Dsr Component : xxx
Dsr Transaction : 989219405e0211ddc88b001cc4b7988e
Dsr User : Guest
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives :
Resource Bundlename :
Session : 0
Source : com.sap.aii.af.mp.ejb.ModuleProcessorBean
ThreadObject : output
Transaction : SAP J2EE Engine JTA Transaction : [2dffffff91ffffffbdffffffe3040ffffffb0]
User : J2EE_GUEST
Hope this will help somebody to get the clue what is causing this error. -
Receiver SOAP adapter in XI 2.0
We are using receiver SOAP adapter in XI 2.0 and 4.6C R/3 system. Recently we started having this problem when vendor upgraded their webmethod server to post invoices to our XI 2.0. When vendor post 10 invoices to XI and all are posted good in XI but some of invoices give the bad response to the vendor's server as below and vendor's server keep posting the invoices with the bad response until they get good response.
<value name="soapResponseData"><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: response is not an HTTP response</faultstring></SOAP:Fault></SOAP:Body></SOAP:Envelope></value>
Any help on this is appreciated...
Thanks in advance!
Mrudulahi,
Check these threads, might be helpful.
Soap Adapter
XI3.0: SOAP-Adapter Exception
Thanks,
Tirumal -
Exception while posting a message using SOAP adapter
Hi
We are getting the following message while posting a SOAP request through SOAP adapter through Http Client. The error message is
<SAP:Error>
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code>MESSAGE.GENERAL</SAP:Code>
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML</SAP:AdditionalText>
</SAP:Error>
Please help in this regard.
Regards
RameshDear Gopal,
I am trying from HTTP->WEB SERvice (R/3 system)
I have created a webservice from RFC.
Receiver Adapter type : SOAP
USer authentification provided
URL provided. i picked from wsdl file
i am getting this error
com.sap.aii.af.ra.ms.api.DeliveryException : invalid content text/html.
I hope u trouble shooted this kind of error.
can u provide me some clues.
regards
chandra
Message was edited by:
chandra shekar dasari -
Soap receiver adapter exception
Hi,
I am using SOAP receiver adapter to access a web service that is hosted on SAP Web AS (in this case it is the integration server Web AS). I use the web services navigator to test the web service and the web service works fine. The name of the web service is 'RemoteCrossReferenceProcessor' and it has one operation 'crossReference'.
But with the soap adapter, I am getting OperationNotFoundException in the logs and my web service is not getting accessed. Here is the server log:
<u><i>An error occurred while processing the message security. Reason: . See trace entry .#3#com.sap.engine.interfaces.webservices.runtime.OperationNotFoundException#Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:RemoteCrossReferenceProcessor'; Key name:'SoapRequestWrapper' key value:'crossReference'; #[no trace for com.sap.security.core.server.ws.service.ServerSecurityProtocol (severity above PATH)]#
#1.5#0003BA0FF9EA0022000000840000688D0003F9349A3C2D61#1118429251382#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage)######b40aca80d9be11d994360003ba0ff9ea#SAPEngine_System_Thread[impl:5]_47##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: NO_BACK_SYSTEM_IN_HOPLIST:#http://sapsand1:8000/sap/xi/engine?type=entry#</i></u>
Here is adapter configuration:
Transport Protocol:HTTP
Message Protocol:SOAP 1.1
Adapter Engine:Integration Engine
Target URL: http://<server_name>>:50000/RemoteCrossReferenceProcessor/Config?style=document
User:
Password:
Default SOAP Action:
I imported the WSDL into the external definition and used the messages from the WSDL for defining my interface mappings.
I am using XI 3.0 SR1 (SP 09).
I am out of ideas as to why the SOAP adapter is not calling my web service. Please help me with your suggestions.
Thanks and Regards.HI Dani,
I was looking for this error and I found this post AXIS SOAP Receiver. This post says about other errors, but sugests many ideas to found the soluction, like:
1- non-deployed all AXIS jars; (but in this case it deployed all)
2- Exists this note for one erro in AXIS: (https://service.sap.com/sap/support/notes/1028961).
3- this document (http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b092777b-ee47-2a10-17b3-c5f59380957f) that have sets for header parameters. This is interesting becouse one of this parameters is obligatory but isn't filled, can occur error like "null object".
By the way, you can check if have update to AXIS (http://ws.apache.org/axis/), becouse isn't a SAP application and in other systems can have this error.
I hope this helps,
Romerito Silva -
SOAP adapter in XI3.0 using J2EE adapter engine
Folks,
I have a scenario SOAP client -> XI 3.0
I am using XI 3.0 and the J2EE adapter framework to configure a sender SOAP adapter. I do not have a Party, just the service and the channel.
I tried using the following url format:
http://<server>:50000/XISOAPAdapter/MessageServlet?channel
=:<service name>:<channel name>
When I use this in my SOAP client , I get an 401 forbidden error in the browser. However when I type this url directly in the browser and I get:
Message Servlet is in Status OK
Status information:
Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#5 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal is Instance of com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0
ModuleProcessorRemote not instantiated
A couple of questions:
1. Inspite of configuring the sender SOAP adapter, the sender service and the interface, I still cannot see the green light for the SOAP adapter in rumtime workbench->adapter monitoring.
Although the communication channel (in intergration builder- design)shows the status of the adapter as "active"
Does this mean that my SOAP adapter is correctly configured and active?
2. The above mentioned url takes the ABAP engine login/password while the J2EE engine (AFW)takes a different login/password. Which authentication should the SOAP client use?
Thanks for your help!
ShaileshPost your message to following URL:
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
port is the J2EE port 50000 in your example.
Check the newest manual for further details.
Regards
Stefan -
Socket time out exception in Reciver Soap Adapter
Dear friends,
I have one errror in Soap Reciever adapter as follows:
"java.net.SocketTimeoutException: Read timed out"
Scenario:
From Portal the data is posted to siebel system
Portal -
> PI -
> Siebel
Adapter: Sender Soap Adapter & Receiver soap adapter
It is Synchronous Interface.
When the Customer is going to siebel system via PI for validation.It is reaching SIEBEL.
From siebel the response message iS not coming back.... it is happening randomly ...
At that point we are getting error message as follows:
"java.net.SocketTimeoutException: Read timed out"
How can we resolve this ..freinds...Hi,
Ask your Siebel guys to check the application in which your SOAP msg is going........i think the application is throwing some error while processing your SOAP req msg and so it is not able to send a response msg to PI..........
Moreover, just check if your source msg size is too large and it is getting timed out in Siebel application while reading your req msg - if this is the case, then ask your Siebel guys to increase some timeout parameter in Siebel system for processing of your SOAP req msg...........but if it is not the case, then ask your Siebel guys to check their application as i suggested above.........
Regards,
Rajeev Gupta -
Soap Adapter meta data is not available in XI3.0
Hi,
We are not getting SOAP Adapter meta data in Integration Builder. Inspite of that we have imported package as the XI content for Software version SAP Basis 6.4 (XI3_0_SAP_BASIS_6.40_00_00.tpz).
When we configuring one of our business scenario using SOAP Adapter. Integration Builder (Configuration), In Communication channel, Adapter type SOAP is not appearing.
Any idea on this?
System:
XI 3.0, SP 10, OS: WINDOWS 2000
Regards,
Rohit GoyalPl check in the back end table at R3 side whether there is any records there or not and check with the functional team that they have entered data.
If data is there then initialize the set up tables and then check in RSA3
Thanks
Shivani -
Soap Adapter not Picking up files from sender
Hello All,
I have configured a SOAP Adapter and started it. When i place a file in the appropriate directory, it is not getting picked up. Are there any reasons this could happen ?
I would really appreaciate it if someone can help me with this !!!
Below is the log:
17:26:27 (3812): Enabling service ToWS
17:26:27 (3812): Enabling service FromWS
17:26:27 (3823): SOAP adapter initialized
17:26:27 (3830): Starting the server at 8660:/XIservices/MXS/xmb
17:26:27 (3830): Starting the server at 4444:/XIservices/MXS/ws
17:26:27 (3807): SOAP adapter started
Below is part of the config file:
The port and path where the adapter waits for web service messages from clients.
XMBWS.WSPort=4444
XMBWS.WSPath=/XIservices/MXS/ws
XMB.SenderBusinessSystem=WLX_100
#XMB.ReceiverBusinessSystem=MD1_400
XMB.User=XIAPPLUSER
XMB.Password=********
XMB.Client =100
XMB.Language=EN
XMB.SenderInterfaceNamespace=http://xi.sap.com/wlx
XMB.ReceiverInterfaceNamespace=urn:sap-com:document:sap:idoc:messages
XMB.SenderInterfaceName=ProcesseFT
XMB.ReceiverInterfaceName=Z_SERVICE_ENTRY.ZSERVICEENTRY01
XMB.TraceLevel=0
XMB.LoggingLevel=0
XMB.QualityOfService=EO
XMB.ContentType=text/xmlHi,
If you are using a Stand-alone J2SE Adapter Engine, you can create a SOAP adapter to pick a SOAP message from a file system and send it to the Integration Server. This is available with the XI3.0.
The configuration will look like this.
Bubble adapter java class
classname=com.sap.aii.messaging.adapter.ModuleBubble
This adapter instantiates a bubble bag for supporting
a soap file upload and sender. 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.ModuleBubbleHelperSOAPFileSenderImpl
#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
Below this line are the parameters specific to the ModuleBubbleHelperSOAPFileSenderImpl
#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
This module loads files from the local file system, consruct SOAP messages
(or SOAP with Attachments messages), and send them to the specified Web Service target URL.
Upon successful completion, response messages are stored in the file system.
Files stored can represent a plain payload, a SOAP envelope, or a SOAP with Attachments.
Plain payload files and SOAP envelope files may be packaged in MIME using some MIME headers.
SOAP with Attachments files must be packaged in MIME.
Specifies the type of the file. The available values are:
plain for plain; soap for soap envelope; swa for soap with attachments
SFSender.ContentMode=soap
Specifies the packaging
true for MIME packaged file; false for bare content
SFSender.MIMEPackaged=true
log everything (4-digit binary, where the bits indicate which
information is logged: req message, req context, resp request, resp context)
SFSender.Log=1111
The target URL to which messages are sent.
SFSender.TargetURL=http://p28848:4040/mysoaphandler
The upload directory on the local file system
This directory has six sub directories with names 0, 1, 2, 3, 4, 5, and 6. (they will be created)
The meaning of each sub directories are:
0 = inbox where you place messages to be sent
1 = trash box
2 = work box
3 = successfully completed (original) messages go in
4 = response messages come in (if any)
5 = undelivered (original) messages go in
6 = error messages come in (if any)
In these directories, the file names are used as key and there can be only one file with
the same name except in the trash box. So, when you place in the inbox a file with
the name identical to one of the files stored in another directory, it will not processed.
SFSender.Directory=/tmp/sfsender
The polling interval in milliseconds (default is 5000)
#SFSender.PollingInterval=5000
The retry delay after each failure in milliseconds (default is 5000)
#SFSender.RetryDelay=5000
The maximal retry count upon failures (default is 3)
After the maximal retry count is reached, the message is moved as undelivered.
#SFSender.RetryCount=3
The number of dispatchers to send requests (default is 3)
SFSender.DispatcherCount=1
END
Hope this helps.
@Ravi: You may call me at +91 9844167672.
Warm regards,
Venki. -
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 -
Error while invoking the ABAP Proxy via SOAP Adapter
Hi,
My scenario involves SOAP Client invoking a webservice hosted in PI which in turn invokes the ABAP Proxy asyncronously.
SOAP Client -> PI -> ECC (ABAP Proxy) . This works fine.
Next , I have exposed the ECC Service Interface as webservice using SOA Manager transaction. Now, once the service is created using SOAManager, i replaced the XI Adapter with SOAP Adapter and provided the target URL as the URL provided by the SOAManager.
SOAP Client -> PI -> ECC (ABAP Proxy via SOAP Adapter)
With this approach, i am encountering the below error message
2009-05-29 12:17:55 Error Adapter Framework caught exception: null
2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
Any ideas on the above errror message? Any pointers or inputs will be appreciated.
Thanks,
Vinayak Kamath> 2009-05-29 12:17:55 Error Adapter Framework caught exception: null
> 2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
This is a generic error message which does not have any information about the error which has occurred.
Do you see any error messages in the SOAP client?
Regards
Stefan -
Error while Testing SOAP Adapter In XI
<b>Hi Frndz
I am trying to test my SOAP adapter which i have exposed as a webservice. I testing this from the WSNavigator which throws the following error:</b>
HTTP/1.1 500 Internal Server Error
Connection: close
Set-Cookie: <value is hidden>
Set-Cookie: <value is hidden>
Server: SAP J2EE Engine/6.40
Content-Type: text/xml; charset=utf-8
Date: Thu, 15 Dec 2005 12:24:19 GMT
<?xml version='1.0'?>
<!-- see the documentation -->
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
<detail>
<s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
<context>XIAdapter</context>
<code>DeliveryException</code>
<text><![CDATA[
com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 404 : Not Found
at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:144)
at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:512)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:74)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:141)
]]></text>
</s:SystemError>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
<b>I have used this url for the Webservice:</b>
<u>http://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:CVXSABSR_TEST_SENDER:CVXSACC_TEST_SENDER</u>
<b>I am unable to figure out where the problem is.
Any ideas to solve this?
Thanks in Advance
DhanyaR Nair</b><b>Hi Andrews and Ravi
Thanks for the quick response.
<u>Andrews</u> the Message Servlet is in OK status, as it reponded from checking the url given by you.
What should i try next?
<u>Ravi</u> i checked the url for checking the Comm Channel. There are two IDs associated with the Channel
1>Object ID
2> ObjectVersion ID
with the ObjectVersionID , we are getting the following error and with ObjectID we got the proper response </b>
<b>with ObjectVersion ID</b>
<u>http://<host>:<port>//XISOAPAdapter/HelperServlet?action=GetChannelInfo&channelID=<Object version ID></u>
<b>response:</b>
<?xml version="1.0" ?>
- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
- <detail>
- <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context>XIAdapter</context>
<code>ADAPTER.SOAP_EXCEPTION</code>
- <text>
- <![CDATA[
com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Channel object with Id Channel:a9f7f390671e11daa2300012799e22c2 not available in CPA Cache.
at com.sap.aii.af.service.cpa.LookupManager.getCPAObject(LookupManager.java:202)
at com.sap.aii.af.mp.soap.web.HelperServlet.processGetChannelInfo(HelperServlet.java:455)
at com.sap.aii.af.mp.soap.web.HelperServlet.doGet(HelperServlet.java:131)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
]]>
</text>
</s:SystemError>
</detail>
</SOAP:Fault>
<b>with the object id</b>
<u>http://<host>:<port>/XISOAPAdapter/HelperServlet?action=GetChannelInfo&channelID=<Object ID></u>
<b>Response</b>
<?xml version="1.0" ?>
- <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
<channelID>ea30ed2ccc243fe49b7c2c5646ed3b2d</channelID>
<name>CVXSACC_TEST_SENDER</name>
<type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
<direction>INBOUND</direction>
<party />
<service>CVXSABSR_TEST_SENDER</service>
</s:ChannelInfo>
<b>with the url</b>
<u>http://<host>:<port>/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:CVXSABSR_TEST_SENDER:CVXSACC_TEST_SENDER</u>
<b>Response</b>
<?xml version="1.0" ?>
- <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
<channelID>ea30ed2ccc243fe49b7c2c5646ed3b2d</channelID>
<name>CVXSACC_TEST_SENDER</name>
<type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
<direction>INBOUND</direction>
<party />
<service>CVXSABSR_TEST_SENDER</service>
</s:ChannelInfo>
<b>How should i proceed ? Any idea frndz
Thanks in Advance
DhanyaR Nair</b> -
Error in while calling a Soap Adapter using the UDF
hi,
i am trying to make a call to Soap Adapter using a UDF.
The code of the UDF is as follows :
InputStream isPayloadStream = null;
AbstractTrace trace= container.getTrace();
String sService="Business Component";
String sChannelName="Soap Channel(Sender)";
SystemAccessor accessor=null;
trace.addInfo("entered UDF");
StringBuffer sb = new StringBuffer(" ");
trace.addInfo("creating the reference file");
sb.append("<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n");
sb.append("<ns0:MT_123082_UDF xmlns:ns0=\"http//infosys.com/pi/projects/png/n1\">\n");
sb.append("<INTERCHANGECONTRLNOS>" + var1 + "</INTERCHANGECONTRLNOS>");
sb.append("<PGPARTNERID>"var2"</PGPARTNERID>""\n""</ns0:MT_123082_UDF>");
trace.addInfo("trigerring the SOAP channel ");
try{
Channel channel = LookupService.getChannel(sService,sChannelName);
accessor = LookupService.getSystemAccessor(channel);
isPayloadStream = new ByteArrayInputStream((sb.toString()).getBytes());
trace.addInfo("creating the xml payload ");
XmlPayload payload = LookupService.getXmlPayload(isPayloadStream);
Payload result=accessor.call(payload);
catch (Exception e){
trace.addInfo(e.getMessage());
finally{
if ( accessor !=null) {
accessor.close();
return " ";
The above code is throwing an error while end to end testing.
the scenario is such,while graphical mapping a UDF will be used, which will create an Xml payload, and send this payload to another SOAP to file scenario.
The error in the sxmb_moni is: "Error when calling an adapter by using the communication channel CC_123085_UDF_SOAP_OUT (Party: , Service: BC_123082_REMADV_D96A, Object ID: fa9c6ee15efc30c68ec34b08034d87d1) XI AF API call failed. Module exception: 'failed to set up the channel fa9c6ee15efc30c68ec34b08034d87d1'. Cause Exception: 'Channel stopped by administrative task.'."
Please can anyone suggest how this error can be rectified.
regards,
MeenakshiHi,
i have checked the communication channel and the XML. The following error occurs everytime i try to run the scenario.
Error:
Error when calling an adapter by using the communication channel CC_123082_UDFRECEIVER_SOAP_IN (Party: , Service: BC_123082_REMADV_D96A, Object ID: 2a895589066d30d4b2686e9d3a8d4c8d) XI AF API call failed. Module exception: 'SOAP Error'. Cause Exception: 'SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request'
Please let me know how this error can be resolved.
Regards,
Meenakshi
Maybe you are looking for
-
How to create two headers line in CSV file for File Receiver Adpater ?
Hi friends , My scenario is RFC to File. I am downloading file in CSV format . May I know how do i add two line of staic headers Like follows <b> CLOCTYP CFLOCTYP Exe Loc. Type Cus Loc. Type</b> Best Regards., V.Rangarajan
-
What is the best way to back up my MacBook Pro (OSX 10.9.5) before taking it in for service?
-
I have a new MacBook Pro. I keep getting the message "Mail would like to use your keychain "login". How can I make this stop? I have run the keychain repair utility.
-
Windows LIve Messager Problems On N97
Hi Everyone I wonder if anyone can help me. I have a Nokia N97 on the three network. I went to use Windows Live Messenger last week and it errored so I thought I would reinstall WLM again. I uninstalled the one on my handset and went to Planet 3 to d
-
Third-party Applications Responding to an iCal Alarm Twice
This issue involves multiple products so I apologize ahead of time if I have put this in the wrong topic or site and would appreciate any suggestions as to whether or not I should refer to the developers of the third-party apps involved. As an enthus