Navigation
Back up to About Overview
[+] Expand All
[-] Collapse All
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
Using Schedules in Enterprise Manager Portal
Tasks to use a schedule are:
- Creating a Schedule in Enterprise Manager Portal
- Applying a Schedule to a Service in Enterprise Manager Portal
Creating a Schedule in Enterprise Manager Portal
To create a schedule:
- Click the Schedules tab.
The Schedules page appears.
- In the Schedules page, click Create.
The Schedule Definition Page appears.
- Enter field values to define a schedule, and click Save.
See Schedule Fields in Enterprise Manager Portal.
A description of the schedule appears in the Schedules page.
Note: The system generates the description of the service. If you want a page to display a different description, you can edit the JSP page and change and compile the Java classes found in the WAR file. If you need assistance to make these changes, contact Juniper Professional Services.
Schedule Fields in Enterprise Manager Portal
Use the fields in this topic to define a service schedule.
Schedule Name
- Name of the schedule.
- Value—Text string
- Default—No value
Subscription is
- Whether or not the subscription can be activated during or outside the scheduled time.
- Value
- Enabled during schedule—Service can be activated during the scheduled time.
- Enabled outside schedule—Service can be activated outside the scheduled time.
- Default—No value
Start Time
- Time that a scheduled activity is to start.
- Value—Time of day in the format hh:mm, where hh indicates the hour and mm indicates the minute. The range is 00:00 to 23:59.
- Default—No value
- Example—13:15
Time Zone
- Time zone for which the schedule is defined.
- Value—Name of time zone
- Default—Local time zone
Duration
- Length of time after the start time that a scheduled activity is allowed.
- Value—Length of time in minutes, hours, days, or weeks
- Guidelines—The length of time should be more than
15 minutes; using a shorter time could adversely affect system performance. Table 21 shows the maximum duration for specified
recurrence patterns.
Table 21: Maximum Duration for Recurrence Patterns
For This Recurrence Pattern
Duration Must Be Less Than
Daily
24 hours
Weekly
24 hours
Monthly
28th day of the month
Yearly
365 days
- Default—No value
- Example—2 hours
During the interval from the start time to 2 hours after the start time, the action (defined on the Schedule Definition Page under the During schedule subscription is field) is available.
Once
- Date on which the scheduled activity is to occur.
- Value—Date in the format mm/dd/yyyy, where mm indicates the month, dd indicates the day, and yyyy indicates the year
- Default—No value
- Example—12/10/2005
Daily
- Whether or not the scheduled activity is to occur every day of the week or every weekday.
- Value
- day—Scheduled activity is to occur on every day of the week
- weekday—Scheduled activity is to occur on each day Monday through Friday
- Default—No value
Weekly
- Scheduled activity occurs on a specified day or days during a week.
- Value—Name of day(s) of the week
- Default—No value
Monthly
- Scheduled activity occurs on the indicated day every month
- Value—Day of the month
- Default—No value
Yearly
- Scheduled activity occurs on a specified day each year
- Value—Month and day
- Default—No value
Range of recurrence Start by
- Date on which a schedule starts for a recurring action.
- Value—Date in the format mm/dd/yyyy, where mm indicates the month, dd indicates the day, and yyyy indicates the year
- Default—No value
The default indicates that the recurring schedule starts immediately—the next time the recurrence pattern applies.
- Example—12/10/2005
Range of recurrence End by
- Date on which a schedule ends for a recurring action.
- Value—Date in the format mm/dd/yyyy, where mm indicates the month, dd indicates the day, and yyyy indicates the year
- Default—No value
The default indicates that the schedule has no end date and remains in place indefinitely.
- Example—12/10/2005
Applying a Schedule to a Service in Enterprise Manager Portal
Before you can schedule a subscription, you must define a schedule.
To apply a schedule to a service that was configured earlier:
- In the navigation pane of Enterprise Manager Portal, click the subscriber for which you want to schedule a service.
- Click the tab for the type of service to be scheduled:
- Bandwidth or Bandwidth & VPNs
- Firewall
Note: If VPN features are not configured, the tab is named Bandwidth.
- On the same line as the service to be assigned to a schedule,
select the name of a schedule under Schedule, and click Apply.
The service provider controls which services can be scheduled. Text on the page indicates which services cannot be scheduled.
