About Build-and-Deploy Modes for Automation Plug-ins
Note:
The information in this topic applies between the OSM 7.0.3 and 7.2.4.x releases. Design Studio uses only the Legacy build-and-deploy mode for releases before OSM 7.0.3, and uses only the Optimized build-and-deploy mode starting in OSM 7.3.
Build-and-deploy modes for automation plug-ins affect how the plug-ins are processed at run time. See "Defining Build-and-Deploy Modes for Automation Plug-ins" for introductory information on build-and-deploy modes. A dispatch mode setting on the OSM server controls the automation plug-in dispatch mode of the OSM system, which is directly related to the build-and-deploy mode you configure in Design Studio. The build-and-deploy mode configured in Design Studio controls building and deploying the automation components required for Legacy mode or Optimized mode; it can also be configured to build and deploy the automation components required for both modes.
-
The Optimized mode enables the automation plug-ins to be deployed and executed more efficiently (automation plug-ins can run in a common EAR file).
-
The Legacy mode deploys and executes the automation plug-in in a manner consistent with previous OSM releases (each automation plug-in runs in its own EAR file).
-
The mode entitled Both (Allow server preference to decide) indicates the automation plug-in can run in either Optimized or Legacy mode (Design Studio builds the cartridge with the automation components required for either mode).
If you build and deploy the automation components required for both modes, OSM executes the automation plug-in at run time in the mode specified by the dispatch mode setting on the OSM server. See the discussion on automation plug-in dispatch modes in OSM Developer's Guide for information on how to define the dispatch mode setting on the OSM server.
The following table summarizes the effective mode OSM uses at run time based on how the automation plug-in build-and-deploy mode and the server dispatch mode are set as of OSM 7.0.3:
| Automation Plug-in Build-and-Deploy Mode (set in Design Studio) | OSM Server Dispatch Mode | Effective Mode Used at Run Time |
|---|---|---|
|
Optimized |
Legacy |
Optimized |
|
Optimized |
Internal |
Optimized |
|
Legacy |
Legacy |
Legacy |
|
Legacy |
Internal |
Legacy |
|
Both |
Legacy |
Legacy |
|
Both |
Internal |
Optimized |
You can set the automation plug-in build-and-deploy mode in two levels:
-
Global preference: Set the mode for all cartridges in the same workspace by setting a global preference. To specify a build-and-deploy mode for all cartridges in the same workspace, see "Setting Automation Plug-in Build-and-Deploy Modes for All Cartridges."
-
Cartridge-level preference: Set the mode for individual cartridges by setting a cartridge management variable. To specify a build-and-deploy mode for individual cartridges, see "Setting Automation Plug-in Build-and-Deploy Modes for Individual Cartridges."
Note:
The cartridge-level preference overrides the global preference.
Design Studio uses the following build-and-deploy modes when a cartridge is deployed:
-
If the Target Version field is to 7.3 or later, the Design Studio build-and-deploy mode is set to Optimized and cannot be changed.
-
If the Target Version field is set to an OSM release between OSM 7.0.3 and OSM 7.2.4; for example, set to 7.0.3, Design Studio uses the build-and-deploy mode that you set for the individual cartridge (the default mode is Optimized) or the mode you set as the global preference.
-
If the Target Version field is set to 7.0.1 or below, the Design Studio build-and-deploy mode is set to Legacy and cannot be changed.
Note:
Optimized mode is not available when using OSM server releases 7.0.2 or earlier. Legacy mode is not available when using OSM server releases 7.3 or later.