Qaaws web services URL is not correct

Hi,
When i am trying to login in Qaaws its showing warning "Web service URL is not correct" for BO server with a yellow icon and in Authorization dropdown its showing nothing.It was working fine in the past, the same problem with Live office also.
Please help.

No,is is saying on browser the following error:
HTTP Status 404 - /dswsbobje
type Status report
message /dswsbobje
description The requested resource (/dswsbobje) is not available.
Apache Tomcat/6.0.24
Regards
vishnu

Similar Messages

Qaaws "Web services url is not correct" while adding host.

Hello all,
            I am getting error "The web services Url is not correct" while adding the host name for Qaaws. The error is coming on the right side of the input text field of the Name showing by yellow warning icon.Please help me to resolve it.I was tried by keeping the host name instead of ip address.But is saying the same error.
regards
vishnu

To enable rest support there are some instructions below:
Before undertaking this process, I recommend backing up the file(s)
you are going to edit.
By default REST is disabled in Axis 2. We need to enable it. We
need to go to the following folder. Assuming D: is the installation drive:
1.     D:\Program
Files\Business Objects\Tomcat55\webapps\dswsbobje\WEB-INF\conf (for 32 Bit OS)
or D:\Program Files (x86)\Business Objects\Tomcat55\webapps\dswsbobje\WEB-INF\conf (for 64 Bit OS)
2.     There is a file with the name axis2.xml (This file is an XML File and contains many parameters as well as many other things).
3.     Make a backup copy of the filename you are about to edit.
4.     Open the axis2.xml file in Notepad or 'XML Editor' to edit
5.     Search for the word REST (Ctrl & F is probably easiest)
6.     You will see a line like this
<parameter name="disableREST" locked="true">true</parameter>
We need to replace' true' with 'false' to enable REST, and after the changing that line will look like following:
<parameter name="disableREST" locked="true">false</parameter>
7.     Save the file and restart the web server.

Edit QAAWS web service

Hi,
I am trying to publish a report block with the same name. I want to replace the existing one. The only changed I made to the block is replace a column.
Please help!
Thank You
Veena

Hi everybody, don't know if this post is reallyb up to date but I had faced the SAME problem with a fresh installation of BO BI 4.1 SP2.
Trying to set the connection in the QAAWS Designer always gave the error: Web Services URL is not correct. After a while we've figured out how to solve it:
When you insert the new host the link to the URL is auto generated like this:
http://BO BI SERVER NAME:8080/dswsbobje/services/Session. THIS LINK IS WRONG!!
Try tiping this: http://BO BI SERVER NAME:8080/dswsbobje/services/Session?wsdl adding the "?wsdl" string to the URL and everything will work!!!
Hope this can be helpful.

HTTPS Web Service datastore : does not work in case of proxy

Data Services 12.2 on Windows XP SP2
I've set up a datastore, type "web service", url is https://.... (an external web service, outside of our company)
I'm able to import the functions of this web service into the datastore.
In a DF, in a query transform, I call one these functions.
The job fails with this error message :
There is no response for the web service <searchCertificate>. Ensure that the network, web server, and service are running properly. Also ensure that the service client call time out is set properly.
I'm sure the web service is active. I have to pass a proxy.
When I do not have to pass a proxy (when I execute this job on my laptop not connected to the office network) the job runs fine !
How can you configure the axis2.xml so that https can run with a proxy ? (no problem to do this for http web services, but I do not see a solution for https web services !)
Thanks !!

Hi Sukarna,
the connection is not the problem.
Actually I've tested the scenario of abap proxy --> PI -->abap proxy for the same interface, it works fine. Only when I try ws instead of proxy, I got this error. Since proxy scenario works fine, the connection should not be issue.
any more clues?
Thanks

Error "web service destination is not configured" in CTS+

Hi experts,
during deployment with CTS+ I get the error "web service destination is not configured" (see below). In fact there is a web service to be deployed and a WebDynpro-DC using this web service as adaptive web service model. The model uses the destination DACC_PI_WS_METADATA_DEST and DACC_PI_WS_EXECUTION_DEST. I configured both destinations in the server with type "WSDL".
Any idea what goes wrong?
Regards,
Christoph
1 ETP199 ######################################
1 ETP199X######################################
1 ETP189 DEPLOYMENT
1 ETP101 transport order     : "JADK900006"
1 ETP102 system              : "JAQ"
1 ETP199X######################################
1 ETP189 DEPLOYMENT
1 ETP101 transport order     : "JADK900006"
1 ETP102 system              : "JAQ"
1 ETP108 tp path             : "tp"
1 ETP109 version and release : "372.04.29" "700"
1 ETP198
2 EPU601X"CTS Deploy Service - Version 0.92" "06.03.2007" " " " "
2 EPU602 "==================================================""======================"" "" "
===="" "" "
2 EPU601 "Deploy web service destination =" " " " " " "
2 EPU601 "Directory =" "/usr/sap/trans/data" " " " "
2 EPU601 "SDM Deploy URL =" " " " " " "
2 EPU601 "SLD Deploy URL =" " " " " " "
2 EPU601 "XI Deploy URL =" " " " " " "
4 EPU607 Non-ABAP system "JAQ" (communication system "KSM")
4 EPU601X"Deploy for" "SDM" " " " "
4 EPU601 "Deploy File =" "karmann.comSC_DACCDIP_DACCD_C~20081001122205.sca" " " " "
4WEPU601 "Web service destination is not configured" " " ", deployment skipped" " "
4WEPU601 "Return Code =" "4" " " " "
4WEPU601 "Highest Return Code =" "4" " " " "

Hello,
I am getting an identical error per below. I have checked Web deploy service, CTSDEPLOY setup in SM59 etc and looks OK, yet the issue still occurs:
   Deployment
   Transport request   : BWDK903389
   System              : BWQ
   tp path             : tp
   Version and release: 372.04.36 700
   CTS Deploy Service - Version 0.92 06.03.2007
   ========================================================================
   Deploy web service destination =
   Directory =
   SDM Deploy URL =
   SLD Deploy URL =
   XI Deploy URL =
   Double-stack system BWQ
   Deploy for SDM
   Deploy File = CTSTEST_20081008_123719.epa
   Web service destination is not configured   , deployment skipped
   Return Code = 4
   Highest Return Code = 4
   Deployment
   End date and time : 20081015162015
   Ended with return code: ===> 4 <===
Anyone have any ideas on this one?
Thanks & Regards,
Michael

AE url is not correct

Hello,
while monitoring AE I observed AE URL is not correct. My server name is ServerXX
Then, I should see the URL for testing my message in RWB as below.
http://ServerXX:50000/MessagingSystem/receive/AFW/
But it is showing ServerYY which i am not sure where this come from.
Can anybody tell me where this server name picks by AE in RWB. So that i can check and change.
Thanks,
Srinivasa

Hi ,
Check it in visual administrator
>cluster>server>services> SAp XI adapter : XI.
In this check xiadpater.url : It should be correct orelse change to the correct url.
Regards
vijay

2 Java ME Web Service Errors of "Not Compliant with JSR-172"

This happened when I use Microsoft's ASMX-based WSDL file on a Java ME WS client.
Say I had a test.asmx WSDL. Then I use NetBeans, and I go to New > Java ME Web Service Client
I tried to import from running web service, URL "http://www.testhost.com/wspackage/test.asmx?WSDL"
and then the popup validation error told me "Reference in element is not supported by this version of stub compiler"
also the X logo error told me "testasmx.wsdl is not compliant with Java ME Web Services specification (JSR-172)"
I wondered what's going on? Is there any data types not supported by JSR-172? Which is it?
When I "Validate XML" this ASMX file, it pops this:
"Error: src-resolve: Cannot resolve the name 's:schema' to a(n) 'element declaration' component."
The "types" section of my WSDL are like this:
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://tempuri.org/MMWebServices/Coverage"
xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
targetNamespace="http://tempuri.org/MMWebServices/Coverage" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
<s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/MMWebServices/Coverage">
<s:import namespace="http://www.w3.org/2001/XMLSchema" />
<s:element name="ViewListDoctor">
<s:complexType>
<s:sequence>
<s:element minOccurs="1" maxOccurs="1" name="iUserId" type="s:int" />
<s:element minOccurs="1" maxOccurs="1" name="iASchId" type="s:int" />
<s:element minOccurs="0" maxOccurs="1" name="sSearchKeyword" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="dsView">
<s:complexType>
<s:sequence>
<s:element ref="s:schema" /> // <<error occured on this line, and every time the ref="s:schema" shows up <<
Anyone have experienced this?

Yes, thx u. I didn't realized I was posting on the wrong section (Enterprise) so I posted again to the J2ME/MIDP section since it was all about mobility. Please delete the first post.

Web Service URL length limits, LV2013 vs LV2012

(* CROSS POST: http://lavag.org/topic/18435-web-service-url-length-limits-lv2013-vs-lv2012/ *)
(* Please reply in this forum. I have marked the other thread to put replies here. *)
Has anyone noticed a reduction to the limit on URL length for Web Services between LV versions 2012 and 2013?
Under LV2012, a RESTful web service appears to accept URL with lengths at least as long as 4096 characters. With LV2013, the max URL length appears to be 511 characters for both RESTful and Project Item web services. Unfortunately for me the project I just converted trips over this issue. My goal with posting this query to here is to improve my understanding of this limitation before I decide how best to modify my code. Certainly using POST rather than GET with a long URL is an option, but again, I'm looking to understand the change in limitation before I choose a solution.
To illustrate I have attached three mostly identical projects which demonstrate the issue. In each case the project contains a webservice consisting of a single VI, "ComputeLength", which takes a String as an input parameter and which outputs the length of the string. The three projects are as follows.
1. LV2012 RESTful web service.
2. LV2013 RESTful web service.
3. LV2013 Project item web service.
The web service contains a single VI. For the RESTful examples, the web service is started by selecting Deploy from the Build specification right click menu. For the Project Item example, the web service is started by selecting Start from the MyComputer/WebService right click menu. The use of this example is demonstrated with the following URL:
(note that the port is 8080 for the two RESTful examples and is 8001 for the Project item web service if used in Debug mode, which is the default for the above instruction.)
http://localhost:8080/webservice/computelength?string=1234567890
And the output looks like this.
<Response>
<Terminal>
<Name>StringLength</Name>
<Value>10</Value>
</Terminal>
</Response>
To see the issue, extend the string parameter such that the URL contains more than 511 characters beyond the port number. For example something like this, http://localhost:8080/webservice/computelength?string=1234567890123456789012345678901234567890....(keep repeating)
For the LV2012 example the string parameter may be at least as long as 4000 characters, which I've demonstrated using Chrome as my browser. For both of the LV2013 examples the URL is limited to 511 characters after the localhost and the port number.
Anyone know whether this is a bug or this is an intentional design change? How about whether the URL length limit is configurable?
I am also consulting NI tech support and will report back their response.
Any advice appreciated.
Thanks,
Martin
Solved!
Go to Solution.
Attachments:
mywebservice.LV2012.RESTful.zip ‏12 KB
mywebservice.LV2013.RESTful.zip ‏12 KB
mywebservice.LV2013.ProjectItem.zip ‏11 KB

Solution found. Apparently starting in LV 2013, there is a default limit of 512 to the URL length. The default limit may be overridden as described below.
Martin
This is Brian in Applications Engineering from National Instruments. I am following up regarding the 511 character limit in your Web Service HTTP request following the port number. After some research I've figured out that the issue is related to a default web server setting called "LimitUri," which limits the maximum length of a URL. The default setting is 512 characters which is why we are seeing this issue.
There are multiple ways of changing the URL length limit depending on how you are using your web service. If you are publishing the web service using the Application Web Server then modify "C:\Program Files (x86)\National Instruments\Shared\NI WebServer\NIWebAppServer.conf" and add "LimitUri 4096" to the end of the file without the quotes.
If you are running the Debug Web Server by just clicking start on the web service then modify "C:\Program Files (x86)\National Instruments\LabVIEW 2013\resource\webserver\niwsdebugserver.conf" and add "LimitUri 4096" to the end of the file without the quotes.

Dynamic Web Service URL

I'm using a .Net based web service to fetch data. The exported XCelsius will be deployed on the customer's environment along with the web service. In that case, the SWF file should connect to web service deployed on my customer site. But, it looks for the hard coded path of the web service. In XCelsius designer, there is no option to pick the web service URL from a cell, as available in the "XML data" button. Is there any other way to pass on the Web Service URL dynamically to the SWF file. Please note, I may use more that one web service connectors in my SWF file.

With regards to the Web Service Connector in CX, you can dynamically set the URL/end point path of the Web Service if you have installed the latest hotfix of CX:
http://support.businessobjects.com/communityCS/FilesAndUpdates/crystal_xcelsius_4.5_hotfix.zip.asp
After, you will see in the properties of the Web Service Connector by tying it to a cell in the speadsheet.

Invalid Web service URL

Hi All,
While creating a model in VC7.0 based on an external webservice(ex: http://api.google.com/GoogleSearch.wsdl), I ended-up with Invalid Web service URL error.
Note: When I access the same WSDL URL using browser it didn't ask me for user authentication, the XML file was opened neatly.
Please assist.
FYI- Portal Version is NW2004s SP16.
Kind regards,
Vijay

Hi Fabien,
Thanks for your feedback.
Yes, I had tried with simple and local one, and found success in that as well.
But, this time I would like to create a model based on the some 3rd party webservice available in internet.
If you know few simple 3rd party webservice available in internet as like the one I have mentioned in my initial post, that would be helpful to me.
Many thanks.
Kind regards,
Vijay

Web Service in Workflow not writing back

Hi,
Ive created a simple Web service that gets the supervisor Id from the form creator Id.
Ive tested the service on the SOAP services page and it works as expected.
But when I try to use this webservice in a workflow it doesnt write the values back into the from-variables.
Also, when you assign the formvariables to the WS-variables in the QPAC properties, the xpath boxes are not really always at the same place, ie. not filled with data or the like.
Is there a serious bug in the webservices QPAC?
Im using LC WF designer 7.0.
Id be thankful for any kind of advice how I can get webservices to run correctly in the designer.
Cheers
Gunther

Hi Gunther
I'm not sure why you're not getting return values.
I suggest you actually try using the external web services, and see whether they work.
One of the issues may be that the wsdl of the web service you're invoking is very complex, more complex than the parser that is built into the Adobe Web Service QPAC is capable of handling. So the web service may be executing correctly, but the data is not being extracted correctly. Perhaps! If this is the case, we do have another web service QPAC you may want to try. It's takes a simpler approach than the Adobe one - rather than trying to parse the schema and present variables to you, it simply allows you to provide a xml input document, and returns a xml output document. You can embed process variables into the input doc, and can assign the output do to an XML variable, where you can use XPath expressions to extract the data. This is currently in beta, if you'd like an early copy, please let me know.
Howard
http://www.avoka.com

Substitution variable for Web Service URLs

Hello all,
I'm building some RESTful web service references into an Apex 4 application.
I have a requirement to incorporate different web service URLs, depending on the environment (Dev, Test, Live etc.).
I'd like to design this so that Apex can pick up the URL from a substitution variable, and I'm not able to do this.
Can anyone help with this, or suggest a workaround?
Thanks,
Rhodri

Hi Jason,
Thanks for your reply.
Could you please explain where you used the substitution variable as the URL Endpoint of your REST Web service reference?
I'm trying to create a Rest Webservice reference (Shared Components > Edit REST Web Reference) and use the substitution variable as the URL in the definition, and &SUBST_VAR. does not seem to work there.
Thanks,
Rhodri

Invalid Web Service URL Error

I am trying to access define a new webservice system using the WSDL for my local queryview web service. When I put in the WSDL URL it comes back with a "Invalid Web Service URL" error. If I put the URL in the Browser address, it successfully brings back the web service information. Any ideas why I can't define this web service system?
http://<server>:8001/sap/bw/xml/soap/queryview?sap-client=040&wsdl=1.1
<server> is a token for posting concerns...
Thanks!

I am imagining that the BW QUERY_VIEW_DATA web service complies to the Basic Profile 1.0.
And I don't quite understand this part?
<i>In addition, connections to Web services for SAP backend systems must be performed via logical destinations (configured in the SAP J2EE engine with the Visual Administrator) and not via portal systems</i>
Since the QUERY_VIEW_DATA Web Service resides on my BW system is the BW system considered a SAP backend system? Any guidance is greatly appreciated.

Web Services Demo (OTNMobileWrapper) not works

I tested in my own database environment and also at my account on htmldb.oracle.com.
- Wheather service works fine
- Amazon works fine
- OTNMobileWrapper did not
I believe the URL and the Action are wrong!
(the Urls in Wheather and Amazon I can call in the browser directly, the Url from OTNMobileWrapper was not found).

yeah, i see what you mean regarding that "OTN Message Service" option in our web services demo. further inspection by a teammate reveals that more than a few of these OTN Live Web Services appear to not be working. i'm currently checking around to see what the deal is with that, but from an html db perspective, though, you should already know what you need to know: it is possible to call web services from within your html db applications. this particular one in our example appears to currently be unavailable (if you do feel it's our "URL and action", btw, please do send that info to [email protected]), but calls to the more stable ones like amazon, for instance, always work.
hope this helps,
raj

EP6 SP2 APIs through web services/urls?

Hi,
One general question to begin this thread -
Can I do anything the portal APIs (UME, KMC and all
the rest) allow me to do and expose it for external
application usage as a web service/url/whatever? If
no, who knows what can be exposed and what is not?
Thanks all,
Yuri

Anyone?

Qaaws web services URL is not correct

Similar Messages

Maybe you are looking for