This chapter provides an overview of how components relate to one another in an Oracle Communications Billing and Revenue Management (BRM) wireless system and describes the tasks you need to perform to install and configure IMT Manager to work with BRM components.
For general information about IMT Manager, see "About Using IMT Manager".
For basic information about integrating wireless services with BRM, see "About Integrating Wireless Services".
To install and use IMT Manager:
Install and configure BRM. This includes setting up standard BRM business policies, such as how to run billing and manage customers.
Set up your G/L IDs, rate plans, and resources before configuring pipeline rating. See "About Integrating Wireless Services".
Install Pipeline Manager. See "Overview of Pipeline Manager Installation".
Extend the IMT and PDC service classes to offer IMT and PDC products and services to your users. See "Adding a new IMT or PDC service".
Do not install IMT Manager and GSM Manager together in the same BRM system. There will be conflicts because they create the same set of services for two different telecommunications standards.
Make sure you install, configure, and test each component before installing the next component. Some components need to be configured before others. See "Component Configuration Dependencies".
Before installing and configuring any optional components, such as Service Manager, run enough tests to ensure that your BRM core server components are installed and configured correctly.
The Pipeline Manager installation process includes the following:
Installing and configuring Account Synchronization Data Manager (DM). The Account Synchronization DM enables the pipeline to get data from the BRM database.
Running the object_auditing script to turn on auditing for BRM objects that pipeline rating needs information about.
Important:You cannot complete all the tasks required for sending account data to pipeline rating until you install Pipeline Manager. For example, when you configure the Account Synchronization Data Manager, you need to specify the location of the Listener map file.
Install and configure Pipeline Manager. Before you configure the rating pipeline, use the sample registry to test the system and make sure it has been installed correctly. See "Installing Pipeline Manager" in BRM Installation Guide.
Configure these pipeline modules:
See BRM Configuring Pipeline Rating and Discounting.
Install and configure Rated Event Loader to load events into the BRM database. See "Installing Rated Event Loader" in BRM Configuring Pipeline Rating and Discounting.
Table 30-1 summarizes the components you install for a typical wireless integration:
BRM server software
Installs the standard BRM system software, including Connection Managers (CMs) and Data Managers (DMs).
Installs the Pipeline Manager system software, modules, database, and utilities. The FCT_Account and DAT_AccountBatch modules are installed with Pipeline Manager.
Installs the following:
Account Synchronization Data Manager
Installs Account Synchronization Data Manager (DM), and object_auditing script.
Rated Event Loader
Installs Rated Event Loader.
Some components cannot be configured without configuring another component first:
Before you install any optional BRM components, you must install the BRM server software.
Before you create BRM provisioning tags for extended rating attributes (ERAs), you must configure ERAs in the pipeline.
Before you create your IMT and PDC price lists, you must perform the following tasks:
Install IMT Manager.
Create and load BRM provisioning tags. To use the sample BRM IMT and PDC price lists, you can load the sample pin_telco_tags_pdc_imt file without editing it. See "Loading Provisioning Tags".
Before you configure rating in the pipeline, you must define the following items in BRM:
Before you can run the Account Synchronization DM, you need to install and configure the Pipeline Manager. See "Installing Pipeline Manager" in BRM Installation Guide.
Before you run the object_auditing script, you must install IMT Manager.
Before you run the pipeline with the DAT_AccountBatch and FCT_Account modules, you must run the object_auditing script to create the audit event tables that the DAT_AccountBatch and FCT_Account modules need. See "Turning on Object Auditing" in BRM Installation Guide.
IMT Manager runs on HP-UX platform. Rated Event (RE) Loader can load events only into an Oracle database.
For detailed information on supported versions, see "BRM Software Compatibility" in BRM Installation Guide.
The pipeline and RE Loader should run on the same UNIX system.
Note:Although you can install RE Loader on the BRM system or the database system, you get better performance if you install it on the pipeline system.
If the pipeline and RE Loader are on different systems, you need to map the pipeline output directories to a drive local to RE Loader.
For a test system, you use two machines:
Pipeline Manager and Rated Event Loader
For a production system, you run BRM components on multiple machines. Follow the guidelines described in "Putting Together Your BRM System" in BRM Installation Guide.
You can install IMT Manager on HP-UX.
Before installing IMT Manager, you must install BRM. See "Putting Together Your BRM System" in BRM Installation Guide.
IMT Manager installation requires 50 MB of disk space.
You need the following information to install IMT Manager:
The URL, login name, and password for the BRM Software Web site from your BRM sales representative.
Get the following information about your existing BRM system from the existing BRM_Home/setup/pin_setup.values file on your BRM server.
The location of your BRM_Home directory and log directories.
The BRM database and port number.
The SQL*Net alias name for Oracle databases or data source name for SQL Server databases.
The user name and password for the database used by your BRM Server software.
Download the IMT Manager software from the BRM Web site to a temporary directory (temp_dir).
Note:f you downloaded to a Windows workstation, use FTP to copy the .tar.Z file to a temporary directory on your UNIX server. You also need an application such as WinZip for extracting compressed files.
Tip:If you are installing multiple components, use a different temporary directory for each component. Otherwise, files for separate components might be overwritten.
Log in to your system as root.
Stop all BRM processes. See "Starting and Stopping the BRM System" in BRM System Administrator's Guide.
Go to temp_dir and extract the IMT Manager files.
uncompress 7.0_IMTMgr_hpux.tar.Z tar xvf 7.0_IMTMgr_hpux.tar
Go to temp_dir, run the installation script install.ksh, and answer the prompts.
Run the pin_setup script.
Your IMT Manager installation is now complete.
Verify that the IMT Manager Facilities Modules (FMs) were added to the Connection Manager (CM) configuration file. See "Enabling IMT Manager and Disabling Provisioning".
Configure your IMT Manager. See "Configuring IMT Manager".
Important:Install IMT Manager before starting these configuration tasks. See "Installing IMT Manager"
To configure your IMT Manager to work properly and to disable provisioning, perform these tasks described in the sections that follow:
For information about configuration files, see "Using Configuration Files to Connect and Configure Components" in BRM System Administrator's Guide.
Important:If your existing event tables are not partitioned, skip this task.
When you install IMT Manager, you create additional event tables. If your event tables are partitioned, to ensure that the new event tables have the same partitioning layout as your existing event tables, enter this command:
For more information, see "Partitioning Database Tables" in BRM System Administrator's Guide.
To enable IMT Manager, you disable provisioning and make sure that the CM configuration file includes entries for IMT and PDC FMs (Facilities Modules).
Open the Connection Manager (CM) pin.conf file in BRM_Home/sys/cm.
Verify that the following entries are included:
- cm fm_module BRM_Home/lib/fm_tcf.sl fm_tcf_config fm_tcf_init pin - cm fm_module BRM_Home/lib/fm_tcf_pol.sl fm_tcf_pol_config - pin - cm fm_module BRM_Home/lib/fm_imt_pol.sl fm_imt_pol_config - pin - cm fm_module BRM_Home/lib/fm_pdc_pol.sl fm_imt_pol_config - pin - cm fm_module BRM_Home/lib/fm_prov.sl fm_prov_config fm_prov_init pin - cm fm_module BRM_Home/lib/fm_prov_pol.sl fm_prov_pol_config - pin
Note:These lines are added automatically when you install IMT Manager. If the entries do not exist, add them. See "Using Configuration Files to Connect and Configure Components" in BRM System Administrator's Guide.
To disable provisioning,
Add the following entry:
-fm_tcf provisioning_enabled 0
Be sure the dm_pointer configuration line is commented out:
//- cm dm_pointer 0.0.10.2 ip BRM42 -- dm_prov_telco //- fm_prov_telco prov_db 0.0.10.2 / 0
Save and close the pin.conf file.
Restart the CM. See "Starting and Stopping the BRM System" in BRM System Administrator's Guide.
After installing and configuring IMT Manager, use the appropriate utilities to load the configuration files containing the following data:
The event map
IMT and PDC notification events
Load provisioning tags by running the load_pin_telco_tags utility:
load_pin_telco_tags -dv pin_telco_tags_pdc_imt
Note:The pin_telco_tags_pdc_imt file has provisioning tags for both PDC and IMT services.
For more information, see "load_pin_telco_tags".
Load the telco event mapping file, pin_event_map_imt, by running the load_event_map utility.
For more information, see load_event_map in BRM Setting Up Pricing and Rating.
Important:This is a mandatory configuration task.
To enable communication with the Pipeline Manager, BRM uses event notification. Event notification is defined in a notification list stored in the BRM database. This list maps BRM opcodes to the BRM events associated with specified events. When one of these BRM events occurs, the corresponding opcode is executed, which triggers the BRM functionality.
To add the PDC or IMT event notification list to the BRM database, you use the load_pin_notify utility to load the pin_notify_telco_pdc_imt file located in the BRM_Home/sys/data/config directory.
Note:The load_pin_notify utility requires a configuration file. See "Creating Configuration Files for BRM Utilities" in BRM System Administrator's Guide.
Caution:The load_pin_notify utility overwrites all existing notification data in the BRM database. You must load all notification data each time you run the load_pin_notify utility.
To load the PDC or IMT notification events: