Using IDM with IBM DB2 Content Manager

When using IDM with IBM DB2 Content Manager, there are other limitations to the solution.

The limitations are (bold indicates changes since last version):

  • The Control Center Configuration Exporter does not support Document Types.
  • The Control Center Configuration Importer does not support Document Types and only values of an existing value set.
  • File names are now automatically stored as properties, but cannot be used in searches.
  • Cache synchronization available in IDM Control Center may require restarting of the IBM DB2 Content Manager application in IBM WebSphere.
  • Value sets cannot be created in the IDM Control Center, but Value Set values can be edited.
  • Document Types are not available in the IDM Control Center.
  • Trailing spaces will not make an attribute’s value unique.
  • Not able to sort by “Checked out date,” “Checked out by,” or “Document Type” in the client.
  • Attribute level permissions are not available.
  • Discard Checkout does not revert a document to its previous version; it only checks in the document and unlocks it for other users.
  • To enable Document Templates, the customer should manually add the MDS_TemplateName and MDS_TemplateDetails attributes to the Document Types that they want to enable for Document Template usage.
  • The Delete BOD is not supported.
  • Only the Delete action is supported. A Retention_Policy_User user must be available. This user name cannot be configured.
  • The new user interface is currently lacking support for SharePoint and IBM Content Manager backend systems. To run IDM with IBM Content Manager or SharePoint backend systems, the client must be switched over to compatibility mode (Look-and-feel before version 12.0.20):
    1. Enable developer options in the Grid by entering _dev in the top right corner search window. Then click Enable. This makes any properties that are normally hidden visible for the IDM application.
    2. Navigate to the IDM application properties: Advanced > Feature Toggles > Release -feature toggles.
    3. Click the check box for the R_WEB_OLD_CLIENT property to enable it.