1. Installation Guide
  2. Installing BRM
  3. Installing Multiple BRM Instances on One System for Testing

12 Installing Multiple BRM Instances on One System for Testing

Learn how to help your developers test their system by installing and setting up multiple Oracle Communications Billing and Revenue Management (BRM) instances.

Topics in this document:

Installing and Configuring Multiple Instances of BRM on One Machine

You can install multiple instances of BRM on one machine to reduce the amount of hardware needed to test the BRM software. To set up multiple instances of BRM on one machine, perform the following steps:

  1. Creating Multiple Users

  2. Installing and Configuring the Oracle Database

  3. Installing Multiple Instances of BRM

  4. Configuring Each BRM Instance

Creating Multiple Users

Create a user for each instance of BRM you want to install. For example, to install four instances of BRM, create users pin1, pin2, pin3, and pin4.

To create multiple users:

  1. Log in as root: 

    % su - root

  2. Create a group. For example, run the following command to create the group pin: 

    # groupadd -g 9500 pin

  3. Create each user. For example, run the following commands to create four users:

    # useradd -g pin -s /bin/csh -d BRM_home/pin1 pin1
# useradd -g pin -s /bin/csh -d BRM_home/pin2 pin2
# useradd -g pin -s /bin/csh -d BRM_home/pin3 pin3
# useradd -g pin -s /bin/csh -d BRM_home/pin4 pin4

  4. Create a password for each user.

Installing and Configuring the Oracle Database

Before you install BRM, you must install the Oracle database and configure it for multiple instances of BRM. Install and configure the Oracle database according to the instructions in "Installing and Configuring the Oracle Database", except create your BRM tablespaces and BRM users as described in this section. You can also create the BRM tablespaces and BRM users during the BRM server installation.

(Optional) Creating Tablespaces for Each User

You can create unique data, index, and temporary tablespaces for each instance of BRM you install. The examples in this document use the following tablespaces:

  • pinN00 (for data)

  • pinxN00 (for indexes)

  • PINTEMPN (for a temporary tablespace)

  1. Create a directory for the tablespaces, such as /u02/oradata/pindb.

    This directory is referred to as table_location.

  2. Connect to the Oracle database by using SQL*Plus:

    % sqlplus system@databaseAlias
Enter password: password

  3. Create a data, index, and temporary tablespace for each BRM user.

    Repeat the following commands for each BRM instance:

    SQL> create tablespace pin00 datafile 'table_location/pin00.dbf'
     size 600M reuse autoextend on extent management 
     local uniform size 64K segment space management 
     auto;
  
Tablespace created.
  
SQL> create tablespace pinx00 datafile 'table_location/pinx00.dbf'
     size 400M reuse autoextend on extent management 
     local uniform size 64K segment space management
     auto;
  
Tablespace created.
    
SQL> create temporary tablespace pintemp tempfile
     'table_location/PINTEMP.dbf' size 100M reuse autoextend on;
  
Tablespace created.
(Optional) Creating Multiple BRM Users

Create the BRM users who can access the Oracle database. The examples in this document use pinN, but you can use another naming scheme.

  1. Connect to the Oracle database by using SQL*Plus:

    % sqlplus system@databaseAlias
Enter password: password

  2. Perform the following for each instance of BRM you will install:

    SQL> create user pinN identified by password;
  
User created.
  
SQL> grant resource, connect to pinN;
  
Grant succeeded.
  
SQL> alter user pin default tablespace pinN00;
  
User altered.
  
SQL> alter tablespace PINTEMP temporary;
  
Tablespace altered.
  
SQL> alter user pin temporary tablespace PINTEMP;
  
User altered.

  3. Type exit to exit SQL*Plus.

Installing Multiple Instances of BRM

Note:

If you already installed the product, you must uninstall its features before reinstalling them.

To install multiple instances of BRM on one machine:

  1. Install the PERL libraries and the JRE required to install BRM components.

  2. Log in as user pinN. 

    % su - pinN

  3. Go to the directory in which you installed the PERL libraries and JRE, and then source the source.me file.

    Caution:

    You must source the source.me file to proceed with installation. Otherwise, “suitable JVM not found" and other error messages appear.

    Bash shell:

    source source.me.sh

    C shell:

    source source.me.csh

  4. Stop all BRM processes. See "Starting and Stopping the BRM System" in BRM System Administrator's Guide.

  5. Install BRM in each instance. See "Installing BRM".

    Note:

    You must log in separately for each instance of BRM that you need to install. For example, log in as pin1 and install the first instance of BRM. Then, log in as pin2 and install the second instance of BRM, and so on.

  6. Go to the directory in which you installed the BRM software, and then source the source.me file:

    Bash shell:

    source source.me.sh

    C shell:

    source source.me.csh

  7. To further configure BRM, such as by changing the default currency and country, edit the BRM_home/setup/pin_setup.values file.

    This file stores the information you provided to the installer and a number of database and add-on component parameters.

Each instance of BRM is installed in the BRM_home/pinN directory, where N represents the instance number. For example, the installation program copies BRM to the following directories when you install four instances of BRM in the default BRM directory, /opt/portal/12.0.0.0.0: 

/opt/portal/12.0.0.0.0/pin1
/opt/portal/12.0.0.0.0/pin2
/opt/portal/12.0.0.0.0/pin3
/opt/portal/12.0.0.0.0/pin4

Configuring Each BRM Instance

Follow these steps for each instance of BRM you want to install on your machine:

  1. Log in as root and change the permissions for the BRM_home/pinN directory and its contents from pin to pinN: 

    % su - root
# cd BRM_home
# chown -R pin pinN

  2. Edit the pin_setup file.

    1. Go to the BRM_home/pinN/setup directory, change permissions for the pin_setup file, and then open the file in a text editor such as vi: 

      % cd BRM_home/setup
% chmod 120000 pin_setup
% vi pin_setup

    2. Save and close the file.

  3. Go to the BRM_home/setup directory and run the pin_setup script: 

    % cd BRM_home/setup
% ./pin_setup

  4. Check the pin_setup.log file for status and errors.

  5. Verify that BRM was installed and set up correctly by creating an account with Billing Care.

  6. Repeat steps 1 through 5 for each instance of BRM you installed on your machine.

Reinitializing the Database

You can reinitialize the BRM database, including tables, indexes, and triggers, and return it to its original condition. You might do this, for example, to clean out a test database.

Note:

When you reinitialize a database, you completely remove existing data from the database. When the data is removed, you cannot restore it. Perform this task only if you are certain you will not need to access any data in the database or you have backed up the data and have confirmed that you can restore it.

Reinitializing BRM Server and Optional Component Data

To reinitialize all BRM data, including data in your core BRM tables and optional component tables, do the following:

  1. Stop all BRM processes. See "Starting and Stopping the BRM System" in BRM System Administrator's Guide.

  2. Edit the pin_setup.values file.

    1. Log in as pin, go to the BRM_home/setup directory, and open the pin_setup.values file in a text editor such as vi: 

      % su - pin
% cd BRM_home/setup
% vi pin_setup.values

    2. Change the $SETUP_DROP_ALL_TABLES and $SETUP_INIT_DB entries to YES: 

      $SETUP_DROP_ALL_TABLES = "YES";
$SETUP_INIT_DB = "YES";

    3. Save and close the file.

  3. Run the pin_setup script: 

    % cd BRM_home/setup
% ./pin_setup

  4. Drop the optional component tables from your database.

  5. Using SQL*Plus, log in to your database as the SYSTEM user and run the following command using the information in Table 12-1: 

    SQL> @path/file_name

    Table 12-1 Optional Component Drop Source File Location and Name

    Optional Component Path File Name

    GPRS Manager

    BRM_home/sys/dd/data

    drop_tables_gprs_oracle.source

    GSM Manager

    BRM_home/sys/dd/data

    drop_tables_service_order_oracle.source

    drop_tables_settlement_oracle.source

    Invoice DM

    BRM_home/sys/dm_invoice/data

    drop_tables.source

    Number Manager

    BRM_home/sys/dd/data

    drop_tables_num_oracle.source

    Rated Event Loader

    BRM_home/sys/dd/data

    drop_tables_rel_oracle.source

    SIM Manager

    BRM_home/sys/dd/data

    drop_tables_sim_oracle.source

    Vertex Manager

    BRM_home/sys/dd/data

    drop_tables_telephony_oracle.source

    Suspense Manager

    BRM_home/sys/dd/data

    drop_tables_suspense_oracle.source

    Services Framework Manager

    BRM_home/sys/dd/data

    drop_tables_telco_oracle.source

    drop_tables_config_accountera_oracle.source

    IP Address Manager

    BRM_home/sys/dd/data

    drop_tables_ip_oracle.source

    drop_tables_apn_oracle.source

  6. Start all BRM processes.

    See "Starting and Stopping the BRM System" in BRM System Administrator's Guide.

All core BRM tables and optional component tables have been dropped from your system. You can start adding test accounts to your database and continue testing.

Reinitializing Optional Component Data Only

To reinitialize data from your optional component tables, but keep the data in your core BRM tables:

  1. Stop the CM and DM processes.

  2. Enable writing of the data dictionary objects in your Oracle DM configuration file:

    1. Open your Oracle DM configuration file (BRM_home/sys/dm_oracle/pin.conf).

    2. Make sure the following entries are set to 1: 

      - dm dd_write_enable_objects  1
- dm dd_write_enable_fields  1
- dm dd_write_enable_BRM_objects  1

    3. Save and close the file.

  3. Stop and restart the CM and Oracle DM processes.

  4. Delete the BRM data dictionary objects for each optional component.

    You can find the data dictionary objects for each component in the files listed in Table 12-2.

    Table 12-2 Optional Component Data Dictionary Drop Source File Location and Name

    Optional Component Path and File Name

    GPRS Manager

    BRM_home/sys/dd/data/dd_objects_gprs.source

    GSM Manager

    BRM_home/sys/dd/data/dd_objects_service_order.source

    BRM_home/sys/dd/data/dd_objects_telco_gsm.source

    BRM_home/sys/dd/data/dd_objects_settlement.source

    BRM_home/sys/dd/data/dd_objects_telco.source

    BRM_home/sys/dd/data/dd_objects_config_accountera.source

    Invoice DM

    BRM_home/sys/dm_invoice/data/dd_objects.source

    Number Manager

    BRM_home/sys/dd/data/dd_objects_num.source

    Rated Event Loader

    BRM_home/sys/dd/data/dd_objects_rel.source

    SIM Manager

    BRM_home/sys/dd/data/dd_objects_sim.source

    Vertex Manager

    BRM_home/sys/dd/data/dd_objects_telephony.source

    Suspense Manager

    BRM_home/sys/dd/data/dd_objects_suspense.source

    IP Address Manager

    BRM_home/sys/dd/data/dd_objects_ip.source

    BRM_home/sys/dd/data/dd_objects_apn.source

    1. Create an flist that contains the POID of the objects you want to delete.

      See "Understanding flists and Storable Classes" in BRM Developer's Guide.

    2. Run the PCM_OP_SDK_DEL_OBJ_SPECS opcode with the input flist you created. For more information, see "Deleting Storable Class Specifications" in BRM Developer's Guide.

  5. Stop the CM and Oracle DM processes.

    See "Starting and Stopping the BRM System" in BRM System Administrator's Guide.

  6. Drop the optional component tables from your database.

  7. Using SQL*Plus, log in to your database as the SYSTEM user and run the following command using the values in Table 12-3: 

    SQL> @path/file_name

    Table 12-3 Optional Component Drop Source File Location and Name

    Optional Component Path File Name

    GPRS Manager

    BRM_home/sys/dd/data

    drop_tables_gprs_oracle.source

    GSM Manager

    BRM_home/sys/dd/data

    drop_tables_service_order_oracle.source

    drop_tables_settlement_oracle.source

    Invoice DM

    BRM_home/sys/dm_invoice/data

    drop_tables.source

    Number Manager

    BRM_home/sys/dd/data

    drop_tables_num_oracle.source

    Rated Event Loader

    BRM_home/sys/dd/data

    drop_tables_rel_oracle.source

    SIM Manager

    BRM_home/sys/dd/data

    drop_tables_sim_oracle.source

    Vertex Manager

    BRM_home/sys/dd/data

    drop_tables_telephony_oracle.source

    Suspense Manager

    BRM_home/sys/dd/data

    drop_tables_suspense_oracle.source

    Services Framework Manager

    BRM_home/sys/dd/data

    drop_tables_telco_oracle.source

    drop_tables_config_accountera_oracle.source

    IP Address Manager

    BRM_home/sys/dd/data

    drop_tables_ip_oracle.source

    drop_tables_apn_oracle.source

  8. Restore the entries in your Oracle DM configuration file to their original value.

    1. Open your Oracle DM configuration file (BRM_home/sys/dm_oracle/pin.conf).

    2. Return the following entries to their original value:

      - dm dd_write_enable_objects  0
- dm dd_write_enable_fields  0
- dm dd_write_enable_BRM_objects  0

    3. Save and close the file.

  9. Stop and restart the CM and Oracle DM processes.

All optional component tables have been dropped from your system. You can start adding test accounts to your database and continue testing.

Removing BRM Data from the Database

To completely remove BRM data, including tables, indexes, and triggers, from the Oracle database:

Note:

After you remove the data, you cannot restore it. Perform this task only if you are certain you will not need to access any data in the database or if you have backed up the data and have confirmed that you can restore it.

  1. Use SQL to connect to the database as the system user: 

    % sqlplus system@databaseAlias
Enter password: password

  2. Stop all BRM processes.

    See "Starting and Stopping the BRM System" in BRM System Administrator's Guide.

  3. Enter the following command, replacing pin_user with the user you created for BRM, such as pin: 

    SQL> DROP USER pin_user CASCADE;

  4. Log in to the database server as pin_user.

    If you receive an error indicating an invalid user name, the operation was successful.