32 Improving Client Performance
Learn how to improve client performance in Oracle Communications Billing and Revenue Management (BRM).
Topics in this document:
Logging Noncurrency Events
By default, BRM is configured to give maximum account-creation performance by logging only events that have a balance impact associated with a currency. To log noncurrency events at the expense of system performance, change the creation_logging entry in the CM configuration file (pin.conf).
By default, these events are logged:
-
/event/billing/charge
-
/event/billing/deal
-
/event/billing/product
By default, these events are not logged:
-
/event/customer/billinfo
-
/event/customer/nameinfo
-
/event/customer/login
-
/event/customer/password
-
/event/customer/status
-
/event/billing/limit
To log noncurrency events:
-
Open the CM configuration file (BRM_home/sys/cm/pin.conf).
-
Edit the creation_logging entry. For example:
- fm_cust creation_logging 1 -
Save and close the file.
The new value becomes effective immediately and applies to the next account created. You do not need to restart the CM to enable this entry.
Configuring BRM to Get Events based on Balance Impact Type
You can limit the event search criteria to just one type of balance impact by changing the value of the PIN_FLD_MODE field directly or by setting the EventChargeDiscountMode parameter to one of the following values:
-
0: (Default and only pre-fix mode) Returns events whose gross, net, or total balance impact matches the search criteria.
-
1: Returns events whose gross balance impact (the sum of all charges) matches the search criteria. Discounts and tax are not considered.
-
2: Returns events whose net balance impacts (the sum of all charges and discounts) matches the search criteria. Tax is not considered
-
3: Returns events whose total balance impact (the sum of all charges, discounts, and tax) matches the search criteria.