- 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
Uploading a License Key
If you need assistance to obtain a new or updated license key, contact your local sales representative.
License keys determine your entitlement to JSA products and features, and the system capacity for handling events and flows.
You must upload a license key when you are doing these tasks:
Updating an expired JSA console license
Increasing the events per minute (EPS) or flows per minute (FPM) limits
Adding a JSA product to your deployment, such as JSA Vulnerability Manager, to your deployment
As of JSA 7.3.0, you do not need to upload a new license when you add an Event Processor or Flow Processor to your deployment. Event and flow processors are automatically assigned a perpetual, or permanent, appliance license, and you can allocate EPS or FPM from the license pool to the appliance.
As of JSA 7.3.2, you can now acquire stackable EPS/Flow increments instead of replacing existing console or other managed hosts license when you need to increase the overall event or flow thresholds of your deployment. After the licenses are uploaded and deployed, the event/flow capacity can then be reallocated through the License Pool Management.
If the license key for your JSA console expires, you are automatically directed to the System and License Management window when you log on. You must upload a license key before you can continue.
If a managed host system has an expired license key, a message is displayed when you log in that indicates that a managed host requires a new license key. You use the System and License Management window to update the license key. If the license pool is not over allocated, delete the expired key and allocate EPS or FPM from the license pool to the managed host.
- On the navigation menu (
), click Admin. - In the System Configuration section, click System and License Management.
- On the toolbar, click Upload License.
- In the dialog box, click Select File.
- Select the license key, and click Open.
- Click Upload, and then click Confirm.
The license is uploaded to your JSA console and is displayed in the System and License Management window.
By default, most licenses are not immediately allocated to a JSA host. However, the system automatically allocates all JSA Vulnerability Manager, and JSA Risk Manager keys to the JSA console.
