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

    Enterprise Service Portals Provided with the SRC Software

    We provide several enterprise service portals in the in the SDK+AppSupport+Demos+Samples.tar.gz file on the Juniper Networks website at: https://www.juniper.net/support/products/src/index.html#sw. Some of the enterprise service portals we provide are intended for demonstration purposes or as a basis for developing a customized enterprise service portal for your SRC implementation. Other enterprise service portals are intended to serve a specific purpose and require little customization. The WAR files for the enterprise service portals contain all required libraries and Web contents.

    The following enterprise service portals are available:

    • Sample enterprise service portal
    • Enterprise Manager Portal
    • NAT Address Management Portal

    Sample Enterprise Service Portal

    The sample enterprise service portal incorporates many of the features that the enterprise service portal API offers. You can use the sample enterprise service portal to demonstrate the functionality available, and you can customize the sample enterprise service portal to create a portal for your own SRC implementation. The source code for the sample enterprise service portal is in its JSP pages; the code was created with the tags in the enterprise portal tag library.

    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.

    Enterprise Manager Portal

    Service providers can deploy Enterprise Manager Portal to provision services for enterprise subscribers. IT managers can access the SRC network through this portal and select the services they require. Enterprise Manager Portal is a complete application for which you need to customize only style sheets and icons.

    NAT Address Management Portal

    Service providers can deploy this enterprise service portal to manage public IP addresses for use with NAT services on devices running Junos OS. IT managers make requests about public IP addresses through Enterprise Manager Portal. The service provider responds to these requests through NAT Address Management Portal. This enterprise service portal is a complete application for which you need to customize only style sheets and icons.

    When an IT manager makes a request about public IP addresses through Enterprise Manager Portal, Enterprise Manager Portal sends an e-mail to a human administrator or a machine. For small installations or demonstration purposes, a human administrator can manage the public IP addresses; however, for large installations, public IP addresses are managed by machines. NAT Address Manager handles two operations: the supply of new IP addresses and the return of unwanted public IP addresses.

    If a human administrator provides the IP addresses, the administrator can access the Address Manager portal by clicking the portal address that is included in the e-mail from Enterprise Manager Portal. The administrator can then use NAT Address Management Portal to make a change to the IT manager’s public IP addresses in the directory. The IT manager can view the changes through Enterprise Manager Portal and can use the assigned IP addresses in subscriptions to NAT services.

    If you use a machine to manage public IP addresses, you must write an application that allows the machine to handle the e-mails that Enterprise Manager Portal sends. The e-mails contain XML code that NAT Address Management Portal and the machine must interpret. The following sequence of events describes how the machine interacts with the portals.

    1. The IT manager requests one or more IP addresses through Enterprise Manager Portal.
    2. Enterprise Manager Portal sends an e-mail to the machine that administers IP addresses.

      The subject line of the e-mail contains the URL of NAT Address Management Portal. The body of the e-mail contains an SDXNATStatusRequest message—XML code that contains a request for information about the status of a particular access.

    3. The machine forwards the e-mail to the URL in the subject line of the e-mail.
    4. The machine extracts the SDXNATStatusRequest message from the e-mail and sends it by means of HTTP to NAT Address Management Portal.
    5. NAT Address Management Portal analyzes the SDXNATStatusRequest message and returns an SDXNATStatusResponse message to the machine.
    6. The machine analyzes the response and determines the next action, such as providing an IP address for the enterprise.
    7. The machine sends the appropriate information in an SDXNATOperationRequest message to NAT Address Management Portal.
    8. NAT Address Management Portal updates the directory and returns an SDXNATOperationResponse message to the machine.

      When NAT Address Management Portal updates the directory, the IT manager can view the new status in Enterprise Manager Portal and can use the assigned IP addresses in subscriptions to NAT services.

    The XML messages described above contain subordinate elements that depend on whether the IT manager’s request is to obtain or return IP addresses. The document type definition (DTD) for the XML messages describes these subordinate elements. You can find the DTD in the in the SDK+AppSupport+Demos+Samples.tar.gz file on the Juniper Networks website at: https://www.juniper.net/support/products/src/index.html#sw. The file is located in the folder SDK/dtd.

    Modified: 2016-05-27