IBM FileNet P8, Version 5.2.1            

IBM Content Navigator assets

Different tools might be required to migrate and deploy an IBM® Content Navigator application and its assets.

The tools that you must use are determined by the tools that are used to create the assets and the storage method for the assets.
  • If your application includes assets that were created by using IBM Content Navigator tools but that are stored in an object store, this topic provides information about the migration and deployment of those assets.
  • If your application includes assets that were created by using other tools but can be processed by IBM Content Navigator, see the information for the tool that was used to create the asset. For example, entry templates that were defined in theWorkplace XT entry template designer, see Workplace XT assets.
  • If your application includes configuration information that is managed with IBM Content Navigator instead of FileNet® P8, you must use other tools for the migration and deployment of those assets. For more information, see Migrating assets for IBM Content Navigator in the online product documentation.

The following tables show migration and deployment information for IBM Content Navigator assets that are stored in object stores.

Entry templates

Table 1. Entry templates
Description An entry template that is defined in IBM Content Navigator V2.0.3 or later can be used to add or check in a document or create a folder. The user who designs the entry template determines what can be seen and done when an item is added or checked in.
Deployment Mechanism FileNet Deployment Manager:
  1. Create deployment data set
  2. Convert objects for import
  3. Analyze objects for import
  4. Import converted objects
Dependencies
  • The class definitions and property definitions of any document class that is referenced in the entry template.
  • The workflow that might be referenced by the entry template.
  • Any repository name or folder path that is referenced in the entry template.
  • Any security principals that are named in the entry template.
Tip: FileNet Deployment Manager does not recognize the preceding objects as associated objects of the entry template and therefore does not automatically include them in the export files. You must specifically add these objects to the export manifest or ensure that they are present in the destination environment before the entry template is used. In addition, the entry template (saved search) can be edited after it is imported to correct portions that might be invalid in relation to the destination environment. For example, a security principal that does not exist in the destination environment might need to be removed or a different user might need to be selected.
Environment-specific data See dependencies.

Saved searches

Table 2. Saved searches
Description Represents a search that is created and saved by using the IBM Content Navigator search view. Running a saved search displays a list of the repository objects that meet the search criteria.
Deployment Mechanism FileNet Deployment Manager:
  1. Create deployment data set
  2. Convert objects for import
  3. Analyze objects for import
  4. Import converted objects
Dependencies
  • Class definitions and property definitions of the objects that this search is used to locate
  • Any custom properties, specific classes, or folders that this search queries
  • Object stores that are referenced by the Search in portion of the search criteria
Tip: FileNet Deployment Manager does not recognize the preceding objects as associated objects of the saved search. Therefore, it does not automatically include these objects in the export files. You must specifically add these objects to the export manifest or ensure that they are present in the destination environment before the search is used. Alternatively, the search can be edited after it is imported to correct portions that might be invalid relative to the destination environment.
Environment-specific data See dependencies.
Notes Searches can be saved in various locations. Be sure to note the location of a saved search so that you can later add it to an export manifest.
Start of change

Social Collaboration Notification Extensions for Content Navigator

Table 3. Social Collaboration Notification Extensions for Content Navigator
Description

For releases of IBM Content Navigator that support the notifications feature, the Social Collaboration Notification Extensions for Content Navigator add-on extensions define classes and properties for an event notification system.

You might need to migrate instances of the following class types if you customized the instances created by IBM Content Navigator or if you stored additional instances. For example, to support localization of an email template, you might create an additional, translated instance of that template.
  • Notification Email Template (ClbNotificationEmailTemplate)
  • Notification Email Template Header (ClbNotificationEmailTemplateHeader)
  • Notification Email Template Footer (ClbNotificationEmailTemplateFooter)
  • Notification Email Template Body (ClbNotificationEmailTemplateBody)

When you use FileNet Deployment Manager to add assets to an export manifest, you can find instances of these class types by viewing the EMS Email Template list of the Uncontained objects node.

Deployment Mechanism FileNet Deployment Manager:
  1. Create deployment data set
  2. Convert objects for import
  3. Analyze objects for import
  4. Import converted objects
Dependencies

The Social Collaboration Notification Extensions for Content Navigator add-on must be installed into the destination object store. For more information about add-on extension assets, see AddOn. For more information about working with these add-on extensions, see Social Collaboration Notification Extensions for Content Navigator.

Environment-specific data None
End of change


Last updated: October 2015
p8pdb017.htm

© Copyright IBM Corporation 2015.