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

Automate Data Source Connection properties change

Started by EarthDog, 14 Nov 2014 07:21:35 AM

Previous topic - Next topic

EarthDog

So in regular intervals i just mirror my prod environment to my dev environment.

Every time after i import all content from zip i do the following:

- Disable ALL schedules on dev machine.
- Change data sources to point to my DEV DataWarehouse server.


How can  i automate this changes in order to be able to run reports against dev DB?

bdbits

Use the option to select content instead of doing the entire content store when setting up the export. There are options for whether you want to include schedules, data connections, etc.

If you insist on taking the entire content store, I think you will be looking at using the SDK to create a custom app to make those modifications.

EarthDog

Quote from: bdbits on 14 Nov 2014 02:20:07 PM
Use the option to select content instead of doing the entire content store when setting up the export. There are options for whether you want to include schedules, data connections, etc.

If you insist on taking the entire content store, I think you will be looking at using the SDK to create a custom app to make those modifications.

if i select specific content then when i restore i should be using the same object ids in order to overwrite old objects?

I mean i will not have an empty content db....

Or i could have exported thebdatasources i am interested fromdev server, and import them after importing all content...

bdbits

When we copy content between environments we generally do not include data sources and everything seems to work out ok. (We have identically-named data sources set up for each platform.) I do not believe we include schedules either, but I would have to ask the team if anybody ever does.

I know some stuff is linked by name, others by object IDs. I think object IDs are GUIDs and therefore unlikely to collide. At any rate, Cognos seems to sort it out somehow or another on import.