Cognos Gateway

[mrcool]

Hi All,

Sorry if my question sounds foolish.

I am trying to understand the exact use of the Gateway URL in the Cognos server configuration. The reason being when I changed the URL to some something like xxx:port/... and started the service it worked without any issue and I was able to access the cognos portal without any problems.
Could you please tell me the exact use of the Gateway URL.

Thanks,
Mc

[jeffowentn]

This might help you.

http://www-01.ibm.com/support/knowledgecenter/#!/SSEP7J_10.1.1/com.ibm.swg.ba.cognos.c8pp_inst.10.1.1.doc/c_changeauri.html%23ChangeaURI

Depending on what version you are using, there are two different methods....  cognos.cgi and cognosisapi.dll.  Your configuration and landscape will dictate which approach you should use.

Jeff

[cognostechie]

The meaning of Gateway URI is to make Cognos look at the web server (IIS in most cases) and find out the physical location of the directory which houses the execution file and then execute it. So if the gateway URI says http://rainyserver/cognos10 then it will go to IIS of rainyserver and find out a virtual directory called cognos10, then look at an entry called cgi-bin which will point it to a location and the name of execution file (cognos.cgi or cognsoisapi.dll) and then execute that file.

I am not sure what you mean by saying that it still works when you change the name of the server and the port number. Try clearing the cache and see if it still works.

[jeffowentn]

Thanks, Cognostechie, for the great response that is easy to understand!

[mrcool]

The meaning of Gateway URI is to make Cognos look at the web server (IIS in most cases) and find out the physical location of the directory which houses the execution file and then execute it. So if the gateway URI says http://rainyserver/cognos10 then it will go to IIS of rainyserver and find out a virtual directory called cognos10, then look at an entry called cgi-bin which will point it to a location and the name of execution file (cognos.cgi or cognsoisapi.dll) and then execute that file.

I am not sure what you mean by saying that it still works when you change the name of the server and the port number. Try clearing the cache and see if it still works.

Thank you so much for the clear explanation.
For ex: If I change the URI to http://sunnyserver/cognos10 and save the configuration it doesn't throw any error. When I used http://rainyserver/cognos10 after the changes, I am still able to access the cognos portal without any issues.
Should I clear the IE cache or something else?

Thanks,
mc

[Daljith]

Doesn't that mean gateway is configured on both the servers - rainyserver  and  sunnyserver.

[mrcool]

No Anna.I named sunnyserver as an example. I have only one gateway.

[Daljith]

ok, can you paste the actual both the exact links that you tried and both are working fine.

[SomeClown]

It's in server config by default but is mostly used by client software which may be installed into the same location.  In the 32-bit days, server components resided in the same directory as client components (Framework) so they used the same configuration information.  Client components use it for the authentication dialog.   For server, the setting in configuration has little effect (more like reference), though I think it might also populate the title bar on the browser (shows sunnyserver as gleaned from the gateway setting).   

[mrcool]

It's in server config by default but is mostly used by client software which may be installed into the same location.  In the 32-bit days, server components resided in the same directory as client components (Framework) so they used the same configuration information.  Client components use it for the authentication dialog.   For server, the setting in configuration has little effect (more like reference), though I think it might also populate the title bar on the browser (shows sunnyserver as gleaned from the gateway setting).   

Thank you so much SomeClown.