Information On Billing Care Installation In Production Mode
Last updated on JULY 31, 2017
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
Question 1.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?
Question 2. 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 we have following questions.
- Is it mandatory to load billing care policies to LDAP, can we load these policies to OPSS schema as at the time of installation of OES admin server, we have installed the OPSS schema?
- If we create additional policies in OES admin, these are going to OPSS schema, so we believe that we can use schema as policy store instead of LDAP for billing care?
- Need details on how to migrate billing care provided system-jazn-data.xml to OPSS schema?
Question 3. 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).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms