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

E28198-10
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
PDF · Mobi · ePub

1 Installing BRM 7.5 Patch Set 10

This chapter describes how to install and uninstall Oracle Communications Billing and Revenue Management (BRM) 7.5 Patch Set 10 on top of a base BRM 7.5 system.

About the Patch Set

Important:

Be sure to test the patch on a non-production system before you deploy it on a production system.

BRM 7.5 Patch Set 10 is a patch that must be applied to the following:

  • BRM 7.5

  • Pipeline Manager

Important:

Before installing BRM 7.5 Patch Set 10, you must have either BRM 7.5 or BRM 7.5 Patch Set 1 or later installed on your system.

Note:

If you are upgrading to BRM 7.5 Patch Set 10 from BRM 7.4, you must first upgrade to BRM 7.5. For more information, see "Upgrading from BRM 7.4 to the BRM 7.5 Patch Set".

Note:

BRM 7.5 Patch Set 10 is cumulative from BRM 7.5 Patch Set 1 and includes all the changes introduced since Patch Set 1.

The patch is available for Oracle Linux, AIX, HP-UX IA64, and Oracle Solaris operating systems.

The patch contains multiple packages to upgrade different BRM and Pipeline Manager components. You can upgrade the following components by installing their corresponding packages:

  • BRM

  • BRM SDK

  • Pipeline Manager

Only files that have been changed are updated. The patch installer makes a backup of any file it updates. You use the backup files to merge your customizations and to uninstall the patch. The prepatch version of each updated file (FileName) is renamed to FileName.PatchNumber.bak and is left in its original directory. For example, when you install BRM 7.5 Patch Set 10 to upgrade Pipeline Manager, the existing sample.reg file is renamed to sample.reg.19678435.bak.

Installing the Patch Set

Caution:

When upgrading a multischema system, pay close attention to the system on which each task is performed.

Perform the following tasks on your BRM system to install BRM 7.5 Patch Set 10:

  1. Shutting Down the Current Instance

  2. Backing Up Files

  3. Backing Up TAP 3.11 Files

  4. Backing Up Your BRM Database

  5. Backing Up Your Pipeline Manager Database

  6. Installing Java Runtime Environment 1.7

  7. Installing Solaris Patches

  8. Installing the Required 32-Bit Libraries for Oracle Linux 6 Update 3

  9. Installing the Patch

  10. Creating Local Indexes on Table Partitions

  11. Upgrading the BRM Database Schema

  12. Upgrading the Pipeline Manager Database Schema

  13. Adding Customizations

Shutting Down the Current Instance

Important:

In multischema systems, all BRM instances must be shut down.

To shut down BRM:

  1. Ensure that no users are logged in.

    Users include customers, client applications, customer service representatives (CSRs), and so on.

  2. Stop all BRM processes.

    Only the database instances should be running during the patch installation. For more information, see the discussion about starting and stopping the BRM system in BRM System Administrator's Guide.

Backing Up Files

Important:

In multischema systems, perform this task first on the primary BRM installation machine and then on the secondary BRM installation machines.

Back up your BRM files. In particular, make sure you back up all customized files, including source code, policy, start_all, pin.conf, pin_ctl.conf, pin_setup.values, and Infranet.properties files.

Backing Up TAP 3.11 Files

If you want TAP Roaming Manager to process both TAP 3.11 (Transferred Account Procedure Number 3 version 11) TD57 specifications version 28 and TAP 3.12 GSM TD57 specifications version 32.1:

  1. Go to the TAP 3.11 installation directory.

  2. Copy and rename each of the files listed in Table 1-1:

    Note:

    This installation uses the extension _0311 in renaming the copies of the required files to associate them with the TAP 3.11 version to which they belong. This naming convention will be used when updating the roaming.reg file with registry configuration appropriate for the processing of TAP 3.11 roaming usage events.

    If you choose a different naming structure, make sure that the roaming.reg file is updated to reflect that naming structure for proper processing of TAP 3.11 roaming usage events.

    Table 1-1 New Names for TAP 3.11 Files Requiring Backup

    Old File Name New File Name

    RAP_0105_AckOutGrammar.dsc

    RAP_0105_AckOutGrammar_0311.dsc

    RAP_0105_FatalReturn.dsc

    RAP_0105_FatalReturn_0311.dsc

    RAP_0105_InGrammar.dsc

    RAP_0105_InGrammar_0311.dsc

    RAP_0105_MissingReturn.dsc

    RAP_0105_MissingReturn_0311.dsc

    RAP_0105_OutGrammar.dsc

    RAP_0105_OutGrammar_0311.dsc

    RAP_0105_StopReturn.dsc

    RAP_0105_StopReturn_0311.dsc

    containerDesc.dsc

    containerDesc_0311.dsc


After installing the patch, configure your registry file to use both TAP 3.11 and TAP 3.12. See the discussion about setting up TAP Roaming Manager to process TAP 3.11 files in BRM Configuring Roaming in Pipeline Manager for more information.

Backing Up Your BRM Database

Important:

In multischema systems, perform this task first on the primary database schema and then on the secondary database schemas.

Make a complete offline backup of your BRM database using the appropriate backup tools for your database version and ensure that the backup is completely valid and usable. The backup must contain both the database definition and all the database contents. See your database software documentation for more information on performing full database backups.

Important:

Store this backup in a safe location. The data in these files will become necessary if you encounter any issues in the upgrade process.

Backing Up Your Pipeline Manager Database

Important:

In multischema systems, perform this task first on the primary database schema and then on the secondary database schemas.

Make a complete offline backup of your Pipeline Manager database using the appropriate backup tools for your database version and ensure that the backup is completely valid and usable. The backup must contain both the database definition and all the database contents. See your database software documentation for more information on performing full database backups.

Important:

Store this backup in a safe location. The data in these files will become necessary if you encounter any issues in the upgrade process.

Installing Java Runtime Environment 1.7

Install the latest version of Java Runtime Environment (JRE) 1.7 on the following systems:

  • The system on which the BRM server is installed

  • Each Windows system on which the BRM client application is installed

To verify the JRE version:

  1. Go to the command prompt on the system on which the BRM server or the BRM client application is installed.

  2. Run the following command:

    java -version
    

    The Java version is displayed. For example:

    java version "1.7.0_13"
    

    If the version displayed does not start with 1.7.0_, JRE 1.7 is not installed.

For information about installing JRE, see the Oracle Java documentation.

Installing Solaris Patches

If BRM is installed on a Solaris server, install the 148198-03 for SPARC patch on that server.

To install the 148198-03 for SPARC patch on Solaris:

  1. On the Solaris server on which BRM is installed, run the following command:

    showrev -p
    

    All the patches that are installed on the server are listed.

  2. If the 148198-03 for SPARC patch is not listed, download and install the 148198-03 for SPARC patch from the My Oracle Support Web site:

    http://support.oracle.com

    For more information about installing the Solaris patches, see the Oracle Solaris documentation.

Installing the Required 32-Bit Libraries for Oracle Linux 6 Update 3

If BRM is installed on an Oracle Linux 6 Update 3 server, install the required 32-bit libraries for Oracle Linux 6 Update 3 on that server.

To install the required 32-bit libraries for Oracle Linux 6 Update 3:

  1. Go to the command prompt on the Oracle Linux 6 Update 3 server on which BRM is installed.

  2. Run the following commands:

    yum -y install glibc.i686
    yum -y install glibc-devel.i686
    yum -y upgrade libXext
    yum -y install libXext.i686
    yum -y upgrade libXtst
    yum -y install libXtst.i686
    yum -y upgrade libgcc
    yum -y install libgcc.i686
    yum -y upgrade libstdc++
    yum -y install libstdc++.i686
    yum -y install libaio.i686
    

    Note:

    If you use a proxy server as an intermediary for Internet access, configure a proxy server to access the yum repository. See http://docs.oracle.com/cd/E37670_01/E37355/html/ol_yum_config.html#ol_proxy_config.

    For more information about installing the 32-bit libraries for Oracle Linux 6 Update 3, see the Oracle Linux 6 documentation.

Installing the Patch

Important:

In multischema systems, perform this task first on the primary BRM installation machine and then on the secondary BRM installation machines.

If the optional components that you require are not installed, you must install the optional managers before installing the BRM 7.5 patch.

To install the patch:

  1. Create a temporary directory (temp_dir).

  2. Go to the My Oracle Support Web site:

    http://support.oracle.com

  3. Sign in with your user name and password.

  4. Click the Patches & Updates tab.

  5. From the list, select Patch Name or Number.

  6. In the text field, enter 19678435 and click Search.

    The Patch Search Results page appears.

  7. Click the patch name.

    The patch details appear.

  8. From the Platform list, select the platform and click Download.

    The File Download dialog box appears.

  9. Download the appropriate p19678435_750_platform.zip software pack to temp_dir, where platform is linux, aix, hpux_ia64, or solaris.

  10. Unzip the p19678435_750_platform.zip file.

  11. Install the Third-Party software by doing the following:

    1. Go to temp_dir and run the following command:

      7.5PS10_ThirdParty_platform_32_opt.bin -console
      

      where platform is linux, aix, hpux_ia64, or solaris.

    2. When prompted, enter the path to the Third-party_Home directory, where Third-party_Home is the directory in which the Third-Party software is installed.

    3. Follow the instructions displayed during installation.

      The latest supported versions of Perl and Remote Diagnostic Agent (RDA) are installed and the corresponding files in the Third-party_Home/tools directory are replaced. For detailed information on supported versions, see the discussion about BRM software compatibility in BRM Installation Guide.

    4. Go to BRM_Home and source the source.me file, where BRM_Home is the directory in which you installed BRM:

      Bash shell:

      source source.me.sh 
      

      C shell:

      source source.me.csh 
      
  12. Go to temp_dir and run the following command, which installs the patch software:

    PatchPackageName.bin -console
    

    where PatchPackageName is:

    • 7.5PS10_19678435_Portal_Base_platform_opt for upgrading BRM plus any BRM optional components installed on your system.

    • 7.5PS10_19678435_Portal_SDK_platform_opt for upgrading the BRM SDK.

    • 7.5PS10_19678435_Pipeline_platform_opt for upgrading Pipeline Manager.

    where platform is linux, aix, hpux_ia64, or solaris.

  13. Follow the instructions displayed during installation.

  14. Run the following command, which installs the database upgrade package:

    PatchPackageName.bin -console
    

    where PatchPackageName is:

    • 7.5PS10_PortalBase_Upgrade_75_75PS_platform_32_opt for upgrading the BRM patch set database schema plus the database schema for any BRM optional components installed on your system.

    • 7.5PS10_Pipeline_Upgrade_75_75PS_platform_32_opt for upgrading the Pipeline Manager patch set database schema.

    where platform is linux, aix, hpux_ia64, or solaris.

  15. Follow the instructions displayed during installation.

Important:

With BRM 7.5 Patch Set 10, the OpenSSL software is no longer part of the BRM patch set installation package. Installing this patch set removes the OpenSSL libraries that were installed by the previous patch sets. For BRM, Oracle recommends that you use the OpenSSL software bundled with the host operating system. Ensure that the latest version of the OpenSSL software is installed for your operating system.

Creating Local Indexes on Table Partitions

Note:

In multischema systems, perform this task first on the primary BRM installation machine and then on the secondary BRM installation machines.

To create local indexes on all the existing event and non-event table partitions:

  1. Open the BRM_Home/setup/scripts/pin_tables.values file in a text editor.

  2. Search the file for the following line:

    $PIN_CONF_PARTITION_IND = "local (partition partition_historic,"."partition partition_last)";
    
  3. Change the value to local:

    $PIN_CONF_PARTITION_IND = "local";
    
  4. Search the file for the following line:

    $PIN_CONF_NON_EVENT_PARTITION_IND = "local (partition partition_last)";
    
  5. Change the value to local:

    $PIN_CONF_NON_EVENT_PARTITION_IND = "local";
    
  6. Save and close the file.

Upgrading the BRM Database Schema

If the optional components are not installed, the database objects associated with these optional components are not created or updated.

If Oracle In-Memory Database (IMDB) Cache is installed, see "Upgrading the BRM Cache Groups Schema in IMDB Cache".

To upgrade the BRM database schema, perform one of the following procedures:

Upgrading the Schema on Single-Schema Systems

To upgrade the schema on single-schema systems:

  1. Open the BRM_Home/sys/dm_oracle/pin.conf file in a text editor.

  2. Uncomment the following entry:

    - crypt md5| ${PIN_HOME}/lib/${LIBRARYPREFIX}pin_crypt4dm64${LIBRARYEXTENSION} "Abracadabra dabracaabrA" 
    
  3. Save and close the file.

  4. Open the BRM_Home/setup/pin_setup.values file in a text editor.

  5. (Optional) Set the values of the following parameters:

    • Set PIN_TEMP_DIR to the directory in which you want to create the temporary files. Ensure that the directory has full write permissions.

    • Set PIN_LOG_DIR to the directory in which you want to create the BRM log files.

  6. In the Information about the CM section, add the following text:

    $MAIN_CM{'pcm_admin_passwd'} = "&aes|08|0D5E11BFDD97D2769D9B0DBFBD1BBF7E5D40C305EDF3D77DF111AAB8F781E92122";
    

    The password that is used by the load utilities to connect to the Connection Manager (CM) is reset to the default password.

  7. In the Information about the databases section, configure the database settings as required.

  8. Set SETUP_INIT_DB to YES, if it is not set.

  9. Save and close the file.

  10. Go to BRM_Home and source the source.me file:

    • Bash shell:

      source source.me.sh 
      
    • C shell:

      source source.me.csh 
      
  11. Run the pin_75_75ps10_upgrade.pl script from the UNIX prompt:

    cd BRM_Home/setup/scripts
    pin_75_75ps10_upgrade.pl
    
  12. Merge the contents of the backed up pin_ctl.conf file into the new pin_ctl.conf file.

Upgrading the Schema on Multischema Systems

To upgrade the schema on multischema systems:

  1. On the primary BRM installation machine, do the following:

    1. Open the BRM_Home/sys/dm_oracle/pin.conf file in a text editor.

    2. Uncomment the following entry:

      - crypt md5| ${PIN_HOME}/lib/${LIBRARYPREFIX}pin_crypt4dm64${LIBRARYEXTENSION} "Abracadabra dabracaabrA" 
      
    3. Save and close the file.

    4. Open the BRM_Home/setup/pin_setup.values file in a text editor.

    5. (Optional) Set the values of the following parameters:

      Set PIN_TEMP_DIR to the directory in which you want to create the temporary files.

      Set PIN_LOG_DIR to the directory in which you want to create the BRM log files.

    6. In the Information about the CM section, add the following text:

      $MAIN_CM{'pcm_admin_passwd'} = "&aes|08|0D5E11BFDD97D2769D9B0DBFBD1BBF7E5D40C305EDF3D77DF111AAB8F781E92122";
      

      The password that is used by the load utilities to connect to the CM is reset to the default password.

    7. In the Information about the databases section, configure the database settings for your primary database schema.

    8. Set SETUP_INIT_DB to YES, if it is not set.

    9. Save and close the file.

    10. Go to BRM_Home and source the source.me file:

      Bash shell:

      source source.me.sh 
      

      C shell:

      source source.me.csh 
      
    11. Run the install.sh script:

      cd BRM_Home/apps/multi_db
      ./install.sh
       
      

      Follow the on-screen instructions, entering the following information for the primary schema and for each secondary schema when requested:

      – Schema user name

      – Schema password

      – Schema SID (the BRM database alias of the schema)

      Important:

      Repeat the "Do you have secondary schema to process" step for each secondary schema in your system.

      The install script fixes any data errors caused by conflicting storable class IDs. The errors might have occurred during global (XA) transactions involving multiple schemas or when accounts were migrated from one schema to another.

      Note:

      As the install script runs, it generates the BRM_Home/apps/multi_db/fix_multi_schema.log file. To view the progress of the script, display the log file in a different console window.
    12. Run the pin_75_75ps10_upgrade.pl script from the UNIX prompt:

      cd BRM_Home/setup/scripts
      pin_75_75ps10_upgrade.pl
      
    13. Merge the contents of the backed up pin_ctl.conf file into the new pin_ctl.conf file.

  2. On each secondary BRM installation machine, do the following:

    1. Open the BRM_Home/sys/dm_oracle/pin.conf file in a text editor.

    2. Uncomment the following entry:

      - crypt md5| ${PIN_HOME}/lib/${LIBRARYPREFIX}pin_crypt4dm64${LIBRARYEXTENSION} "Abracadabra dabracaabrA" 
      
    3. Save and close the file.

    4. Open the BRM_Home/setup/pin_setup.values file in a text editor.

    5. In the Information about the CM section, add the following text:

      $MAIN_CM{'pcm_admin_passwd'} = "&aes|08|0D5E11BFDD97D2769D9B0DBFBD1BBF7E5D40C305EDF3D77DF111AAB8F781E92122";
      

      The password that is used by the load utilities to connect to the CM is reset to the default password.

    6. Change the $DM_ORACLE{’db_num'} entry, where db_num is the number of the corresponding secondary database schema to upgrade.

    7. Configure the database settings as required.

    8. Set SETUP_INIT_DB to YES, if it is not set.

    9. Save and close the file.

    10. Go to BRM_Home and source the source.me file:

      Bash shell:

      source source.me.sh 
      

      C shell:

      source source.me.csh 
      
    11. Run the pin_75_75ps10_upgrade.pl script from the UNIX prompt:

      cd BRM_Home/setup/scripts
      pin_75_75ps10_upgrade.pl
      
    12. Merge the contents of the backed up pin_ctl.conf file into the new pin_ctl.conf file.

  3. On the primary BRM installation machine, do the following:

    1. Go to the BRM_Home/setup/scripts directory.

    2. Run the following command:

      pin_multidb.pl -i
      
    3. At the following prompt, enter y, which begins the configuration:

      Do you want to start the configuration now? (y/n):   y
      
    4. At the following prompt, enter 2, which initializes the primary database:

      Please enter the starting step (0-8). If you don't know, enter 0:   2
      
    5. Follow the instructions displayed and exit the pin_multidb.pl script.

      The refresh groups are recreated in the primary database.

    6. Run the following command:

      pin_multidb.pl -R all
      

      The views, based on the information in the refresh groups, are re-created in the secondary databases.

Upgrading the BRM Cache Groups Schema in IMDB Cache

Note:

This procedure is required only if you installed Oracle IMDB Cache Manager.

Important:

In multischema systems, perform these tasks first on the primary BRM installation machine and then on the secondary BRM installation machines.

When you upgrade the BRM Cache Groups schema in IMDB Cache, you delete the data stores in IMDB Cache and then re-create them.

To upgrade the BRM Cache Groups schema in IMDB Cache:

  1. (Optional) If you have created any customizations in the cache groups, save the BRM_Home/bin/pin_tt_schema_gen.values file to a different location. Note down the name and location of this file.

    Note:

    In a BRM system with multiple database schemas, save the pin_tt_schema_gen.values file for each schema.
  2. Connect to IMDB Cache using ttIsql.

  3. Run the following command, which unloads each cache group:

    UNLOAD CACHE GROUP CacheGroupName
    

    where CacheGroupName is the name of the cache group to be unloaded.

    All cache instances from all cache tables in CacheGroupName are unloaded.

    Important:

    Unload all cache groups before you start the upgrade.

    For information about unloading a cache group, see the discussion about cache group operations in Oracle In-Memory Database Cache User's Guide.

  4. Detach all IMDB nodes from the cache grid.

    • For high-availability (HA) systems:

      Important:

      If the grid member is an active standby pair, detach the active master and standby master databases separately.

      Run the following commands, in the order indicated, which detach the IMDB node on the active standby pair from the cache grid:

      ttCWAdmin –stop –dsn DataStoreName
      ttCWAdmin –drop –dsn DataStoreName
      

      where DataStoreName is the name of the data store to detach.

      For more information on detaching grid members in an HA environment, see Oracle In-Memory Database Cache User's Guide.

    • For non-HA systems:

      Run the following command, which detaches all the IMDB nodes:

      ttGridDetach();
      

      For information about the ttGridDetach() command, see the discussion about cleaning up the caching environment in Oracle In-Memory Database Cache User's Guide.

  5. Run the following command, which stops the replication agent on each database:

    CALL ttRepStop;
    

    For more information on stopping the replication agent, see the discussion about managing the replication agent in Oracle In-Memory Database Cache User's Guide.

  6. Drop the cache groups by doing the following:

    1. Run the following command, which drops all the default BRM cache groups:

      BRM_Home/bin/tt_drop.sql
      
    2. Run the following command, which drops each custom cache group that you created:

      DROP CACHE GROUP CacheGroupName
      

      where CacheGroupName is the name of the cache group you want to drop.

    For information about dropping cache groups, see Oracle In-Memory Database Cache User's Guide.

  7. Run the following command, which stops the TimesTen cache agent:

    call ttCacheStop;
    

    For information about stopping the TimesTen cache agent, see Oracle In-Memory Database Cache User's Guide.

  8. Destroy the data store by doing the following:

    1. Disconnect from all databases.

    2. Stop the TimesTen main daemon process, which manages all databases under the same TimesTen installation, by running the following command:

      ttdaemonadmin -stop
      
    3. Restart the TimesTen main daemon process by running the following command:

      ttdaemonadmin -start
      
    4. Destroy the data store by running the following command:

      ttDestroy DataStoreName
      

      where DataStoreName is the name of the data store to be destroyed.

      For information about ttDestroy, see the discussion about cleaning up the caching environment in Oracle In-Memory Database Cache User's Guide.

  9. Stop the CM processes.

    For more information, see the discussion about starting and stopping the BRM system in BRM System Administrator's Guide.

  10. Stop the IMDB Cache Data Manager (DM) processes.

    For more information, see the discussion about starting and stopping Oracle IMDB Cache DM in BRM System Administrator's Guide.

  11. Re-create the data store in IMDB Cache.

    For more information, see the discussion about creating the data store in Oracle IMDB Cache in BRM System Administrator's Guide.

  12. Generate the schema SQL and load SQL scripts to set up the cache group schema by doing the following:

    Note:

    In a BRM system with multiple database schemas, complete these steps for each schema.
    1. Configure the pin_tt_schema_gen.values file.

      For more information, see the discussion about configuring the pin_tt_schema_gen.values file in BRM System Administrator's Guide.

      Optionally, you can use the pin_tt_schema_gen.values file saved in step 1.

    2. Run the following command, which generates your schema and load scripts:

      pin_tt_schema_gen
      

      For more information, see the discussion about generating your schema and load SQL scripts in BRM System Administrator's Guide.

  13. Initialize your data stores.

    For more information, see the discussion about initializing your data stores in Oracle IMDB Cache in BRM System Administrator's Guide.

  14. Connect your data stores to the BRM database.

    For more information, see the discussion about connecting your data stores to the BRM database in BRM System Administrator's Guide.

  15. Connect the IMDB Cache DM to your data stores.

    For more information, see the discussion about connecting IMDB Cache DM to your data stores in BRM System Administrator's Guide.

  16. Configure the CM to connect to the Oracle DM.

    For more information, see the discussion about using configuration files to connect and configure components in BRM System Administrator's Guide.

  17. Run the pin_75_75ps10_upgrade.pl script from the UNIX prompt:

    cd BRM_Home/setup/scripts
    pin_75_75ps10_upgrade.pl
    

Upgrading the Pipeline Manager Database Schema

Important:

In multischema systems, first run the database upgrade script on the primary database schema, synchronize the configuration and rate-related tables for each secondary database schema in your BRM system, and then run the upgrade script on the secondary database schemas.

To upgrade your Pipeline Manager database schema:

  1. Open the Pipeline_Home/upgrade/pipeline_upgrade.cfg file in a text editor, where Pipeline_Home is the directory in which Pipeline Manager is installed.

  2. Set the values of the following parameters:

    • Set PIN_TEMP_DIR to the directory in which you want to create the temporary files.

    • Set the $PIPELINE_TBLSPACE environment variable to the tablespace where you want to create pipeline database objects.

  3. In the Information about the databases section, configure the database settings as required.

  4. Save and close the file.

  5. Grant the required access to user pin on the Pipeline Manager tables and sequences, if you have not already done so. See the discussion about loading the discount stored procedure in BRM Installation Guide for more information about the Pipeline Manager tables and sequences that you should grant user pin access to.

  6. Run the pin_upgrade_pipeline_75_75ps10.pl and create_pricing_discountmodel_procedures.plb scripts from the UNIX prompt:

    cd Pipeline_Home/upgrade/scripts
    pin_upgrade_pipeline_75_75ps10.pl
    cd Pipeline_Home/database/Oracle/Scripts
    sqlplus login/password@database_alias < create_pricing_discountmodel_procedures.plb
    

    where:

    • login is the user name for the database schema you are updating.

    • password is the password for the specified user name.

    • database_alias is the BRM database alias of the schema you are updating.

Adding Customizations

Important:

In multischema systems, incorporate customizations first on the secondary BRM installation machines and then on the primary BRM installation machine.

Incorporate any customizations you made, including source code, policy, pin.conf, pin_ctl.conf, pin_setup.values, and Infranet.properties files, unless you have already incorporated them.

(Production system only) Remove all entries for the pin_virtual_time utility from the configuration files.

Upgrading from BRM 7.4 to the BRM 7.5 Patch Set

Note:

In multischema systems, perform this task first on the primary BRM installation machine and then on the secondary BRM installation machines.

To upgrade BRM 7.4 to the BRM 7.5 patch set:

  1. Upgrade BRM 7.4 to base BRM 7.5. See the discussion about upgrading from BRM 7.4 to BRM 7.5 in BRM Upgrade Guide.

    Note:

    Do not upgrade the BRM 7.4 database schema to the base BRM 7.5 database schema.
  2. If BRM is installed on a Solaris server, install the 148198-03 for SPARC patch on that server. See "Installing Solaris Patches".

  3. Open the BRM_Home/setup/pin_setup.values file in a text editor.

  4. Set the values of the following parameters:

    $SETUP_CREATE_PARTITIONS = "NO";
    $ENABLE_PARTITION = "NO";
    $SETUP_DROP_ALL_TABLES = "NO";
    $SETUP_INIT_DB = "NO";
    $CREATE_DATABASE_TABLES = "NO";
    
  5. Save and close the file.

  6. Go to the BRM_Home/setup directory and run the following command:

    ./pin_setup
    
  7. Install the BRM 7.5 patch set software. See "Installing the BRM 7.5 Patch Set".

  8. Upgrade the BRM patch set database schema. See "Upgrading the BRM 7.5 Patch Set Database Schema".

  9. Upgrade the BRM patch set Pipeline Manager database schema. See "Upgrading the BRM 7.5 Patch Set Pipeline Manager Database Schema".

Installing the BRM 7.5 Patch Set

Important:

In multischema systems, perform this task first on the primary BRM installation machine and then on the secondary BRM installation machines.

If the optional components that you require are not installed, you must install the optional managers before installing the BRM 7.5 patch set.

To install the BRM 7.5 patch set:

  1. Create a temporary directory (temp_dir).

  2. Go to the My Oracle Support Web site:

    http://support.oracle.com

  3. Sign in with your user name and password.

  4. Click the Patches & Updates tab.

  5. From the list, select Patch Name or Number.

  6. In the text field, enter 19678435 and click Search.

    The Patch Search Results page appears.

  7. Click the patch name.

    The patch details appear.

  8. From the Platform list, select the platform and click Download.

    The File Download dialog box appears.

  9. Download the appropriate p19678435_750_platform.zip software pack to temp_dir, where platform is linux, aix, hpux_ia64, or solaris.

  10. Unzip the p19678435_750_platform.zip file.

  11. Install the Third-Party software by doing the following:

    1. Go to temp_dir and run the following command:

      7.5PS10_ThirdParty_platform_32_opt.bin -console
      

      where platform is linux, aix, hpux_ia64, or solaris.

    2. When prompted, enter the path to the Third-party_Home directory, where Third-party_Home is the directory in which the Third-Party software is installed.

    3. Follow the instructions displayed during installation.

      The latest supported versions of Perl and Remote Diagnostic Agent (RDA) are installed and the corresponding files in the Third-party_Home/tools directory are replaced. For detailed information on supported versions, see the discussion about BRM software compatibility in BRM Installation Guide.

    4. Go to BRM_Home and source the source.me file, where BRM_Home is the directory in which you installed BRM:

      Bash shell:

      source source.me.sh 
      

      C shell:

      source source.me.csh 
      
  12. Go to temp_dir and run the following command, which installs the patch software:

    PatchPackageName.bin -console
    

    where PatchPackageName is:

    • 7.5PS10_19678435_Portal_Base_platform_opt for upgrading BRM plus any BRM optional components installed on your system.

    • 7.5PS10_19678435_Portal_SDK_platform_opt for upgrading the BRM SDK.

    • 7.5PS10_19678435_Pipeline_platform_opt for upgrading Pipeline Manager.

    where platform is linux, aix, hpux_ia64, or solaris.

  13. Follow the instructions displayed during installation.

  14. Run the following command, which installs the database upgrade package:

    PatchPackageName.bin -console
    

    where PatchPackageName is:

    • 7.5PS10_PortalBase_Upgrade_74_75_platform_32_opt for upgrading the BRM patch set database schema plus the database schema for any BRM optional components installed on your system.

    • 7.5PS10_Pipeline_Upgrade_74_75_platform_32_opt for upgrading the Pipeline Manager patch set database schema.

    where platform is linux, aix, hpux_ia64, or solaris.

  15. Follow the instructions displayed during installation.

Important:

With BRM 7.5 Patch Set 10, the OpenSSL software is no longer part of the BRM patch set installation package. Installing this patch set removes the OpenSSL libraries that were installed by the previous patch sets. For BRM, Oracle recommends that you use the OpenSSL software bundled with the host operating system. Ensure that the latest version of the OpenSSL software is installed for your operating system.

Upgrading the BRM 7.5 Patch Set Database Schema

If the optional components are not installed, the database objects associated with these optional components are not created or updated.

If Oracle In-Memory Database (IMDB) Cache is installed, see "Upgrading the BRM Cache Groups Schema in IMDB Cache".

To upgrade the BRM 7.5 patch set database schema, perform one of the following procedures:

Upgrading the BRM 7.5 Patch Set Schema on Single-Schema Systems

To upgrade the BRM 7.5 patch set schema on single-schema systems:

  1. Open the BRM_Home/sys/dm_oracle/pin.conf file in a text editor.

  2. Uncomment the following entry:

    - crypt md5| ${PIN_HOME}/lib/${LIBRARYPREFIX}pin_crypt4dm64${LIBRARYEXTENSION} "Abracadabra dabracaabrA" 
    
  3. Save and close the file.

  4. Open the BRM_Home/setup/pin_setup.values file in a text editor.

  5. (Optional) Set the values of the following parameters:

    • Set PIN_TEMP_DIR to the directory in which you want to create the temporary files. Ensure that the directory has full write permissions.

    • Set PIN_LOG_DIR to the directory in which you want to create the BRM log files.

  6. In the Information about the CM section, add the following text:

    $MAIN_CM{'pcm_admin_passwd'} = "&aes|08|0D5E11BFDD97D2769D9B0DBFBD1BBF7E5D40C305EDF3D77DF111AAB8F781E92122";
    

    The password that is used by the load utilities to connect to the Connection Manager (CM) is reset to the default password.

  7. In the Information about the databases section, configure the database settings as required.

  8. Set SETUP_INIT_DB to YES, if it is not set.

  9. Save and close the file.

  10. Go to BRM_Home and source the source.me file:

    • Bash shell:

      source source.me.sh 
      
    • C shell:

      source source.me.csh 
      
  11. Run the pin_75ps10_upgrade.pl script from the UNIX prompt:

    cd BRM_Home/setup/scripts
    pin_75ps10_upgrade.pl
    
  12. Merge the contents of the backed up pin_ctl.conf file into the new pin_ctl.conf file.

Upgrading the BRM 7.5 Patch Set Schema on Multischema Systems

To upgrade the BRM 7.5 patch set schema on multischema systems:

  1. On the primary BRM installation machine, do the following:

    1. Open the BRM_Home/sys/dm_oracle/pin.conf file in a text editor.

    2. Uncomment the following entry:

      - crypt md5| ${PIN_HOME}/lib/${LIBRARYPREFIX}pin_crypt4dm64${LIBRARYEXTENSION} "Abracadabra dabracaabrA" 
      
    3. Save and close the file.

    4. Open the BRM_Home/setup/pin_setup.values file in a text editor.

    5. (Optional) Set the values of the following parameters:

      Set PIN_TEMP_DIR to the directory in which you want to create the temporary files.

      Set PIN_LOG_DIR to the directory in which you want to create the BRM log files.

    6. In the Information about the CM section, add the following text:

      $MAIN_CM{'pcm_admin_passwd'} = "&aes|08|0D5E11BFDD97D2769D9B0DBFBD1BBF7E5D40C305EDF3D77DF111AAB8F781E92122";
      

      The password that is used by the load utilities to connect to the CM is reset to the default password.

    7. In the Information about the databases section, configure the database settings for your primary database schema.

    8. Set SETUP_INIT_DB to YES, if it is not set.

    9. Save and close the file.

    10. Go to BRM_Home and source the source.me file:

      Bash shell:

      source source.me.sh 
      

      C shell:

      source source.me.csh 
      
    11. Run the install.sh script:

      cd BRM_Home/apps/multi_db
      ./install.sh
       
      

      Follow the on-screen instructions, entering the following information for the primary schema and for each secondary schema when requested:

      – Schema user name

      – Schema password

      – Schema SID (the BRM database alias of the schema)

      Important:

      Repeat the "Do you have secondary schema to process" step for each secondary schema in your system.

      The install script fixes any data errors caused by conflicting storable class IDs. The errors might have occurred during global (XA) transactions involving multiple schemas or when accounts were migrated from one schema to another.

      Note:

      As the install script runs, it generates the BRM_Home/apps/multi_db/fix_multi_schema.log file. To view the progress of the script, display the log file in a different console window.
    12. Run the pin_75ps10_upgrade.pl script from the UNIX prompt:

      cd BRM_Home/setup/scripts
      pin_75ps10_upgrade.pl
      
    13. Merge the contents of the backed up pin_ctl.conf file into the new pin_ctl.conf file.

  2. On each secondary BRM installation machine, do the following:

    1. Open the BRM_Home/sys/dm_oracle/pin.conf file in a text editor.

    2. Uncomment the following entry:

      - crypt md5| ${PIN_HOME}/lib/${LIBRARYPREFIX}pin_crypt4dm64${LIBRARYEXTENSION} "Abracadabra dabracaabrA" 
      
    3. Save and close the file.

    4. Open the BRM_Home/setup/pin_setup.values file in a text editor.

    5. In the Information about the CM section, add the following text:

      $MAIN_CM{'pcm_admin_passwd'} = "&aes|08|0D5E11BFDD97D2769D9B0DBFBD1BBF7E5D40C305EDF3D77DF111AAB8F781E92122";
      

      The password that is used by the load utilities to connect to the CM is reset to the default password.

    6. Change the $DM_ORACLE{&rsquor;db_num'} entry, where db_num is the number of the corresponding secondary database schema to upgrade.

    7. Configure the database settings as required.

    8. Set SETUP_INIT_DB to YES, if it is not set.

    9. Save and close the file.

    10. Go to BRM_Home and source the source.me file:

      Bash shell:

      source source.me.sh 
      

      C shell:

      source source.me.csh 
      
    11. Run the pin_75ps10_upgrade.pl script from the UNIX prompt:

      cd BRM_Home/setup/scripts
      pin_75ps10_upgrade.pl
      
    12. Merge the contents of the backed up pin_ctl.conf file into the new pin_ctl.conf file.

  3. On the primary BRM installation machine, do the following:

    1. Go to the BRM_Home/setup/scripts directory.

    2. Run the following command:

      pin_multidb.pl -i
      
    3. At the following prompt, enter y, which begins the configuration:

      Do you want to start the configuration now? (y/n):   y
      
    4. At the following prompt, enter 2, which initializes the primary database:

      Please enter the starting step (0-8). If you don't know, enter 0:   2
      
    5. Follow the instructions displayed and exit the pin_multidb.pl script.

      The refresh groups are recreated in the primary database.

    6. Run the following command:

      pin_multidb.pl -R all
      

      The views, based on the information in the refresh groups, are re-created in the secondary databases.

Upgrading the BRM 7.5 Patch Set Cache Groups Schema in IMDB Cache

Note:

This procedure is required only if you installed Oracle IMDB Cache Manager.

Important:

In multischema systems, perform these tasks first on the primary BRM installation machine and then on the secondary BRM installation machines.

When you upgrade the BRM 7.5 patch set Cache Groups schema in IMDB Cache, you delete the data stores in IMDB Cache and then re-create them.

To upgrade the BRM 7.5 patch set Cache Groups schema in IMDB Cache:

  1. (Optional) If you have created any customizations in the cache groups, save the BRM_Home/bin/pin_tt_schema_gen.values file to a different location. Note down the name and location of this file.

    Note:

    In a BRM system with multiple database schemas, save the pin_tt_schema_gen.values file for each schema.
  2. Connect to IMDB Cache using ttIsql.

  3. Run the following command, which unloads each cache group:

    UNLOAD CACHE GROUP CacheGroupName
    

    where CacheGroupName is the name of the cache group to be unloaded.

    All cache instances from all cache tables in CacheGroupName are unloaded.

    Important:

    Unload all cache groups before you start the upgrade.

    For information about unloading a cache group, see the discussion about cache group operations in Oracle In-Memory Database Cache User's Guide.

  4. Detach all IMDB nodes from the cache grid.

    • For high-availability (HA) systems:

      Important:

      If the grid member is an active standby pair, detach the active master and standby master databases separately.

      Run the following commands, in the order indicated, which detach the IMDB node on the active standby pair from the cache grid:

      ttCWAdmin –stop –dsn DataStoreName
      ttCWAdmin –drop –dsn DataStoreName
      

      where DataStoreName is the name of the data store to detach.

      For more information on detaching grid members in an HA environment, see Oracle In-Memory Database Cache User's Guide.

    • For non-HA systems:

      Run the following command, which detaches all the IMDB nodes:

      ttGridDetach();
      

      For information about the ttGridDetach() command, see the discussion about cleaning up the caching environment in Oracle In-Memory Database Cache User's Guide.

  5. Run the following command, which stops the replication agent on each database:

    CALL ttRepStop;
    

    For more information on stopping the replication agent, see the discussion about managing the replication agent in Oracle In-Memory Database Cache User's Guide.

  6. Drop the cache groups by doing the following:

    1. Run the following command, which drops all the default BRM cache groups:

      BRM_Home/bin/tt_drop.sql
      
    2. Run the following command, which drops each custom cache group that you created:

      DROP CACHE GROUP CacheGroupName
      

      where CacheGroupName is the name of the cache group you want to drop.

    For information about dropping cache groups, see Oracle In-Memory Database Cache User's Guide.

  7. Run the following command, which stops the TimesTen cache agent:

    call ttCacheStop;
    

    For information about stopping the TimesTen cache agent, see Oracle In-Memory Database Cache User's Guide.

  8. Destroy the data store by doing the following:

    1. Disconnect from all databases.

    2. Stop the TimesTen main daemon process, which manages all databases under the same TimesTen installation, by running the following command:

      ttdaemonadmin -stop
      
    3. Restart the TimesTen main daemon process by running the following command:

      ttdaemonadmin -start
      
    4. Destroy the data store by running the following command:

      ttDestroy DataStoreName
      

      where DataStoreName is the name of the data store to be destroyed.

      For information about ttDestroy, see the discussion about cleaning up the caching environment in Oracle In-Memory Database Cache User's Guide.

  9. Stop the CM processes.

    For more information, see the discussion about starting and stopping the BRM system in BRM System Administrator's Guide.

  10. Stop the IMDB Cache Data Manager (DM) processes.

    For more information, see the discussion about starting and stopping Oracle IMDB Cache DM in BRM System Administrator's Guide.

  11. Re-create the data store in IMDB Cache.

    For more information, see the discussion about creating the data store in Oracle IMDB Cache in BRM System Administrator's Guide.

  12. Generate the schema SQL and load SQL scripts to set up the cache group schema by doing the following:

    Note:

    In a BRM system with multiple database schemas, complete these steps for each schema.
    1. Configure the pin_tt_schema_gen.values file.

      For more information, see the discussion about configuring the pin_tt_schema_gen.values file in BRM System Administrator's Guide.

      Optionally, you can use the pin_tt_schema_gen.values file saved in step 1.

    2. Run the following command, which generates your schema and load scripts:

      pin_tt_schema_gen
      

      For more information, see the discussion about generating your schema and load SQL scripts in BRM System Administrator's Guide.

  13. Initialize your data stores.

    For more information, see the discussion about initializing your data stores in Oracle IMDB Cache in BRM System Administrator's Guide.

  14. Connect your data stores to the BRM database.

    For more information, see the discussion about connecting your data stores to the BRM database in BRM System Administrator's Guide.

  15. Connect the IMDB Cache DM to your data stores.

    For more information, see the discussion about connecting IMDB Cache DM to your data stores in BRM System Administrator's Guide.

  16. Configure the CM to connect to the Oracle DM.

    For more information, see the discussion about using configuration files to connect and configure components in BRM System Administrator's Guide.

  17. Run the pin_75ps10_upgrade.pl script from the UNIX prompt:

    cd BRM_Home/setup/scripts
    pin_75ps10_upgrade.pl
    

Upgrading the BRM 7.5 Patch Set Pipeline Manager Database Schema

Important:

In multischema systems, first run the database upgrade script on the primary database schema, synchronize the configuration and rate-related tables for each secondary database schema in your BRM system, and then run the upgrade script on the secondary database schemas.

To upgrade your BRM 7.5 patch set Pipeline Manager database schema:

  1. Open the Pipeline_Home/upgrade/pipeline_upgrade.cfg file in a text editor, where Pipeline_Home is the directory in which Pipeline Manager is installed.

  2. Set the values of the following parameters:

    • Set PIN_TEMP_DIR to the directory in which you want to create the temporary files.

    • Set the $PIPELINE_TBLSPACE environment variable to the tablespace where you want to create pipeline database objects.

  3. In the Information about the databases section, configure the database settings as required.

  4. Save and close the file.

  5. Grant the required access to user pin on the Pipeline Manager tables and sequences, if you have not already done so. See the discussion about loading the discount stored procedure in BRM Installation Guide for more information about the Pipeline Manager tables and sequences that you should grant user pin access to.

  6. Run the pin_upgrade_pipeline_75ps10.pl and create_pricing_discountmodel_procedures.plb scripts from the UNIX prompt:

    cd Pipeline_Home/upgrade/scripts
    pin_upgrade_pipeline_75ps10.pl
    cd Pipeline_Home/database/Oracle/Scripts
    sqlplus login/password@database_alias < create_pricing_discountmodel_procedures.plb
    

    where:

    • login is the user name for the database schema you are updating.

    • password is the password for the specified user name.

    • database_alias is the BRM database alias of the schema you are updating.

Post-Installation Tasks

This section provides instructions for the post-installation tasks.

Compiling and Linking Your Programs on Solaris

If BRM is installed on a Solaris server, recompile the C++ code that links with BRM libraries.

To recompile and link your programs on Oracle Solaris:

  1. If you have C++ code that links with BRM libraries and it uses standard C++ template libraries, rebuild the C++ code using the -library=stdcxx4 option.

    For more information, see the discussion about creating client applications by using PCM C++ in BRM Developer's Guide.

Granting Read Privileges to the Pending XA Transaction Database Views

If you use JCA Resource Adapter to support extended architecture (XA) transactions, grant read privileges to the pending XA transaction database views for each BRM database user.

To grant read privileges to the pending XA transaction database views:

  1. Using SQL*Plus, log in to your database as the SYSDBA user:

    sqlplus sys@database_alias as sysdba
     
    

    where database_alias is the database alias of your BRM database.

  2. Grant read privileges to the pending XA transaction views:

    SQL>GRANT SELECT ON DBA_2PC_PENDING TO user;
    SQL>GRANT SELECT ON DBA_PENDING_TRANSACTIONS TO user;
     
    

    where user is the name of a BRM database user.

  3. Run the following command, which exits SQL*Plus:

    SQL>exit
    

Resetting the JCA Resource Adapter Transaction Mode

In BRM 7.5 Patch Set 10, JCA Resource Adapter is automatically deployed in XA Transaction mode. To run JCA Resource Adapter in the Local Transaction mode or No Transaction mode, manually reset the transaction mode.

For an overview of the transaction modes, see the discussion about JCA Resource Adapter transaction management in BRM JCA Resource Adapter.

To change the transaction mode, see one of the following sections:

Changing the JCA Resource Adapter Transaction Mode on Oracle WebLogic Server

After JCA Resource Adapter is deployed, you can change the transaction mode.

To change the JCA Resource Adapter transaction mode on the WebLogic server:

  1. Start the WebLogic Server domain if it is not already started.

  2. Log in to WebLogic Server Administration Console. The default is the following:

    http://localhost:8001/console
      
    
  3. In the Domain Structure tree, click Deployments.

    The Summary of Deployments pane appears.

  4. In the Deployments table, click the JCA Resource Adapter name.

    By default, the name is OracleBRMJCA15Adapter.

    The Settings for Adapter_Name pane appears.

  5. Click the Configuration tab.

  6. Click the Outbound Connection Pool tab.

  7. In the Outbound Connection Pool Configuration table, expand the OracleConnectionFactory node.

  8. Click eis/BRM, which is the name of the JNDI for JCA Resource Adapter.

  9. In the Properties tab, click the TransactionMode property value.

  10. Enter one of the following values:

    • NO_TRANSACTION

    • LOCAL_TRANSACTION

    • XA_TRANSACTION

  11. Click Save.

  12. Click the Transaction tab.

  13. From the Transaction Support list, select the value that matches the transaction mode selected in step 10:

    • No Transaction

    • Local Transaction

    • XA Transaction

  14. Click Save.

  15. Log out of WebLogic Server Administration Console.

Changing the JCA Resource Adapter Transaction Mode on Oracle Application Server

After JCA Resource Adapter is deployed, you can change the transaction mode.

To change the JCA Resource Adapter transaction mode on Oracle Application Server:

  1. Unzip the BRM_Home/apps/brm_integrations/jca_adapter/OracleBRMJCA15Adapter.rar file by using the following command:

    unzip OracleBRMJCA15Adapter.rar –d OracleBRMJCA15Adapter
      
    
  2. In the META-INF directory, open the ra.xml file.

  3. In the config-property section, replace the value in the <config-property-value> element with the appropriate transaction mode:

    <config-property>
    <config-property-name>transactionMode</config-property-name>
    <config-property-type>java.lang.String</config-property-type>
    <config-property-value>TransactionMode</config-property-value>
    </config-property>
      
    

    where TransactionMode is one of the following:

    • NO_TRANSACTION

    • LOCAL_TRANSACTION

    • XA_TRANSACTION

  4. In the <transaction-support> element, replace the value with the appropriate transaction support value:

    <transaction-support>TransactionSupported</transaction-support>
      
    

    where TransactionSupported is the value in the following list that matches the transaction mode selected in the preceding step:

    • NoTransaction for No Transaction mode

    • LocalTransaction for Local Transaction mode

    • XATransaction for XA Transaction mode

  5. Save and close the file.

  6. Repackage the META-INF directory in the OracleBRMJCA15Adapter.rar file by entering the following command:

    jar –cvf ../AdapterName.rar .
      
    

    where AdapterName is the JCA Resource Adapter name.

  7. Redeploy JCA Resource Adapter.

Creating an Oracle AQ Database Queue

If your system includes Synchronization Queue DM, you must re-create your Oracle AQ database queue before you can begin synchronizing pricing data. For more information on how to create a database queue, see the discussions about the following:

  • Manually creating a database queue on an Oracle database in BRM Synchronization Queue Manager.

  • Creating additional account synchronization queues in BRM Installation Guide.

After you re-create the Oracle AQ database queue, do the following:

  1. Open the BRM_Home/sys/dm_aq/aq_queuenames file in a text editor.

  2. Add the re-created Oracle AQ database queue name along with the relevant details in the queue block.

  3. Save and close the file.

  4. Stop and restart the DM_AQ services. See the discussion about starting and stopping the Synchronization Queue DM in BRM Synchronization Queue Manager.

Configuring Views for Oracle Application Infrastructure Architecture

In single-schema or multischema environments, you must create or configure a unified collections action view and a unified collections scenario view to be queried by Oracle AIA.

To configure the views for Oracle AIA:

  1. On the primary database schema, run the following commands, which grant permissions for each of the secondary schemas:

    Important:

    This step is not required for single-schema systems.
    sqlplus login/password@database_alias
    SQL>GRANT SELECT ON CONFIG_COLLECTIONS_ACTION_T TO schema_name WITH GRANT OPTION;
    SQL>GRANT SELECT ON CONFIG_COLLECTIONS_SCENARIO_T TO schema_name WITH GRANT OPTION;
    

    where:

    • login is the user name for the primary database schema.

    • password is the password for the specified user name.

    • database_alias is the BRM database alias of the primary schema.

    • schema_name is the name of the secondary schema.

  2. On each secondary database schema, run the following commands, which grant permissions on tables required for collections action and scenario view:

    Important:

    This step is not required for single-schema systems.
    sqlplus login/password@database_alias
    SQL>GRANT SELECT ON AU_COLLECTIONS_ACTION_T TO schema_name;
    SQL>GRANT SELECT ON COLLECTIONS_SCENARIO_T TO schema_name;
    SQL>GRANT SELECT ON BILLINFO_T TO schema_name;
    SQL>GRANT SELECT ON COLL_ACTION_IF_VIEW To schema_name;
    SQL>GRANT SELECT ON COLL_SCENARIO_IF_VIEW to schema_name;
    SQL>exit
    

    where:

    • login is the user name for the secondary database schema.

    • password is the password for the specified user name.

    • database_alias is the BRM database alias of the secondary schema.

    • schema_name is the name of the primary schema.

  3. On the primary database schema, run the following command:

    sqlplus login/password@database_alias
    

    where:

    • login is the user name for the primary database schema.

    • password is the password for the specified user name.

    • database_alias is the BRM database alias of the primary schema.

  4. Do the following:

    • To create a unified collections action view, run the following command:

      SQL>CREATE OR REPLACE VIEW "UNIFIED_COLL_ACTION_IF_VIEW" AS SELECT * FROM schema1.COLL_ACTION_IF_VIEW UNION  SELECT * FROM schema2.COLL_ACTION_IF_VIEW;
      
    • To create a unified collections scenario view, run the following command:

      SQL>CREATE OR REPLACE VIEW "UNIFIED_COLL_SCENARIO_IF_VIEW" AS SELECT * FROM schema1.COLL_SCENARIO_IF_VIEW UNION SELECT * FROM schema2.COLL_SCENARIO_IF_VIEW;
      

      where:

      • schema1 is the name of the primary schema.

      • schema2 is the name of each of the secondary schemas.

  5. Run the following command, which exits SQL*Plus:

    SQL>exit
    

Configuring the Infranet.properties File for the pin_virtual_gen Utility

To enable virtual columns in the BRM database, you must configure the Infranet.properties file before using the pin_virtual_gen utility to convert a standard BRM database into one with virtual columns.

Important:

In multischema systems, perform this task first on the primary BRM installation machine and then on the secondary BRM installation machines.

To configure the Infranet.properties file:

  1. Open the BRM_Home/apps/pin_virtual_columns/Infranet.properties file in a text editor.

  2. Add the following entries:

    # Logging configuration
    infranet.log.file = vcol.pinlog
    infranet.log.level = 1
    infranet.log.name = VCOL
    
    # Infranet JDBC connection configuration
    infranet.vcol.userid = user_name
    infranet.vcol.password = password
    infranet.vcol.dbname = database_alias
    
    infranet.vcol.worker_threads = 10
    

    where:

    • user_name is the login name to use for connecting to the BRM database.

    • password is the encrypted password for user_name.

    • database_alias is the BRM database alias.

  3. Save and close the file.

Configuring the pin.conf File for Rule-Based Collections Scenario

You must configure the pin.conf file before using the load_config utility to load additional parameters for rule-based collections scenario assignment.

To configure the pin.conf file:

  1. Open the BRM_Home/apps/load_config/pin.conf file in a text editor.

  2. Uncomment the following entry:

    - load_config validation_module libLoadValidCollections LoadValidCollections_init
    
  3. Save and close the file.

Configuring TAP Roaming Manager

If you have TAP Roaming Manager installed on your system, do the following:

  1. Create the input and output directories for the Stop RAP Generator pipeline by running the following commands at the UNIX prompt:

    mkdir -p Pipeline_Home/data/stoprap/in
    mkdir -p Pipeline_Home/data/stoprap/out
    

    See BRM 7.5 Patch Set 10 Release Notes for more information about the StopRapGen utility and the Stop RAP Generator pipeline.

  2. Include the other iScript source files in your iScript by running the following command.

    Bash shell:

    export ISCRIPT_INCLUDE="Pipeline_Home/iScriptLib/iScriptLib_Roaming;Pipeline_Home/formatDesc/Formats/TAP3-NG;."
    

    C shell:

    setenv ISCRIPT_INCLUDE="Pipeline_Home/iScriptLib/iScriptLib_Roaming;Pipeline_Home/formatDesc/Formats/TAP3-NG;."
    

    The preprocessor uses the semicolon-separated list of directories specified in the ISCRIPT_INCLUDE environment variable as the input directories for the other iScript source files to include in your iScript.

    Important:

    If an iScript include statement contains the relative path of an included iScript and the iScript file name, after setting the ISCRIPT_INCLUDE environment variable, remove the relative path and include only the iScript file name.

Configuring Conversion Manager to Migrate the /purchased_bundle_t Class from a Legacy Database to the BRM Database

If you have Conversion Manager installed on your system, you must load the create_cmt_procedure.sql stored procedure to configure Conversion Manager to migrate the /purchased_bundle_t class from a legacy database to the BRM database.

To configure Conversion Manager:

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

  2. Run the following command, which opens SQL*Plus:

    sqlplus login/password@database_alias
    

    where:

    • login is the login name to use for connecting to the BRM database.

    • password is the encrypted password for login.

    • database_alias is the BRM database alias.

  3. Run the following command:

    SQL>@ create_cmt_procedure.sql
    

    The stored procedure is loaded.

  4. Run the following command, which exits SQL*Plus:

    SQL>exit
    

Enabling Global Search in a Multischema Environment

In a multischema environment, do the following on each BRM installation machine in which a CM is running:

  1. Go to the BRM_Home/lib directory.

  2. Run the following command, which copies the fm_global_search.so.PatchNumber.bak file to fm_global_search.so:

    cp fm_global_search.so.PatchNumber.bak fm_global_search.so
    

    where PatchNumber is the patch number of the current BRM 7.5 patch set.

  3. Stop and restart the CM. See the discussion about starting and stopping the BRM system in BRM System Administrator's Guide.

Enabling the Logging Mechanism for the pin_purge Utility

To enable the logging mechanism for the pin_purge utility:

  1. Open the BRM_Home/apps/pin_subscription/pin.conf file in a text editor.

  2. Add the following entries to the file:

    - pin_purge logfile BRM_Log_Dir/pin_subscription/pin_purge.pinlog 
    - pin_purge loglevel 2
    

    where BRM_Log_Dir specifies the directory for the generated log file.

  3. Save and close the file.

Configuring Account Migration Manager Using Oracle Application Infrastructure Architecture in a Multischema Environment

You must load the create_amt_mv_pkg.sql and create_amt_mv_pkb.sql stored procedures to configure Account Migration Manager (AMM) with your external application using Oracle AIA in a multischema environment.

To configure AMM:

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

  2. Run the following command, which opens SQL*Plus:

    sqlplus login/password@database_alias
    

    where:

    • login is the login name to use for connecting to the BRM database.

    • password is the encrypted password for login.

    • database_alias is the BRM database alias.

  3. Run the following commands in the given order:

    SQL>@ create_amt_mv_pkg.sql
    SQL>@ create_amt_mv_pkb.sql
    

    The stored procedures are loaded.

  4. Run the following command, which exits SQL*Plus:

    SQL>exit
    

Increasing the Size of the CM Cache For the Facilities Modules on AIX 6.1 TL9

If BRM and the optional managers are installed on AIX 6.1 TL9, you must increase the size of the CM cache for the Facilities Modules (FMs) to prevent errors at CM startup.

To increase the size of the CM cache for the FMs on AIX 6.1 TL9:

  1. Open the BRM_Home/sys/cm/pin.conf file in a text editor.

  2. Add the following line:

    - cm cm_cache_space 7340032
    
  3. Save and close the file.

  4. Stop and restart the CM. See the discussion about starting and stopping the BRM system in BRM System Administrator's Guide.

Modifying the i_item_glseg_eff__id Index

Modify the i_item_glseg_eff__id index on the ITEM_T table in the BRM database before generating a general ledger report.

To modify the i_item_glseg_eff__id index:

  1. Open the BRM_Home/sys/dd/data/replace_item_index_glseg_eff.source file in a text editor.

  2. Set the values of the following parameters:

    • Set the $PIN_CONF_TBLSPACEX1 parameter to the tablespace defined in the BRM_Home/setup/scripts/pin_tables.values file.

    • Set the $PIN_CONF_STORAGE_MED_INS parameter to the storage parameters defined in the BRM_Home/setup/scripts/pin_tables.values file.

  3. Save and close the file.

  4. Run the following command, which opens SQL*Plus:

    sqlplus login/password@database_alias
    
  5. Run the following command, which modifies the i_item_glseg_eff__id index:

    SQL>@ replace_item_index_glseg_eff.source
    

    Note:

    For information about the database performance, see the comments in the replace_item_index_glseg_eff.source file.
  6. Run the following command, which rebuilds the i_item_glseg_eff__id index:

    SQL>@ ALTER INDEX i_item_glseg_eff__id REBUILD
    
  7. Run the following command, which exits SQL*Plus:

    SQL>exit
    

Resetting the Value of OPENED_T of the Previously Billed Items for General Ledger Reports

To generate billed revenue general ledger reports based on the actual billing date, reset the value of the OPENED_T field in the /item object for the previously billed items that are incorrectly set to 0 in the BRM database.

Note:

Reset the value of the OPENED_T field in the /item object for the previously billed items only if the UseActualBilledTimeForGLReport business parameter is enabled. For more information about enabling the UseActualBilledTimeForGLReport business parameter, see the discussion about generating general ledger reports for billed revenue to be based on the actual time of billing in BRM Collecting General Ledger Data.

To reset the value of OPENED_T of the previously billed items for billed revenue general ledger reports:

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

  2. Run the following command, which opens SQL*Plus:

    sqlplus login/password@database_alias
    
  3. Run the following command, which resets the value of OPENED_T for the previously billed items that are incorrectly set to 0:

    SQL>@ fix_items_with_zero_opened_t.source
    

    Note:

    For information about the database performance, see the comments in the fix_items_with_zero_opened_t.source file.
  4. Run the following command, which exits SQL*Plus:

    SQL>exit
    

Running the RE Loader Daemon

To run the Rated Event (RE) Loader daemon to load the pipeline-rated events into the BRM database:

  1. Open the BRM_Home/apps/pin_rel/Infranet.properties file in a text editor.

  2. Add the following entry:

    infranet.rel.use_end_time = value
    

    where value is:

    • 1 to specify that RE Loader use the end time of the rated event for deciding the billing cycle. This is the default.

    • 0 to specify that RE Loader use the start time of the rated event for deciding the billing cycle.

  3. Add the following entries:

    batch.check.interval = value
    batch.file.rename.extension = value
    batch.start.highload.time = value
    batch.end.highload.time = value
    batch.lock.socket.addr = value
    batch.rel.archiveDir = value
    batch.rel.rejectDir = value
    batch.random.events = value
    event.max.at.highload.time = value
    event.max.at.lowload.time = value
    event.file.location = value
    event.file.pattern = value
    event.tt_node = value
    event.archiveDir = value
    event.rejectDir = value
    

    where:

    • value is the appropriate value for the respective entry. For more information about the appropriate values, see the discussion of configuring the RE Loader Infranet.properties file in BRM Configuring Pipeline Rating and Discounting.

    • event is the appropriate event type.

  4. Create a set of these entries for each event type you want to load.

  5. Save and close the file.

  6. (Oracle IMDB Cache systems only) Do the following:

    1. Open the BRM_Home/bin/pin_ctl.conf file in a text editor.

    2. Search the file for the following line:

      common env_platform:common env_variable:TT_LIB_PATH:__TIMESTEN_CLIENT_HOME__/lib
      
    3. Replace __TIMESTEN_CLIENT_HOME__ with the full path of the 32-bit Oracle IMDB Cache client software library directory.

    4. (Linux only) Verify that the first directory path in the LD_LIBRARY_PATH environment variable is Oracle_Home/lib32, where Oracle_Home is the directory in which Oracle Database is installed.

    5. Save and close the file.

    6. Open the BRM_Home/bin/start_rel_daemon file in a text editor.

    7. Search the file for the following line:

      TT_LIB_PATH=__TIMESTEN_CLIENT_HOME__/lib
      
    8. Replace __TIMESTEN_CLIENT_HOME__/lib with the full path of the 32-bit Oracle IMDB Cache client software library directory.

    9. Save and close the file.

Setting Up RE Loader Processing Directories

To set up RE Loader processing directories, do the following in each instance of RE Loader:

  1. In your BRM_Home/apps/pin_rel directory, create processing directories, if they are not already created.

    For example, create a BRM_Home/apps/pin_rel/GPRS directory and a BRM_Home/apps/pin_rel/GSM directory.

  2. Configure the Infranet.properties file. See the discussion about configuring the RE Loader Infranet.properties file in BRM Configuring Pipeline Rating and Discounting.

  3. Copy all files from the BRM_Home/apps/pin_rel directory to each processing directory.

See the discussion about setting up RE Loader processing directories in BRM Configuring Pipeline Rating and Discounting.

Setting the JAVA_HOME Environment Variable

You must set the JAVA_HOME environment variable to the latest version of JRE 1.7 before running any BRM processes.

To set the JAVA_HOME environment variable on the system on which the BRM server is installed:

  1. Stop all BRM daemons, processes, and managers and all Java processes.

    For more information, see the discussion about starting and stopping the BRM system in BRM System Administrator's Guide.

  2. Set the JAVA_HOME environment variable to the directory in which JRE 1.7 is installed.

    See the discussion about BRM software compatibility in BRM Installation Guide for the supported JRE 1.7 version.

  3. Create a symbolic link, for all BRM-related Java processes, to latest version of JRE 1.7 by running the following command:

    ln -s $JAVA_HOME/bin/java BRM_Home/ThirdPartyApps/jre/1.6.0/bin/java
    
  4. Start all the BRM processes.

  5. Verify the Java version by running the following command:

    java -version
    

    The Java version is displayed. For example:

    java version "1.7.0_13"
    

    If the version displayed does not start with 1.7.0_, the update was not successful.

To set the JAVA_HOME environment variable on each Windows system on which the BRM client application is installed:

  1. Stop all the BRM client applications.

  2. On the desktop, right-click My Computer and select Properties.

    The System Properties dialog box appears.

  3. Click the Advanced tab.

  4. Click Environment Variables.

    The Environment Variables dialog box appears.

  5. In the System variables pane, click New.

    The New System Variable dialog box appears.

  6. In the Variable name field, enter JAVA_HOME.

  7. In the Variable value field, enter the path to the directory in which the latest version of JRE 1.7 is installed.

  8. Click OK.

  9. In the System variables list box, select Path and then click Edit.

    The Edit System Variable dialog box appears.

  10. In the Variable value field, add ;%JAVA_HOME%\bin at the end of the existing path.

  11. Click OK.

  12. In Environment Variables dialog box, click OK.

  13. In the System Properties dialog box, click OK.

Setting the Java Path for BRM Client Applications

You must set the Java path to the latest version of JRE 1.7 before running any BRM client application.

Important:

Ensure that your Web browser is using the latest version of JRE 1.6 before starting Pricing Center from Java Web Start. You cannot start Pricing Center from Java Web Start in a Web browser using JRE 1.7.

To set the Java path for the BRM client application installed on a Windows system:

  1. Close the BRM client application.

  2. Open the BRM_Client_Home\lib\BRM_client_batch file in a text editor.

    where:

    • BRM_Client_Home is the directory in which the BRM client application is installed.

    • BRM_client_batch is the batch file you use to run the BRM client application. For example, to run Customer Center, you use runCC.bat.

  3. Search for the following entry:

    C:\PROGRA~1\COMMON~1\PORTAL~1\JRE\bin\javaw.exe
    
  4. Change this entry to:

    java_path\bin\java.exe
    

    where java_path is the directory in which the latest version of Java 1.7 is installed.

    For example:

    C:\"Program Files"\Java\jdk1.7.0_13\bin\java.exe
    

    Note:

    If @start is not present, add it to the entry. For example:
    @start C:\"Program Files"\Java\jdk1.7.0_13\bin\java.exe
    
  5. Save and close the file.

  6. Start the BRM client application.

Setting the Environment Variables Before Generating the Base64 Encoded Hash in a Solaris Environment

If you are using the libcm_hash.so library's generate_hash API to generate the base64 encoded hash in a Solaris environment, you must set the environment variables to point to the OpenSSL libraries.

To set the environment variables before generating the base64 encoded hash in a Solaris environment:

  1. Run the following command, which sets the LD_PRELOAD environment variable to the OpenSSL libcrypto.so library:

    Bash shell:

    export LD_PRELOAD=OpenSSL_Home/lib/libcrypto.so
    

    C shell:

    setenv LD_PRELOAD OpenSSL_Home/lib/libcrypto.so
    

    where OpenSSL_Home is the directory in which the OpenSSL software is installed on the host operating system.

  2. Run the following command, which adds the directory path to the OpenSSL libcrypto.so file in the LD_LIBRARY_PATH environment variable:

    Bash shell:

    export LD_LIBRARY_PATH=OpenSSL_Home/lib:$LD_LIBRARY_PATH
    

    C shell:

    setenv LD_LIBRARY_PATH OpenSSL_Home/lib:$LD_LIBRARY_PATH
    

Updating BRM Jurisdiction Codes for Vertex Communications Tax Q (CTQ)

If you have Vertex CTQ Series 2.00.05 or later installed on your system, you must update the BRM jurisdiction codes in the BRM database.

To update the BRM jurisdiction codes:

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

  2. Run the following command, which opens SQL*Plus:

    sqlplus login/password@database_alias
    

    where:

    • login is the login name to use for connecting to the BRM database.

    • password is the encrypted password for login.

    • database_alias is the BRM database alias.

  3. Run the following command:

    SQL>@ update_new_ctq2_jurisdiction_codes.source
    

    The BRM jurisdiction codes are updated.

    Note:

    For more information about database performance during this update, see the comments in the update_new_ctq2_jurisdiction_codes.source file.
  4. Run the following command, which exits SQL*Plus:

    SQL>exit
    

Upgrading BRM Database Schema With the Database Objects Associated With Optional Components

While upgrading the BRM database schema, if the optional components are not already installed, the database objects associated with the optional components are not created and updated.

If the optional components are installed after upgrading the BRM database schema, to upgrade the BRM database schema with the database objects associated with the optional components:

  1. Open the BRM_Home/setup/pin_setup.values file in a text editor.

  2. Set the values of the following parameters:

    $DM_ORACLE{'enable_write_objects'} = 1; 
    $DM_ORACLE{'enable_write_fields'} = 1; 
    $DM_ORACLE{'enable_write_portal_objects'} = 1; 
    
  3. Save and close the file.

  4. Open the BRM_Home/sys/dm_oracle/pin.conf file in a text editor.

  5. Set the values of the following parameters:

    $DM_ORACLE{'enable_write_objects'} = 1; 
    $DM_ORACLE{'enable_write_fields'} = 1; 
    $DM_ORACLE{'enable_write_portal_objects'} = 1; 
    
  6. Save and close the file.

  7. Go to the BRM_Home/setup directory and enter the following command:

    % ./pin_setup
    
  8. Reinstall the overlay patch software. See "Installing the Patch".

  9. Upgrade the BRM database schema. See "Upgrading the BRM Database Schema".

  10. Merge the contents of the backed up pin_ctl.conf file into the new pin_ctl.conf file.

Uninstalling the Patch Set from BRM

To uninstall the patch set from BRM:

  1. (Optional) Back up the upgraded environment by doing the following:

  2. Stop all BRM daemons, processes, and managers.

  3. Log in as user pin.

  4. Go to the directory in which you installed the Third-Party package and source the source.me file:

    • Bash shell:

      source source.me.sh 
      
    • C shell:

      source source.me.csh 
      
  5. Run the BRM_Home/uninstaller/PatchPackageName/uninstaller.bin program, where PatchPackageName is the name of the upgrade package you want to uninstall.

    Note:

    You can use the -console parameter to run the program from a command line.

    This starts a series of interactive prompts.

  6. Follow the instructions on the screen.

  7. Restore the database from the offline backup of your BRM database that you created in "Backing Up Your BRM Database". See your database software documentation for more information on restoring full database backups.

Uninstalling the Patch Set from Pipeline Manager

To uninstall the patch set from Pipeline Manager:

  1. (Optional) Back up the upgraded environment by doing the following:

  2. Stop all Pipeline Manager daemons, processes, and managers.

  3. Log in as user pin.

  4. Go to the directory in which you installed the Third-Party package and source the source.me file:

    • Bash shell:

      source source.me.sh 
      
    • C shell:

      source source.me.csh 
      
  5. Run the Pipeline_Home/uninstaller/PatchPackageName/uninstaller.bin program, where PatchPackageName is the name of the upgrade package you want to uninstall.

    Note:

    You can use the -console parameter to run the program from a command line.

    This starts a series of interactive prompts.

  6. Follow the instructions on the screen.

  7. Restore the database from the offline backup of your Pipeline Manager database that you created in "Backing Up Your Pipeline Manager Database". See your database software documentation for more information on restoring full database backups.