visual analyzer landing page is not loading after adding /va in httpd.conf file and mod_wl_ohs.conf file
944333 wrote:visual analyzer landing page is not loading after adding /va in httpd.conf file and mod_wl_ohs.conf file
Hi, could you please spend few more minutes writing all the things you forgot in the previous message?
I'm sure your tool as a version, you mention an httpd.conf file which means you don't have "just" an OBIEE as you have a webserver in front etc.
Don't expect people to spend time guessing all you didn't write.
The better the question is, the better the answer will be ...
we are using OBIEE12.2.1.0 and OHS Version 11.1.1.9
in httpd.conf we have added follwing parmeter:
RewriteRule ^/$ /analytics/ [R,L] -- analytics is working
RewriteRule ^/$ /va/ [R,L] -- va is not working
and mod_wl_ohs.conf file we have added following parameters:
<Location /analytics/>
#AuthType Osso
AuthType Oblix
SetHandler weblogic-handler
WebLogicHost xxxxx
WeblogicPort xxxxx
#WLProxySSL ON
#WLProxySSLPassThrough ON
</Location>
<Location /va/>
WebLogicHost xxxxxx
analytics is working but va is not working
My memories of Apache HTTPD (OHS is just that in the end) rewrite rules are almost 20 years old but ....
944333 wrote:in httpd.conf we have added follwing parmeter:RewriteRule ^/$ /analytics/ [R,L] -- analytics is workingRewriteRule ^/$ /va/ [R,L] -- va is not working
How is that supposed to work?
You have the first rule saying to take /<whatever or even nothing> and send to /analytics/, with the R and L flag.
R = HTTP-302 redirect sent the to the browser
L = last, stop processing any other rule
And after you say that /<whatever or even nothing> must be sent to /va/ . First you will never hit that rule because any kind of request will match the first rule, and the L flag will stop the processing.
You can't have the same match but sending to 2 different places.
That's your error, write 2 rewrite rule which could coexist and the web server will act accordingly.
Right now everything is working as expected, at configured at least.
In other words, the question is: what do you want your OHS to do? What is the expected behaviour? The httpd.conf must follow the answers to those questions and only that.
Hi Gianni,
We want to redirect actual URL. we does n't want to show actual URL to any user.
With BIGIP/analytics -- page is coming with 5 sec.
with BIGIP/va - in stage environment which is coming with in 50 sec
with BIGIP/va - with the same changes VA landing page is showing LOADING status in production
Did changes in httpd.conf to RewriteRule ^/$ http:/xxxxxxxxxxxxxx.xxx.com/va/login.jsp [R,L] still taking 50 sec.
