Supported Packages for Content Synchronization
Content synchronization provides the ability to create content in one ESM installation and push this content to other ESM installations. With the use of the content management feature, you can establish peer relationships and designate the publisher and subscribers. You can then manage packages to be pushed automatically or manually. Details on content management are in the Command Center User's Guide.
Not all packaged resources are eligible for content synchronization. The following table contains a list of resource packages you can push to subscribers.
Note: It is assumed you have created the package with the contentsync format, as described in Creating or Editing Packages.
|
Resource |
Notes |
|---|---|
|
Active channels |
|
|
Active lists |
Definition only, not list entries. Subscribers can override with their own entries. |
|
Drilldowns |
|
|
Drilldown lists |
|
|
Dashboards |
|
|
Data Monitors |
Definition only, but not data. Subscribers can override with their own data. |
|
Customers |
|
|
Fields |
|
|
Field Sets |
|
|
Integration Configurations |
|
|
Integration Commands |
|
|
Integration Targets |
|
|
Knowledge Bases |
|
|
Notes |
Notes are defined within resources. |
|
Queries |
|
|
Query Viewers |
|
|
Reports |
|
|
Report Templates |
|
|
Rules |
|
|
Saved Searches |
Created on the Command Center and available on the ArcSight Console as resources. |
|
Search Filters |
Created on the Command Center and available on the ArcSight Console as resources. |
|
Session Lists |
Definition only, but not list entries. Subscribers can override with their own entries. |
|
Trends |
Definition only, but not the events searched by the trends. |
|
Users |