Checking SOAP action in monitoring

Experts,
is there a possibility somewhere in the monitoring to check what SOAP action was used for a message sent via SOAP adapter?
Thank you very much in advance.
Best regards
Michael

hi,
>>>is there a possibility somewhere in the monitoring to check what SOAP action was used for a message sent via SOAP adapter?
Thank you very much in advance.
yes:
1. you can see action in SOAP receiver adapter in ID (in parameters)
2. if you use dynamic action you will see that in dynamic configuration section of the XI message
in monitoring - it will be visible with attribute - THeaderSOAPACTION
Regards,
Michal Krawczyk

Similar Messages

How can I check the called SOAP-action

Hi,
our scenario is IDOC - XI - SOAP (based on a wsdl). I've imported the wsdl as external definitions. The I implement all necessary interfaces, mappings, .... When I'm sending any IDOCs, I see the right interface, but I can't check the right SOAP-Action. The Receiver firm means, that the wrong function will be called.
Have you any ideas?
Thanks
Matthias

Hi Matthias,
the only way to check the SOAP Action is using an HTTP sniffer. Or you write a simple Java program that listens to a port and writes incoming data to a file.
But I have never heard about the problem, that the SOAP action is not correct. Make sure, that the correct receiver channel is used, the channel is activated and the cache refreshed.
Regards
Stefan

DynamicConfiguration - Comma is appended in start of Soap Action

HI All,
I am setting soapAction in receiver communication channel using DynamicConfiguration.
I performed following Configuration in receiver SOAP adapter.
Advanced Tab -> Check 'Use Adapter Specific Message Attributes' -> Check 'Variable Transport Binding' ->
Variable Header (XHeaderName1) = THeaderSOAPACTION
SOAP Action in General Tab is empty
I am using following code snippet in UDF under message mapping.
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get
(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP","THeaderSOAPACTION");
String soapAction = "http://abc.com/acon/service/1.0/IServiceOut/AddNote";
conf.put(key, soapAction);
return "";
Now while executing scenario using SOAPUI tool, at runtime i get following soap error message -
soap fault: The message with Action ', http://abc.com/acon/service/1.0/IServiceOut/AddNote' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).
I observed that in soapAction "," (comma) is being appended in starting. I believe this additional comma is causing problem. How can we remove this automatically appended comma from Soap Action?
Thanks in anticipation.
- Gopi

Hi,
We are able to solve additional comma (,) problem in start of SOAPAction. Thanks for your inputs.
But now we are facing another problem which contains 2 SOAPActions in HTTP Headers as shown below.
POST /MyService/MyService.svc HTTP/1.0
Accept: */*
Host: training.com:8080
User-Agent: SAP-Messaging-com.sap.aii.af.sdk.xi/1.0505
content-id: <soap-001CC4FC74A51EE18DF87E8066A44800.sap.com>
Content-Type: text/xml; charset=utf-8
Content-Length: 277
SOAPACTION:
SOAPACTION: http://abc.com/acon/service/1.0/IServiceOut/AddNote
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
<SOAP:Header/>
<SOAP:Body>
some body message
</SOAP:Body>
</SOAP:Envelope>
Please provide inputs to remove empty SOAP Action from HTTP Headers.
Do i need to set any parameter in receiver channel to suppress it?
- Gopi

Receiver Adapter - Target URL/SOAP Action

Hi,
Can I just confirm the following 2 values required on a SOAP Receiver adapter:
Target URL : Location within SOAP:Address tag of WSDL
SOAP Action: SoapAction within SOAP:Operation for relevant Web Service method within WSDL
Cheers,
PaulC.

> Target URL : Value of SOAP:Address tag from web service WSDL
right, it is attribute "soapAction"
> SOAP Action: Value of SOAP:Operation for relevant Web Service method within web service WSDL
right. attribute "location"
check this guide:
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4

Can we use same SOAP ACTION in different environments?

Hi All,
I have a doubt.
Can we use same SOAP Action URL in different environments i.e suppose say Quality, Production and Pre production.And the Target URL is different in both environments.
If yest what is the impact in different environment.

Hi ,
SOAP action is nothing but operation/method in webservice .
Usually at end system end as a good practice/std they will maintain the same soap action name in all their environments,but it's always better to cross check url and soap action with end system folks before configuring in PI .
We have faced an issue in production some time back ,at target system end they upgraded their server and used new wsdl which is almost similar to existing but one of the operation they duplicated by adding few addition fields but forgot to inform PI system.Though we are using new wsdl but pointed to old soap action .Interface got failed in PROD after investigation we come to know that we are using wrong soap action
Regards
Venkat

What does SOAP action do?

Hi All,
From hep.sap, i have got a very few knoweldge abt SOAP Action. i.e.,"Specify the SOAP action. The action species the value for the SOAPAction in Web service messages.".
Can any one elaborate SOAP Action purpose, since we are calling Webservice through SOAP URL.
Thanks

Hi ,
it is like a function that web service can perform.
you find the SOAP action from WSDL file at tag soap:operation:
If more than one message type is described in the WSDL, several SOAP actions might also be defined. Check for the correct operation name. If no SOAP action is defined in the WSDL, you can leave the parameter in the receiver channel empty.
Regards,
Rohit
pls reward points if found useful...

SOAP - Action Return Rode ea01

My POA is logging the following error :
SOAP Action Return Code - ea01
Any idea what this indicates
We have BES 5.01 for GW running and all seems ok
Steve

Steve,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

How to create one soap interface with two soap action?

Hi,
I need to create one SOAP Interface with two or more webmethods (soap action), for example:
Interface: MI_Outb_User
Webmethods: createUser, searchUser, deleteUser.
Can anybody helpe me?

Hi Santos,
I assume you will use one action at a time and depending upon certain condition you want to invoke the webservice and the corresponding action. If this is yes, then please check michaels reply in this thread:
How can I handle serveral soap actions
or see stefans reply:
Re: Is SOAP Adapter Action field can contain 2 or more "SOAP Actions"
If this is not, then please ignore it.
Regards,
---Satish

Calling a web service from a portal application / SOAP Action

Hallo,
Ich möchte aus einer Portal Applikation auf einen Web Service zugreifen.
Dafür habe ich mit dem Wizard "Portal Service from Wsdl file - Client side"
eine Portal Service erzeugt, auf den ich dann zugreife.
Leider wird dabei ein Fehler ausgegeben (Stacktrace-Ausschnitt s.u.).
Ich habe ein Posting zu dem Fehler hier im SDN gefunden, leider hatte dort niemand eine Antwort. Vielleicht hat inzwischen jemand eine Idee?
Das Feld soapaction ist in der soapconfig.xml leer angegeben (soapaction="").
Es ändert aber nichts an der Fehlermeldung, wenn ich dort etwas eintrage.
Ein weiterer Gedanke ist, dass die soapaction, die wenn ich es richtig verstehe eine URL auf die web service methode enthalten soll, im Grunde dynamisch sein sollte, da der Web Service lokal in dem Portal läuft, auf dem die Applikation gerade deployed ist. Auf den Web Service wird mit WebDynPro erfolgreich zugegriffen (dynamisch). Meine Vermutung ist, dass hier das Problem liegt und es entweder mit diesem Wizard nicht möglich ist oder ein Bug vorliegt.
Also ist die Frage: Wie erzeuge ich dasselbe für eine Portal-Applikation?
Ich hoffe, dass mir jemand mit einer Antwort oder Hinweisen wo man weiterforschen kann, weiterhelfen kann.
Freundliche Grüße,
Daniel Dehnhard
Stacktrace:
Component finished with error: (com.sapportals.portal.prt.service.soap.exception.PRTFaultEnvelopeVersion)
java.lang.IllegalArgumentException: The SOAP Action "" include in the soap request not corresponding to the Portal service method.
at com.sapportals.portal.prt.service.soap.element.PRTSOAPBodyElement.processParams(PRTSOAPBodyElement.java:253)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPBodyElement.init(PRTSOAPBodyElement.java:190)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPBodyElement.(PRTSOAPBodyElement.java:56)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPBody.init(PRTSOAPBody.java:94)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPBody.(PRTSOAPBody.java:36)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPEnvelope.init(PRTSOAPEnvelope.java:113)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPEnvelope.(PRTSOAPEnvelope.java:54)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPMessage.processSOAPMessage(PRTSOAPMessage.java:58)
at com.sapportals.portal.prt.service.soap.element.PRTSOAPMessage.(PRTSOAPMessage.java:40)
at com.sapportals.portal.prt.service.soap.SOAPService.call(SOAPService.java:180)
at com.sapportals.portal.prt.service.soap.PRTSOAPCall.invokeMethod(PRTSOAPCall.java:209)
at de.enviam.ep.egk.km.webservicewrapper.Z_EP_EM_EGK_CustomerGroupToCRMData.getCustomerGroup2CrmDataByGPNr(Z_EP_EM_EGK_CustomerGroupToCRMData.java:218)
at de.enviam.ep.egk.km.imp.EPImpSchedulerTask.resolveGroupId(EPImpSchedulerTask.java:764)

Hi,
I am accessing a web service from a Portal Component through a Portal Web Service. First i created a web service, then a portal web service which is made to access the wsdl file of the web service. Now i access the Portal Web Service from a Portal Component. Now i am getting an error as,
Exceptionjava.lang.IllegalArgumentException: The SOAP Action "" include in the soap request not corresponding to the Portal service method.
The code which i wrote in component is below
String text = "word";
FuncHelloResponse res=new FuncHelloResponse();
FuncHello fn= new FuncHello() ;
fn.setName(text);
res= ( (INewPortal) PortalRuntime.getRuntimeResources().getService(INewPortal.KEY)).FuncHello(fn);
response.write(res.getResponse());
Can any one solve this problem?

PI 7.1 multiple operation interface and SOAP action doubt

Hi guys,
I'm trying to implement a scenario, where I have a single outbound (sender side) interface with multiple operations (as 7.1 allows). The problem is afetr the WSDL generation I have the same SOAP action for each operation. Standardly there should be unique SOAP action per operation, but how to achieve it?
And another question - is it ok to use SOAP sender adapter for this interface?
Thanks for your help,
Olian

Hi Olian,
>>The problem is afetr the WSDL generation I have the same SOAP action for each operation. Standardly there should be unique SOAP action per operation, but how to achieve it?
I dont think you need to have separate action, the Operation Name inside Service Interface differentiate the Request type. Also when you send SOAP message to PI, you are sending it to either
http://host:port /XISOAPAdapter/MessageServlet?channel=p:s:c
(where host is the host name, port is the port number, p is the optional party name, s the service name, and c is the channel name, respectively.The URL given above is valid for 3.0/7.0/7.1.)
or * http://host:port /XISOAPAdapter/MessageServlet?senderParty=FP& senderService=FS& interface=IF&receiverParty=TP&receiverService=TS&interfaceNamespace=IFNamespace *
(7. 10 onwards a new URL syntax is also valid and is recommended to be used. )
>>And another question - is it ok to use SOAP sender adapter for this interface?
Yes
Regards
Suraj
Edited by: S.R.Suraj on Sep 8, 2009 6:23 AM

Missing soap action in the soap axis receiver adapter ?

Hi Guys,
I could not find the soap action field in the soap receiver adapter and i followed the OSS note
Note 1054986 - SOAP (Axis) receiver adapter's SOAPAction field missing
Please apply the following patch and use the handler parameter defaultSOAPAction for the XI30OutboundHandler handler in the request chain. This handler parameter can be configured as a module parameter for the HandlerBean module associated with this handler. It is noted that this module parameter takes precedence over the channel parameter for SOAPAction if this field is available.
For SP12
XI ADAPTER FRAMEWORK CORE 7.0
Support Package 12, Patch Level 1 (SAPXIAFC12P_1.SCA)
we are on SP15 so i think the option should be available ?
Do i need to add this parameter in the Module Configuration ?
Moduel Key : ?
Parameter Name: handler.type ---> is this right
Parameter Value ---> ?
we need to validate the user id and pw on IIS for NTLM authentication. Any help regarding developong the handlers would be great
any help would be appreciated.
Thanks,
Srini

Srinivas,
You are on the right path...........yes that is the right note for this issue.
The problem is this is not a general fix that comes with all service packs as the axis adapter is not used a lot, that being said.if you dont see it with sp15..i would safely go apply this fix and see if it works..else you might have to open an oss note for the same...
Hope that helps..
Regards
Ravi Raman
P.S: On my home system..i did apply the fix and i was on a much higher sp level ..i saw some errors..in the logs but nothing a restart couldent fix..

Dynamic Configuration of SOAP Action

Hello Everyone,
I am currently working on a project which requires us to set the SOAP action dynamically:
I did follow the guidelines mentioned in the following links
Dynamic Configuration of Some Communication Channel Parameters using Message Mapping
Dynamic webservice selection
The process which we are using is as follows
We are creating the following UDF and mapping the root nodes in message mapping using it
DynamicConfigurationKey keyURL = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP","THeaderSOAPACTION");
// access dynamic configuration
DynamicConfiguration conf = (DynamicConfiguration) container
.getTransformationParameters()
.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
conf.put(keyURL,"RetrieveList");
return "";
In the Receiver Comm Channel we are setting the use adapter specific identifiers option and the use variable binding option. We are leaving the SOAP Action field blank.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>SOAP:Server</faultcode>
<faultstring>String index out of range: 0</faultstring>
<faultactor>Server</faultactor>
</SOAP:Fault>
Now we tested the scenario using TCP Mon and we identified that for the value of SOAP Action we are getting the following results
SOAPAction:
SOAPAction: actual value
It means that 2 SOAP Action are generated one being the empty SOAP Action from Receiver Comm Channel and the other being the one generated using UDF.
Can anyone please update us on if our steps are proper or is there a way to supress the SOAP Action which we left empty in the receiver comm channel.
Your help is truly appreciated.
Thanks.
Kiran

Did you follow all the three steps I have pointed in the thread,
1. In the Receiver SOAP adapter,Select options ,
a) Use Adapter Specific Message Attributes
b) variable Transport Binding.
c) Keep the SOAP action field empty.
In the receiver SOAP adapter, make sure that the soap action is empty and the above options are selected.
In this case, the SOAP action from the UDF will be choosen.
But, if you enter something in the receiver SOAP adapter's SOAP action this will be treated as the SOAP action rather than the UDF code.
Regards
Bhavesh

WSDL without SOAP Action (BTS.Operation?)

Hi
I got a WSDL without SOAP Action specified. I'm able to generate XSDs, set up a send port and call an operation. Since I was calling a single web operation then I set up my Action at send port WCF config to be
http://localhost/CarService/updateLocation, i.e. [service URL]/[operation name].
My problem now is that I need to call two separate operations from that web service by using BTS.Operation property; one is still
updateLocation and the other one is removeLocation. How can I specify Action in send port WCF config when SOAP Action is missing in WSDL? I tried specifying different values but none of them were successful.
Ex.
<BtsActionMapping>
<Operation Name="updateLocation" Action=""/>
<Operation Name="removeLocation" Action=""/>
</BtsActionMapping>
Kind regards
A.H.

Hi,
How are going to call these web-methods. Are your going to call these two methods from the same Orchestration. Or are you going to call these methods from two different send ports by content-based routing (send port filter).
In BizTalk, this instruction (SOAP Action) is set by assigning a value to WCF.Action context property. You can specify WCF.Action property in two ways:
Single Action Format
Action Mapping Format
The way you have been calling before "http://localhost/CarService/updateLocation" is called Single Action Format. Now you have use the Action mapping format.
In Action mapping format, you map the WCF.Action context is “mapped”/resolved from another context property BTS.Operation. So if you call from the Orchestration, set the BTS.Operation approirately to resolve the URL in the config. i.e if you have config
like this:
<BtsActionMapping>
<Operation Name="updateLocation" Action="http://localhost/CarService/updateLocation"/>
<Operation Name="removeLocation" Action="http://localhost/CarService/removeLocation"/>
</BtsActionMapping>
In your orchestration, if you set the WCF.Action to "removeLocation", WCF.Action would be resolved to "http://localhost/CarService/removeLocation". In orchestration, you set the
WCF.Action context, by setting the logical send port's operation name. Refer to this article for more info:http://www.fortuvis.com/blog/biztalk-and-wcf-soap-action/
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.

Invalid SOAP action when using java ws WebService

Hi all,
this is a slightly more detailed error for a problem i posted recently. I am connecting to a web service that was generated from WSDL. It has two methods "HelloWorld" and "HelloSayFirstName". As defined in the WSDL, the methods use the SOAP action document style. I want to add a cookie to the http header, so after the port is created, I use the following to add the header to the requestContext:
          BindingProvider bindingProvider = (BindingProvider) servicePort;
          Map<String, Object> requestContext = bindingProvider.getRequestContext();
          List<String> cookies = new ArrayList<String>();
          cookies.add("mycookie=mytoken");
          HashMap<String, List<String>> httpHeaders = new HashMap<String, List<String>>();
          httpHeaders.put(HTTPConstants.HEADER_COOKIE, cookies);
          requestContext.put(MessageContext.HTTP_REQUEST_HEADERS, httpHeaders);
This works when I call the first method (HelloWorld) - the first activity message sent to the server contains the following:
<HttpRequest>
<Method>POST</Method>
<QueryString></QueryString>
<WebHeaders>
<Cache-Control>no-cache</Cache-Control>
<Connection>keep-alive</Connection>
<Pragma>no-cache</Pragma>
<Transfer-Encoding>chunked</Transfer-Encoding>
<Content-Type>text/xml; charset=UTF-8</Content-Type>
<Accept>*</Accept>
<Cookie>mycookie=mytoken</Cookie>
<Host>exampleHost</Host>
<User-Agent>Java/1.5.0_14</User-Agent>
<SOAPAction>"http://tempuri.org/IMyService/HelloWorld"</SOAPAction>
</WebHeaders>
</HttpRequest>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<To s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">http://exampleHost/WebServices/WCFService/Service.svc</To>
<Action s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">http://tempuri.org/IMyService/HelloWorld</Action>
</s:Header>
<soap:Body>
<HelloWorld xmlns="http://tempuri.org/" xmlns:ns2="http://schemas.datacontract.org/2004/07/" xmlns:ns3="http://schemas.microsoft.com/2003/10/Serialization/">
<myValue1>world</myValue1>
</HelloWorld>
</soap:Body>
</soap:Envelope>
However, after this method, the httpHeaders in the requestContext object have been updated to include the "Accept" header and the "SOAPAction" header - which is the incorrect action! Now, when I call the method "HelloSayFirstName" I get the following:
<HttpRequest>
<Method>POST</Method>
<QueryString></QueryString>
<WebHeaders>
<Cache-Control>no-cache</Cache-Control>
<Connection>keep-alive</Connection>
<Pragma>no-cache</Pragma>
<Transfer-Encoding>chunked</Transfer-Encoding>
<Content-Type>text/xml; charset=UTF-8</Content-Type>
<Accept>*</Accept>
<Cookie>mycookie=mytoken</Cookie>
<Host>exampleHost</Host>
<User-Agent>Java/1.5.0_14</User-Agent>
<SOAPAction>"http://tempuri.org/IMyService/HelloWorld"</SOAPAction>
</WebHeaders>
</HttpRequest>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<To s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">http://exampleHost/WebServices/WCFService/Service.svc</To>
<Action s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">http://tempuri.org/IMyService/HelloWorld</Action>
</s:Header>
<soap:Body>
<HelloSayFirstName xmlns="http://tempuri.org/" xmlns:ns2="http://schemas.datacontract.org/2004/07/" xmlns:ns3="http://schemas.microsoft.com/2003/10/Serialization/">
<dataContractValue></dataContractValue>
</HelloSayFirstName>
</soap:Body>
</soap:Envelope>
It seems that the SOAPAction in the http header and the soap header is incorrect. Is there any reason why the requestContext would keep hold of the action that was previously called, and not use the new action? I'm stumped here - any help would be greatly appreciated.
Cheers.

Does not only happen when using JAX-WS.
the following servlet code is enough to reproduce the problem :
protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
response.setContentType("text/xml;charset=\"utf-8\"");
It only occurs on 10.1.3.4.0 (works fine on 10.1.3.3.0 and 11.1.1.1.0 TP4)
Regards

PI 7.1 SOAP Action parameters in SOAP request?

Hi all,
I have to implement an IDOC->PI->XML interface to transfer some master data. After performing the mapping, the mapped data needs to be sent to the target system using a SOAP request via a webservice.
On PI, I specified the URL for the WS in a SOAP-oriented Communication Channel. In the parameter "SOAP Action" of this CC, I entered the relevant method name to be used to transfer the mapped data. However, this method requires 2 parameters:
- applicationName: this is the name of the target structure used in the Message Mapping
- xmlMessage: this is the actual mapped message string
So my question is: how can I bind these 2 parameters in my PI design and configuration?
Thanks for your help,
Eric

there can be one WS having many actions....which means one WS can be used in multiple interfaces.
However, this method requires 2 parameters:
- applicationName: this is the name of the target structure used in the Message Mapping
- xmlMessage: this is the actual mapped message string
If I get it correctly, you have to actually set the SOAP action before you send the message to the WS....and you want to do it in SAP PI?
so your action is something like http://something.abcd/applicationName/xmlMessage and you have to set the things here?
If yes, then you can use the Dynamic Configuration (adapter specific message attributes...ASMA) in SOAP channel (UDF in mapping) and set this ASMA THeaderSOAPACTION
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get
(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP","THeaderSOAPACTION");
String a = http://something.abcd/applicationName/xmlMessage //set the value of actual action here
conf.put(key, a);
return "";
Regards,
Abhishek.

Checking SOAP action in monitoring

Similar Messages

Maybe you are looking for