19 Upgrading BRM and Pipeline Manager

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 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.

About the 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.

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)

System Configurations Supported by This Upgrade

This upgrade supports the system configurations listed under "BRM Compatibility Matrix" in BRM Installation Guide.

Oracle In-Memory Database (IMDB) Cache Manager

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.

When you are asked to install IMDB Cache Manager in the procedure outlined in this chapter, install IMDB Cache Manager, version 2.

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 this software, see the installation or upgrade guide at Oracle Database Documentation Library 11g R2 documentation website.

Online Charging Connectivity and BRM 7.5

The AAA Gateway, Radius Manager, and Diameter Manager are no longer supported in BRM 7.5. You must migrate all current configurations/customizations on AAA Gateway, Radius Manager, and Diameter Manager for network connectivity to Oracle Communications Online Mediation Controller (OCMC).

See Oracle Communications Online Charging Solution document 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 in Oracle Communications Service Broker 6.0 documentation.

Tasks Involved in the BRM 7.4-to-7.5 Upgrade Process

This section provides a list of 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. Be sure to check whether a task is required for your system.

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".
Creating a complete backup of your BRM 7.4 data. See "Creating a Complete Backup of Your BRM 7.4 Data".
Create a new schema in BRM 7.5. See "Creating Your BRM 7.5 Database"
Install BRM 7.5 without creating a schema. See "Installing BRM 7.5 (Without the Create Schema Option)".
Import your data BRM 7.4 data. See "Importing Your BRM 7.4 Data"
Set the environment variables. See "Setting the Environment Variables".
Install the upgrade package. See "Installing the BRM 7.5 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 Portalbase database schema to the BRM 7.5 schema. See "Upgrading the Portalbase 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".
Add optional components. See "Adding 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".

Preparing for the Upgrade to BRM 7.5

This section describes the steps you must complete before starting the upgrade.

Shutting Down the Current Instance

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.

Turning Off BRM Service Authentication and Authorization

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 the AAA Gateway Manager in your BRM 7.4 environment, see Oracle Communications Billing and Revenue Management 7.4 Documentation.

About Providing Access to Services during This Upgrade

Important:

You cannot provide your customers access to your BRM system while the upgrade is in progress.

This temporary stoppage of service is due to the following reasons:

BRM 7.5 does not support AAA gateway with Radius Manager. It requires a migration to Oracle Communications Online Mediation Controller (OCMC).
The migration process does not allow any traffic to be processed during the migration.

See Oracle Communications Online Charging Solution document for details on the migration process.

Creating a Backup of the IMDB Cache Data

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, then, at this point in the upgrade process, you must create a backup of the existing IMDB Cache data.

To do so,

Complete the steps described under "Preparing for the Upgrade to IMDB Cache Manager Version 2" in "Upgrading IMDB Cache Manager from Version 1 to Version 2".

Important:
Complete the steps described in that section only.
Proceed to "Creating a Complete Backup of Your BRM 7.4 Data" in this chapter, the next step in the process to upgrade your BRM system.

Creating a Complete Backup of Your BRM 7.4 Data

Creating a complete backup of the data in your BRM 7.4 environment requires the following actions to be performed in your BRM 7.4 environment:

Backing Up Files
Backing Up Your BRM 7.4 Database
Exporting Your BRM 7.4 Data

Backing Up Files

Back up your BRM 7.4 files.

Important:

If you are performing the upgrade on systems with distributed or HA architecture, back up the files on every node.

In particular, ensure that you back up the following files:

All files customized for BRM 7.4 including any associated source code
Registry files
Policy files
pin.conf
pin_setup.values
Infranet.properties
All other files that contain any customizations used in BRM 7.4

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".

Backing Up Your BRM 7.4 Database

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 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.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 the Oracle Database Utilities document.

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.

Exporting Your BRM 7.4 Data

Export the data in your BRM 7.4 Database. Use the exp utility to create the backup file.

Important:

On multischema or multidatabase systems, first perform this task on the primary system and then on the secondary systems.

Additionally, record the system time of each backup file so that you can match that time entry to import the backup data into the appropriate system in BRM 7.5.

For example, the following command exports the data stored in the Portalbase database:

exp login/password@$ORACLE_SID file=74to75DatabasePortal.dmp log=Portal_exp.log

where login and password are associated with the Portalbase database.

The following command exports the data stored in the Pipeline database:

exp login/password@$ORACLE_SID file=74to75DatabasePipeline.dmp log=Pipeline_exp.log

where login and password are associated with the Pipeline database.

For more information on the exp utility, see the discussion on export and import utilities in the appropriate version of the Oracle Database Utilities document.

Important:

Store this backup in a safe location. The exported data will be imported back after you install the upgrade and create a new BRM 7.5 schema. See "Importing Your BRM 7.4 Data".

Creating Your BRM 7.5 Database

Important:

On multischema or multidatabase systems, first perform this task on the primary system and then on the secondary systems.

Create a blank BRM database into which you will import the backup you created. For more information, see the description for "Creating your BRM Database" under "Configuring Oracle for BRM" in BRM Installation Guide.

Upgrading to BRM 7.5

This section describes the steps necessary to upgrade to BRM 7.5.

Installing BRM 7.5 (Without the Create Schema Option)

Install BRM 7.5 without the creating the database schema. To do so, edit the pin_setup.values file and turn off the values that create the database schema before you run the pin_setup script.

When you run the pin_setup script updated in this manner, the database is not initialized, database tablespaces and default partitions are not created, and the tables are not dropped. See BRM Installation Guide.

Editing the pin_setup.values File to Restrict Schema Creation

Important:

On multischema or multidatabase systems, first perform this task on the primary system and then on the secondary systems.

To edit the pin_setup.values file,

Go to the BRM_Home/setup directory and open the pin_setup.values file in a text editor.

Locate the following entries and set them as desired. The default values are shown here:

$SETUP_CREATE_PARTITIONS = “NO”;
$ENABLE_PARTITION = "NO";
$SETUP_DROP_ALL_TABLES = "NO";
$SETUP_INIT_DB = "NO";
$CREATE_DATABASE_TABLES = "NO";

Save and close the file.

Running the pin_setup Script

Run the updated pin_setup script from 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 cm.pinlog file erroneously contains several PIN_ERROC_FLIST and PIN_ERRCLASS_SYSTEM_DETERMINATE error messages. You can safely ignore these messages.

Importing Your BRM 7.4 Data

After you have successfully created a new schema, import the backup data you created in "Exporting Your BRM 7.4 Data".

Important:

On multischema or multidatabase systems, first perform this task on the primary system and then on the secondary systems.

When you import the backup data (you created in "Exporting Your BRM 7.4 Data"), check the system time of each backup file to ensure that the data is imported into the appropriate system in BRM 7.5.

Use the imp utility to import the backup data. For example:

The following command imports the data from the backup of the Portalbase database:

imp login/password@$ORACLE_SID file=74to75DatabasePortal.dmp log=imp.log

where login and password are associated with the newly-created Portalbase database.

The following command imports the data from the backup of the Pipeline database:

imp login/password@$ORACLE_SID file=74to75DatabasePipeline.dmp log=Pipeline_imp.log

where login and password are associated with the newly-created Pipeline database.

For more information on the imp utility, see the discussion on export and import utilities in the appropriate version of the Oracle Database Utilities document.

Setting the Environment Variables

Before installing the upgrade, ensure that the environment variables are set correctly. To do so:

Go to the directory where you installed the BRM 7.5 Third-Party package.
Initialize the source.me script:
- For Bash Shell:
```
% source source.me.sh
```
- For C shell:
```
% source source.me.csh
```

Installing the BRM 7.5 Upgrade Package

To install the upgrade package:

Download the main upgrade package from the Oracle Software Delivery Cloud Web site (http://edelivery.oracle.com/) to a temporary directory (temp_dir) on your system.
Go to this temp_dir directory
Install the Portalbase upgrade package with the following command:
- For Solaris and Linux systems:
```
7.5.0_PortalBase_Upgrade_74_75_platform_32_opt.bin
```
  where platform is the appropriate platform.
- For AIX systems:
```
7.5PS1_PortalBase_Upgrade_74_75_aix_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.
Install the Pipeline upgrade package with the following command:
- For Solaris and Linux systems:
```
7.5.0_Pipeline_Upgrade_74_75_platform_32_opt.bin
```
  where platform is the appropriate platform.
- For AIX systems:
```
7.5PS1_Pipeline_Upgrade_74_75_aix_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.

Upgrading Your Data to BRM 7.5

This sections describes the tasks to be completed to upgrade your data to BRM 7.5:

Pointing the BRM 7.5 Installation to the New Database Schema

Before you run the Portalbase upgrade script, verify that the Oracle data manager (DM) is configured correctly as this DM provides the interface to the BRM 7.5 database. Verify that Oracle DM is configured properly by starting dm_oracle.

Important:

On multidatabase systems, first perform this task on the primary system and then on the secondary systems.

You should ensure that Oracle DM starts and stops correctly because upgrade scripts start and stop Oracle DM while making changes to the database schema.

For information on pin.conf and infranet.properties files, see "Using Configuration Files to Connect and Configure Components" in BRM System Administrator's Guide; and for information on configuring pin_setup.values, see "Installing BRM" in BRM Installation Guide

Upgrading the Portalbase Database Schema to the BRM 7.5 Schema

Important:

On multidatabase systems, first perform this task on the primary system and then on the secondary systems.

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.

Upgrading the Schema on Single Database Systems

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:

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.

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_74_75_upgrade.pl scripts from the UNIX prompt:
```
% cd BRM_Home/setup/scripts
% perl pin_74_75_upgrade.pl
```
where BRM_Home is the directory where BRM 7.5 is installed.

Upgrading the Schema on Multiple Database Systems

To upgrade the schema on multidatabase systems, you upgrade the primary database and then 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 two 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";

Save and close the file.
From the UNIX prompt, run the pin_74_75_upgrade.pl scripts on your primary DM machine:
```
% cd BRM_Home/setup/scripts
% perl pin_74_75_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.

Run the following commands on multidatabase systems:
```
% 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.

Perform 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 for the entry 'db_num' in:
```
$DM_ORACLE{'db_num'}
```
In the Information about the databases section, configure the database settings for your secondary database.
Save and close the file.
From the UNIX prompt, run the pin_74_75_upgrade.pl scripts on the secondary DM machine:
```
% cd BRM_Home/setup/scripts
% perl pin_74_75_upgrade.pl
```

Upgrading the Pipeline Manager Database Schema to the BRM 7.5 Schema

Complete the following steps to upgrade the Pipeline Manager database schema.

Important:

Run the database upgrade script on the secondary databases and then on the primary database.

Go to the Pipeline_Home directory where Pipeline_Home is the directory in which the Pipeline Manager is installed.
Open the Pipeline_Home/upgrade/pipeline_upgrade.cfg file.

Set the value of the PIN_TEMP_DIR parameter to the directory where the temporary files must be created. To do so, set the following values:

$PIN_HOME = "/opt/portal/7.4";
$PIN_LOG_DIR = "/var/portal/7.4";
$PIN_TEMP_DIR = "/tmp";
$PIN_SHARED_DIR = "/opt/portal/7.4";
$PIN_VERSION = "7.4";

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_74_75_pipeline_upgrade.pl script from the UNIX prompt:

pin_74_75_pipeline_upgrade.pl
% cd Pipeline_Home/upgrade/scripts
% perl pin_74_75_pipeline_upgrade.pl

Update the value for AccessLib registry entry in the registry files for the Pipeline Manager. To do so, change its value from oci10g63 to oci10g72 in each of 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.

Completing the Upgrade to BRM 7.5

This section describes the tasks required to complete the upgrade process.

Installing the BRM 7.5 Client Applications

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.

Adding Optional Components

At this point, add the optional components that you plan to use in BRM 7.5. The optional components include migrating (from Radius Manager) to Oracle Communications Service Broker Online Mediation Controller, installing or upgrading to IMDB version 2, and so on.

Note:

This section lists only some of the optional components. Complete the necessary steps to add other optional components (associated with and supported by BRM) that you require. Configure their connections to your BRM system appropriately.

Completing the Upgrade from IMDB Cache Manager Version 1 to Version 2

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 the 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".

Installing OCMC for Authentication/Authorization in BRM 7.5

AAA Gateway, Radius Manager or Diameter Manager are no longer supported in BRM 7.5.

Install Oracle Communications Service Broker Online Mediation Controller by completing the steps described in Oracle Communications Service Broker Online Mediation Controller Implementation Guide at the following location:

http://docs.oracle.com/

Other Database Configurations

Complete the steps in this section that are appropriate for your BRM 7.5 environment.

Update DM_IFW_SYNC Queue Database Configuration Setting

This step is required if you use Pipeline Manager in BRM 7.5. IFW_SYNC is used for synchronization between Portalbase and Pipeline database. To update the DM_IFW_SYNC queue:

Go to the BRM_Home/sys/dm_ifw_sync/ directory, where BRM_Home is where BRM 7.5 is installed.
Open pin.conf file.
Update the settings for sm_database, sm_userid, and sm_password to reflect the new values associated with the updated BRM 7.5 Portalbase database.
```
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.

Verify IFW_SYNC_QUEUE Queue in the Database

Verify that the IFW_SYNC_QUEUE queue is created in the required (Portalbase or Pipeline) database.

If the IFW_SYNC_QUEUE does not exist in the database, re-create IFW_SYNC_QUEUE. This step is required if you use Pipeline Manager. IFW_SYNC_QUEUE is used for synchronization between Portalbase and Pipeline database.

To create IFW_SYNC_QUEUE:

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
```

Update the Default Settings for the pin_rel Utility

If you use the pin_rel utility, complete the following steps to verify that the database configurations settings are updated:

Go to the BRM_Home/apps/pin_rel/ directory, where BRM_Home is where BRM 7.5 is installed.
Open the Infranet.properties file.

Check and, if necessary, update the entries for the following:

infranet.rel.dbname = DATABASE_NAME
infranet.rel.userid = USERNAME
infranet.rel.password = PASSWORD

Save and close the file.

Restoring Customizations

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.

BRM Production Systems and pin_virtual_time Configuration Entries

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.

Post-upgrade Procedures

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:

Updating Pipeline Manager Configuration Data
Creating an Oracle AQ Database Queue
Loading the pin_notify File

Updating Pipeline Manager Configuration Data

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.

Creating an Oracle AQ Database Queue

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.

Loading the pin_notify File

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).

Restoring Service to Your Customers

The Oracle Communications Online Charging Solution document contains the details on the steps that must be completed to restore service to your customers. Complete the process that is appropriate for your BRM 7.5 installation.

Rolling Back an Upgrade

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, by using the steps described in "Creating a Complete Backup of Your BRM 7.4 Data" as a reference.

Important:
Keep these backups in a separate location. Do not overwrite the contents of the 7.4 data you created when you originally completed the step described in "Creating a Complete Backup of 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 execute the upgrade script described in the section "Installing the BRM 7.5 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 Upgrade Package" you must import the data as described in "Importing Your BRM 7.4 Data".