Skip Headers
Oracle® Communications Billing and Revenue Management Installation Guide
Release 7.5

E16706-11
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

18 Installing Pipeline Manager

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

You should be familiar with the following topics:

Determining Your System Requirements

Before you install Pipeline Manager, ensure that requirements described in this section are met.

Supported Platforms

For information on supported platforms and required patches, see "BRM Software Compatibility".

Hardware Requirements

Pipeline Manager requires the following hardware listed in Table 18-1:

Table 18-1 Pipeline Manager Required Hardware

Component Requirements

CPU

4 or more CPUs

RAM

More than 4 GB (to use 54-bit)

Disk Type

RAID disc array (RAID 5 hardware solution with appropriate cache strongly recommended, RAID 0 software solution)


Note:

The more pipelines you configure and the more CPUs you use, the more important it is to put input and output on systems that are managed by different Controllers.

Third-Party Software Requirements

Table 18-2 describes the required third-party software.

Important:

These software components are not part of the Pipeline Manager package or license. You must obtain these products separately.

Table 18-2 Pipeline Manager Required Third-Party Components

Pipeline Manager Requirements Third-Party Component

Database server

(Oracle systems) Oracle 10g server, or 11g server

Database client

Oracle 10g or Oracle 11g (R1 or R2)

GUI server

Java Runtime Environment (JRE) 1.6.0_26


For required OS patch levels, see "BRM Software Compatibility".

Creating a User and Configuring Environment Variables

Follow these steps to create a Pipeline Manager user and set up system environment variables on a system:

  1. Create a user that owns the Pipeline Manager software. The examples in this document use the default user integrate with the bash shell as the default shell.

    Note:

    You must create a Pipeline Manager user and set the user's environment before installing Pipeline Manager.
  2. Log in as user integrate.

  3. Go to the Pipeline_home directory.

    Note:

    The default Pipeline_home directory is /opt/ifw.
  4. Open the source.me.sh file for your shell in a text editor.

    Note:

    The source.me file is for a bash shell. If you use a C shell, open the source.me.csh file.
  5. Set the following environment variables for Pipeline Manager using the information in Table 18-3:

    Table 18-3 Pipeline Manager Environment Variables

    Environment Variable Description

    IFW_EVENTHANDLER_PORT

    The port number on which the event handler daemon listens for events.

    Important:

    • If you are starting more than one framework process, change the value of this parameter before starting each process. Each process must have a unique event handler port for all users on a host. A framework process will not start if it cannot start the event handler daemon, and the event handler daemon will not start if it cannot listen on the specified port.

    • Do not set this variable to a well-known port number, such as port 11960 used by BRM.

    IFW_HOME

    The directory where the Pipeline Manager software is installed.

    The default installation directory for Pipeline Manager is /opt/ifw.

    Note: This documentation refers to this directory as the Pipeline_home.

    INT_PERL_LIB

    Set to THIRD_PARTY_SOFTWARE/tools/PerlLib, where THIRD_PARTY_SOFTWARE is the directory where you installed the Third-Party software. The default directory is /opt/portal/ThirdParty.

    LD_LIBRARY_PATH

    The library path.

    Set this to include Pipeline_home/lib.

    If your system already has this variable set to another value for other applications, Pipeline Manager might not find the proper libraries.

    To determine if a pre-existing value is present, enter the following command:

    echo $LD_LIBRARY_PATH 
    

    If the variable is already set in your system, add the new variable as follows:

    export LD_LIBRARY_PATH=${LD_LIBRARY_PATH};Pipeline_home/lib
    

    C shell:

    setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH};Pipeline_home/lib
    

    Important: After your first upgrade reset the LD_LIBRARY_PATH environment variable to the following:

    setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH};BRM_Home/lib;Pipeline_home/lib
    

    where BRM_Home/lib must come before Pipeline_home/lib, separated by a semicolon.

    LD_LIBRARY_PATH_64

    (Solaris)

    The library path.

    Set this to include Pipeline_home/lib.

    If your system already has this variable set to another value for other applications, Pipeline Manager might not find the proper 64-bit libraries.

    To determine if a pre-existing value is present, enter the following command:

    echo $LD_LIBRARY_PATH_64
    

    If the variable is already set in your system, add the new variable as follows:

    export LD_LIBRARY_PATH_64=${LD_LIBRARY_PATH_64};Pipeline_home/lib
    

    C shell:

    setenv LD_LIBRARY_PATH_64 ${LD_LIBRARY_PATH_64};Pipeline_home/lib
    

    LIBPATH

    (AIX)

    Set this to include Pipeline_home/lib.

    LD_PRELOAD_64

    (Solaris)

    A variable that can be used to configure libumem memory allocation. Set using the ifw-start script. See "libumem Memory Allocator".

    MALLOC_TRIM_THRESHOLD_

    MALLOC_MMAP_MAX_

    MALLOC_TOP_PAD_

    (Linux only)

    On Linux Pipeline Manager platforms, modify the MALLOC_TRIM_THRESHOLD_, MALLOC_MMAP_MAX_, and MALLOC_TOP_PAD_ environment variables with these values:

    • MALLOC_TRIM_THRESHOLD_ = -1

    • MALLOC_MMAP_MAX_ = 0

    • MALLOC_TOP_PAD_ = 268435456

    For more information on these variables, see the Linux documentation Web site (http://www.linux.com/learn/docs).

    _M_ARENA_OPTS

    _M_CACHE

    PTHREAD_SCOPE_SYSTEM

    (HP-UX only)

    On HP-UX IA64 Pipeline Manager platforms, modify the _M_ARENA_OPTS, _M_CACHE_OPTS, and PTHREAD_SCOPE_SYSTEM environment variables with these values:

    • _M_ARENA_OPTS = 32:4

    • _M_CACHE_OPTS = 40:12:1

    • PTHREAD_SCOPE_SYSTEM = 1

    Important: To achieve acceptable system performance:

    • You must set the _M_CACHE_OPTS environment variable.

    • Do not set the _M_SBA_OPTS environment variable.

    For more information on these variables, see the Hewlett-Packard documentation Web site (http://docs.hp.com/index.html).

    NLS_LANG

    Set this to LANG American_America.AL32UTF8.

    Important: You must use American_America as the language and territory regardless of your locale and the UTF8 or AL32UTF8 character set.

    BRM 7.5 supports AL32UTF8 as its default character set. It also continues to support the UTF8 character set for BRM installations that are being upgraded to BRM 7.5 from previous versions. The unicode character set AL32UTF8 is recommended for all new BRM 7.5 deployments.

    PATH

    The Pipeline Manager executable path.

    Set this to include Pipeline_home/bin.

    SHLIB_PATH

    (HP-UX IA64 only)

    The library path.

    Set this to include Pipeline_home/lib.

    IFW_EVENTHANDLER_PORT

    The port number on which the event handler daemon listens for events.

    Important:

    • If you are starting more than one framework process, change the value of this parameter before starting each process. Each process must have a unique event handler port for all users on a host. A framework process will not start if it cannot start the event handler daemon, and the event handler daemon will not start if it cannot listen on the specified port.

    • Do not set this variable to a well-known port number, such as port 11960 used by BRM.


  6. Save and close the updated file.

  7. Update the environment for the current shell session:

    For bash shell:

    source source.me.sh
      
    

    C shell:

    source source.me.csh
    

Setting the Maximum Allowed Number of Open Files

To avoid causing a failure of Pipeline Manager, you must configure the maximum number of pipeline files allowed per process in the kernel. The recommended value is 2048. You should also set the maximum number of open files allowed for the system to 20480 (ten times the number of files per process).

To modify the number of open files allowed:

(Linux) Setting Maximum Open Files on Linux

To set the maximum open files on Linux:

  1. Log on as root.

  2. Open the system file (/etc/sysctl.conf).

  3. Add the following lines to the end of the file, or modify the values if these lines are already present:

    # sets the hard limit on file descriptors:
    fs.file-max = 2605192
      
    
  4. Run sysctl -p to reload all the settings from the system file.

(Solaris) Setting Maximum Open Files on Solaris

To set the maximum open files on Solaris:

  1. Log on as root.

  2. Open the system file (/etc/system).

  3. Add the following lines to the end of the file, or modify the values if these lines are already present:

    * sets the hard limit on file descriptors:
    set rlim_fd_max = 20480
    * sets the soft limit on file descriptors:
    set rlim_fd_cur = 2048
      
    
  4. Restart your computer to enable the new kernel parameters.

(HP-UX IA64) Setting Maximum Open Files on HP-UX IA64

To set the maximum open files on HP-UX IA64:

  1. Log on as root.

  2. Enter the command to start the System Administration Manager (SAM) program. For example:

    /usr/bin/sam
      
    
  3. Double-click the Kernel Configuration icon.

  4. Double-click the Configurable Parameters icon.

  5. Double-click the maxfiles parameter and enter 2048 in the Formula/Value field.

  6. Double-click the nfiles parameter and enter 20480 in the Formula/Value field.

  7. Click OK.

  8. Select Actions - Process New Kernel from the menu bar.

  9. Restart your computer to enable the new kernel parameters.

(AIX) Setting Maximum Open Files on AIX

To set the maximum open files on AIX:

  1. Log on as root.

  2. Open the limits file (/etc/security/limits).

  3. Add the following lines to the end of the file, or modify the values if these lines are already present:

    * sets the hard limit on file descriptors:
    nofiles_hard = 20480
    * sets the soft limit on file descriptors:
    nofiles = 2048
      
    
  4. Restart any application in a new user session.

Installing Pipeline Manager

This section describes how to install and uninstall Pipeline Manager.

Important:

If you are installing Pipeline Manager to replace an identical release (for example, to restore a clean version of the package), you must first uninstall the existing installation. See "Uninstalling Pipeline Manager".

To install Pipeline Manager:

  1. Install the Third-Party software package:

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

    For Bash shell:

    source source.me.sh
      
    

    C shell:

    source source.me.csh
      
    
  3. Download the Pipeline Manager package to a temporary directory (temp_dir).

    See "Downloading the BRM Applications Media Pack".

    Important:

    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".
  4. Go to the temp_dir and enter this command:

    • For Solaris and Linux systems:

      7.5.0_Pipeline_platform_32_opt.bin
        
      

      where platform is solaris or linux.

    • For AIX systems:

      7.5PS1_Pipeline_aix_64_opt.bin
        
      
    • For HP-UX IA64 systems:

      7.5PS5_Pipeline_hpux_ia64_64_opt.bin
      

    Note:

    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 product. To ensure a command line installation starts, use the -console parameter.
  5. Follow the instructions displayed during installation.

    Note:

    If you do not specify the installation directory, Pipeline Manager is installed in the /opt/ifw directory.

Configuring the Registry File for Linux

If you installed Pipeline Manager on a Linux operating system, you must change the registry file's AccessLib entry to point to the correct database library.

To configure the registry file for Linux:

  1. Open your system's registry file in a text editor.

  2. Change all AccessLib entries to oci10g72. For example:

    AccessLib = oci10g72 
    

    Note:

    By default, the AccessLib entry is set to oci10g72.
  3. Save and close the file.

Uninstalling Pipeline Manager

To uninstall Pipeline Manager:

  1. Run the uninstaller.bin program from Pipeline_home/uninstaller/Pipeline.

  2. Delete the Pipeline_home/uninstaller directory and its contents.

Pipeline Manager Directory Structure

Installation creates the following directory structure shown in Table 18-4:

Note:

Pipeline_home is the default Pipeline Manager installation directory, /opt/ifw.

Table 18-4 Directory Structure Created by Pipeline Manager Installation

Directory Description

Pipeline_home/bin/

Server binaries, such as the main Pipeline Manager binary ifw.

Pipeline_home/conf/

Contains registry files.

Pipeline_home/data/

Contains source and directory files for EDRs.

Pipeline_home/database/

Database creation scripts and database documentation.

Pipeline_home/discount/

Balance Data Module transaction and data. See "DAT_BalanceBatch" in BRM Configuring Pipeline Rating and Discounting.

Pipeline_home/etc/

Error messages.

Note: You can copy the error messages to another directory and customize them; for example, as preparation for translation into other languages.

Pipeline_home/formatDesc/

External file format definitions and internal container definitions.

Pipeline_home/info/

Info registry, which shows the current system status.

Pipeline_home/instrumentation/

Performance Data collection.

Pipeline_home/iScriptLib/

iScript libraries.

Pipeline_home/lib/

Shared libraries.

Pipeline_home/lib64/

Shared libraries (64-bit)

Pipeline_home/log/

Process log.

Pipeline_home/releaseNotes/

Release notes.

Pipeline_home/samples/

Sample registries that you can use for testing your Pipeline Manager setup.

Pipeline_home/semaphore/

Directory that is checked regularly for semaphores.

Pipeline_home/tam/

 

Pipeline_home/tools/

The tools such as binaries and Perl scripts.


Installing Pipeline Configuration Manager

This section describes how to install Pipeline Configuration Manager.

For information about Pipeline Configuration Manager, see "About Pipeline Configuration Manager".

Note:

Pipeline Configuration Manager is available for the HP-UX IA64, Linux, Solaris, and AIX operating systems.

Important:

If you are installing Pipeline Configuration Manager to replace an identical release (for example, to restore a clean version of the package), you must first uninstall the existing installation. See "Uninstalling Pipeline Configuration Manager".

Before installing Pipeline Configuration Manager, you must install:

To install Pipeline Configuration Manager:

  1. If the Third-Party software package is not installed, install it.

    See "Installing the Third-Party Software".

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

    source source.me.sh
      
    

    C shell:

    source source.me.csh
      
    
  3. Download the software to a temporary directory (temp_dir).

    Important:

    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".
  4. Go to temp_dir and enter the following command:

    7.5.0_Pipeline_ConfMgr_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.
  5. Follow the instructions displayed during installation.

    Note:

    If you do not specify an installation directory, Pipeline Configuration Manager is installed in the /opt/ifw directory.

Uninstalling Pipeline Configuration Manager

To uninstall Pipeline Configuration Manager, run the uninstaller.bin program from Pipeline_home/uninstaller/Pipeline_ConfMgr.

Installing Roaming Settlement Package

This section describes how to install Roaming Settlement Package.

For information about managing settlement for roaming charges, see "About Managing Settlement for Interconnect Charges" in BRM Configuring Roaming in Pipeline Manager.

The hardware and software requirements for Roaming Settlement Package are the same as for Pipeline Manager. For more information, see "Installing Pipeline Manager". In addition to this, install BRM before proceeding.

The Roaming Settlement Package includes the utility and template files for extracting settlement data from the pipeline database and loading it into the BRM database. It also includes the files needed to load SMS settlement data, which is used to generate SMS settlement reports. For information about SMS settlement reports, see "About Generating SMS Usage Reports" in BRM Configuring Roaming in Pipeline Manager.

To install Roaming Settlement Package, see "Installing Roaming Settlement Package".

Installing Roaming Settlement Package

Note:

If you have already installed the feature, features that are already installed cannot be reinstalled without uninstalling them first. To reinstall a feature, uninstall it and then install it again.
  1. 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".

  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 the temp_dir directory and enter this command:

    7.5.0_SMSSettlement_Reports_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.
  4. When prompted, enter the directory where you want to install the roaming settlements package.

    The default directory is opt/portal/7.5.

    The installation program installs the package files in the specified directory.

  5. Go to the directory where you installed the roaming settlements package and source the source.me file:

    Bash shell:

    source source.me.sh
      
    

    C shell:

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

Your Roaming Settlement Package installation is now complete.

Increasing Heap Size to Avoid ”Out of Memory” Error Messages

To avoid "Out of Memory" error messages in the log file after installation, increase the maximum heap size used by the Java Virtual Machine (JVM). The exact amount varies greatly with your needs and system resources. By default, the JVM used has a maximum heap size of 60 MB. Increase the maximum heap size to 120 MB by entering the following sample code in a text editor:

%IF_EXISTS%("INIT_JAVA_HEAP", "@INIT_JAVA_HEAP@20m") %IF_EXISTS%("MAX_JAVA_HEAP", "@MAX_JAVA_HEAP@120m")
  

where 20m and 120m indicate the minimum and maximum heap sizes respectively.

Save the file as Packagename.ja in the temporary directory (temp_dir) to which you downloaded the installation software.

Packagename indicates the name of the installation software. For example, if you downloaded the 7.5.0_Pipeline_solaris_64_opt.bin file on Solaris then, save the file as 7.5.0_Pipeline_solaris_64_opt.ja.

Configuring an Oracle Pipeline Manager Database

This section describes how to configure the Pipeline Manager database on Oracle.

Before proceeding, you should be familiar with executing database scripts.

Before setting up the Oracle database for Pipeline Manager, ensure the following:

  • An Oracle database instance is mounted and open.

  • You have administrator access to the database instance.

To install and configure the Pipeline Manager database, follow the steps in these sections:

  1. Setting the Environment for the Pipeline Manager Database

  2. Setting Up the Oracle JSA Database Schema

  3. Setting Up the Oracle Pipeline Manager Framework Database Schema

  4. Loading Procedures for FCT_DuplicateCheck

  5. Encrypting the Database Password

  6. (Solaris) Configuring Memory Allocation and Block Transfer Mode on Solaris Systems

  7. Loading the Tailor-Made Stored Procedure

  8. Loading the Discount Stored Procedure

Setting the Environment for the Pipeline Manager Database

Before setting up the database schemas for your Oracle Pipeline Manager database, you must configure database environment variables.

  1. Open the configuration file for the login shell. This is the file in which your user profile is stored; for example, .profile or .bashrc. By default it is stored in your home directory.

  2. Change the following variables in Table 18-5 to match your Pipeline Manager environment:

    Table 18-5 Environment Variables of Pipeline Manager Database

    Environment Variable Description

    ORACLE_HOME

    (for Oracle databases only)

    Include or set this variable to point to the Oracle installation path.

    LD_LIBRARY_PATH

    (32-bit systems) Include or set entries to point to the database /lib directories.

    Example for Oracle databases:

    LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib32:$ORACLE_HOME/rdbms/lib32
    

    LD_LIBRARY_PATH_64

    (64-bit systems) Include or set entries to point to the database /lib directories.

    Example for Oracle databases:

    LD_LIBRARY_PATH_64=$IFW_HOME/lib:$ORACLE_HOME/lib:$ORACLE_HOME/rdbms/lib
    

    PATH

    Include or set entries to point to the database /bin directory.

    Example for Oracle databases:

    ${ORACLE_HOME}/bin
    

  3. Save and close the file.

Setting Up the Oracle JSA Database Schema

This section describes how to run scripts to set up the Oracle JSA database schema.

Run the scripts described in the following steps to set up the database schema for the JSA tables and tablespaces:

Note:

All scripts are located in the Pipeline_home/database/Oracle/Scripts directory.
  1. Open the JSA_Tablespaces.sql file with a text editor.

  2. Replace all occurrences of the string *** with the path to the Oracle tablespace data file.

  3. Save the file.

  4. Log in as user database administration (DBA).

  5. Run the JSA_Tablespaces.sql script.

    This script creates the tablespaces for the JSA server.

  6. Run the JSA_Roles.sql script.

    This script creates roles and the default JSA user.

  7. Log out and log in as user JSA.

  8. Run the JSA_Create.sql script.

    This script creates the JSA tables.

  9. Run the JSA_Synonyms.sql script.

    This script creates the JSA public synonyms.

  10. Run the JSA_Prepare.sql script.

    This script inserts some default values into the tables.

The Oracle JSQ database schema is now set up.

Setting Up the Oracle Pipeline Manager Framework Database Schema

To set up the database schema for the Pipeline Manager framework work tables and tablespaces:

Note:

All scripts are located in the Pipeline_home/database/Oracle/Scripts directory.
  1. Open the ifw_Tablespaces.sql file with a text editor.

  2. Replace the occurrences of the string ORA_DAT_PATH and ORA_IDX_PATH with the path that leads to the *.dbf files shown in the script file.

  3. Save the file.

  4. Log in as user DBA.

  5. Run the ifw_Tablespaces.sql script.

    This script creates the tablespaces for the Pipeline Manager framework.

  6. (Optional) Change the default Pipeline Manager user name (pipeline_user) from integrate to another name:

    1. Open the ifw_Roles.sql file by using a text editor.

    2. In the User: INTEGRATE section, replace the two occurrences of INTEGRATE in the following string with the new default user name:

      INTEGRATE identified by INTEGRATE
        
      
    3. In the GRANT commands that follows the QUOTA commands in the User: INTEGRATE section, replace all occurrences of INTEGRATE with the new default user name.

    4. Save the file.

  7. Run the ifw_Roles.sql script.

    This script creates the appropriate roles and the default user.

  8. Log out and log in as pipeline_user.

  9. Run the ifw_Create.sql script.

    This script creates the Pipeline Manager framework tables.

  10. Run the ifw_Synonyms.sql script.

    This script creates the public synonyms.

The Oracle Pipeline Manager framework database schema is now set up.

You can create only one instance of the pipeline schema in a particular database. You can create multiple users and give permission to access the same tables. Creating multiple instances lead to public synonym conflict.

To avoid public synonym conflicts in a multiuser environment, change the public synonyms to private synonyms for specific users. See "Changing Public Synonyms to Private for Users in Multiuser Environments" for more information.

For example, if you create table1 for user1, you can create user2 and assign permissions to access table1. Typically, you access the table as user1.table1. However, using synonyms, you can directly access the table as table1. No prefix (user1) is required.

Changing Public Synonyms to Private for Users in Multiuser Environments

Changing public synonyms to private synonyms for a user is required for avoiding public synonym conflict in a multiuser environment.

Note:

All scripts are located in the Pipeline_Home/database/Oracle/Scripts directory

To change public synonyms to private synonyms for a user:

  1. Connect to the Oracle database with SQL*Plus:

    % sqlplus system/manager@databaseAlias
      
    

    where databaseAlias is the database alias of the Oracle database.

  2. Drop the public synonyms for IFW tables for the user.

  3. Grant CREATE ANY synonym access to the user you created for the Pipeline Manager tables. For example:

    SQL>CREATE ROLE synonym_role;
    SQL>GRANT CREATE ANY SYNONYM TO synonym_role;
    SQL>GRANT synonym_role TO pin_user;
      
    

    where pin_user is the BRM user.

  4. Open the ifw_Synonyms.sql file with a text editor.

  5. Remove the occurrences of the string public and add the Pipeline Manager database user. For example, for ifw_SEQ_AGGREGATION table, change the string to:

    create synonym ifw_SEQ_AGGREGATION for ifw_user.ifw_SEQ_AGGREGATION;
      
    

    where ifw_user is the is the Pipeline Manager database user.

  6. Save the file.

  7. Run the ifw_Synonyms.sql script.

    This script creates the private synonyms for the user.

  8. Exit SQL*Plus.

The public synonyms are now changed to private synonyms for the user.

Loading Procedures for FCT_DuplicateCheck

Before using the FCT_DuplicateCheck module, you must load the duplicate check stored procedures in the Pipeline Manager database:

  1. Load the DuplicateCheck_Oracle.plb file from Pipeline_home/database/Oracle/Scripts/DuplicateCheck.

  2. Verify that there is an unique index BIDX_DUPCHK_DATA on the DATA column of the IFW_DUPLICATECHECK table. If not, then create it before starting Pipeline Manager.

The duplicate check stored procedures are now loaded.

Encrypting the Database Password

If your database is encrypted with the MD5 format, use the pin_crypt_upgrade utility to migrate your data to the AES encryption scheme, and then use the pin_crypt_app utility to encrypt the Pipeline Manager password. For information about these utilities, see "pin_crypt_upgrade" and "pin_crypt_app" in BRM Developer's Guide.

For information on updating your encryption scheme, see "Migrating Data from MD5 to AES Encryption" in BRM Developer's Guide.

For information on encryption, see "About Encrypting Information" in BRM Developer's Guide.

  1. Go to the BRM_Home/bin directory.

  2. Run the pin_crypt_app utility with the enc parameter, and specify the plaintext password:

    pin_crypt_app -enc Plaintext_password
      
    

    The output is the AES tag followed by a vertical bar and the encrypted password. For example:

    &aes|0D5E11BFDD97D2769D9B0DBFBD1BBF7EE03F1642861DFA57502C7FB85A654267
      
    
  3. Write down the encrypted password or copy it to a text editor.

  4. Open the Pipeline Manager startup registry file.

  5. In the DataPool section, enter the user name, encrypted password, and database name.

    For example:

    UserName     = INTEGRATOR
    PassWord     = &aes|0D5E11BFDD97D2769D9B0DBFBD1BBF7EE03F1642861DFA57502C7FB85A654267
    DatabaseName = IFWDB
    

    Important:

    Be sure that these lines are not commented. (The default is commented.)
  6. Save the registry file.

(Solaris) Configuring Memory Allocation and Block Transfer Mode on Solaris Systems

If you run Pipeline Manager on the Solaris platform, configure the following:

libumem Memory Allocator

By default, the Hoard memory allocator is used on Solaris systems. If you run Pipeline Manager on Solaris 9, you might achieve better performance by using the libumem memory allocator.

To enable the libumem memory allocator, edit the ifw-script file (ifw-start.sh or ifw-start.csh, depending on your system needs) to set the LD_PRELOAD_64 environment variable to /usr/lib/sparcv9/libumem.so.1 and to change the executable from ifw to ifw_nomalloc as shown in the following examples:

For the ifw-start.sh file, change:

. /opt/ifw/source.me.sh
ifw $*
  

To the following:

export LD_PRELOAD_64=/usr/lib/sparcv9/libumem.so.1
. /opt/ifw/source.me.sh
ifw_nomalloc $*
  

For the ifw-start.csh file, change:

source /opt/ifw/source.me.csh
ifw $*
  

To the following:

setenv LD_PRELOAD_64=usr/lib/sparcv9/libumem.so.1
source /opt/ifw/source.me.csh
ifw_nomalloc $*

Block Transfer Mode

On Solaris systems, you should set up Pipeline Manager buffers to function in block transfer mode. This mode addresses performance and scalability issues that occur when two or more threads are accessing the same buffer (thread contention).

When buffers operate in block transfer mode, EDR blocks of a configurable size are transferred simultaneously between the threads. If, for example, the block size is set to 100, concurrent buffer access is reduced to 1/100 of the number without the block transfer mode.

Specifying Block Transfer Mode and Block Size

To specify block transfer mode and block size, set the values in the registry files as shown in the following example:

Buffer 
{ 
  Size = 4000
  BlockTransfer = TRUE    # Optional, defaults to FALSE
  BlockSize = 500         # Only needed when BlockTransfer = TRUE
} 
  

This example specifies a buffer size of 4000 and a block size of 500. Up to eight (4000/500) blocks can be in the buffer.

Loading the Tailor-Made Stored Procedure

Loading of the stored procedure is required for the Tailor-Made Plan feature.

The following are the requirements to load the tailor-made stored procedure:

  • BRM and Pipeline Manager should be installed.

  • The BRM schema and the Pipeline Manager schema should reside on the same database.

To load the stored procedure, do the following:

  1. Connect to the Oracle database with SQL*Plus:

    % sqlplus system/manager@databaseAlias
      
    
  2. Grant access of pipeline schema to user pin by doing the following:

    1. Run the SQL grant select, update, insert, delete commands on the Pipeline Manager tables.

      For example, for the ifw_rateplan table, run the command:

      SQL> grant select, update, insert, delete on ifw_rateplan to pin;
        
      

      Run the command on the following tables:

      • ifw_rateplan

      • ifw_rateplan_cnf

      • ifw_rateplan_ver

      • ifw_model_selector

      • ifw_selector_detail

      • ifw_selector_rule

      • ifw_selector_rule_lnk

      • ifw_selector_ruleset

      • ifw_pricemodel

      • ifw_pricemdl_step

    2. Run the SQL grant select commands on the Pipeline Manager tables mentioned below.

      For example, for the ifw_service table, run the command:

      SQL> grant select on ifw_service to pin;
        
      

      Run the command on the following tables:

      • ifw_service

      • ifw_timezone

      • ifw_timemodel

      • ifw_impact_cat

      • ifw_zonemodel

      • ifw_calendar

    3. Run the SQL grant select commands on the Pipeline Manager sequences.

      For example, for the ifw_seq_selectordetail sequence, run the command:

      SQL> grant select ifw_seq_selectordetail to pin;
        
      

      Run the command on the following tables:

      • ifw_seq_selectordetail

      • ifw_seq_selectorrule

      • ifw_seq_modelselector

      • ifw_seq_pricemodel

      • ifw_seq_rateplan

  3. Type exit to exit SQL*Plus.

  4. Go to the ifw/database/Oracle/Scripts directory.

  5. Enter this command to open SQL*Plus:

    sqlplus pin/pin@database_Name
      
    

    Where database_Name is the service name or database alias of the Oracle database.

  6. Enter this command to load the stored procedure:

    SQL>@create_pricing_tailormadeplan_procedures.plb
      
    
  7. Type exit to exit SQL*Plus.

Loading the Discount Stored Procedure

Loading of the stored procedure is required for discount configuration.

The following are the requirements to load the discount stored procedure:

  • BRM and Pipeline Manager should be installed.

  • The BRM schema and the Pipeline Manager schema should reside on the same database.

To load the stored procedure, do the following:

  1. Connect to the Oracle database with SQL*Plus:

    % sqlplus system/manager@databaseAlias
      
    
  2. Grant access of pipeline schema to user pin by doing the following:

    1. Run the SQL grant select, update, insert, delete commands on the Pipeline Manager tables.

      For example, for the ifw_discountmodel table, run the command:

      SQL> grant select, update, insert, delete on ifw_discountmodel to pin;
        
      

      Run the command on the following tables:

      • ifw_discountmodel

      • ifw_dscmdl_ver

      • ifw_dscmdl_cnf

      • ifw_dsctrigger

      • ifw_dsccondition

      • ifw_discountrule

      • ifw_discountstep

      • ifw_dscbalimpact

      • ifw_discountmaster

      • ifw_discountdetail

    2. Run the SQL grant select commands on the Pipeline Manager sequences.

      For example, for the ifw_seq_discountmodel sequence, run the command:

      SQL> grant select ifw_seq_discountmodel to pin;
        
      

      Run the command on the following tables:

      • ifw_seq_discountmodel

      • ifw_seq_discountconfig

      • ifw_seq_discounttrigger

      • ifw_seq_discountcondition

      • ifw_seq_discountrule

      • ifw_seq_discountstep

      • ifw_seq_discountbalimpact

      • ifw_seq_discountmaster

  3. Type exit to exit SQL*Plus.

  4. Go to the ifw/database/Oracle/Scripts directory.

  5. Enter this command to open SQL*Plus:

    sqlplus pin/pin@database_Name
      
    

    Where database_Name is the service name or database alias of the Oracle database.

  6. Enter this command to load the stored procedure:

    SQL>@create_pricing_discountmodel_procedures.plb
      
    
  7. Type exit to exit SQL*Plus.

What's Next?

To test your installation, you can use Pipeline Configuration Manager to configure pipelines and load sample data into the Pipeline Manager database. See "About Pipeline Configuration Manager".