Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

RQM CR: moving Reporting server

Hi
Customer wants to move RQM CR to a different server; the database remains the same just the reporting components need to be moved. Is this technically feasible and are there any gotchas to be aware of?
Thanks

0 votes



3 answers

Permanent link
Hi
Customer wants to move RQM CR to a different server; the database remains the same just the reporting components need to be moved. Is this technically feasible and are there any gotchas to be aware of?
Thanks

I've never tried moving an RRDI Report Server to another system, so this answer may not be totally complete.
1) Install RRDI on the new system. Do not create a new Content Store database
2) Use the Cognos Configuration Utility to connect the new RRDI to the existing Content Store database. Make sure the connection test succeeds. Do not start your old RRDI server after this, as you shouldn't have more then one Cognos server using the Content Store database.
3) In Cognos Administration, delete the data warehouse data source and create a new one. This may not be necessary, but its easy to do and can't hurt.
4) I'd verify that you can access the data warehouse by running Query Studio and verifying that you get the data model and can drag fields into the report and see data.
5) On the jazz/RQM server, modify the URL of the reporting server to point to the new server. This is what I'm not sure about. I'm not sure if jazz caches the URL any place else. Maybe you could delete all references to the report server first, then create a new reference.
6) If the OAuth key/secret get changed on the jazz side, make the corresponding changes in the jazzns_config.xml on the RRDI server. I would verify that they match in any case. Since the values in the file are encrypted, you'll have to replace the encrypted values with the values from the jazz server and set the "encrypted" attribute to false.
7) Restart your RRDI server.
8) If any uses have bookmarked the Cognos URL, make sure they get the new URL.

That's all I can think of. It should be complete from the RRDI side, but I'm not positive about the jazz/RQM side.

Mike

0 votes


Permanent link
Thanks Mike,

Will this approach work for RQM CR v2.0.x (as well as RRDI .. as you describe) ?

0 votes


Permanent link
Thanks Mike,

Will this approach work for RQM CR v2.0.x (as well as RRDI .. as you describe) ?

hi,

It should work with RQM V2.0.x and RCPR 1.0. You can skip steps 5 and 6 as I don't believe it is integrated with Jazz like RRDI is. If RQM knows the URL of the report server, you'll have to update that.

I believe the ETLs used Cognos Data Manager, not the CLM data collection jobs. If they are loaded as Data Movement Tasks and scheduled through Cognos Connection, then they should continue to work as you've preserved the Content Store. Verify this though.

In any case, I would suggest this overall approach:
1) Shutdown your existing report server.
2) Follow the procedure to install the new server
3) Verify that the new server works: ETL, report execution, etc
4) If it works, then uninstall RCPR from your old server so it doesn't get accidentally started
5) If it doesn't, shutdown the new server and restart the old one so you'll be operational while figuring out what the problem is.

Mike

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Nov 28 '11, 10:28 p.m.

Question was seen: 11,251 times

Last updated: Nov 28 '11, 10:28 p.m.

Confirmation Cancel Confirm