This chapter describes how to install Oracle Communications Billing and Revenue Management (BRM) applications on Windows.
Note:
The BRM server components (Connection Manager (CM), Data Manager (DM), and so on) do not run on Windows systems.The BRM system includes several client applications that provide graphical user interfaces to the data in the BRM database. You use BRM client applications to manage customers and payments and to configure your BRM system. See ”About the BRM Client Applications” in BRM Concepts.
The BRM system also includes one server application, Self-Care Manager, that provides customer self-care services using Web browsers and wireless devices. Customers use Self-Care Manager to display and modify their account data. See "About Self-Care Manager" in BRM Managing Customers.
You can install BRM applications in any combination and in any order; however, you must first install BRM. See "BRM Installation Overview".
Table 10-1 lists the approximate disk space required to download, extract, and install each client application.
Note:
BRM client applications require the Java Runtime Environment (JRE). The JRE is included in each application package and is approximately 50 MB. Once the JRE is installed with a BRM application, it will not be reinstalled.Table 10-1 Required Disk Space for Windows Applications
| Application | Type | Required Disk Space |
|---|---|---|
|
Brand Manager |
Client application |
100 MB |
|
Business Configuration Center |
Client application |
100 MB |
|
Collections Configuration |
Client application |
100 MB |
|
Customer Center |
Client application |
125 MB |
|
Customer Center SDK |
Developer tool |
54 MB |
|
Developer Center |
Developer tool |
110 MB |
|
Payment Tool* |
Client application |
140 MB |
|
Permissioning Center |
Client application |
112 MB |
|
Pricing Center |
Client application |
165 MB |
|
Self-Care Manager |
Server application |
100 MB |
* Payment Center is installed with Payment Tool. It is accessible only if you purchase the Payment Suspense Manager feature.
This section describes how to install and start all BRM client applications except Customer Center and Pricing Center.
To install Customer Center, see "Installing Customer Center on Windows".
To install Pricing Center, see "Installing Pricing Center on Windows".
To install the BRM client applications, you need the following:
An application such as WinZip for extracting compressed files.
The following information about the machine running the CM to which Customer Center, Payment Tool, Payment Center, and Pricing Center will connect:
Computer or server name
Port number
Database number
Windows users must have administrator privileges to install Customer Center, Payment Tool, or Pricing Center.
A supported version of the 32-bit JDK installed. For 64-bit systems, confirm that the JDK location is included in your path, or in the standard C:\Program Files (x86)\Java location on Windows.
For information on localized versions of the client applications, see "Creating a Localized Version of BRM" in BRM Developer's Guide.
Download the software to a temporary directory (temp_dir).
Important:
To install Payment Center, download and install the PaymentTool.zip file.Extract the files in the .zip file to a temporary directory.
For information on installing Customer Center, see "Installing Customer Center on Windows".
For information on installing Pricing Center, see "Installing Pricing Center on Windows".
To install all other client applications:
Follow the steps in "Downloading the Compressed Files".
Go to the temporary directory where you extracted the client application download file.
Double-click Setup.exe.
On the Choose Destination Location screen, select the destination folder for the program and click Next.
On the Connection Manager screen, enter the server, port, and database information and click Next.
For a demonstration system, enter the server name (computer where you installed the CM) and accept the default values of 11960 and 0.0.0.1.
On the Select Program Folder screen, accept the default program folder Portal or select a new one; click Next.
On the Start Copying Files screen, click Next to start installing the application.
On the Setup Complete screen, you can choose to restart the computer or wait until you have installed all the applications.
Click Finish to complete the process.
This procedure applies to any BRM client application, but there are additional ways to start Customer Center and Pricing Center. See "Starting Customer Center" and "Starting Pricing Center".
To start a client application:
From the start options, choose ProductName, which is under Portal, where ProductName is the BRM client application you want to start.
The Login dialog box appears.
Enter your login name and password.
For information on 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.
For information on how to use a client application, see the Help for that application.
On Windows 7 and Windows 8.1, Payment Tool must be run as an administrator. See the Windows 7 or Windows 8.1 online Help for information.
To install Customer Center, see the following:
You must install Customer Center on a system with a Web server. 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.Obtain the following information about the machine running the CM to which Customer Center will connect:
Computer or server name
Port number
Database number
Make sure you have Windows administrator privileges.
Install a third-party Web server.
Make sure each Customer Center client system has a Web browser.
For a list of supported browsers, see "BRM Software Compatibility".
Optionally, you can install the Java Runtime Environment (JRE) 1.6.0_26 on each client system. If you do not do it in advance, JRE 1.6.0_26 will be installed as part of downloading Customer Center.
See "Installing Java Web Start and Downloading Customer Center".
To display decimals to the desired precision, ensure that your regional settings are properly defined.
If you have not already downloaded and extracted the client application, follow the steps for "Downloading the Compressed Files".
Install Customer Center on the same system as your Web server.
Go to the temporary directory where you unzipped the client application download file.
Double-click Setup.exe.
Enter a destination folder. You can enter your Web server's document root directory, such as C:\Program Files\Apache Group\Apache\htdocs on an Apache Web server or choose one of the following default installation paths:
For Windows XP:
C:\Program Files\Portal Software\CustomerCenter
For Windows 7 and 8.1:
C:\Program Files (x86)\Portal Software\CustomerCenter
You can also enter a subdirectory of your Web server's document root directory or another directory that you map to your Web server.
Enter the name and port number of the BRM server where the CM is running.
Enter the database number for the DM (for example, 0.0.0.1).
Enter the full URL to the location of Customer Center on your Web server. The default URL is http://machine_name where machine_name is the name of the system where you are installing Customer Center.
Important:
Your Web server must be mapped to the URL you specify.Specify the URL as follows:
If you are installing Customer Center in your Web server's document root directory, or a directory mapped to your Web server's document root directory, use the default URL.
If you are installing Customer Center in a subdirectory of your Web server's document root, add the subdirectory names to the default URL. But do not change the top-level URL.
For example, if your default URL is http://server1, and you install Customer Center in the applications subdirectory of your document root, your URL should be http://server1/applications.
If you are installing Customer Center in a directory outside your Web server directory, map that installation directory to a subdirectory of your document root. Then add the name of the subdirectory of the document root to the default URL.
For example, you can install Customer Center in C:\Program Files\Portal Software\CustomerCenter, and then map that directory to the applications subdirectory of the Web server document root. If your default URL is http://server1, your URL should be http://server1/applications.
If your Web server uses a port number other than 80, add the port number to the URL as follows: URL:port_number.
For example, if your Customer Center URL is http://server1 and your port number is 81, your URL should be http://server1:81.
See your Web server documentation for information on the document root directory and mapping other directories to your URL.
Note:
To access Customer Center, add the file name CustomerCenter_en.html to the URL you specify here. Do not add the file name on this screen.For Apache and iPlanet Web servers, open your Web server's MIME types file to add an entry for JNLP, a special file type associated with Java Web Start. For IIS Web servers, you do not need to do this.
Add a MIME type as follows:
For an Apache Web server, add the following entry to the mime.types file:
application/x-java-jnlp-file JNLP
For an iPlanet Web server, add the following entry to the mime.types file:
type=application/x-java-jnlp-file exts=JNLP
You can also use the iPlanet Server Manager to add a MIME type.
For more information, see your Web server documentation.
For iPlanet Web servers only, edit the mime.types file for your Web server to enable downloading of .exe files. This is necessary so that client systems can download the Java Web Start installation file from the Web server.
Change the .exe file extension's MIME type association as follows:
Remove exe, and the comma before it, from this line:
type=magnus-internal/cgi exts=cgi,bat,exe
Add exe, preceded by a comma, to the end of this line:
type=application/octet-stream exts=bin,exe
You can also make this change with the iPlanet Server Manager. See the iPlanet documentation.
Stop and restart your Web server.
To set the heap size for Java Web Start implementations:
Open your CustomerCenter_locale.jnlp file.
Change the j2se element to set the initial and maximum heap size.
The default entry looks like this:
<j2se version="1.4*"/>
For example, this entry changes the initial heap size to 128 megabytes and the maximum heap size to 256 megabytes:
<j2se version="1.4*" initial-heap-size="128m" max-heap-size="256m"/>
Note:
The heap sizes specified in the JNLP file is used for all associated Customer Center clients.Stop and restart Customer Center to make the change take effect.
The first time you start Customer Center on a client system, you download and install Java Web Start.
Note:
With Internet Explorer, you have the option of installing directly from the server without downloading the file.Go to this URL in your Web browser:
http://machine_name/CustomerCenter_en.html
Replace machine_name with the name of the system running the Web browser and Customer Center. If Customer Center is located in a subdirectory of your Web browser's document root directory, include the full path to CustomerCenter_en.html.
If your Web server uses a port number other than the default of 80, include the port number in the URL:
http://machine_name:port_number/CustomerCenter_en.html
For example, if Customer Center is on a system called server1 using port 81, go to this URL: http://server1:81/CustomerCenter_en.html.
The browser begins downloading the Java Web Start installation file, javawebstart-install.exe.
Note:
If your Web server uses default port 80, specifying the port number is optional. Otherwise, you must include the port number.
If your Web server does not display the page correctly or does not start downloading the Java Web Start installation file, make sure you set the JNLP MIME type in your Web server. See "Installing the Customer Center Files".
If the MIME type is set in your Web server, try clearing the cache in your Web browser. For Internet Explorer, delete temporary Internet files. For Netscape, clear the memory cache and the disk cache.
Choose the directory to save the installation file, then save the file.
Go to the temporary directory where you saved the Java Web Start installation file.
Double-click javawebstart-install.exe and follow the prompts in the installer.
Note:
If you do not have JRE 1.6.0.26 installed, Java Web Start installs it.
If you are using a Netscape browser, Java Web Start prompts you to restart your browser at the end of the installation.
Java Web Start might prompt you to restart your system.
(For Netscape 6 only) In Netscape, choose Edit - Preferences - Navigator - Helper Applications and create a new MIME type using the values in Table 10-2:
Stop and restart Netscape.
In your Web browser, return to the Customer Center URL (http://machine_name:port_number/CustomerCenter_en.html) and click the link for running Customer Center.
Java Web Start launches and copies the Customer Center files from the Web server.
In the Security dialog box that asks whether you want to install and run Customer Center, click Start.
For more information on using Java Web Start, see the Java Web Start documentation at java.sun.com.
After installing Java Web Start and running Customer Center for the first time, you can start Customer Center in any of these ways:
Java Web Start.
Browser.
Using any of these methods, if there's a newer version of the Customer Center files on the Web server, Java Web Start installs them on your system.
To start Customer 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.
To start Customer Center from your browser, go to the URL http://machine_name:port_number/CustomerCenter_en.html.
This URL automatically starts Java Web Start, which in turn starts Customer Center.
To remove a version of Customer Center that has been downloaded to a client system:
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.
Choose Application - Remove Application.
For more information about the GSM Manager components, see "About the GSM Manager Components" in BRM Telco Integration.
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.
Important:
You must install the GSM Manager Customer Center Extension on a system that already has Customer Center installed. See "Installing Customer Center on Windows".To install GSM Manager Customer Center Extension:
Download the software to a temporary directory (temp_dir).
Extract the downloaded .zip file to a temporary directory (temp_dir).
Go to temp_dir and run the setup.exe program. The installation wizard for GSM Manager Customer Center Extension starts.
Answer the prompts in the installation wizard screens.
Your GSM Manager Customer Center Extension installation is now complete.
To install Pricing Center, see the following sections:
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.
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.
Note:
When you install Pricing Center, you also automatically install the Resource Editor and the Zone Mapper.Obtain the following information about the machine running the CM to which Pricing Center will connect:
Computer or server name
Port number
Database number
Make sure you have Windows administrator privileges.
Install a third-party Web server.
Make sure each Pricing Center client system has a Web browser.
For a list of supported browsers, see "BRM Software Compatibility".
Optionally, you can install JRE 1.6.0_26 on each client system. If you do not do it in advance, JRE 1.6.0_26 will be installed as part of downloading Pricing Center.
See "Installing Java Web Start and Downloading Pricing Center".
Important:
Install Pricing Center on the same system as your Web server.Follow the steps for "Downloading the Compressed Files".
Go to the temporary directory where you unzipped the client application download file.
Double-click Setup.exe.
When the Welcome screen appears, click Next.
The Choose Destination Location window opens.
Click Next to choose the default directory, or use the Browse button to choose a different directory and then click Next.
The Install Type window opens.
On the Install Type window, choose one of the following:
Standalone install
If you will use Pricing Center as a standalone application on a single system, select Standalone install and click Next.
The Install Sample Price Plans window opens.
Sample price plans are selected by default. To install them, click Next. To skip installing sample price plans, clear the check box, then click Next.
The Enable Pipeline Rating Feature window opens. Skip to the next step.
Web server install
If you are installing Pricing Center on a central server, select Web server install and click Next.
The Enter the Web Server Name window opens.
Specify the URL as follows:
If you are installing in your Web server's document root directory or in a directory mapped to your Web server's document root directory: Use the default URL.
If you are installing in a subdirectory of your Web server's document root: Add the subdirectory names to the default URL. But do not change the top-level URL.
If you are installing in a directory outside your Web server directory: Map that installation directory to a subdirectory of your document root. Then add the name of the subdirectory of the document root to the default URL.
Enter the URL where you want Pricing Center installed and click Next.
The Enable Pipeline Rating Feature window opens.
The Enable pipeline rating feature check box is selected by default.
If you rate events using Pipeline Manager, accept the default selection and click Next.
If you do not rate events using Pipeline Manager, clear this option and click Next.
The Enable Data Migration Functionality window opens.
You use the Pipeline Manager data migration feature to move pipeline pricing data from a development system to a production system. For more information on data migration, see Pricing Center Help.
Choose how you want data migration to be handled using the values in Table 10-3:
Table 10-3 Data Migration Configuration Values
| Value | Description |
|---|---|
|
Turn OFF Data Migration |
Turns off the data migration feature. This is the default. |
|
Import Only |
Gives you the ability to import change set files without enabling the full set of data migration features. This option is useful for production systems where you want to reduce the risk of accidental data changes. |
|
Turn ON Data Migration |
Turns on the full set of data migration features so you can manage, import, and export pipeline pricing data. |
Click Next.
The Select Program Folder window opens.
Specify the folder where you want Pricing Center to add program icons and click Next.
The Start Copying Files window opens.
Click Next.
The Pricing Center files are copied to the directory you specified.
When the files have been copied, the Setup Complete window appears.
Click Finish to complete the setup process.
Important:
If you installed Pricing Center as a standalone product, skip this section and go to "Granting Administrative Privileges to Pricing Center Users".If you installed the Web Server version of Pricing Center, follow the instructions in this section.
The first time you start Pricing Center on a client system, you download and install Java Web Start.
Go to this URL in your Web browser:
http://machine_name/PricingCenter_en.html
Replace machine_name with the name of the system running the Web browser and Pricing Center. If Pricing Center is located in a subdirectory of your Web browser's document root directory, include the full path to PricingCenter_en.html.
If your Web server uses a port number other than the default of 80, include the port number in the URL:
http://machine_name:port_number/PricingCenter_en.html
For example, if Pricing Center is on a system called server1 using port 81, go to this URL: http://server1:81/PricingCenter_en.html.
The browser begins downloading the Java Web Start installation file, javawebstart-install.exe. On Internet Explorer, you have the option of installing directly from the server without downloading the file.
Note:
If your Web server uses default port 80, specifying the port number is optional. Otherwise, you must include the port number.
If your Web server does not display the page correctly or does not start downloading the Java Web Start installation file, make sure you set the JNLP MIME type in your Web server.
If the MIME type is set in your Web server, try clearing the cache in your Web browser. For Internet Explorer, delete temporary Internet files. For Netscape, clear the memory cache and the disk cache.
Specify the directory where you want the installation file saved, then save the file.
Go to the temporary directory where you saved the Java Web Start installation file.
Double-click javawebstart-install.exe and follow the prompts in the installer.
Note:
If you do not have JRE 1.6.0_26 installed, Java Web Start installs it.
If you are using a Netscape browser, Java Web Start prompts you to restart your browser at the end of the installation.
Java Web Start might prompt you to restart your system.
(For Netscape 6 only) In Netscape, choose Edit - Preferences - Navigator - Helper Applications and create a new MIME type as described in Table 10-4.
Stop and restart Netscape.
In your Web browser, return to the Pricing Center URL (http://machine_name:port_number/PricingCenter_en.html) and click the link for running Pricing Center.
Java Web Start launches and copies the Pricing Center files from the Web server.
In the Security dialog box that asks whether you want to install and run Pricing Center, click Start.
For more information on using Java Web Start, see the Java Web Start documentation at java.sun.com.
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:
Setting Up the Database Server for the Pipeline Manager Administrator
Specifying Administrative Privileges for Pipeline Manager Users
Go to the DM directory:
cd BRM_Home/sys/dm_oracle
Back up the database configuration file (pin.conf).
Important:
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 md5| BRM_Home/lib/libpin_crypt4dm.so "secret_key"
For more information, see "About Encrypting Information" 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.
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
Specify values for the entries described in Table 10-5. 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 10-5 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. |
Example 10-1 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.
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 Step 6 of "Modifying the pricing_admin.pl Script Configuration File".
Note:
The DB 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
If your system uses branding and you use pipeline pricing components:
Open the pricing_admin.sce scenario file located in BRM_Home\setup\scripts.
Change the PIN_FLD_READ_ACCESS value from Self to Global:
PIN_FLD_READ_ACCESS STR [0] "Global"
Save and close the file.
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.
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 valhalla mary_allen dorado
Important:
BRM user names (login names) are case sensitive, but Pipeline Manager user names are not. Therefore, be sure to 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 the 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.
This section describes how to remove single and multiple users from the Pipeline Manager database.
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
After installing the standalone version of Pricing Center, you can start it from the Windows start options.
See "Starting Standalone Pricing Center".
After installing Java Web Start and running Pricing Center for the first time, you can start Pricing Center in the following ways:
Java Web Start.
Browser.
Use any of these methods to start the Web version. If a newer version of the Pricing Center files is available on the Web server, Java Web Start installs them on your system.
To start standalone Pricing Center, see "Starting Standalone Pricing Center".
To start the standalone version of Pricing Center:
From the start options, choose Pricing Center, which is under Portal.
Enter the root account password in the Login Application Center window.
To start Pricing Center from the Java Web Start Application Manager:
Important:
To start Pricing Center from Java Web Start, ensure that your Web browser is using the latest version of JRE 1.6 before starting Pricing Center from Java Web Start. You cannot start Pricing Center from Java Web Start in a Web browser using a version of JRE later than JRE 1.6.Start Java Web Start from the start options.
If you do not see Pricing Center listed in the Application Manager, choose View - Downloaded Applications.
Select Pricing Center and click Start.
To start Pricing Center from your browser, go to the URL http://machine_name:port_number/PricingCenter_en.html.
This URL automatically starts Java Web Start, which in turn starts Pricing Center.
To remove a version of Pricing Center that has been downloaded to a client system:
Start Java Web Start from the start options.
If you do not see Pricing Center listed in the Application Manager, choose View - Downloaded Applications.
Select Pricing Center.
Choose Application - Remove Application.
To remove a standalone version of Pricing Center from Windows:
From the Windows uninstall feature, select Pricing Center 7.5.
Click Change/Remove.
Click OK.
This section describes the requirements and the procedure for installing Customer Center SDK on Windows.
Customer Center SDK package includes components that are used to customize both Customer Center and Self-Care Manager. Follow these instructions for installing the common SDK package.
To customize Customer Center, see "Customizing the Customer Center Interface" in BRM Developer's Guide.
To customize Self-Care Manager, see "Customizing the Self-Care Manager Interface" in BRM Developer's Guide.
Important:
Before installing Customer Center SDK, verify that JDK 1.6.0_26 is installed in your development environment. You must also have access to a BRM server.For information about Customer Center SDK, see "Using Customer Center SDK" in BRM Developer's Guide.
Customer Center SDK is available for the Windows operating system.
You must have the following software installed on or available to your system before you install Customer Center SDK:
BRM.
A Web server such as Apache HTTP Server, IPlanet Web Server, or Microsoft Internet Information Server (IIS) with the Customer Center client software installed.
To install Customer Center, see "Installing Customer Center on Windows".
An application such as WinZip for extracting compressed files.
The JDK supported for this release.
(Customer Center only) A Java Code Signing Certificate. Customer Center SDK includes a makecertificate utility for creating a self-signed certificate that you use to create jar files to deploy your customizations.
(Optional) Borland JBuilder 5 or later, Professional or Enterprise Edition. You can use JBuilder for various tasks such as creating WAR files for Self-Care Manager and custom pages for Customer Center.
Before installing Customer Center SDK, have the following information available:
The destination folder for your Customer Center SDK installation.
The name of the server where the CM is running.
The port number where the CM is running.
The database number for the Oracle DM.
The URL for the Web server from which Customer Center is deployed. This is the directory where Customer Center is installed. For example, http://server1.
To install Customer Center SDK, verify that you have Administrator privileges, and then follow these steps:
Download the Customer Center SDK software.
Unzip the compressed Customer Center SDK files you downloaded.
Click Setup.exe to start the installation.
The installation program extracts files to a temporary directory on your computer.
Follow the instructions on the screen, providing the following information when prompted, or click Next to accept the default entries:
Destination folder for the installed software.
For Windows XP:
C:\Program Files\Portal Software\CustomerCenterSDK
For Windows 7 and 8.1:
C:\Program Files (x86)\Portal Software\CustomerCenterSDK
CM's server name, port, and database number.
Customer Center Web Start deployment URL, if available. Use the URL where you will deploy your customizations.
Program folder for the start options.
When the Setup Complete dialog box appears, click Finish to complete the installation.
Note:
You can delete the temporary extraction directory created by the installation program if it is not automatically deleted when you exit your unzip application.If you installed GSM Customer Center Extension on a Customer Center installation, copy the following files from the Customer Center library directory (CC_path\lib) to the library directory of the version of Customer Center included in Customer Center SDK (CCSDK_path\lib):
GSMManager.jar
GSMManager_en.jar
Modular.properties
where:
CC_path is the path to your Customer Center installation path.
CCSDK_path is the CC SDK installation path.
GSM Customer Center Extension enables additional features, such as support for associating SIM and number devices with GSM services. See the information about working with GSM accounts in Customer Center Help.
To extract the SDK files, you need a zip file utility, such as WinZip.
If you have installed an earlier version of the SDK, uninstall it.
Extract the files in the zip file to a temporary directory.
Install the files.
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:
For Windows XP:
subst W: "C:\Program Files\Portal Software\Localization SDK"
For Windows 7 and 8.1:
subst W: "C:\Program Files(x86)\Portal Software\Localization SDK"
To prepare the MFC files, verify that the Visual C++ files are in the path:
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\vcvars32.bat
The MFC files are ready to be translated. After translation, see "Building Payment Tool" in BRM Developer's Guide.
To use Self-Care Manager, you must install a third-party Web server, an application server, and Self-Care Manager itself. Perform the following procedures:
Installing the Self-Care Manager Files
Important:
You must install your application server and Self-Care Manager on the same system. The CM can be on the same system as Self-Care Manager or on a different system.Supported application servers include WebLogic and WebSphere. For more information, see the vendor installation instructions for the application server you are using.
Before installing Self-Care Manager, make sure your application server servlet engine is installed. See "Installing an Application Server".
To install the Self-Care Manager files:
Follow the steps for "Downloading the Compressed Files".
See "Installing the Software" for information about the dialog boxes that appear when you install Self-Care Manager.
Note:
When you configure your application server, it extracts the Self-Care Manager files to a location within your application server installation. The default location is C:\Program Files\application_server\servers\default\WebKit.Configure your application server to work with Self-Care Manager. For details, see "Configuring the Application Server" in BRM Managing Customers.
This section describes problems you might encounter when installing BRM client applications and their solutions.
You cannot start one of the client applications, even though the installation appeared to be successful.