Installing BRM Thick Clients

8 Installing BRM Thick Clients

Learn how to install applications that provide graphical user interfaces to the data in the Oracle Communications Billing and Revenue Management (BRM) database.

Topics in this document:

Note:

Before installing BRM thick clients, you must first install BRM. See "Installing BRM".
If you upgraded BRM 12.0 to a BRM 12.0 patch set, install the BRM 12.0 patch set client applications. See "Downloading the BRM Client Software".
BRM thick clients (such as Customer Center and Pricing Center) are supported by BRM 12.0 Patch Set 2 and later releases. If you want to use these clients, install the BRM 12.0 Patch Set 2 client software. For information on the clients supported from BRM 12.0 Patch Set 2, see the discussion about new features in BRM in BRM Patch Set Release Notes.
Localized versions of BRM thick clients are supported by BRM 12.0 Patch Set 3 and later releases. The following languages are supported: French, Italian, Spanish, Japanese, Korean, Chinese Simplified, Chinese Traditional, Russian, and Portuguese Brazilian.

About Installing BRM Clients

You can install the BRM clients in GUI mode or in silent mode. Installing the BRM clients in silent mode lets you perform a noninteractive installation of BRM. You can use silent mode to install the clients quickly.

BRM clients installation must be performed by a user who has permissions to write to the oraInventory directory.

For installation instructions, see the following sections:

About BRM Client Package

The BRM Install Package includes the BRM server and BRM client packages. The BRM client package includes all the BRM client applications. You can use the Installer to install one or more of the following individual BRM client applications:

Business Configuration Center (referred as Field Validation Editor)
Revenue Assurance Center
Developer Center
Customer Center (including GSM Manager: Customer Center Extension)

GSM Manager: Customer Center Extension enables support for assigning SIM cards and telephone numbers in Customer Center. See the discussion about setting up GSM services in Customer Center Help.

Note:
You must install the GSM Manager Customer Center Extension on a system on which Customer Center is installed.
Customer Center SDK

You can use JBuilder (for example, Borland JBuilder) for various tasks such as creating WAR files for Self-Care Manager and custom pages for Customer Center.
Collection Center
Collections Configuration Center
IP Address Administration Center
Number Administration Center
Permissioning Center
Payment Tool

Note:
You can install Payment Tool only on Windows.
Payment Center
Pricing Center

Note:
When you install Pricing Center, you automatically install the Resource Editor and the Zone Mapper.
Self-Care Manager
SIM Administration Center
Voucher Administration Center
Suspense Management Center
Localization (L10N) SDK

For installing Customer Center, Pricing Center, Self-Care Manager, or Suspense Management Center, see:

For installing other BRM client applications, see "Installing BRM Clients in GUI Mode".

Installing Self-Care Manager

To use Self-Care Manager, you must install a third-party application server before installing Self-Care Manager. Supported application servers include Tomcat and WebLogic. For more information, see the vendor installation instructions for the application server you are using.

Note:

You must install the application server and Self-Care Manager on the same system. The Connection Manager (CM) can be on the same system as Self-Care Manager or on a different system.

For instructions on installing Self-Care Manager, see "Installing Individual BRM Clients". After installing Self-Care Manager, configure the application server to work with Self-Care Manager.

Installing Customer Center

You must install Customer Center on a system that includes the following:

A third-party Web server. BRM currently supports Apache Tomcat. For supported versions, see "Additional BRM Software Requirements" in BRM Compatibility Matrix.
Java Web Start technology with SSL enabled. See "Enabling SSL for Web Start Deployment" in BRM System Administrator's Guide.

You then use the Web server and Java Web Start technology to distribute Customer Center to your CSRs.

To use Customer Center, CSRs download it from the Web server to their Windows client systems. When CSRs run Customer Center, they run their local versions that communicate directly with the BRM database.

Each time a CSR runs Customer Center, the application uses Java Web Start to check the Web server for updates and automatically download new versions.

Note:

You can install Customer Center on either a UNIX or Windows system, but Customer Center can be run only on a Windows system.

Install Customer Center on the directory on which Apache Tomcat is installed; for example, Tomcat_home\webapps\ROOT. For instructions on installing Customer Center, see "Installing Individual BRM Clients". After installing Customer Center, configure the application server to work with Customer Center.

Installing Pricing Center

Pricing Center can be installed as a standalone application or on a system with a Web server.

If you will use Pricing Center as a standalone application on a single system, install the standalone version.
If you are installing with a Web server, you use the Web server and Java Web Start technology to distribute Pricing Center to your CSRs. You must install the third-party application server (Apache Tomcat) before installing Pricing Center. You must also enable SSL for Java Web Start. See "Enabling SSL for Web Start Deployment" in BRM System Administrator's Guide.

To use Pricing Center, CSRs download it from the Web server to their Windows client systems. When CSRs run Pricing Center, they run their local versions that communicate directly with the BRM database.

Each time CSRs run Pricing Center, the application uses Java Web Start to check the Web server for updates and to automatically download any new versions it finds.

Install Pricing Center on the directory on which Apache Tomcat is installed; for example, Tomcat_home\webapps\ROOT. For instructions on installing Pricing Center, see "Installing Individual BRM Clients". After installing Pricing Center, configure the application server to work with Pricing Center.

Installing Suspense Management Center

Suspense Management Center can be installed as a standalone application or on a system with a Web server.

If you will use Suspense Management Center as a standalone application on a single system, install the standalone version.
If you are installing with a Web server, you use the Web server and Java Web Start technology to distribute Suspense Management Center to your CSRs. You must install the third-party application server (Apache Tomcat) before installing Suspense Management Center. You must also enable SSL for Java Web Start. See "Enabling SSL for Web Start Deployment" in BRM System Administrator's Guide.

To use Suspense Management Center, CSRs download it from the Web server to their Windows client systems. When CSRs run Suspense Management Center, they run their local versions that communicate directly with the BRM database.

Each time a CSR runs Suspense Management Center, the application uses Java Web Start to check the Web server for updates and automatically download new versions.

Install Suspense Management Center on the directory on which Apache Tomcat is installed; for example, Tomcat_home\webapps\ROOT. For instructions on installing Suspense Management Center, see "Installing Individual BRM Clients". After installing Suspense Management Center, configure the application server to work with Suspense Management Center.

Downloading the BRM Client Software

You can download the BRM client software from the following locations:

For release 12.0: From the Oracle software delivery website (https://edelivery.oracle.com)
For a 12.0 Patch Set: From the Oracle support website (https://support.oracle.com)

Search for and download the Oracle Communications Billing and Revenue Management 12.0.0.x.0 software, where x is 0 for the 12.0 release, 1 for Patch Set 1, 2 for Patch Set 2, and so on. Unzip the pPatchNumber_12.0.0.x.0_Generic.zip file. The Zip archive includes one of these JAR files for installing BRM clients:

brmclients_12.0.0.x.0_generic.jar contains the client software in English.
brmclients_all_12.0.0.x.0_generic.jar contains the localized version of the client software.

Installing BRM Clients in GUI Mode

The steps for installing BRM clients in GUI mode depend on the clients you choose to install:

To install all BRM clients, select the Complete installation option.

See "Installing All BRM Clients" for more information.
To choose one or more BRM clients to install each time you run the installer, select the Custom installation option.

This option installs only the clients that you select. This option is recommended for advanced users.

See "Installing Individual BRM Clients" for more information.

Installing All BRM Clients

You can install Developer Center and Self Care Manager on UNIX, and the other BRM clients on Windows.

To install all BRM clients:

Obtain the BRM clients software. See "Downloading the BRM Client Software".
Go to the temp_dir directory, do one of the following:

On UNIX, run one of the following commands:
- To start the GUI installer:
```
Java_home/bin/java -jar brmclients_12.0.0.V.0_generic.jar
```
  where:
  - Java_home is the directory in which you installed the latest supported Java version.
  - v is the BRM version; for example, v is 0 for BRM 12.0, 1 for BRM 12.0 Patch Set 1, and 2 for BRM 12.0 Patch Set 2.
- To start the GUI installer and install the application using the oraInventory directory in a different location:
```
Java_home/bin/java -jar brmclients_12.0.0.V.0_generic.jar  -invPtrLoc FilePath/oraInst.loc
```
  where FilePath is the path to the directory in which the oraInst.loc file is located.
- To start the GUI installer and create a silent installer response file during the installation:
```
Java_home/bin/java -jar brmclients_12.0.0.V.0_generic.jar -record -destinationFile path
```
  where path is the response file location and name.
On Windows, run one of the following commands:
- To start the GUI installer:
```
Java_home/bin/java -jar brmclients_12.0.0.V.0_generic.jar
```
  where v is the BRM version; for example, v is 0 for BRM 12.0, 1 for BRM 12.0 Patch Set 1, and 2 for BRM 12.0 Patch Set 2.
- To start the GUI installer and install the application using the oraInventory directory in a different location:
```
Java_home/bin/java -jar brmclients_12.0.0.V.0_generic.jar FilePath/oraInst.loc
```
  where FilePath is the path to the directory in which the oraInst.loc file is located.
- To start the GUI installer and create a silent installer response file during the installation:
```
Java_home/bin/java -jar brmclients_12.0.0.V.0_generic.jar -record -destinationFile path
```
  where path is the absolute path to the response file.
The Welcome screen appears.
Click Next.

The Installation Location screen appears.
Enter the full path or browse to the directory in which to install BRM.
Click Next.

If the Language Selection screen appears, ensure that the default language (English) is selected and click Next.

Note:
If the "Select at least one language" error appears, click OK and then proceed to next step.

The Installation Type screen appears.
Select Complete, and click Next.

If you are installing BRM 12.0 clients, the SSL Authentication screen appears. Proceed to step 13.

If you are installing BRM 12.0 Patch Set 1 clients, the Suspense Management Center Installation Type screen appears. Proceed to step 11.

If you are installing clients from BRM 12.0 Patch Set 2 or later releases, the Customer Center Installation Type screen appears. Proceed to step 7.
(From BRM 12.0 Patch Set 2 only) Select the standalone or Web server installation option and click Next.

The Customer Center Web Server screen appears.
(From BRM 12.0 Patch Set 2 only) In the Web Server URL field, enter the complete URL of the Customer Center Web server and click Next.

The Pricing Center Installation Type screen appears.
(From BRM 12.0 Patch Set 2 only) Select the standalone or Web server installation option and click Next.

The Pricing Center Web Server screen appears.
(From BRM 12.0 Patch Set 2 only) In the Web Server URL field, enter the complete URL of the Pricing Center Web server and click Next.

The Suspense Management Center Installation Type screen appears.
(From BRM 12.0 Patch Set 1 only) Select the standalone or Web server installation option and click Next.

The Suspense Manager Web Server screen appears.
(From BRM 12.0 Patch Set 1 only) In the Web Server URL field, enter the complete URL of the Suspense Management Web server and click Next.

The SSL Authentication screen appears.
Do one of the following:
- If you do not want to enable secure communication for BRM clients, deselect the Enable SSL check box.
- To enable secure communication for BRM clients, leave the Enable SSL check box selected.
In the Oracle Client Wallet Password field, enter a password for the Oracle client wallet.
In the Confirm Wallet Password field, enter the Oracle client wallet password again.
Enter the client wallet password again.
Click Next.

The Installation Summary screen appears.
Review your selections, and click Install.

The Installation Progress screen appears, and the installation begins.

Note:

After the installation begins, you cannot stop or cancel the installation.

When the installation is done, click Next, the Installation Complete screen appears.

The installer checks for all required software and displays errors if it detects any missing or unavailable components or if any connectivity issues occur.

For information about BRM installer logs, see "Troubleshooting the BRM Installation."

Installing Individual BRM Clients

You can install a subset of BRM client applications (for example, Developer Center and Revenue Assurance Center) on UNIX or Windows.

Note:

If you already have a client application installed, you must uninstall it before installing the new version.

To install individual BRM clients:

Obtain the BRM clients software. See "Downloading the BRM Client Software".
Go to the temp_dir directory and then do one of the following:

On UNIX, run one of the following commands:
- To start the GUI installer:
```
Java_home/bin/java -jar brmclients_12.0.0.V.0_generic.jar
```
  where:
  - Java_home is the directory in which you installed the latest supported Java version.
  - v is the version of the patch set; for example, v is 0 for BRM 12.0, 1 for BRM 12.0 Patch Set 1, and 2 for BRM 12.0 Patch Set 2.
- To start the GUI installer and install the application using the oraInventory directory in a different location:
```
Java_home/bin/java -jar brmclients_12.0.0.V.0_generic.jar FilePath/oraInst.loc
```
  where FilePath is the path to the directory in which the oraInst.loc file is located.
- To start the GUI installer and create a silent installer response file during the installation:
```
Java_home/bin/java -jar brmclients_12.0.0.V.0_generic.jar -record -destinationFile path
```
  where path is the response file location and name.
On Windows, run one of the following commands:
- To start the GUI installer:
```
Java_home/bin/java -jar brmclients_12.0.0.V.0_generic.jar
```
  where v is the version of the patch set; for example, v is 0 for BRM 12.0, 1 for BRM 12.0 Patch Set 1, and 2 for BRM 12.0 Patch Set 2.
- To start the GUI installer and install the application using the oraInventory directory in a different location:
```
Java_home/bin/java -jar brmclients_12.0.0.v.0_generic.jar FilePath/oraInst.loc
```
  where FilePath is the path to the directory in which the oraInst.loc file is located.
- To start the GUI installer and create a silent installer response file during the installation:
```
Java_home/bin/java -jar brmclients_12.0.0.v.0_generic.jar -record -destinationFile path
```
  where path is the response file location and name.
The Welcome screen appears.
Click Next.

The Installation Location screen appears.
Enter the full path or browse to the directory in which to install the BRM clients.

Note:

If you already have a client application installed and installing a new client application, enter the full path or browse to the directory in which the existing client application is installed.
Click Next.

If the Language Selection screen appears, ensure that the default language (English) is selected and click Next.

Note:

If the "Select at least one language" error appears, click OK and then proceed to next step.

The Installation Type screen appears.
Select Custom, and click Next.

The Feature Sets Selection screen appears.
From the clients list, select the clients to install.
Click Next.

If you are installing BRM 12.0 clients, the SSL Authentication screen appears. Proceed to step 11.

If you are installing BRM 12.0 Patch Set 1 clients, the Suspense Management Installation Type Screen appears if you selected to install Suspense Management Center. Otherwise, the SSL Authentication screen appears. Proceed to step 11.

If you are installing other patch set clients, the corresponding Installation Type screen appears. For example, if you selected to install Customer Center, the Customer Center Installation Type Screen appears.
(BRM 12.0 patch set installation only) Select the standalone or Web Server installation option and click Next.

The corresponding Web Server screen appears.
(BRM 12.0 patch set installation only) In the Web Server URL field, enter the complete URL of the client's Web server and click Next.

The SSL Authentication screen appears.
Do one of the following:
- If you do not want to enable secure communication for BRM clients, deselect the Enable SSL check box.
- To enable secure communication for BRM clients, leave the Enable SSL check box selected.
In the Client Wallet Password field, enter a password for the client Oracle wallet.
Click Next.

The Installation Summary screen appears.
Review your selections, and click Install.

The Installation Progress screen appears, and the installation begins.

Note:

After the installation begins, you cannot stop or cancel the installation.

When the installation is done, click Next, the Installation Complete screen appears.

The installer checks for all required software and displays errors if it detects any missing or unavailable components or if any connectivity issues occur.

For information about BRM installer logs, see "Troubleshooting the BRM Installation".

Installing BRM Clients in Silent Mode

The silent installation uses a response file in which you have set installation information. To obtain the response file, you run the GUI installer for the first install. The GUI installer generates a response file that contains the key-value pairs based on the values that you specify during the GUI installation. You can then copy and edit the response file to create additional response files for installing the BRM client applications on different machines.

Creating a Response File

To create a response file:

Create the response file by doing one of the following:
- Create a copy of the response file that was generated during the GUI installation. See "Installing BRM Clients in GUI Mode" for more information.
  
  Note:
  
  The GUI Installer does not save passwords provided during installation in the response file. You must manually add the passwords after creating a copy of the response file.
- Go to the temp_dir directory in which you downloaded the BRM client software pack, and create a response file by doing one of the following:
  - On UNIX, run the following command:
```
Java_home/bin/java -jar brmclients_12.0.0.v.0_generic.jar -record -destinationFile path/SilentInstall.rsp
```
  - On Windows, run the following command:
```
java -jar brmclients_12.0.0.v.0_generic.jar -getResponseFileTemplates
```
    v is the BRM version; for example, v is 0 for BRM 12.0, 1 for BRM 12.0 Patch Set 1, and 2 for BRM 12.0 Patch Set 2.
A response file is created with the default values. You can create as many response files as needed.
Open the file in a text editor.
Modify the response file you copied by specifying the key-value information for the parameters you want in your installation.
Save and close the response file.

Performing a Silent Installation

To perform a silent installation:

Create a response file. See "Creating a Response File".
Copy the response file you created to the machine on which you will run the silent installation.
On the machine on which you will run the silent installation, go to the temp_dir directory in which you downloaded the BRM client software pack, and do one of the following:
- On UNIX, run the following command:
```
Java_home/bin/java -jar brmclients_12.0.0.v.0_generic.jar -debug -invPtrLoc  Inventory_home/oraInventory/oraInst.loc [parameter=value] -responseFile path -silent
```
  where:
  - v is the BRM version; for example, v is 0 for BRM 12.0, 1 for BRM 12.0 Patch Set 1, and 2 for BRM 12.0 Patch Set 2.
  - path is the location and name of your response file.
  - parameter is the name of an installation parameter.
  - value is the value of the installation parameter.
  For example:
```
Java_home/bin/java -jar brmclients_12.0.0.2.0_generic.jar -debug -invPtrLoc Ora/oraInventory/oraInst.loc INSTALL_TYPE=Complete -responseFile /tmp/brm_complete.rsp  -silent
```
  The installation runs silently in the background.
- On Windows, run the following command:
```
java -jar brmclients_12.0.0.v.0_generic.jar -debug -invPtrLoc Inventory_home/oraInventory/oraInst.loc [parameter=value] -responseFile path -silent
```
  where:
  - v is the BRM version; for example, v is 0 for BRM 12.0, 1 for BRM 12.0 Patch Set 1, and 2 for BRM 12.0 Patch Set 2.
  - parameter is the name of an installation parameter.
  - value is the value of the installation parameter.
  - path is the location and name of your response file.
  For example:
```
java -jar brmclients_12.0.0.2.0_generic.jar -debug -invPtrLoc Ora/oraInventory/oraInst.loc INSTALL_TYPE=Complete -responseFile /tmp/brm_complete.rsp  -silent
```
  The installation runs silently in the background.

The Installer checks for all required software and writes errors to a log file if it detects any missing or unavailable components or if any connectivity issues occur.

For information about BRM installer logs, see "Troubleshooting the BRM Installation".

Configuring the Localization SDK on Windows

After installing the localization (L10N) SDK, you must configure the SDK on Windows. See "Installing Individual BRM Clients" for installing the Localization SDK.

To configure the localization SDK on Windows, in a command window, use the subst command to substitute the drive letter for the build tree directory of the SDK.

If you installed the SDK in the default location, enter the command as follows:

subst W: "C:\Oracle_Home\LocalizationSDK"

Granting Administrative Privileges to Pricing Center Users

You use the pricing_admin.pl script to grant administrative privileges to Pricing Center users. Users with administrative privileges are called pricing admins.

To grant administrative privileges to Pricing Center users, perform the procedures in the following sections:

Modifying the Database Configuration File

Go to the DM directory:
```
cd BRM_home/sys/dm_oracle
```
Back up the database configuration file (pin.conf).

Note:
You will be restoring the pin.conf file later in the procedure.
Open the pin.conf file with a text editor.
If the dd_write_enable_objects entry is set to 0, set the entry to 1.
If the crypt entry is commented out, uncomment it and configure it according to the notes that precede this entry:
```
- crypt Encrypt_method| BRM_home/lib/Encryption_library "Secret_key"
```
where:
- Encrypt_method is the type of encryption method, which is either aes or ozt.
- Encryption_library is the path and filename of the encryption library. The prefix for the library is lib for Solaris and Linux, or null "" for Windows. The extension for the library is .so for Solaris and Linux, and .dll for Windows.
- Secret_key is your encrypted AES or OZT key.
For more information, see "Configuring the Data Manager for AES Encryption" or "Configuring the Data Manager for Oracle ZT PKI Encryption" in BRM Developer's Guide.
Save and close the file.
Stop and restart the DM and CM. See "Starting and Stopping the BRM System" in BRM System Administrator's Guide.

Modifying the pricing_admin.pl Script Configuration File

Go to the BRM_Home\setup\scripts directory.
Open the setup configuration file (pin.conf) file with a text editor.

Check that the following entries are specified in the pin.conf file:

- nap login_type 1
- - userid 0.0.0.1 /service/admin_client 1

Specify appropriate values for the login_name and parameters:

- nap login_name login_name
- nap login_pw password

For example:

- nap login_name integrate
- nap login_pw integrate

Enter the host name and port number of your server in the cm_ptr entry:
```
- nap cm_ptr ip host_name port_number
```

If you are using Pipeline Manager, specify values for the entries described in Table 8-1. These entries specify Pipeline Manager configuration data used by the pricing_admin.pl script to set up and maintain pricing admins and the Pipeline Manager database for Pricing Center.

Table 8-1 Pipeline Manager Configuration Data

Entry	Description
default_table_space_name	The tablespace that newly created Oracle users are assigned to. The default is INTEGRATE_TS_1_DAT. If the default tablespace is not available in the Pipeline Manager database, use an available existing tablespace or create a new one. Important: You must specify a value for default_table_space_name before you run the pricing_admin.pl script with the -set parameter.
database_role_name	The role that provides select, insert, delete, and update privileges on IFW_* and JSA_* tables. The default is INTEGRATE_ROLE_ALL. If the default role is not available in the Pipeline Manager database, use an existing role that provides these privileges or create a new role. If you use the -init parameter, the entry is optional.
host	The host name for the server where the Pipeline Manager database is located and running.
port	The port number used by the Pipeline Manager database listener.
db	The name of the Pipeline Manager database instance. Note: You must set the db value to the ORACLE_SID value. If you set the db value to the SERVICE_NAME value, BRM does not generate an error when creating the /config/pricing_admin object; however, you cannot connect to the Pipeline Manager database from Pricing Center.
db_type	The name of the database vendor. The value should be one of the system database driver groups of entries in the jsaconf.properties file, for example, oracle.
login_name	The default Pipeline Manager database user name. Important: You must specify a value for login_name before you run the pricing_admin.pl script with the -init parameter.
login_pw	The password of the default Pipeline Manager database user. Important: You must specify a value for login_pw before you run the pricing_admin.pl script with the -init parameter.
admin	The DBA on the Pipeline Manager database that has user creation privileges.
admin_pw	The password of the DBA account.
db_alias	The alias used to log in to the Pipeline Manager database. Important: Ensure that the tnsnames.ora file also contains an entry with this alias.

Following is a sample pin.conf entry value:

- pipeline default_table_space_name    INTEGRATE_TS_1_DAT
- pipeline database_role_name          INTEGRATE_ROLE_ALL
- pipeline host                        ttal-013
- pipeline port                        1521
- pipeline db                          pindb
- pipeline db_type                     oracle
- pipeline login_name                  integrate
- pipeline login_pw                    integrate
- pipeline admin                       system
- pipeline admin_pw                    manager
- pipeline db_alias                    ttal

Note:

To ensure that Pricing Center can connect to the server, add the name and IP address of the Pipeline Manager host system to the host file of each machine running Pricing Center.

Save and close the file.

Setting Up the Database Server for the Pipeline Manager Administrator

To set up an Oracle database server for the Pipeline Manager administrator:

Edit the tnsnames.ora file to specify HOST, PORT, and SERVICE_NAME values. Use the same values that you used for the host, port, and db entries in the setup configuration file (BRM_home\setup\scripts\pin.conf).

The following is the required name entry in the tnsnames.ora file that corresponds to the sample pin.conf file shown in "Modifying the pricing_admin.pl Script Configuration File."

Note:
The database alias in the following example is ttal-013, the port name is 1521, and the Pipeline Manager database name (SERVICE_NAME) is pindb. Be sure to change these values to match your environment.
```
TTAL-013 =
 (DESCRIPTION =
  (ADDRESS_LIST =
   (ADDRESS = (PROTOCOL = TCP) (HOST = ttal_013) (PORT = 1521) )
  )
 (CONNECT_DATA =
  (SERVICE_NAME = pindb)
 )
)
```
To ensure that the pin.conf entries for admin, admin_pw, db_alias, and host are correct, try connecting to the Pipeline Manager database using the following command:
```
sqlplus admin/admin_pw@db_alias
```

Initializing the Pricing Admin Configuration Object

Initialize the pricing admin configuration object by running the pricing_admin.pl script:

Go to the BRM_home\setup\scripts directory.
Run the pricing_admin.pl script with the -init parameter:
```
perl pricing_admin.pl -init
```
If initialization is successful, the system returns this line:
```
Initialized config object for pricing admin.
```
Restore the original database configuration file (pin.conf) that you backed up in "Modifying the Database Configuration File".
Stop and restart the DM to apply the new settings. See "Starting and Stopping the BRM System" in BRM System Administrator's Guide.

Specifying Administrative Privileges for Pipeline Manager Users

To specify administrative privileges for Pipeline Manager users:

Ensure that every Pipeline Manager user who will be a pricing admin has a CSR account in BRM (an account using the admin_client service). You create CSR accounts in Customer Center by using the CSR Plan. See information about the Account Creation wizard's Contact page in Customer Center Help.
Create a text file that has the user name and password (in that order) of each pricing admin on a separate line. User names and passwords must be separated by a space. For example:
```
john_jones password
mary_allen password
```
Note:

BRM user names (login names) are case sensitive, but Pipeline Manager user names are not. Therefore, type the names exactly as specified in Customer Center, but avoid using names that are too similar. For example, do not create two accounts with the user names ”Smith” and ”smith” because they will both be logged in to Pipeline Manager as ”SMITH.”
Go to the BRM_home\setup\scripts directory.
Run the pricing_admin.pl script with the -set parameter:
```
perl pricing_admin.pl -set < text_file
```
where text_file is the name of the file you created in Step 2.
Delete the text file if security is a concern.

Removing Pricing Admins

This section describes how to remove single and multiple users from the Pipeline Manager database.

Removing One Pricing Admin

To remove one pricing admin from the database:

Go to the BRM_home\setup\scripts directory.
Run the pricing_admin.pl script with the -remove parameter:
```
perl pricing_admin.pl -remove
```
When prompted, enter the user name to be deleted.

For each pricing admin removed, the system responds with this line:
```
Removed pricing admin user_name
```
Repeat Step 3 until all appropriate user names are removed.

Removing Multiple Pricing Admins

To remove multiple pricing admins from the database:

Go to the BRM_home\setup\scripts directory.
Create a text file (text_file) containing only the user names that you want to remove. Put each user name on a separate line, as in this example:
```
john_jones
mary_allen
```
Run the pricing_admin.pl script with the -remove and text_file parameters:
```
perl pricing_admin.pl -remove < text_file
```

Starting a BRM Client Application on UNIX

You can install Developer Center and Self Care Manager on UNIX only.

To start a BRM client application on UNIX:

Go to the install_dir directory, where install_dir is the directory in which you installed the BRM clients.
Grant permissions for the BRM client application by running the following command:
```
chmod 755 applicationName.sh
```
where applicationName is the name of the BRM client application you want to start.
Run the following command:
```
./applicationName.sh
```

Starting a BRM Client Application on Windows

To start a BRM client application on Windows:

From the start options, choose ProductName, where ProductName is the name of the BRM client application you want to start.

The Login dialog box appears.
Enter your login name and password.

For information about login names and passwords for client applications, see "Implementing System Security" in BRM System Administrator's Guide.
To connect to a database other than the one specified during installation, click Connection Info and enter the host name and port number.
Click OK.

Starting a BRM Client Application from Java Web Start

To start Customer Center, Pricing Center, or Suspense Management Center from the Java Web Start Application Manager:

Start Java Web Start from the start options.
If you do not see Customer Center listed in the Application Manager, choose View - Downloaded Applications.
Select Customer Center and click Start.

Problems Installing BRM Client Applications

This section describes problems you might encounter when installing BRM client applications and their solutions.

Problem: Cannot Start a Client Application after Installation

You cannot start one of the client applications, even though the installation appeared to be successful.

Possible Cause

BRM could not add the client application to your Windows path because the path is too long. Therefore, Windows cannot find it.

Solution

Review your path statement and delete references to obsolete programs. For more information, see your Windows documentation. Reboot the system before you try restarting the client application.

What's Next?

After installing the BRM client applications, you can test BRM with your business models:

For an overview of setting up product offerings, see "About Creating Product Offerings" in BRM Creating Product Offerings.
For an overview of setting up billing, see "Configuring Billing" in BRM Configuring and Running Billing.
For an overview of setting up customer account creation and managing customer accounts, see "Customizing Account Creation" in BRM Managing Customers.