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, for entry templates that were defined in the Workplace 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.
  • Start of changeAny folder path that is referenced in the entry template.End of change
Tip: Start of changeFileNet Deployment Manager recognizes the preceding objects as associated objects of the entry template. Therefore, they can be included indirectly when exporting the entry template by selecting the appropriate include options in the export manifest. Alternatively, you can either directly add these objects to the export manifest or use other means to ensure that these objects are present in the destination environment before the entry template is used. Otherwise, you must edit the entry template after it is imported to correct any references to these objects that are invalid in the destination environment.End of change
Environment-specific data Start of change
  • Any object stores that are referenced in the entry template.
  • Any security principals that are named in the entry template.
Tip: FileNet Deployment Manager recognizes the preceding objects as referenced objects of the entry template and converts these references in the export files by using the appropriate data maps.
End of change
Start of change

Folder preferences

Table 2. Folder preferences
Description A folder preference that is defined in IBM Content Navigator V2.0.3 or later can be used to associate a folder with an entry template. The entry template is invoked when a user attempts to add documents or subfolders to the associated folder.
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
  • Any entry template that is referenced by version series ID in the folder preference.
Tip: FileNet Deployment Manager does not recognize the preceding object as an associated object of the folder preference and therefore it does not automatically add it in the export files. You must specifically add this object to the export manifest or ensure that it is present in the destination environment before the folder preference is used.
Environment-specific data
  • Any object stores that are referenced in the folder preference.
  • Any security principals that are named in the folder preference.
Tip: FileNet Deployment Manager recognizes the preceding objects as referenced objects of the folder preference and therefore converts these references in the export files using the appropriate data maps.
Notes Folder preferences are a type of annotation and are not visible when you are browsing to add assets to an export manifest. To export them, you must add the folder for which the folder preference is defined and select the Include annotations on documents, folders, and custom objects option for the folder.
End of change

Saved searches

Table 3. Saved searches
Description Start of changeA saved search 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.End of change
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 Start of change
  • Folders that this search queries
Tip: FileNet Deployment Manager recognizes the preceding objects as associated objects of the saved search. Therefore, they can be included indirectly when exporting the saved search by selecting the appropriate include options in the export manifest. Alternatively, you can either directly add these objects to the export manifest or use other means to ensure that these objects are present in the destination environment before the saved search is used. Otherwise, you must edit the saved search after it is imported to correct any references to these objects that are invalid in the destination environment.
End of change
Environment-specific data Start of change
  • Object stores that are referenced by the Search in portion of the search criteria
Tip: FileNet Deployment Manager recognizes the preceding objects as referenced objects of the saved search. Therefore, it converts these references in the export files by using the appropriate data maps.
End of change
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

Teamspaces

Table 4. Teamspaces
Description A teamspace is a folder with associated properties and content that is created and saved by using IBM Content Navigator.
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
  • Any entry templates associated with the teamspace
  • Any saved searches associated with the teamspace
  • Any document for a folder row associated with the teamspace
  • Any class definition associated with the teamspace
Tip: FileNet Deployment Manager recognizes the preceding objects as associated objects of the teamspace. Therefore, you have the option to include them in the export files. You can also specifically add these objects to the export manifest or ensure that they are present in the destination environment before the teamspace is used.

recognizes the preceding objects as associated objects of the teamspace. Therefore, they can be included indirectly when exporting the teamspace by selecting the appropriate include options in the export manifest. Alternatively, you can either directly add these objects to the export manifest or use other means to ensure that these objects are present in the destination environment before the teamspace is used. Otherwise, you must edit the teamspace after it is imported to correct any references to these objects that are invalid in the destination environment.

Environment-specific data
  • Any object store that is referenced in the teamspace properties
  • Any security principals that are named in the teamspace properties
Tip: FileNet Deployment Manager recognizes the preceding objects as referenced objects of the teamspace and therefore converts these references in the export files by using the appropriate data maps.
Notes Reviews and recovery bins cannot be deployed, so any of these objects associated with the teamspace are not included when deploying a teamspace. Subfolders and assets filed in folders can be included when you are adding assets to an export manifest, during the step to specify the include options of an asset.
End of change
Start of change

Social Collaboration Notification Extensions for Content Navigator

Table 5. 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: March 2016
p8pdb017.htm

© Copyright IBM Corporation 2016.