Undeploying Composite Cartridges with Shared Component Cartridges
By default, when you undeploy a composite cartridge with some component cartridges that are being used by other solutions in the run-time environment, the shared component cartridges remain deployed, and the composite cartridge and component cartridges that are not shared by other solutions are undeployed.
Note:
When multiple versions of a composite cartridge are running in a Production environment, you can undeploy an earlier version without impacting the currently-running versions.
Forcing the Undeployment of Shared Component Cartridges
To force the undeployment of shared component cartridges within a composite cartridge, use the undeploy_shared_cartridge variable in the Composite Cartridge editor Cartridge Management Variable tab. This variable forces the undeployment of the entire composite cartridge even if there are shared component cartridges contained within it.
For example, consider a scenario where two versions of a composite cartridge (1.0.0 and 2.0.0) are deployed in the run-time environment and share some component cartridges. If you set the undeploy_shared_cartridge variable of composite cartridge 1.0.0 to true then all of the component cartridges, including shared component cartridges, are undeployed. However, this forces composite cartridge version 2.0.0 to become invalid because its dependent cartridges no longer exist in the system.
Note:
Forcing the undeployment of shared component cartridges within a composite cartridge could render some solutions non-functional because their dependent component cartridges no longer exist in the run-time environment. This option should only be used in troubleshooting or run-time environment clean-up situations.
Undeploying Component Cartridges from a Composite Cartridge During Development
During the development of a composite cartridge, you may need to undeploy a component cartridge used by the solution. By default, component cartridges that are used by solutions in the run-time environment cannot be undeployed.
To force the undeployment of one or more component cartridges used by a solution, you can set the allow_undeploy_component_cartridge_in_solution parameter in the oms-config.xml file to true.
Note:
Forcing the undeployment of component cartridges that are used in a composite cartridge could render the solution non-functional. This option should only be used in troubleshooting or run-time environment clean-up situations.