Configuring Insight/Cognos Data Manager with 2 JTS Repositories
Accepted answer
Hi Corey,
To accomplish this, our team updated the XDC files we downloaded from the first repository to add a second ResourceGroup for the second repository, linking to the ResourceGroup for the first repository.
Make sure you fill in the URL, user name, and password correctly and the other big gotcha is setting the GUID accurately. This requires you to manually update the XDC files in a text editor to ensure that the GUID of the second repository is set correctly to match the UUID of your repository -- you can get this from the second set of XDC files you downloaded. It should look something like _xAnYQQ_PEd6yro8l0oSGHAJFS (it will have a JFS, BUILD, WORKITEM, etc extension for each XDC file type).
Once you have a set of combined XDC files, when you run the ETL it will loop through each resource group and run them in sequence.
One other answer
my understanding is that steps 1 to 3 are about the first full load, and in that case you replace your existing connection with the new JTS to do a full load only from that instance.
I think you would need a new Cognos data source to use for the delta load described in step 4, so that you can still use the original one to point to the first JTS.
I'm not sure about what would be the most efficient way to duplicate the jobs and replace the data sources, as the article doesn't seem to fully cover this aspect.
Best Regards,
Francesco Chiossi