This chapter contains procedures for upgrading from Oracle Communications Billing and Revenue Management (BRM) 7.3.1 to BRM 7.4. It covers BRM on HP-UX IA64, Linux, AIX, and Oracle Solaris.
Important:
Before performing this upgrade, see "About Upgrading BRM Releases" for information on how to plan, prepare for, and test your upgrade.There is one overlay upgrade patch: 7594327. This overlay upgrade patch includes the changes that are necessary for upgrading BRM 7.3.1 to BRM 7.4. It upgrades the following components:
32-bit BRM
BRM SDK
32-bit Third-Party software
BRM SNMP
Pipeline Manager
Pipeline PDK
TIMOS Data Manager
The upgrade identifies BRM components already installed in your environment and upgrades them to BRM 7.4.
Refer to the upgrade patch README for more information.
This section provides a list of 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.
Caution:
When upgrading a multidatabase system, perform each task on both the primary and secondary system.Perform these tasks when upgrading your BRM system:
To shut down BRM 7.3.1:
Stop all BRM 7.3.1 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.
Ensure that no users are logged in.
Users include customers, client applications, customer service representatives (CSRs), and so on.
Back up your BRM 7.3.1 files. In particular, ensure that you back up all customized files, including source code, policy files, pin.conf, pin_setup.values, and Infranet.properties files. Copy your customizations from these files to the BRM 7.4 files after upgrading to BRM 7.4.
Important:
Back up all the customized load utility files to a different location. After the upgrade is completed and services start running, restore the customized load utility files to their original location. Run the load utility applications to restore the customized entries in the database.For more information, see "Transferring Customizations to the New Release".
To maintain a controlled environment for pre-upgrade testing, cut off interaction between your BRM system and your customers.
For information on providing access to services while authentication is turned off, see "About Maintaining Access to the BRM System during the Upgrade Process".
For information on the BRM authentication module, see BRM RADIUS Manager in Oracle Communications Billing and Revenue Management (BRM) Documentation.
Make a complete offline backup of your BRM 7.3.1 database and ensure that the backup is completely valid and usable. See your database software documentation for more information on performing full database backups.
In addition to the backup, use the Oracle export utility to export all BRM 7.3.1 tables. This helps to restore individual tables, if necessary.
Before installing the upgrade, ensure the environment variables are set correctly:
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
To install the overlay upgrade patch:
Go to the My Oracle Support Web site:
and download patch 7594327 to a temporary directory (temp_dir) on your system.
Go to temp_dir and run the following command, which installs the overlay upgrade patch software:
% PatchPackageName.bin
where PatchPackageName is:
7.4_7594327_Portal_Base_platform_32_opt for upgrading BRM plus any BRM optional components installed on your system.
7.4_7594327_Portal_SDK_platform_32_opt for upgrading the BRM SDK.
7.4_7594327_ThirdParty_Upgrade_platform_32_opt for upgrading Third-Party software (this will install the RDA tool). For more information, see ”Collecting Diagnostic Information by Using RDA” in BRM System Administrator's Guide.
7.4_7594327_SNMP_3rd_party_tool_platform_64_opt for upgrading BRM SNMP.
7.4_7594327_Pipeline_platform_64_opt for upgrading Pipeline Manager.
7.4_7594327_Pipeline_PDK_platform_64_opt for upgrading the Pipeline PDK.
7.4_7594327_Timos_platform_64_opt for upgrading TIMOS Data Manager.
where platform is hpux_ia64, solaris, linux, or aix.
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.4.Important:
First run the database upgrade script on the secondary databases and then on the primary database.Note:
If your base system has TIMOS DM installed, before running the upgrade script, install the TIMOS DM upgrade package (7.4_7594327_Timos_platform_64_opt, where platform is hpux_ia64, solaris, linux, or aix.)The pin_731_74_upgrade.pl script runs a series of scripts that upgrade BRM 7.3.1 to BRM 7.4.
To upgrade your BRM database schema:
Open the BRM_Home/setup/pin_setup.values file.
(Optional) Set the values of the following parameters:
PIN_TEMP_DIR to the directory in which you want to create the temporary files.
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.
Save and close the file.
Run the pin_731_74_upgrade.pl script from the UNIX prompt:
% cd BRM_Home/setup/scripts % perl pin_731_74_upgrade.pl
Important:
First run the database upgrade script on the secondary databases and then on the primary database.To upgrade the Pipeline Manager database schema:
Open the Pipeline_Home/upgrade/pin_setup.values file.
Set the value of the PIN_TEMP_DIR parameter to the directory in which want to create the temporary files.
Point $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.
Run the pin_731_74_pipeline_upgrade.pl script from the UNIX prompt:
pin_731_74_pipeline_upgrade.pl % cd Pipeline_Home/upgrade/731_74 % perl pin_731_74_pipeline_upgrade.pl
Update the AccessLib registry entry from oci10g61 to oci10g63 for Login, LoginInfranet, and LoginQueue modules. This includes files such as wireless.reg, rerating.reg, roaming.reg, and other registry files located in Pipeline_Home/conf directory.
Important:
First install the overlay upgrade patch on the secondary database and then on the primary database.Go to BRM_Home/setup/pin_setup.values file.
Change the $DM_ORACLE{'db_num'} entry, where db_num is the number of the secondary database to upgrade.
Save and close the file.
Run the pin_731_74_upgrade.pl script from the UNIX prompt:
% cd BRM_Home/setup/scripts % perl pin_731_74_upgrade.pl
When you install client applications, be sure to update the BRM 7.4 Infranet.properties and INI files with any 7.3.1 customizations.
Important:
You must upgrade all client applications and optional components to BRM 7.4.To upgrade custom client applications, recompile them with BRM 7.4 libraries.See "Updating Custom Applications" for more information.
Important:
First incorporate customizations on the secondary databases and then on the primary database.Incorporate any customizations you made to your Release 7.3.1 policy source code, configuration files, invoicing, reports, and general ledger reporting. See "Transferring Customizations to the New Release" for more information.
(Production system only) Ensure that you remove all entries for the pin_virtual_time utility from the configuration files.
See ”Using the Authentication and Authorization Modules” in BRM RADIUS Manager.
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 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.
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.
Run the following command:
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).
Remove the unused procedures and packages from the BRM database.
To remove the unused procedures and packages from the BRM database:
Enter the following command, which opens SQL*Plus:
sqlplus login/password@ORACLE_SID
where:
login is the user name for the database schema you are updating.
password is the password for the specified user name.
ORACLE_SID is the BRM database alias of the schema you are updating.
Enter the following commands in the given order:
SQL>drop procedure DROP_PROCEDURES; SQL>drop package EVENT_PARTITION;
The unused procedures and packages are removed.
Enter the following command, which exits SQL*Plus:
SQL>exit
For AIX only, you must remove or rename the xml.jar file from the JRE bundle to avoid a conflict with a Third-Party package.
To remove or rename the xml.jar file:
Go to the BRM_Home/opt/portal/7.4/ThirdPartyApps/jre/1.5.0/lib directory.
Remove or rename the xml.jar file.
To uninstall any upgrade package:
Back up the BRM database.
Back up all the BRM files.
Stop all BRM daemons, processes, and managers.
Log in as user pin.
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
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 uninstall from a command line.This starts a series of interactive prompts.
Follow the instructions on the screen.