Different tools might be required to migrate and deploy an IBM® Content Navigator application and its assets.
The following tables show migration and deployment information for IBM Content Navigator assets that are stored in object stores.
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: |
Dependencies |
Tip:
![]() ![]() |
Environment-specific data | ![]()
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.
![]() |
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: |
Dependencies |
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 |
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. |
Description | ![]() ![]() |
---|---|
Deployment Mechanism | FileNet Deployment Manager: |
Dependencies | ![]()
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.
![]() |
Environment-specific data | ![]()
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.
![]() |
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. |
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: |
Dependencies |
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 |
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. |
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.
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: |
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 |