Georg,

There is a lot of confusion around this in some people's minds, and it is primarily due to some overloaded technical terms that people understand differently. For ANY Jazz application, there needs to be a JTS connection, an app server, and a data storage medium. Most of the time we refer to this data store as the "database", but it should be thought of as a logical data store. So for any Jazz application you have something like this:

App server <--> Application <--> Data Store

Now the physical representation of that data store can vary from vendor to vendor, but keep in mind that each application instance will have it's own unique data store. So if I have two instances of the RQM application running, then I need a different data store for each instance.

In SQL server or DB2 we refer to each data store as "logical databases" that are hosted on a single instance of a database software/hardware which is collectively called the "database server". In Oracle, you would use a single Oracle instance, and use different userid/tablespaces to host each data store needed.

Now two of these logical datastores will not kill your performance, unless you have a horribly undersized machine hosting your database software implementation. We often see a single database machine, with a single instance of he database software, supporting multiple logical Jazz data stores, with no adverse impact on performance. Often the database will host the data store for the JTS (and RRC), RTC, RQM, and the data warehouse.

So to answer your questions, YES it is possible to have multiple Jazz applications using the same database "instance" (meaning same hardware and database software), they just need to have their own data stores (either tablespaces or logical databases) within that instance. The second part of the question asked if this would work, and the answer to that is YES it does work. You just need to have two different Public URI's designated for the multiple Jazz instances (in this case the two different RQM's need to have different Public URI's). If you associate them to the same JTS, you can even report across them.