SOAP adapter Module Issue

Hi,
i had configured a JDBC to SOAP scenario and the SOAP adapter has the Module (localejbs/ReplaceXMLTag)
now the issue is while execute teh scenario, it works fine at DEV but shows error at QA as given below
"Delivery exception: Object not found in Lookup of Replace XML tag"
please let me know how to resolve this issue.
Thanks in advance....

> i had configured a JDBC to SOAP scenario and the SOAP adapter has the Module (localejbs/ReplaceXMLTag)
> "Delivery exception: Object not found in Lookup of Replace XML tag"
Have you spelled this correct? The name in the error message seems to be different from th module name.

Similar Messages

PI 7.1 adapter module issue

I deoplyed my module and worked fine. now i changed some code by adding parameter to module
strModuleKey = moduleContext.getContextData("module.key");
I changed the related things in my communication channel(gave parameters)
Now, i get below error while executing...
java.lang.ClassCastException: class com.sap.aii.af.sdk.xi.mo.MessageContext:library:com.sap.aii.af.sdk.libcom.sap.engine.boot.loader.ResourceMultiParentClassLoader428c6e04alive incompatible with interface com.sap.engine.interfaces.messaging.api.Message:interface:com.sap.aii.af.ms.ifccom.sap.engine.boot.loader.ResourceMultiParentClassLoader2dd7e4d6alive
Followed the below url but in vain..
PI JAVA ADAPTER MODULE PROBLEM
Incompatible with interface - Exception in Adapter Module
Issue on developing Adapter Module
Also if you are using PI 7.1 refer to the blog:
/people/stefan.grube/blog/2008/12/11/adjust-your-pi-70-adapter-modules-for-pi-71-in-15-minutes
Please let me know if u have any other suggestions other than this...
Thanks
Prabhakar

Hi Venkat,
Yes, you cannot add custom modules to soap adapter.
Please refer below documentation for the same..!!
http://help.sap.com/saphelp_nwpi71/helpdata/EN/44/8c4756224a6fb5e10000000a155369/content.htm
http://help.sap.com/saphelp_nwpi71/helpdata/EN/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
Regards,
Swetha.

Sender SOAP Adapter Modules!

Hi Can anyone guide me how to write a Sender SOAP adapter module ?

Hi Pooja, thanks for the reply I have seen that.
Please look at the below forum.
SOAP Adapter and plain HTTP
It says "When you write a module for sender SOAP adapter, you have to deal with the incoming message, as the SOAP adapter first calls the customer module, then creates the XI message."

Any one knows how to use Axis Framework in the SOAP Adapter Modules

How to use Axis Framework in the SOAP Adapter?
How to add custom handler modules?
http://help.sap.com/saphelp_nw04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/frameset.htm
I went through the above link on help.sap.com. But still could not create a working example.
I have created a wc on some 3ed party app server using apaches axis. I am trying to call that web service from XI using SOAP receiver? I need to add some security related headers to the soap message, SO I am trying to use a handler. I want to know how to configure this handler in SOAP axis adapter module.
Thank you
Moni

Ravi ,
I am trying exactly the same. Hers is the scenario.
ABAP Proxy --> PI (7.0) SP 12 ---> WebService.
Since This is service is secured, means it is using OASIS web servie securyty user name token,
I am trying to use AXIS adapter. and I want to configure HandlerBean in which I want to use apache wss4j api to add the userNameToken. I am looking for some documentation on this.
I need to add SOAP action element too as I can not configure this one on the communication channel.
Thanks for any inputs in this regard.
Moni

SOAP adapter - Module options...

Hi,
with a SOAP receiver, in tab "Module" we have "Module configuration". For instance, we can specify:
Module Key        = soap
Parameter name = XMBWS.Timeout     (found in oss note 856597)
Parameter value = 10000
Where can I find all the others available parameters ?
Thanks
Mickael
P.S: maybe with: http://help.sap.com/saphelp_nw2004s/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
Message was edited by:
        Mickael Huchet

Huchet,
In the receiver SOAP adapter, if you want to add your own modules to process the request message, you add them before the module specified below; if you want to add your own modules to process the response message, you add them after the following module:
sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
Also you can see a list of parameters in this link:
http://help.sap.com/saphelp_nw04/helpdata/en/bf/27fd3b651f6a1ce10000000a11402f/content.htm
Go through this help for some info:
http://help.sap.com/saphelp_nw04/helpdata/en/a4/31d940f52f7e7fe10000000a1550b0/content.htm
---Satish

Sender SOAP Adapter Security Issue

Hi All,
We are building a SOAP to proxy scenario. The sender is a SOAP Adapter and the receiver is Proxy. The SOAP WSDL and URL is provided to the legacy system. When the legacy system is trying to send the data using the WSDL and the URL provided, they are receiving a dialog box to enter the user name and password. We can create a system user and provide those credentials to the legacy system. However, the legacy folks are not interested in including this in their web service.
Could you please suggest, if there is a way to create the web service such that it wouldn't request for user credentials? Something like no authorizations in the web service?
Thanks,
Manohar Dubbaka.

Hi Preeti,
Thanks for the response. Since we are on PI 7.0, I believe the setting that you are referring to should be on Visual Admin. Could you please let us know the parameter or the setting that needs to be changed in VA?
I am not sure, how we can make use of SSO to prevent them from entering the user credentials. Your help in this regard would be much appreciated.
Thanks,
Manohar Dubbaka.

SOAP adapter: WSDL issue

Hi Experts,
I am working on File-XI-->Mail scenrio using SOAP adapter. My file contains only one line fields say:
TATA 407
I have configered File adapter perfectly and CC of it is showing perferctly green (Data is coming in MONI). On the counter SOAP side, I would like to send this file to the Gmail. But I am not able to do this due to the fact that I am not understanding the WSDL ? I have read several doucments but not one is giving the perfect idea about it.
Please tell me how to accomplish it. Please avoid to send the links. Please help ASAP.
-=Soniya=-

Hi Soniya,
>>I do agree that Mail adapter can be used in place of SOAP
No, it's not that.
SOAP and Mail adapter are two different things. SOAP adapter is used to exchange SOAP messages (do not confuse "message" with "email message") between applications (XI/PI to third pary OR third-party application to XI/PI) using SOAP/HTTP protocol. Whereas Mail adapter is used to send email using IMAP/POP3 protocol.
>>Somebody is saying that Webservices are the one, where you send your messages either side people are saying.
Correct. You can configure SOAP adapter as sender in PI and receive SOAP messages in PI sent by some third-party application. OR you can configure SOAP adapter as receiver and post the message form PI to some third-party provided URL.
For exposing webservice from PI all you need to do is to go to Integration directory. Select the sender aggrement you want to puslish as web service. From TOOLS menu say display WSDL. Save this WSDL and provide it to client/third-party application. They will have to generate the client proxy class and post the message from there to PI.
For cosuming webservice in PI (posting message from PI), third-party application has to provide you with a URL which you will enter into SOAP receiver type adapter.
Regards.

SOAP adapter 404 issues

Dear friends,
My scenario is web serivce to proxy, and i created the sender interface and relevant sender soap adapter, finally I exposed the outbound service with a web service, the URL is http://hostname:port/ISOAPAdapter/MessageServlet?channel=:servicename:channelname
After that, i called the web service from XMLSPY, but got the exception information in the response message:
<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.JAVA_EXCEPTION</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.consumer.CallConsumer.onMessage(CallConsumer.java:158)
 at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:917)
 at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(AccessController.java:219)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
 ]]></text>
 </s:SystemError>
 </detail>
and then I opened the RWB to find the detail information from message monitoring, the relevant error information are as below:
2008-09-02 17:20:54 Success SOAP: request message leaving the adapter (call)
2008-09-02 17:20:54 Success Application attempting to send an XI message synchronously using connection SOAP_http://sap.com/xi/XI/System.
2008-09-02 17:20:54 Success Trying to put the message into the call queue.
2008-09-02 17:20:54 Success Message successfully put into the queue.
2008-09-02 17:20:54 Success The message was successfully retrieved from the call queue.
2008-09-02 17:20:54 Success The message status set to DLNG.
2008-09-02 17:20:54 Error Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 404 : Not Found.
2008-09-02 17:20:54 Error Transmitting the message using connection http://hostname:50000/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 404 : Not Found.
2008-09-02 17:20:54 Error The message status set to FAIL.
2008-09-02 17:20:54 Error Returning to application. Exception: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 404 : Not Found
Does anybody know what's the problem? I ever cheched the message servlet: http://hostname:port/XISOAPAdapter/MessageServlet?channel=:servicename:channelname, the status is OK.
Regards,
Bean

Dear friends,
The problem has been finally solved, it's due to the wrong configuration of the pipeline URL in SLD for the integration server, the port should be 80*, not 5*00, thanks to all of you.
Bean

Sender SOAP Adapter Authentication issue

All,
We have a SOAP-XI-RFC scenario. We exported the wsdl from the Integration Directory. When we try to call the web service using webservice studio client. We get the following error. We are using a user that has (SAP_XI_ADMINISTRATOR role on it).
ResponseCode: 401 (Unauthorized)
Connection:close
Pragma:no-cache
Content-Length:1790
Cache-Control:no-cache
Content-Type:text/html
Date:Fri, 30 Nov 2007 20:01:23 GMT
Expires:0
Server:SAP J2EE Engine/7.00
WWW-Authenticate:Basic realm="XISOAPApps"
Any thoughts?
Thanks.

hi thezone ,
ResponseCode: 401 (Unauthorized)
as per this specific error try checking that
1.check the wsdl url format
http://<server>:<port>/XISOAPADAPTER/MESSAGESERVLET?channel=:<Service>:<Channel>
2. test the wsdl by putting the url in internet explorer and see if you are getting a dialog box for user name and password, also in this step you will confirm the working status of message servlets of web service.
3. by step 2 IE will send a message to XI, now you check your adapter
4. test ur xml instance in your soap tester, go to its properties and make sure that you had given correct user name and password over there on specified fields.
regarding your soap communication channel it will be activated after receiving first message. you can detect any problem in connection only after receiving first message.
Regards,
Mandeep Virk
reward points if helpful

Outbound SOAP Adapter Authentication issue

Hi All,
We have a scenario vendor to ECC (SOAP to Proxy) scenario. They are consuming Xi webservice. Now we don't want to give them the USERNAME and PASSWORD for our Integration Engine. Is there a way we can hard code UserID/Passowrd in the Adapter instead?
Regards,
XIer

Ashish,
>Is there a way we can hard code UserID/Passowrd in the Adapter instead?
No
Cheers
Agasthuri Doss

Error in AXIS SOAP Adapter

Hi Experts,
Cuurently i am working on Synchronous scenario.
My scenario is ABAP Client Proxy> PI>AXIS SOAP ADAPTER(Webservice).
My client requirement is to use UsernameToken security with PasswordDigest.
I have deployed all the relevant .jar files and add the modules related to usernameToken security as per *SAP Note 1039369 FAQ XI Axis Adapter* in Receiver SOAP adapter.
Now when i am pushing the data from R/3 to PI, data is successfully coming to PI however when the data is going outside PI through Receiver AXIS SOAP Adapter in RWB is showing
*The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System*
*The message status set to DLVD*.
Moreover when i am checking the message through SXMB_MONI i cant see the chequred flag for Request message and for response message its giving the following
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="SOAP">FAULT</SAP:Code>
<SAP:P1>http://schemas.xmlsoap.org/soap/envelope/</SAP:P1>
<SAP:P2>Server.generalException</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>WSDoAllReceiver: security processing failed (actions number mismatch)</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
and when i am cheking the trace of Respose message (request for message mapping ) its giving the
<Trace level="1" type="T">Message has no payload</Trace>
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_MM_UrlResponse_To_CourseAccessUrlResponse_</Trace>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Parsing an empty source. Root element expected! at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:151).....
Currently SSL is not installed in my PI server.For temperory i am using HTTP instead of HTTPS.
Please provide your valuable inputs on this.
Regards
Anku chopra
Edited by: AnkuChopra on Aug 28, 2009 1:59 PM

Hi Experts,
In my Receiver SOAP adapter module Tab.
As my scenario is synchronous and i required UsernameToken with PasswordDigest security i have added following parameter value in module.(as per SAP Note 1039369 FAQ XI Axis Adapter ).
Processing Sequence.
Module Key
afreq
xireq
wssec
trp
xires
afres
Module configuration
ModuleKey ParameterName parametervalue
xireq handler.type java:com.sap.aii.axis.xi.XI30OutboundHandler
wssec action UsernameToken
wssec handler.type java:com.sap.aii.adapter.axis.ra.handlers.security.WSDoAllSender
wssec passwordType PasswordDigest
wssec pwd.password ********************
wssec user XYZ
trp handler.type java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
trp module.pivot true
xires handler.type java:com.sap.aii.axis.xi.XI30OutboundHandler.
Do we need to do any other configuartion apart from above in parameter value.
While getting response from third party i getting error as WSDoAllReceiver: security processing failed (actions number mismatch)
Do i need to add parameter value for WSDoAllReceiver as well as my scenario is synchronous.
Please help me out on this as i am not able to proceeed further because of the above errro.
Please advice.
regards
Anku Chopra

Soap adapter default encoding

Hi there,
we have a XI <-> webservice scenario, where the XML messages are sent in a string (the wsdl is wrapped, literal) with digital signing.
As of now, we have a problem in the digital signing, since the webservice won't validate the signature. We made some tests and this is what I've concluded.
From what I've observed, there are three ways of sending XML file content in a string (let me know if there are more). They are:
1. putting the xml content between "<![CDATA[" and "]]>";
2. replacing '<', '>' and '"' with "<", ">" and """;
3. replacing '<' and '>' with "<" and ">".
2 and 3 appear to be different encodings.
We tried to send three messages to a test webservice, each with a different way of defining the string, using receiver soap adapter. This test webservice was located in a local machine and we ran a sniffer on it. The three incoming messages were logged by the sniffer, but the upseting news were that the three of them had the same encoding in the input string, which was the third one above ("<" and ">", which by the way is the default by UTF-8).
This only occurs when using SOAP adapter. I tested File adapter and it sent the file exactly how delivered by the sender service (meaning, with the different encodes or with CDATA). We even thought about using module processor for replacing the characters in the message, but since any custom module processor comes before the main adapter module processor, it won't have any effect on the final message.
Using XMLSpy, I sent some test messages to our digital signer (which is also a webservice) with the three ways and it returned a different output when using "<" encoding in the input. Then, I sent this signed message to the webservice and it validated the signature!
We are suspecting that the webserver (which is IBM's WebSphere) always converts the input string to "<", and when they calculate the message hash code, it's different from what we sent (since we always sign a "<" encoded message).
My question is: is there any way of changing the default encode that the soap adapter module processor uses? Or at least of making it not changing the encode of the payload? If it were possible, we would send the message to the signer webservice with "<" encoding and the problem would be solved.
Thanks in advance,
Henrique.

Morten,
actually, we've found out that < = < , in both UTF-8 and ISO-8859-1 encodings. It makes no difference if you use one or the other.
The point which was troublesome for us were the special characters (like á,â,à,ã,é, etc) which have different encoding for UTF-8 and ISO-8859-1. Since we had identified that the service we were accessing wasn't able to identify these characters properly, we just removed them from the string fields and that worked out for us.
Hope it helps you out.
Regards,
Henrique.

SOAP Adapter (Ports and Interfaces)

Is it true that for every single interface, a new soap adapter needs to be configured? Can one soap adapter handle many interfaces?
Do I need one port for each interface or can I use one port for multiple interfaces. (note, I am using Soap Adapter)
Thanks in advance for your responses

When you are talking about "ports", I assume, that you are using the J2SE Adapter Framework.
Yes, you need a seperate Soap Adapter module (or in XI 3.0 J2EE Adapter Framework a seperate channel) for each interface and for each SOAP Adapter Module you need a different port.
Regards
Stefan

Issue with overwriting msg using adapter module when WSS enabled in SOAP CC

Hi guys,
I have a SOAP->RFC scenario where on the sender side I'm using an adapter module. This adapter module should modify the message content based on some conditions. This works fine unless the WSS is enabled in the sender SOAP CC. When enabled, the message doesn't get modified. If disabled, it works fine. Do you have any explanation for this? Is there any workaround for this?
Thanks, Olian

Hi Olian,
For 2004s (PI71) too sender adapter doesn't support modules (in normal SOAP mode and not in AXIS)
http://help.sap.com/saphelp_nwpi71/helpdata/EN/a4/f13341771b4c0de10000000a1550b0/frameset.htm
>>if I use the module w/o WSS enabled on the CC,
Can you tell me how you did this??
Regards
Suraj

PI 7.1 Adapter Module Development - Identify SOAP Fault Message

Hi Experts,
here's a PI 7.1 Adapter Module Development issue I hope you can help me to resolve. It's about identifying SOAP fault messages.

Scenario at a glance:
Adapter Modules placed in the modules chain at request and response time in a synchronous Scenario:
- Request: SOAP Axis to RFC 
- Response and Fault Response: RFC to SOAP Axis

The issue is how to identify SOAP fault message in SOAP Axis Adapter Module in the response message:
The client gets SOAP fault messages like the follwong one:
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <ns1:exception xmlns:ns1="http://typen.geschaeftsstelle.pab.barmer.de">
 <ns1:errortext>bla bla bla ...</ns1:errortext>
 </ns1:exception>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>


But when trying to access the tags faultcode and/or faultstring in the adapter module via xPath expressions I do not get them. Obviously the SOAP Fault tags are built AFTER the adapter module has been passed. So my question is:
How can I clearly/uniquely detect a SOAP fault response message (and distinguish it from a "normal" response message) in my SOAP Axis Adapter Module?

I tried it the following way:


// Check Message Payload for SOAP Fault Message via xPath expressions
...
// SOAP Fault Code
zv_xPression = zc_constXPattern.replaceFirst("&", "faultcode");
zv_soapFaultCode = XPathAPI.eval(zv_doc, (String) zv_xPression).toString();
// SOAP Fault String
zv_xPression = zc_constXPattern.replaceFirst("&", "faultstring");
zv_soapFaultString = XPathAPI.eval(zv_doc, (String) zv_xPression).toString();
// check for SOAP Fault Message
if (zv_soapFaultCode.equals("") && zv_soapFaultString.equals("")) {
 // Create Audit Log entry - NOT a SOAP Fault Message
 zv_msgText = zc_constModuleName + " 0190: xPath - OK! This message is NOT a SOAP Fault Message";
 zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.SUCCESS, zv_msgText);
 zv_faultCheck = false;
}
else {
 ...
 // Create Audit Log entry - SOAP Fault Message
 zv_msgText = zc_constModuleName 
 + " 0200: xPath - this message is a SOAP Fault Message. " 
 + " - Faultcode is: " + zv_soapFaultCode 
 + " - Faultstring is: " + zv_soapFaultString; 
 zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.ERROR, zv_msgText);
 ...
}
...

But zv_soapFaultCode and zv_soapFaultString are always empty (with other payload tags this coding works fine).

Any ideas? 
Thanx very much in advance!
Regards,
Volker

Hi Alex!
Like already mentioned I solved my problem by identifying the SOAP exception with the messageClass attribute of the PI message header. Acess code:
try {
String zv_msgClass = zv_piMsg.getMessageClass().toString();
} catch (Exception e) {
zv_msgText = zc_constModuleName
+ " E0110: Message processing terminated."
+ " Reason: Error while getting MessageClass "
+ zv_dataSource
+ e;
// create trace and audit log entry (severity ERROR) for exception
zv_location.errorT(ZV_SIGNATURE, zv_msgText);
zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.ERROR, zv_msgText);
ModuleException me = new ModuleException(e);
zv_location.throwing(ZV_SIGNATURE, me);
e.printStackTrace();
throw me;
} // end of try-catch-block
But I do not think this will solve your problem. I am almost sure, that something in your Axis configuration is wrong/missing. If a handler cannot be instatiated then it really may be missing. Have a look at defaultTrace.trc. Maybe you will find more suitable information about the root cause of your problem. Also have a look at NWA under software components and/or application modules if you can find/see your modules.
But there is a general issue when trying to catch PI fault messages. If e.g. the requestor tries to login with wrong userid/pasword, then you will have no chance to catch this kind of error - at least as far as I know. Because in this very early stage of PI message processing no module is called.
One last question: Did you develop your own Adapter or just an adapter module? In the first case: Is your adapter started and healthy? Have a look at RWB -> communication channel monitoring.
Regards,
Volker

SOAP adapter Module Issue

Similar Messages

Maybe you are looking for