Enterprise Deployment of RTC
Are there currently plans to support the Enterprise Deployment of RTC across large organizations? What are the releases and timelines if so?
This includes the following:
1) License tracking
2) Scalable scenarios for Project Repository creation and maintenance
3) Scalable scenarios for deploying RTC, RDM, and RQM
This includes the following:
1) License tracking
2) Scalable scenarios for Project Repository creation and maintenance
3) Scalable scenarios for deploying RTC, RDM, and RQM
3 answers
The 1.0.1 release will include flexibility for license tracking. In
1.0.1 it will be possible to use a single floating license server to
control CALs for multiple Jazz servers and it will also provide reports
of license usage.
About the 'scalable scenarios', can you provide some more details about
what you expect?
Matt Lavin
Jazz Server Team
shelbyph wrote:
1.0.1 it will be possible to use a single floating license server to
control CALs for multiple Jazz servers and it will also provide reports
of license usage.
About the 'scalable scenarios', can you provide some more details about
what you expect?
Matt Lavin
Jazz Server Team
shelbyph wrote:
Are there currently plans to support the Enterprise Deployment of RTC
across large organizations? What are the releases and timelines if
so?
This includes the following:
1) License tracking
2) Scalable scenarios for Project Repository creation and maintenance
3) Scalable scenarios for deploying RTC, RDM, and RQM
Scalabe scenarios include the following:
1)Create or modify user groups on the active directory domain. Ideally, we should only use Active directory or LDAP for authentication.
2)Supporting multiple repositories using one RTC instance. For enterprise deployment, it is not a good idea to install multiple RTC instances on one server and each repo uses a separate virtual IP.
3)Support for RTC integration with other tools that are built on top of Jazz platform. It is hard to convince people on and off Jazz to use different tools.
1)Create or modify user groups on the active directory domain. Ideally, we should only use Active directory or LDAP for authentication.
2)Supporting multiple repositories using one RTC instance. For enterprise deployment, it is not a good idea to install multiple RTC instances on one server and each repo uses a separate virtual IP.
3)Support for RTC integration with other tools that are built on top of Jazz platform. It is hard to convince people on and off Jazz to use different tools.
Thanks for the details.
1. I think that, in general, RTC will try to avoid duplicating function
that is available in other tools. Creating general purpose
creation/modification support for LDAP repositories is pretty hard, and
there are other tools already designed to help with LDAP repository
management. You should be able to configure your RTC server to use
Active Directory or LDAP if you want, even with 1.0.
2. Supporting larger installations of RTC is definitely on the radar for
future development. We understand that the 1.0 is a bit limiting for
extremely large teams, and we want to make it easier in the future.
3. Good tool integration was one of the motivators and design principals
when creating Jazz. RTC is the first step, but other tools will
definitely become better integrated as the teams have time to understand
and leverage what Jazz has to offer.
Matt Lavin
Jazz Server Team
shelbyph wrote:
1. I think that, in general, RTC will try to avoid duplicating function
that is available in other tools. Creating general purpose
creation/modification support for LDAP repositories is pretty hard, and
there are other tools already designed to help with LDAP repository
management. You should be able to configure your RTC server to use
Active Directory or LDAP if you want, even with 1.0.
2. Supporting larger installations of RTC is definitely on the radar for
future development. We understand that the 1.0 is a bit limiting for
extremely large teams, and we want to make it easier in the future.
3. Good tool integration was one of the motivators and design principals
when creating Jazz. RTC is the first step, but other tools will
definitely become better integrated as the teams have time to understand
and leverage what Jazz has to offer.
Matt Lavin
Jazz Server Team
shelbyph wrote:
Scalabe scenarios include the following:
1)Create or modify user groups on the active directory domain.
Ideally, we should only use Active directory or LDAP for
authentication.
2)Supporting multiple repositories using one RTC instance. For
enterprise deployment, it is not a good idea to install multiple RTC
instances on one server and each repo uses a separate virtual IP.
3)Support for RTC integration with other tools that are built on top
of Jazz platform. It is hard to convince people on and off Jazz to
use different tools.