IBM DB2 Document Manager Version 8.4 Fix Pack 1 (Build 100) 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 fixed after the initial release of Version 8.4 of DB2 Document Manager.

If a link below does not work, the detailed information for that APAR is not yet available from the Support page. Try again in a day or two.

Table 1. Problems fixed in DB2 Document Manager Version 8.4 Fix Pack 1 (Build 100)

APAR	Brief problem description
IO04424	Content Manager: Represents item option required Set button DB2 Content Manager systems only. To save the value of the Represents item option on the Attributes tab of the New and Modify Item Type windows, you were required to click Set before clicking OK or Apply. This was inconsistent with a number of other windows and it was overlooked by some customers, causing Designer not to save the value of the Represents item option. Now that clicking OK or Apply saves the value of the Represents item option, the Set button is no longer needed, so it was removed from the Attributes tab of the New and Modify Item Type windows.
IO04431	Lotus Notes: E-mail notifications not displaying double-byte characters correctly Lotus Notes e-mail notifications that contained characters from double-byte character sets did not display properly.
IO04824	Designer: No error message when maximum number of routes or states breached Designer did not display a message when you tried to add more than the maximum number of routes (300) or states (100) to a life cycle map. Also, the number of routes and states that customers were actually able to add varied depending on the circumstances.
IO04826	Rendition Services: Hanging under Microsoft Word 2003 The Dialog2 parameter in the DdmRDlgs.ini file did not suppress Microsoft Word 2003 user prompts, and this caused Rendition Services to hang when the following conditions existed: The Microsoft Word 2003 document was read-only One of the following two conditions was true: Rendition Services was configured to run as a user who was not currently logged on (in other words, a user other than the local system account). Rendition Services was configured to use the local system account, but the option Allow service to interact with desktop was cleared.
IO04845	FileNet user and group names > 28 characters not displayed The 28-character limitation on FileNet® user and group names documented in the IBM DB2 Document Manager 8.3 Fix Pack 6 Readme still holds true. The application now logs all user and group names that exceed 28 characters.
IO04867	Desktop: Group-defined views not displaying correctly In an environment in which the view that a Desktop user saw was defined by the group that the user selected, the wrong view was displayed.
IO04993	Designer: No error when trying to change minimum attribute length For an attribute that is used by an item type, Designer did not display an error message, as it should have, if you tried to change the minimum length of the attribute. Also, Designer did not allow you to change the minimum length of a variable character attribute to 0 (zero) even though the attribute was not used by an item type. Designer should have allowed the length change.
IO05003	Notification Services: Not handling SMTP errors properly DdmSmtp errors were not handled properly by Notification Services. The DdmSmtp errors, which were written to the DdmSmtp.log file, should also have been written to the Notification Services log file. And notification requests that failed due to a recoverable SMTP error should have been requeued for later processing.
IO05037	Declared records invisible under Tivoli Access Manager A customer could declare records by using DB2 Document Manager or DB2 Records Manager, but subsequently, the customer could not view the declared records from DB2 Document Manager after DB2 Records Manager Enabler was deployed in an IBM Tivoli Access Manager environment. The record was viewable from the DB2 Content Manager Client for Windows.
IO05071	Folder migration failed if certain users became ineligible Folder migration failed when a user that was listed in a pre-version 8.3 Fix Pack 2 folder access list was no longer a valid DB2 Content Manager user.
IO05756	Outlook menus disappeared Some Microsoft Outlook menus (Tools -> Macro -> Macros, Security, and Visual Basic Editor) failed to appear when users started Outlook before they started Document Manager.
IO05815	Designer: Did not set cache object to Pending Creating a new item type by using Designer did not set the Library Property Definitions cache object to the Pending state in Cache Manager, which is required by the DB2 Document Manager Client API.
IO05926	Document transitioning failed when displaying user names Transitioning a document failed when CVL values were configured to display the display names of users (Description was chosen for the Use list value on the New or Modify CVL Configuration window), but transitioning a document succeeded when CVL values were configured to display the actual, unique names of users. (Name was chosen for the Use list value on the New or Modify CVL Configuration window.)
IO06236	Attribute values sometimes not saved Attribute values were not saved when the Add from Library Template command was used to create a new item and assign that item to a class that belonged to a different item type.
IO06266 / IO06734	Panagon: User lists of 20 items displaying only 10 Panagon systems only. In a list of exactly 20 items, the user's list of checked-out documents or list of favorite documents displayed only ten items.
IO06298	Role list not grayed when containing only one item The Role list did not behave like the Action list in the Transition window when there was only one role in the list. (If there is only one selection in a list, the list should be grayed out.)
IO06361	Processes not re-executing after folder action failure Process jobs were not re-executed after folder actions failed because incorrect error status was returned from the folder action calls.
IO06566	Content Manager: View indicator not displaying properly DB2 Content Manager systems only. If the Display expanded view indicator (+) option on the Advanced View Configuration window was selected but none of its sub-options were selected, a static folder on the Desktop was not displayed with an expanded view indicator (+) next to it. The indicator displayed only if one or more of the Display expanded view indicator (+) sub-options were selected.
IO06677	Users unable to change state from document template If a class has more than one state in which a document can be added and the State property of a new item template is assigned a default value (on the Properties page of the New or Modify New Item Template Configuration window), the Add From Document Template command did not allow a user to change the state of the new document from the state of the document template.
IO06696	Microsoft Word: Older version attributes overwritten Using the Version History command to select and then view an older version of a Microsoft Word document overwrote the document's property exchange attributes with the attributes from the most recent version of the document.
IO06702	Some users unable to view entire document name in Add dialog When adding a document from the Desktop, users with monitors at lower resolutions were sometimes unable to view the entire document name within the Add dialog (typically because the full path was too long).
IO06706	AutoCAD upgraders unable to add linked JPEG files After upgrading from Autodesk AutoCAD 2004 to AutoCAD 2006, when a user opened and saved DWG files in AutoCAD, the linked JPEG files could not be scanned into DB2 Document Manager. This happened to all DWG files with linked JPEG images that they created by using AutoCAD 2004.
IO06834	Users without printing privileges could print Users without the required privilege (specifically, the ClientPrint privilege) could still print documents from the Document Manager Viewer. Users who lack the ClientPrint privilege can no longer print (the Print menu command is disabled). See section 3.8 below: Document Manager Viewer determines printing access through user privileges
IO06850	Notepad plug-in attribute updates incomplete When a user added a document from a Notepad plug-in, the application did not propagate all updated attribute values to the .ini file.
IO06967	Outlook integration: users prompted to save wrong items The Desktop was integrated with Microsoft Outlook and was configured to save only e-mails, but users were prompted to save other Outlook items (appointments, calendar entries, and so on) also.
IO06996	Case-insensitive search option not honored If a Power Search was saved that had both the Enable prompting for values option selected and the Case insensitive search option selected, the Case insensitive search option was not honored when the search was executed.
IO07007	Users couldn't re-execute a dynamic search Clicking a dynamic search folder a second time when the results of the first search were displayed in the Desktop's view pane did not re-execute the search. This is working as designed. Added function to the right-click menu's Refresh command to provide the ability to re-execute the search. See the "Searching: Re-executing a dynamic search" section below for complete information.
IO07023	Pre-client plug-in missing class value An Add dialog had a pre-client plug-in such that when a user added a document and selected a class for the document, the pre-client plug-in was activated. But the DM_Class value was missing from the data exchange file.
IO07106	Restricted users saw inaccurate search results Users with limited privilege sets retrieved inaccurately empty search results.
IO07164	Importing numbered objects could prevent document additions Exporting an item-numbered object, adding documents to it, then re-importing the object was generating a "document already exists" error message.
IO07251	Specifying a mask could prevent the addition of a document When configuring an Add dialog, if you selected the properties on an attribute, did not specify the attribute as required, and specified a mask in the Format field, you restricted the attribute's value to certain characters. (For example, specifying "#" for an attribute of type Extended Alphanumeric restricts users from providing anything other than a number as the specified character of the attribute's value.) Subsequently, when a user tried to add a new document and left the value of that attribute blank, an error was displayed ("Mask on a dialog makes the attribute required") and the user was unable to add the document.
IO07284	Office integration: folder expansion in add dialog was slow In the Add Folder dialog under the Office integration, folder expansion was slow.
IO07392	Folder imports sometimes failed When trying to import folders within the Item Loader (Document -> Add -> Item Loader), users could select Library -> Export Folder before the menu had fully loaded, causing folder import failures on previously exported folders.
IO07457	Users unable to create PDFs from Outlook e-mail Users were unable to use Rendition Services to create PDFs of Microsoft Outlook e-mail. Rendition Services appeared to hang after it launched Microsoft Outlook (Outlook.exe). The fix for this problem also enables Rendition Services to generate PDFs from HTML files.
IO07477	Property Exchange returned inaccurate values Property exchanges that included an undefined attribute were returning strings that included the undefined attribute name (such as "Title_3") instead of a null value.
IO07484	Transition dialog displayed even when no action was possible Even when the user could take no action (for example, they lacked permission or the document was not in life cycle), the Transition dialog still appeared.
IO07565	Service processing could not recover after stoppage When the Life Cycle, Notification, Print, or Rendition service stopped during processing, users could not change the Priority of a request from Processing to any other value, preventing any processing from taking place. Users with privileges can now change the Priority value of requests from Processing to high, normal, or low, requeuing the requests and enabling processing to continue.
IO07655	Invalid property exchange caused integrated application to fail When Property Exchange could not locate a specified property (because of a name change or deletion from the library), the application would freeze. The application now displays an error dialog and logs the error.
IO07698	Desktop menu command did not launch executable plug-in Desktop menu commands did not launch executable plug-ins, which include DLLs as well as executable files, as they should. Note: The file that contains the current plug-in version number, DdmPlugin.ini, now resides in the directory C:\Documents and Settings\All Users\Application Data\IBM\DB2 Document Manager. Executable plug-ins with a specified client location of %DMPlugin% appear in the client directory C:\Documents and Settings\All Users\Application Data\IBM\DB2 Document Manager\dmclient\plugins
IO07702	Native renditions incorrectly created Compound Document links Using native rendition to copy a document incorrectly added a compound document link to the parent or source item.
IO07827	Plug-in .ini files mishandled multi-line attributes Multi-line attributes with line returns were not handled correctly in the INI files that are associated with Desktop action plug-ins. The portions of the attribute value that followed a line return were each written to a new line in the INI file. When the attribute value was later retrieved, only the portion that preceded the first line return was read from the INI file. The rest of the value was lost. Important: The fix for this problem introduces a new format for property values that are written to the INI files that are associated with Desktop action plug-ins. See the "Custom dialog controls: Data exchange file format" section below for complete information.
IO07836	Outlook e-mail attachments did not inherit their parent profile In Outlook integration, adding an e-mail and its attachment as a compound document failed to copy the e-mail profile to the attachment, even when the "Copy Master items profile to new related files" was set to Yes.
IO07904	Notes integration: Semi-colons in document names misinterpreted The Notes integration treats semi-colons (;) as text delimiters, so the integration was interpreting single file names as multiple names.
IO07986	Users could not search on an empty attribute value Users could not search for items that contained an empty attribute (an attribute with no value entered). They can now select a new operator, "Is Empty".
IO07990	Date-dependent processes producing inaccurate results When launching automated date-dependent processes, users were seeing inaccurate results because the processes would use the wrong date. Users in some time zones (GMT -x, as in New York) were seeing the correct date +1, while in other time zones (GMT +x, as in China) were seeing the correct date -1.
IO08000	Plug-in data type and format information missing from documentation Information was missing on the possible data types and the expected format of the data when setting a value from a plug-in. See the [ItemData_X] section under Documentation corrections and clarifications below.
IO08014	Microsoft Word users prevented from adding documents while viewing When viewing a document in Microsoft Word, users trying to add the document could not do so (they received an incorrect message that the document was checked out).
IO08015	Folders in folder navigation pane not collapsing properly In the Desktop folder navigation pane, clicking the - (minus) sign sometimes failed to collapse an expanded folder.
IO08032	Role-checking caused slow display of the class list When adding documents, performance related to the display of the class list in the Add dialog could be slower than expected. This was due to a large number of classes and the need to perform role checking across item types, classes, and states.
IO08035	Outlook integration: vCards could not launch Outlook Under the Outlook integration, double-clicking on a vCard appointment file (.vcs) or contact file (.vcf) in Desktop would fail to launch Outlook.
IO08052	Desktop action plug-in .ini file creation was slow The .ini file generated during the process of creating a Desktop action plug-in opened slowly.
IO08078	Designer could not export rule sets that referenced other rule sets In Designer, attempting to export a rule set that referenced another rule set caused errors.
IO08209	Users were not informed of "too many items to display" When performing a power search that returned more than 500 items, users were not informed that the application would display only 500 items.
IO08219	Rules could not check for empty date fields Users could not create a rule that checked for an empty date field.
IO08220	Outlook integration: could not add e-mails with long subject lines The application could not add Outlook e-mails with long subject lines, but would still issue a confirmation message.
IO08221	Outlook and Notes: could not add e-mails with tabs in subject The application could not add Outlook or Notes e-mails with tabs in subject lines, but would still issue a confirmation message.
IO08225	Outlook integration: long text between % symbols crashed application Trying to add an Outlook e-mail that contained more than 64 characters between two % symbols caused the application to crash.
IO08238	Notes integration could not add attachments delivered by API The Notes® integration was not recognizing and thus not adding attachments delivered through an API.
IO08270	Lifecycle Services incorrectly resetting document security No way existed for Lifecycle Services to apply security actions only when a document was transitioned to a state. Lifecycle Services also applied security actions when it processed Checkin and Modify properties triggers. This meant that if a user changed the security on a document after that document had transitioned to the new state, the document security was subsequently reset by Lifecycle Services. See the section "States: New option controls whether security actions are applied after potential property value changes" for information about a new option that provides greater control over the application of security actions.
IO08439	Rendition: destination option menus displaying incorrect values The rendition destination option Set item class to... was displaying classes belonging to the original library rather than the selected destination library. Similarly, the option Apply item template was displaying item templates belonging to the original library rather than the selected destination library.

2. Known Problems

This section describes the known problem in DB2 Document Manager Version 8.4 Fix Pack 1.

2.1 Long file names truncated

When adding a document to the repository, DB2 Document Manager removes that portion of the document file name that is more 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.

3. Quality Improvements

This section contains information about quality improvements in this release.

3.1 Planned 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. DB2 Document Manager, Version 8 Release 4 with Fix Pack 1 is scheduled to be certified to CC assurance level EAL3. When the certification process is complete, we will post a flash on the Document Manager support web site:

http://www.ibm.com/software/data/cm/docmgr/support.html

Newer versions of the product will continue to be evaluated at the same or higher assurance levels as required.

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) 7.0.9 and 8.1.1
• Autodesk AutoCAD 2008 and 2008 Service Pack 1
• Bentley MicroStation V8 XM
• Microsoft Office 2007 Service Pack 1

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, 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: each line return replaced with ''\n'' and each backslash character replaced with "\\".

After the plug-in finishes, DB2 Document Manager reverses the INI modifications in memory after the property values are read from the INI file. 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 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 CM group ICMPUBLC or by creating super-groups containing other groups.

3.8 Document Manager Viewer determines printing access through user privileges

The 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 denied printing privileges may 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 1

DB2 Document Manager Version 8.4 Fix Pack 1 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 1:

• DB2 Document Manager Version 8.4
• 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 1 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 1 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 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 this reason, you should install this hotfix package. 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: 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 crashes 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 this 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.1.3 Common Criteria certification details

When Common Criteria certification is complete, a new Document Manager installation help topic will include the following text:

The evaluation was performed on the product with the following configuration. Single sign-on must be disabled. Allowing trusted logon must be disabled. The DB2 Content Manager System Administration Guide contains instructions for allowing trusted logon. Common criteria users must adhere to the password guidelines stated in this document.

DB2 Document Manager uses the operating system time for the timestamp, so an administrator does not have to do anything to set up that timestamp when installing.

It is assumed that the applications and operating system interfaced by the DB2 Document Manager product does not compromise the security of the DB2 Document Manager product and, where applicable, that they have been configured in accordance with the manufacturer’s installation guides. No additional integrated applications enforce any security function or support any of the security functions being claimed.

It is assumed that all software and hardware, including network and peripheral devices, have been approved for the transmission of protected data. Such items are to be physically protected against threats to the confidentiality and integrity of the data.

It is assumed that there are one or more competent individuals who are assigned to manage the DB2 Document Manager product and the security of the information it contains. These individuals must ensure that this product is delivered, installed, managed, and operated in a secure manner. Such personnel are assumed not to be careless, willfully negligent, or hostile and will follow and abide by the instructions provided by the administrative guidance.

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 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 logging in.

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

5.2.2.2 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.3 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.4 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 a 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.5 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 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 completing 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.6 [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 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 above format, 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 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.7 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 this 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.