Configure a multi-user development environment

The ability to have multiple users working concurrently on a single galaxy is often required, particularly for large and/or complex projects that often require multiple developers to work together. If multiple developers will be working with the IDE to build objects and applications, you can structure your environment to enhance team coordination and avoid disconnects and conflicts. Coordinating this effort can be difficult. Even before starting, there are IT infrastructure requirements and limitations that must be considered.

A multi-user environment can be set up with multiple concurrent IDE connections from either standalone computers within the galaxy or RDS client sessions. Advantages of a multi-user development system include:

• Multiple engineers can work simultaneously.

• Changes can always be rolled back.

• The Production Galaxy is isolated from the development system, and development work done on remote workstations does not interfere with or disrupt work being done on the Production Galaxy.

• Individual updates from remote workstations can be released to the Production Galaxy, without requiring check-in/check-out or long wait times.

• The IDE remains responsive, with no interruptions from security updates.

This section describes different ways to configure your development system, and also describes the recommended architecture that will support the most concurrent users. If you select one of the alternative architectures, keep in mind some basic considerations:

• SQL Server Express vs SQL Server: a full version of SQL Server is tolerant of more concurrent users than SQL Server Express (up to three for SQL Express vs. up to five for a full SQL Server version).

• Multi-galaxy pairing must be enabled whenever the development galaxy spans more than one GR.

• In a shared-GR development environment, the IDE may disconnect periodically from the galaxy as the number of users increases. You can avoid this if you use the recommended multi-user development architecture.

• Running InTouch OMI Preview may occasionally crash the the ASB services in shared GR development environments. Again, you can avoid this if you use the recommended multi-user development architecture.