Information on Billing Care Installation in Production Mode
(Doc ID 2286085.1)
Last updated on MARCH 12, 2021
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
This article describes the below queries about integrating Billing care with existing LDAP for authentication and authorization of billing care resources.
For installing OOB Billing Care in production mode, so far the user has done the following:
a) Installed Oracle entitlement admin server
b) Created OES client domain for billing care
And the user has facing issues while loading xml provided in Billing Care SDK (system-jazn-data.xml), it is mentioned in Billing Care documentation to first change the file jps-config.xml and after that use migrateSecurityStore to move this xml to LDAP, here are some questions.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Questions and Answers|
|How to load billing care policy stores to existing LDAP and integrate billing care to authenticate users through LDAP and get billing care roles/permissions?|
|Imported the OOB xml to OES as mentioned on development environment and done changes to the policies and permissions.Need steps for exporting these new permissions (complete xml) and import it to higher environment (End to End testing environment).|