Migrate Content from Core Services to Content Library

[#1]

Migrate Content from Core Services to Content Library

The customers who want to use Centralized Content Management, and if their content is already deployed, a migration process is required.

The following types of content can be migrated from Core Services:

• Application Rule

• Network Rule

• Log Device

• Live Feeds

• LUA Parser

Note:
- When the user upgrades a Decoder or Log Decoder from 11.x, 12.0 or 12.1 version to 12.1.1 or later version, a back up of all the content is created automatically. Backup file will be available on Core Services' host under the following path:
For Log Decoder - /var/netwitness/logdecoder/logdecoder_backupcontent_ccm.tar
For Network Decoder - /var/netwitness/decoder/decoder_backupcontent_ccm.tar
- When migrating content from two Decoders that have two different types of Custom or Live Base Parser associated with same Custom or Live Base Parser, both the Custom Parsers are added to Content Library. Th association inside the Policy will be with the most recently migrated Custom Parser.
- Within a migrated Policy, a Custom Parser will have only one Custom or Live Base Parser associated with it.
- Migrated content version will be in the Policy, if as part of migration, the Policy is auto created. If you remove this content, you cannot add the old version of the content back.

For steps on how to migrate content from Core Services to Content Library, see Migrate Content from Service under Manage Services.

                                                  Previous Page                                             Next Page