IBM DB2 Document Manager Version 8.4 Fix Pack 2 (Build 121) Readme

Content

This readme contains the following sections:

1. Problems fixed in this release
2. Known problems
3. Quality improvements
4. Supplemental installation information
5. Product documentation and support

Tip: The information contained in this readme is also available in the Enterprise Content Management Version 8.4 Information Center.

1. Problems fixed in this release

This section lists problems that were fixed after the initial release of Version 8.4 Fix Pack 1 of DB2 Document Manager.

If a link in the following table does not work, the detailed information for that APAR is not yet available from the Support page.

Table 1. Problems fixed for Version 8.4 Fix Pack 2 (Build 121) of DB2 Document Manager

APAR	Brief problem description
IO08029	Lifecycle Manager operations were applied to an incorrect document version Lifecycle Manager operations acted on the latest version of the document at the time the request was queued, instead of the version of the document at the time of the operation. Since the fix of this APAR, the operation always applies to the latest version of the document at the time of request processing. As a result of this change, the version numbers of entries that are displayed in the activity and history logs in the Lifecycle Map dialog window might be out of order.
IO08215	CVL list was truncated when the search was saved When a CVL list that contained a large number of values was selected in the search criteria, the size of the CVL was too long and was truncated.
IO08285	Default Search operator was incorrect in German edition In the Document Content window, the default search operator was set to "oder" (English: or) instead of "und" (English: and).
IO08307	Dates of notification e-mails were shown in time stamp format Notifications that were sent that contained date values, but not time values, resulted in e-mails that showed the date with additional blank time stamp formatting. Example: 2008-01-14-00.00.00.000000.
IO08401	Adding Visio files sometimes caused DdmExtr.exe process to stop DB2 Document Manager interpreted some Visio files incorrectly as another type of file, causing the DdmExtr.exe process to stop functioning when those files were added.
IO08441	Rendition Services could not de-encrypt the user ID and password For customers who were using the user defined rendition type, the Rendition Services were unable to use the token to de-encrypt the user ID and password from the INI file.
IO08449	Power search on the Library tab produced inconsistent results When the "Search all item types" check box was not selected, and one or more item types were added to the search list, the search incorrectly filtered out semantic types Document (1), Folder (2) and GPSSmartFolder. When the "Search all item types" check box was selected, the search correctly included them.
IO08464	User could not use “checked out” or “checked out by” filters in a Process Rule search Search properties for the Process Rule component of Designer did not provide filtering by “checked out” or “checked out by” status.
IO08481	Selecting a new group from a scrolling list in the Document Manager Desktop sometimes resulted in a change to an incorrect group When a large number of selections exceeded the size of the list window, resulting in a scrolling list, selecting a group from the list sometimes resulted in a change to an incorrect group.
IO08505	Access to Component Manager command from an XML component could not be restricted All users were able to access the Component Manager command by right-clicking on an XML component, and access restrictions to the command could not be configured.
IO08545	The DB2 Information Integrator for Content encryption toolkit was loading slowly The DB2 Information Integrator for Content encryption tool kit load took too long to load.
IO08552	Desktop menu command executable plug-ins did not get an INI file During processing, Document Manager plug-in files that had the executable radio button selected were not expanded to the temporary control INI file.
IO08570	Selecting an executable Desktop menu command plug-in caused a command prompt to display When a user selected an executable Desktop menu command plug-in, and the plug-in was a console application (not a Windows application), an unnecessary command window displayed. To prevent this, users can now select the option "Do not display command window."
IO08597	In Document Manager, the Add dialog window always indexed plain text documents In Document Manager 8.3 Fix Pack 8 and earlier, the Add dialog window always submitted plain text documents (.txt files) for indexing, even when users specified “no indexing” by de-selecting the Search Index option in the Add dialog window.
IO08600	After upgrading to FileNet Content Services 5.4 and Document Manager 8.3 Fix Pack 6, items in the Lifecycle Services request processing failed Lifecycle Services request processing would fail with the following error: [DDM11642E] ERROR [-2147157502]: Attempting to lock request.
IO08608	The Day value for the Cache Configuration Purge Schedule could not be set correctly Users could not set the Day value in the Purge Schedule window of the Cache Configuration correctly. For example, after a user changed the Day value from Sunday to another day, then clicked OK to modify the Cache Configuration, the value reverted back to Sunday.
IO08661	The Lifecycle Manager activity log lost some update versions when multiple updates were performed within a short time When several update library item actions were performed before the processing of the Lifecycle queue, earlier updates were lost and only the last update was logged in the Lifecycle Manager activity log.
IO08752	DB2 Document Manager Desktop removed Microsoft Office files from client computer when check-in failed When a user tried to check in a Microsoft Office file that was already checked in, the Document Manager Desktop removed the file from the user’s desktop instead of posting a message that the file was already checked in.
IO08821	The Rendition Services stopped while waiting for AutoCAD 2007 jobs to complete The DB2 Document Manager Rendition Services did not receive notification that AutoCAD 2007 jobs had completed, which stopped the rendition service indefinitely.
IO08832	The contents of the Recent Documents folder were cleared when the view was changed In the Recent Documents folder, all items that were listed in the Desktop view pane were cleared whenever the user changed the view.
IO08853	Jobs could be deleted from the job queue even if they were still processing If a deleted job was still processing, the automation service sometimes stopped until the processes that were associated with the deleted job were cleared from the process queue. Now, a job cannot be deleted if any of its associated processes are still pending.
IO08855	Role checking did not occur in the Desktop folder navigation pane If users selected controlled-class folders in the Desktop folder navigation pane, role checking did not occur, so access control was not enforced. Users whose roles restricted access were able to open the folders from the folder navigation pane.
IO08862	Labels and control boxes within a dialog window sometimes were not displayed When users changed classes within a dialog window, the dialog window's control boxes and control box labels sometimes were no longer displayed correctly.
IO08912	Attempts to check out a compound document resulted in an error when users did not have access to the child document When users attempted to check out a compound document for which they had no access to the child document, DB2 Document Manager displayed a blank dialog window. Clicking Continue produced a General Internal Error.
IO08919	Default values for library properties were lost when a new item template was used in a different locale Because new item templates internally used display names instead of the real names of properties when default values were specified, the default values for library properties were lost when a new item template was used in a different locale from the one in which the template was defined.
IO08975	Creating XML component links failed when users specified the XML component type When users specified an XML component type during XML component link creation, the action failed. The users received an error message and the links were not created.
IO09030	Property exchanges of date or Boolean values were not enabled for Microsoft Office applications Exchanging date or Boolean property values from the applications to Document Manager and Boolean property values from DB2 Document Manager to the applications was not enabled for Microsoft Office applications.
IO09035	Failed error notifications were not reprocessed If an error notification failed, DB2 Document Manager did not mark the failed notification for reprocessing and did not resend the notification.
IO09037	DB2 Document Manager did not release allocated virtual memory when it was integrated with Microsoft Outlook Each time a Microsoft Outlook process occurred, such as saving an e-mail, DB2 Document Manager allocated virtual memory but did not release it when the process completed. Memory usage increased until performance was impacted.
IO09057	The Add dialog windows did not recognize range settings DB2 Document Manager accepted values that did not conform to specified ranges for the Add dialog window fields. For example, if a range was set as [0-2] and a user entered a character that was out of range, such as 4, the system accepted the value and the document was added with no error.
IO09112	Deleting a class whose name is the prefix of other class names caused the configuration links of the other classes to be deleted also Within the scope of a single item type (that is, not spanning item types), deleting a class whose name is the prefix of other class names caused the configuration links of the other classes to be deleted. Example: For the following classes, Class X Class XY Deleting class X would also delete all of the configuration links under class XY.
IO09154	Existing search result lists were not updated during a view or copy action after a revised document version was checked in When a document was viewed or copied from a list of search results that was obtained before a newer version of the document was checked in, the Desktop retrieved the older version instead of the latest version. With the fix of this APAR, the latest version is retrieved when a document is viewed or copied from old search results.
IO09187	Security actions on the state failed if they were configured in the Security dialog window by using display names When display names were used to configure security instead of the unique user ID, security actions failed. With the fix of this APAR, the use of display names works properly in the security action configuration.
IO09240	The padlock icon was displayed in the Version History dialog window The purple padlock icon, which indicates that a document is declared as a record, was sometimes displayed in the Version History dialog window.
IO09265	Decimal values were not sorted correctly in the Desktop view When users listed decimal values in the Desktop view, and then clicked a column to sort the view, the numbers were not sorted correctly. For example, the value 100.00 occurred before the value 90.00. The Desktop now sorts decimal values in the correct numerical order.
IO09266	Compound documents' links were deleted during failed document delete actions When a user without the ItemDelete privilege attempted to delete a compound document, the deletion attempt appropriately failed and the document was not deleted. However, the compound document (cpdoc) links and icons were deleted from the document. With the fix of this APAR, DB2 Document Manager checks for the ItemDelete privilege before it begins to process a deletion request. If the user does not have ItemDelete privileges, the links and icons are not deleted, and the user receives a General Internal Error.
IO09276	The Add dialog window displayed an item class to a user who did not have access authority to add items to the class If a user specified a default item class in user preferences and then the user was removed from the role that had Add access to the class, the class was still displayed in the user's Add dialog window.
IO09304	DB2 Document Manager returned an incorrect error message In certain situations, adding a document returned a default error message to the user when a custom-defined message was expected. With the fix of this APAR, the correct error message is returned.
IO09363	Search template default values did not display correctly in the Desktop When a user changed from one search template to another after an initial search, the default values that were set in the Designer were no longer displayed. Instead, the attribute fields in the search template were populated with the word “ignore.”
IO09369	In the Designer, inactive options were displayed in the drop-down menu that was used for creating an Action dialog window Administrators could configure Transition dialog windows for two features that had no situational functionality and did not work.
IO09471	Custom controls did not recognize the setting height > x1 When a dialog window was configured with the control type set to Custom and the height attribute set to accept multiple rows of text, users could not enter more than one line of text.
IO09871	Entries were repeated in the activity logs Under certain circumstances, requests in the life cycle queue caused errors that were processed repeatedly, causing multiple entries in the activity logs.
IO10006	Cache files were deleted for class names that began with special characters Cache files were deleted for class names that began with special characters. The class names were not displayed in the Add dialog window's drop-down menu.
IO10038	Security actions failed when Name field values exceeded 256 characters The Name field of the Security Actions Definitions window supported only 256 characters. With the fix of this APAR, the number of characters that is supported is 2048. Important: If the number of characters in the Name field exceeds 2048, the security action will fail.

2. Known Problems

This section describes the known problems in DB2 Document Manager Version 8.4 Fix Pack 2 (Build 121).

2.1 A generic error message is displayed when a user without the itemdelete privilege attempts to delete a record

For DB2 Document Manager systems that are integrated with IBM Records Manager, an incorrect error message is displayed when a user without the itemdelete privilege attempts to delete a document that is declared as a record.

Incorrect message:
A general internal error occurred.

Correction:
Document cannot be deleted. User does not have the itemdelete privilege.

Note: Before DB2 Document Manager 8.4 Fix Pack 2, the following message was displayed for this error:

Document cannot be deleted. Version XXX of the document has been declared as a record.


2.2 The cursor position cannot be controlled in a Microsoft Outlook item

The Microsoft Outlook API that DB2 Document Manager uses to implement Outlook integration does not support control of the cursor position for placement of attachments in an Outlook item.

2.3 Invalid class attribute causes DB2 Document Manager operation to fail

If you specify a value that is not valid for a document's class attribute in the Power Modify dialog window, any DB2 Document Manager operation that needs to read the class configuration will fail. The document might become unusable. If this happens, use the Power Modify dialog window to reset the class value.

2.4 Long file names truncated

When a user adds a document to the repository, DB2 Document Manager removes a portion of the document file name that is longer than a certain number of characters. The maximum number of characters varies from 166 to 214, depending on the operating system of the DB2 Document Manager server and the connection protocol between the DB2 Document Manager client and server.

2.5 Complex search queries with a large number of CVL values can result in an error

When users perform complex search queries, DB2 Document Manager sometimes returns a General Internal Error. This occurs only in some circumstances when a single query contains a very large number of conditions. For example, if users combine many OR conditions and LIKE operators in a single search query, the action can result in low search performance or an error.

For recommendations on how to perform effective search queries and avoid the error, see the technote IBM DB2 Content Manager Query Performance Guide.

2.6 Rendition Services sometimes fails for certain applications

Some applications can be started by using the system account. However, some applications require a Windows user account to start the application. Therefore, to ensure that Rendition Services works properly, the application that processes the rendition must be able to run the print command by using the appropriate method:

• By using the system account if Rendition Services is set up to run by using the system account
• By using the Windows user account if Rendition Services is set up to run using the Windows user account

3. Quality Improvements

This section contains information about quality improvements in this release.

3.1 Compliance with Common Criteria assurance level EAL3

Common Criteria (CC) evaluated products are evaluated in accordance with Common Criteria, an internationally recognized ISO standard (ISO 15408) for the security evaluation of IT products and systems.

With the release of Fix Pack 1, DB2 Document Manager Version 8.4 was certified to CC Evaluation Assurance Level 3 (EAL3). Newer versions of the product will continue to be evaluated at the same or higher EALs as required.

The Documentation Addendum for Common Criteria contains security information that supersedes the information that is documented in the IBM DB2 Document Manager Information Center, the IBM DB2 Document Manager 8.4 System Administration Guide, and the IBM DB2 Document Manager 8.4 Planning and Installation Guide.

The addendum is available at the following Web page:
IBM DB2 Document Manager: Documentation Addendum for Common Criteria

3.2 Application integration: Support for newer versions of integrated applications

The DB2 Document Manager Desktop integrates with newer versions of several applications, including:

• Adobe Acrobat (Distiller) 9
• Autodesk AutoCAD 2009
• Cimmetry AutoVue client 19.2C2

Note: Adobe Acrobat Distiller is supported for PDF rendition only, not for DB2 Document Manager client integration.

3.3 Federal Desktop Core Configuration (FDCC) Compliance

DB2 Document Manager offers compliance with the Federal Desktop Core Configuration (FDCC) for Windows XP SP2 and Windows Vista Enterprise.

Important: To use the integration between Document Manager Desktop and Microsoft Office applications under FDCC, you must undertake specific installation procedures, which are included in the technote How to install IBM DB2 Document Manager Desktop on an FDCC-compliant Microsoft Vista or Windows XP system

3.4 Application integration: Cimmetry AutoVue support for MicroStation V8 XM

Cimmetry AutoVue has supported the MicroStation V8 XM format since Version 19.1 Service Pack 2. DB2 Document Manager Version 8.3 Fix Pack 4 was updated to include support for Cimmetry AutoVue Version 19.1 Service Pack 2, so DB2 Document Manager has supported compound document detection in MicroStation V8 XM files since that release.

3.5 States: New option controls whether security actions are applied after potential attribute value changes

In previous releases, Lifecycle Services applied a state's security actions in the following situations:

• When a document transitioned to the state
• When processing a Modify properties trigger, if any of the security action definitions were based on a library attribute
• When processing a Checkin trigger, if any of the security action definitions were based on a library attribute

However, not all customers wanted security actions to be applied in the latter two cases, even those that defined property-based security actions. Some customers wanted Lifecycle Services to apply security actions only when a document entered a new state and they wanted Desktop users to be able to set a document's security without Lifecycle Services subsequently resetting the security when it processed Checkin and Modify properties triggers.

Beginning in this release, you can control whether Lifecycle Services applies security actions when it processes Modify properties and Checkin triggers. Use the new option on the Security page of the New or Modify State Configuration window: If property-based security actions exist, apply all state security actions when processing Checkin or Modify properties triggers.

• Leave this option clear to have Lifecycle Services apply all security actions only when a document transitions to the state.
  
• Select this option to have Lifecycle Services apply all security actions after a user checks in a document or modifies the properties of a document.
  
  Important: Lifecycle Services applies the security actions only if one or more of the security action definitions are based on a library attribute. If none of the security action definitions are based on a library attribute, Lifecycle Services does not apply the security actions when processing Checkin or Modify properties triggers.

Action required for existing customers: If you want the state security behavior of your system to continue to operate as it has in past releases, select the new option on the Security page of the New or Modify State Configuration window.

3.6 Custom dialog controls: Data exchange file format

When it writes item property values to the INI file, DB2 Document Manager modifies the values in the following ways:

• Each UNIX or DOS-style line return is replaced with "\n" to prevent the property value from splitting across multiple lines.

For example, if the item property value is an address with multiple lines such as:

350 5th Ave.
New York, NY 10118

the value that is written to the INI file is:

PropertyValue_Y=350 5th St.\nNewYork, NY 10118

• Each backslash ("\") character in the item property value is escaped with an additional backslash character to prevent it from being mistaken for part of a line return ("\n") character.

For example, if the item property value is a path such as:

C:\projects\new\designs\

the value that is written to the INI file is:

PropertyValue_Y=C:\\projects\\new\\designs\\

Desktop action plug-ins must undo these modifications before they display item property values to users. When plug-ins save user-modified values to the INI file, they must convert the values back to the expected INI format. Therefore, each line return that is replaced with ''\n'' and each backslash character that is replaced with "\\" must be converted back to the expected INI format.

After the plug-in finishes, and after the property values are read from the INI file, DB2 Document Manager reverses the INI modifications in memory. As a result of the line return modifications and subsequent reversal, UNIX-style line returns are converted to DOS-style line returns.

3.7 Recommendation: Limit ACLs to 40 pairs of user/group and privilege sets

To take advantage of folder caching and avoid performance delays that are caused by unnecessary library retrievals, administrators should configure Access Control Lists (ACLs) to include no more than 40 pairs of user/group and privilege sets. Do so using the built-in Content Manager group ICMPUBLC or by creating super-groups that contain other groups.

3.8 DB2 Document Manager viewer determines printing access through user privileges

The DB2 Document Manager viewer determines whether a user can print a document by examining the user privileges, not through an ACL (as Content Manager does). Note also that a user who is denied printing privileges might still be able to print by opening a document in another application.

3.9 Searching: Re-executing a dynamic search

Users can now re-execute a dynamic search by positioning the cursor over the dynamic search folder in the folder navigation pane of the Desktop and selecting the Refresh command from the right-click menu.

Important: This function assumes that you added the Refresh command to the menu that you selected from the Folder objects Right mouse list on the Menu Interface page of the New or Modify Desktop Template Configuration window.

4. Supplemental installation information

Read this section before you install or upgrade DB2 Document Manager.

4.1 Upgrading to DB2 Document Manager Version 8.4 Fix Pack 2

DB2 Document Manager Version 8.4 Fix Pack 2 requires that a publicly available version of one of the following releases, or a custom test fix for one of these releases, is installed before you upgrade to Version 8.4 Fix Pack 2:

• DB2 Document Manager Version 8.4 Fix Pack 1
• DB2 Document Manager Version 8.4
• DB2 Document Manager Version 8.3 Fix Pack 10
• DB2 Document Manager Version 8.3 Fix Pack 9
• DB2 Document Manager Version 8.3 Fix Pack 8
• DB2 Document Manager Version 8.3 Fix Pack 7
• DB2 Document Manager Version 8.3 Fix Pack 6
• DB2 Document Manager Version 8.3 Fix Pack 5
• DB2 Document Manager Version 8.3 Fix Pack 4
• DB2 Document Manager Version 8.3 Fix Pack 3
• DB2 Document Manager Version 8.3 Fix Pack 2
• DB2 Document Manager Version 8.3 Fix Pack 1
• DB2 Document Manager Version 8.3

4.2 Hardware and software requirements

This section provides hardware and software requirements for DB2 Document Manager that supersede the information in Chapter 1 of Planning and Installing DB2 Document Manager.

Hardware and software requirements for IBM DB2 Document Manager Version 8.4 Fix Pack 2 contains a complete list of software requirements for this fix pack.

4.2.1 DB2 Content Manager

DB2 Content Manager systems only

DB2 Document Manager Version 8.4 Fix Pack 2 requires DB2 Content Manager Version 8.3 Fix Pack 6a or later.

4.3 Microsoft Windows Server 2003 and Windows XP update for Windows Communication Foundation

Microsoft Support provides an update that adds support for the WS-AtomicTransaction protocol to MSDTC and support for the Windows Communication Foundation (WCF) COM+ Integration feature.

The update is free and available now from Microsoft Support (KB article 912817). For more information about this update, see the Microsoft Web site at: http://www.microsoft.com/downloads/details.aspx?familyid=86B93C6D-0174-4E25-9E5D-D949DC92D7E8&displaylang=en

Important: This Windows update is a prerequisite for DB2 Document Manager Version 8.3 Fix Pack 5 and later releases and is a prerequisite for the fix to APAR IO06225a.

Microsoft Windows Server 2003 SP2 systems: This update is not needed on Microsoft Windows Server 2003 SP2 systems.

4.4 Microsoft Windows 2000 Post-Service Pack 4 COM+ 1.0 Hotfix Rollup Package 33

Microsoft Support provides a hotfix that fixes a problem that causes DB2 Document Manager to stop responding. When this problem occurs, an event is not logged in Event Viewer. The cause is an access violation that occurs in Comsvcs.dll when you are running a COM+ application on a Microsoft Windows 2000-based computer.

A hotfix for this problem is free and available now from Microsoft Support (KB article 892349). For more information about this problem, see the Microsoft Web page at: http://support.microsoft.com/kb/892349/.

The hotfix is included in Microsoft Windows 2000 Post-Service Pack 4 COM+ 1.0 Hotfix Package 33. For more information about this hotfix rollup package, see the Microsoft Web page at: http://support.microsoft.com/kb/896720/.

The Hotfix Rollup Package 33 contains all of the fixes that were released in the previous Windows 2000 COM+ 1.0 hotfix rollup packages.

Important: This hotfix is a prerequisite for DB2 Document Manager Version 8.3 Fix Pack 5 and later releases, and a prerequisite for the fix to APAR IO06225a.

4.5 IProcessInitializer Interface does not register with Microsoft COM+ Rollups

For Microsoft Windows 2000 systems only: The IProcessInitializer Interface does not register with Microsoft COM+ Rollups

To read about this problem and its resolution, which should be performed on servers that already have Rollup Package 33, see the Microsoft Web site at: http://support.microsoft.com/kb/319776.

4.6 Autodesk AutoCAD 2007 Service Pack 2

Autodesk provides an AutoCAD 2007 service pack that includes a hotfix for problems that can occur when closing, saving, or plotting drawings. For complete information and to download the service pack, see the following AutoCAD Services and Support Web pages:

AutoCAD 2007 Service Pack 2:

http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=9444984&linkID=9240618

AutoCAD 2007 Hotfix:

http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=8185238&linkID=9240618

5. Product documentation and support

This section provides links and updates to the product documentation and support.

5.1 Accessing the documentation

You can access the DB2 Document Manager product documentation at the following Web page:
http://www.ibm.com/software/data/cm/docmgr/support.html

5.2 Documentation corrections and clarifications

This section contains corrections and clarifications for information in the DB2 Document Manager product documentation.

5.2.1 Planning and Installation Guide

This section describes documentation corrections and clarifications for information in the DB2 Document Manager Planning and Installation Guide.

5.2.1.1 Desktop and Designer installable on a single system or multiple systems
Source:
Chapter 1: Planning for DB2 Document Manager
System components overview
Configuration examples
Suggested configuration scenarios

Error:
The first bullet mistakenly implies that you cannot run both the Desktop and the Designer on the same client system. It currently reads:
“Clients, running either the DB2 Document Manager Desktop end-user application or the DB2 Document Manager Designer system administration application.”
You can install DB2 Document Manager Desktop and Designer on the same system or separate systems. In particular, the Configure command works under both configurations. A Desktop user can use the Configure command to start the Designer on a remote system.

Correction:
The first bullet should read:
Clients, running the DB2 Document Manager Desktop end-user application, the DB2 Document Manager Designer system administration application, or both the Desktop and Designer applications

5.2.1.2 Notification Services not a base component
Source:
Chapter 1: Planning for DB2 Document Manager
System components overview
Configuration examples
Suggested configuration scenarios

Error:
Notification Services is incorrectly identified as a base component of the server.

Correction:
The second bullet should read:

• DB2 Document Manager server, which includes the following base components:
• Cache Manager
• Lifecycle Services

5.2.2 System Administration Guide

This section describes documentation corrections and clarifications for information in the DB2 Document Manager System Administration Guide.

5.2.2.1 Common Criteria certification details

The Documentation Addendum for Common Criteria contains security information that supersedes the information that is documented in the IBM DB2 Document Manager Information Center, the IBM DB2 Document Manager 8.4 System Administration Guide, and the IBM DB2 Document Manager 8.4 Planning and Installation Guide.

The addendum is available at the following Web page:
IBM DB2 Document Manager: Documentation Addendum for Common Criteria

5.2.2.2 DB2 Document Manager does not support items that have more than one base part
Source:
Chapter 5: Configuring item types and classes
Item Types Overview

Clarification:
The following limitation should be included:
DB2 Document Manager does not support items that have more than one base part. For example, an item that contains both the ICMBASE and ICMBASETEXT base parts is not supported.

5.2.2.3 MAPI Notification limitations with Microsoft Outlook
Source:
Chapter 2: Getting Started
Configuring DB2 Document Manager to send notifications to your e-mail account

Chapter 6: Configuring Library Elements
Adding a notification configuration for Microsoft e-mail

Clarification:
The following limitations should be included:

• MAPI Notification only works with Outlook Express and Outlook 2000 SR-1a. Outlook 2000 SP2 and SP3 adds additional security features that prevents the DB2 Document Manager notification service from connecting to Outlook.

• MAPI Notification only works when Outlook 2000 is configured for Internet Mail Only mode. If it is configured for either Corporate or Workgroup mode, then the Notification service will not be able to log into MAPI.

5.2.2.4 Group name not applicable to Desktop login
Source:
Appendix G: End-user quick reference guide
Starting and logging in to the Desktop
How to start and log in to the Desktop

Error:
Step 4 incorrectly mentions the group name as potentially applicable when you are logging in.

Correction:
Step 4 should read:
4. Type your user name and password, then click Log in.

5.2.2.5 Configuring a view

Source
Chapter 3. Designing the Desktop
Views overview
Configuring a view

Error
Steps 7 and 8 contain inaccurate information about your ability to specify 0 (zero) if you do not want to limit the number of items that are returned. 0 (zero) is not a valid value for the lists Maximum # of items returned and Return documents in increments of.

Correction
Steps 7 and 8 should read:

7. From the Maximum # of items returned list, select the number of documents to return from DB2 Document Manager searches. (You can select a number up to 10,000 or type in a number up to 99,999.) If the search results exceed the number you specified, the search returns the last set of items.

8. From the Return documents in increments of list, select the number of documents to return. If the search result exceeds the number of documents you specified, the return increment control allows the user to specify a higher number of documents to display.

5.2.2.6 Determining a sequence of revisions

Source
Chapter 7. Configuring a life cycle
Revisioning

Clarification
Revision numbers are unique but not necessarily sequential because the application reuses the revision numbers of deleted revisions. To identify the most recent revision, find the latest modified date and time. Do not use revision numbers to determine the sequence.


5.2.2.7 Rendition Services overview

Source
Chapter 10. Configuring Rendition Services
Rendition Services overview

Clarification
This section is missing the following important information about a Microsoft Outlook limitation.

Microsoft Outlook limitation: Microsoft Outlook does not support automated printing of e-mail messages that are in HTML format. This means that an attempt by a user to create a rendition of an HTML-formatted e-mail message will fail.

Recommendation: If your users need to print HTML-formatted e-mail messages, they can use an Outlook MSG file viewer that supports HTML e-mail messages. One example is the Priasoft MSG File Viewer and Assessor. Be aware that to launch the MSG viewer when Rendition Services attempts to create a rendition of an HTML-formatted e-mail message, the viewer must either register a print handler in the Windows registry or support command line arguments and you must add the required registry settings manually.


5.2.2.8 Creating a PDF rendition configuration

Source
Chapter 10. Configuring Rendition Services
Creating rendition configurations
How to create a rendition configuration (step 11 a 5 b)

Clarification
Step 11 a 5 b should read:

Select the If possible, print using associated application option to enable Rendition Services to attempt to convert the rendition source file to PostScript with its native application. If the native application is not present on the server where Rendition Services is running, the default specified application is used.

Requirement: Whenever a Windows application is opened for the first time by a Windows user ID, certain windows open, prompting for user input. These windows must be suppressed from opening each time that the application is launched. Any other automatic windows must also be disabled. For any Windows service, Rendition Services must be able to run unattended. If a window is presented that requires a user to acknowledge the window, Rendition Services cannot run.

Recommendation: When you are first setting up the configurations for Rendition Services, configure Rendition Services to run with the system account and interact with the Desktop. This provides a certain measure of visual feedback in setting up and troubleshooting the configuration. After you complete your testing, assign a Windows user ID to Rendition Services. Microsoft Outlook is an exception to this recommendation.

• For Microsoft Outlook 2000 and Microsoft Outlook 2002 sites, start and run an instance of Outlook on the server where Rendition Services is running. Configure Rendition Services to run with the system account and interact with the Desktop.

• For Microsoft Outlook 2003 sites, do not start and run an instance of Outlook on the server where Rendition Services is running. Rendition Services starts Microsoft Outlook when it needs it. Configure Rendition Services to run with a Windows user account (not the system account).

5.2.2.9 [ItemData_X] section

Source
Appendix E. Custom dialog controls
Data exchange file
[ItemData_X] section

Clarification
This section is missing information about the PropertyMaxBufferSize_Y entry. The description for this entry should read:

Entry

Description

PropertyMaxBufferSize_Y

Maximum buffer size that is allowed for the library property that is specified by PropertyLabel_Y (where both PropertyLabel_Y and PropertyMaxBufferSize_Y have the same value for Y). The maximum buffer size includes space for an end-of-line character (\n). This means that the real buffer size is PropertyMaxBufferSize - 1. For example, if a property of type character has a PropertyMaxBufferSize of 25, you can store up to 24 characters in that property. This is true for all property types that DB2 Document Manager supports. DB2 Document Manager retrieves this value from the repository. The plug-in should not set this value.

This section is also missing information about the possible data types and the expected format of the data when you are setting a value from a plug-in (by using the entry PropertyUpdateValue_Y).

Data formats

BLOB
DB2 Document Manager does not support properties of data type BLOB.

Character
For properties of data type Character, the type and length are defined in the General section of the Modify Library Property Configuration window.

Example: If the maximum length for properties of data type Character is 254 and a plug-in provides a value that is longer than 254 characters, the value is truncated.

CLOB
DB2 Document Manager does not support properties of data type CLOB.

Date
For properties of data type Date, the value must be in the following format: yyyy-mm-dd

where:

• yyyy is a 4-digit year value (0000 to 9999)
• mm is a 2-digit month value (01 to 12)
• dd is a 2-digit day value (01 to 31)

Example:

2008-03-03-08.26.33.000000

If a plug-in provides a value that is not in the format just described, DB2 Document Manager ignores the value that is provided and uses the default value of 1970-01-01 (January 1, 1970).

Decimal
For properties of data type Decimal, the length and number of fixed digits is defined in the Decimal length section of the Modify Library Property Configuration window.

Example: If a property of data type Decimal is defined to have a total length of 5 and to have 2 fixed digits, DB2 Document Manager supports values between -999.99 and 999.99.

Double
For properties of data type Double, DB2 Document Manager supports decimal values with a maximum length of 31 digits, including the sign (positive or negative) and the decimal point. Values can have up to 6 digits after the decimal point. Scientific notation (such as 1.234e+02) is not supported.

Long
For properties of data type Long, the minimum and maximum length is defined in the Integer length section of the Modify Library Property Configuration window. Commas, such as the thousandth separator, are not supported.

Short
For properties of data type Short, the minimum and maximum length is defined in the Integer length section of the Modify Library Property Configuration window. Commas, such as the thousandth separator, are not supported.

Time
For properties of data type Time, the value must be in the following format: yyyy-mm-dd-hh.mm.ss.nnnnnn

where:

• yyyy is a 4-digit year value (0000 to 9999); ignored by DB2 Document Manager
• mm is a 2-digit month value (01 to 12); ignored by DB2 Document Manager
• dd is a 2-digit day value (01 to 31); ignored by DB2 Document Manager
• hh is a 2-digit hour value, in 24-hour format (00 to 23)
• mm is a 2-digit minute value (00 to 59)
• ss is a 2-digit second value (00 to 59)
• nnnnnn is a 6-digit microsecond value (000000 to 999999)

Example:

2008-03-03-08.26.33.000000

Plug-ins must provide the date portion (yyyy-mm-dd) of the Time value, but DB2 Document Manager ignores it.

Time stamp
For properties of data type Time stamp, the value must be in the following format: yyyy-mm-dd-hh.mm.ss.nnnnnn

where:

• yyyy is a 4-digit year value (0000 to 9999)
• mm is a 2-digit month value (01 to 12)
• dd is a 2-digit day value (01 to 31)
• hh is a 2-digit hour value, in 24-hour format (00 to 23)
• mm is a 2-digit minute value (00 to 59)
• ss is a 2-digit second value (00 to 59)
• nnnnnn is a 6-digit microsecond value (000000 to 999999)

Example:

2008-03-03-08.26.33.000000

Time stamp values in the data exchange file are in Greenwich Mean Time (GMT). Plug-ins must convert time stamp values to GMT when they are writing them to the data exchange file. The application automatically converts the output to local time.

Variable character
For properties of data type Variable character, the supported character set is defined by the character type that is selected from the Character type list on the Modify Library Property Configuration window. The minimum and maximum length is defined in the Character length section of this same window and does not include the end-of-line character (\n).

Example: If the minimum and maximum lengths that are specified are 0 and 2048, respectively, the property can store a string with up to 2048 characters. DB2 Document Manager allocates a buffer of size 2049 bytes for this value. The last byte is used to hold the end-of-line character.

5.2.2.10 DB2 Document Manager viewer uses the Stellent INSO Engine

Source
Appendix H. DB2 Document Manager viewer
Supported formats

Error
DB2 Document Manager viewer uses the Stellent INSO Engine, not the MS-Tech INSO Engine.

Correction
The DB2 Document Manager viewer uses two engines for rendering viewable documents and images: Bedrock Engine and Stellent INSO Engine.

5.3 Support Web site

For any questions, concerns, or problems related to DB2 Document Manager or to access the product documentation, visit the following Web site:
http://www.ibm.com/software/data/cm/docmgr/support.html

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user’s responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA 95141-1003
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

Trademarks

See http://www.ibm.com/legal/copytrade.shtml for information about IBM trademarks.

Adobe, Acrobat, Portable Document Format (PDF), and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.