3 ECE System Requirements

This chapter describes the software, hardware, and information requirements for Oracle Communications Billing and Revenue Management Elastic Charging Engine (ECE).

Note:

This chapter lists requirements for ECE 11.2 Patch Set 8 software, the latest release of ECE. ECE patch sets are full installations, and ECE 11.2 Patch Set 8 includes all features from the base release, prior patch sets, and interim patches.

Software Requirements

This section describes the supported and required software.

Table 3-1 lists operating systems that support ECE.

Table 3-1 Supported Operating Systems

Product Version

Red Hat Enterprise Linux (64bit)

Important: To protect from security vulnerabilities, ensure you apply the latest critical patch updates. See "About Critical Patch Updates".

ECE is certified on Red Hat Enterprise Linux 5 and 6; regularly apply the latest patch set for Red Hat Enterprise Linux 5 and 6 to ensure that you have the latest security fixes.

5.0 (plus latest patch updates)

6.0 (plus latest patch updates)

Oracle Linux (64bit)

Important: To protect from security vulnerabilities, ensure you apply the latest critical patch updates. See "About Critical Patch Updates".

ECE is certified on Oracle Linux 5 and 6 and you should regularly apply the latest patch set for Oracle Linux 5 and 6 to ensure that Oracle Linux has the latest security fixes.

5.0 (plus latest patch updates)
with Release 2 Unbreakable Enterprise Kernel (UEK)

6.0 (plus latest patch updates)
with Release 2 or 3 UEK

Oracle Solaris for SPARC (64bit)

10


Table 3-2 lists the required third-party software.

Table 3-2 Required Software

Product Version

Groovy

For ECE 11.2 Patch Set 2:

  • 2.1.3

For ECE 11.2 Patch Set 3 through ECE 11.2 Patch Set 5:

  • 2.2.2

For ECE 11.2 Patch Set 6 through ECE 11.2 Patch Set 8:

  • 2.3.9

Java Platform, Standard Edition (Java SE), containing Java Development Kit (JDK) and Java Runtime Environment (JRE)

(32bit or 64bit)

Important: To protect from security vulnerabilities, ensure you apply the latest critical patch updates. See "About Critical Patch Updates".

ECE is certified on JDK7 and you should regularly apply the latest patch set for JDK7 to ensure that JDK has the latest security fixes.

1.7.0 (plus latest patch updates)

Oracle Coherence for Java libraries

The ECE package includes only those Oracle Coherence libraries that are required by ECE (not all Oracle Coherence libraries); these libraries are installed as part of the ECE installation.

For ECE 11.2 Patch Set 2:

  • 3.7.1

For ECE 11.2 Patch Set 2 through ECE 11.2 Patch Set 5:

  • 12.1.2.0.1

For ECE 11.2 Patch Set 6 through ECE 11.2 Patch Set 8:

  • 12.1.2.0.3


Table 3-3 lists the additional products required for running ECE in an integrated, end-to-end test or production system. Network mediation software is required for ECE to communicate with network-facing applications of the charging system.

For a production system, Oracle recommends that you install all the additional products using the same operating system in the system on which you install ECE. However, you may choose to install the other products using different operating systems for a test system.

Table 3-3 Required Products in an Integrated System

Product Version

Pricing Design Center (PDC)

For ECE 11.2 base release:

  • 11.1 Patch Set 3

For ECE 11.2 Patch Set 2:

  • 11.1 Patch Set 5

For ECE 11.2 Patch Set 3:

  • 11.1 Patch Set 5

For ECE 11.2 Patch Set 4:

  • 11.1 Patch Set 6

For ECE 11.2 Patch Set 5:

  • 11.1 Patch Set 6 and interim patch 20126599

For ECE 11.2 Patch Set 6:

  • 11.1 Patch Set 7 and interim patch 21441932

For ECE 11.2 Patch Set 7 and interim patch ECE 11.2.0.7.1:

  • 11.1 Patch Set 7 and interim patch 21650219

For ECE 11.2 Patch Set 8:

  • 11.1 Patch Set 7 and interim patch 22826383

Oracle WebLogic Server 11g Enterprise Edition

Note: Installing Oracle WebLogic Server is a prerequisite for PDC. ECE also uses Oracle WebLogic Server in an integrated system.

For ECE 11.2 base release and ECE 11.2 Patch Set 1:

  • 10.3.4

For ECE 11.2 Patch Set 2 through ECE 11.2 Patch Set 8:

  • 10.3.6

Oracle Communications Billing and Revenue Management (BRM)

For ECE 11.2 base release and ECE 11.2 Patch Set 1:

  • 7.5 Patch Set 5 and interim patch 17169116

For ECE 11.2 Patch Set 2:

  • 7.5 Patch Set 8

For ECE 11.2 Patch Set 3:

  • 7.5 Patch Set 8 and interim patch 18870571

For ECE 11.2 Patch Set 4:

  • 7.5 Patch Set 10

For ECE 11.2 Patch Set 5:

  • 7.5 Patch Set 10 and interim patch 20208473

For ECE 11.2 Patch Set 6:

  • 7.5 with Patch Set 12 and interim patch 21231092

For ECE 11.2 Patch Set 7:

  • 7.5 Maintenance Patch Set 1 and interim patch 21663796

For ECE 11.2 Patch Set 8:

  • 7.5 Maintenance Patch Set 1 and interim patches 21663796, 21781375, and 23284086

Oracle Communications Offline Mediation Controller

ECE supports Offline Mediation Controller on Linux x86 or x86-64 or Solaris SPARC (64bit).

For ECE 11.2 Patch Set 1:

  • 6.0.0.1.0

For ECE 11.2 Patch Set 2 through ECE 11.2 Patch Set 4:

  • 6.0.0.2.0

For ECE 11.2 Patch Set 5:

  • 6.0.0.2.0 and interim patch 20111745

For ECE 11.2 Patch Set 6 through ECE 11.2 Patch Set 8:

  • 6.0.0.3.0 with 6.0.0.3.0 ECE distribution cartridge

Oracle Communications Online Mediation Controller (backward compatibility only)

For backward compatibility, ECE supports Online Mediation Controller on Linux x86 or x86-64 or Solaris SPARC (64bit).

Important: Online Mediation Controller is supported only for backward compatibility for existing implementations. Use Diameter Gateway for new implementations.

6.1.0.0.8 and patch 21277110

Oracle NoSQL Database Enterprise Edition

For ECE 11.2 base release and ECE 11.2 Patch Set 1:

  • 11gR2 (11.2.2.0.39)

For ECE 11.2 Patch Set 2 through ECE 11.2 Patch Set 5:

  • 12cR1 (12.1.2.1.54)

For ECE 11.2 Patch Set 6 through ECE 11.2 Patch Set 8:

  • 12cR1 (12.1.2.1.57)


Table 3-4 lists optional software products.

Table 3-4 Optional Products

Product Version

Oracle Application Management Pack for Oracle Communications (for monitoring ECE nodes)

12.1.0.1


About Critical Patch Updates

You should install all critical patch updates as soon as possible. To download critical patch updates, find out about security alerts, and enable email notifications about critical patch updates, see the Security topic on Oracle Help Center:

http://www.oracle.com/technetwork/topics/security/whatsnew/index.html

Hardware Requirements

The number and configuration of the computers that you employ for your ECE installation depend on the scale and the kind of deployment you have planned according to your charging requirements. Work with your performance team to determine your sizing requirements.

For a standalone system, ECE requires:

  • 4 GB of RAM (or more)

  • 200 MB of disk space (or more)

  • 2 x86 cores (or more)

Information Requirements

This section describes the information that you must provide during the ECE installation. You define some of these values when you install and configure BRM, PDC, Oracle NoSQL Database, and Oracle WebLogic Server for PDC.

Note:

Oracle recommends that you print the tables in this section and record the values for future reference.

Certain information is required for both an ECE standalone installation and an ECE integrated installation. See "Information Requirements for Standalone and Integrated Installations."

Additional information is required for an integrated installation. See "Information Required Only for an ECE Integrated Installation."

For more information about standalone and integrated installations, see "Overview of ECE Installed Components."

Tip:

This section describes information that you must provide during the ECE installation process for predefined values. For a preview of all required information, including values that you set during installation, see "Elastic Charging Engine Installer Screens".

Information Requirements for Standalone and Integrated Installations

This section describes the information requirements common to both an ECE standalone installation and an ECE integrated installation.

Persistence Data Details

During the installation, you must specify the path to the directory into which the ECE BRM CDR plug-in will write call detail record (CDR) files of rated events.

This is the directory where the plug-in stores completed CDR files that are ready to be processed by BRM.

Required Information for Machines in the Coherence Cluster

Table 3-5 lists the information requirements for the machines in the Coherence cluster.

If convenient, you can use the Value column of the table to note the values for your specific installation so that you have them available when you run the ECE installer.

Table 3-5 Information for Machines in the Coherence Cluster

Information Type Description Value

User name

The user name for all machines in the cluster. You create this user and specify the user name as a pre-installation task.

All machines must have the same user name.

Tip: Along with same user name, all the servers must also allow password-less SSH login for the driver machine user.

-

Java heap settings

The memory to be allocated to each node in the Coherence cluster.

-

Cluster name

The Coherence cluster name used by applications for identifying ECE in the cluster.

The cluster name must be less than 32 characters.

-

Host names or IP addresses

The names or the IP addresses of all host machines on which ECE nodes will reside.

This information is required only if you enable security-related configurations during the installation with or without Secure Sockets Layer (SSL).

Include your computer name in this entry. Do not enter localhost or a loopback address.

-

IP address range

If you have multiple hosts in the same subnet, note the from and to IP addresses for the range of hosts in the same subnet.

This information is required only if you enable security-related configurations during the installation with or without SSL.

-

Administrator alias name

The alias name that defines the administrator for securing the Coherence cluster. You define this value during installation.

This is required only if you enable SSL and security-related configurations during the installation.

This value cannot be changed after it is set.

-

Administrator alias password

The password for the administrator alias. You define this value during installation.

This is required only if you enable SSL and security-related configurations during the installation.

This value cannot be changed after it is set.

-


Required Oracle NoSQL Database Information

Table 3-6 lists the Oracle NoSQL database information required during the ECE installation.

If convenient, you can use the Value column of the table to note the values of the fields for your specific installation so that you have it available when you run the ECE installer.

Table 3-6 Oracle NoSQL Database Information

Information Type Description Value

Host name

The name of the machine on which Oracle NoSQL database is installed.

-

Port number

The port number assigned to the Oracle NoSQL Database service.

-

Data store name

The name of the data store in which you want ECE to persist rated event information. This must be the name that you defined during the installation of Oracle NoSQL database.

-


Keystore Credentials Information

ECE uses credential stores or keystores for cluster security. You will be asked to specify keystore credential values during the installation process.

ECE uses two keystore files:

  • The keystore.jks file stores cipher keys used for encrypting the passwords used between ECE and BRM or PDC when required.

  • The server.jks file is used for enabling Secure Sockets Layer (SSL) and stores cipher keys used for keeping the Coherence cluster secure.

During the ECE installation, you are asked to specify the following keystore credential information:

  • The password ECE uses to access the boundary system alias key in the keystore.jks file. The boundary systems are BRM and PDC.

  • The certificate store password used for accessing the keystore.jks and server.jks files.

  • The authorization of users for what they can do regarding cluster security. You set this value in the DName field during installation.

    The DName (acronym for Distinguished Name) is similar to a group in UNIX.

    Examples:

    CN=Administrator,OU=Rating,O=CompanyB
    

    Or:

    CN=Developer,OU=ECE
    

    Where:

    • CN is the common name for the user.

    • OU is the organizational unit of the user.

    • O is the organization of the user.

For more information about the keystores and how they are used, see the discussion of setting up and managing Elastic Charging Engine security in BRM Elastic Charging Engine System Administrator's Guide.

Required Diameter Gateway Information

During installation, you must specify the following information that Diameter clients use to identify your Diameter Gateway server.

Field or Option Description
Skip During installation, you must specify whether Diameter Gateway is started when ECE is started.
Origin Host The value for the Origin-Host attribute-value pair (AVP) to be sent in the Diameter request.

This is a unique identifier that you assign your Diameter Gateway server on its host. It can be any string value.

This value is used by the Diameter client to identify your Diameter Gateway server as the connecting Diameter peer that is the source of the Diameter message.

Origin Realm The value for the Origin-Realm AVP to be sent by the Diameter Gateway in outgoing Diameter requests.

This is the signaling realm (domain) that you assign your Diameter Gateway server.

This value is used by Diameter clients to identify your Diameter Gateway server as the source of the Diameter message.


For more information about how the Origin-Host and Origin-Realm AVPs can be specified, refer to Internet Engineering Task Force (IETF) Network Working Group RFC 3588 (Diameter Base Protocol).

The Diameter Gateway details you enter in this screen apply to a single instance (node) of a Diameter Gateway server that the installer adds to your ECE topology. You must add more Diameter Gateway nodes to your topology after installation. See BRM Elastic Charging Engine Installation Guide for more information.

Required Third-Party Library Information

During the installation, you need to know the directory where you saved the JAR files required for the ECE installation process.

For more information, see "Obtaining Required JAR Files."

Information Required Only for an ECE Integrated Installation

This section describes the additional information requirements for an ECE integrated installation.

Config Data Details

During the installation, you must specify the path to the directory that contains configuration data (mediation specifications).

After installation, when you load data into ECE, the loading utility reads and loads configuration data from this directory.

For more information about configuration data, see the discussion about implementing ECE with BRM in BRM Elastic Charging Engine Implementation Guide.

Required WebLogic Server Information

You install WebLogic Server when you install PDC. You set up two JMS queues on a WebLogic server:

  • A pricing data JMS queue that ECE listens on to consume pricing data that PDC publishes into the queue.

  • A notification event queue (JMS topic) into which ECE publishes notification events that external systems, such as network mediation programs, can consume to obtain data for their own processing.

    Note:

    ECE provides a post-installation script that will create the notification event queue for you.

Table 3-7 lists the WebLogic Server information that is required during the ECE installation.

If convenient, you can use the Value column of the table to note the values of the fields for your specific installation so that you have it available when you run the ECE installer.

Table 3-7 WebLogic Server Information

Information Type Description Value

Host name

The host name of the server on which the JMS queues reside.

-

Port number

The port number of the server on which the JMS queues reside.

-

User name

The user name for logging in to the WebLogic server on which the JMS queues reside.

-

Password

The password for logging in to the WebLogic server on which the JMS queues reside.

-

Module name

The JMS system module name on the WebLogic server on which the JMS queues reside.

-

Subdeployment

The name of the subdeployment target in the JMS system module.

-

Connection Factory name

The connection factory name that is used to create connections to the JMS topic queue on the WebLogic Server to which ECE will publish notification events.

After you install ECE, you will run an ECE post-installation script that will create the JMS topic queue on the WebLogic Server. The connection factory name is used by the script to create the connections to the JMS topic queue.

-

Topic Name

The JMS topic queue name of the JMS topic on the WebLogic Server to which ECE will publish notification events.

After you install ECE, you will run a post-installation script that will create the JMS topic on the WebLogic Server. The topic name is the name the ECE post-installation script will use to create the JMS topic.

-

Disable SSL

During installation, you must specify whether SSL will be used to secure the ECE JMS queue connection.

-

Keystore password

The password used to access the SSL keystore file.

-

Keystore location

The full path to the SSL keystore file.

-


Required BRM Information

Table 3-9 lists the BRM information required during the ECE installation.

If convenient, you can use the Value column of the table to note the values of the fields for your specific installation so that you have it available when you run the ECE installer.

Table 3-8 BRM Information

Information type Description Value

BRM user name

The user name for logging in to BRM.

-

BRM password

The password for logging in to BRM.

-

Database user name

The BRM database schema user name.

-

Database password

The password for the BRM database user.

-

Database driver

The driver used to connect to the BRM database.

-

Database host name

The IP address or the host name of the computer on which the BRM database is configured.

-

Database port number

The port number assigned to the BRM database service.

-

Service name

The name of the BRM database service.

-

CM host name

The IP address or the host name of the computer on which the BRM Connection Manager (CM) is configured.

-

CM port number

The port number for the CM.

-

Disable SSL

During installation, you must specify whether SSL will be used to secure the BRM Gateway connection.

-

Wallet file absolute path

The default path to the Oracle wallet file containing the SSL trusted certificates for BRM Gateway:

/opt/wallet/client/cwallet.sso

If SSL is enabled for BRM Gateway but the wallet is in a different location, you must replace the default path with the full path to the actual location during installation.

-

Queue name

The name of the database queue that the BRM Account Synchronization DM uses to publish business events for ECE to consume.

-

Suspense queue name

The name of the database queue that ECE will use to move failed update requests (for business-event data that could not be consumed by ECE) so they can be retried later.

An ECE post-installation script will create the queue itself. You only need to supply the name you want to use for the queue.

-

Acknowledgement queue name

The name of the database queue that ECE will use to publish acknowledgement events for BRM to consume (used for rerating).

An ECE post-installation script will create the queue itself. You only need to supply the name you want to use for the queue.

-


Required External Manager Gateway Information

Table 3-9 lists the External Manager (EM) Gateway information required during the ECE installation.

If convenient, you can use the Value column of the table to note the values of the fields for your specific installation so that you have it available when you run the ECE installer.

Table 3-9 BRM Information

Information type Description Value

Number EM Gateways

The number of EM Gateway instances you want ECE to run automatically when you start EM Gateway.

-

Starting Port Number

The port number assigned to EM Gateway.

If you have more than one EM Gateway instance, this is the starting port number. Subsequent port numbers increase by one for each additional EM Gateway instance. For example, if the starting port number is 15502 and you specify three EM Gateway instances, ports 15502, 15503, and 15504 are used by EM Gateway processes.

Ensure that no other processes on the machine use port numbers assigned to EM Gateway instances.

-

Disable SSL

During installation, you must specify whether SSL will be used to secure the EM Gateway connection.

-

Client Authentication Disabled

During installation, you must specify whether authentication is performed to check whether EM Gateway is allowed to communicate with ECE.

-

Wallet File Absolute Path

The default path to the Oracle wallet file containing the SSL trusted certificates for EM Gateway:

/opt/wallet/server/cwallet.sso

If SSL is enabled for EM Gateway but the wallet is in a different location, you must replace the default path with the full path to the actual location during installation.

-


Required PDC Pricing Components Queue Information

During the installation, you must specify the system connection information of the server on which the JMS queue for PDC pricing component data resides.

PDC publishes pricing component data into this queue. ECE listens on this JMS queue to consume the pricing component data.

Field or Option Description
Host Name The IP address or the host name of the computer on which the PDC JMS queue resides.
Port Number The port number of the computer on which the PDC JMS queue resides.
User Name The user for logging in to the server on which the PDC JMS queue resides.
Password The password for logging in to the server on which the PDC JMS queue resides.
Disable SSL During installation, you must specify whether SSL will be used to secure the PDC JMS queue connection.
PDC Keystore Password The password used to access the SSL keystore file.
Keystore Path The full path to the SSL keystore file.