Demo Quick Start

Introduction

Installing in Demo Mode

Switching to Demo Mode at Run Time

Installation Instructions for Demo Mode

Browsers

Running the SESM Demo

Starting the Demo

Stopping the SESM Demo

Demo Data File

Demo Data Filename and Location

File Contents and Format

Logon Names and Passwords for a Demo

Special Demo Profile Attributes for Demonstrating LDAP Features

Demo Quick Start

This chapter describes procedures for installing and running the New World Service Provider (NWSP) application in Demo mode. The chapter includes the following topics:

Introduction

SESM Demo mode has two purposes:

It lets you demonstrate the capabilities of SESM when other required network components, such as SSG, are not available.
It is a valuable tool for developers of SESM web applications. Using Demo mode, developers can quickly test the customizations they make to an SESM application. See the Cisco Subscriber Edge Services Manager Web Developer Guide for information about using Demo mode during application development.

To prepare for using the Demo mode, you can either:

Install SESM in Demo mode
Install SESM in LDAP or RADIUS mode and switch to Demo mode at run time

The following sections describe the differences between these two approaches.

Installing in Demo Mode

The Demo mode installation is quick. It requires the entry of only a few parameters. In Demo mode, you can demonstrate the features of both RADIUS and LDAP deployments.

If you install in Demo mode, you should not expect to switch to LDAP or RADIUS modes at run time for the following reasons:

The MBean configuration files are not set up properly to support the switch to those other modes. Several manual changes are required in the files.
The Demo installation might not install all of the components required by the other modes. For example, a Demo installation does not install the SPE component, which is required to run in LDAP mode.

Switching to Demo Mode at Run Time

You can install and configure SESM to run in LDAP or RADIUS mode, and then easily switch to run the application in Demo mode at run time. The switch from the other modes to Demo mode is supported as follows:

When you install SESM in LDAP or RADIUS mode, the demo data file that supports Demo mode is included in your installation directory.
The MBean configuration files are set up to point to the demo data file when the application is run in Demo mode.
The mode attribute in the nwsp.xml file is a Java system property, so that it can be changed at run time.
The NWSP startup scripts accept a run time argument to change the mode.

To switch to Demo mode at run time, use the following command:

Platform	Command
Solaris and Linux	`jetty/bin/startNWSP.sh -mode Demo`
Windows NT	`jetty\bin\startNWSP.cmd Demo`

Installation Instructions for Demo Mode

To install SESM in Demo mode, follow these procedures:

Step 1 Log on as a privileged user:

On Solaris—Run the installation program as root.
On Windows NT—Run the installation program as a member of the Administrators group.

Make sure you have write privileges to the directory in which you intend to load the demo.

Step 2 Obtain the installation image from the product CD-ROM or from the Cisco web site. The installation image is a tar or zip file, depending on the platform on which you want to install the demo. See the "Obtaining the SESM Installation File and License Number" section for more information.

Step 3 Uncompress the tar or zip file to a temporary directory. The result includes an executable .bin or .exe file. Table 4-1 shows the names of the compressed and executable files.

Table 4-1: Installation Image Filenames

Platform	Compressed Filename	Executable Installation Filename
Solaris	sesm-3.1.3-pkg-sol.tar	sesm_sol.bin
Linux	sesm-3.1.3-pkg-linux.tar	sesm_linux.bin
Windows NT	sesm-3.1.3-pkg-win32.zip	sesm_win.exe

Step 4 Execute the installation image as follows:

On Solaris, change directories to the location of the installation image, and enter the image name. For example:

solaris>sesm_sol.bin

On Windows NT, you can double-click the file's icon. Otherwise, open a command prompt window, change directories to the location of the image, and enter the image name. For example:

C:\>sesm_win.exe

Step 5 Follow the instructions on the installation windows to install the demo. Table 4-2 describes the parameters that you use to install the demo.

Table 4-2: Demo Installation and Configuration Parameters

Component	Input Summary	Explanation
General installation parameters	License type	Click the Evaluation button. You do not need a license number.
	License agreement	Read the displayed license agreement to ensure that you agree with the terms of the license. You must accept the agreement to proceed with installation.
	Installation directory	You can accept the displayed default installation directory, click Browse to find a location, or type the directory name in the box. The default installation directories are: On Solaris and Linux: `/opt/cisco/sesm_3.1.3` On Windows NT: `C:\Program Files\cisco\sesm_3.1.3` You must have write privileges to the installation directory.
	Setup type	Click the Demo button. The difference between a demo installation and a typical installation is the values that the installation program inserts in the configuration files and the components that are installed. For example, a demo mode installation does not install the SPE component.
NWSP web application configuration	Web Application Port Number	Specify the port on which the container (the J2EE web server) for the SESM portal applications will listen for HTTP requests from subscribers. The installation program updates the application startup scripts for NWSP, WAP, and PDA to use this value. If you want to run these applications simultaneously, you must edit the start scripts to ensure that each application uses a different port. The displayed default value is port 8080. Tip Each web server running on the same machine must listen on its own unique port. If another web server or another instance of the SESM portal application is listening on 8080, change this value.

Browsers

You can use the following browsers to demonstrate the NWSP application:

Netscape Release 4.x and later

Internet Explorer Release 5.x and later

These browser limitations apply to the NWSP sample application and are mentioned to ensure predictable results during demonstrations. When you develop an SESM application for deployment, you should consider the end users of your deployed application, and design the application to accommodate the media that they commonly use.

Running the SESM Demo

This section includes the following topics:

Starting the Demo

To start the demo, follow these procedures:

Step 1 Start the NWSP web application in Demo mode.

Platform	SESM Installed Mode	Demo Startup Command
Solaris and Linux	Demo mode	`jetty/bin/startNWSP.sh`
Solaris and Linux	RADIUS or LDAP mode	`jetty/bin/startNWSP.sh -mode Demo`
Windows NT	Demo mode	`jetty\bin\startNWSP.cmd`
Windows NT	RADIUS or LDAP mode	jetty\bin\startNWSP.cmd Demo

Step 2 Open a web browser.

Step 3 Go to the NWSP URL, which is:

: http:// host:port

Where:

: host is the IP address or host name of the computer on which you installed the NWSP application. You can enter the value localhost, or the IP address 127.0.0.1, to indicate the local computer.
: port is the NWSP port number that you specified during the installation.

For example:

http://localhost:8080

The NWSP logon page appears.

Step 4 Log on using a user ID and password defined in the demo data file. Table 4-3 shows the user IDs and passwords in the installed demo data file.

Step 5 The NWSP home page appears. The service selection list shows subscribed services for the user ID you used on the logon page. Select a service to demonstrate service connection.

Stopping the SESM Demo

To stop the demo, follow the procedures described in the "Stopping Applications" section.

Demo Data File

This section describes the demo data file. It includes the following topics:

You might want to examine the demo data file to:

See the services and features associated with each demo user ID.
See examples of the vendor specific attributes (VSAs) that SESM and SSG require in a RADIUS database.
Add new profiles or change existing ones to enhance your demonstration

Demo Data Filename and Location

The subscriber and service profile data that supports the NWSP application running in Demo mode is stored in a RADIUS Merit flat file. The file is located in:

nwsp

config

demo.txt

If you change the name or location of the demo.txt file, you must reflect this change in the demoDataFile attribute in the SESMDemoMode MBean in the nwsp.xml file.

File Contents and Format

The demo.txt file contains example subscriber profiles, service profiles, and service group profiles that support the SESM sample applications in Demo mode. The file is in Merit RADIUS flat file format and includes profiles that use the following types of attributes:

RADIUS standard attributes
Cisco vendor-specific attributes described in "Configuring RADIUS"
SESM demonstration attributes described in the following section

You can use the profiles in the demo.txt file as test data for an SESM deployment in RADIUS mode.

Logon Names and Passwords for a Demo

Table 4-3 shows the user IDs and passwords in the profiles in the installed demo data file.

Table 4-3: Logon Names and Passwords for a Demo

Demo Purpose	User IDs	Passwords
To demonstrate RADIUS mode features	`radiususer` Note Other valid users are user1, user2, and so on, up to user44.	For all of the demo users, the password is: `cisco`
To demonstrate LDAP mode features	`golduser subgolduser` Note subgolduser is a subaccount to golduser.	For all of the demo users, the password is: `cisco`

Special Demo Profile Attributes for Demonstrating LDAP Features

Table 4-4 describes the subscriber profile attributes for demonstrating features that are available in LDAP mode but not in RADIUS mode. See "Configuring RADIUS" for a description of all other attributes in the demo data file. The attributes in Table 4-4 are for use in Demo mode only.

Note The attributes in Table 4-4 are recognized only by an SESM portal running in Demo mode. They are not valid VSAs and they should not be added to the RADIUS dictionary. These attributes are not recognized by SSG.

Table 4-4: Special Attributes for Demonstrating LDAP Features in Demo Mode

Attribute Description

Attribute	Description
Account-Info	Subattributes that can be specified in the demo data file to demonstrate LDAP mode features are: Epermission—Sets permissions to perform a task. The value for permission must be one of the following strings: Service Selection—The permission to perform service selection is implied and does not have to be explicitly coded in the profile. Self Manage—Use this string to demonstrate the LDAP mode feature that allows a subscriber to update their own X.500 user schema information, such as name, address, e-mail, and hobbies. Subaccount Manage—Use this string to demonstrate the LDAP mode feature that allows a subscriber to create a subaccount. The Demo mode does not create an actual subaccount; the supporting subaccount profile must be defined in the demo.txt file. Define the subaccount profile and use the F attribute. Service Subscription—Use this string to demonstrate the LDAP mode feature that allows a subscriber to subscribe to a new service and have immediate access to that service. If you use this string, you must also add a C or L attribute. Vname;type;value—Use this attribute to specify the initial values that will appear in the fields on the My Account page in the NWSP application running in Demo mode. The Demo allows you to change these values. Use a separate attribute line for each field. The format for each line consists of: name—Name of the field on the My Account page in the NWSP application. These are X.500 fields. You can add more fields to the demo if you alter the NWSP application to display more fields, as described in the Cisco Subscriber Edge Services Manager Web Developer Guide. See the Cisco Distributed Administrator Tool Guide for a list of the X.500 names. type—Identifies the format of value, as follows: S or s—Indicates that value is a string. V or v—Indicates that value is a vector of strings in the following format, including the parentheses: `{string1;string2;string3}` value—Indicates the value to be displayed in the field on the web page display. For example: `Account-Info = "Vhobbies;V;{science;news;travel}"` CserviceName—Use this attribute to demonstrate the LDAP mode self-subscription feature. This feature allows a subscriber to subscribe to a new service and have immediate access to that service. The serviceName value must match a service profile name defined elsewhere in the demo flat file (demo.txt). LgroupName—Use this attribute to demonstrate the LDAP mode self-subscription feature, subscribing to a predefined group of services. The groupName value must match a service group profile name defined elsewhere in thedemo.txt file. FparentAccountName—Use this attribute to indicate that this subscriber profile is a subaccount profile. The parentAccountName must match another subscriber profile name defined elsewhere in the demo flat file. (In the installed demo.txt file, subgolduser is defined as a subaccount to golduser.) RusergroupName—Use this attribute to indicate that this subscriber is a member of a user group. The PDA application running in Demo mode demonstrates brand awareness by displaying different branded pages based on the user group values of bronze, silver, and gold. See the pdademo.txt file.

Account-Info

Subattributes that can be specified in the demo data file to demonstrate LDAP mode features are:

Epermission—Sets permissions to perform a task. The value for permission must be one of the following strings:

Service Selection—The permission to perform service selection is implied and does not have to be explicitly coded in the profile.
Self Manage—Use this string to demonstrate the LDAP mode feature that allows a subscriber to update their own X.500 user schema information, such as name, address, e-mail, and hobbies.
Subaccount Manage—Use this string to demonstrate the LDAP mode feature that allows a subscriber to create a subaccount. The Demo mode does not create an actual subaccount; the supporting subaccount profile must be defined in the demo.txt file. Define the subaccount profile and use the F attribute.
Service Subscription—Use this string to demonstrate the LDAP mode feature that allows a subscriber to subscribe to a new service and have immediate access to that service. If you use this string, you must also add a C or L attribute.

Vname;type;value—Use this attribute to specify the initial values that will appear in the fields on the My Account page in the NWSP application running in Demo mode. The Demo allows you to change these values. Use a separate attribute line for each field. The format for each line consists of:

name—Name of the field on the My Account page in the NWSP application. These are X.500 fields. You can add more fields to the demo if you alter the NWSP application to display more fields, as described in the Cisco Subscriber Edge Services Manager Web Developer Guide. See the Cisco Distributed Administrator Tool Guide for a list of the X.500 names.
type—Identifies the format of value, as follows:

: S or s—Indicates that value is a string.
: V or v—Indicates that value is a vector of strings in the following format, including the parentheses:

{string1;string2;string3}

value—Indicates the value to be displayed in the field on the web page display.

: For example:

CserviceName—Use this attribute to demonstrate the LDAP mode self-subscription feature. This feature allows a subscriber to subscribe to a new service and have immediate access to that service. The serviceName value must match a service profile name defined elsewhere in the demo flat file (demo.txt).
LgroupName—Use this attribute to demonstrate the LDAP mode self-subscription feature, subscribing to a predefined group of services. The groupName value must match a service group profile name defined elsewhere in thedemo.txt file.
FparentAccountName—Use this attribute to indicate that this subscriber profile is a subaccount profile. The parentAccountName must match another subscriber profile name defined elsewhere in the demo flat file. (In the installed demo.txt file, subgolduser is defined as a subaccount to golduser.)
RusergroupName—Use this attribute to indicate that this subscriber is a member of a user group. The PDA application running in Demo mode demonstrates brand awareness by displaying different branded pages based on the user group values of bronze, silver, and gold. See the pdademo.txt file.

Table of Contents