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

Related Documentation

    Function of Enterprise Service Portals

    The SRC software enables service providers to use enterprise service portals to provision services to enterprise subscribers who connect to the SRC network by means of a JunosE router or a device running Junos OS. An enterprise service portal is a standalone Web application that runs in a Java 2 Platform, Enterprise Edition (J2EE)-compliant Web application server. An enterprise service portal must have a corresponding configuration in the directory. Typically, a service provider provisions the router and configures the initial directory structure.

    IT managers in an enterprise log in to the SRC network through an enterprise service portal. The managers can then activate services and perform some administrative tasks associated with their enterprises. When an IT manager requests an action through an enterprise service portal, the enterprise service portal uses the SRC software’s enterprise service portal application programming interface (API) to interact with the SAE and to update data in the directory.

    More specifically, the enterprise service portal calls methods in this API to:

    • Authenticate IT managers in an enterprise.
    • Create, delete, and modify accounts for IT managers.
    • Navigate among retailers, enterprises, sites, and accesses.
    • Create, delete, activate, and deactivate subscriptions to services.
    • Get feedback from the sessions that a subscription generates. This feedback, which comes directly from the SAE managing the session, indicates whether the session is active in the network and provides the values used for the service parameters.
    • Get feedback about the use of resources, such as the number of bytes and packets the SAE has sent or received for a particular service.
    • Configure values for service parameters.

    Consistency of Data in the Directory

    Enterprise service portals can monitor the consistency of data as you enter it through the portal; for example, an enterprise service portal can prevent you from deleting a subscription if that subscription depends on other data in the directory. Enterprise service portals do not constantly monitor the consistency of existing data in the directory for all subscribers, however, because doing so would consume significant network resources. Consequently, if you use an LDAP browser to modify data in the directory that was entered through a portal, you must be sure that the data in the directory is consistent.

    Privileges of IT Managers

    The enterprise service portal API controls the privileges that determine how IT managers can manipulate subscribers, subscriptions, and services associated with a retailer or enterprise. All IT managers in an enterprise share the same connections to the directory.

    Developing and Customizing Enterprise Service Portals

    You can customize enterprise service portals to provide customer-specific webpages and supply specified services. By modifying JavaServer pages (JSP), which use a set of customized tags to call methods in the enterprise service portal API, you can customize an enterprise service portal to suit a customer’s environment.

    For information about the JSP tags that you can use to customize an enterprise service portal, see the documentation for the enterprise tag library on the Juniper Networks website at https://www.juniper.net/techpubs/software/management/src/api-index.html.

    Identifying the SAE

    An enterprise service portal handles a request from an IT manager by communicating with the SAE that manages the subscriber affected by the IT manager’s request. You can use the following methods to allow the enterprise service portal to identify which SAE manages a subscriber:

    • For SRC implementations that use more than five SAEs, configure a network information collector (NIC) that takes the distinguished name (DN) of an access as the key and returns the corresponding SAE as the value.
    • For SRC implementations that use five or fewer SAEs, you can use directory eventing to identify the SAEs. If you configure this option, SAEs update the addresses of their external interfaces in the directory at a specified time interval. Each update triggers an event that is sent to the enterprise service portal to confirm that the corresponding SAE is available. If the enterprise service portal does not receive the update event within a certain time, the enterprise service portal assumes that the SAE is not available and subsequently does not send any service activation or feedback requests to that SAE. When the SAE becomes available and starts to manage subscribers again, the enterprise service portal sends new requests to that SAE.

    Modified: 2016-05-27