Soap parameters

Hi...Experts,
i am doing rfc-soap scenario, we r getting the response from target(SOAP) to XI, we want to send that response from XI to SAP Inbox.
Transport Protocols is : HTTP / SMTP,
which Transport Protocol is suggestable for my requirement HTTP or SMTP.pls sugest me.
regards,
Jain

Hi,
Transport Protocol
● HTTP (including HTTPS)
● SMTP (including SMTPS)
The adapter uses this transport protocol to send SOAP messages as e-mails.
So use HTTP in your case
Reward Points If Helpful
Regards
Seshagiri

Similar Messages

Do Not Use SOAP Envelope doesn't show on SOAP Parameters

Hi!..
Somebody knows why the Do Not Use SOAP Envelope option on conversion Parameters for SOAP Adapter isn't there?...I have XI 3.0 SP19 and I'd seen on a lot of notes and how's to that there is a kind of option. I need the functionality that that check does but I can't find it.
I Only have Keep headers, Keep Attachments, Use Encoded headers and Use query string.
Thanks in advance..
Carlos.

HI Carlos,
I've got same problem, which metadata should I reimport?
cheers,
Edu

SOAP Parameters: Ugly name, can that be changed for something more friendly

Hi, Everyone,
I follow examples here: http://www.oracle-base.com/articles/11g/NativeOracleXmlDbWebServices_11gR1.php ( ours is 11GR2 but the differences are almost none) and created a test procedure and it automatically pubishes it as a SOAP service, its WSDL like: http://10.1.1.11:8181/orawsv/SDKUSER/GET_DESCRIPTION?wsdl shows something like:
xsd:element name="P_ID-NUMBER-IN" type="xsd:double" />
- <xsd:element name="P_DESCRIPTION-VARCHAR2-OUT">
I thought it will be nice just show the name as : P_ID and P_DESCRIPTION instead of something like P_ID-NUMBER-IN ( the name + the data type), I need let IPHONE developers(outside) to access our SOAP web service but I thought these names are ugly and confusing, can I change its parameter name exactly as I defined in Procedure parameter place?
Any suggestions are greatly welcome.
Edited by: seanzh on Mar 15, 2011 12:24 PM

Thank you, Mobra, this pure PL/SQL soap_server_pkg works great, easy to implement( I do see its limitation like the results must be convertable to CLOB type), but it works for simple implementation, without these "ugly" names and best yet: it works easily with Visual Studio web references ( I had hard time getting Oracle native web services working with VS web services as its OUT parameters have NO datatype, VS can't discover the data type so it puts something like P_descritionVARCHAR2OUT as data type, impossible to process ).
I do have a little concern with this implementation: the XML response comes out with something like & lt;?xml version="1.0"?& gt; stuff for non-single(like Row data) return values in XMLSpy test , not exactly like others seperated by something like <column Name1>value1</column Name1> , I understand the returned result is a single CLOB value so the brackets are part of the value. I would think it's not standard way for XML response.
Edited by: seanzh on Mar 19, 2011 2:45 PM
Edited by: seanzh on Mar 19, 2011 2:54 PM
Edited by: seanzh on Mar 19, 2011 3:28 PM

Soap parameters at target side

Hi...All,
i am doing rfc-soap(B2B) scenario for eBanking interfaces.
i am using the digital certificate at soap side. what are all the paramenters are required at soap target side for my requirement..in soap target side number of parameters are there i.e(Configure user authentication,Certificate Authentication,Configure proxy, Adapter specific msg attribute, security parameters, Conversion Parameters,etc...)..
what are all the parameters are required pls suggest me..
regards,
Pasi.

Hi,
Check with this
http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/frameset.htm
REgards
Seshagiri

RFC to SOAP parameters issue - Odd!

All,
We have a RFC to SOAP scenario.. There is a table parameter with 4 fileds in it - OPERATION, ID, TYPE, VALUE.
And in RFC we pass the following in the table,
OPERATION - "CHECK"
ID - 001
TYPE - MAT
VALUE - 234567890
Somehow, the incoming XML doesnt have TYPE and VALUE, but have them concatenated into ID.When we debug on the ABAP side, we se the internal table populated properly just before the call.
But in XI - we see the incoming XML as,
<?xml version="1.0" encoding="UTF-8" ?>
- <rfc:Z_TEST xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
<EX_TAB />
- <IM_TAB>
- <item>
<OPERATION>CHECK</OPERATION>
<ID>001MAT2345</ID>
<TYPE />
<VALUE />
</item>
</IM_TAB>
</rfc:Z_TEST>

Hi rk,
could it be that someone changed the coding of the RFC after you imported the RFC into XI?
If so, reimport again.
Regards Mario

Proxy to soap synchronous

Hi.
In my synch proxy to soap scenario, facing the error while testing web service from altova spy.
Err thrown after i send request is "<RCVR Deter> "MESSAGE_INCOMPLETE"
This is when i use WSDL generated from my ID.
When i use wsdl given from client it doesnt post at all, with message code (500).
Scanned sdn and asked everyone i cud, but cudnt hit any solution.
I noticed following things in WSDL given by client,
1. URL within WSDL's adress tag, when pasted in browser doesnt opens WSDL or any web page rather says "Welcome to axis.."
2,When added ?wsdl at the end of the url, the wsdl can be seen.(so using URL with "?wsdl" as my target URL in soap receiver ID, is approach right??)
3.In WSDL from client has, <wsdl:operation name="XXX" parameterOrder="XXXXX">
what ideally shud be approach when soap is at receiver end.
Also, Great confusions about These::
1. URL in target url in soap receiver
2.URL of file location, while sending request. (shud b wsdl file saved in desktop, or url of wsdl )
3.soap end point and action (what if, when no action is there in wsdl) when changing soap parameters
4.In moni and also in altova getting err <Receiver determintaion> Message_incomplete
5.when to use wsdl generated from ID and when to use wsdl provided from client.
I am badly stuck in this scenario. Couldnt find any way out, at the same time its v v critical object.
wud be thankful if someone can help me in sorting out this..
thanks

5.when to use wsdl generated from ID and when to use wsdl provided from client.
This should be your first question
Use wsdl generated by ID in case of soap sender scenarion and use wsdl from client in case your scenario is soap receiver.
This is when i use WSDL generated from my ID.
For the receiver soap scenario, you dont have to generate wsdl in ID. Use the wsdl given by receiver.
When added ?wsdl at the end of the url, the wsdl can be seen
If your scenarion could work after adding this, then there is nothing wrong in this approach.
1. URL in target url in soap receiver
Use the URL provided by the receiver system. The same url is present in the wsdl file that receiver provide to you.
2.URL of file location, while sending request. (shud b wsdl file saved in desktop, or url of wsdl )
What do you mean by this? For a soap receiver channel, you only need the URL and use the wsdl provided by receiver.
3.soap end point and action (what if, when no action is there in wsdl) when changing soap parameters
Action is not compulsary. Just use the wsdl provided by client and check whether it contains <action> tag or not. If it has, then only provide the action.
4.In moni and also in altova getting err <Receiver determintaion> Message_incomplete
Your case is of soap receiver. You should not send messge from Altova to XI in this case.
Regards,
Prateek

InDesign Server, Applescript, and SOAP

Hi All,
I've scoured these forums and the rest of the 'net as best I can, but I can't seem to find a solution for my issue, so I'm hoping maybe someone out there can shed some light on it for me.
I have InDesign Server running on one box (IP of 192.168.1.5, launched to service SOAP commands on port 12345), and I'm attempting to send a SOAP command to it via Applescript from another box, but I can't seem to figure out how to get it the RunScriptParameters. The Applescript I'm running looks something like (dummy text in for the parameters right now, because that's where my trouble is):
tell application "http://192.168.1.5:12345/"
set resultText to call soap {method name:"RunScript", method namespace uri:"http://ns.adobe.com/InDesign/soap/", parameters:????}
end tell
Every time I run it, under a variety of ways of trying to feed it parameters, I get the error: "/ got an error: The required SOAP element "RunScriptParameters" could not be found. Please check the SOAP message that was sent to InDesignServer." I'm lead to believe that the method name and method namespace uri I'm sending through are correct, as if I change either of those it gives me a generic error. (Method <blah> not implemented, if I change "RunScript or the method namespace uri.)
So, what I'm left with is figuring out how exactly to send through the RunScriptParameters with this setup. I've tried every way I can think of to feed it the scriptLanguage, scriptFile, and scriptArgs, as an array of elements under parameters, as part of a variable called runScriptCommands which I feed through parameters, and every variety of this, to no avail, all giving exactly the same error. Any help would be immensely appreciated.
(And I know Applescript may not be the ideal way to call a SOAP command, but it would be a very simple way for me to test ID Server scripts in my situation, and there isn't any reason that I can see that it shouldn't work...)
Thanks!
Mathew

Hey..Can you tell me how did you executed jsx using sampleclient. Which SDK's sampleclient you used for executing this.??

Error RFC to SOAP Scenario

Hi Experts,
I am getting an error while dealing with RFC to SOAP scenario::
soap fault: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: . at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocol.SetContext(Type type, HttpContext context, HttpRequest request, HttpResponse response) at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
IS it problem from the webserver in sending the response?
Please suggest.
Thanks & Regards,
Sushama

Hi Suraj,
Thanks for the imputs.
We are given with the webservice by separate team, also I am accessing the application via Citrix. I cant test the WS outside the client network and in client desktop they haven't installed Altova Xml Spy
Request and response both are generated in Moni. It seems problem in receiving response only ?? WS url is also correct.
Regarding Receiver Soap parameters:
I have checked adapter specific identifiers and Variable transport binding.
Please suggest, if this is problem with the WS, I need to check with the team.
Thanks & Regards,
Sushama

Oracle BI Publisher - Passing multiple wildcard search to a bind variable

Hi,
Please help me in resolving the below mentioned issue:
I have developed a report in oracle BI Publisher with a SQL query.
While scheduling the report to run I used to pass mutilple parameters like CGAMSVC08,RLCSVC51
If the pass the parameter with wildcard search like C% it works.
When I pass two or more parameter values with wildcard search like C%,R% its not working.
Could you please let me know how should I give the bind variable in the SQL query. Currently I'm paramater like the one shown below for passing multiple paramaters:
Where (',' || :PRMRETRID || ',' like '%,'||RL.RETROFIT_ID|| ',%')
Edited by: user1101445 on May 23, 2012 2:02 AM

HI Tyler.
Well, here's the latest.
I found this little gem in the BIEE 10.1.3.3.3 Release Notes Documentation...
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, and 10.1.3.3.3.
Reports that use the BI Publisher data template as the data model may fail with the
following error: "Data not defined."
This error will occur if you defined a parameter in your data template but you do not
pass a value to it via the user interface. If you do not specify this parameter in the "Parameters" section of the report definition that you created using the BI Publisher Edit Report interface, then you will receive the error.
To work around this issue, either define the parameter in the Edit Report interface or remove the parameter from the data template.
That bit is now working.
Having set this up and using your guide it works if my SOAP parameters declaration passes a single value like this...
<parameterNameValues>
<item>
<name>P_INVOICE_ID</name>
<multiValuesAllowed>true</multiValuesAllowed>
<values>
<item>16641</item>
</values>
</item>
</parameterNameValues>
But if I try and pass two or more like this...
<parameterNameValues>
<item>
<name>P_INVOICE_ID</name>
<multiValuesAllowed>true</multiValuesAllowed>
<values>
<item>16641,18421</item>
</values>
</item>
</parameterNameValues>
BIP states "java.sql.SQLException: ORA-01722: invalid number"
My SQL where clause is..
<sqlStatement name="Q1">
<![CDATA[select * from vw_invoice_summary
where invoice_summary_id IN (:P_INVOICE_ID)]]>
</sqlStatement>
And the BIP error records the parameter value as P_INVOICE_ID 16641,18421 (which are legit invoice IDs)
In summary, works if I pass one invoice ID, fails if I pass two or more.
Any ideas? Or do you reckon this is now a post for the BIP forum?
Kind regards.
Simon

Web Services support for collection like ArrayList

Getting this error message:
"<Info> Did not find property empty in java.util.ArrayList:
java.lang.NullPointerException"
Are collections like ArrayList supported or am I trying to do something that
can't be done? Any suggestions?
Thanks
Danny

Hi Danny,
Betcha thought I forgot 'bout cha, huh?
I didn't ;-)
The short answer to your question is no; WLS 6.1 does not support using any of
the classes in java.util.*. However, it does support Object arrays as an element
of an Object array, which means you can have code in you service implementation
that looks like this:
public Object[] getNestedObjects()
     Object[] objects = new Object[2];
     objects[0] = new Object[]{
          new String("23.76"),
          new Float((float)23.76)
     // Here, WorkOrder is a JavaBean or an object
     // that implements weblogic.soap.xml.XMLizable
     WorkOrder[] workOrders = new WorkOrder[]{
                    new WorkOrder(),
                    new WorkOrder(),
                    new WorkOrder()
     objects[1] = new Object[]{
          new String("My name is"),
          new String("Slim Shady"),
          workOrders
     return objects;
The main issue I see with doing this is again, interoperability ;-)
If the SOAP toolkit consuming the WSDL for the web service with the above method
cannot handle the "xsd:anyType" XML Schema data type, you're in trouble. In general,
SOAP toolkits want to know what type an element is so they can process it correctly.
When you use a Variant data type (in Visual Basic) or java.lang.Object (in Java),
you are basically promoting the use of weak data typing (or late binding). From
what I've read about SOAP (well, actually what Don Box said he had in mind), XML
Schema and namespaces were adopted to combat this very thing- weak or no data
typing. Personally, I agree ;-) I think strong data typing makes processing a
SOAP request much easier and faster, for everyone. Don't get me wrong, I don't
have anything against object casting, but SOAP parameters (and return values)
are not objects. They are XML elements, just like the other parts of the SOAP
message. There is no behavior, just state. This being the case, isn't it safer
to stick with the data types (e.g. arrays, structures, primitives, etc.) defined
in the SOAP spec and "XML Schema Part 2: Datatypes" document? Enough SOAP boxing
(pun intended). If you are interested in the "complexTypes" object graphs (using
developer defined classes that implement weblogic.soap.xml.XMLizable) lab results,
I can send you a zip. The biggest difference between using JavaBeans and objects
that implement weblogic.soap.xml.XMLizable, is that you have much more control
over which Java objects the later gets serialized/deserialized to/from. With classes
that implement weblogic.soap.xml.XMLizable, the SOAP processor passes you the
actual XML stream for the SOAP parameter (which in this case, is your developer
defined class). It (the SOAP processor) also calls your developer defined class
to get an XML representation for it's data types. It works great with Java clients
(using the client.jar, of course), and I'm trying it out with .NET and MS SOAP
clients this weekend. The most interesting revelation was figuring out how wsgen
(well, actually the WSDL processor) generates the information in the <types> element
of the WSDL ;-) I actually even know how to code an XMLizable so that it produces
the exact element and attribute names I want. I also figure out how to get it
to produce an <element ...>, as opposed to a <attribute ...>, and visa versa.
Of course, WLS 7.0 (and WebLogic Workshop) make all of this a moot point, but
it was fun to get the SOAP/WSDL processors in WLS 6.1 to "do my bidding" for a
short while ;-)
Regards,
Mike Wooten
"Danny Ngo" <[email protected]> wrote:
>
Hi Mike,
Thank you for your response. Do you know if WLS 6.1 Web Services support
the
return of nested object array (object that contains other object arrays).
Thanks
-Danny
"Michael Wooten" <[email protected]> wrote:
Hi Danny,
For interoperability (with non-Java SOAP implementations)reasons, the
Java collections
are not supported in WLS 6.1 ;-) You should consider using an arrayin
place of
this.
Regards,
Mike Wooten
Danny Ngo <[email protected]> wrote:
Getting this error message:
"<Info> Did not find property empty in java.util.ArrayList:
java.lang.NullPointerException"
Are collections like ArrayList supported or am I trying to do something
that
can't be done? Any suggestions?
Thanks
Danny

XI 3.0 Sender SOAP Adapter Default XI Parameters

Hi all,
I've noticed when posting to an inbound comm channel using the sender SOAP adapter that unless I specify a namespace and interface under the 'Default XI Parameters', an error is returned indicating I need to specify default values for the namespace and interface.
This doesn't make sense. I don't want to set up a new inbound comm channel for every interface for the same sender service. As long as the SOAP address location is correct, i.e. sender service and interface are specified correctly, why should I need to set a default namespace and interface? Also, what is the expected behavior of the default XI parameters? Should it override what's passed in the SOAP location string?

Hi,
I think you have to add:
Optional: xml.addHeaderLine 0
Obligatory: try to put the ; between quotation marks like:
Hope this helps.
Cheers,
Paul

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.

Reading parameters from Query string : Sender SOAP adapter.

Hello Experts,
I have a SOAP to SOAP scenario. Here we will have multiple receivers and dynamic receiver determination is needed.
The sender will send a Value in Query string of URL to sender SOAP adapter. This value in Query string parameter will decide the receiver at runtime.
I need to know, how can we read values from Query string of incoming call? I did tried to search blogs & forum threads but unfortunately not able to hit the right links.
Any inputs will be of great help.
Should i use "Use Query String" on sender soap channel? I tried it, but i was not able to find any query string parameters in SOAP header or payload.
Please guide me, its bit urgent.
Regards,
Abhi.

> But the argument provided from their side is: They are using standard XSD and this service is provided out of box with sender application.
If they can add a URL parameter, they can also add a field to the structure.
> They cant control the value mapping of parameters in payload to the extent required to implement this change.
Adding a new field to the structure would not affect any existing mapping.
> Since they have this custom requirement of multiple receivers & receiver to be determined at runtime, they need to go for Query string.
This can be done based on any field of the payload.
> I need to find a way to read the query string in any case.
This is not supported by SOAP adapter.
> Can I use one of the header parameters to be mapped to this value (By selecting "Use Query string" & "Keep Headers" flag in sender CC) & then extract this value from header using Dynamic configuration ?
This feature works only for XI header fields, like message ID or QoS.
Not for individual parameters.

Defalt VI Parameters in SOAP Sender Channel Config

Hi all,
I have configured soap sender channel with Default XI Parameters as * for both Interface name space and Interface name.
SOAP adapter sends the message with * as the interface namespace and interface and fails with the error "No receiver could be determined".
Why is SOAP adapter is using the default XI parameters from the channel instead of the parameters passed with the SOAP message.
I could make this work specifying the Default XI parameters with correct name space and interface, but my problem is I have 2 different interfaces from the same service and cannel, I don't want to create a separate channel for each of the interfaces.
Please help.

Hi Pratat,
you have to set the
Use Query String to true and the adapter will take the service/interface data from the query string instead of the Default XI Parameters
Regards,
Nicolá

Default XI parameters in 7.1, soap sender.

Hi,
I have a quick question about Default XI Parameters in Soap sender adapter in PI 7.1.
Why are they not present in PI 7.1( sender interface and sender NS )?
which are mandatory parameters in 7.0.
I was guessing that , this ways we can create a generic soap sender CC.
Does anyone have a exact answer as why it was removed?
Regards,
Venkat..

> Even in PI 7.0 we will add interface name and CC to the URL.
> 1. Do you mean that we are supposed to have NS too along with above entries?
Yes, you should add interface and namespace as it is mentioned in SAP Note 856597
> 2. What do you mean by aligning behavior of SOAP adapter with other adapters?
Other adapters (File, JMS) get interface and namespace from a sender agreement connected to a sender channel. The behaviour of the SOAP adapter was different before.
I was told by development that migrated channels from 7.0 work without any change. If this is not the case, open an OSS ticket for this.
For new channels you have to call the SOAP adapter always with interface name and namespace. The online help is not correct.
Regards
Stefan

Soap parameters

Similar Messages

Maybe you are looking for