9 Installing BRM Client and Server Applications on UNIX

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

  • Developer Center

  • Event Extraction Manager

  • BRM SDK

  • PCM SDK

  • Self-Care Manager

Installing Applications and Tools

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.

  1. Download the software to a temp_dir.

  2. Save the .tar.Z file to a temporary directory (temp_dir).

  3. Log in as user pin.

  4. Go to temp_dir and uncompress and extract the .tar.Z file.

Installing Developer Center

To install Developer Center:

  1. Go to temp_dir file.

  2. Open the setup.cnf file with any text editor. The default version of the file contains the following configuration information:

    INSTALL_PATH=/opt/portal/7.5/DevCenter 
    MAIN_CM_HOSTNAME=__ENTER_INFORMATION__ 
    MAIN_CM_PORT=11960 
    JRE_Path=$INSTALL_PATH
      
    
  3. (Optional) To change the default installation directory of /opt/portal/7.5/DevCenter, specify a new path in the INSTALL_PATH entry.

  4. Replace:

    • MAIN_CM_HOSTNAMEto your BRM system host.

    • (Optional) SetMAIN_CM_PORTto your BRM system port number.

  5. Set the JRE path if it is different from the default.

  6. Save and close the file.

  7. Run the following command:

    % ./install.ksh
    

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

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 Event Extraction Manager, use the custom install.

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

  1. Install 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".

  2. 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
      
    
  3. Go to temp_dir and run the following command:

    7.5.0_RatedEventLoader_platform_opt.bin
    

    where platform is the operating system UNIX.

    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.
  4. Select Custominstall when asked to specify the setup type.

  5. Enter the number of EventExtractionTool and click Next.

  6. 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 in the BRM_Home location.
  7. Go to the directory where you installed Event Extraction Manager and source the source.me file:

    Bash shell:

    source source.me.sh
      
    

    C shell:

    source source.me.csh
      
    
  8. Go to the BRM_Home/setup directory and run the pin_setup script.

    Note:

    pin_setup 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.

Though installing BRM SDK on BRM servers is not necessary, doing so has some advantages. 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.

To install BRM SDK:

  1. Install 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".

  2. 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
      
    
  3. Go to temp_dirand run the following command:

    7.5.0_Portal_SDK_platform_opt.bin
      
    

    where platform is the Linux.

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

    The default directory 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 directory in which you installed BRM or any other optional component.

  5. Go to BRM_SDK_Home 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:

  1. Go toBRM_SDK_Home/uninstaller/Portal_SDKdirectory.

  2. Run the following command:uninstaller.bin

Note:

The uninstallation does not uninstall any compiled BRM SDK policy files. Remove these file manually.

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.

Though installing BRM SDK on BRM servers is not necessary, doing so has some advantages. 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.

To install PCM SDK:

  1. Install the software to (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".

  2. 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
      
    
  3. Go to temp_dir and run the following command:

    7.5.0_PCM_SDK_platform_opt.bin
      
    

    where platform is the Linux.

    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.

  4. Go to BRM_SDK_Home 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:

  1. Go toBRM_SDK_Home/uninstaller/PCM_SDKdirectory.

  2. Run the following command:uninstaller.bin

Note:

The uninstallation does not uninstall any compiled PCM SDK policy files. Remove these files manually.

Installing Self-Care Manager

To use Self-Care Manager, you must also install a third-party application server:

To install Self-Care Manager:

  1. Install an Application Server:

    Supported application servers include Tomcat, WebLogic, and WebSphere. For more information, see the vendor installation documents for instructions on installing the application server.

  2. On the machine on which you have installed the application server, download the Self-Care Manager files by following the Installing Applications and Tools.

  3. 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 
      
    
  4. (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.
  5. Replace MAIN_CM_HOSTNAMEto your BRM system host.

  6. (Optional) Set MAIN_CM_PORTto your BRM system port number.

  7. Save and close the file.

  8. Run the following command:

    % ./install.ksh
      
    

    The application 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, test BRM with your business models: