9 Installing BRM Client and Server Applications on UNIX

This chapter describes how to install Oracle Communications Billing and Revenue Management (BRM) applications on UNIX.

The Oracle Communications Billing and Revenue Management (BRM) system includes applications that provide graphical user interfaces to the data in the BRM database. The following applications are available:

Self-Care Manager server application: Use to provide customer self-care services using Web browsers and wireless devices. Customers use Self-Care Manager to view their account details. See "About Self-Care Manager" in BRM Managing Customers.

To install Self-Care Manager, see "Installing Self-Care Manager".
Developer Center client application: Use for programming tasks, including creating and modifying storable classes, testing customizations, and importing events from log files into BRM. See "About Developer Center" in BRM Developer's Guide.

To install Developer Center, see "Installing BRM Client Applications".

Important:
Before installing server or client applications, you must first install BRM.

Downloading Applications

You download the software by using a Web browser. If your server is not running a Web browser, you can download and extract the software to a PC and then use ftp to transfer the file to the server.

Download the software to a temporary directory (temp_dir).
Save the .tar.Z file to a temporary directory (temp_dir).
Log in as user pin:
```
% su - pin
  
```
Go to the temporary directory where you downloaded the software (temp_dir) and uncompress and extract the .tar.Z file:
```
% cd temp_dir 
% uncompress file_name.tar.Z 
% tar -xvf file_name.tar 
  
```
This extracts the files to a subdirectory of the current directory.

Installing BRM Client Applications

This section describes how to install BRM client applications. Developer Center applications are the only applications supported on UNIX.

Installing the Software

Go to the directory where you downloaded and extracted the software .tar.Z file.
Open the setup.cnf file with any text editor. The default version of the file contains this configuration information:
```
INSTALL_PATH=/opt/portal/7.5/application_Name 
MAIN_CM_HOSTNAME=__ENTER_INFORMATION__ 
MAIN_CM_PORT=11960 
JRE_Path=$INSTALL_PATH
  
```
For Developer Center, application_Name is DevCenter.
(Optional) To change the default installation directory of /opt/portal/7.5/application_Name, specify a new path in the INSTALL_PATH entry.
For MAIN_CM_HOSTNAME, enter the name of your BRM system host.
(Optional) For MAIN_CM_PORT, enter your BRM system port number if it's different from the default of 11960.
Enter the JRE path if it's different from the default.
Save and close the file.
Enter this command to install the application:
```
% ./install.ksh
  
```

The application is installed in the directory specified in the setup.cnf file.

Starting BRM Client Applications

To start a client application:

Go to the install_dir directory.
Enter the following command:
```
./application_Name.sh
```

Installing Event Extraction Manager

For more information about Event Extraction Manager, see "Using Event Extraction Manager" in BRM Setting Up Pricing and Rating.

The default installation automatically installs all three applications on your system. To install only the Event Extraction Manager software, you must use the custom install.

To install the event loaders and Event Extraction Manager together, follow the instructions in "Installing Rated Event Loader" in BRM Configuring Pipeline Rating and Discounting.

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 only the Event Extraction Manager:

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".
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_RatedEventLoader_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.
To install Event Extraction Manager either on this computer or on another computer, select custom install when asked to specify the setup type. Select the EventExtractionTool component by typing its number and click Next.
Follow the instructions displayed during installation. The default installation directory for Event Extraction Manager is opt/portal/7.5.

Note:
The installation program does not prompt you for the installation directory if BRM or Event Extraction 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 Event Extraction 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.

Your Event Extraction Manager installation is now complete.

Installing BRM SDK

For more information about BRM SDK, see "Using BRM Developer Tools" in BRM Developer's Guide.

You can install BRM SDK independently of the BRM server, making it possible to isolate development activities from production servers. For example, you can install BRM SDK on each of the computers used by BRM developers at your site. These developers can share access to test and production BRM servers.

While it is not necessary to install BRM SDK on BRM servers, there are some advantages to doing so. For example, installing the SDK on your BRM server gives you access to sample applications that are not included in the server installation.

Important:

To use BRM SDK, you must have access to a test installation of BRM. Use the test installation to verify the functionality of new or customized components before deploying them to your production BRM installation. See "Testing New or Customized Components" in BRM Developer's Guide.
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.

You can install BRM SDK on Solaris, Linux, and AIX. See "BRM Software Compatibility" for specific version numbers.

To install BRM SDK:

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".
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_Portal_SDK_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.
When prompted, enter the directory where you want to install BRM SDK.

The default directory for installing BRM SDK is opt/portal/7.5/PortalDevKit.

The installation program installs BRM SDK files in the specified directory.
Note:
- The installation directory is called BRM_SDK_home in the documentation.
- Do not install BRM SDK in the same installation directory in which you installed BRM or any other optional component.
Go to the directory where you installed the BRM SDK package and source the source.me file:

Bash shell:
```
source source.me.sh
  
```
C shell:
```
source source.me.csh
  
```

Your BRM SDK installation is now complete.

Uninstalling BRM SDK

To uninstall BRM SDK, run the BRM_SDK_home/uninstaller/Portal_SDK/uninstaller.bin.

Note:

The uninstallation will not uninstall any compiled BRM SDK policy files. These files should be manually removed.

Installing PCM SDK

For more information about Portal Communications Module (PCM) SDK, see "Using BRM Developer Tools" in BRM Developer's Guide.

You can install PCM SDK independent of the BRM server, making it possible to isolate development activities from production servers. For example, you can install PCM SDK on each of the computers used by BRM developers at your site. These developers can share access to test and production BRM servers.

While it is not necessary to install PCM SDK on BRM servers, there are some advantages to doing so. For example, installing the SDK on your BRM server gives you access to sample applications that are not included in the server installation.

Important:

To use PCM SDK, you must have access to a test installation of BRM. Use the test installation to verify the functionality of new or customized components before deploying them to your production BRM installation. See "Testing New or Customized Components" in BRM Developer's Guide.
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.
Third-Party software and BRM SDK must be installed before you install PCM SDK, otherwise the installation of PCM SDK will fail.

You can install PCM SDK on Solaris, AIX, and Linux. See "BRM Software Compatibility" for specific version numbers.

To install PCM SDK:

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".
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_PCM_SDK_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.
- PCM SDK is automatically installed in the same directory as BRM SDK. The default directory for installing BRM SDK is opt/portal/7.5/PortalDevKit.
Go to the directory where you installed the PCM SDK package and source the source.me file:

Bash shell:
```
source source.me.sh
  
```
C shell:
```
source source.me.csh
  
```

Your PCM SDK installation is now complete.

Uninstalling PCM SDK

To uninstall PCM SDK, run the BRM_SDK_home/uninstaller/PCM_SDK/uninstaller.bin program.

Note:

The uninstallation will not uninstall any compiled PCM SDK policy files. These files should be manually removed.

Installing Self-Care Manager

To use Self-Care Manager, you must install a third-party application server and Self-Care Manager itself. Follow these procedures to install everything you need to run Self-Care Manager:

Installing an Application Server
Installing the Self-Care Manager Files

Important:
You must install the application server and Self-Care Manager on the same system. The Connection Manager (CM) can be on the same system as Self-Care Manager or on a different system.

Installing an Application Server

Supported application servers include Tomcat, WebLogic, and WebSphere. For more information, see the vendor installation instructions for the application server you are using.

Installing the Self-Care Manager Files

Before installing Self-Care Manager, make sure an application server is already installed.

To install the Self-Care Manager files:

Follow the steps for Downloading Applications.
In the temporary directory where you downloaded the Self-Care Manager .tar file, open the setup.cnf file with any text editor. The default version of the file contains this configuration information:
```
INSTALL_PATH=/opt/portal/7.5/WebKit 
MAIN_CM_HOSTNAME=__ENTER_INFORMATION__ 
MAIN_CM_PORT=11960 
  
```
(Optional) To change the default installation directory of /opt/portal/7.5/WebKit, specify a new path in the INSTALL_PATH entry.

Note:
You can install Self-Care Manager in any location.
For MAIN_CM_HOSTNAME, enter the name of your BRM system host.
(Optional) For MAIN_CM_PORT, enter your BRM system port number if it's different from the default of 11960.
Save and close the file.
Enter this command to install Self-Care Manager:
```
% ./install.ksh
  
```
Self-Care Manager is installed in the directory specified in the setup.cnf file.

After installing the Self-Care Manager files, configure the application server to work with Self-Care Manager. See "Configuring the Application Server" in BRM Managing Customers.

What's Next?

After installing the BRM server and client applications, you need to test BRM with your business models:

For an overview of setting up price lists, see "Setting Up Price List Data" in BRM Setting Up Pricing and Rating.
For an overview of setting up billing, see "Setting Business Policies for Billing" in BRM Configuring and Running Billing.
For an overview of setting up customer registration and managing customer accounts, see "Customizing Registration" in BRM Managing Customers and "About Registering Customers" in BRM Concepts.