Data Connection Issues when Promoting Data Modules between environments

[Alex M]

Hi

I have encountered an issue when attempting to promote data modules from our development environment, via our user testing environment to our production environment.
We have setup Data connections with the same name in each environment but the data schemas are named differently in each environment (DEV / UAT / PROD) and this causes an error when promoting the data module as it is unable to find the named Schema.

Unfortunately with the way sever is setup 2 of the 3 Schemas are on the same server so we cannot rename them to a generic schema name which would work across all 3 environments.

After browsing the forum and finding a very useful post I have been able to get around this issue by manually editing the XML extract's from Cognos and renaming the Schema.

However if the data module refers to uploaded data then Cognos encrypts the contents of the extract file which stops me form being able to amend the XML. This manual editing process also slows down deployments between environments and it feels like something that should be doable from within Cognos itself.

I was wondering if anyone else had encountered such an issue and knew of solution to this problem or if there was any way to re-point data modules between environments or add aliases / parameters for the database/schema names?

This issue is currently occurring on Cognos 11.1.7
Thanks in advance
Alex

[bus_pass_man]

You can get a module to use a differently-named schema using the relink functionality.  If the metadata is different (for example, if the tables are upper case in one schema and lower case in another) you are in a pickle.


1.Open the data module.
2.Press the sources button, which is on the left.
3.Select the schema you want to relink and choose relink.
4.Navigate to choose the schema and click OK.
You can do the same thing for uploaded files.


I'm not sure what you mean by editing the xml but it seems like something weird, possibly not supported, and, if I correctly understand what the problem is, not necessary.

[MFGF]

I'm not sure what you mean by editing the xml but it seems like something weird, possibly not supported, and, if I correctly understand what the problem is, not necessary.

I'm guessing this is referring to exporting the metadata from a data module. It's definitely not something that is supported - it may be useful for debug purposes but I wouldn't recommend doing it then hacking the JSON - that has danger written all over it.

https://www.cognoise.com/index.php/topic,37418.0.html

Cheers!

MF.

[Alex M]

Thanks a lot for the advice, I cant believe I didn't see that option when I have looked before.

It sounds like exactly what I was looking for