6 Configuring Rated Event Loader to Run Automatically

Learn how to set up Oracle Communications Billing and Revenue Management (BRM) Rated Event Loader (RE Loader) to run automatically using either Batch Controller or the RE Loader daemon.

This information applies only to the original processing method.

Topics in this chapter:

See also:

Configuring RE Loader to Run Automatically by Using Batch Controller

To run RE Loader automatically, configure Batch Controller and the RE Loader batch handler. When a pre-rated event file is available, Batch Controller automatically starts the RE Loader batch handler, which runs the RE Loader utility (pin_rel).

To configure RE Loader to run automatically, do the following for each instance of RE Loader:

Configuring the RE Loader Batch Handler

To configure the RE Loader batch handler:

  1. Give the SampleRelHandler.pl file a unique name. You will configure Batch Controller to call the handler using this name.

  2. Create the following subdirectories: An archive subdirectory where successfully processed files can be stored and a reject subdirectory where unsuccessfully processed files can be stored.

  3. Open the SampleRelHandler_config.values file and modify the entries shown in Table 6-1.

    Table 6-1 Mandatory RE Loader Batch Handler Configuration Entries

    Entry Description

    $FILETYPE

    Specifies the event record file-name pattern to look for. To load only specific files, change the value of this entry. The default is *.dat.bc (any data file processed by Batch Controller).

    Batch Controller runs the RE Loader batch handler for each file with a name that matches this pattern.

    Tip: You can use an asterisk (*) to represent zero or more characters in the file name. No other wildcards are supported.

    $HANDLER_DIR

    Specifies the full path to the directory containing the RE Loader batch handler, which is this processing directory.

    $pinRELDir

    Specifies the full path to the directory containing the RE Loader application, which is this processing directory.

    $pinREL

    Specifies the full path to the batch application executable.

    $STAGING

    Specifies the full path to the event output directory.

    If you specify a directory other than the event output directory, use the Linux command that links the event output directory to the input staging directory.

    $PROCESSING

    Specifies the full path to the directory from which event record files are processed. The default is defined in the $pinRELDir environment variable.

    This must be the same directory specified in the following RE Loader Infranet.properties entries:

    • infranet.rel.default.interim_directory

    • infranet.rel.storable_class.classname.interim_directory

    $ARCHIVE

    Specifies the full path to the directory where a successfully processed file is archived. This is the archive subdirectory created in step 2. Change this value if you used a name other than the default, $pinRELDir/archive.

    $REJECT

    Specifies the full path to the directory where an unsuccessfully processed file is stored. This is the reject subdirectory created in step 2. Change this value if you used a name other than the default, $pinRELDir/reject.

  4. Save and close the file.

Configuring Batch Controller

The RE Loader package includes Batch Controller. If your system already has Batch Controller installed, the RE Loader installer does not install another. Use the sample Batch Controller properties file (BRM_home/apps/pin_rel/SampleBatchControllerInfranet.properties) to configure Batch Controller.

The default configuration for the sample Batch Controller runs RE Loader batch handler whenever a rated event record file appears in the event output directory. You can change this setting to trigger the RE Loader batch handler at specified times or based on other kinds of occurrences by editing the event entries that trigger the RE Loader batch handler. See "Setting Activity Times and Triggers" in BRM System Administrator's Guide.

The optimal number of RE Loader processes to configure is at least three. Depending on the size of your files and the time it takes to load events, configuring four or five processes might save time.

To configure Batch Controller:

  1. Copy the BRM_home/apps/pin_rel/SampleBatchControllerInfranet.properties file to your BRM_home/apps/batch_controller directory and change its name to Infranet.properties.

  2. Open the BRM_home/apps/batch_controller/Infranet.properties file.

  3. Edit the BRM connection parameters.

    See "Using Configuration Files" in BRM System Administrator's Guide.

  4. Set the relHandler.start.string parameter to the path of the RE Loader batch handler and to the name of the handler script that you gave it when configuring the RE Loader batch handler. See step 1 in "Configuring the RE Loader Batch Handler".

    For example:

    relHandler.start.string    BRM_home/apps/pin_rel/REL_handler_name.pl
    
  5. (Optional) To change the number of RE Loader batch handler processes you want to run, set the maximum batch handler entries.

    Note:

    The number of RE Loader batch handler processes called depends on the number of event record files in the event output directory. If you change these entries, test RE Loader's performance.

    relHandler.max.at.highload.time 3
    relHandler.max.at.lowload.time 3
    
  6. Set the cdrFileEvent.file.location parameter to specify the location of the event output directory:

    cdrFileEvent.file.location /export/Portal/integRate
    
  7. Set the cdrFileEvent.file.pattern parameter to which files should be processed by Batch Controller:

    cdrFileEvent.file.pattern cdr*.dat

    Note:

    You can use an asterisk (*) as a wildcard character to represent zero or more characters in the file name.

  8. Save and close the file.

  9. Stop and restart Batch Controller.

For more information about configuring Batch Controller, see "Controlling Batch Operations" in BRM System Administrator's Guide.

Configuring RE Loader to Run Automatically by Using the RE Loader Daemon

The RE Loader daemon detects when CDR files arrive in the input directory, and then processes them. RE Loader daemon moves the original file to an archive directory if the records are successfully loaded or to a reject directory if the records are not successfully loaded.

To run RE Loader automatically by using the RE Loader daemon:

  1. Configure the RE Loader Infranet.properties file. See "Configuring the Rated Event Loader Infranet.properties File".

  2. Use the pin_ctl utility to run the BRM_home/bin/start_rel_daemon script. See "Running the pin_ctl Utility" in BRM System Administrator's Guide.

To stop the RE Loader daemon, run the BRM_home/bin/stop_rel_daemon script.

You can also run these scripts manually.