A
B
- bandwidth on demand. See BoD
- BoD (bandwidth on demand)
C
- callback interface
- captive portal
- configuration level in Enterprise Manager Portal
- conventions
- CORBA (Common Object Request Broker Architecture)
- plug-in interface
- remote API
- customer support 1
D
- DCU (destination class usage)
- demonstration applications
- deployment scenarios
- destination class usage
- devices running Junos OS
- forwarding preferences
- managing traffic
- policies
- provisioning services
- routing preferences
- services 1
- directory server
- DirX directory server
- documentation
E
- enterprise
- Enterprise Manager Portal
- application protocols, managing
- BoD subscriptions
- configuration level
- deployment settings
- firewall exception rules
- firewall subscriptions
- fixed addresses for outgoing traffic
- help
- NAT
- IP address 1, 2, 3
- rules for traffic
- NAT Address Management Portal
- NAT rules 1, 2
- overview 1, 2
- policies
- public IP addresses, configuring
- schedules 1, 2
- services
- Enterprise Service Portal audit plug-in
- enterprise service portals 1, See also Enterprise Manager Portal
- enterprise tag library 1, 2
- equipment registration 1, See also sample residential portal
- event notification
- events, IT manager audit
- example-simple
F
- files
- WEB-INF/jboss-web.xml
- WEB-INF/portalBehavior.properties
- WEB-INF/struts-config.xml 1, 2, 3
- WEB-INF/tiles-defs.xml 1, 2, 3
- WEB-INF/web.xml
- firewall ports for sample SRC-applications
- firewall services
- folders for installed software
- forwarding preferences 1, 2
I
- installing
- installing software
- interfaces
- IP address managers, event notification
- IP addresses
- IP Filter
- IP-in-IP tunneling
- ISP service in sample residential portal
- IT manager
J
- Jakarta Struts Web application framework
- Java development environment, Tomcat 1, 2
- Javadoc documentation for sample residential portal
- JSP tag library. See enterprise tag library
- JunosE routers
L
M
- manuals
- Monitoring Agent
- acting as pseudo RADIUS server
- configuring
- properties
- pseudo RADIUS agent 1, 2
- installing
- intercepting DHCP messages
- intercepting RADIUS accounting messages
- monitoring 1, 2
- overview
- stopping
- multihop environment
N
- NAT (Network Address Translation) 1, See also NAT Address Management Portal
- NAT Address Management Portal
- Network Address Translation. See NAT
- NIC (network information collector)
- notice icons
P
- packages, Solaris. See Solaris packages
- parameters
- patches for Solaris
- performance
- plug-ins 1, See also Enterprise Service Portal audit plug-in
- policies
- ports for sample SRC-applications
- precedence
- prevention, use of unauthorized resources
- privileges
- properties for sample residential portal
- proxy request management
- public wireless LAN applications
R
- removing
- residential portal 1
- routing instances
- rules, NAT
S
- SAE (service activation engine)
- sample applications
- sample enterprise service portal
- configuring connection to directory
- customizing 1
- data, displaying
- managing services
- monitoring
- networks for departments 1, 2, 3
- overview
- service parameters 1, 2
- sample residential portal
- action classes
- behaviors
- customizing
- developing portal based on the sample 1, 2
- development tools
- equipment registration 1, 2
- installing
- login
- model components
- overview 1, 2
- personal digital assistant (PDA)
- prerequisites
- schedules
- service activation
- services
- usage
- view components
- Web application framework
- sending traffic to VPNs
- service activation
- service parameters, enterprise
- service schedules
- service schedules, sample residential portal
- services 1, See also firewall services
- basic BoD
- BoD 1, 2, 3
- devices running Junos OS 1
- BoD and VPNs
- NAT 1, 2
- sample enterprise service portal, managing
- single-hop environment
- Solaris packages
- Solaris patches
- source class usage (SCU)
- SRC single-hop requirement
- subscribers
- subscriptions
- substitutions
- support, technical See technical support
T
- technical support
- text conventions defined
- Tomcat, as Java development environment 1, 2
U
- uninstalling. See removing
V
- value substitution
- virtual portal address
- virtual private networks. See VPNs
- VPNs (virtual private networks)
W
- WAR files
- Web application server
- Web applications
- WEB-INF/jboss-web.xml
- WEB-INF/portalBehavior.properties
- WEB-INF/struts-config.xml 1, 2, 3
- WEB-INF/tiles-defs.xml 1, 2, 3
- WEB-INF/web.xml
Download This Guide
Related Documentation
Services for Enterprise Manager Portal Overview
Enterprise Manager Portal is an application that lets service providers provision services for enterprise subscribers.
Enterprise Manager Portal can apply the types of services listed in Table 7 to enterprise traffic as specified on devices running Junos OS or JunosE routers.
Table 7: Services Available from Enterprise Manager Portal
Types of Service | Types of Router |
|---|---|
Firewalls—stateful or stateless | Devices running Junos OS |
Network Address Translation (NAT) | Devices running Junos OS |
Bandwidth on demand (BoD) | Devices running Junos OS or JunosE routers |
BoD for traffic routed to specified layer 3 VPNs | Devices running Junos OS |
The service provider uses services and policies in the SRC directory to manage traffic on a device running Junos OS or on a JunosE router. IT managers in enterprises that are customers of the service provider subscribe to these services through Enterprise Manager Portal.
Some of the services and policies are defined in the sample data and require little or no customization. You can, however, create some new services and policies, such as those for BoD.
Directory Structure
Use the directory structure in the sample data to organize services and policies. The following list shows the location of the policies and services in the directory:
- Services—l=entJunos, o=Scopes, o=umc
- Policies—ou=entJunos, o=Policies, o=umc
Although the scope that includes services for Enterprise Manager Portal is named entJunos, the policies for the BoD services have policy rules for both JunosE routers as well as devices running Junos OS.
Priorities for Subscriptions
Each subscription to a service has a priority that is identified by a service parameter named priority. A subscription with a lower priority setting takes precedence over a subscription with a higher priority setting. The SAE uses the priorities to determine the order in which it applies subscriptions to a particular type of service to traffic. For example, if the same traffic is affected by subscriptions to several firewall services on a device running Junos OS, the SAE applies those subscriptions in a prioritized order. Priorities of different types of service are independent of each other; for example, for devices running Junos OS, priorities of NAT services are independent of priorities for BoD services.
Depending on the type of service, you must specify either an explicit priority or a range of priorities in the service or the policy rules. When you specify a range of priorities, the IT manager selects an explicit priority in this range through Enterprise Manager Portal. The sample data includes definitions of priorities for each type of service; however, you can modify the priorities if you want to provide different ranges of priorities.
A substitution in a subscription provides the value for the service parameter named priority. This parameter is in the precedence policy rule field to control the ordering of policies when a subscription is activated.
