This chapter describes Oracle Communications Billing Care software and hardware requirements.
Billing Care is deployed on an Oracle WebLogic Server domain configured as an Oracle Entitlements Server (OES) client domain. The OES Client domain connects to the following Oracle Identity and Access Management (IAM) components:
OES Administration Server for resource authorization
Oracle Access Management (OAM) for domain authorization
Oracle Identity and Access Management (OIM) is used for user authentication
Oracle Unified Directory (OUD) for user directory management
IAM requires an Oracle Enterprise Database for storing authentication and authorization policies and user information. Use the Fusion Middleware Repository Creation Utility (RCU) to create the necessary database schemas in your database. See Fusion Middleware Repository Creation Utility User's Guide for more information on the RCU.
Oracle provides Life Cycle Management tools (LCM) for installing IAM. See Deployment Guide for Oracle Identity and Access Management for more information on using LCM to install and configure the required products. Alternatively, consult the individual product documentation if you choose to use individual product installers.
Billing Care is supported only on the software and hardware listed in the following sections. You must install and connect all required software components for a secure installation.
Table 3-2 lists software required for running Billing Care.
Download required Oracle software from the Oracle Software Delivery Cloud:
or Oracle Technology Network:
http://www.oracle.com/technetwork/indexes/downloads/index.html
or Oracle support web site:
Table 3-2 Billing Care Software Requirements
| Product | Version |
|---|---|
|
Oracle WebLogic Server 11g Enterprise Edition |
10.3.6 |
|
Oracle Database Server |
The same version used by the BRM 7.5 installation that Billing Care connects to. See the installation guide for your database host operating system for additional information on database hardware and software requirements at: |
|
Oracle Fusion Middleware Repository Creation Utility 11g |
11.1.1.9.0 |
|
Oracle Identity and Access Management Repository Creation Utility and Life Cycle Management Tools (includes Oracle Identity Management (OIM), Oracle Unified Directory (OUD), Oracle Entitlements Server (OES), and Oracle Access Manager (OAM)) |
11gR2PS2 (11.1.2.2.0) or later |
|
Oracle Communications Billing and Revenue Management (BRM) on Linux x86 or x86-64 or Solaris SPARC (64 bit) |
7.5 Patch Set 15 and later patch sets |
|
Internet Browser |
(Windows only) Microsoft Internet Explorer 11 Mozilla Firefox 32 Google Chrome 38 |
|
64bit Java Development Kit (JDK) |
1.7.0_79 |
The Billing Care installer validates the JDK version and checks for a running OES Client domain before deploying Billing Care. Detected errors, any missing or unavailable components, or any connectivity-related issues are displayed in the Billing Care installer.
For production installations, you must install the required software listed in Table 3-2 and perform the required pre-installation procedures listed in "Billing Care Pre-Installation Tasks" before running the Billing Care installer. Test installations can be done on a basic WebLogic domain.
The number and configuration of the hosts used for your Billing Care installation depend on your requirements. For example, large transaction volumes, multiple geographical locations, or fail-over requirements affect the amount of required hardware.
Table 3-3 lists the recommended hardware requirement for a single server production Billing Care installation containing all components. See "Preparing to Install" in Oracle Fusion Middleware Installation Guide for Oracle Identity and Access Management for more information on IAM component hardware and sizing.
Table 3-3 Billing Care Single Server Minimum Hardware Requirements
| Component | Requirement |
|---|---|
|
Hard disk |
200 GB of free disk space Note: A minimum of 1.5 GB should be free in the domain home. |
|
Processor |
Oracle recommends using 6 or more cores, each running at 1.5 GHz or greater. |
|
Memory |
A minimum of 35 GB physical memory and 16 GB swap. If you plan to install the required database on the same server, see "Checking the Hardware Requirements" for more information about required memory. For more information on calculating required memory in your environment, see Oracle Fusion Middleware System Requirements and Specifications for Oracle Identity and Access Management at:
|
Table 3-4 lists the minimum hardware requirement for each OES Client domain host on which Billing Care is deployed.
Table 3-4 Billing Care OES Client Domain Server Minimum Hardware Requirements
| Component | Requirement |
|---|---|
|
Hard disk |
30 GB of free disk space Note: A minimum of 1.5 GB should be free in the domain home. |
|
Processor |
Oracle recommends using twin cores, each running at 1.5 GHz or greater. |
|
Memory |
A minimum of 8 GB physical memory and 8 GB swap for the OES Client domain server. For more information on calculating required memory in your environment, see Oracle Fusion Middleware System Requirements and Specifications for Oracle Identify and Access Management at:
|
For information on network considerations, including support for IPv6 addresses, see "Configuring IPv4 and IPv6 for Fusion Middleware Products" in Oracle Fusion Middleware System Requirements and Specifications at:
http://docs.oracle.com/html/E18558_01/fusion_requirements.htm#BABICJGA