Defining 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.

When you deploy cartridges with automation plug-ins to your OSM run-time environment (automation plug-ins for automation tasks as well as for activation tasks), you can define a configuration to have Design Studio build and deploy automation plug-ins in a particular way. Prior to OSM 7.0.3, when you built and deployed a cartridge that included automation plug-ins, OSM ran each automation plug-in in that cartridge in its own separate EAR file; this method of building and deploying automation plug-ins is now referred to as the Legacy build-and-deploy mode. Legacy mode simply refers to the manner in which automation plug-ins were deployed and processed prior to OSM 7.0.3. As of release OSM 7.0.3, you can build and deploy a cartridge in Design Studio using the Optimized build-and-deploy mode, the default mode; this mode improves the performance of processing of automated or activation tasks and improves the performance of build and deployment of cartridges with such tasks.

Note:

The Legacy build-and-deploy mode is deprecated, but it is supported for backward compatibility in OSM server versions before OSM 7.3.

Note:

XML Catalog support is required to be enabled for all cartridges as of release OSM 7.0.3.