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

 

framework connect to different BI server ,how to config?pls help,thanks

Started by ycbao, 13 May 2009 10:54:02 AM

Previous topic - Next topic

ycbao

hi all,
I install framework on pc1, BI server1 on pc2, BI server2 on PC3,(PC2 and PC3 one is test env,other is real envirement), when start framework on pc1, it only connect to one server,how can i config framework on pc1? 
thanks!

kolonell

The best (read proper) way to solve this is to install another instance of FM in a different folder. In short only use one instance of FM for one environment. The reason FM doesn't work on your second environment is 'encryption'. Since every Environment is unique it will generate unique keys and certificates.
The other way would be to export the configuration (decrypt) every time you would like to switch environments and delete the crypto informations in the configuration folder.

As you can see it just better to install a second instance of FM.

blom0344

Another option is to have just the one FM for test and create exports of packages from the test to the 2nd environment. This way you can be sure about synchronizing the package versions between the environments. We work this way with our development and test environments and we believe it is the most efficient way to work..

kolonell

oh yes,forget my suggestions .. blom's options is _the_ one to use in dev/prod environment .. That should teach me for not reading the initial question properly  ;)

blom0344

I use the setup that kolonell describes on my laptop. I have a local Cognos instance running on WinXP with it's own FM and a second FM to work with the development server when I am working online

ycbao

thanks to kolonell and bolm,
but how to create exports of packages from the test to the 2nd environment?
from fm or from cognos administrator?

blom0344

export and import of packages is handled through cognos connection (content administration) You cannot use FM in this respect without the actions that kolonell described. You basically:

1. Create an export job
2. Assign the package you want to export with proper settings
3. Export
4. Copy the .zip file to the other server ..\deployment folder
5. Create import job
6. Select .zip to be imported
7. run import