SOAP vs. GO Url

I'm currently trying to integrate OBIEE reports with my webpage and was hoping to get some advice from people who might have attempted this before. I currently have a SOAP proxy (generated by Apache Axis) and have been successful in putting the components in our site, however, the SOAP interface is very slow - taking about 700-1000 ms per request (5-6 SOAP calls, made locally)
The REST interface (GO Url) is a nice alternative, but I need to ability to pass in a 'bridge' a la the SOAP call. Is there any way to do this and, failing that, is there anything I should look at to improve the performance of the SOAP server?

Hi Sheela,
This is a PortalGO eg, which i used. Replace ! with < and # with >.
CONCAT(CONCAT('!a style="text-decoration:none" href=/analytics/saw.dll?PortalGo&PortalPath=/shared/Revenue/_portal/Revenue&Done=Dashboard&Page=Overview&Path=/shared/revenue/overview/hierarchy+vs+revenue&Action=Navigate&Options=d&p0=1&p1=eq&p2="Fiscal%20Time"."Fiscal%20Year%20Month"&p3=@{variables.selected_month}#','Revenue ($k)'),'!/a#')
Hope this helps..
Regards,
Seetharam

Similar Messages

Soap receiver target url

Hi guys,
I'm having some doubts on a soap receiver adapter.
Imagine, you use the ID to define a webservice.
Two simple synchronous interfaces, meaning, you send a string and receive another string via SOAP.
In the ID you define the comm channels, the soap sender and receiver.
My doubt is in the receiver side, you have tou specify the target URL. The problem is, how can I know the target URL, since the service will only be defined later. Meaning, I want XI to answer to a sender client which will use the WSDL generated after by the ID tool.
Where should XI answer to?
I've seen some blogs concerning some similar issues, but none concerning the problem I'm facing.
Can you guys help me or give me any hints on how to work around the problem...

Hi,
If you have a SOAP client sending a request message to XI and expecting a Response message, you need to configure SOAP sender adapter only. You do not need SOAP receiver adapter in this scenario. Sender adapter doesnt require any URL, moreover when you define a webservice in XI, you have to construct a URL where this web service can be reached.
You need the SOAP receiver adapter (where u need to mention the URL of teh service) if the receiver system exposes a webservice to which you are trying to connect from XI.
What are ur sender and receiver systems?
praveen

SOAP Receiver : Dynamic URL configuration vs. TAuthKey capability

Hello all,
I plan to use dynamic URL configuration of web service URL in SOAP Receiver CC. I got an idea, which is more or less described on SDN already. But one thing bothers me a lot.
In my scenario we talk about 10 and more WebServices' URLs to be called dynamically. The WS call will include also authorization username:passwd and it is expectable, that each WS will have different uname:passwd definition to be authorized with.
I made a capability analysis of SOAP Receiver CC - tab Advanced - Authetication keys and there are prepared only 10 possibilities to define password for authentication key (which I'll handle to CC via TAuthKey parameter).
In the help page http://help.sap.com/saphelp_nw04s/helpdata/en/29/5bd93f130f9215e10000000a155106/frameset.htm there is a note regarding authentication key:
If authentication is required for the receiver system, you can enter a password with confirmation for each key value. This means that you do not need to write passwords in the enhanced message header.
So in other words there should be a way, how to send to CC even the password with other adapter-specific message attributes. (or maybe I miss the meaning of this comment, like the other way is to develope own module for CC and process additional attribs from enhanced message header)
Does anyone have some experience with handling the authentication data in "enhanced message header" ?
Thanx for you info in advance.
Regards
Tom

Hi all,
I got an idea that the solution could be to use "Enhanced receiver determination" and use a set of Services-CommChannels with special naming convention. With this (little bit complicated) scenarion I'll get a possibility to define more then one SOAP Receiver CC => I'll get more than 10 options to store the logon password.
What do you think ?
Points for ideas guaranteed.
Tom

SOAP receiver: configure URL on runtime

Hi experts:
I have an RFCs --> XI --> SOAPs scenario. The URLs for SOAPs are always like "http://server:port/directory/xxxxxxx" and only changes "xxxxxxx". The user/passord is the same for all URLs.
My question:
There is some way to configure dynamically the URL? I have tried to use DynamicConfiguration but I must write all the URL in each (java) mapping. Server and port will change when I transport to the productive systems so I'm interested in maintaining the basis URL on the communication channel by adding the last part dynamically
Thanks

Valero Lázaro wrote:
> My question:
> There is some way to configure dynamically the URL? I have tried to use DynamicConfiguration but I must write all the URL in each (java) mapping. Server and port will change when I transport to the productive systems so I'm interested in maintaining the basis URL on the communication channel by adding the last part dynamically
>
> Thanks
use dynamic configuration itself.
in your case you will have different values for different env. i.e Dev, Qa and PRD so in the code you can check what is the current sap system (based on SID) and write the logic
ex.
// Assume XID is Dev, XIQ is QA etc
String sysName = (String) System.getProperty("SAPSYSTEMNAME");
if(sysName.equals("XID"))
//your logic here
else if(sysName.equals("XIQ"))
//your logic here
else
// your logic
the above code will help you get the SID and based on it you can set the url via dynamic conf.

Webservices soap address location url update

Hi,
Is there any way to change the soap address location in the wsdl?
I tried by changing the frontendport and host,But I don't have any option for updating the protocol(http/https) option in weblogic.
advance thanks

Thank you very much,
I followed the same document for updation of endpoint,these settings only updating the host and port ,not the frontend access protocol. End points are generated properly if both the proxy and internal app server mapping uses the same protocol.
Weblogic always using the application server protocol instead of proxy protocol.
Example:wsdl accessed from proxy with https and the internal mapping is http.
https://proxy:443/xxx/xxx?wsdl--->http://appserver:7001/xxx/xxx?wsdl--->web servies end point is http://proxy:80/xxx/xxx?wsdl but the expected endpoint is
https://proxy/xxx/xxx?wsdl.
thanks for providing any other advices

SOAP Adapter:target URL

Hi,
to have to call a webservice with different operations, i do the following:
http://host:port/WebService/Config1?style=document&method=SetMaterial
and
http://host:port/WebService/Config1?style=document&method=SetMaterial
in two different comm.channels
but it didn't work.
Some help?
thanks,
Peter Ha

hi,
check whether any authentication is required....
regards,
Sundararamaprasad.

Error when setting dynamically the target URL in receiver SOAP Adapter

Hi,
I'm setting dynamically (from the mapping) the target URL in the receiver SOAP adapter:
String url = "http://mosxd30:50000/XISOAPAdapter/MessageServlet?senderParty=&senderService=DUM&receiverParty=&receiverService=&interface=SI_OA_CustomInvoiceData&interfaceNamespace=urn:repsol.com:laboratory:firma";
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP", "TServerLocation");
conf.put(key, url);
The receiver adapter fails with:
"invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized"
Reading weblogs, etc, the most probable cause for this is a wrong target URL, but then what I did was to set it as a fixed URL in the C.Channel, and it worked, so the URL is fine.
In the communication channel, I'm using "Configure user authentication", with a user and password, and what I think it's happening is that if I use another different URL dynamically, the channel is ignoring the user authentication settings.
Any ideas?
Thanks

I forgot to say that I've checked the SAP note "FAQ Soap adapter", and it says:
Q: I get an authorization error "401 Unauthorized" from the adapter's servlet. What went wrong?
           A: The adapter's servlet is protected by default. You must use one of the user names assigned in security role xi_adapter_soap_message for component XISOAPAdapter. Please consult the documentation for Visual Administrator to view and change the security setting.
           The user authentication of the SOAP adapter is not part of the SOAP adapter but of the web container of the J2EE engine. The default authentication setting is defined in the web.xml descriptor file of the SOAP dapter web application. This setting may be modified from Visual Administrator with some restriction. Please refer to the security documentation for the J2EE engine.
           Please note that 710 onwards there is no Visual Administrator instead the Netweaver Administrator is to be used to assign the roles to the user to access the SOAP adater servlet.The user must be assigned one of the following roles SAP_XI_IS_SERV_USER, SAP_XI_APPL_SERV_USER, SAP_XI_DEVELOPER_J2EE, SAP_XI_ADMINISTRATOR_J2EE.
The target URL is a sender soap adapter (the result of one interface is sent to another one via soap adapter), and it's this one which is complaining because of the authentication I think. But I don't know why it's ignoring the user authentication flag I'm using.

Display WSDL in ID with difference URL for send SOAP scenario

Hi Experts,
I have one question here about Display WSDL tool in ID.
The first step is to specify the Integration Server SOAP Inbound Channel (URL).
Refering to the help document this URL can be either the Integration Server or an Adapter Engine.
However by simply click Propose URL option, the URL given automatically is pointing to the Integration Engine only.
http://<host>:<port>/sap/xi/engine?type=entry
Does this mean in this case, no sender SOAP adapter channel is required?
And the further question is what is the difference between URL to IE and AE.
Here i know the URL format are different, my question is what is the major difference in the processing process?
And what are the pros and cons of giving different URL when Display WSDL?
Thanks in advance. Any inputs will be appreciated.
Best Regards,

Hello,
Does this mean in this case, no sender SOAP adapter channel is required?
If it will be connecting directly to the integration engine, yes. No sender adapter is required.
And the further question is what is the difference between URL to IE and AE.
Here i know the URL format are different, my question is what is the major difference in the processing process?
And what are the pros and cons of giving different URL when Display WSDL?
The advantages and disadvantages are summed up in Stefan's blog below:
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
Hope this helps,
Mark
Edited by: Mark Dihiansan on Sep 8, 2011 5:43 AM

How to use SOAP in ColdFusion

Hi All,
The code set am using as follows
index.cfm
<cfsavecontent variable="soap">
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope
        xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
        xmlns:xsd="http://www.w3.org/2001/XMLSchema"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xmlns="http://one.dileep.com/soaptest/">
    <soapenv:Header>
    <setInit>1</setInit>
    
    </soapenv:Header>
    <soapenv:Body>
        <addNumbers soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" >
      
            <firstNumber>1000</firstNumber>
            <secondNumber>10</secondNumber>
        </addNumbers>
       </soapenv:Body>
</soapenv:Envelope>
</cfsavecontent>
<cfhttp url="http://one.dileep.com/soaptest/soaptest.cfc" method="post">
    <cfhttpparam type="header" name="content-type" value="text/xml">
    <cfhttpparam type="header" name="SOAPAction" value="">
    <cfhttpparam type="header" name="content-length" value="#len(soap)#">
    <cfhttpparam type="header" name="charset" value="utf-8">
    <cfhttpparam type="xml" name="message" value="#trim(soap)#">
</cfhttp>
<cfdump var="#xmlparse(cfhttp.FileContent)#">
soaptest.cfc
<cfcomponent output="false" >
    <cffunction name="addNumbers" access="remote" returntype="any" output="false">
        <cfargument name="firstNumber" type="string" required="true"/>
        <cfargument name="secondNumber" type="string" required="true"/>
        <cfset retunVal="NO">
        <cfset username=0>
        <cfif isSOAPRequest()>
            <cfset username = getSOAPRequestHeader("http://one.dileep.com/soaptest/", "setInit")>
          
        </cfif>
        <cfreturn arguments.firstNumber + arguments.secondNumber & username   />
    </cffunction>
</cfcomponent>
This is the right way for implimenting SOAP in COLDFUSION webservice ?
More Questios
1- 
What is the relevance of the cfc URL ? I am using sub domains
eg : one.dileep.com, two.dileep.com,yyy.dileep.com, in this case the cfc url 'http://<<subdomain>>.dileep.com/soaptest/' should changed accordingly?
2-
We have to give any tag name as Header?
3- 
SOAP body tag must be the method name that we need to exicute?
Here, I have to execute method 'addNumbers'
4- 
While retrieving the header value should we need to specify the cfc url?('http://<<subdomain>>.dileep.com/soaptest/')
Please help.

Have you read the chapter in CFWACK vol 3 on working with webservices? It's not very in-depth, but has some pointers and the usual lame-a** code example.
Depending on the complexity of what you are trying to do, you might be better off building a RESTful service instead of a SOAP service. Despite it's name, SOAP tends to be overkill if all you are doing is passing a couple of args to the webservice, but is good if the request is complex. REST is easiest if you are just sending a couple of args, but a pain in the a** if you are trying to do something complex in a single operation (works better to break down into individual state-changing calls to individual webservices).
A couple of comments on what you are doing in your code:
It's a lot simpler to use CFINVOKE than to roll your own webservice HTTP call. If you're writing your own webservice this should be especially true. I've ended up using CFHTTP to call vendor's webservices that I had no control over and wouldn't work with CFINVOKE, but that is the case where I've seen that to be true. Check out the example in CFWACK.
If you continue on the CFHTTP route, you might find it easier to use the CFXML tag instead of using CFSAVECONTENT to create the XML variable - this will allow CF to validate the xml document and ns references. It also allows you to use the CFDUMP tag to get a formatted view of the xml doc to help with debugging.
Most of the CFHTTPPARAMS you have included in your call are not really needed, at least that's been my experience. For example, this is all I ever use in my SOAP calls:
   <cfhttp url="https://adwords.google.com/api/adwords/cm/v200909/AdGroupAdService" method="post">
    <cfhttpparam name="SOAPAction" type="header" value=""/>
    <cfhttpparam type="xml" value="#ToString(variables.adAd)#"/>
   </cfhttp>
"variables.adAd" is the xml doc created by this code:
   <cfxml variable="adAd">
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v20="https://adwords.google.com/api/adwords/cm/v200909" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >
       <soapenv:Header>
          <v20:RequestHeader>
               authorization data goes here
          </v20:RequestHeader>
       </soapenv:Header>
       <soapenv:Body>
               magic happens here
       </soapenv:Body>
    </soapenv:Envelope>
   </cfxml>
Hope this helps. My experience in this is that it requires some trial and error and lots of CFDUMPs to get it right the first time, but after you get over that initial hurdle it all suddenly "makes sense" from then on.
Reed

Upgrading from 8.1 to 9.2: non-WL SOAP/websvc client timeout

So, I was using a Weblogic 8.1 'clientgen' generated a SOAP/websvc client, based on a WSDL the svc provider gave me. The generated components were accessing an Axis SOAP svc from a WL 8.1 deployed svc.
To set the conn timeout and SOAP-end-point-URL dynamically, I did this:
System.setProperty("weblogic.webservice.UseWebLogicURLStreamHandler","true");
BindingInfo bindingInfo =(weblogic.webservice.binding.BindingInfo) stub._getProperty("weblogic.webservice.bindinginfo");
bindingInfo.setTimeout(3);
bindingInfo.setAddress("http://someco.com/SOAPEndPoint");
After regenerating using WL 9.2 'clientgen', it turns out BindingInfo is deprecated, but it only says "please migrate to jws for webservices". Not sure what that means, but after some searching, I was able to figure out that I might be able to do this:
stub._setProperty(MyStub.ENDPOINT_ADDRESS_PROPERTY,"http://someco.com/SOAPEndPoint");
stub._setProperty("weblogic.wsee.transport.connection.timeout",3);
Sadly, my env is not ready yet, so I haven't been able to try it out, so I thought I'd check here for comments.
I know I could do this using Axis' wsdl2java generated components, but I want to keep it within weblogic for now.
Also, I'm suspecting that the URL stream handler is no longer needed either.
Any comments?
Karoly

Hi All,
I am also having the same problem.
Some one PLEASE HELP, its very urgent.
Thanks,

Using CopyIntoItems from Copy.asmx from a remote soap client

Hello,
I have been working on a soap client that runs on a remote client (not on the SharePoint server) and is platform-independent so that it cannot use the SP Object Model. I have managed to get most of the functionality working using SharePoint web-services except for CopyIntoItems.
My target server is a SharePoint 2007 server and I have a Document Library set up so I can upload files into it.
My soap request looks as follows.
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body>
<CopyIntoItems xmlns="http://schemas.microsoft.com/sharepoint/soap/">
<SourceUrl>http://null</SourceUrl>
<DestinationUrls>
<string>http://shpt.ad2010.local:35492/sites/targetsubsite/Test List/hello.txt</string>
</DestinationUrls>
<Fields>
<FieldInformation Type="Text" DisplayName="Test Column2" InternalName="Test_x0020_Column20" Id="{8c35c0ca-d578-47fd-b7f3-aed199141c86}" Value="Value 0" />
<FieldInformation Type="Text" DisplayName="Test Column3" InternalName="Test_x0020_Column30" Id="{6c0d3fe3-4f0d-4cff-997b-201747f83315}" Value="Value 1" />
</Fields>
<Stream>WW91IHNheSBoZWxsbywgSSBzYXkgZ29vZGJ5ZQ==
</Stream>
</CopyIntoItems>
</soap:Body>
</soap:Envelope>
The URL I am invoking this on is: http://shpt.ad2010.local:35492/sites/targetsubsite/_vti_bin/Copy.asmx
The response I get back is as follows:
<?xml version="1.0" ?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Body>
<CopyIntoItemsResponse xmlns="http://schemas.microsoft.com/sharepoint/soap/">
<CopyIntoItemsResult>
0
</CopyIntoItemsResult>
<Results>
<CopyResult DestinationUrl="http://shpt.ad2010.local:35492/sites/targetsubsite/Test List/hello.txt" ErrorCode="DestinationInvalid" ErrorMessage="The Copy web service method must be called on the same domain that contains the destination url."/>
</Results>
</CopyIntoItemsResponse>
</soap:Body>
</soap:Envelope>
I am unable to find any help on the error mentioned here. I have tried setting the source URL to something valid (I have to make it up because there really is no source URL as I copy from the remote client).
I wonder if I can even use the CopyIntoItems request (or the Copy web-service as a whole) from a remote soap client, and whether it was only meant to be used for copies between SharePoint Sites. Any clues are much appreciated.

I am trying to use the copy.asmx service to upload a file from a custom sharepoint form into a document library, and I can only use javascript with jquery. (no visual studio)
I have a similar soap envelope.
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body>
<CopyIntoItems xmlns="http://schemas.microsoft.com/sharepoint/soap/">
<SourceUrl>C://dir/file.txt</SourceUrl>
<DestinationUrls>
<string>http://[server]/sites/subsite/Demo List/sample.txt</string>
</DestinationUrls>
<Fields>
<FieldInformation Type="Text" DisplayName="Title" InternalName="Title" Id="{fa564e0f-0c70-4ab9-b863-0177e6ddd247}" Value="Test Value" />
</Fields>
<Stream>base64Binary</Stream>
</CopyIntoItems>
</soap:Body>
</soap:Envelope>
I'm getting a 500 "internal server error" back.
Can anyone see what I'm doing wrong ?
Kris Blair

Dynamically loading the url of a web reference object in C#

Hi,
We have a number of assemblies (C# - VS 2010) that access third party web services via SOAP. The url to access the site is part of the web reference object.
We have need to be able to change the url used to access the service at run runtime when conditions require.
What would the be the best practice of dynamically setting the url to be used at run time?
Thanks in advance.
SanDegan99

You could specify the URLs as keys in the application configuration file (App.config or web.config) of the main application:
https://msdn.microsoft.com/en-us/library/system.configuration.configurationmanager.appsettings(v=vs.110).aspx
https://msdn.microsoft.com/en-us/library/aa374182(v=vs.85).aspx
App.config:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" />
</startup>
<appSettings>
<add key="url1" value="http://www.url.com/test.asmx"/>
</appSettings>
</configuration>
You can then retrieve these values using the ConfigurationManager class in any assembly that is referenced from the main application like this (add a reference to System.Configuration.dll):
string url = System.Configuration.ConfigurationManager.AppSettings["url1"].ToString();
You can change the values of the keys in the application configuration file without having to recompile the application.
The other option is to specify the URLs in a database or some other persistent storage from which you read at runtime but configuration files are generally used to store these kind of variable application settings.
Please remember to mark helpful posts as answer to close your threads and remember that any new question you may have should be asked in a new thread of its own.

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.

Sender SOAP Adapter with HTTPs call

Hello,
Our scenarion is .. we will have a sender SOAP adater .. but it needs to be called using HTTPs(SSL).
Now considering we have the certificate generated and installed ..and that integration server is HTTPs enabled....What URL should the sending system call..?
For normal HTTP call the inbound address for inbound Adapter is: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
For the case of HTTPs just changing the htttp to https and the port number in in the calling system will suffice? Or is there other configurations that needs to be done??
Thanks and Regards,
Himadri

Hi Himadri,
Firstly as suggested by others you can call using https and give the https port in the soap adapter servler URL. Secondly you need to do the following configurations:
1) If its PI 7.0/3.0, deploy the latest version of the SAP Java cryptography toolkit.
2) Configure SAP PI as the server for HTTPS calls. In short
      Using the SSL Provider service:
                            a.      Select whether the J2EE Engine should:
                               ■      Request (but not require) that the user presents a client certificate for authentication.
                               ■      Require that client certificates are to be used for authentication.
                            b.      Import the CAu2019s root certificate into the Trusted Certification Authorities list. (Choose Add.) using the following For all the steps, link is mentioned below for XI 3.0, you can find similar ones for PI 7.0
http://help.sap.com/saphelp_nw04/helpdata/en/f1/2de3be0382df45a398d3f9fb86a36a/content.htm
3) If you want to enable client authentication then you would need to add the client certificate in the TrustedCA keystore view of the SAP J2EE engine.
4) In the SOAP Adapter sender channel, configure Inbound Security level as HTTPS or HTTPs with client authentication based on your scenario.
Best Regards,
Pratik

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

Reg: soap client

while i am trying to test my webservice in soap client it throws
error
Failed to parse soap message
Original(raw) message:
com.sap.uddi.generic.impl.soap.NativeSOAPException : Failed to open socket
Cause : class java.net.ConnectException : Connection refused: connect
can anyone help me out

HI Ajay,
Same kind of problem is discussed here... Please check..
SOAP Request
Target URL for SOAP client
Re: Error in Webservice call
Cheers..
Vasu
<i>** REward Points if found useful **</i>

SOAP vs. GO Url

Similar Messages

Maybe you are looking for