Deploying objects in a large or very large system

The ArchestrA system deploys objects in a "cascade" manner: that is, objects are deployed in hierarchical order. However, in the context of large- or very large systems, a cascade deployment, though reliable, may consume a large amount of system resources, or time, to complete the deploy operation.

Note: For details about different deployment scenarios, see the IDE Online Help (search "cascade" to filter results).

In this context, a large system is defined as a system in a 20- to 50,000 I/O point range, and a very large system is one that has at least 50,000 I/O points. These values are approximate and must be considered along with other performance variables listed in the previous tables.

When working in a large or very large systems, it is often more efficient to deploy object groups in a specific order, using the multi-select function in combination with, or instead of cascade deployment. Deploying objects in this scenario can save overall deployment time.

To deploy in a large system

For a large system, perform Cascade deployment from the Platform level. Make sure that Platforms hosting Primary Engines are deployed first, then Platforms hosting Backup Engines. This strategy avoids issues in load-balancing environments.

To deploy in a very large system

When working in a very large system (high I/O, high numbers of Areas), use the multi-select (Ctrl + click) to deploy in the following sequence:

1. Galaxy Repository Platform

2. All other Platforms

3. Primary AppEngines

4. Backup AppEngines

5. Primary Engine for I/O (include redundant partner): Skip already deployed objects.