To set up RE Loader for multischema systems:

1. Install and configure one instance of Pipeline Manager for each BRM database schema and one instance for the multischema account router.

   For example, if your BRM system contains three schemas, install and configure four instances of Pipeline Manager.

2. In the multischema account router instance of Pipeline Manager, configure the following:

   1. Set the FCT_AccountRouter module's Mode registry entry to ROUTER and configure the module's streams registry entry to create an output stream for each schema Pipeline Manager instance. See "FCT_AccountRouter" in BRM Pipeline Manager Reference.

   2. Set the DAT_AccountBatch module's UseAsRouter registry entry to True. See "DAT_AccountBatch" in BRM Pipeline Manager Reference.

Before you install RE Loader, you must grant execute permission to pin_user for dbms_lock:

1. Log in to your database as the SYS user:

   % sqlplus sys@databaseAlias
   Enter password: password

2. Grant execute privileges to pin_user:

   SQL> grant execute on dbms_lock to pin_user

When you install RE Loader on a system where BRM is not installed, you must grant the Data Manager (DM) write permission before installing RE Loader.

Perform the following on all machines containing a DM:

1. In a text editor, open your DM configuration file:

   BRM_home/sys/dm_oracle/pin.conf

   BRM_home is the directory in which you installed BRM components.

2. Write down the values of your dd_write_enable_fields, dd_write_enable_objects, dd_write_enable_portal_objects, and dd_mark_as_portal entries.

3. Set the values of the following entries to 1:

   - dm dd_write_enable_fields 1
   - dm dd_write_enable_objects 1
   - dm dd_write_enable_portal_objects 1
   - dm dd_mark_as_portal 1

   Note:

   If any entry is not in the file, add it.

   For more information, see the information in the DM pin.conf file.

4. Save and close the file.

5. Stop and restart the DM.

   You can now install RE Loader.

To install RE Loader, see "Installing Individual BRM Components" in BRM Installation Guide.

To create partitions for RE Loader events:

1. On the system where BRM is installed, go to the BRM_home/apps/partition_utils directory.

2. Run the partition_utils utility to enable delayed-event partitions:

   perl partition_utils.pl -o enable -t delayed -c storable_class
   

   where storable_class specifies the event classes for which you want partitioning.

   Note:

   You must create partitions for all subclasses of a specific event that you want to load.

   For example, this command creates partitions for /event/delayed/session/telco/gsm delayed events:

   perl partition_utils.pl -o enable -t delayed -c /event/session/telco/gsm
   

For more information, see:

• "Enabling Delayed-Event Partitioning" in BRM System Administrator's Guide

• "partition_utils" in BRM System Administrator's Guide.

Your RE Loader installation is now complete.

To return your DM permissions to their original values:

1. In a text editor, open your DM configuration file:

   BRM_home/sys/dm_oracle/pin.conf

2. Restore the following entries to their original values (the values they had before you modified them). The default value for each entry is 0:

   - dm dd_write_enable_fields 
   - dm dd_write_enable_objects 
   - dm dd_write_enable_portal_objects 
   - dm dd_mark_as_portal
   

3. Save and close the file.

4. Stop and restart the DM.

To set the Oracle library paths:

1. Open the BRM_home/apps/pin_rel/pin_rel file in a text editor. BRM_home is the directory where you installed BRM components.

2. Add the following before the command that runs Java.

   setenv ORACLE_HOME Oracle_home
   setenv SHLIB_PATH ${ORACLE_HOME}/lib
   setenv PATH ${PATH}:${ORACLE_HOME}/bin
   

   Note:

   Oracle_home points to the location where you installed the full 32-bit client software.

3. Save and close the file.

4. Open the BRM_home/apps/pin_rel/SampleRelHandler_config.values file in a text editor.

5. Add these lines between the FILETYPE and HANDLER_DIR variables:

   Note:

   The paths you set depend on your system setup.

   $ENV{'ORACLE_HOME'} = "/u01/app/oracle/product/11i64";
   $ENV{'SHLIB_PATH'} = "/usr/lib:/opt/portal/7.5/lib:/u01/app/oracle/product/11i64/lib";
   $ENV{'PATH'} = ".:/bin:/usr/bin:/usr/local/bin:/u01/app/oracle/product/11i64/bin:/opt/portal/7.5/bin";
   

6. Save and close the file.

setenv ORACLE_HOME /u01/app/oracle/product/10g64
setenv ORACLE_SID       PIND10g64
setenv NLS_LANG American_America.AL32UTF8
setenv LD_LIBRARY_PATH $LD_LIBRARY_PATH:$ORACLE_HOME/lib32:$ORACLE_HOME/rdbms/lib32
setenv LD_LIBRARY_PATH_64 $IFW_HOME/lib:$ORACLE_HOME/lib:$ORACLE_HOME/rdbms/lib
setenv ORACLE_BIN $ORACLE_HOME/bin
setenv ORACLE_DOC $ORACLE_HOME/odoc
setenv ORA_NLS33 $ORACLE_HOME/ocommon/nls/admin/data
alias ora 'cd $ORACLE_HOME'
set path = ($path $ORACLE_BIN)