Skip Headers
Oracle® Communications Billing and Revenue Management Installation Guide
Release 7.5

E16706-11
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
PDF · Mobi · ePub

23 Account Synchronization Installation Utilities

This chapter provides reference information for Oracle Communications Billing and Revenue Management (BRM) Account Synchronization installation utilities.

object_auditing

Use this utility to enable object auditing when using the Oracle database.

Caution:

  • When installing wireless managers such as Account Synchronization Manager or GSM Manager, you must install all managers before running this utility. If you run this utility before installing a wireless manager, your installation will fail.

  • If you are using a BRM multischema system, you must install all wireless managers, then install your multischema system, and then run the object_auditing.pl utility, in that order.

For more information about auditing, see "About Tracking Changes to Object Fields" in BRM Developer's Guide.

The object_auditing.pl script turns on object auditing by invoking the pin_history_on utility with the -v and pin_history_on_input input file parameters to turn on object auditing. The script then creates the specified audit table indexes by using the create_indexes_audit_tables_oracle.source file.

You define which objects are audited by editing the pin_history_on_input file (BRM_Home/apps/integrate_sync/pin_history_on_input) before running this utility to load the file.

You customize the audit table indexes by editing the create_indexes_audit_tables_oracle.source file (BRM_Home/sys/dd/data/create_indexes_audit_tables_oracle.source).

For more information, see "Turning On Object Auditing".

Note:

To connect to the BRM database, the object_auditing script needs a configuration file in the directory from which you run the utility. See "Creating Configuration Files for BRM Utilities" in BRM System Administrator's Guide.

Location

BRM_Home/setup/scripts

Syntax

perl object_auditing

Results

Look in the utility log file (default.pinlog) to find any errors. The log file is either in the directory from which the utility was started, or in a directory specified in the configuration file.

pin_history_on

Use this utility to enable object auditing when using the Oracle database.

Use the object_auditing.pl script to run this utility after installing all your wireless managers. See "object_auditing".

Caution:

  • When installing wireless managers such as Account Synchronization Manager or GSM Manager, you must install all managers before running this utility. If you run this utility before installing any wireless manager, your installation will fail.

  • If you are using a multischema system, you must install all wireless managers, then install your multischema system, and then run the pin_history_on utility, in that order only.

If you choose to run this utility independently (not as part of the object_auditing script), you must also perform these tasks:

  • Manually modify entries in the Oracle DM configuration file to give the DM permission to write the objects in the input file to the database.

  • Create audit table indexes for the objects that you audit.

For more information, see "Manually Configuring Object Auditing".

For more information about auditing, see "About Tracking Changes to Object Fields" in BRM Developer's Guide.

You define which objects are audited by editing the pin_history_on_input file and running this utility to load the file. For more information, see "Turning On Object Auditing".

Note:

To connect to the BRM database, the pin_history_on utility needs a configuration file in the directory from which you run the utility. See "Creating Configuration Files for BRM Utilities" in BRM System Administrator's Guide.

Location

BRM_Home/bin

Syntax

pin_history_on [-d | -v | -h] pin_history_on_input

Parameters

-d

Enables debugging mode.

-v

Displays information about successful or failed processing as the utility runs.

Note:

This parameter is always used with other parameters and commands. It is not position dependent. For example, you can enter -v at the beginning or end of a command to initiate the verbose parameter. To redirect the output to a log file, use the following syntax with the verbose parameter. Replace filename.log with the name of the log file:

pin_history_on any_other_parameter -v> filename.log

-h

Displays the syntax and parameters for this utility.

pin_history_on_input

Name of the file that specifies which fields within the objects to audit. A sample file is included in the BRM_Home/apps/integrate_sync directory

Results

Look in the utility log file (default.pinlog) to find any errors. The log file is either in the directory from which the utility was started, or in a directory specified in the configuration file.

pin_ifw_sync_oracle

Use this utility to create, drop, and monitor Account Synchronization queues in your Pipeline Manager database.

The Account Synchronization DM uses these queues to send BRM business events to the Pipeline Manager Listener (DAT_Listener) module. See "About Sending Account Data to Pipeline Manager".

Location

BRM_Home/apps/pin_ifw_sync

Syntax for Creating a Queue

Creates an Account Synchronization queue, queue table, and database package in your database. The database package contains stored procedures for queuing, dequeuing, and purging business events.

pin_ifw_sync_oracle.pl create
                      [-l username/password@DatabaseAlias]
                      [-q queue_name -t queue_table] 
                      [-s]storage_clause
                      [-r retention_time]

Parameters for Creating a Queue

-l username/password@DatabaseAlias

Specifies how to connect to the database.

For example:

pin_ifw_sync_oracle.pl create -l pin/password@pindb.portal.com
  

If you omit this parameter, the utility prompts you for this information.

-q queue_name -t queue_table

Specifies the queue name and queue table name.

If you omit these parameters, the utility automatically creates a queue named IFW_SYNC_QUEUE and a queue table named IFW_SYNC.

-s storage_clause

Specifies the storage settings for the queue table.

If you omit this parameter, the storage settings are set by the storage_clause parameter in the BRM_Home/apps/pin_ifw_sync/create_ifw_sync_queue.conf file. See "Configuring the Queue Location".

For example:

pin_ifw_sync_oracle.pl create -s "tablespace PIN00 initrans 5 storage (initial 200k next 200k maxextents unlimited pctincrease 0 )"
-r retention_time

Specifies the amount of time, in seconds, until processed events are removed from the database queue.

If you omit this parameter, the retention time is set by the retention_time parameter in the BRM_Home/apps/pin_ifw_sync/create_ifw_sync_queue.conf file. See "Configuring How Often Processed Events Are Removed from the Queue".

Syntax for Dropping a Queue

Drops the specified queue and its associated queue table from your database. If the database contains no other Account Synchronization queues, this command also drops the Account Synchronization database package, which contains stored procedures for queuing, dequeuing, and purging events.

pin_ifw_sync_oracle.pl drop [-q queue_name] [-l username/password@DatabaseAlias]

Parameters for Dropping a Queue

-q queue_name

Specifies the name of the queue to drop.

If you omit this option, the utility automatically drops the default queue, IFW_SYNC_QUEUE.

-l username/password@DatabaseAlias

Specifies how to connect to the database.

If you omit this option, the utility prompts you for this information.

Syntax for Generating a Report

Generates a report that displays the state of each event in an Account Synchronization queue.

pin_ifw_sync_oracle.pl report -r summary|detail [-q queue_name]
                       [-l username/password@DatabaseAlias]

Parameters for Generating a Report

-r summary | detail

Generates the specified type of report.

  • -r summary generates a report that summarizes the number of events in each state. Events can be in the following states shown in Table 23-1:

    Table 23-1 Pipeline Manager Event States

    State Description

    READY

    The event has not been dequeued or processed by Pipeline Manager.

    PROCESSED

    The event was dequeued and processed by Pipeline Manager.


  • -r detail generates a report that details the ID, event state, queuing time, and dequeuing time for each event.

-q queue_name

Specifies the queue name.

If you omit this parameter, the utility automatically generates a report for the default queue, IFW_SYNC_QUEUE.

-l username/password@DatabaseAlias

Specifies how to connect to the database.

If you omit this parameter, the utility prompts you for this information.

Syntax for Testing a Queue

Tests the specified queue by attempting to enqueue and dequeue 20 test events. You run this command to test if a newly created queue functions properly.

Note:

You need to test a queue only after it is first created.
pin_ifw_sync_oracle.pl test [-q queue_name] 
                     [-l username/password@DatabaseAlias]

Parameters for Testing a Queue

-q queue_name

Specifies the queue name.

If you omit this parameter, the utility automatically tests the default queue, IFW_SYNC_QUEUE, and default queue table, IFW_SYNC.

-l username/password@DatabaseAlias

Specifies how to connect to the database.

If you omit this parameter, the utility prompts you for this information.

Syntax for Listing Queues

Lists all queues in the current user's database.

pin_ifw_sync_oracle.pl list [-l username/password@DatabaseAlias]

Parameters for Listing Queues

-l username/password@DatabaseAlias

Specifies how to connect to the database.

If you omit this parameter, the utility prompts you for this information.

Syntax for Getting Help

Displays the syntax for the pin_ifw_sync_oracle utility.

pin_ifw_sync_oracle.pl help

Results

The pin_ifw_sync_oracle utility notifies you when it runs successfully. Otherwise, look in the default.pinlog file for errors. This file is either in the directory from which the utility was started or in a directory specified in the utility configuration file.