Hi,
We're upgrading from 11.0.1 to 11.1.4 and running into problems with our Netscaler.
It currently redirects <main-site>/bi to <cognos-server:9300>/bi and (I think) <main-site>/ibmcognos to <cognos-server:9300>. In 11.1.4, it's trying to access many different top-level directories like "drill", "prompting", "skins" and others. It seems that anything under <cognosdir>/webcontent is possible. The Netscaler doesn't know what to do with those so all those files aren't found.
Does anyone know if there's a way to get Cognos to look for all those under <main-site>/bi or <main-site>/<some-dir> instead of in the root directory?
Thanks,
Jack Goldstein
Quote from: jackg_tor on 16 Apr 2020 05:11:34 PM
Hi,
We're upgrading from 11.0.1 to 11.1.4 and running into problems with our Netscaler.
It currently redirects <main-site>/bi to <cognos-server:9300>/bi and (I think) <main-site>/ibmcognos to <cognos-server:9300>. In 11.1.4, it's trying to access many different top-level directories like "drill", "prompting", "skins" and others. It seems that anything under <cognosdir>/webcontent is possible. The Netscaler doesn't know what to do with those so all those files aren't found.
Does anyone know if there's a way to get Cognos to look for all those under <main-site>/bi or <main-site>/<some-dir> instead of in the root directory?
Thanks,
Jack Goldstein
Hi,
I'm not an expert on web servers, but the first thing I'd ask is have you set up your web server using the 11.1.x steps?
https://www.ibm.com/support/knowledgecenter/SSEP7J_11.1.0/com.ibm.swg.ba.cognos.inst_cr_winux.doc/t_gateway_iis.html
The above is for IIS - you didn't specify which web server you are using.
Cheers!
MF.
Hi MF,
Thanks for the quick reply.
I'm running on Linux with everything on the same system using the built-in Websphere Application Server. To be honest, I just skimmed over that whole gateway section because everything seemed to be working without it. It was only when we moved from our beta-test to production that it stopped working because the former was forwarding all traffic starting with the site name to Cognos while the latter depends on the "/bi" prefix.
I'll read over that section now, more carefully. Thanks for the tip.
Jack
For completeness, I'll say that we ended up changing the Netscaler from a common top-level web site with "/bi" directed to the Cognos system (e.g. "https://oursite.ourdomain/bi") to a top-level site just for Cognos (e.g. "https://cognos.oursite.ourdomain") and then changed the former to point to the latter.