hi
just wondering how a local install of framework manager works. is there any instruction as to set this up on a local machine and work with the current cognos environment.install locally it still requires username/password and wondering how this works without accessing the current cognos environment
regards
bunker
FM has its own configuration tool. We basically only change the Gateway and Dispatcher URI to match the proper Cognos instance. With single signon enabled on the server this is all it takes
Hi
What if we do not have single signon. Should i replicate all the cognos configuration settings locally on the framework install to match what the server settings are
regards
bunker
hI
using these settings worked and the user was able to log onto the system. One issue they are having now when they open framework manager log onto the system and create a new package , create a new datasource is greyed out.
bunker
The Data Source gets created in the Content Store. Does your FM have connection to the Content Store?
Hi
I have datasource connected and created in the content store through the admin section. The errror i am not receiving from the local install of framework manager is RQP-DEF-0120 Database connection is dropped
.
If i log onto the server and use this instance of FW manager it works fine but on the local machine i am getting this error
regards
bunker
You probably need the Content Manager installed on the local machine and configure that to connect to the Content Store.
nfldbunker,
Which database are you working with? What security did you set up? Once you create a datasource in Cognos administration it should be available for a local FM instance..
hi
i did not create the database in sql but was created by another user. that is why i am wondering if it could be some sort of security on the database. i created the datasource in cognos but when i try and access in framework manager locally i get the error but if the user who created the database tries in a local install of framework manager it works fine
bunker
That seems likely..
You need to check how the datasource is setup. We typically use a single login that is reused for every database. Every datasource connection then has a sign-on that stores the specific account with the proper password. This enables acces to the database by SQL server authentication. Without the sign-on autentication may be performed through windows authentication. It is then quite well possible that this acces is denied.
To summarize, this is more a database/DBa issue then a Cognos one..