- play_arrow What's New for Administrators
- play_arrow Overview of JSA Administration
- play_arrow User Management
- play_arrow License 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 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
Content Management Script Parameters
Use the contentManagement.pl script to export content from one JSA deployment and import it to another deployment.
The following table describes the parameters for the contentManagement.pl script and the actions to which each parameter applies.
/opt/qradar/bin/contentManagement.pl --action [action_type] [script_parameters]
Parameter | Description |
---|---|
-a[action_type] or --action[action_type] | Required. Specifies the action. Valid action types are The |
-c[content_type] or --content-type[content_type] | Used with the When used with the When used with the |
-d or --debug | Used with all actions. Use debug level logging when you run the |
-e or --include-reference-data-elements | Used with the Set this flag to include reference data keys and elements in the export. Reference data keys and reference data elements are applicable
to the |
-f[file_path] or --file[file_path] | Used with When used with the When used with the The filename and path are case-sensitive. |
-g or --global-view | Used with the Includes accumulated data in the export. |
-h[action_type] or --help[action_type] | Used with all actions. Displays help that is specific to the |
-i[content_identifier] or --id[content_identifier] | Used with the . You can specify all to Exporting All Custom Content Of a Specific Type. |
-n[name] or --name[name] | Used with the Specifies the name of the package template file that contains the list of custom content to export. The package template file is created the first time that you
use the You must specify the |
-o[filepath] or --output-directory[filepath] | Used with the Specifies the full path to the directory where the export file is written. If no output directory is specified, the content is exported to the current directory. If the specified output directory does not exist, it is created. |
-q or --quiet | Used with all actions. No output appears on the screen. |
-r[regex] or --regex[regex] | Used with the When searching, you must use the |
-t[compression_type] or --compression-type[compression_type] | Used with the Specifies the compression type of the export file. Valid compression types are ZIP and TARGZ (case sensitive). If you do not specify a compression type, the default compression type is ZIP. |
-u[user] or --user[user] | Used with the Specifies the user that replaces the current owner when you import user-specific data. The user must exist on the target system before you import the content. |
-v or --verbose | Used with all actions. Use when you log in to view default-level information for the content management tool. |