- play_arrow What's New for Administrators
- play_arrow Overview of JSA Administration
- play_arrow User Management
- play_arrow System Management
- System Management
- System Health Information
- JSA Component Types
- Data Nodes
- Network Interface Management
- JSA System Time
- NAT-Enabled Networks
- Off-site Hosts Management
- Managed Hosts
- Configuration Changes in your JSA Environment
- Deploying Changes
- Restarting the Event Collection Service
- Shutting Down a System
- Restarting a System
- Collecting Log Files
- Changing the Root Password on Your JSA Console
- Resetting SIM
- play_arrow JSA Set Up Tasks
- JSA Set Up Tasks
- Network Hierarchy
- Automatic Updates
- Manual Updates
- Configuring System settings
- IF-MAP Server Certificates
- SSL Certificates
- IPv6 Addressing in JSA Deployments
- Advanced Iptables Rules Examples
- Data Retention
- System Notifications
- Custom Offense Close Reasons
- Configuring a Custom Asset Property
- Index Management
- Restrictions to Prevent Resource-intensive Searches
- App Hosts
- Checking the Integrity Of Event and Flow Logs
- Adding Custom Actions
- Managing Aggregated Data Views
- Accessing a GLOBALVIEW Database
- play_arrow Event Data Processing in JSA
- Event Data Processing in JSA
- DSM Editor Overview
- Properties in the DSM Editor
- Property Configuration in the DSM Editor
- Opening the DSM Editor
- Configuring a Log Source Type
- Configuring Property Autodetection for Log Source Types
- Configuring Log Source Autodetection for Log Source Types
- Configuring DSM Parameters for Log Source Types
- Custom Log Source Types
- Custom Property Definitions in the DSM Editor
- Event Mapping
- Exporting Contents from the DSM Editor
- play_arrow Using Reference Data in JSA
- play_arrow User Information Source Configuration
- play_arrow Juniper Networks X-Force Integration
- play_arrow Managing Authorized Services
- play_arrow Backup and Recovery
- play_arrow Flow Sources Management
- play_arrow Remote Networks and Services Configuration
- play_arrow Server Discovery
- play_arrow Domain Segmentation
- play_arrow Multitenant Management
- Multitenant Management
- User Roles in a Multitenant Environment
- Domains and Log Sources in Multitenant Environments
- Provisioning a New Tenant
- Monitoring License Usage in Multitenant Deployments
- Rules Management in Multitenant Deployments
- Network Hierarchy Updates in a Multitenant Deployment
- Retention Policies for Tenants
- play_arrow Asset Management
- play_arrow Configuring JSA to Forward Data to Other Systems
- Forward Data to Other Systems
- Adding Forwarding Destinations
- Configuring Forwarding Profiles
- Configuring Routing Rules to Forward Data
- Using Custom Rules and Rule Responses to Forward Data
- Configuring Routing Rules to Use the JSA Data Store
- Viewing Forwarding Destinations
- Viewing and Managing Forwarding Destinations
- Viewing and Managing Routing Rules
- play_arrow Event Store and Forward
- play_arrow Security Content
- play_arrow SNMP Trap Configuration
- play_arrow Protect Sensitive Data
- play_arrow Log Files
- play_arrow Event Categories
- play_arrow Common Ports and Servers Used by JSA
- play_arrow RESTful API
License Management
License keys entitle you to specific JSA products, and control the event and flow capacity for your JSA deployment. You can add licenses to your deployment to activate other JSA products, such as JSA Vulnerability Manager.
When you install JSA, the default license key is temporary and gives you access to the system for 35 days from the installation date. The email that you received from Juniper Networks when you purchased JSA contains your permanent license keys. These license keys extend the capabilities of your appliance, and you must apply them before the default license expires.
To apply a license key to the system, follow these steps:
Obtain the license key. For new or updated license keys, contact your local sales representative.
After you apply the license keys to JSA, Distributing Event and Flow Capacity to ensure that each of the managed hosts is allocated enough capacity to handle the average volume of network traffic, and still have enough EPS and FPM available to efficiently handle a data spike. You do not need to deploy the changes after you redistribute the EPS and FPM capacity.
License Expiry
The processing capacity of the system is measured by the volume of events and flows that JSA can process in real time. The capacity can be limited by either the appliance hardware or the license keys. The temporary license key allows for 5,000 events per second (EPS) on the JSA console, and 10,000 EPS on each managed host. The FPM rate for the temporary license is 200,000 on both the JSA console and the managed hosts.
When a license expires, JSA continues to process events and flows up to the licensed capacity limits. If the EPS and FPM capacity of the expired license was allocated to a host, the shared license pool might go into a deficit, and cause JSA to block capabilities on the Network Activity and Log Activity tabs.
When JSA is not licensed to handle the volume of incoming network data, you can add a license that has more event or flow capacity.