Hi Georg,

unfortunately RQM 3.0 never got released. There are also architectural changes that were introduced in RTC 3 that makes it hard to suggest what to do in your situation. RTC 3 introduced the split of JTS and RTC. To minimize administrative tasks and make life easier you would typically want to use the same JTS for RTC and RQM.

See https://jazz.net/search_results.jsp?q=upgrade#page=0&type=type%3DDocument-LibraryItem&q=upgrade for all the upgrade material that can help you understanding the options.

In a nutshell it boils down to:

Option A: Going for an integrated CLM with common JTS
1. You can use RQM 2.x together with RTC 3.0. In this scenario you would upgrade RTC/JTS and the RQM later.
2. You can upgrade the JTS of RTC 3.0 to 3.0.1, leave RTC at 3.0 and add RQM 3.0.1.x to it. This is only possible if you have installed the JTS on a separate server.
3. You can upgrade JTS and RTC to 3.0.1.x and add RQM 3.0.x

Option B: Separate JTS
1. You install RQM 3.x independent from RTC with its own JTS and setup the friends/trusts. The consequence of this is a limitation in reporting across tools especially with RRDI. RRDI only supports common reports across one JTS and the registered applications. You would need Inight to get reporting across JTS's.