Create a new user with the user name FABRIC_SYSTEM_USER and the role Communications Catalog Administrator using the Security Console. If you have already created this as a part of the Launch setup, no additional setup is required.

Register Destination in Launch for publishing to PDC/BRM instance. Usually, you would have many PDC/BRM instances such as (Development, SIT, UAT and Production). Each instance of BRM instance is a destination that needs to be setup for Launch to publish to the correct PDC instance.

Configure destinations in Launch to appropriate life cycle status for which you would like to publish to external application. For example, you can configure a destination for test instance to the Ready to Publish life cycle status and configure one for production instance to the Active status.

Here’s the list of steps to create a Siebel destination:

1. Navigate to the Launch user interface > Administration > Lifecycle Status.

2. Select the new lifecycle configuration version in the PENDING state.

3. Choose the Edit option for the In design state and click Add Destination.

4. Provide the Name, Type, and Publish Sequence. Click Add.

   Note:

   Destination Name and Type should match the spoke system configuration in the CX Industries Framework.
5. Select the PDC destination name in the Destinations field and save it.
6. Choose the Activate option for the PENDING lifecycle configuration version.
7. Verify that the new lifecycle configuration version changed to the ACTIVE state.

For more information on how to configure the Destination in Launch, see REST API Reference for Launch Cloud Service and "Publish Catalog Entities" in Launch Cloud Service Implementation Guide.

Configure the Entity Profile to ensure that PDC/BRM supported product modeling is followed by Launch using the Entity Profile tile in Administration space.

No two applications are the same when it comes to modeling capabilities and so is the case between PDC/BRM and Launch. Though the result might be the same, the constructs might be different between the applications, and while integrating the applications, you need to factor in any restrictions of the target(spoke) application to ensure an error-free publishing of catalog definitions. Some of the common patterns between PDC and Launch can be classified as:

• Both the applications have the same construct capabilities and restrictions for an entity at par - for example, Balance Element, Product Offering, Service Specification entities, and so on.

• Both the applications have minimal common capabilities and/or additional capabilities or restrictions in one and not in the other - for example, PDC/BRM and Launch can have commitment terms, but Launch has the provision to configure multiple commitment terms to an offer, while only one commitment term is supported in PDC/BRM package.

Configure your external application in the Industry Framework for each instance. For more information, refer to the topic Integrate External Applications to add a Spoke End Point in the article Implement CX Industries Framework, on My Oracle Support, Doc ID 2720527.1.

Create client credentials and security requirements for PDC/BRM. See PDC/BRM documentation for information about creating client credentials and security requirements for PDC/RSM deployment.

Ensure that the services, events and service-event maps, general ledger IDs (GLID), tax codes, and balance elements required for charge or discount offers are set appropriately.

Before setting up integration, complete the following conditional tasks in PDC/BRM and Launch.

1. GLID name on Launch and BRM system should be same.

   1. In Launch → Setup and Maintenance, go to standard lookup ORA_ATC_GLID and set the GLID. Example: Create 101 GLID in launch.

   2. In PDC, use pin_glid application to create the general ledger ID. Create 101 GLID in PDC.

2. Tax code name on Launch and BRM system should be same.

   1. a. In Launch, use the REST API operation to create https:///<HOST>/crmRestApi/atcProductCatalog/11.13.18.05/productCatalogReferenceManagement/v1/taxServiceProvider. Example: Tax001 should be setup as taxCode in taxSupplier in Launch.

   2. In PDC, set up the same set of tax codes as configured in Launch.

3. Balance element name, code, numeric code on Launch needs to be same as PDC.

   1. In Launch, use the REST API to create the Balance element https:///<HOST>/crmRestApi/atcProductCatalog/11.13.18.05/productCatalogReferenceManagement/v1/balanceElement.Example: Name: US Dollar, code - USD, numeric code – 840 and so on.

   2. In PDC, configure the Balance Element (Name, Code, Numeric code), along with other attributes that should match with attributes in Launch.

4. Usage specification name and metering rule name in Launch needs to be same as the configured Usage event and RUM name on PDC side.

   1. In Launch, use the REST API to create the usage specification https://<HOST>/crmRestApu/atcProductCatalog/11.13.18.05/tmf-api/usageManagement/v2/usageSpecification. The fields name, meteringRule.name should match with PDC. Example: EventDelayedTelcoGSMTelephony, meteringRule.name – Duration

   2. In PDC, configure the serviceEventMap with the same event name and RUM.

5. The Service specification code in service specification in Launch and Service Event Map Name on BRM side should be same.

   1. Launch Service Specification service code needs to be configured. Example: The service code /service/telco/gsm/telephony needs to be same on both systems.

   2. In PDC, configure the ServiceEventMap.