16 Running Utilities in Multischema Systems

Learn how to run utilities in an Oracle Communications Billing and Revenue Management (BRM) multischema system.

Topics in this document:

• About Utilities that Support Multischema Systems

• About Non-MTA Utilities that Support Multischema Systems

• About Non-MTA Utilities that Do Not Support Multischema Systems

See also "Managing a Multischema System".

About Utilities that Support Multischema Systems

The utilities listed in Table 16-1 can be configured to support global searches across all database schemas in a multischema system.

Table 16-1 Utilities Supporting Multischema Systems

Utility Type	Utility Name
Billing	pin_bill_accts pin_trial_bill_accts
Customer Management	pin_state_change
Invoicing	pin_inv_accts pin_inv_doc_gen pin_inv_export
Payment	pin_collect pin_deposit pin_refund
General Ledger	pin_ledger_report
Analytics	pin_generate_analytics

The way you configure one of these utilities to run against multiple schemas depends on how it is run:

• Through Business Operations Center: These utilities are run by Business Operations Center during basic operations such as billing, invoicing, and payment collection. You configure whether these operations are performed against all schemas or against a specific schema by using the Business Operations Center GUI only. See "Specifying Job Frequency Settings" in Business Operations Center Online Help.

• Manually at the command line: You configure a utility to run against multiple schemas by editing its pin.conf file.

If you are running one of these utilities manually, you configure it to run against all schemas by doing the following:

1. Open the utility's pin.conf file in a text editor.

   For example, for pin_ledger_report, you would open the BRM_home/apps/pin_billd/pin.conf file.

2. Set the multi_db entry 1:

   - pin_mta multi_db   1

   Caution:

   If the utility is being run through Business Operations Center, the multi_db entry must be set to 0.

3. Save and close the file.

About Non-MTA Utilities that Support Multischema Systems

You can run the following non-MTA utilities against all schemas in a multischema system or against a specified schema:

• pin_clean (see "pin_clean" in BRM Configuring and Collecting Payments)

• pin_recover (see "pin_recover" in BRM Configuring and Collecting Payments)

By default, these utilities run against all schemas.

To run these utilities against only one schema in a multischema system, include the -schema schema_number parameter with the utility. For example, if your BRM database contains three schemas, you would run the pin_clean utility against only the primary schema by running this command:

pin_clean -schema 1

About Non-MTA Utilities that Do Not Support Multischema Systems

The following non-MTA utilities can connect to only one CM and its associated schema at a time:

• pin_mass_refund (see "pin_mass_refund" in BRM Managing Accounts Receivable)

• pin_config_distribution (see "pin_config_distribution")

To run these utilities in a multischema system, you must have a CM for each schema in the system. You then connect and run the utility against each CM and schema pair. For example, to run a non-MTA utility on a multischema system:

• Connect the utility to the primary CM and run the utility against the primary schema.

• Connect the utility to a secondary CM and run the utility against its associated secondary schema.

• Connect the utility to another secondary CM and run the utility against its associated secondary schema.

To run a non-MTA utility in a multischema system:

1. Connect the utility to the primary CM:

   1. On the primary CM machine, open the BRM_home/apps/pin_billd/pin.conf file in a text editor.

   2. Edit the following entries:

      - nap   cm_ports   ip    PrimaryHost   PrimaryPort
      - nap   login_name       PrimaryLoginName
      - nap   login_pw         PrimaryLoginPassword
      - nap   login_type       LoginType
      - -     user_id          0.0.0.x /service/pcm_client 1

   3. Save and close the file.

2. On the primary CM machine, go to the BRM_home/apps/pin_billd directory and run the utility.

3. Connect the utility to a secondary CM:

   1. On the secondary CM machine, go to the BRM_home/apps/pin_billd directory and open the pin.conf file in a text editor.

   2. Edit the following entries:

      - nap   cm_ports   ip    SecondaryHost   SecondaryPort
      - nap   login_name       SecondaryLoginName
      - nap   login_pw         SecondaryLoginPassword
      - nap   login_type       LoginType
      - -     user_id          0.0.0.x /service/pcm_client 1

   3. Save and close the file.

4. On the secondary CM machine, go to the BRM_home/apps/pin_billd directory and run the utility.

5. Repeat steps 3 and 4 for each remaining secondary schema in your system.