2 Installing Revenue Assurance Manager

This chapter describes how to install Oracle Communications Billing and Revenue Management (BRM) Revenue Assurance Manager and Revenue Assurance Center.

Before you read this chapter, you should be familiar with BRM concepts and architecture. See:

System Requirements

Revenue Assurance Manager server component is supported on the HP-UX IA64, Linux, AIX, and Solaris operating systems. For information on disk space requirements for these operating systems, see BRM Installation Guide.

Revenue Assurance Center is supported on the Windows platform and requires approximately 100 MB of disk space.

Software Requirements

Before installing Revenue Assurance Manager, you must install:

  • Third-Party software, which includes the Perl libraries and JRE required for installing BRM components. See the instructions for installing the Third-Party software in BRM Installation Guide.

  • BRM. See BRM Installation Guide.

  • Oracle version 10g or 11g.


    If you are using an earlier version of Oracle, you must upgrade it before you install Revenue Assurance Manager. For information on upgrading Oracle, see your Oracle documentation.

Before installing Revenue Assurance Center, you must install BRM. See BRM Installation Guide for install instructions.

Installing Revenue Assurance Manager


If you already have Revenue Assurance Manager installed, you must uninstall it before installing a new version.

To install Revenue Assurance Manager:

  1. Download the software to a temporary directory (temp_dir).


    • If you download to a Windows workstation, use FTP to copy the .bin file to a temporary directory on your UNIX server.

    • You must increase the heap size used by the Java Virtual Machine (JVM) before running the installation program to avoid ”Out of Memory” error messages in the log file. See "Increasing Heap Size to Avoid ”Out of Memory” Error Messages" in BRM Installation Guide for more information.

  2. Go to the directory where you installed the Third-Party package and source the source.me file.


    You must source the source.me file to proceed with installation, otherwise ”suitable JVM not found” and other error messages appear.

    Bash shell:

    % source source.me.sh

    C shell:

    % source source.me.csh
  3. Go to temp_dir and enter this command:

    % 7.5.0_RevAssuranceMgr_platform_opt.bin

    where platform is the operating system name.


    You can use the -console parameter to run the installation in command-line mode. To enable a graphical user interface (GUI) installation, install a GUI application such as X Windows and set the DISPLAY environment variable before you install the software.
  4. Follow the instructions displayed during installation. The default installation directory for Revenue Assurance Manager is /opt/portal/7.5.


    The installation program does not prompt you for the installation directory if BRM or Revenue Assurance Manager is already installed on the machine and automatically installs the package at the BRM_Home location.
  5. Go to the directory where you installed the Revenue Assurance Manager package and source the source.me file:

    Bash shell:

    % source source.me.sh

    C shell:

    % source source.me.csh
  6. Change directory to the BRM_Home/setup directory and run the pin_setup script.


    The pin_setup script starts all required BRM processes.
  7. If your event tables are partitioned, run the partition_utils utility with the -o update parameter from the BRM_Home/apps/partition_utils directory:

    % perl Bin_Home/bin/partition_utils -o update

    See "Updating Partitions" and "partition_utils" in BRM System Administrator's Guide for more information.

Your Revenue Assurance Manager installation is now complete.

Loading the CollectProcessAudit Trigger in Rated Event Loader

This section explains how to define the CollectProcessAuditForIREL trigger in Rated Event (RE) Loader. You must define this trigger in RE Loader before using Revenue Assurance Manager. CollectProcessAuditForIREL defines event ID and batch ID mapping in rated EDRs and loads them into the BRM database.

To load the trigger:

  1. Go to the BRM_Home/sys/data/config directory.

  2. Run the following command:

    % sqlplus login/password @$ORACLE_SID @CollectProcessAuditForIREL.sql

    where ORACLE_SID is the BRM database alias.

Configuring Universal Event Loader to Load Revenue Assurance Data

To configure the Universal Event (UE) Loader properties file to load revenue assurance data:

  1. Open the UE Loader properties file (BRM_Home/apps/uel/Infranet.properties) in a text editor.

  2. Change this setting:

    infranet.uel.date_pattern = dd/MMM/yyyy:hh:mm:ss a zzzz 

    to this:

    infranet.uel.date_pattern = yyyyMMddHHmmss.
  3. Change the infranet.uel.max_threads entry to 1.

  4. (Optional) Change the infranet.uel.max_load_errors entry.

    This entry determines whether UE Loader will continue loading records even after receiving errors. UE Loader stops loading records when the number of errors it receives reaches the error limit defined in infranet.uel.max_load_errors. To ignore the errors and continue loading the remaining records, set this entry to a higher number. The default is 9999.

  5. Save and close the file.

About Installing Revenue Assurance Center

Revenue Assurance Center is an optional client application you can use to search for and display revenue assurance information that is stored in the BRM database.

Before installing Revenue Assurance Center, obtain information about the machine running the CM to which Revenue Assurance Center will connect, such as:

  • A location for the software (if other than the default)

  • Computer or server name

  • Port number

  • Database number

Installing Revenue Assurance Center

To install Revenue Assurance Center:

  1. Download the software to a temporary directory (temp_dir).

  2. Select the .zip file, and click the Install button.

    You will be prompted for the following information:

    • The destination folder. Click Next to use the default location, or enter a different directory.

    • On the Connection Manager screen, enter the server, port, and database information. Click Next.

    • On the Select Program Folder screen, accept the default program folder, BRM, or select a new one. Click Next.

  3. On the Start Copying Files screen, click Next to start installing the application.

  4. Click Finish to complete the installation process.

Starting and Using Revenue Assurance Center

To start Revenue Assurance Center:

  1. From the start options, choose Revenue Assurance Center, which is under Portal.

    The Revenue Assurance Center user interface opens.


    When prompted, enter the BRM login and password. Contact your system administrator to obtain the default username and password.
  2. Click the Revenue Assurance Center Help button to display information on how to use Revenue Assurance Center.

See "Customizing Revenue Assurance Center" for information on how you can change features in Revenue Assurance Center.

Uninstalling Revenue Assurance Manager

To uninstall Revenue Assurance Manager, run the BRM_Home/uninstaller/RevAssuranceMgr/uninstaller.bin.