Define the deployment model

The last workflow task defines the deployment model that specifies where objects are deployed. In other words, the deployment model defines which nodes will host the various objects that make up the Galaxy.

Each computer in the System Platform network must have a WinPlatform object, AppEngine object, and Area object deployed to it. For example, KT101, LT 101 and MK101 are all areas in the following figure:

The Deployment View in the IDE shows the Galaxy organized by Platform (WinPlatform object). Each engine object assigned to the Platform is shown next. Area objects assigned to each engine are next in the hierarchy.

The objects deployed on particular platforms and engines define the objects' "load" on the platform. The load is based on the number of I/O points, the number of attributes, derivation depth, etc. More complex objects consume more resources. No more than two AppEngines should be assigned to a single logical processor. In a redundant system, these are typically the primary and backup AppEngines. See System sizing guidelines for more information.

Note: For object types and target deployment node recommendations (such as DIObjects), see Assess system size and performance.

After deployment, you can use the Object Viewer to check communications between nodes and determine if the system is running optimally. For example, a node may be executing more objects than it can easily handle, and it will be necessary to deploy one or more objects to another computer.

Note: For more information on deployment, see the Application Server User Guide.