Deployment considerations

Objects are always deployed to the active engine:

• If the primary engine is the currently-active engine of a redundant pair, objects are deployed to the primary engine.

• If the backup engine is the currently-active engine, the objects are deployed to the backup engine.

When an active engine becomes the standby, the engine sets all objects off scan, shuts down all features that make up the object and stops executing all deployed objects. All objects are unregistered on the previously active engine.

When a standby engine becomes active, the engine calls startup on all features that make up the objects. The call-up includes a method that shows the objects are starting up as part of a failover. The newly active engine calls SetScanState on all features and begins executing all objects that are on scan.

Best Practice

To deploy objects in a Load Shared configuration

1. Deploy the platforms individually rather than in a cascade.

2. Cascade deploy the primary engines.

3. Finally, cascade deploy the backup engines. Always deploy the primary engine first.