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
Developing a Portal Based on the Sample Residential Portal
The source code is included with the sample residential portal. To modify the behavior of the portal beyond a simple configuration, install a Java development environment. You can find the source code of the sample residential portal in the directory WEB-INF/src. The portal pages are stored in the layout and tiles directories.
The sample residential portal does not require any specific environment, but the procedures below assume that you use the Eclipse platform. A servlet container is required to run the portals during development. We recommend that you use Tomcat and its Eclipse plug-in.
For information about your development environment, see the documentation for the product you are using.
Preparing to Develop a Portal Based on the Sample Residential Portal
The following instructions describe how to set up a development environment that uses Eclipse and Tomcat on a Solaris platform. If you want to use Eclipse and Tomcat on a different operating system, see the following websites:
- For Eclipse:
- For Tomcat:
To get ready to develop a portal based on the sample residential portal:
- Download and install Eclipse from
- Download the Tomcat plug-in for Eclipse from
- Unzip the plug-in into the Eclipse installation directory.
- Download Tomcat from
- Install Tomcat:mkdir $HOME/eclipse cd $HOME/eclipse unzip /tmp/eclipse-SDK-2.0.2-solaris-motif.zip unzip /tmp/tomcatPluginV201.zip cd $HOME gzip –dc /tmp/tomcat-4.1.18.tar.gz | tar xvf -
- Start Eclipse.
- Configure the Tomcat plug-in.
Select Window > Preferences > Tomcat, and configure the Tomcat version and the path where you installed Tomcat.
Creating a Portal Project
To create a new Tomcat project inside Eclipse:
- Select File > New > Project > Java > Tomcat Project, enter the name of the project, and click Finish.
- Select File > Import… > Zip File, enter the path for ssportal.war; and click Finish.
- Select File > Properties > Java Build Path > Libraries > Add Jars, open the sample project, navigate to WEB-INF/lib, and select all JAR files in the WEB-INF/lib directory.
- Select File > Properties > Tomcat, and click Can update server.xml file.
Building the Portal
Eclipse automatically rebuilds the project when you save a modified source file.
To test or debug the project, run the code inside Tomcat.
To start Tomcat:
- Select Tomcat > Start Tomcat.
You can set break points in your code to debug the code.
Deploying the Portal
To create a new Web application, set the name of the target WAR file.
- Select File > Properties > Tomcat.
- Enter the path of the target WAR file in the field WAR file for export.
- Right-click the portal project, and select Tomcat Project > Export to the WAR file set in project properties.
- Copy the WAR file to the final deployment location; for example, /opt/UMC/jboss/server/default/deploy on your portal server.
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 Configuring Simulated Router Drivers (SRC CLI).
