15 Installing Multiple BRM Instances on One System for Testing

This chapter provides information to help developers test their Oracle Communications Billing and Revenue Management (BRM) system configuration.

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 Oracle

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 each user. For example, type the following to create four users:

   For HP-UX IA64, Linux, and Solaris:

   # 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
     
   

3. Create a password for each user.

   For example, type the following to create the pin1 password:

   # passwd pin1
   

Installing and Configuring Oracle

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

Creating Tablespaces for Each User

You must 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)

To create tablespaces for each user:

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/manager@databaseAlias
     
   

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.
   

Creating Multiple BRM Users for Oracle

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

To create multiple BRM users for Oracle:

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

   % sqlplus system/manager@databaseAlias
     
   

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 have already installed the product, features that are already installed cannot be reinstalled without uninstalling them first. To reinstall a feature, uninstall it and then install it again.

To install multiple instances of BRM on one machine:

1. If the Third-Party software package is not installed, install it.

   See "Installing the Third-Party Software".

2. Log in as user pinN.

   % su - pinN
     
   

3. Download the software to a temporary directory (temp_dir).

4. Go to the directory where you installed the Third-Party package and 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
     
   

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

6. Go to the temp_dir directory and enter this command:

   7.5.0_Portal_Base_platform_opt.bin
     
   

   where platform is the operating system name.

   Note:

   You can use the -console option to run the installation in a command-line mode. To enable a graphical user interface (GUI) installation, install a GUI application such as X Windows and set the DISPLAY environment variable before you install the patch.

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

   Follow the instructions displayed during installation. Your responses are written to the BRM_Home/setup/pin_setup.values file. Table 15-1 lists the setup prompt descriptions.

   Table 15-1 Prompt Descriptions

   Prompt	Description
   Setup type:	Enter the type of installation you prefer. The default is Typical. Enter Typical for development and production systems. Enter Demo for test or demonstration systems. This is the quickest option and asks you the least number of questions. Enter Custom for production systems. The installer lets you install a subset of the BRM components.
   Directory name:	Enter the directory in which to install BRM. The default is /opt/portal/7.5.
   Create BRM Database Tablespaces?	Enter whether you want the installer to create default tablespaces for you. Enter No to create custom tablespaces manually. You must create your tablespaces before you run the pin_setup script. Do not select Yes. Selecting Yes may cause installation to fail.
   Database alias:	Enter your database alias. The default is pindbhostname.
   Oracle DM database number:	Enter the database number. The default is 0.0.0.1.
   Oracle DM port:	Enter the port number for the BRM Data Manager (DM). The default is 12950.
   Database username:	Enter your database user name. The default is pin. Important: Make sure you enter the user name for pin1, then pin2, and so on.
   Database password:	Enter your database password. The default is pin. Important: Make sure you enter the password for pin1, then pin2, and so on.
   Oracle DM character set:	Enter the character set your database uses. BRM strongly recommends using the UTF8 character set. The default is UTF8.
   Storage Model used for Oracle tablespaces:	Enter the desired size of your database. The default is Small. Enter Test for test or demonstration databases smaller than 700 MB. Enter Small for demonstration databases smaller than 1.5 GB. Enter Medium for production databases smaller than 30 GB. Enter Large for production databases larger than 30 GB.
   Tablespace name for Tables:	Enter the name of your data tablespace. The default is pin00.
   Tablespace name for Indexes:	Enter the name of your index tablespace. The default is pinx00.
   Drop the BRM tables?	Enter whether you want to drop the database tables. The default is No. If you select Yes, the installer drops all existing tables on your system. This results in irrecoverable loss of data. Do not use this unless you have backed up all of your existing data. If you select No, the installer uses your existing BRM tables. In test systems, select Yes to reinitialize the database.
   Partition tables?	Specify whether you want to enable partitioning. The default is Yes. Caution: To partition tables, you must have Oracle Partitioning installed. If you select Yes but do not have Oracle Partitioning installed, the BRM setup program fails when it tries to create partitions. If you select Yes, the following classes are automatically enabled for partitioning: event, bill, invoice, item, journal, newsfeed, sepa, and user activity. To enable other classes for partitioning during installation, see "Enabling Different Classes for Partitioning during Installation". Note: This sets the $ENABLE_PARTITION parameter to Yes in the pin_setup.values file. If you select No, you can enable partitioning after installation. See "Converting Nonpartitioned Classes to Partitioned Classes" in BRM System Administrator's Guide. If you plan to use Rated Event (RE) Loader to load prerated events, you must partition your event tables. For more information, see "Partitioning Tables" in BRM System Administrator's Guide.
   Add 12 fixed (monthly) partitions to all event tables?	This prompt is displayed only if you enter Yes to the "Partition tables?" prompt. Specify whether you want the installer to add 12 monthly partitions to your event tables: Enter Yes to have the installer add 12 monthly partitions, a historic partition, and a last partition to your event tables. This sets the $SETUP_CREATE_PARTITIONS parameter to Yes in the pin_setup.values file. Enter No if you want the installer to add only a historic partition and a last partition to the event tables. You can use this partitioning layout for a simple test or demonstration system. For a production system, however, you must add purgeable partitions after installation is complete and before the system generates events.
   CM Port	Enter the port number for the Connection Manager (CM). The default is 11960.

   
   

8. Go to the directory where you installed the BRM software and source the source.me file:

   Bash shell:

   source source.me.sh
     
   

   C shell:

   source source.me.csh
     
   

9. To further configure BRM, such as 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/7.5:

/opt/portal/7.5/pin1
/opt/portal/7.5/pin2
/opt/portal/7.5/pin3
/opt/portal/7.5/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 755 pin_setup
      % vi pin_setup
        
      

   2. Edit the VERSION and PINUSER entries to include the pinN directory:

      VERSION = 7.5/pinN
      PINUSER = pinN
        
      

   3. Save and close the file.

3. Edit the pin_setup.values file.

   1. Go to the BRM_Home/pinN/setup directory and open the pin_setup.values file in a text editor such as vi:

      % cd BRM_Home/setup
      % vi pin_setup.values
        
      

   2. Modify all path references to include the pinN directory:

      $PIN_HOME = "/opt/portal/7.5/pinN"
      $PIN_LOG_DIR = "/var/portal/7.5/pinN"
      $PIN_TEMP_DIR = "/opt/portal/7.5/pinN/setup"
        
      

   3. Save and close the file.

4. Go to the BRM_Home/setup directory and run the pin_setup script:

   % cd BRM_Home/setup
   % ./pin_setup
     
   

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

6. Verify that BRM was installed and set up correctly by creating an account with Customer Center.

7. Repeat steps 1 through 6 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.

Caution:

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:

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 execute the following command using the information in Table 15-2:

   SQL> @path/file_name
   

   Table 15-2 Optional Component Drop Source File Location and Name

   Optional Component	Path	File Name
   Content Manager	BRM_Home/sys/dd/data	drop_tables_content_oracle.source
   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
   Resource Reservation Manager	BRM_Home/sys/dd/data	drop_tables_reservation_oracle.source
   SIM Manager	BRM_Home/sys/dd/data	drop_tables_sim_oracle.source
   Vertex Quantum Manager	BRM_Home/sys/dd/data	drop_tables_telephony_oracle.source
   Vertex Manager	BRM_Home/sys/dd/data	drop_tables_telephony_oracle.source
   SMS Settlement Reports	BRM_Home/sys/dd/data	drop_tables_sms_settle_report_oracle.source
   Services Framework AAA Manager	BRM_Home/sys/dd/data	drop_tables_telco_aaa_oracle.source
   GSM AA Manager	BRM_Home/sys/dd/data	drop_tables_gsm_aaa_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
   Voucher Manager	BRM_Home/sys/dd/data	drop_tables_voucher_oracle.source
   Collections Manager	BRM_Home/sys/dd/data	drop_tables_collections_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_portal_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 following files listed in Table 15-3:

   Table 15-3 Optional Component Data Dictionary Drop Source File Location and Name

   Optional Component	Path and File Name
   Content Manager	BRM_Home/sys/dd/data/dd_objects_content.source
   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
   Resource Reservation Manager	BRM_Home/sys/dd/data/dd_objects_reservation.source
   SIM Manager	BRM_Home/sys/dd/data/dd_objects_sim.source
   TelcoTax Manager	BRM_Home/sys/dd/data/dd_objects_telephony.source
   Vertex Quantum Manager	BRM_Home/sys/dd/data/dd_objects_telephony.source
   Vertex Manager	BRM_Home/sys/dd/data/dd_objects_telephony.source
   SMS Settlement Reports	BRM_Home/sys/dd/data/dd_objects_sms_settle_report.source
   Suspense Manager	BRM_Home/sys/dd/data/dd_objects_suspense.source
   GSM AAA Manager	BRM_Home/sys/dd/data/dd_objects_gsm_aaa.source
   Services Framework AAA Manager	BRM_Home/sys/dd/data/dd_objects_telco_aaa.source
   IP Address Manager	BRM_Home/sys/dd/data/dd_objects_ip.source BRM_Home/sys/dd/data/dd_objects_apn.source
   Collections Manager	BRM_Home/sys/dd/data/dd_objects_collections.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. Execute the PMC_OP_SDK_DEL_OBJ_SPECS opcode with the input flist you created.

      See "Executing Opcodes" 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 execute the following command using the values in Table 15-4:

   SQL> @path/file_name
   

   Table 15-4 Optional Component Drop Source File Location and Name

   Optional Component	Path	File Name
   Content Manager	BRM_Home/sys/dd/data	drop_tables_content_oracle.source
   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
   Resource Reservation Manager	BRM_Home/sys/dd/data	drop_tables_reservation_oracle.source
   SIM Manager	BRM_Home/sys/dd/data	drop_tables_sim_oracle.source
   Vertex Quantum Manager	BRM_Home/sys/dd/data	drop_tables_telephony_oracle.source
   Vertex Manager	BRM_Home/sys/dd/data	drop_tables_telephony_oracle.source
   SMS Settlement Reports	BRM_Home/sys/dd/data	drop_tables_sms_settle_report_oracle.source
   Services Framework AAA Manager	BRM_Home/sys/dd/data	drop_tables_telco_aaa_oracle.source
   GSM AA Manager	BRM_Home/sys/dd/data	drop_tables_gsm_aaa_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
   Voucher Manager	BRM_Home/sys/dd/data	drop_tables_voucher_oracle.source
   Collections Manager	BRM_Home/sys/dd/data	drop_tables_collections_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_portal_objects  0
        
      

   3. Save and close the file.

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

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

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

Follow these steps to completely remove BRM data, including tables, indexes, and triggers, from the Oracle database:

Caution:

When 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 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/manager@databaseAlias
   SQL>
     
   

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.