This chapter describes how to install Oracle Communications Billing and Revenue Management (BRM) GSM Manager and the Wireless Provisioning Data Manager.
Important:
Before installing the GSM Manager and Wireless Provisioning Data Manager, you should be familiar with the overall integration and installation procedures. See the following documents:The GSM Manager installation includes two sets of components:
GSM server components
Provisioning Data Manager
You can choose to install either or both of these sets of components on the same machine or on different machines.
GSM Manager Customer Center Extension adds functionality to the core Customer Center.
Note:
To install GSM Manager Customer Center Extension, see "Installing GSM Manager Customer Center Extension on Windows" in BRM Installation Guide.
The GSM Self-Care Manager pages are installed with Self-Care Manager. See "Setting Up Customer Self Care with Self-Care Manager" in BRM Managing Customers.
After you install the GSM Manager software, you must:
Be sure that the Connection Manager (CM) and Provisioning Data Manager are configured correctly, and if not, configure them. In most cases, configuration is done during installation, but you should verify that it was done correctly. See the following topics:
Configure the event notification feature required for GSM provisioning. See "Configuring Event Notification for GSM Manager".
Load the supplementary service and service-level ERA provisioning flag descriptions that Customer Center displays. See "Loading GSM Provisioning Flag Definitions".
Load provisioning tags. See "About Provisioning Tags for Telco Services".
Before installing GSM Manager, you must install:
Third-Party software, which includes the PERL libraries and JRE required for installing BRM components. See "Installing the Third-Party Software" in BRM Installation Guide.
BRM. See "Putting Together Your BRM System" in BRM Installation Guide.
Oracle 10g or Oracle 11g.
Before installing GSM Manager Customer Center Extension, you must install:
BRM. See "Putting Together Your BRM System" in BRM Installation Guide.
Customer Center. See "Installing Customer Center on Windows" in BRM Installation Guide.
(Windows) An application such as WinZip for extracting compressed files.
GSM Manager is supported on the HP-UX IA64, Solaris, AIX, and Linux operating systems. For information on disk space requirements for these operating systems, see "Disk Space Requirements" in BRM Installation Guide.
The GSM Manager Customer Center Extension is supported on the Windows platform and requires approximately 10 MB of disk space. To install GSM Manager Customer Center Extension, see "Installing GSM Manager Customer Center Extension on Windows" in BRM Installation Guide.
Note:
If you have already installed the product, features that are already installed cannot be reinstalled without uninstalling them first. To reinstall a feature, uninstall it and then install it again.To install GSM Manager:
Download the software to a temporary directory (temp_dir).
Important:
If you download to a Windows workstation, use FTP to copy the .bin file to a temporary directory on your UNIX server.
You must increase the heap size used by the Java Virtual Machine (JVM) before running the installation program to avoid ”Out of Memory” error messages in the log file. For information, see "Increasing Heap Size to Avoid 'Out of Memory' Error Messages" in BRM Installation Guide.
Go to the directory where you installed the Third-Party package and source the source.me file.
Caution:
You must source the source.me file to proceed with installation, otherwise ”suitable JVM not found” and other error messages appear.Bash shell:
source source.me.sh
C shell:
source source.me.csh
Go to the temp_dir directory and enter this command:
7.5.0_GSM_Mgr_platform_opt.bin
where platform is the operating system name.
Note:
You can use the -console parameter to run the installation in command-line mode. To enable a graphical user interface (GUI) installation, install a GUI application such as X Windows and set the DISPLAY environment variable before you install the software.(Optional) If you are not installing all GSM Manager components on this computer, use the custom install when asked to specify the setup type. Select the components you are installing by typing their respective numbers and click Next. The components are:
GSM Manager
TCFramework
Provisioning_DM
Follow the instructions displayed during installation. The default installation directory for GSM Manager is opt/portal/7.5.
Note:
The installation program does not prompt you for the installation directory if BRM or GSM Manager is already installed on the machine and automatically installs the package at the BRM_Home location.Go to the directory where you installed the GSM Manager package and source the source.me file:
Bash shell:
source source.me.sh
C shell:
source source.me.csh
Go to the BRM_Home/setup directory and run the pin_setup script.
Your GSM Manager installation is now complete. For information on starting the Provisioning Data Manager, see "Starting and Stopping the BRM System" in BRM System Administrator's Guide.
Important:
You should verify that the GSM Manager FMs were added to the Connection Manager (CM) configuration file. See "Using configuration files to connect and configure components" in BRM System Administrator's Guide.Important:
Install GSM Manager and the Provisioning Data Manager software before starting these configuration tasks.In most cases, the server configuration tasks are handled during installation. However, you might need to manually configure some components. You should check the configuration after installation to verify that it is correct.
To configure your GSM Manager system, follow the configuration steps in these sections:
For information about configuration files, see "Using Configuration Files to Connect and Configure Components" in BRM System Administrator's Guide.
Important:
If your event tables are partitioned, this is a mandatory configuration task. If your event tables are not partitioned, skip this task.When you install GSM Manager, you create additional event tables. Run the partition_utils utility from the BRM_Home/apps/partition_utils directory. See "Adding Partitions" and "partition_utils" in BRM System Administrator's Guide.
To configure the Provisioning Data Manager, you edit the Provisioning Data Manager configuration file (BRM_Home/sys/dm_prov_telco/pin.conf).
Open the Provisioning Data Manager configuration file (BRM_Home/sys/dm_prov_telco/pin.conf).
Edit the file according to the instructions in it.
Important:
You must edit the dm_provision prov_ptr entry to connect to the provisioning system.For information about the entries specific to the Provisioning Data Manager, see "Provisioning Data Manager Configuration File Entries".
For information about Data Manager configuration, see "Configuring DM Front Ends and Back Ends" in BRM System Administrator's Guide.
The following entries should appear in the Provisioning Data Manager pin.conf file and have the correct settings.
Note:
These entries are more fully described in the pin.conf file itself.
If you use HP-UX or AIX, replace solaris with hpux or aix in these instructions.
- dm dm_db_no 0.0.10.2 / 0 - dm dm_logfile BRM_Home/dm_prov_telco/dm_prov_telco/dm_provision.pinlog - dm dm_port 11990 - dm dm_sm_obj BRM_Home/sys/dm_prov_telco/dm_prov_telco.so - dm_provision prov_ptr ip Hostname_of_the_provisioning_system20000 - dm_provision connect_retry_interval 0 - dm_provision connect_retries 0 - dm dm_trans_timeout 0
Save the file.
Important:
Before starting the Provisioning Data Manager, you must start the provisioning system.Table 11-1 lists the Provisioning Data Manager configuration file entries.
Table 11-1 Provisioning Data Manager Configuration File Entries
| Entry | Description |
|---|---|
|
- dm dm_db_no |
Specifies the Provisioning Data Manager database number. The number is 0.0.10.2 / 0. Important: The first four digits of this number (0.0.10.2) must match the database number in the pointer to the Provisioning Data Manager in the CM pin.conf file. See "Connecting the Connection Manager to the Provisioning Data Manager". |
|
_dm dm_logfile |
Specifies the path of the log file. |
|
- dm dm_port |
Specifies the port number on which the Provisioning Data Manager listens for connections. The default port number is 11990. Important: This number must match the port number in the pointer to the Provisioning Data Manager in the CM pin.conf file. For more information, see "Connecting the Connection Manager to the Provisioning Data Manager". |
|
- dm dm_sm_obj |
Specifies a pointer to the shared library that contains the code for the Provisioning Data Manager. |
|
- dm_provision prov_ptr ip |
Specifies the host name of the provisioning system. The default port number is 20000. |
|
- dm_provision connect_retry_interval |
Specifies the retry interval in seconds. |
|
- dm_provision connect_retries |
Specifies the number of retries. |
|
- dm dm_trans_timeout |
Specifies the timeout interval in seconds. |
The CM configuration file includes entries that point to the Provisioning Data Manager.
To check or add these entries:
Open the CM configuration file (BRM_Home/sys/cm/pin.conf) and look for the following entries:
- cm dm_pointer 0.0.10.2 ip Hostname_of_the_Provisioning_Data_Manager 11990 - fm_prov_telco prov_db 0.0.10.2 / 0
If the entries do not exist, add them. For more information, see "Guidelines for Database and Port-Number Entries" in BRM System Administrator's Guide.
Restart the CM. See "Starting and Stopping the BRM System" in BRM System Administrator's Guide.
Important:
This is a mandatory configuration task.By default, there are only sample network elements. Before creating telephone numbers and SIM cards, you need to add the network elements that you will use with your GSM services. Your customized network elements are displayed in SIM Administration Center and Number Administration Center.
You assign network elements to SIM cards and telephone numbers:
When you create a block of numbers, you specify the network element for all the numbers in the block.
When you create an order of SIM cards, you specify the network element for all the SIM cards in the order.
For more information, see the following sections:
About Managing SIM Card Inventory
Note:
You cannot define network elements by brand; all network elements can be used by any brand.This section describes how to use utilities to load configuration files required for your system.
Loading the Permit Mapping Files
Note:
Account-level ERAs and sample provisioning tags are loaded as part of installation.Load provisioning by running the load_pin_telco_provisioning utility:
load_pin_telco_provisioning -dv pin_telco_provisioning load_pin_telco_provisioning -dv pin_telco_provisioning_gsm
For more information, see "load_pin_telco_provisioning".
Load telco and GSM service order states by running the load_pin_telco_service_order_state utility:
load_pin_telco_service_order_state -dv pin_telco_service_order_state load_pin_telco_service_order_state -dv pin_telco_service_order_state_gsm load_pin_telco_service_order_state -dv pin_telco_service_order_state_gsm_data load_pin_telco_service_order_state -dv pin_telco_service_order_state_gsm_fax load_pin_telco_service_order_state -dv pin_telco_service_order_state_gsm_sms load_pin_telco_service_order_state -dv pin_telco_service_order_state_gsm_telephony
For more information, see "load_pin_telco_service_order_state".
Note:
If you use custom events you must manually edit the BRM_Home/sys/data/config/pin_event_map_telco_gsm file.Load the telco event mapping file by running the load_event_map utility, as in this example:
load_event_map -dv pin_event_map_telco_gsm
For more information, see load_event_map in BRM Setting Up Pricing and Rating.
Important:
This is a mandatory configuration task.Customer Center displays the provisioning flags of GSM supplementary services and service-level ERAs. You can customize and localize the descriptions for these flags. For information about these flags, see "About Provisioning GSM Services".
To add or change provisioning flags in the BRM database, you edit a copy of the telco_features_and_profiles_states.en_US sample file in the BRM_Home/sys/msgs/telcofeaturesandprofilesstates directory. You then use the load_localized_strings utility to load the contents of the file into the /strings objects.
When you run the load_localized_strings utility, use this command:
load_localized_strings telco_features_and_profiles_states.locale
For more information, see load_localized_strings in BRM Developer's Guide.
Note:
If you are loading a localized version of this file, use the correct file extension for your locale. For a list of file extensions, see "Locale Names" in BRM Developer's Guide.For information on loading the telco_features_and_profiles_states.locale file, see "Loading Localized or Customized Strings" in BRM Developer's Guide.
For information on creating new strings for this file, see "Creating New Strings and Customizing Existing Strings" in BRM Developer's Guide.
Load the GSM number and SIM permit mapping files by running the load_pin_device_permit_map utility:
load_pin_device_permit_map pin_device_permit_map_num_telco_gsm load_pin_device_permit_map pin_device_permit_map_sim_telco_gsm
For more information on this utility, see "Defining Device-to-Service Associations" in BRM Developer's Guide.
Important:
This is a mandatory configuration task.To enable provisioning, GSM delayed activation, and communication with Pipeline Manager, BRM uses event notification.
Before you can use GSM Manager, you must configure the event notification feature as follows:
If your system has multiple configuration files for event notification, merge them. See "Merging Event Notification Lists" in BRM Developer's Guide.
Ensure that the merged file includes the entire event notification list in the BRM_Home/sys/data/config/pin_notify_telco file.
(Optional) If necessary to accommodate your business needs, add, modify, or delete entries in your final event notification list. See "Editing the Event Notification List" in BRM Developer's Guide.
(Optional) If necessary to accommodate your business needs, create custom code for event notification to trigger. See "Triggering Custom Operations" in BRM Developer's Guide.
Load your final event notification list into the BRM database. See "Loading the Event Notification List" in BRM Developer's Guide.
For more information, see "Using Event Notification" in BRM Developer's Guide.
Caution:
Loading the sample price list overwrites existing plan lists. To keep existing plan lists, you need to open the sample GSM price list and add the GSM plans to your existing plan lists.When you install GSM Manager, a sample GSM price list is copied to your system. You can open it directly in Pricing Center, but you must load it into the BRM database to create GSM accounts with it.
To load the sample GSM price list:
Start Pricing Center.
Choose File - Import - Real-time Data.
Import the TelcoGSMSamplePricePlan.xml file on your computer.
The default location on Windows is one of the following:
If you installed Pricing Center with Java Web Start, the default location is your Windows My Document folder.
If you installed Pricing Center as a standalone application, the default location is C:\Program Files\Portal Software\PricingCenter\Sample_Price_Plans\Optional_Manager_Plans.
Note:
As part of importing the XML file, you either confirm your current database connection or specify a database.The objects in the price list appear in the Snapshot pane on the left side of the Pricing Center window.
Drag the pricing objects from the Snapshot pane to the price list work area.
Choose File - Commit to Portal Database and click OK in the confirmation box.
Enter your BRM database login information and click Connect.
The pricing objects in the sample price list are added to your BRM database.
After the sample plan list is committed to the database, click OK in the confirmation box.
Instead of using Pricing Center, you can use the loadpricelist utility to load the TelcoGSMSamplePricePlan.xml file. This file includes the same price list as the IPL file. By default, the file is installed in BRM_Home/setup/scripts.
For information, see the following sections in BRM Setting Up Pricing and Rating:
To test GSM provisioning, you use the BRM Network Simulator utility. See "Testing Provisioning Using BRM Network Simulator".