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

How I can copy a bunch Analyst library + Contributor Application

Started by EP_explorer, 20 Apr 2010 04:16:45 AM

Previous topic - Next topic

EP_explorer

Cognos Planning 8.4

I want to receive a copy of a bunch Analyst Library + Contributor Application. I can copy an Analyst library (e.g. using Copy Wizard in Analyst). I also can copy an Contributor Application (e.g. Deployment export->Deployment import) but I can't join them in one bunch after it. When I try to choose the new Analyst library in CAC Synchronize I receive the message:
There is a problem with the synchronization of this application.
Check that the library name is correct....

Can anybody help with the way to copy of the bunch?

craig_karr

You can take a deployment and include the libraries as well in the deployment export to make sure that they are connected and will work together after the import

EP_explorer

It didn't help.

May be I should be more clear. It happens in the same server.

And after I tried to use the previous advice Cognos simply changed the previous library to the new imported library during import deployment. And when I tried to connect the previous library, Analyst said that I have already the library with the same Number (ID).

Thus I have 2 libraries with the same ID and I can connect only one of them in one period of time.

I want in the result have 2 Analyst Libraries and 2 Contributor Applications. 2 bunches:
1) 1st Analyst library and 1st Contributor application
2) 2nd Analyst library and 2nd Contributor application - which will be the same copy of the first ones. And I will change the 2nd Analyst library and conseqently 2nd Contributor application.

SomeClown

Don't think you can do that on the same server without recreating the Contributor app.

To have a copy of an Analyst library in the same environment, you need to do the Analyst library copy (like you mentioned).  This creates the mandatory new lib id (number) to keep the Analyst libraries unique.

Analyst libraries store the links between Contributor objects and Analyst objects.  These are not copied via the wizard.

Contributor apps contain a reference to the synchronizing Analyst library.  You can change to point to a new one, but then you will not have any of the references between objects and the next synchronize will likely wipe out all your copied data.

To have a "dev" version and a "prod" version in the same server is not easy.  Most find that keeping a change log between the two is the easiest option in the same environment.

If you are archiving last years, then just copy the old Analyst folder somewhere else, then replicate (copy) the supporting contributor database for the new app.  Link to existing and give it a new name.

EP_explorer