|
|
This chapter describes how to access the Cisco Subscriber Edge Services Manager (SESM) application from a web browser. It also describes configuration procedures for a customized application. The chapter contains the following topics:
Subscribers can access SESM web applications, such as NWSP, with the following browsers:
To access the NWSP application, follow these procedures:
Step 2 Start a browser.
Step 3 Go to the NWSP URL, which is the host and port number that you specified during the installation:
Default values are:
http://localhost:8080
If captive portal is configured, the port value should be 80, as follows:
http://localhost:80
 |
Note If the captive portal feature is configured for the SESM application and the TCP redirect feature is configured on SSG, subscribers are redirected to the captive portal application without entering an URL. |
Step 4 When the NWSP logon page appears, log in using a valid user ID and password. A valid user ID and password is defined in user profiles as follows:
|
Note See "Demo Quick Start," for instructions on logging on to the NWSP application running in DEMO mode. |
The Cisco Service Selection Dashboard (SSD) Release 3.0(1) is a collection of components for creating specialized Java 2 Platform, Enterprise Edition (J2EE) web server applications. J2EE provides a framework for using various Java-based components to develop multi-tiered applications. The multi-tiered application (as opposed to the two-tiered client server application) provides many opportunities for isolating and controlling functional pieces of a large application. For more information about the J2EE development platform, see:
A Cisco SESM application consists of the following:
<installDir>nwsp
call "%SCRIPTDIR%start.cmd" nwsp %PORTNO%
jetty subdirectory. For example, for the NWSP application, the configuration file name is:
nwsp.jetty.xml
An application name in the startup script tells the ConfigAgent which configuration file to open. The application name is passed to ConfigAgent by the application startup scripts. The application name might also be used in other ways. For example, you can configure the parameter that defines the Jetty Server log file name to incorporate the application name in the log file name.
Application developers at your site might make changes to the delivered NWSP sample application, producing a customized application. Customized applications require their own set of configuration files, although the files might be very similar to those provided for the sample application.
To configure a customized SESM application that will run on the Jetty server, follow these steps:
nwsp.jetty.xml file and appropriately rename it. For example:
jetty
config
newApplication.jetty.xml
Step 2 Edit the new file, enabling and disabling features as described in the "Configuring an SESM Web Application" section.
Step 3 Create a startup script for the new application by copying the startNWSP script and appropriately renaming the copy. For example:
jetty
bin
startNewApplication
Step 4 Edit the new file, changing the application name and the port number parameters. See the "Explanation of the NWSP and CDAT Startup Scripts" section for more information.
Step 5 Copy the nwsp directory structure, and rename the nwsp objects appropriately. For example, copy:
nwsp
config
nwsp.xml
docroot
docs
Step 6 See the Cisco Subscriber Edge Services Manager Web Developer Guide for information about customizing the JSPs, images, and other components. That guide also describes how to update the docroot folder, recompile affected components, and edit the web.xml file.
Posted: Wed Jul 24 12:19:33 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.