31 Setting Up Customer Self Care with Self-Care Manager

Learn how to set up Oracle Communications Billing and Revenue Management (BRM) Self-Care Manager to display Web pages that your customers can use to access their accounts. It includes a procedure for configuring the application server.

Topics in this document:

• About Self-Care Manager

• Configuring the Application Server

• Deploying Self-Care Manager

• Supporting Localized Versions of Self-Care Manager

• Using Self-Care Manager

• Troubleshooting Self-Care Manager

• Using the Default HTML Web Pages

• Changing Web pages

• Files Used by Self-Care Manager

To add or change Self-Care Manager functionality, see "Customizing the Self-Care Manager Interface" in BRM Developer's Guide.

About Self-Care Manager

Self-Care Manager includes the following components:

• A set of Java Server Pages (JSPs) that display HTML forms in a standard Web browser. The JSPs can display data, such as a list of available packages, from the BRM database.

  You can customize the JSPs to change the appearance of the Web pages or to change the data that you receive from or display to customers. For more information about JSPs, see Sun Microsystems' Java documentation.

• A set of BRM Business Application SDK (BAS) beans that provides an interface between the JSPs and BRM. The BAS beans connect to a Connection Manager (CM) and transfer data to and from BRM.

  A programmer can create custom controllers and other Java components to customize the data that you display or receive from customers. For more information, see "Customizing the Self-Care Manager Interface" in BRM Developer's Guide.

• An application server that processes requests originating from customer Web browsers, manages customer sessions, and transfers data to and from the BAS beans. For more information, see the JavaSoft documentation.

The JSPs and the application server are run by your Web server.

Supported Application Servers

Self-Care Manager supports the Tomcat and WebLogic application servers. Figure 31-1 shows the flow of information.

Figure 31-1 Self-Care Manager System Architecture

Description of "Figure 31-1 Self-Care Manager System Architecture"

For installation instructions, see "Installing Self-Care Manager" in BRM Installation Guide.

About Customizing Self-Care Manager

Self-Care Manager can be customized as follows:

• You can change the appearance of Self-Care Manager pages by editing the HTML files, JSPs, and style sheet. This requires HTML knowledge. See "Changing Web pages" for more information.

• You can modify or add source code to collect additional information from your customers or to provide your customers with additional options. This requires the Customer Center SDK as well as Java programming knowledge.

About Currencies

All accounts created in Self-Care Manager use the default account currency for your BRM system. Your customers do not have the option of selecting a currency when they create an account through Self-Care Manager.

You can change the default currency Self-Care Manager uses by changing the default account currency. See "Setting the Default Account Currency".

If you want customers to have the option of selecting a currency, a programmer can customize Self-Care Manager to add a currency field. See "Customizing the Self-Care Manager Interface" in BRM Developer's Guide.

Configuring the Application Server

You can deploy your Self-Care Manager application with these application servers:

• Apache Tomcat. See "Setting up Apache Tomcat".

• WebLogic. See "Setting Up Oracle WebLogic".

Setting up Apache Tomcat

This section explains how to deploy your Self-Care Manager application with Apache Tomcat.

Note:

Self-Care Manager is not compatible with Tomcat in a clustered environment. Self-Care Manager should not have the <distributable /> element set in the web.xml file.

Requirements

• Your Self-Care Manager WAR file. See "Customizing the Self-Care Manager Interface" in BRM Developer's Guide.

• The directory in which Self-Care Manager is installed. The default is BRM_home/WebKit/WebKit, where BRM_home is the directory in which the BRM server software is installed.

Deploying Your Application with Apache Tomcat

To deploy your Self-Care Manager application with Apache Tomcat:

1. Install Apache Tomcat. For information, see the Apache Tomcat documentation.

2. Deploy your WAR file as a new Web component by using the Apache Tomcat interface.

3. Copy the WebKit.properties and Infranet.properties files from BRM_home/WebKit/WebKit to Tomcat_home\lib.

4. Stop and restart the Tomcat server.

   Your Self-Care Manager application is now deployed.

Setting Up Oracle WebLogic

This section explains how to deploy your Self-Care Manager application with Oracle WebLogic.

Requirements

• Creating a new WebLogic domain.

• Your Self-Care Manager WAR file. See "Customizing the Self-Care Manager Interface" in BRM Developer's Guide.

• The default directory in which Self-Care Manager is installed. The default is C:\Program Files\Portal Software\Self Care Manager.

Deploying Your Application with Oracle WebLogic

To deploy your Self-Care Manager application with WebLogic:

1. Install WebLogic. For information, see the WebLogic documentation.

2. Create WebLogic domain. For information, see the WebLogic documentation.

3. Copy the WebKit.properties and Infranet.properties files from C:\Program Files\Portal Software\Self Care Manager to WebLogic_home\mydomain\applications\webkit_en\WEB-INF\classes.

4. Start the WebLogic server.

5. Deploy your WAR file as a new Web component by using the WebLogic interface. For information, see the WebLogic documentation.

6. Stop and restart the WebLogic server.

   Your Self-Care Manager application is now deployed.

Deploying Self-Care Manager

Your Self-Care Manager installation includes the user interface files (JSPs, HTML files, and GIFs) for the standard browser version of Self-Care Manager. The files are in the htmlui_en directory.

Note:

This is the directory name for the English locale. Directory names for localized versions use the appropriate locale in place of en.

One approach to deploying Self-Care Manager so your subscribers can access it:

• Configure your Web server to look for index.html as the default HTML home page.

• Have subscribers enter http://hostname/WebKit/htmlui_en in the Web browser.

  Note:

  If your Web server does not support specifying a default home page for each application, subscribers will need to enter the full URL, including the file name for the home page. For example, http://hostname/WebKit/htmlui_en/index.html.

Supporting Localized Versions of Self-Care Manager

If you have customers in different countries, you can set up localized versions of the Self-Care Manager pages. You obtain localized versions of Self-Care Manager from BRM or use the Localization SDK to create localized versions. In both cases, you install a Self-Care Manager WAR file just as you do for English.

You can deploy multiple localized versions of Self-Care Manager in one of these ways:

• Set up a separate application server for each locale. You set up multiple application servers with a single Web server. For information, see your application server documentation.

  You can then follow the standard procedure for configuring your application server for each combination of server and locale. For each server, deploy the WAR file for a different locale.

• Set up a separate Web application in your application server for each locale.

  Note:

  If you use this method, you will encounter problems later if you try to use opcode and flist logging for troubleshooting.

For information on creating localized versions of Self-Care Manager, see "Localizing Self-Care Manager" in BRM Developer's Guide.

Using Self-Care Manager

This section describes how to set up Self-Care Manager for use.

Setting Connection Parameters

Self-Care Manager uses information in the WebKit.properties file to establish a connection to BRM. This properties file includes the standard BRM connection parameters, such as database number and login type.

Note:

BRM connection parameters are also in the Infranet.properties file.

To set connection parameters:

1. Open the Self-Care Manager properties file (SelfCareManager_install_dir/WebKit.properties).

2. Edit these entries:

   user=root.0.0.0.1 
   password=password 
   host=hostname 
   port=11960 

3. Save and close the file.

4. Open the Infranet.properties file (SelfCareManager_install_dir/Infranet.properties).

5. Edit the infranet.connection entry; for example:

   infranet.connection=pcp://root.0.0.0.1:password@host:40010/service/pcm_client 1

   In this example:

   • The login name is root.0.0.0.1.

   • The hostname is host.

   • The port is 40010.

6. Save and close the file.

   Note:

   To improve security, change the default root login name (root.0.0.0.1). See "Managing Login Names and Passwords for BRM Access" in BRM System Administrator's Guide.

Specifying which Package List to Display

By default, Self-Care Manager displays packages included in the webclient package list. If the webclient package list does not exist, Self-Care Manager displays packages included in the default-new package list.

To specify a package list for Self-Care Manager:

1. Open the Self-Care Manager properties file (SelfCareManager_install_dir/WebKit.properties).

2. Enter the name of the package list in the Infranet.PricingPlan entry; for example:

   pricingplan=webclient 
   

3. Save the file.

Setting the Timeout

You can specify the length of time before a timeout when there is no customer activity.

You change the timeout setting in your application server.

Enabling a Single Login for Multiple Services

By default, Self-Care Manager requires your customers to enter a separate login and password for each service when they purchase bundles with more than one service.

You can set up Self-Care Manager to require only a single login and password that applies to all services. To do this, edit the Self-Care Manager properties file as follows:

1. Open the Self-Care Manager properties file (SelfCareManager_install_dir/WebKit.properties).

2. Change the singleLogin entry to:

   singleLogin=true 
   

3. Save and close the file.

Optimizing Self-Care Manager Connection Pool Performance

Self-Care Manager uses connection pooling. When a BRM connection is required for an opcode call, the connection is made for a brief period of time, instead of for the entire duration of a user session, and is then released back to the connection pool. This enables each BRM connection to handle multiple customer connections.

To optimize Self-Care Manager performance, you can change the following connection pooling parameters in the Self-Care Manager properties file (SelfCareManager_install_dir/WebKit.properties):

• infranet.bas.connectionpool.size: The maximum number of connections in the connection pool. More connections can improve performance but put a heavier load on the BRM server. Any value greater than 0 is valid. The default is 4.

  infranet.bas.connectionpool.size = 4
  

• infranet.bas.connectionpool.timeout: The maximum time in milliseconds that customers wait for a BRM connection before getting notified that a connection is not available. If customers do not get a connection within this time, they get an “error communicating with BRM" message.

  You must add this parameter to the Self-Care Manager properties file (WebKit.properties) using a value appropriate for your installation. Any value greater than 0 is valid.

  infranet.bas.connectionpool.timeout = connection_timeout_in_milliseconds
  

  The default is 30000 (30 seconds).

Adding a Service to the Self-Care Manager Home Page

The Self-Care Manager home page includes a list of services available to your customers. If you add an optional manager to your BRM system, and that optional manager uses Self-Care Manager, you need to add those service types to the list in the home page.

Note:

If you have multiple Self-Care Manager home pages, you need to add those service types to each home page.

To add a service:

1. Open the Self-Care Manager home page with an HTML editor or text editor. The default Self-Care Manager home page is index.html.

2. Locate this section of the file:

   <SELECT Name="service" Size="1">
        <OPTION Value="ip" SELECTED>ip
        <OPTION Value="email">email
        <OPTION Value="telephony">telephony
    </SELECT>
   

3. For each service you want to appear on the list, add a new option to this list. For Value, enter the BRM name of the service. The name outside the OPTION tag is the name displayed on the Web page.

   For example:

   <OPTION Value="gsm/sms">GSM SMS
   <OPTION Value="gsm/telephony">GSM Telephony
   <OPTION Value="gsm/data">GSM Data
   

4. Save and close the file.

Troubleshooting Self-Care Manager

This section contains troubleshooting information about these Self-Care Manager issues:

• The error logs show an “error communicating with Portal" message

• The Web pages display errors

The error logs show an “error communicating with Portal" message

To debug this type of error, you turn on opcode and flist logging for the Java PCM. This logs the input and output flists for each opcode that Self-Care Manager calls. You can use these flists to see problems communicating with BRM.

To turn on opcode and flist logging:

1. Open the Infranet.properties file in a text editor. The file is located in your Self-Care Manager installation directory.

2. Add these lines to the file:

   infranet.log.opcodes.enabled=true 
   infranet.log.opcodes.file=pathname/opcodes.log 
   

   where pathname is the path to the directory for the log file. For example:

   infranet.log.opcodes.file=d:/temp/opcodes.log
   

   Note:

   You must use forward slashes in the directory paths.

3. Stop and restart the application server.

4. Save and close the file.

5. Reproduce the error and check the file applicationserver_install_dir/servers/default/javaPCM.log.

The Web pages display errors

The Web pages might display an error message or display “Click to continue" in place of the correct page. To debug this type of problem, you enable debugging in the error.jsp file so that exceptions are written to the log file debug_errorlog.jsp. This prints a stack trace, which can help developers locate where an exception occurred.

To enable debugging in the error.jsp file:

1. Open the appropriate version of the error.jsp, located in the htmlui_en directory in the Self-Care Manager installation directory.

2. Uncomment this line by removing <% and %>:

   <%@ include file = "debug_errorlog.jsp" %>
   

3. Save and close the file.

Using the Default HTML Web Pages

Self-Care Manager supplies a set of JSPs that you can use as part of your customer self-care website. These JSPs serve HTML pages.

This section describes Self-Care Manager's default HTML pages and provides an overview of the functionality they offer.

For information on customizing these pages, see "Changing Web pages" and "Customizing the Self-Care Manager Interface" in BRM Developer's Guide.

Logging In

Figure 31-2 shows the login page your customers see when they access your self-care website.

Figure 31-2 Login Page for Self-Care Website

Description of "Figure 31-2 Login Page for Self-Care Website"

Self-Care Manager supports email, IP, and telephony service types.

Accessing Account Information

After customers log in to your website on the login page, the Account Information page appears. This page displays the details of the account bill unit (/billinfo object) and balance groups associated with the bill unit, and the current balance of all the balance groups.

To view the details of the other bill units in the account, customers click the Other Bill Units Information link on the Account Information page and select the bill unit. The details will be displayed in the Account Information page. For information, see "Accessing Account Information".

From this page, customers can perform the following tasks:

• Finding or Searching for and Viewing Events

• Applying Voucher Top-Ups

• Viewing Resource Reservation Details

• Viewing Invoices

• Viewing Account Activity

• Viewing Products or Offers Purchased

• Paying Bills Online

• Viewing Service Details for a Bill Unit

• Viewing Bill Units in an Account

• Changing Login Name, Password, or Account Status

Finding or Searching for and Viewing Events

Customers can specify the search criteria and view the events of the selected bill unit. To enable this feature, you must configure the item types in the WebKit.properties file.

To specify the search criteria, customers click the Event Search link on the Account Information page. The Event Search page appears. Customers then specify the search criteria and click Search.

To view the events of other bill units in the account, see "Viewing Bill Units in an Account".

Based on the search criteria and the item types configured in WebKit.properties, events are retrieved and displayed in the Event Search page.

For example:

• To view all the events related to cycle_forward, add /cycle_forward to the key EventSearch.ItemTypes in WebKit.properties:

  EventSearch.ItemTypes=/cycle_forward
  

• To view all the events related to adjustment and payment, add /adjustment and /payment to the key EventSearch.ItemTypes in WebKit.properties:

  EventSearch.ItemTypes=/adjustment,/payment
  

Applying Voucher Top-Ups

Customers use vouchers to top-up their currency and noncurrency account balances. They can top-up one currency balance and an unlimited number of noncurrency balances. For more information, see "About Standard Top-Ups" in BRM Configuring and Collecting Payments.

To top-up their account with a voucher, customers click the Voucher Top-Up link on the Account Information page. The Voucher Top-Up page appears. Customers can then enter the voucher ID and pin and click Validate to check the balances and validity of the specified voucher. If the voucher is valid, the Apply button is enabled.

If there are multiple balances in the bill unit, customers can select the balance groups whose account balance they want to top up.

To apply the vouchers immediately and top-up the account balances, customers select the required balance groups, select Allocate Now, and click Apply.

Customers can also choose just to apply the voucher to the balance groups and not top up the account balance. To do this, the customer clicks Apply without selecting Allocate Now. The voucher can later be allocated but only through Customer Center.

Viewing Resource Reservation Details

Customers can view the resource reservation details of a bill unit. To do this, customers click the Resource Reservation link on the Account Information page. It displays available credit limit, total bill amount, amount reserved, and available balance of all the balance groups in a bill unit.

To view the reservation details, customers click the Reservations link and the details are displayed in the Resource Reservations Details page.

If the credit limit of any of the balance groups is unlimited, the Credit Limit value is displayed as Unlimited.

To find the balance group, which has unlimited credit balance customers, click the Unlimited link displayed next to the Credit Limit. The Included Services page appears. See "Viewing Service Details for a Bill Unit".

Viewing Invoices

Customers can view their invoice details by generating a report of their past bills. To view the invoice details, customers click the Invoice link on the Account Information page. The Invoice Selection page.

Customers can then select new start and end dates for the report or keep the default dates that represent the last billing cycle. After clicking Submit, the Invoice page appears, which lists invoices available for the selected period. In this page, customers click the invoice they want to view.

Viewing Account Activity

To view their account details, customers can generate a report. To generate a report, customers click the Account Activity link on the Account Information page.

Customers can then select new start and end dates for the report or keep the default dates which represent the last billing cycle.

After clicking Submit, the Account Activity page appears which shows the account's details; for example, customer's name, address, and event details in chronological order.

If the customer uses additional services, some types of usage activity appear on separate pages. Links for the additional pages appear on the line just above the list of events.

Viewing Products or Offers Purchased

To view the products or offers purchased, customers click the Products link on the Account Information page. The Product Information page.

If a discount was purchased as part of a bundle, an icon appears before the bundle name.

Paying Bills Online

To pay bills online, customers click the Online Payment link on the Account Information page.

To pay the bill, customers enter an amount and credit card information and click Submit.

BRM updates the customer's balance the next time you run billing and collects the BRM-initiated payment.

For more information, see "About BRM-Initiated Payment Processing" in BRM Concepts.

To view online bill payment records, customers click the Online Payment Audit link on the Online Payment page. A page appears on which they enter start and end dates. Self-Care Manager displays the payments made between the start and end dates.

Viewing Service Details for a Bill Unit

To view the list of services and the details associated with all the balance groups in a bill unit, customers click the Included Services link on the Account Information page. The Service Details page appears and displays the details of the services.

Viewing Bill Units in an Account

To view all the bill units in an account, customers click the Other Bill Units Information link on the Account Information page. The Service Level Bill Unit Information page appears and displays all the bill units.

To view the details of a specific bill unit, click on the bill unit. The details are displayed in the Account Information page. For information, see "Accessing Account Information".

Changing Login Name, Password, or Account Status

Customers can change their login name, password, or account status by clicking the appropriate link on the Account Information page.

If customers click Change a Login or Change Status, the Change Service Login page appears.

The account status can be active, inactive, or closed.

Changing Web pages

This section describes editing Self-Care Manager files to change the appearance of the pages and to make other modifications. You can make these types of changes if you are familiar with HTML tags and JSP tags. For information on making more extensive customizations to Self-Care Manager, see "Customizing the Self-Care Manager Interface" in BRM Developer's Guide.

Editing Self-Care Manager Files

To change the appearance of Web pages, edit the following user interface files, located by default in the htmlui_en directory:

• JSPs: The files containing the text and forms that provide the user interface on the pages. JSPs are HTML pages with added JSP tags. You can use any text editor and some HTML editors to edit the JSPs.

  For information on modifying these pages, see "Editing JSPs".

• HTML pages: The HTML account creation page and files with common HTML code used by the JSPs. For example, the header.html file includes the HTML HEAD tag. You can use a text editor or HTML editor to edit these files.

• Cascading style sheet (CSS): The file that defines the appearance of the HTML pages. Edit this file to make global formatting changes, including fonts, text alignment, and margins. You can use a text editor or a CSS editor to edit this file.

• GIF files: The graphics displayed in the HTML pages. You can edit the files with a graphics program or replace them with your own graphics.

  Note:

  Before editing, make a copy of the default pages, including all HTML pages and JSPs, and edit and test the copies.

When you edit a Self-Care Manager file, you should edit the version located in the Self-Care Manager WAR file. This ensures that the customized files are used if you reconfigure your servlet engine for Self-Care Manager in the future. See "Modifying the Self-Care Manager WAR File".

You can also use the Customer Center SDK to modify Self-Care Manager files from the WAR file. See BRM Developer's Guide.

Editing JSPs

JSPs use standard HTML formatting. In addition, the JSPs use special code to display information, or to display a text entry field for customer input. Each JSP tag starts with <% and ends with %>.

You can move data input and display codes from one location on the page to another. You can also delete them. For example, if you do not offer the IP telephony service, you can delete all code that displays IP telephony information.

Note:

• When editing JSPs, be careful to maintain the syntax when moving or deleting code. For example, a missing %> from a JSP tag will cause problems.

• When removing code, do not remove input entry points for information that is required for account creation. See "Customizing the Self-Care Manager Interface" in BRM Developer's Guide.

• Do not copy data input and display codes from one page to another. Each code works only on the page that includes it.

For more information about editing JSPs, see Sun Microsystems' JSP documentation or other JSP reference documents. For more extensive JSP customization, see "Customizing the Self-Care Manager Interface" in BRM Developer's Guide.

Modifying the Self-Care Manager WAR File

When you edit Self-Care Manager files, you should edit the versions in the Self-Care Manager Web Application Archive (WAR) file. This file is created when you install Self-Care Manager, and it is the source for the Self-Care Manager files that the servlet engine copies when you configure it to run Self-Care Manager.

If you configured your servlet engine before modifying individual JSPs or other files, you also must copy your modified files to the servlet engine directory where Self-Care Manager files are located.

By modifying the files in the WAR file, you make sure that you do not overwrite your modified files if you reconfigure your servlet engine for Self-Care Manager in the future.

Following are instructions for modifying the Self-Care Manager WAR file. Alternatively, you can use the Customer Center SDK to create a customized WAR file. See BRM Developer's Guide.

To modify the Self-Care Manager WAR file, you need to install the Java Development Kit (JDK) on your system. The system running your application server already has the JDK. For information on supported versions, see "BRM Software Compatibility" in BRM Compatibility Matrix.

To modify the Self-Care Manager WAR file:

1. Copy the SelfCareManager_install_dir/WebKit/webkit_en.war file to a temporary directory.

2. Extract the files from the WAR file using the jar command, as follows:

   jar xvf webkit_en.war 
   

3. Delete or move the copy of webkit_en.war in the temporary directory.

4. Edit any files in the htmlui_en directory.

5. Create a new WAR file using the jar command from the temporary directory where you extracted the original files:

   jar cvf webkit_en.war . 
   

6. Copy this WAR file to SelfCareManager_install_dir/WebKit.

When you set up Self-Care Manager as an application in your servlet engine, it will include the files you modified.

If you have already set up Self-Care Manager in the servlet engine, copy the modified files to the correct location in the servlet engine's directory.

Files Used by Self-Care Manager

This section describes the various types of files used by Self-Care Manager.

JSPs Used by Self-Care Manager

Table 31-1 describes the JSPs used by Self-Care Manager:

Note:

These pages use the Business Application SDK (BAS) component collection (PIAComponentCollection) to hold BAS lightweight components (that is, PLightComponentHelper).

Table 31-1 Self-Care Manager JSPs

File name	Description
change_login_form.jsp	Enables customers to change the login name for a service.
change_passwd_form.jsp	Enables customers to change a password.
change_status_form.jsp	Enables customers to change account status.
constants.jsp	Defines strings for constants commonly used in other Self-Care Manager files.
debug_errorlog.jsp	Enables error logging for debugging.
error.jsp	Handles errors and displays error messages for all JSPs.
footer.jsp	Contains standard information displayed at the end of all JSPs.
invoice_selection.jsp	Enables customers to select the start time and end time used for generating the invoice.
load_session.jsp	Used by other JSPs to retrieve commonly used account data saved during the session, such as the name and address for the account.
login_verify.jsp	Verifies the login name and password and displays confirmation when a customer logs in.
logout.jsp	Displays confirmation that a customer logged out and ends the session.
online_payment.jsp	Enables customers to pay an outstanding bill online with a credit card.
online_payment_audit.jsp	Enables customers to search for records of online bill payments. The customer specifies a start date and end date.
purchase_plan_form.jsp	Enables customers to purchase additional packages.
selection.jsp	Enables customers to select the day, month, and year when specifying a time range for viewing account activity or invoices.
session_id.jsp	Saves the current user's session ID.
show_invoice.jsp	Displays a customer invoice.
usage_report.jsp	Displays details about customer activity, such as a list of IP telephony calls. HTML pages use UsageReportGeneral.jsp instead.
usage_selection.jsp	Enables customers to set the start and end dates for a usage report. For example, a customer can specify to see IP telephony calls for more than a single month.
UsageReportCommon.jsp	Included in the other usage report JSPs to do event search tasks that are common to all the usage report JSPs.
UsageReportContent.jsp	Displays details about a customer's content usage.
UsageReportGeneral.jsp	Displays details about general customer activity, including cycle forward fees, purchase fees, adjustments, and IP and email usage. Other usage report JSPs display activity for specific types of usage.
UsageReportGprs.jsp	Displays details about a customer's mobile data (GPRS) usage.
UsageReportGsm.jsp	Displays details about a customer's mobile voice (GSM) usage.
UsageReportSms.jsp	Displays details about a customer's mobile messaging (SMS) usage.
UsageReportView.jsp	Included in the other usage report JSPs to display the data from a usage report on the Web page.
view_balance.jsp	Displays the customer's account balance summary and has links to resource or balance reservation, event search, and voucher top-up pages.
view_invoice.jsp	Enables customers to specify which invoice to display.
view_product.jsp	Displays information about a customer's purchased products or charge offers.
AccountBalancePrepaid.jsp AccountBalancePrepaidView.jsp ReservationInfo.jsp ReservationInfoView.jsp	Display the resource or balance reservation details of a bill unit.
Event_details.jsp Event_search.jsp eventsearch_dateselection.jsp	Enable customers to view the events of the selected bill unit.
Voucher_details.jsp	Enables customers to top-up account balances by using a voucher.

HTML Pages Used by Self-Care Manager

Table 31-2 shows the HTML files used by Self-Care Manager:

Table 31-2 HTML Files Used by Self-Care Manager

File name	Description
footer.html	HTML code that you can use as a footer on every JSP page by including this file name in the JSP. For example: <jsp:include page="footer.html"/>
header.html	HTML code that you can use as a header on every JSP page by including the file name in the JSP.
index.html	The default account creation home page. Customers see this page first when they go to your website.

Other Files Used by Self-Care Manager

Self-Care Manager also uses these files:

• Style sheet: The HTML version of the JSPs use the style sheet infranet_general.css.

• GIF files: The HTML version of the JSPs use several GIF files. Most are stored in htmlui_en/graphics, others are stored in htmlui_en.