2 Planning Your Billing Care Installation
Learn how to plan for your Oracle Communications Billing Care installation.
Topics in this document:
About Planning Your Billing Care Installation
When planning a Billing Care installation, consider how many physical servers are required to support the Oracle Enterprise Database, Oracle WebLogic Server domains, and Oracle Identity Management (IDM) components (optional) needed in your environment.
Consider the security and networking requirements necessary for securing Billing Care communications with your Oracle Communications Billing and Revenue Management (BRM) system in addition to software and hardware requirements.
See "Billing Care System Requirements" for information about required hardware and software.
About Test Installations and Production Installations
Install Billing Care either as a test or production installation depending on your required environment.
About Test Installations
Use test installations when setting up internal development or testing Billing Care instances. Test installation gives you the option to use Billing Care without Oracle Platform Security Services (OPSS) security. The deployed Billing Care application in your test WebLogic Server domain connects directly to your BRM system using native WebLogic Server user management.
Test installations include the following components:
-
WebLogic Server
-
WebLogic Server domain to host Billing Care with Billing Care security disabled
-
Deployed Billing Care application WAR
This guide includes information on installing test installations. It is not mandatory to perform the IDM preinstallation steps for test installations.
About Production Installations
Use production installations when setting up secure Billing Care instances using security. Production installations require user authentication and authorization for securing access to Billing Care. This guide provides general guidelines for installing and configuring IDM components. It does not contain detailed information on configuring IDM components. Consult the respective product documentation using the references provided in this guide for more information on configuring IDM components.
Production installations include the following components:
-
Enterprise Database
-
Database creation with Oracle Repository Creation Utility (RCU)
-
WebLogic Server
-
OPSS JRF-enabled WebLogic domain
-
(Optional) IDM components, including:
-
Oracle Access Management (OAM) for single sign-on (SSO) configuration
-
Oracle Identity Governance for user management
-
Oracle Unified Directory (OUD) for user directory management
-
Database Planning
Billing Care production installations require an Enterprise Database for storing OPSS schema. This database is in addition to your BRM server database. Database sizing requirements depend on the number of Billing Care users in your environment.
See "Installing and Configuring Oracle Enterprise Database" for information on setting up the required database for Billing Care.
Authentication and Authorization Planning
When planning a Billing Care installation, consider the requirements carefully. Each OPSS JRF-enabled domain hosts a deployed instance of Billing Care and connects to OPSS for authorization. Determine how many OPSS JRF-enabled domains are needed to support the Billing Care deployments required by your transaction volume.
For authentication, you can use Security Assertion Markup Language (SAML) for SSO or the IDM components and Oracle HTTP Server Webgate for user authentication, SSO, and user directory management.
If you are using SAML, see the SAML documentation for information on sizing and installation.
If you are using IDM components, see Oracle Fusion Middleware Installation Guide for Oracle Identity and Access Management for more information on sizing and installation.
About Installing a Secure System
In production environments, you must ensure that communication between components and access to the system servers are secure. The Billing Care installer prompts you to select security options. After you install Billing Care, enable SSL communication between Billing Care and BRM. For information about securing Billing Care, see "Billing Care Security" in BRM Security Guide.