About Composite Cartridge Projects

You use composite cartridge projects to extend the functionality of existing component cartridges, without having to unseal the component cartridge and modify the contents directly.

For example, consider a typical central order management solution which consists of the following component cartridges:

Base Cartridge v1.0
Billing Cartridge v1.0
Provisioning Cartridge v1.0
Fulfillment Pattern Cartridge v1.0
Product Mapping Cartridge v1.0
Composite Cartridge v.1.0

If you wanted to extend this solution by adding a new Shipping fulfillment function, the new solution would consist of the following cartridges:

(New) Shipping Cartridge v1.0:

A new Shipping cartridge is created to host the new fulfillment function, decomposition rules, processes and tasks, and any additional task data required by the new fulfillment function.
(Sealed) Base Cartridge v1.0:

The sealed base cartridge that serves as the foundation for the original solution remains sealed and unchanged. It contains such entities as the order, order item specification, order recognition rules, and required tasks for the order. It is deployed as part of the solution.
(Unchanged) Billing Cartridge v1.0:

The billing cartridge is unchanged but is deployed as part of the solution.
(Unchanged) Provisioning Cartridge v1.0

The provisioning cartridge is unchanged but is deployed as part of the solution.
(Updated) Fulfillment Pattern Cartridge v2.0:

The v1.0 fulfillment pattern cartridge is updated to include the new shipping dependencies along with the billing and provisioning dependencies. The cartridge is versioned and is deployed as part of the solution. This cartridge would generally not be sealed, as orchestration fulfillment patterns are not usually reusable components of the solution.
(Unchanged) Product Mapping Cartridge v1.0

The product mapping cartridge is unchanged but is deployed as part of the solution.
(Updated) Composite Cartridge v2.0:

A new composite cartridge is created to reference all other cartridges in the solution; specifically, Shipping Cartridge v1.0, Base Cartridge v1.0, Billing Cartridge v1.0, Provisioning Cartridge v1.0, and Fulfillment Pattern Cartridge v2.0.

In this way, you can extend any cartridge that has been deployed to an OSM run-time environment, including Order-To-Activate cartridges in the Oracle Communications Order to Cash Integration Pack for OSM.

See OSM Developer's Guide for cartridge development guidelines and solution-versioning best practices.