This chapter explains how to install the Oracle Communications Billing and Revenue Management (BRM) Collections Manager software. Installation includes both client and server components.
Note:
Collections Manager Reports are installed separately. See "Installing BRM Reports" in BRM Reports.Before you read this chapter, you should be familiar with BRM concepts and architecture. See "Introducing BRM", "BRM System Architecture" in BRM Concepts, and "Understanding Collections Manager".
The BRM Collections Manager server components include opcodes, utilities, and storable classes. You install these components in the BRM_Home directory.
The Collections Manager server components are supported on the HP-UX IA64, Solaris, Linux, and AIX operating systems. For information on disk space requirements for these operating systems, see "Disk Space Requirements" in BRM Installation Guide.
Before installing the BRM Collections Manager server components, you must install:
Third-Party software, which includes the PERL libraries and JRE required for installing BRM components. See "Installing the Third-Party Software" in BRM Installation Guide.
BRM. See "Putting Together Your BRM System" in BRM Installation Guide.
Oracle database software.
Note:
If you have already installed the product, features that are already installed cannot be reinstalled without uninstalling them first. To reinstall a feature, uninstall it and then install it again.To install BRM Collections Manager server components:
Download the software to a temporary directory (temp_dir).
Important:
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. For information, see "Increasing Heap Size to Avoid ”Out of Memory” Error Messages" in BRM Installation Guide.
Go to the directory where you installed the Third-Party package and source the source.me file.
Caution:
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
Go to the temp_dir directory and enter this command:
7.5.0_CollectionsMgr_platform_opt.bin
where platform is the operating system name.
Note:
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.Follow the instructions displayed during installation. The default installation directory for Collections Manager is opt/portal/7.5.
Note:
The installation program does not prompt you for the installation directory if BRM or Collections Manager is already installed on the machine and automatically installs the package at the BRM_Home location.Go to the directory where you installed the Collections Manager package and source the source.me file:
Bash shell:
source source.me.sh
C shell:
source source.me.csh
Go to the BRM_Home/setup directory and run the pin_setup script.
Note:
The pin_setup script starts all required BRM processes.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 partition_utils.pl -o update
For more information, see "Updating Partitions" and "partition_utils" in BRM System Administrator's Guide.
Start all BRM processes. See "Starting and Stopping the BRM System" in BRM System Administrator's Guide.
Your Collections Manager installation is now complete.
To run collections automatically, you need to edit the pin_bill_day script.
Open the pin_bill_day script in a text editor. The script is located in BRM_Home/bin.
Find the Collections Manager section of the script. If the following lines are commented out, remove the comment marks:
cd ${PINDIR}/apps/pin_collections
pin_collections_process
pin_collections_send_dunning
Save and close the file.
BRM Collections Manager includes two client applications:
Collections Configuration
Collections Center
The client applications are supported on Windows platforms only. You can install them in multiple locations, in any combination. Neither application requires the other.
You can install the client applications on Windows.
Table 2-1 shows the disk space required by client applications to download, extract, and install the software:
Table 2-1 Disk Space Requirements
| Application | Required Space (MB) |
|---|---|
|
Collections Configuration |
110 |
|
Collections Center |
110 |
Note:
Collections Configuration and Collections Center require the Java Runtime Environment (JRE). It is included in both application packages and is approximately 50 MB. When the JRE gets installed with a BRM client application, it is not installed again.Before installing BRM Collections Manager, you must install:
BRM. See "Putting Together Your BRM System" in BRM Installation Guide.
BRM Collections Manager server components. See "Installing Server Components".
An application such as WinZip for extracting compressed files.
You install the BRM Collections Manager client components in the same way that you install other BRM clients. Both components are installed separately. See "Installing BRM Client Applications on Windows" in BRM Installation Guide.
To uninstall BRM Collections Configuration, choose Start - Programs - Portal - Uninstall Collections Configurations and answer the prompts.
To uninstall BRM Collections Center, choose Start - Programs - Portal - Uninstall Collections Center and answer the prompts.
After you install BRM Collections Manager, you need to set it up. See "Setting Up Collections Manager".