Configuring Object Auditing for GSM

52 Configuring Object Auditing for GSM

You can enable object auditing for GSM services so Oracle Communications Billing and Revenue Management (BRM) can track changes.

Topics in this document:

Turning On Object Auditing

Enable BRM to audit GSM objects. Auditing objects creates a history of certain information, such as phone numbers and logins, so BRM can track changes.

The object_auditing.pl utility invokes the pin_history_on utility to load the file containing the objects to audit and turn on object auditing. It then creates the audit table indexes in the BRM database.

Caution:

You must install all wireless managers before running this utility. If you run this utility before installing a wireless manager, your installation will fail.

To turn on object auditing:

For multischema systems, ensure you have installed all optional managers and the multischema software.
Customize the list of objects to audit by editing the BRM_home/apps/integrate_sync/pin_history_on_input file.
Customize your audit table indexes by editing the BRM_home/sys/dd/data/create_indexes_audit_tables_oracle.source file.
The object_auditing.pl utility requires a pin.conf configuration file. You can create one or run the utility from a directory that contains a pin.conf file, such as BRM_home/sys/dm_oracle.
Run the following command:
```
perl object_auditing
```

Manually Configuring Object Auditing

To enable BRM to audit GSM objects, run the object_auditing.pl script. For more information, see "object_auditing.pl". If you don't run the object_auditing.pl script, you can configure object auditing manually.

To manually configure object auditing, do the following:

Modify the Oracle DM configuration file (pin.conf) and run the pin_history_on utility. See "Running the pin_history_on Utility".
Modify the create_indexes_audit_tables_oracle.source file and create the audit table indexes. See "Creating Audit Table Indexes".

Running the pin_history_on Utility

You must install all wireless managers before running the pin_history_on utility. If you run this utility before installing a wireless manager, your installation will fail. If you are using a multischema system, install all wireless managers and the multischema software before running the pin_history_on utility.

To run the pin_history_on utility:

Open the BRM_home/sys/dm_oracle/pin.conf file in a text editor.

Note the value of the following entries:

- dm dd_write_enable_fields 
- dm dd_write_enable_objects 
- dm dd_write_enable_BRM_objects 
- dm dd_mark_as_BRM

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_BRM_objects 1
- dm dd_mark_as_BRM 1

Note:

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

Save and close the file.
Stop and restart the Oracle DM.
Run the pin_history_on utility:
```
pin_history_on inputFile
```
Note:

If you run the utility from another directory, include the path to the pin_history_on utility in the command line.
Open the BRM_home/sys/dm_oracle/pin.conf file in a text editor.

Restore the following entries to their original values (the values they had before you modified them):

- dm dd_write_enable_fields 
- dm dd_write_enable_objects 
- dm dd_write_enable_BRM_objects 
- dm dd_mark_as_BRM

Save and close the file.
Stop and restart the Oracle DM.

Creating Audit Table Indexes

After running the pin_history_on utility, you must create indexes for the new audit tables. The BRM installation installs a file (create_indexes_audit_tables.source) that specifies the necessary indexes on the audit tables.

To create audit table indexes:

Open the BRM_home/sys/dd/data/create_indexes_audit_tables_oracle.source file in a text editor.
Set the $PIN_CONF_TBLSPACEX1 entry to pinx00.

Note:

This entry must have the same value as the variable $MAIN_DB{'indexes_group'} configured in the BRM_home/setup/pin_setup.values file. The default value of this entry is pinx00.

Set the $PIN_CONF_STORAGE_MED entry to the following:

storage (initial 200k next 200k maxextents unlimited pctincrease 0)

Save and close the file.

Create the audit table indexes in SQL*Plus by running the following command:

sqlplus @database_Alias @filepath/create_indexes_audit_tables_oracle.source