This chapter contains the procedures required to upgrade Oracle Communications Billing and Revenue Management (BRM) and Pipeline Manager from version 7.4 to version 7.5. It covers BRM on HP-UX IA64, Linux, Solaris, and AIX platforms.
Important:
Before performing this upgrade, see "About Upgrading BRM Releases" for information on how to plan, prepare for, and test your upgrade.This upgrade includes the changes that are necessary for upgrading BRM version 7.4 to BRM version 7.5.
Note:
For AIX systems, this upgrade includes the changes that are necessary for upgrading BRM version 7.4 to BRM version 7.5 Patch Set 1.Note:
For HP-UX IA64 systems, this upgrade includes the changes that are necessary for upgrading BRM version 7.4 to BRM version 7.5 Patch Set 5.It upgrades the following components:
BRM
BRM Software Development Kit (BRM SDK)
Third-Party software
Simple Network Management Protocol for BRM (BRM SNMP)
Pipeline Manager
Pipeline Portal Development Kit (Pipeline PDK)
This upgrade supports the system configurations listed under "BRM Compatibility Matrix" in BRM Installation Guide.
If IMDB Cache Manager was not installed in your BRM 7.4 environment and you plan to add this software to your BRM 7.5 environment, review "Installing IMDB Cache Manager" in BRM System Administrator's Guide.
Note:
BRM 7.5 systems with IMDB Cache Data Manager version 2 require Oracle Clusterware for Oracle Database 11g.For high-availability (HA) BRM 7.5 systems, IMDB Cache Data Manager version 2 requires Oracle Clusterware for Oracle Database 11g Release 2.
For information on installing or upgrading to IMD B Cache Data Manager version 2 software, see the installation or upgrade guide at the Oracle Database Documentation Library 11g R2 documentation website.
AAA Manager and Diameter Manager are no longer supported in BRM 7.5. You must migrate all current configurations/customizations on AAA Gateway Manager and Diameter Manager for network connectivity to Oracle Communications Online Mediation Controller.
See the Oracle Communications Online Charging Solution documentation for details on the migration process. For more information on how BRM connects to the network for online charging, see Oracle Communications Service Broker Online Mediation Controller Implementation Guide.
This section lists the tasks required to update BRM 7.4 to BRM 7.5. Some tasks are optional or apply only to certain platforms or system configurations.
Caution:
When upgrading a multischema or multidatabase system, pay close attention to the system on which each task is performed.The following tasks must be completed to upgrade your BRM system:
Shut down the current instance of BRM. See "Shutting Down the Current Instance."
Turn off service authentication and authorization. See "Turning Off BRM Service Authentication and Authorization."
If Oracle In-Memory Database (IMDB) Cache Manager version 1 was installed in your BRM 7.4 environment, prepare the IMDB Cache database for the upgrade. See "Creating a Backup of the IMDB Cache Data."
Create a complete backup of your BRM 7.4 data. See "Backing Up Files."
(HP-UX IA64 only) Install the optional components. See "Installing Optional Components."
Install BRM 7.5 without creating a schema. See "Installing BRM 7.5."
Set the environment variables. See "Setting the Environment Variables."
Install the database upgrade package. See "Installing the BRM 7.5 Database Upgrade Package."
Point your BRM 7.5 installation to the new database schema. See "Pointing the BRM 7.5 Installation to the New Database Schema."
Upgrade the BRM database schema to the BRM 7.5 schema. See "Upgrading the BRM Database Schema to the BRM 7.5 Schema."
Upgrade the Pipeline Manager database schema to the BRM 7.5 schema. See "Upgrading the Pipeline Manager Database Schema to the BRM 7.5 Schema."
Install BRM 7.5 client applications. See "Installing the BRM 7.5 Client Applications."
Install optional components. See "Installing Optional Components."
Check other database configurations. See "Other Database Configurations."
Restore customizations in BRM 7.5. See "Restoring Customizations."
Restore service authentication and authorization in BRM 7.5. See "Restoring Service to Your Customers."
Important:
On multidatabase systems, first perform this task on the primary system, and then on the secondary systems.To shut down BRM 7.4:
Stop all BRM 7.4 processes. Only the database instance should be running during the upgrade.
For more information, see ”Starting and Stopping the BRM System” in BRM System Administrator's Guide located in the Oracle Communications Billing and Revenue Management (BRM) 7.4 Documentation.
Ensure that no users are logged in.
Users include customers, client applications, customer service representatives (CSRs), and so on.
Important:
On multidatabase systems, first perform this task on the primary system and then on the secondary systems.To maintain a controlled environment for pre-upgrade testing, cut off interaction between your BRM system and your customers.
For information on turning off service authentication/authorization provided by the RADIUS Manager and AAA Gateway Manager, see the Oracle Communications Billing and Revenue Management 7.4 Documentation.
Important:
You cannot provide your customers access to your BRM system while the upgrade is in progress.Important:
The steps in this section are not required if IMDB was not installed in your BRM 7.4 environment.If you had Oracle IMDB Cache Manager version 1 installed in your BRM 7.4 environment, create a backup of the existing IMDB Cache data by doing the following:
Complete the steps described under "Preparing for the Upgrade to IMDB Cache Manager Version 2".
Important:
Complete the steps described in that section only.Important:
If you are performing the upgrade on systems with distributed or HA architecture, back up the files on every node.Back up the following files:
All files customized for BRM, including any associated source code
Registry files
Policy files
pin.conf
pin_setup.values
Infranet.properties
Important:
Back up all the customized load utility files to a different location. The data in these files is used to transfer and restore your customizations after upgrading to BRM 7.5.For more information, see "Transferring Customizations to the New Release".
Important:
If you are performing the upgrade on systems with distributed or HA architecture, back up the files on every node.To back up Pipeline Manager files:
Enter the following command to rename the vpd.properties file:
mv vpd.properties vpd.properties_74
Enter the following command to rename the opt/ifw.
mv opt/ifw opt/ifw_74
Important:
On multidatabase systems, first perform this task on the primary system and then on the secondary systems.Make a complete offline backup of your BRM 7.4 database. Ensure that the backup is completely valid and usable. See your database documentation for more information on performing full database backups.
In addition to the backup, use the Oracle export utility to export all BRM 7.4 tables. This helps to restore individual tables, if necessary. For more information on the exp utility, see the discussion on export and import utilities in the appropriate version of Oracle Database Utilities.
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.Note:
For HP-UX IA64 systems, install the optional managers before Step 5.When you run the updated pin_setup script, the database is not initialized, database tablespaces and default partitions are not created, and the tables are not dropped. See BRM Installation Guide.
To install BRM 7.5:
Go to (http://edelivery.oracle.com/) to a temporary directory (temp_dir) on your system.
Download the upgrade package to temp_dir.
In the temp_dir, enter the following command, which installs the Third-Party software package:
For Solaris and Linux systems:
7.5.0_ThirdParty_platform_32_opt.bin
where platform is solaris or linux.
For AIX systems:
7.5PS1_ThirdParty_aix_32_opt.bin
For HP-UX IA64 systems:
7.5PS5_ThirdParty_hpux_ia64_32_opt.bin
Enter the following command, which installs the Portal base package:
For Solaris and Linux systems:
7.5.0_Portal_Base_platform_32_opt.bin
where platform is solaris or linux.
For AIX systems:
7.5PS1_Portal_Base_aix_32_opt.bin
For HP-UX IA64 systems:
7.5PS5_Portal_Base_hpux_ia64_32_opt.bin
Note:
You can use the -console parameter to run the installation from a command line. To install using a GUI, obtain a GUI application, such as X Windows, and set the DISPLAY environment variable before you install BRM 7.5.Follow the instructions displayed during installation.
Enter the following command, which installs the Pipeline package:
For Solaris and Linux systems:
7.5.0_Pipeline_platform_64_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
Follow the instructions displayed during installation.
Important:
On multischema or multidatabase systems, first perform this task on the primary system and then on the secondary systems.To restrict the schema creation:
Open the BRM_home/setup/pin_setup.values file in a text editor. where BRM_home is the directory in which BRM is installed.
Locate the following entries and set them as NO. The default values are shown here:
$SETUP_CREATE_PARTITIONS = ”NO”; $ENABLE_PARTITION = "YES"; $SETUP_DROP_ALL_TABLES = "YES"; $SETUP_INIT_DB = "YES"; $CREATE_DATABASE_TABLES = "YES";
Save and close the file.
Go to the BRM_home/setup directory.
Enter the following command:
./pin_setup
Check the pin_setup.log file for status and errors.
Note:
After you run pin_setup:The pin_setup.log file erroneously contains the ”Load pin_rerate fields failed” error message. You can ignore this message.
The cm.pinlog file erroneously contains several PIN_ERROC_FLIST and PIN_ERRCLASS_SYSTEM_DETERMINATE error messages. You can ignore these messages.
To ensure that the environment variables are set correctly:
Go to the directory where you installed the BRM 7.5 Third-Party package and source the source.me file.
Bash Shell:
source source.me.sh
C shell:
source source.me.csh
To install the database upgrade package:
Go to temp_dir.
Enter the following command, which installs the BRM database upgrade package:
For Solaris and Linux systems:
7.5.0_PortalBase_Upgrade_74_75_platform_32_opt.bin
where platform is solaris or linux.
For AIX systems:
7.5PS1_PortalBase_Upgrade_74_75_aix_32_opt.bin
For HP-UX IA64 systems:
7.5PS5_PortalBase_Upgrade_74_75_hpux_ia64_32_opt.bin
Note:
You can use the -console parameter to run the installation from a command line. To install using a GUI, obtain a GUI application, such as X Windows, and set the DISPLAY environment variable before you install BRM 7.5.Enter the following command, which installs the Pipeline database upgrade package:
For Solaris and Linux systems:
7.5.0_Pipeline_Upgrade_74_75_platform_32_opt.bin
where platform is solaris or linux.
For AIX systems:
7.5PS1_Pipeline_Upgrade_74_75_aix_32_opt.bin
For HP-UX IA64 systems:
7.5PS5_Pipeline_Upgrade_74_75_hpux_ia64_32_opt.bin
Note:
You can use the -console parameter to run the installation from a command line. To install using a GUI, obtain a GUI application, such as X Windows, and set the DISPLAY environment variable before you install BRM 7.5.Before you run the BRM upgrade script, verify that Oracle Data Manager (DM) is configured correctly. The command that starts the DM ispin_ctl start dm_oracle.
Important:
On multidatabase systems, first perform this task on the primary system and then on the secondary systems.Ensure that Oracle DM starts and stops correctly because upgrade scripts start and stop Oracle DM while making changes to the database schema.
To upgrade the BRM 7.4 Portalbase database schema to BRM 7.5 Portalbase database schema, complete the appropriate steps in this section.
To upgrade the schema on single database systems:
Open the BRM_home/setup/pin_setup.values file in a text editor.
(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 is set with full write permissions.
Set PIN_LOG_DIR to the directory in which you want to create the BRM log files.
In the Information about the databases section, configure the database settings as required.
Set SETUP_INIT_DB to YES.
Save and close the file.
Do one of the following:
For UNIX systems, Go to BRM_HOME/setup/scripts directory and enter the command,pin_74_75_upgrade.pl script from the UNIX prompt:
For HP-UX IA64 systems, enter the command,pin_75ps5_upgrade.pl.
The pin_74_75_upgrade.pl script runs a series of scripts that upgrade BRM 7.4 to BRM 7.5. To upgrade the BRM 7.4 Portalbase database schema to BRM 7.5 Portalbase database schema, complete the appropriate steps in this section.
To upgrade the schema on multidatabase systems, you upgrade the primary database and then upgrade the secondary databases.
To upgrade the schema on the primary database for your BRM system, complete the following on your primary DM machine:
Open the BRM_home/setup/pin_setup.values file in a text editor.
(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.
In the Information about the databases section, configure the following database settings as required for your primary database.
$MAIN_DB{'alias'} = ( $ENV{'ORACLE_SID_PIN'} or $ENV{'ORACLE_SID'} );
$MAIN_DB{'user'} = "USERNAME";
$MAIN_DB{'password'} = "PASSWORD";
$MAIN_DB{'Database'} = "DATABASE_NAME";
Set SETUP_INIT_DB to YES.
Save and close the file.
Do one of the following:
For UNIX systems, go to BRM_home/setup/scripts directory and enter the command, pin_74_75_upgrade.pl script on your primary DM machine:
For HP-UX IA64 systems, run the command, pin_75ps5_upgrade.pl .
The DBMS_SNAPSHOT.refresh command is required for multidatabase systems only.
Note:
Do not perform this step for multischema systems running on Oracle 11g databases.% sqlplus login/password@ORACLE_SID SQL> execute DBMS_SNAPSHOT.refresh('CONFIG_BUSINESS_PARAMS_T','F') SQL> exit
where ORACLE_SID is the BRM database alias.
Do the following on your secondary DM machine for each secondary database in your BRM system:
Open the BRM_home/setup/pin_setup.values file in a text editor.
Enter the number of the secondary database to upgrade:
$DM_ORACLE{'db_num'}
In the Information about the databases section, configure the database settings for your secondary database.
Set SETUP_INIT_DB to YES.
Save and close the file.
Do one of the following:
From the UNIX systems, go to BRM_home/setup/scripts and enter the command, pin_74_75_upgrade.pl.
For HP-UX IA64 systems, enter the command, pin_75ps5_upgrade.pl
To upgrade the Pipeline Manager database schema:
Important:
Run the database upgrade script on the secondary databases and then on the primary database.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.
Set the following values:
$PIN_HOME = "/opt/portal/7.5"; $PIN_LOG_DIR = "/var/portal/7.5"; $PIN_TEMP_DIR = "/tmp"; $PIN_SHARED_DIR = "/opt/portal/7.5"; $PIN_VERSION = "7.5";
Set $PIPELINE_TBLSPACE to the tablespace where you want to create pipeline database objects.
In the Information about the databases section, configure the database settings as required.
Save and close the file.
Do one of the following:
From the UNIX systems, go to BRM_home/setup/scripts and enter the command, pin_74_75_upgrade.pl.
For HP-UX IA64 systems, enter the command, pin_75ps5_upgrade.pl
Update the value for the AccessLib registry entry in the registry files for Pipeline Manager. To do so, if you are using Oracle 10g change the value from oci10g63 to oci10g72, if you are using Oracle 11g change the value from oci10g63 to oci11g72 in the following modules.
Login
LoginInfranet
LoginQueue
The registry files containing these modules are located in Pipeline_home/conf directory. The files are wireless.reg, wirelessRealtime.reg, rerating.reg, roaming.reg, and so on.
When you install client applications, be sure to update the BRM 7.5 Infranet.properties and INI files with any 7.5 customizations.
Important:
You must upgrade all client applications and optional components to BRM 7.5.To upgrade custom client applications, recompile them with BRM 7.5 libraries. See "Updating Custom Applications" for more information.
Install the optional components that you plan to use in BRM 7.5; foe example, CSM Manager.
If you had IMDB Cache Manager installed in BRM 7.4, you must update the Oracle schema for use with IMDB Cache Manager version 2.
To do so, complete the following steps:
Install IMDB Cache. See "Installing IMDB Cache".
Install IMDB Cache Manager version 2. See "Installing IMDB Cache Manager Version 2".
Re-create the data store in IMDB Cache Manager version 2. See "Re-creating the Data Store in IMDB Cache Manager Version 2".
Reestablish connections to your BRM system. See "Reestablishing Connections to BRM".
AAA Gateway and Diameter Manager are no longer supported in BRM 7.5.
Install Oracle Communications Online Mediation Controller by completing the steps described in Oracle Communications Service Broker Online Mediation Controller Implementation Guide at the following location:
Complete the steps in this section that are appropriate for your BRM 7.5 environment.
If you use Pipeline Manager in BRM 7.5:
Open BRM_home/sys/dm_ifw_sync/pin.conffile in a text editor.
Set the following values:
dm_ifw_sync sm_database DATABASE_NAME or DATABASE_SID dm_ifw_sync sm_id USERNAME dm_ifw_sync sm_pw PASSWORD
Save and close the file.
To verify that the IFW_SYNC_QUEUE queue is created in the required (BRM or Pipeline) database:
Enter the following command to go to the required directory:
cd $PIN_HOME/sys/dm_ifw_sync/
Provide:
the queue name for the -q parameter
the table name for the -t parameter
the login and password for ORACLE_SID, the Portalbase database
in the following command:
pin_ifw_sync_oracle.pl create -q queue_name -t <queue_table> -l login/password@ORACLE_SID
If you use the pin_rel utility:
Open the BRM_home/apps/pin_rel/Infranet.propertiesfile in a text editor.
Set the following entries:
infranet.rel.dbname = DATABASE_NAME infranet.rel.userid = USERNAME infranet.rel.password = PASSWORD
Save and close the file.
Important:
You must first incorporate customizations on the secondary databases and then on the primary database.Incorporate any customizations you made to your Release 7.4 policy source code, configuration files, invoicing, reports, and general ledger reporting. See "Transferring Customizations to the New Release" for more information.
Ensure that you remove all entries for the pin_virtual_time utility from the configuration files associated with your BRM production system. For more information, see "pin_virtual_time" in BRM Developer's Guide.
This section provides a list of post-upgrade tasks. Some tasks are optional or apply only to certain platforms or system configurations. Be sure to check whether a task is required for your system.
Perform these tasks after you upgrade your BRM system:
If there have been any changes to the configuration associated with the BRM 7.5 pipeline database (such as changes to user name or port), you must update the configuration settings to provide access to Pricing Center. To do so, you must update the /config/pricing_admin object by running the pricing_admin.pl script with the appropriate values.
For more information, see "Granting Administrative Privileges to Pricing Center Users" in BRM Installation Guide.
Important:
On multidatabase systems, first perform this task on the primary system and then on the secondary systems.If your system includes the Synchronization Queue Data Manager, 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 ”Manually Creating a Database Queue on Oracle” in BRM Synchronization Queue Manager.
After you re-create the Oracle AQ database queue, perform these steps:
Update BRM_home/sys/dm_aq/aq_queuenames with the re-created Oracle AQ database queue name.
Restart DM_AQ services.
Important:
On multidatabase systems, first perform this task on the primary system and then on the secondary systems.If your system includes Pipeline Manager, you must reload the event notification configuration file, pin_notify, in the BRM database. For more information, see ”About the Event Notification List” in BRM Developer's Guide.
To load the pin_notify file:
Go to the BRM_home/sys/data/config directory.
Use the following command to run the load_pin_notify utility:
load_pin_notify pin_notify
If you do not run the utility from the directory in which the configuration file is located, include the complete path to the file.
Stop and restart the Connection Manager (CM).
Oracle Communications Online Charging Solution contains the details on restoring the service to your customers. Complete the process that is appropriate for your BRM 7.5 installation.
To roll back this upgrade:
If you had run the upgrade script, keep a copy of the data in your current BRM 7.5 environment.
Create a backup of the BRM 7.5 data: refer to "Backing Up Files".
Important:
Keep these backups in a separate location. Do not overwrite the contents of the 7.4 data you backed up your BRM 7.4 data.Stop all BRM daemons, processes, and managers.
Log in as user pin.
Go to the directory where you installed the Third-Party package and source the source.me file:
Bash shell:
source source.me.sh
C shell:
source source.me.csh
Run the BRM_home/uninstaller/UpgradePackageName/uninstaller.bin program, where UpgradePackageName is the name of the upgrade package you want to uninstall.
Note:
You can use the -console parameter to run uninstall from a command line.This starts a series of interactive prompts.
Follow the instructions on the screen.
If you did not run the upgrade script described in the section "Installing the BRM 7.5 Database Upgrade Package", you have completed the rollback for the upgrade.
If you executed the upgrade script described in the section "Installing the BRM 7.5 Database Upgrade Package", restore the data from the backup of your BRM 7.4 data that you created in "Backing Up Files".