Local GR nodes plus shared GR (recommended)

Local GR nodes for each developer, combined with a shared, centralized GR node offers high performance and eliminates many of the challenges that can affect other development architectures. Most development work can be done on the local nodes, and then uploaded, via an aaPKG file, to the shared GR node for integration and/or testing. The shared GR node can be an on-premises system, or you can use Integration Studio, a cloud service hosted by AVEVA. With a local GR for each developer, most of the challenges that apply to other multi-user development environments are avoided.

Click here for more information about AVEVA Integration Studio.

Many concurrent users are supported (no upper limit has been identified).

This approach has the following advantages and disadvantages:

Advantages:

• High performance: with most development work done on local nodes, there are no slow downs associated with shared access and network traffic.

• Remote access: developers can work from different sites and geographic locations.

• IT infrastructure: with a shared GR and IDE, there are fewer potential bottlenecks between the two Application Server components.

• Multiple projects and versions: the centralized IDE allows better project/version management.

Disadvantages:

• Transferring work between the remote GR nodes and the shared GR node requires manually exporting and importing aaPKG files.