Skip Headers
Oracle® Communications Design Studio Modeling OSM Processes
Release 7.2.4
Go to Design Studio Help Home
Go to Table of Contents
Go to Feedback page

Go to previous page
Go to next page
Mobi · ePub

Defining Build-and-Deploy Modes for Automation Plug-ins

Note:

The information in this topic applies as of release OSM 7.0.3. Design Studio uses only the Legacy build-and-deploy mode for earlier releases.

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

Note:

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

Related Topics

About Build-and-Deploy Modes for Automation Plug-ins

Setting Automation Plug-in Build-and-Deploy Modes for Individual Cartridges

Setting Automation Plug-in Build-and-Deploy Modes for All Cartridges