This chapter contains procedures for upgrading from Portal™ release 7.3 to Oracle Communications Billing and Revenue Management (BRM) 7.3.1. It covers BRM on UNIX (HP-UX and Solaris) and Windows platforms.
Important:
Before performing this upgrade see the BRM 7.3.1 upgrade documentation for information on how to plan, prepare for, and test your upgrade.If you are installing BRM for the first time, see the BRM 7.3.1 installation documentation.
For uninstall information, see "Uninstalling Portal 7.3 Applications".
There are two prerequisite 7.3 patches, 5835756 and 5903622, and the 7.3.1 upgrade patch itself, 6498580. Download these patches from the Oracle MetaLink Web site to a temporary directory on your system.
The 7.3.1 upgrade patch, 6498580, installs five components: 32-bit_Portal_Base, Portal_SDK, Pipeline, Pipeline_TDK, and TIMOS. The installer identifies Portal components already installed in your environment and upgrades them to the BRM 7.3.1 release. During installation, you will be prompted to designate directories for the 32-bit_Portal_Base and Portal_SDK components.
See the patch README file for a list of affected files.
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.
Unless otherwise noted, all steps apply to a single-database 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 Portal 7.3:
Stop all Portal 7.3 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 on.
Users include customers, client applications, customer service representatives (CSRs), and so on.
Before installing the current patch package, back up your Portal 7.3 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.3.1 files after installing BRM 7.3.1.
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 Portal 7.3 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 Portal 7.3 tables. This helps to restore individual tables, if necessary.
Download and install Portal 7.3 patches 5835756 and 5903622 for your platform, if you have not already done so. These patches are available from the Portal 7.3 patch page on the Oracle MetaLink Web site. Follow the installation instructions in the README file downloaded with the patches.
To install the JDK, perform these steps:
Rename the ThirdParty directory; for example, for UNIX: /opt/portal/7.3/ThirdPartyApps to /opt/portal/7.3/ThirdPartyAppsOld.
Windows: The default installation path is:
C:\Program Files\Common Files\Portal Software\ThirdParty
UNIX: The default installation path is:
/opt/portal/ThirdParty
Install the BRM 7.3.1 Third-Party package in the default location.
Before installing the upgrade patches, ensure the environment variables are set correctly:
Go to the directory where you installed the Third-Party package.
Initialize the source.me script:
Bash shell:
% source source.me.sh
C shell:
% source source.me.csh
Ensure that you install RPM packages in the correct numeric sequence.
To install the upgrade patch in an ISMP environment, perform these steps:
Download patch 6498580 from the Oracle MetaLink Web site to a temporary directory (temp_dir) on your system.
Go to temp_dir and install the patch package by entering the package name. Use this syntax:
% PatchPackageName.bin
where PatchPackageName is the following:
7.3.1_6498580_Portal_Base_platform_32_opt for upgrading Portal base plus any Portal optional components installed on your system.
7.3.1_6498580_PCM_SDK_platform_32_dbg for upgrading PCM SDK.
7.3.1_6498580_Portal_SDK_platform_32_dbg for upgrading BRM SDK.
7.3.1_6498580_Pipeline_platform_64_opt for upgrading Pipeline Manager.
7.3.1_6498580_Timos_platform_64_opt for upgrading TIMOS Data Manager.
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.3.1.If you upgraded both Portal base and Resource Reservation Manager from 7.3 to 7.3.1, you must reorganize the entries in your Connection Manager (CM) pin.conf file. You must move the fm_reserve_pol entry to just after the fm_reserve entry, as shown below:
- cm fm_module BRM_Home/lib/fm_reserve.so fm_utils_config fm_utils_init pin - cm fm_module BRM_Home/lib/fm_reserve_pol.so fm_reserve_pol_config - pin
If you upgraded from Portal SDK 7.3 to BRM SDK 7.3.1, you must manually remove the Portal_Home/source/sys/fm_gprs_pol directory and its contents from your system. The files in this directory are for GPRS Manager 2.0, which was obsoleted in Portal 7.3. This directory was incorrectly created during the Portal SDK 7.3 installation and can cause compilation errors in BRM SDK 7.3.1.
To install the patches in a RPM environment, perform these steps:
Download patch 6498580 from the Oracle MetaLink Web site to a temporary directory (temp_dir) on your system.
Merge the patch RPM files with their corresponding Portal packages. Use this syntax for each merge:
% PSC_Home/tools/pin_repackage.sh AbsolutePath/PortalPackageName.rpm AbsolutePath/PatchPackageName.rpm >>& pin_repackage.log
where PortalPackageName is the file name for the original 7.3 package, and PatchPackageName is the name of the 7.3.1 patch package.
Patch_Portal_Base-7.3-1.6498580.platform for upgrading Portal base plus any Portal optional components installed on your system.
Patch_Pipeline-7.3-1.6498580.platform for upgrading Pipeline Manager.
Patch_Timos-7.3-1.6498580.platform for upgrading TIMOS Data Manager.
Each new merged package will have the same name as the Portal package, except for the version numbers. The first part of the new package version number is incremented by one, and the second part of the version number is taken from the patch package. For example, if you merge Portal_Base-7.3-11.1234.sparc64.rpm with Patch_Portal_Base-7.3-1.6498580.sparc64.rpm, the resulting merged package name is Portal_Base-7.3-12.6498580.sparc64.rpm.
Move the merged packages to the BRM_Home repository:
% mv MergedRPMPackageFile BRM_Home/webapps/repository
Run the createrepo command:
% BRM_Home/webapps/repository/createrepo `pwd`
If you upgraded both Portal and Resource Reservation Manager from 7.3 to 7.3.1, you must reorder the entries in your Connection Manager (CM) pin.conf file. You must move the fm_reserve_pol entry to just after the fm_reserve entry, as shown below:
- cm fm_module BRM_Home/lib/fm_reserve.so fm_utils_config fm_utils_init pin - cm fm_module BRM_Home/lib/fm_reserve_pol.so fm_reserve_pol_config - pin
Important:
First run the database upgrade script on the secondary databases and then on the primary database.The pin_73patch_731_upgrade.pl script runs a series of scripts that upgrade the Release 7.3 database to BRM 7.3.1.
To upgrade your database schema:
Run the pin_73patch_731_upgrade.pl script from the UNIX or DOS prompt:
% cd BRM_Home/setup/scripts % perl pin_73patch_731_upgrade.pl
Update secondary databases using the same procedure as the primary database:
Go to BRM_Home/setup.
Open the pin_setup.values file.
Find the $DM_ORACLE{'db_num'} entry.
Change db_num to the number of the secondary database to upgrade.
Run the pin_73patch_731_upgrade.pl script from the UNIX or DOS prompt:
% cd BRM_Home/setup/scripts % perl pin_73patch_731_upgrade.pl
When you install client applications, be sure to update the BRM 7.3.1 Infranet.properties and INI files with any 7.3 customizations.
Important:
You must upgrade all client applications and optional components to BRM 7.3.1.To upgrade custom client applications, recompile them with BRM 7.3.1 libraries. For more information, see "Updating Custom Applications".
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.3.1 policy source code, configuration files, invoicing, reports, and general ledger reporting. For more information, see "Transferring Customizations to the New Release".
(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.
Test your upgraded system by running various daily operations on it. Tests include running the ”after” version of the reports you ran before beginning the upgrade. For more information, see "Testing Your Upgraded System".
To uninstall any Portal 7.3 application:
Go to the uninstaller directory located in the default installation directory (Portal_Home or IFW_Home):
Windows: C:\Portal
UNIX: /opt/portal/7.3 or /opt/portal/ifw
Run the uninstaller
(Windows) uninstaller.exe
(UNIX) uninstaller.bin with the following options:
uninstaller.bin -is:javahome Renamed73ThirdPartyLocation/jre
(UNIX) To set up the default JRE to run the uninstaller, use the following command:
C shell:
Portal_Home/ThirdPartyApps/source.me.csh
Bash shell:
Portal_Home/ThirdPartyApps/source.me.sh