Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
ContentIndex
  
[+] Expand All
[-] Collapse All

 A  B  C  D  E  F  I  J  L  M  N  P  R  S  T  U  V  W

 

A

action classes in the sample residential portal
application protocols, managing
architecture    
enterprise service portal
 

B

bandwidth on demand.     See BoD    
BoD (bandwidth on demand)    
services
subscriptions
 

C

callback interface
captive portal    
implementing
preventing access to resources
configuration level in Enterprise Manager Portal
conventions    
notice icons
text
CORBA (Common Object Request Broker Architecture)    
plug-in interface    
enterprise service portal
remote API
customer support    1
contacting JTAC
 

D

DCU (destination class usage)
demonstration applications
deployment scenarios    
enterprise service portal
destination class usage
devices running Junos OS    
forwarding preferences
managing traffic
policies    
basic BoD
BOD
BoD and VPNs
firewall
NAT
provisioning services    
prerequisites
routing preferences
services    1
basic BoD
BoD
BoD and VPNs
firewall
NAT    12
directory server    
deployment with remote SAE
DirX directory server    
deployment with remote SAE
documentation    
comments on
 

E

enterprise    
service parameters
Enterprise Manager Portal    
application protocols, managing
BoD subscriptions
configuration level
deployment settings
firewall exception rules    
stateful firewalls    12
stateless firewalls    12
firewall subscriptions
fixed addresses for outgoing traffic
help
NAT    
IP address    123
rules for traffic
NAT Address Management Portal
NAT rules    12
overview    12
policies
public IP addresses, configuring    
incoming traffic
outgoing traffic
schedules    12
services
Enterprise Service Portal audit plug-in
enterprise service portals    1,  See also Enterprise Manager Portal    
accessing
architecture
configuring directory connections
data, displaying
deploying
improving performance
installing
managers    12
operators, managing    12
overview
performance
planning
prerequisites    12
server description
value substitution
value substitution for policy parameters
enterprise tag library    12
equipment registration    1,  See also sample residential portal    
description
event notification    
DHCP server
IP address manager
PCMM network
RADIUS server
events, IT manager audit
example-simple
 

F

files    
WEB-INF/jboss-web.xml
WEB-INF/portalBehavior.properties
WEB-INF/struts-config.xml    123
WEB-INF/tiles-defs.xml    123
WEB-INF/web.xml
firewall ports for sample SRC-applications
firewall services    
configuring    12
description
managing in Enterprise Manager Portal
policies for
router support
folders for installed software
forwarding preferences    12
 

I

installing    
Web applications
installing software    
enterprise service portals
interfaces    
callback
IP address managers, event notification
IP addresses    
acknowledging release
assigning in NAT Address Management Portal    12
NAT services    123
IP Filter
IP-in-IP tunneling
ISP service in sample residential portal
IT manager    
audit plug-in    
events
operators, managing    1234
 

J

Jakarta Struts Web application framework
Java development environment, Tomcat    12
Javadoc documentation for sample residential portal
JSP tag library.     See enterprise tag library    
JunosE routers    
policies    
basic BoD
BOD
services    
basic BoD
BoD
 

L

listeners, defining
 

M

manuals    
comments on
Monitoring Agent    
acting as pseudo RADIUS server
configuring    
properties
pseudo RADIUS agent    12
installing
intercepting DHCP messages
intercepting RADIUS accounting messages
monitoring    12
overview
stopping
multihop environment
 

N

NAT (Network Address Translation)    1,  See also NAT Address Management Portal    
rules
services for Enterprise Manager Portal
services, IP address    123
types
NAT Address Management Portal    
acknowledging IP address release
assigning IP addresses
deployment settings
Enterprise Manager Portal
overview
Network Address Translation.     See NAT    
NIC (network information collector)    
enterprise service portals. with
notice icons
 

P

packages, Solaris.     See Solaris packages    
parameters    
acquisition path and substitutions
sample enterprise service portal
patches for Solaris
performance    
enterprise service portals
plug-ins    1,  See also Enterprise Service Portal audit plug-in    
listeners
policies    
basic BoD
BoD
BoD and VPNs
NAT
parameters
ports for sample SRC-applications
precedence    
subscriptions
prevention, use of unauthorized resources
privileges    
IT managers
properties for sample residential portal
proxy request management
public wireless LAN applications
 

R

removing    
Solaris packages
Web applications
residential portal    1
developing
overview    12
prerequisites for development
RADIUS authentication for login
security
routing instances
rules, NAT
 

S

SAE (service activation engine)    
identifying
sample applications
sample enterprise service portal    
configuring connection to directory
customizing    1
privileges
data, displaying
managing services
monitoring    
service sessions
subscriptions
networks for departments    123
overview
service parameters    12
sample residential portal    
action classes
behaviors
customizing
developing portal based on the sample    12
development tools
equipment registration    12
installing
login
model components
overview    12
personal digital assistant (PDA)
prerequisites
schedules
service activation
services    
management
schedules
subscriptions
usage    
information
view components
Web application framework
sending traffic to VPNs
service activation
service parameters, enterprise
service schedules    
Enterprise Manager Portal, in
service schedules, sample residential portal
services    1,  See also firewall services    
basic BoD
BoD    123
devices running Junos OS    1
BoD and VPNs
NAT    12
sample enterprise service portal, managing
single-hop environment
Solaris packages    
installing
removing
Solaris patches
source class usage (SCU)
SRC single-hop requirement
subscribers    
billing
subscriptions    
enterprise hierarchy
priority
sample enterprise service portal, creating
substitutions    
parameter acquisition path
use
support, technical     See technical support    
 

T

technical support    
contacting JTAC
text conventions defined
Tomcat, as Java development environment    12
 

U

uninstalling.     See removing    
 

V

value substitution
virtual portal address
virtual private networks.     See VPNs    
VPNs (virtual private networks)    
directory
identifiers
modifying    1
VPN to which router sends traffic
sending traffic
stopping router from sending traffic
 

W

WAR files
Web application server    
application deployment
installing Web applications inside
Web applications    
installing
removing
WEB-INF/jboss-web.xml
WEB-INF/portalBehavior.properties
WEB-INF/struts-config.xml    123
WEB-INF/tiles-defs.xml    123
WEB-INF/web.xml

Configuration Files for the Sample Residential Portal Overview

The ssportal.war file contains the following configuration files in the WEB-INF directory:

  • portalBehavior.properties—Specifies properties to configure the portalBehavior servlet that determines the behavior of the sample residential portal.

    Modify this file to run the sample residential portal. See WEB-INF/portalBehavior.properties.

  • web.xml—Specifies the deployment descriptor for the sample residential portal. It describes the servlets, other components, and initialization parameters.

    Note: We recommend that you do not change the deployment descriptor.

  • jboss-web.xml—Contains one configuration property that defines the Web context of the sample residential portal as the root context.

    Modify this file to run the sample residential portal in a context other than root. The WEB-INF/jboss-web.xml file is proprietary to the JBoss application server.

  • struts-config.xml—Contains the configuration for the struts action servlet. See WEB-INF/struts-config.xml.
  • tiles-defs.xml—Contains the definitions of the tiles template system. The definitions describe the general layout of every webpage used in the sample residential portal. See WEB-INF/tiles-defs.xml.

WEB-INF/portalBehavior.properties

Set the following properties to configure the portalBehavior servlet to determine the behavior of the sample residential portal, and to connect to the LDAP server.

In addition, configure the other properties listed in the file for the network information collector (NIC) proxy configuration. For information about the values to configure for NIC properties, see SRC PE Network Guide.

Factory.behavior

  • Model for handling subscribers who connect using DHCP.
  • Value
    • net.juniper.smgt.ssp.model.EquipmentRegistrationBehavior
    • net.juniper.smgt.ssp.model.ISPServiceBehavior
    • net.juniper.smgt.ssp.model.CableBehavior
  • Guidelines—For information about the behaviors, see Installing the Sample Residential Portal.

Factory.locator

  • Method that the portal uses to locate the SAE that is managing the subscriber who tries to access the application.
  • Value
    • net.juniper.smgt.ssp.LocalFeatureLocator—Uses the locally configured object reference

      If you specify net.juniper.smgt.ssp.LocalFeatureLocator, configure a value for LocalFeatureLocator.objectRef.

    • net.juniper.smgt.ssp.DistributedFeatureLocator—Uses NIC configuration

LocalFeatureLocator.objectRef

  • CORBA object reference for the single SAE whose address is resolved by the locator. Specify the object reference if you set net.juniper.smgt.ssp.LocalFeatureLocator for Factory.locator.
  • Value—A reference to the CORBA object in one of the following formats:
    • The absolute path to the IOR file in the form file://<absolutePath>
    • The corbaloc URL in the format:

      corbaloc::<host>:<port>/SAE

      • <host>— IP address or host on which the SAE is installed.
      • <port>—TCP/IP port number for the SAE. The default is 8801.
    • COS naming service in the format:

      corbaname::<host>[:<port>][/NameService]#<key>

      where <key> is provided by the publisher of the IOR to the COS naming service.

    • The actual IOR in the form IOR:<objectReference>
  • Guidelines—Configure this property to use the portal as a demonstration application in a small environment that does not use NIC.

    By default, the SAE does not publish its IOR to a COS naming service.

  • Example
    • Absolute path—file:///opt/UMC/sae/var/run/sae.ior
    • corbaloc URL—corbaloc::10.10.6.171:8801/SAE
    • Actual IOR—

      IOR:000000000000002438444C3A736D67742E6A756E697...

LocalFeatureLocator.vrName

  • Virtual router to use in a Packet Cable Multimedia (PCMM) environment as the virtual router on the local machine.
  • Value—Name of virtual router
  • Guidelines—Configure this property only if you configured a value for LocalFeatureLocator.objectRef.
  • Default—default@simJunos

DistributedFeatureLocator.locName

  • Namespace for the NIC proxy configuration.
  • Value—<namespace>
  • Guidelines—For the cable behavior to create an assigned IP subscriber, the NIC must resolve an IP address to both the SAE IOR and the name of the virtual router that manages the IP address.
  • Default—/ which indicates the root namespace
  • Example—DistributedFeatureLocator.locName = /nicProxy indicates that the NIC proxy configuration is in /nicProxy.

Config.java.naming.provider.url

  • Location of the LDAP server.
  • Value—ldap://<IP address>:<port number>
  • Example—ldap://127.0.0.1:389 (default location if you are using the default OpenLDAP installation from the SRC installation).

Config.net.juniper.smgt.des.backup_provider_urls

  • Location of a backup LDAP server.
  • Value—ldap://<IP address>:<port number>

WEB-INF/struts-config.xml

The WEB-INF/struts-config.xml file contains the following settings. The file has multiple sections.

data-sources

  • Not used by the sample residential portal.

form-beans

  • Holds data entered in an HTML form and makes it available to the associated action.

global-exceptions

  • Specifies that the sample residential portal declare one global exception handler, which is invoked for any exception raised during action processing.

global-forwards

  • Global forwards for handling error situations. The sample residential portal declares a number of global forwards.
  • Value
    • unknownUser—Used when an action is processed for a subscriber who is not known by the system. The possible pages are either .error.unknownUser.page, which displays an error message, or .login.page, which asks the user to log in.
    • nonUniqueUser—Used when a request cannot be mapped to a single subscriber session.

      The sample residential portal uses the IP address of the subscriber, preventing this error.

    • unknownService—Used when a request refers to a service that is not loaded by the SAE. This can happen if services are modified while subscribers are connected to the portal.
    • unknownSubscription—Used when a request refers to a service to which the current subscriber is not subscribed.
    • serviceAuthError—Used if authorization for a service is denied; for example, because mutex group restrictions are violated or a plug-in has denied authorization.
    • loginError—Used if login was unsuccessful.
    • saeError—Used for SAE internal errors.
    • error—Used for any other problem.

action-mappings

  • Actions that each correspond to an interaction of the subscriber with the portal page. The sample residential portal declares a number of actions.
  • Value
    • /index—Displays the main page of the portal; collects information about the subscriber requesting the page and forwards it to the .index.page.
    • /services—Gets information about the subscribed services and forwards to the .services.page.
    • /activate—Checks whether authentication is required and forwards the request either to the .service.auth.page or back to the .services.page.

      Called when the subscriber wants to activate a service.

    • /deactivate—Forwards the request back to the .services.page.

      Called when the subscriber wants to deactivate an active service.

    • /schedules—Gets information about the service schedule. Allows the subscriber to view and change service schedules. The action forwards the request to the .schedules.page.
    • /scheduleOperation—Forwards the request back to the .schedules.page.

      Called when the subscriber wants to change the service schedule.

    • /usage—Collects statistics for currently active services and forwards them to the .usage.page.
    • /account—Allows modification of the activationTrigger property of currently subscribed services. After a change of the activationTrigger property has been processed, the action forwards subscribers to the .account.page.
    • /subscribe—Allows the subscriber to subscribe to and unsubscribe from services. After processing the subscription change, the action forwards subscribers to the .subscribe.page.
    • /register—Allows subscribers to register MAC addresses for authenticated DHCP addresses. The action checks whether the subscriber has provided a username and password and forwards the request to the .register.auth.page to enter the username and password or to the .register.page displaying the currently registered equipment.
    • /unregister—Allows subscribers to remove MAC addresses that are registered for DHCP addresses. The action checks whether the subscriber provided a username and password and forwards the request to the .unregister.auth.page to enter the username and password or to the .unregister.page displaying the currently registered equipment.
    • /login—Allows the subscriber to log in to the system. If the login causes a switch of the DHCP IP address, the request is forwarded to the wait.page. If the DHCP IP address remains the same after the login, the request is forwarded to the index.page.
    • /logout—Allows the subscriber to log out of the system. If the logout causes a switch of the DHCP IP address, the request is forwarded to the .wait.page. If the DHCP IP address remains the same after the login, the request is forwarded to the index.page.
    • /wait—Checks whether the IP address of the current subscriber is authenticated or unauthenticated. If the address is of the wrong type, the request is forwarded to the .wait.page, which will renew itself automatically. If the address is of the expected type, the request is forwarded to .index.page.
    • /accessDenied—Processes a captive portal request. The request is forwarded only to the .error.accessDenied.page.

controller

  • Ensures generation of the correct headers for disabling caching of the generated pages.
  • Value—nocache

message-resources

  • Base name of the resource bundle. The resource bundle contains message strings in different languages.
  • Value
    • WEB-INF/classes/net/juniper/smgt/ssp/ApplicationResources.properties

      The location of the resource file containing messages in English that is shipped with the sample residential portal.

    • WEB-INF/classes/net/juniper/smgt/ssp/ApplicationResources_xx.properties

      where xx is the two-letter ISO language code, optionally followed by an underline and the two-letter country code; for example, en_CA for English/Canada or zh_TW for Chinese/Taiwan.

      To create a sample residential portal that supports other languages, translate the messages and store the translated file in the above location.

plug-in

  • Processes templates.

WEB-INF/tiles-defs.xml

The WEB-INF/tiles-defs.xml file contains the following settings.

site.layout

  • Main definition that specifies the general structure of all pages. The layout is based on a common template file, /layouts/common.jsp. The definition contains values for template variables shared by all page definitions.
  • Value
    • title—Common title of all pages.
    • header—Page fragment displaying the header section of the pages.
    • menu—Page fragment displaying the menu bar.
    • footer—Page fragment displaying the footer section of the pages.
    • body—Page fragment displaying the content of the pages. The default setting is empty and should be overwritten by individual page definitions.
    • color—Color scheme used the by pages. A color scheme consists of a style sheet (style_sheets/color.css) and a set of images (stored in images/color). The predefined color schemes are blue and green.
    • menuTag—Action name of the current page. The menu bar code uses this tag to highlight the action associated with the current page.

site.layout.nomenu

  • Provides an extension of the main layout that defines a version of the page without a menu bar.

.*.page

  • Provides the definition of portal pages. These pages are used for forwards in the action-mappings section of the struts-config.xml file. The page definitions extend one of the common layouts and define the value of the body variable as appropriate.

Modified: 2016-05-27