Soap Adapter will be stored?
hi..
How Soap Adapter will be stored?
bye.
Hi,
Chk these
For more details ref this SAP Note:
Note 856597 - FAQ: XI SOAP Adapter
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5474f19e-0701-0010-4eaa-97c4f78dbf9b
rgds
Chemmanz
Similar Messages
-
How Sender SOAP Adapter will retriew the data to process further
How Sender SOAP Adapter will receive the data to send the integration server to process further
Hi,
1. All details are always taken from the Sender Agreement.
For the Sender File adapter and the Sender SOAP adapter , the details that include are , Sender Service, Sender Interface Name and namespace and these are the details that make up the SOAP header when the message hits the integration Engine.
Once the corresponding Adapter for the message is identified, ie. the Sender SOAP adapter , the message for the SOAP header is then taken from the Sender Agreement of that adapter. This is the exact reason why one Sender Adapter can be involved in one and only one Sender Agreement.
Regards
Bhavesh -
XI / PI SOAP Adapter - MessageServlet not found / not responding
I am in trouble with XI SOAP Adapter. When I try to reach the <b>MessageServlet</b> ( http://host:port/XISOAPAdapter/MessageServlet ) I get the response that document dont exists. Why MessageServlet do not respond? Anyone can help me?
In my Adapter Monitor ( http://host:port/mdt/amtServlet ) I see about the SOAP adapter a grey status and the information: "SOAP Adapter Monitoring is now part of Channel Monitoring". This is not a problem, according to Suraj: "SOAP Adapter will become active only when you sent a message through that for atleast one time.")
See also these topics:
SOAP adapter installation and activation
Adapter monitoring: SOAP is grey although it is used?
how can i enable SOAP Adapter?
https://websmp208.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012003146900000286382005 (<b>SAP Note 856597</b>)
<i> I have readed these topics (and others), but my problem seems to be a little different.
</i>
My XI runtime cache contents (SXI_CACHE) are up-to-date.
<b>Information of some of my XI components:</b>
Software Components
Vendor Name Version Location Applied
sap.com SAP-JEE 6.40 SP17 (1000.6.40.17.0.20060516064307) SAP AG 20060612185606
sap.com SAP-JEECOR 6.40 SP17 (1000.6.40.17.0.20060516064111) SAP AG 20060612185559
sap.com NWMADMIN 6.40 SP17 (1000.6.40.17.0.20060515153837) MAIN_APPL63VA_C 20060612185601
sap.com SAP_XITOOL 3.0 SP17 (1000.3.0.17.0.20060504222004) SAP AG 20060613105756
sap.com SAP_XIPCK 3.0 SP16 (1000.3.0.16.0.20060220233019) SAP AG 20060612185556
sap.com LM-TOOLS 6.40 SP17 (1000.6.40.17.0.20060417111655) MAIN_APPL63VA_C 20060612185603
sap.com SAP-XICONS 3.0 SP16 (1000.3.0.16.0.20060220232901) SAP AG 20060612185600
sap.com SAP-XIAFC 3.0 SP12 (1000.3.0.12.5.20050712085155) SAP AG 20060612185555
sap.com SAP_XIAF 3.0 SP17 (1000.3.0.17.0.20060522230043) SAP AG 20060613103623
sap.com SAP_JTECHF 6.40 SP17 (1000.6.40.17.0.20060516064445) SAP AG 20060612185559
sap.com SAP_JTECHS 6.40 SP17 (1000.6.40.17.0.20060516064629) SAP AG 20060612185606
<b>sap.com com.sap.aii.af.mp 3.0 (3.0.1720060522104934.0000) SAP AG 20060613102037 sap.com/SAP-XIAFC </b>
sap.com com.sap.aii.af.soapadapter 3.0 (3.0.1720060522104934.0000) SAP AG 20060613103506 sap.com/SAP_XIAF
Thanks a lot! If you need other information, please, let me know.
<b><i>Ivan, from Brazil</i></b><i>"https://websmp208.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012003146900000286382005 (<b>SAP Note 856597</b>)
I have readed these topics (and others), but my problem seems to be a little different."</i> -
Hi All,
My scnario is SAP -PI--webService (SOAP adapter) Asynchronous.
In case of any error while processing the data into webservice, I think webservice will pass back a relevant message to thePI through SOAP. I am able to see only the error descrtion in the CC monitoring.
How does PI interpret the XML which SOAP passes back in the event of an error during processing?Where we can find the XML message of the error?
What is the functionality is in place in SAP-PI to get the returned information from the webservice in the event of an issue?
Thanks in Advance
KartikeyaKarthik,
Asynchronous / synchronous is decided by the sender system /adapter
> I think webservice will pass back a relevant message to thePI through SOAP
If it is Async the SOAP adapter will not get the response back from the webservice
Cheers
Agasthuri Doss -
TO Get Ensuring Exactly Once Processing data from sender soap adapt
To XI Specialists
Now Im trying to get Ensuring Exactly Once Processing data from sender soap adapteter.
My plan is that send data from Receiver adapter, to Sender adapter by SOAP.
(1st interface is ABAP to Soap "BE", 2nd interface is Soap to File "EO")
Sender SOAP adapter will returun Ensuring Exactly Once Processing data.
(see SAP HELP, http://help.sap.com/saphelp_nw70/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm )
AND I want to get Ensuring Exactly Once Processing data, I want to determine what to do in ABAP proxy.
SO I made and tested 2interface. but error occuered.
I checked the error, and Now I know what is the cause.
The cause is that Ensuring Exactly Once Processing data didnt enter the payload, at Receiver Adapter.
1st interface coulnt get the payload data, so mapping error occuered....
Please give me help,
<b>"How to get Ensuring Exactly Once Processing data From Sender SOAP ADAPTER"</b>
or
<b>"How to enter Ensuring Exactly Once Processing data into Payload of Receiver SOAP ADAPTER"</b>
and more excelent way....
our XI is version7.0 and SP10
Please teach me your wisdom!
Naoki KuriharaI seeked and I noticed that
maybe I catched the message but the message dont have payload.
so I got no_payload error.
I checked SAP note.
I noticed, no_payload error will be managed to nomal message at SP13....
my XI is SP12....
I ll seek for another way!!
Thank you! noaki -
Receiver SOAP Adapter - Dynamic username & password
Hi,
I am working on a scenario where the receiver SOAP adapter will have dynamic user name & password. but the URL remains same. how do we achieve this.
Thanks,
MaheshHi Baskar,
I have checked all your Replies in SDN related to SOAP Header Creation for Wssec Web Service.
I am working on a Interface (CRM Proxy to Web Service having wssec) in PI 7.0 SP6. I have created the SOAP Header by using XSLT mapping to pass the username token and password but hardcoding user credentials in the XSLT mapping doesn't sound too neat. And transporting it from D to Q to P is even worse.
And also i have 2 username and 2 passwords to access to different instances in the same web service. So i have to pass the different Username and Password based on the Instance in SOAP header dynamically using XSLT mapping.
Therefore i request you help me out on how to pass the Username and password dynamically in the XSLT mapping to Create dynamic SOAP Header to access different instances.
If possible can you provide step-by-step aproach including XSLT mapping and Code for dynamic SOAP Header creation.
Thank you very much for your valuable inputs.
Regards,
Ajay Kodali. -
SOAP Adapter - Guaranteed delivery
Hi ppl,
I have a requirment where we are exploring the possibility of the source system being able to expose its data in http format so that we can get use XI SOAP adapter to get the same over https. As SOAP adapter would access the data through WAN, what would happen to the data if the WAN is broken? How does the guaranteed delivery work in case of SOAP adapter?>
Ethan Hunt wrote:
> thanks for your reply. For inbound messages, how will the data be recieved by SOAP adapter in case of broken WAN. If the source system is exposing the data once in every minute and the WAN is broken for 10 min, when it comes up again, will SOAP adapter recieve all the messages sent by the source system during the connectivity failure? I am not sure how the expose of data in http format works.
From your comments, it seems that the source system acts as a client, and PI (SOAP Adapter) will receive the data from the client.
You can configure the "Quality of Service" of the sender soap adapter with 3 possible options:
- Exactly once (async)
- Exactly once in order (async)
- Best effort (synchronous)
In the first two cases, your client will get an HTTP 200 response (with an empy SOAP message), while in the last case it will get as a response the message you have configured in PI. Take into account that in the first two cases, even if there is an internal error in PI (mapping error for example) your SOAP adapter will still have delivered an HTTP 200 response, as the SOAP adapter did its mission (received the message and delivered it to the Integration Server).
If the client can't reach PI, it won't get an HTTP 200, it will get an HTTP 500 or other error code, so it's your client responsability to retry sending the message until it gets the proper response.
http://help.sap.com/saphelp_nwpi71/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
Edited by: Jorge Lopez on Jul 13, 2009 3:20 PM -
Hi All,
I have a scenario as below,
(R/3)Idoc->XI 3.0 (sp11) (SOAP Adapter)>xCBL to client via HTTPS over Internet. The client is using SAP BC. I am using BPM in XI.
I want to get acknowledgment(success/failure) from the client when they receive the document from soap adapter.
Does anybody know how I can get that please.
Really appreciate if anybody has/had similar requirement and how they resolved it.
Thank you.
Warm Regars,
RanjanHi Robert,
Thank you for the info. When I looked at the SOAP Adapter docos, it says it can only handle the System Ack and not the application ACK. That means even if the Web Services at the client end sends an ACK (which it does) then the soap adapter will not be able to capture this.
I have enabled the technical acknowledgement in BPM and I could the ack coming back to XI correctly but when I enabled the Application acknowledgement it says on the sxmb_moni, Ack not possible.
How can I capture the Application acknowledgement from client if its a Synchronous communication.
Do I need to configure separate sender BC adapter and have the client configure the BC to send the ack to the Adapter engine.
Any suggestion is much appreciated.
Thank you.
Warm Regards,
Ranjan -
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. -
Soap adapter not able to see payload
Hi all,
I am using SOAP adapter at receiver side. We are sending some XML file to supplier https server location.
Here in SXmb_Moni the message shows checked flag but it is not showing the Output payload over there? what can be the reason for this.
One more thing is that at reciever side we are using https: // abc.com URL . When I go to RWB and see the communication channel monitoring then in some case it shows SSL exception and in sme IO. Exception.
Here every thing is fine. Please let me know what additional steps/ configuration we need to do in XI to post the xml data to the https server.
Your comments and input would be thankful.
regards
Ram SinghalHi,
What is the some exception ..
please give exact error..
See SAP Note 856597
<i> Q: Can I use SSL for my receiver adapter?
A: Yes. You can enter any target URL with "https:..." and the adapter will use the HTTP protocol over an SSL connection.
Q: I get the SSL handshaking error. I get some error when I call my SSL web service.
A: First, please make sure that the SSL server is working correctly with another client. If the server is working and you still have the problem, the most likely cause is that your J2EE engine is not configured appropriately to be able to use the unrestricted strong features of the cryptographic library. Please make sure that:
- The JDK java security lib directory ($JAVAHOME/jre/lib/security) contains the unrestricted strong version of local_policy.jar and US_export_policy.jar, which are about 5KB and not the restricted version that are about 3KB each. If you have the restricted version, please refer to http://java.sun.com/ to obtain the unrestricted version.
- The full version of IAIK is available in the J2EE engine's Security Provider. To check this, go to Service -> Security Provider -> Cryptography Providers, and select IAIK. The Provider Information field should show the full version (e.g., IAIK Security Provider v3.12) and not the evaludation version (e.g., IAIK Security Provider v3.01, evaluation version). If you have the evaludation version, please refer to the security setting section of the SAP J2EE documentation.
Q: Can I use SSL with client certificate to authenticate my adapter?
A: Yes. You can configure your receiver channel to use a client certificate. This feature is available from SP13.
Related Questions "I cannot call an SSL web service requiring a client certificate."
Q: I cannot call an SSL web service requiring a client certificate.
A: If you can call an SSL web service requiring no client certificate, please make sure that your clietn certificate is valid and correctly stored in the key store of the J2EE engine. There have been some problems reported in SP13. Please consult SAP Note 870845 for the correction and/or the workaround.
If your certificate entry contains more than one certificates, please make sure that they are ordered correctly.
If you are experiencing some problem, please refer to note 888421 for three different options in using certificates at SSL handshaking.
To trace security related problems, the logging level of components com.sap.aii.security.lib and com.sap.aii.af.security should be set to DEBUG, in addition to the SOAP adapter component com.sap.aii.af.mp.soap and com.sap.aii.messaging. It is recommended to reactivate (or restart) the channel after this setting.</i>
Regards
Chilla.. -
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 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 -
The difference between SOAP adapter and WS adapter in PI 7.1
Hello all,
can anybody explain what is the main difference between SOAP adapter and WS adapter in PI 7.1?
I have checked this [link|http://help.sap.com/saphelp_nwpi71/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm]
but was not able to find the real difference.
Or better, what can I do with WS adapter I can't do with SOAP adapter? What are their advantages/disadvantages?
Thank you all, Igor.In addition to RM, ws adapter also support other ws standard like SAML which is not available in SOAP adatper. Beside:
if your sender or receiver is SAP system, you can also monitor the message in the sender/receiver in addition to the PI box. This is a very good thing, because sometime the MONI in PI shows nothing wrong, but the MONI in your receiver will show you error message that's only related to the receiver system.
However, if you define ws sender CC, and your ws client doesn't support RM, you will have issue sending ws request.
And ws CC will generate ws runtime in PI box, if your configuration is wrong (like user name and password not correct), even if you correct it, the ws runtime sometime won't be regenated based on the correction. In this case you need to delete the ws CC/agreement, and re-create it with all correct information.
Beside make sure your basis team configured the PI system properly regarding ws. If not, you will have lot of pain to figure the problem which was my case.
Jayson -
Hi,
Scenario is Sender SOAP and Receiver (Server Proxy) .
Integrated the ESS applications on .net portal using soap adapter..example salary slip, ctcview....
If we give input as empno to soap adapter it will give you salary details back to .net portal.
All this functional;ity are working fine..
Now i need to check the authorization to acess this soap request. As this webservice works for all the employess in the organazation. but i need to restrict for few employees. Is there any authorization check in XI as it is there in ESS.
If so how to use that . Now in .net portal they are useing the same user name and pwd for all the soap requests.
Regards
Vijay
Edited by: vijay Kumar on May 25, 2010 11:18 AMMichal
Hopefully I can help you for once!
You can set the SOAP action to debug in the Java Admin Console.
Set com.sap.aii.af.mp.soap and com.sap.aii.messaging set to DEBUG
Set location
 Services
 Log Configurator
 Locations
 Choose com.sap.aii.messaging
 Assign Severity Debug
See https://service.sap.com/sap/support/notes/856597 for more info...
This note has a an attachment: tcpgw.zip for tracing the whole message...
Maybe you are looking for
-
I bought iphone 5s device only from apple and used my o2 sim for sometime, now I want to use 3 sim, can I replace the sim directly or anything Apple has to do on my device?
-
Advise for adding larger internal hard drive & faster processor
After five years it is time to make some upgrades to my G4 Quicksilver 733 MHz Tower. The hard drive is nearly full and the processor doesn't seem as fast as it once did (especially after using my faster PowerBook G4). I want to replace the 40GB hard
-
Restoring With Compressed Backup on Oracle.
Hi, We are taking Oracle Database back up in to Tape on compress mode in ProductionServer by modifying the initLPV.sap file as we have 300 GB of data, now I want to restore this backup using tape on to Quality Server.. SAP is running with AIX 5.3
-
Quick question about airport card
I have a G3 ibook with an airport card installed. And I just bought an apple mini. Can I move the airport card from the ibook to the mini? This would be a godsend...hope the ansewr is yes.
-
Mountain Lion log off instead of shut down
Every time I want to shut down my computer (apple icon in menu bar -> Shut down...), it just seems to log off and display the login screen. There I must again click the shut down button, and then it properly shuts down. How do I fix this?