[Contents] [Prev] [Next] [Index] [Report an Error]

# Overview of the Sample Residential Portal

The sample residential portal is a demonstration portal that shows how to use some of the features available in the Common Object Request Broker Architecture (CORBA) remote application programming interface (API) to create a Web application. You can customize the sample residential portal for your environment, or create a new Web application using the SAE CORBA remote API.

## Web Application Architecture

The sample residential portal uses the Jakarta Struts Web application framework. Although Struts provides an easy and extensible framework for building Web applications, it is not required for building portals that use the CORBA remote API.

Jakarta Struts supports the model-view-control design paradigm, which separates an application into three sets of components:

- Model—Contains the data and business logic.
- View—Contains the presentation to the subscriber.
- Control—Contains the interface procedures.

The strict separation of the three layers promotes reuse of the components and allows easy adaptation of the application to different requirements.

### Model Components

The model provides an abstraction layer of the CORBA remote API and contains the business logic, which determines how the sample portal behaves. The sample residential portal includes several implementations of the model (which we call behaviors) to demonstrate some typical usage scenarios. See Behaviors for the Sample Residential Portal for more information.

### View Components

The view components of the Web application provide the HTML code sent to the subscriber’s browser. The view is implemented by means of JavaServer Pages (JSP) and several tag libraries provided as part of Jakarta Struts.

The tiles tag library provides a template mechanism to build Web pages based on reusable partial pages. The general layout of all pages of the portal application is defined in a single JSP page.

### Control Components

The control components provide the interactions between the subscriber and the mode through the Action and ActionForm classes.

Action classes implement the functionality for a single operation, such as “ list the subscriptions of a particular service category,” or “ activate a service.”

ActionForm classes encapsulate data provided by the subscriber on an input form. The Struts framework initializes these classes with data entered in an HTML form and passes them to the appropriate action. The ActionForms are then passed to a view component that uses the data to initialize the content of fields in an input form.

## Behaviors for the Sample Residential Portal

The sample residential portal provides the following user behaviors (scenarios):

- Equipment registration

  Used by subscribers who use Dynamic Host Configuration Protocol (DHCP) connections to register their devices to receive an authenticated IP address.

- Internet Service Provider (ISP) service

  Used by subscribers who use Point-to-Point Protocol (PPP), static IP, or unauthenticated DHCP connections to log in to the portal and receive an unauthenticated IP address.

- Cable

  Used by subscribers who have assigned IP addresses in a PacketCable Multimedia (PCMM) environment.

[Contents] [Prev] [Next] [Index] [Report an Error]