Multiple Jazz Team Servers on one Physical Server - RTC 2.0

jbclark wrote:

I would like to do the following:

1. Split the JTS into two physical servers - one AppServer, one DB
Server.

2. Have a production instance of the JTS (such as
https://host1:9443/jazz) that is associated with DB1.

3. Have a play area instance of the JTS (such as
https://host1:9444/jazz) that is associated with DB2.

Is this possible? Eventually, the play area DB2 will be deleted and
the URL will no longer be used. Only production will remain.

Yes, this is possible. In RTC 2.0, you can even use the same port with
a different context root if you prefer, something like:

https://host1:9443/jazz
https://host1:9443/jazz-play

Thanks,
Craig Chaney
Jazz Server team

Great. Now the trick is, how do I do this? I only see one teamserver.properties file for each database in the installation folder. This implies to me that anyone connecting to the Jazz Team Server gets directed to the same database instance. How can I use different ports or context roots to direct me to a different database instance if I only have one entry in teamserver.properties?

Also - any idea if it is also possible to do the same thing with RRC and have RTC and RRC share the same physical app server and DB server?

Thanks,

jbclark wrote:

I would like to do the following:

1. Split the JTS into two physical servers - one AppServer, one DB
Server.

2. Have a production instance of the JTS (such as
https://host1:9443/jazz) that is associated with DB1.

3. Have a play area instance of the JTS (such as
https://host1:9444/jazz) that is associated with DB2.

Is this possible? Eventually, the play area DB2 will be deleted and
the URL will no longer be used. Only production will remain.

Yes, this is possible. In RTC 2.0, you can even use the same port with
a different context root if you prefer, something like:

https://host1:9443/jazz
https://host1:9443/jazz-play

Thanks,
Craig Chaney
Jazz Server team

I wanted to post the answer to this since Craig answered my question off line:

Yes, this can be done in RTC 2.0. You need to duplicate the conf/jazz folder (which corresponds to the "/jazz" in the repository URL. So, two connections conf/jazz1 and conf/jazz2 can point to separate DB instances because each has its own teamserver.properties file. Note that there are other instance-specific modifications that need to be made. Details can be found at:

https://jazz.net/wiki/bin/view/Main/InstallingMultipleJazzWARs

Great. Now the trick is, how do I do this? I only see one teamserver.properties file for each database in the installation folder. This implies to me that anyone connecting to the Jazz Team Server gets directed to the same database instance. How can I use different ports or context roots to direct me to a different database instance if I only have one entry in teamserver.properties?

Also - any idea if it is also possible to do the same thing with RRC and have RTC and RRC share the same physical app server and DB server?

Thanks,

jbclark wrote:

I would like to do the following:

1. Split the JTS into two physical servers - one AppServer, one DB
Server.

2. Have a production instance of the JTS (such as
https://host1:9443/jazz) that is associated with DB1.

3. Have a play area instance of the JTS (such as
https://host1:9444/jazz) that is associated with DB2.

Is this possible? Eventually, the play area DB2 will be deleted and
the URL will no longer be used. Only production will remain.

Yes, this is possible. In RTC 2.0, you can even use the same port with
a different context root if you prefer, something like:

https://host1:9443/jazz
https://host1:9443/jazz-play

Thanks,
Craig Chaney
Jazz Server team