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
Installing the Sample Residential Portal
The sample residential portal is a Web application. The application is packaged as a standard Web application archive (WAR file) in the webapp subdirectory in the SRC software distribution.
Before you install the sample residential portal:
- (Optional) Install a Web application server on the machine on which you want to install the sample residential portal. We recommend you use the Web application server included in the SRC software.
- Install the sample data from the SRC software distribution. See Loading Sample Data into a Juniper Networks Database (SRC CLI).
- Set up the RADIUS authfile for the user scenario you want to demonstrate. See Installing the Sample Residential Portal.
Tasks to install the sample residential portal are:
- Preparing the Application for Customization
- Configuring the Sample Residential Portal
- Deploying the Updated WAR File
Note: The sample residential portal can be installed by root or authorized nonroot users.
Preparing the Application for Customization
When you customize the sample residential portal, copy the WAR file to a temporary folder and work in that folder. To do so:
- Login as root or another authorized user.
- Create a temporary folder in which you will work on the
WAR file.mkdir ssportal
- Access the temporary folder.cd ssportal
- Copy the WAR file to the temporary folder.cp /cdrom/cdrom0/Demos+Sample_Applications/webapp/ssportal.war.
Configuring the Sample Residential Portal
To configure the sample residential portal:
- Access the temporary folder to which you copied the WAR
file.cd ssportal
- Extract the files from the WAR file.unzip -quo ssportal.war
- With a text editor, edit the portalBehavior.properties file and other files in the WEB-INF directory
as needed. See Configuration Files for the Sample Residential Portal Overview.
Use WEB-INF/portalBehavior.properties as a guideline for editing the portalBehavior.properties file to use properties specific to your environment.
- Replace the portalBehavior.properties and any other updated
files in the WAR file.zip -u ssportal.war
Deploying the Updated WAR File
To deploy the updated WAR file:
- Copy the WAR file to the deployment directory for your
Web server.
If you are using JBoss, copy the file to /opt/UMC/jboss/ server/default/deploy directory. JBoss automatically starts the Web application when a new WAR file is copied into the deployment directory.
By default the sample residential portal is deployed into the root context (“/”). You can access the portal through http://server:8080. If you want to deploy the sample residential portal into something other than the root context, modify the WEB-INF/jboss-web.xml configuration file.
Testing a Portal Application
Simulated router drivers allow you to create subscriber sessions without connecting to a router. You can use a simulated router drive when you want to test your portal application. See SRC PE Monitoring and Troubleshooting Guide.
