If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Cognos ISAPI problem, no Gateway URI configuration option

Started by zakatak, 31 Jan 2014 12:32:34 PM

Previous topic - Next topic

zakatak

I am in the process of building a new Cognos environment.  The Cognos portion of the environment has 3 servers; a Content Manager server, an Application server, and a Gateway server.  Each machine is Windows Server 2012.  Everything appears to be connecting to each other.  If I point a browser to http://cogweb01/ibmcognos/isapi then I am presented with the welcome page.  If I point a browser to http://cogweb01/ibmcognos I get 404.3 message stating the URL cannot be found.  When I look at the address of 404.3 I see that it is trying to use cognos.cgi whereas the one that works uses cognosisapi.dll.

In the inst_cr_winux.pdf that is included in the install files I am directed to:

Quote
11. Start IBM Cognos Configuration.
12. In the Explorer panel, click Local Configuration > Environment.
13. In the Gateway URI box, change the cognos.cgi part of the URI to
cognosisapi.dll.

However I do not have a Gateway URI box nor any values with cognos.cgi to change to cognosisapi.dll.

Any ideas what I've missed?

Ammus1234

This link will help you.
http://www.ibm.com/developerworks/data/library/cognos/infrastructure/web_servers/page599.html

Check the heading 'Making the ISAPI Gateway the default'
You need to modify default.htm and index.htm files as specified.

zakatak

Thank you, that helps quite a bit.

I'm still having an issue, but I think it might be IIS-related this time.  http://servername/ibmcognos directs me to the isapi module and everything is peachy, but http://servername.domainname.tld/ibmcognos directs me to the cgi module...

So that's fun.  Thanks again.

zakatak

So that issue that was an issue is not really an issue once I clear the browser cache on the local machine.

So thanks again.