Assign an engine to a ViewApp

Before deploying ViewApps, you need to assign each one to the ViewEngine (for access from the Application Manager) or WebViewEngine (for browser access) that it will run on. As you assign ViewApps, consider the I/O, memory, and CPU needs of each one. Assign your ViewApps to distribute these loads evenly across the platforms in the Galaxy environment at runtime.

The operating system determines how engines are assigned to individual CPU cores and attempts to load balance across CPU and other computing resources on the platform. If you need to change which platforms and engines VIewApps are assigned to in order to improve load balancing, undeploy the ViewApps and reassign them to different ViewEngines and WebViewEngines.

If you are using redundant AppEngines, you can control how objects are loaded at runtime.