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

Unable to access (manual URL) the second namespace

Started by usecognos, 13 Feb 2008 04:43:08 PM

Previous topic - Next topic

usecognos

Hi:
I'm new to cognos 8 admin, and not sure if what I was trying to do was possible.

We've got an existing namespace used to authenticate users.  We've then added a new namespace that will replace the existing one eventually.  They both work since we can select either one in the logon screen.

Then, to make the new namespace transparent to our current users (for now while we define groups/roles for it), we used Cognos Configuration's Environment - Gateway Namespace, and entered the existing namespace ID.   This then showed only the existing namespace in the logon screen.

I tried to logon to the system using the following url and specifying the new namespace ID but it gave the "Authentication failed.." error.

http://servername/cognos8/cgi-bin/cognos.cgi?b_action=xts.run&CAMUsername=abcde&CAMPassword=pwd123&h_CAM_action=logonAs&CAMNamespace=NEWNS&m=portal/cc.xts&m_tab=w

Is it even possible to do this?  Do we have to create a second gateway?

Thank you for your help.

ducthcogtechie

Give out links to the namespace:

http://servername/cognos8/cgi-bin/cognos.cgi?CAMNamespace=Namespace1
http://servername/cognos8/cgi-bin/cognos.cgi?CAMNamespace=Namespace2

usecognos

Thank you very much for your response. 

My only concern is that some users will not use the new URL if they already have their favorite link or shortcut to the http://servername/cognos8/cgi-bin/cognos.cgi... and they'll notice the 2 namespaces dropdown field.

Sorry but just to make sure that I understand.. By specifying a Gateway Namespace in CConfig env, this automatically disables the other namespace, right?

Thanks for your patience and please let me know.


ducthcogtechie

yes, but with your way you would need to install an additional gateway tier on the server, so each can specify it's own namespace. Then you would probably work with 2 aliases to get them devided.
Then you send out an email to the users to go to a new gateway adres.
I don't see the benefit here. I would go for the easy way and use the url's. If people insist on using a dropdown, they are free to do so. If you permanently want to get rid of the dropdown, then yes, use 2 gateways.

choices, choices, choices.....  ;)