I just want to use number from my server to change tile number, such as using URL http://10.59.XXX.100:8080/Map/dynamicTileOnlyNo
In SCN blog, they use /sap/fiori/employees/destinations/northwind/V3/Northwind/Northwind.svc/Employees/$count to set dynamic data
which stand for
/<fiori proxy>/<application id>/destinations/<destination name>/<path to OData service>/<OData collection>/<query string>
But I tried http://services.odata.org/Northwind/Northwind.svc/Employees/$count , returned:
Failed to update data via service /sap/fiori/realtimealerthttp://10.59.172.100:8080/Map/dynamicTileOnlyNo: HTTP request failed - 404 Not Found - sap.ushell.components.tiles.applauncherdynamic.DynamicTile
Why HCP add /sap/fiori/realtimealert in front? Should I set something in Destinations?
I tried add destinations in "Configure Portal Service ":
Name: northwind
URL: http://services.odata.org/
Still returned:
GET
https://flpportal-iXXXXXXtrial.dispatcher.hanatrial.ondemand.com/sap/fiori/alert/destinations/northwind/Northwind/Northwind.svc/Employees/$count
404 (Not Found)
Must I use odata or something?
As mentioned in the SCN blog, you need to use relative paths in the URL in combination with odata.
It also seems like your destinations are not configured properly.
Please check HCP documentation on this.
Related
When I try to deploy an application from WEBIDE to an internal System, it is throwing an error:
"Request cannot be routed. The server has not found any Matching resource /sap/bc/adt/discovery".
The service /sap/bc/adt is active in SICF, cloud connector and Destinations have been configured Correctly.
make sure the values in the property WebIDEUsage in the destination are correct (first a in dev_abap looks strange).
Here you have all the possible values and the explanation
https://help.sap.com/viewer/825270ffffe74d9f988a0f0066ad59f0/Cloud/en-US/5c3debce758a470e8342161457fd6f70.html
dev_abap: for extensibility scenarios and developing or deploying to
SAPUI5 ABAP Repository (corresponds to URL path /sap/bc/adt)
Definitely some services are not activated in SICF, you should check them in detail.
I have OSRM (node-osrm) set up locally and it produces correct results for routes on the server. However, when I request routes from it via leaflet routing machine I get the following error in the browser:
leaflet-routing-machine.js:2605 Routing error: Object {status: undefined}status: undefined__proto__: ObjectdefaultErrorHandler
# leaflet-routing-machine.js:2605fire
# leaflet-src.js:588(anonymous function)
# leaflet-routing-machine.js:2900_routeDone
# leaflet-routing-machine.js:4693(anonymous function)
# leaflet-routing-machine.js:4645loaded
# leaflet-routing-machine.js:46
The app works with the mapbox router and the response looks slight different (different order).
After comparing responses from a commercial server and my own server I found the problem: Leaflet routing machine (LRM) expects a route response containing:
name,
summary,
coordinates,
waypoints,
instructions.
LRM docs on iRoute
The OSRM engine does not include instructions out-of-the-box in the response, these must be added on the server after the route is returned by OSRM. The osrm-text-instructions plugin does so nicely. osrm-text-instructions
I'm trying to get the latest version of an artifact.
going to http://archiva:8080/restServices shows me the Available RESTful services: clicking on http://archiva:8080/restServices/archivaServices?_wadl leads to an empty(all white) page fore me. Opening the Development tools in my browser I get this output in the javascript-console
Failed to load resource: the server responded with a status of 404 (Not Found)
and
GET http://archiva:8080/restServices/archivaServices?_wadl 404 (Not Found)
I also read here that there should be a application.wadl but for me there isn't!
I use the latest(2.2.1) Standalone version from here
the request for a certain artifact looks like that
http://archiva:8080/restServices/archivaServices/searchService/artifact?g=eu.test&a=test&v=LATEST
Maybe you miss the contextPath in the url. For example, if you want to access the ping service. The url could be:
http://localhost:8080/archiva/restServices/archivaServices/pingService/ping.
Please notice that maybe you will get 403 due to by default archiva does not allow csrf access.
The configruation detail is: http://archiva.apache.org/docs/2.2.3/adminguide/customising-security.html
I'm trying to retrieve projects metrics using the REST Api. Therefore I first query the projects using "/api/projects/index". Afterwards I retrieve the metrics using "/api/metrics/search". Both works fine. And I result with:
[id:35476, k:com.test:TestProject, nm:TestProject, qu:TRK, sc:PRJ]
[custom:false, description:Cyclomatic complexity, direction:-1, domain:Complexity, hidden:false, id:10019, key:complexity, name:Complexity, qualitative:false, type:INT]
Now I wanted to retrieve a projects metrics. Therefore I use the following URL:
https://MYHOST/sonarqube/api/timemachine/index?resource=35476&metric=10019&fromDateTime=2010-12-25T23:59:59+0100&toDateTime=2018-12-25T23:59:59+0100
There the server retruns only: [{"cols":[],"cells":[]}]
This surprices me, because when I enter the WebInterface of sonar for the project, I can see numbers. I tried some other metrics, however all ended with the same result. What am I doing wrong?
You didn't mention server version, so I'll assume the latest: 5.2.
I got the same result for a bare query (http://nemo.sonarqube.org/api/timemachine/index), and for a query which specified resource but not metrics (http://nemo.sonarqube.org/api/timemachine/index?resource=org.sonarsource.sonarqube%3Asonarqube).
So I'm guessing there's a problem with either your resource or metric id. Try using the keys (com.test&%3ATestProject, and complexity) instead.
And yes, the ids you got back from the other web services should work here, but what's meant by "id" can be a little... ah... variable from service to service to service.
I installed a new instance of hybris server in a VM and made it available on a public internet page. I am trying to call the Product resource REST server or even a simple list of countries REST service.
http://xxx.xxx.com/ws410/rest/countries
However, I am getting an error with the status "HTTP/1.1 404 Not Found". Please can you help me?
Am I missing something? Should I Configure ws410 path somewhere?
Did you added platformwebservices extension into your localextensions.xml file ? Please ensure that you have below line in your localextensions.xml file
<extension name="platformwebservices" />
For more details check this.
ws410 is a default webroot path which is defined in platformwebservices/extensioninfo.xml file.
<webmodule jspcompile="false" webroot="/ws410"/>
Do you add the port 9001 par default on your URL. Try this http://xxx.xxx.com:9001/ws410/rest/countries