on 08-28-2018 9:19 AM
Hi,
After having upgraded to 4.2 SP5 Patch 5 we face the following problem:
Due to our architecture requirements we have set the CMC -> Restful Web Service URL to point the tomcat server instead of WACS one
so initially it was
http://wacs_server:6405/biprws
and was replaced with
https://tomcatserver/biprws (we have that this URL provides an XML answer when placed on the client browser)
After doing the change we have checked that the BI Web Services does not longer work fine. When we call (using Rich Client e.g) them we retrieve the message
WACS server is not running or is disabled. Unable to log in cypress service.
This error is already documented on below KBA
2233289 - Error while viewing dashboard: WACS server is not running or is disabled. Unable to log in cypress service.
Effectively we have set the parameter daaws.raylight.processing contained in dsws.properties file to true to manage so problems on the refresh of data when calling the BI web services,
But it does look like that when BI web services needs to call raylight rest he is not able to find the server when the Restful API URL points to Tomcat. If we set up again the Restful URL parameter on CMC to use WACS therefore BI web services works again.
Note: We have same issue if we try to enable SSL on WACS. If we set up the CMC -> Restful Web Service URL to the new WACS SSL URL
we have same issue that when trying to use tomcat.
Anyone has been able to use BI web services on an scenario where the Restful Web Service URL is different from the default WACS one (SSL WACS, Tomcat,.....)
Thanks,
Alfons
Looks like SSL issue.Please try tomcat URL without ssl in CMC -> Applications -> RestFull webservices .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes Bharath, you make the point.
Using the Tomcat server & WACS without SSL make it works. And using the WACS/Tomcat SSL URL doesn't.
So definitely the issue is not about using tomcat or WACS , is about using a SSL URL when calling restful SDK API on dswsbobje app.
Problem to us is that with the arrival of the new BI launchpad we must use a SSL URL when calling the restful SDK API, beacuse the the web server goes through SSL (if we don;t that we have a mix of SSL and non-SSL calls that causes below error)
The page at 'https://server/BOE/BILaunchpad' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://server/biprws/v1/logon/token'. This request has been blocked; the content must be served over HTTPS.
Question is: why dswsbobje is not able to manage a SSL URL when using the rest API?
We have checked that
Any idea?
Thanks
is the SSL transport enabled in axis2.xml ?
Hi Dennis,
Yes, it is as well as rest of cyhanges described on KBA 2010653 need to make dswsbobje work on SSL.
We have checked that we might access to SSL URL https://server/dswsbobje/services/Session?wsdl through HTTPS in browser (as well as Live Office), so dswsbobje app works fine except when it is required to use the raylight web services (uncommented line daaws.raylight.processing = true on dsws.properties file)
At the meantime on the same file <BO Install Dir>\tomcat\webapps\dswsbobje\WEB-INF\classes\dsws.properties we have found a property named
# allow to redirect Raylight calls to a specific URL (dev mode)
# daaws.raylight.processing.baseurl
but it does not seems to work (it looks like the URL considered to call the Raylight on dswsbobje is always the one defined on the CMC -> App -> Restful Web service -> Access URL)
Definitely we are missing some property that allos dswsbobje app to access Raylight (Restful SDK API) through HTTPS but we don't know which one it is (neither found any KBA/Guide explaining which one to use)
Thanks,
Is your Tomcat server different than CMS server? You need to use CMS server name , not Tomcat server name.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, the CMS server (where WACS is based) is different from the Tomcat one. We use a 3-tier architecture with a load balancer on top of tomcat. We need to use it because with the arrival of the new BI launchpad rest SDK api is used intensively by the users when browsing so we want to use the Rest API based on tomcat instead of the one existing on WACS for multiple reasons (SSL, load balancer.....)
User | Count |
---|---|
84 | |
10 | |
9 | |
8 | |
6 | |
6 | |
6 | |
5 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.