Jasper Server Asynchronous report execution not working with multiple server instances - rest

I'm implementing the Asynchronous report execution with Jaspersoft and follow the docs. I have 2 jasper server instances and traffic is manage through a load balancer and the load balancer supports only round-robin policy.
According to documentation, reportExecutions API (http://:/jasperserver[-pro]/rest_v2/reportExecutions) successfully returns a requestId. But report polling service (http://:/jasperserver[-pro]/rest_v2/reportExecutions/requestID/status/) always gives 404 resource.not.found error.
When server running on a single instance, all APIs are working properly.
I'm using the TIBCO jasperserver 7.1.0 Enterprise edition.

According to this, the issue is in cookies. Getting "Cookie" header from response of the reportExecutions API and adding it to polling request will solve the issue.

Related

Can my Web Server Issue a Client Rest Request to another REST Server

I have a web server that handles configuration set-up for various IO devices. I need to get some data from a REST server that is running on a different server. Can that web server code issue a client REST GET command to a REST server running on a different server? I tried it but I get a http 500 error. The server code is failing on the REST server request code.
I am closing out this question. Yes, your server can issue http requests to other services. I was having another problem with a self-signed certificate and the error made it look like their was a problem with my http request service.

Confugaration/steps needed when consuming external Restful service from Fiori front end server

I have deployed a custom UI5 app ( using external REST ful services--> service hosted in another Java stack system) in the front end server.
I used Ajax to call the service directly with the URL as shown below.
This app has run successfully when i use "proxy" in local host(eclipse).
-->Ajax Call code Snippet
So i replaced proxy with target url while deploying in front end. (http ://xxx.xxx:port)
When running from front end server i got cross origin error as shown below.
Error1:<http://xxx:port/xxx/ngservices/rest/query/ZQUE_WEBSERV_APPHISTORY/executeGet. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://xxx:port' is therefore not allowed access. The response had HTTP status code 401>
After enabling CORS plugin in chrome i got unauthorised error as shown below.
Error2:<http://xxx:port/xxx/ngservices/rest/query/ZQUE_WEBSERV_APPHISTORY/executeGet. Response for preflight has invalid HTTP status code 401>
I got the above errors initally while running from localhost.After that i used proxy and it got solved.
I just deployed the app in frontend server and ran it directly. I haven't done any other configurations.
Do i need to do any extra configurations for consuming these external services or kindly suggest any other suggestions.
Important info:
*Able to call external service from localhost(eclipse--> used proxy here) but not able to call service from frontend server.
*Front end architecture: Central hub deployement and connected to SRM,HR and CRM backends currently.
Regards
Phani Poorna
Both of these errors can be solved by creating and configuring a destination on your platform.
A destination is essentially a proxy: when you create it, you specify the backend URL, the authentication mechanism (Principal propagation/basic authentication etc). From your client, you just need to then connect to your destination to query the backend.
What do you mean by Fiori front end server? Are you referring to the Portal service hosted on HANA Cloud Platform?
If so, then you can create a destination by going to Connectivity - Destinations from your HCP account. From your Fiori application, you then need to connect your destination using the following URL pattern:
/destinations/<destination name>/<whatever you want to add to the URL the destination points to>
If you are using a different PaaS, I'm sure it will have some similar way of creating a proxy between your client and your backend. (Edit: I just saw you're using the Central hub deployment - I am not familiar with this system but it must have a very similar way of creating destinations).
Hope this helps, let me know if you have any questions.

What is the difference between Report manager URL and web service URL in ssrs 2008

What is the difference between Report manager URL and web service URL in ssrs 2008 r2?
The Web Service URL page to configure or modify the URL used to access the report server.
The Report Manager URL page to configure or modify the URL used to access Report Manager.
The report server is the central component of a Reporting Services installation. It consists of a pair of core processors plus a collection of special-purpose extensions that handle authentication, data processing, rendering, and delivery operations. Processors are the hub of the report server.
Report Manager is an ASP.NET web application that provides report management/viewing capabilities for a Reporting Services instance configured in native mode.
For more information please see:
http://msdn.microsoft.com/en-us/library/ms188133.aspx
http://msdn.microsoft.com/en-us/library/ms181174.aspx

Get data from a remote server using WSDL

My remote server expose some methods in WSDL. Is it possible to use this WSDL within jasper server to get data? I looked into examples that Jasper consume data that are available in the XML but didn't found anything on using web service (WSDL).
Thanks

Apache can't send request to localhost:8080 (to use Mule Esb Flow)

I'm trying to use a sample web application that use Ajax to send a request to a php REST service.
I need to use Mule ESB to do this, so i fix my ajax function to send request to ESB on localhost:8080. But the browser said that i can't do this for security reason.
So, there are any way to use mule ESB with a web app (local appache server) locally ?
Trying to GET a resource from the same host but from a different port is considered cross scripting as explained here
If you want to retrieve it you can:
all the option listed at the above link
put mule behind a reverse proxy within your apache configuration
serve all the content via mule