Create a multi-user development system
- Last UpdatedDec 19, 2024
- 2 minute read
Distributed multi-user development solution
The following practices are highly recommended:
-
On the GR node that contains your production (functional) Galaxy, add a second Galaxy. We will call this second Galaxy the Development Galaxy. The Development Galaxy will act as a central storage location, and will be used to:
-
Maintain the current master templates, including top-level Object Wizards for all objects.
-
Distribute master templates and Object Wizards to each Local GR for development (via .aaPkg export).
-
Control master template updates from local developers (via .aaPkg import).
-
Maintain ownership relations between developers and master templates via OS User Based or OS Group Based security.
The figure below shows an example of template hierarchy levels, shown in Derivation view. Set access and ownership within the team/organization to each template level to maintain control and security of the project.

-
-
Install a temporary, local GR at each IDE development node. The local GR allows each developer to work independently, without interfering with or interference from other developers that may be checking in/out objects, security updates, and deployment actions.
The local GR can be used for both development and testing.
Note: The local GR should not require an additional platform count license because it is temporary, and it is not used for run time.
