When you integrate Launch with third-party target systems, you need to respect the boundaries of the source and target systems. Entity profiles help you to create these boundaries between source and target systems.

Launch can consume catalogs from other applications as a part of its coexistence strategy. For example, Launch can consume and federate any third-party catalogs.

Entity profiles are constructs that incorporate a set of rules used by Launch to ensure the following:

• Migrate entities smoothly from runtime systems based on their features.
• Apply restrictions to protect the shape of the migration from modification in Launch.
• Publish changes or revisions made to the migrated entities in Launch back to and without breaking, the target runtime application.

A migrated resource must have a resource-specific entity profile associated with every instance of the resource, to respect the source ecosystem.

Oracle Digital Business Experience (DBE) is a business support system (BSS) stack that provides an end-to-end solution to help service providers manage experiences and revenue at every stage of the customer journey.

You can use DBE across any line of business to simplify deployment complexity and reduce cost. The solution also works to support evolving digital transformation goals as CSPs look to increase business agility through advanced technology. DBE contains an enterprise product catalog (Launch), configure-price-quote (CPQ), customer relationship management (CRM) powered by the Siebel CRM engine, central order management (OSM), and monetization capabilities (BRM). The integration of these best of breed solutions can help CSPs grow revenue, deliver personalized customer experiences, and remain operationally agile and efficient as they explore new market opportunities.

You can now have Launch as a central design time catalog for defining and distributing commercial definitions with Oracle's Siebel CRM and BRM applications.

Take advantage of the prebuilt integration between Launch and Siebel CRM to centrally manage product and services portfolio across your ecosystem. Launch is the primary source of data for catalog definitions.

Siebel customers can innovate faster by centrally managing their Product Portfolio for their entire eco-system, including Siebel CRM.

The prebuilt integration between the two applications allows migration of catalog definitions from Siebel to establish them as the authoritative source in Launch.

Take advantage of the prebuilt integration between Launch and Billing and Revenue Management, specifically the Pricing Design Center (PDC). Publish product offerings with charges and discounts in PDC and BRM to perform rating and billing.

Launch has OCI Object Store as the default Content Management System (CMS) to manage content. To enable Launch to interact with a different CMS and manage content, a contractual agreement is required between Launch and the CMS. To establish this contract, Launch provides a Swagger specification for the Third Party CMS. A concrete client implementation of this Swagger is necessary, which should be REST-based and can be deployed on any chosen platform.

This framework offers a robust solution for integrating Launch with external content management systems, enabling seamless content management across the entire Launch ecosystem.

Using this framework, you can:

• Connect Launch to your preferred CMS.
• Retrieve content dynamically from the external CMS.
• Enhance the Launch Cloud Service with rich, externally managed content.

For more information, see Launch Cloud Service Integration Guide.