Readme
for IDM Desktop, FileNet Web Services, and Open Client 4.0

This readme provides the following information for the 4.0 release of IDM Desktop, Web Services, and Open Client:

• Before You Install
• About the software CDs
• Web client orientation
• Important notes about installing and upgrading
• Documentation installed with the software
• New Features in IDM Desktop and FileNet Web Services
• New Features in Open Client
• Important notes for developers

Before You Install

Every shipment of FileNet P8 Image Manager software includes a Before You Install CD. The BYI CD introduces the Image Manager family of products, explains how the products are related, and describes the installation order, if any. Read the BYI when you want to start with a high-level orientation.

About the Software CDs

IDM Desktop 4.0 is delivered on a single CD. Likewise, FileNet Web Services 4.0 is delivered on a single CD and includes both web server and web client software. Open Client, an optional add-on to Web Services, is on the FileNet Web Services CD. To add Process Integration to Web Services or Open Client or both, you install Open Client with Process Integration and then:

• For 5.0 integration, install the Process Connectivity Bundle, which you download from the FileNet FTP site
• For 5.1 integration, install Process Java Applets and Connectivity, which is shipped on its own CD

Web Client Orientation

FileNet Web Services supports several web clients. The table below summarizes the download and installation required, if any, for the various web clients.

Important Notes about Installing and Upgrading

Exit from all programs including virus protection programs before installing or upgrading FileNet software.

If you are installing from a network drive, map the network drive so you can start Help from Setup.

Reboot immediately before and immediately after any installation or upgrade. The reboot after an installation or upgrade registers the new DLLs. This can take several minutes. Please be patient and wait for the registration to complete.

You must configure an ODBC Data Source for each CS database server.

Accessing various CS libraries using IDM Desktop 4.0 and Web Services 4.0

• Accessing CS 5.3 libraries. IDM Desktop 4.0 and Web Services support CS 5.3 via the CS 5.4 Client DLLs, which are installed by the IDM Desktop and Web Services Setup program.
• Accessing CS 5.4 libraries. The CS 5.4 Client DLLs are installed with IDM Desktop/Web Services 4.0. For access to CS 5.4 libraries, you must uninstall the CS 5.3 Client DLLs.

Installing Web Services

See the FileNet Web Services Administrator's Help for information on installing and upgrading FileNet Web Services, the FileNet Web Services Client, and Web Services Application Integration. See the Open Client Administrator's Help for information on installing Open Client.

Quiet installation and upgrade (from 3.3 only) are provided for FileNet Web Services.

Note In case if you are upgrading from IDM Web Services 3.3 to IDM Web Services 4.0, then to use IDMWeb sample ASP (2.x) pages the DocContent.DLL and DocUpload.DLL files need to be copied from the IDM Web Services 4.0 installation folder (..\FileNet\IDM\Web\IDMWS) into the Sample Application's folder.

Installing Open Client

On Windows 2003, you must activate ASP.NET after installing .NET. (On Windows 2000, installing .NET activates ASP.NET automatically.)

MSJVM or Alternate Configuration 

By default, the MSJVM is used for remote scripting by the FileNet Web Services Client and FileNet Web Services Application Integration.

If a web client machine has a version of Microsoft Windows that does not include the MSJVM, you have two options:

• Download the MSJVM from the FileNet CSS web site, or from another source, to the workstation.
• Set up an alternate configuration for Web Services that removes the dependency on the MSJVM for all clients. See the topic, "Client SSL and MSJVM requirements" in the Web Services Administrator's Help for instructions on setting up Web Services to use the alternate configuration.

To download and install the Microsoft JVM, if needed for Windows XP

1. From the FileNet FTP site for patches, download Msjavx86.exe to the PC where you plan to install the Microsoft VM.
2. Open the JVM folder, and then double-click Msjavx86.exe to run the executable file.
3. This step is REQUIRED, not optional. Click Start, point to All Programs, and then click Windows Update. Install any fixes for the Microsoft VM that Windows Update detects.

Installing and Upgrading IDM Desktop

Silent installation facilities are provided for installing and upgrading IDM Desktop. It is not necessary to remove your Oracle ODBC configuration prior to upgrade.

IDM Desktop platforms are qualified with and without a browser installed.

IDM Desktop includes the following third-party products:

• Outside In Viewer Technology 8.0
• Pixel Translation 7.0 SP3

Uninstalling IDM Desktop and Web Services

Delete the ODBC Data Sources before uninstalling IDM Desktop. (FR 47417)

Installing and Upgrading Web Services Application Integration

A user can download Web Services application integration from the download page. To navigate to the download page:

1. Connect to a Web Services 4.0 site.
2. Click the Utilities button on the IDM bar (the vertical bar along the left edge), and then click the Download button.
3. Select FileNet P8 Image Manager Application Integration setup .
4. Click Continue with download, and then follow the on-screen instructions.

4.0 Documentation Installed with the Software

For a list of the documentation supplied with IDM Desktop, see the topic "About documentation" in the IDM Desktop Help (idmdsktp.hlp). If you are upgrading from an earlier release, see the Help files for information on new features in the release. You can review the new features, the installation procedures, and other documentation from the CD before installing the software. The Help files are on the CD in the \Docs folder and are installed with the software.  After installation you can access Help by pressing Start>Programs>FileNet IDM>Help for Users, Help for Administrators, and Help for Developers. Likewise, after installing Open Client, you can access Help by pressing Start>Programs>FileNet IDM>Help for Open Client Users, Help for Open Client Administrators, and Help for Open Client Developers.

Information on the FileNet IDM Desktop and Web Services Toolkit, which has programming information for both IDM Desktop and FileNet Web Services, is contained in the Help for Developers (idmsdk.hlp). The Help for Developers is copied to an IDM Desktop workstation during installation if you select and install the optional Developer Files in Setup. Developer Help is always installed with FileNet Web Services and Open Client. This Help file contains reference information for the IDM objects' methods, properties, and events, as well as descriptions of the object model and "Working with..." examples. To begin developing with the Toolkit, open the FileNet IDM Desktop and Web Services Toolkit Help for Developers by clicking on Start > FileNet IDM > Help for Developers, and review the topics: Using Type Libraries in Visual Basic and Developing with Visual C++.

New Features in IDM Desktop and Web Services

Following are the new features in IDM Desktop and Web Services:

• IDM Web Services now supports CS 5.4.
• Silent install of 4.0 and upgrade (from 3.3) are supported for FileNet Web Services.
• The CVL entries are viewed in the same order in which the values are entered in CVL.
• Support for long file names (>128 characters) in the IDM Viewer.
• ActiveX client now works even with the Enable Parent Paths option in IIS set to False.
• Supports check-in operation through Application Integration for documents with no LocalDB tracking.

New Features in Open Client

Following are the new features in Open Client:

• Bridging feature gaps between Open Client and FileNet Web Services Client applications such as using a URL reference to view or open a document, viewing additional document states, and copying the entire folder.
• Supports viewing COLD 2 and Mixed-Format (BMP, JPEG, TXT) IS documents using Java Viewer.
• Java Viewer supports additional annotation types, called extended annotations such as Oval, Line, Rectangle, and Image Stamp annotation.
• Enables viewing PDF documents using the IIS Byte Serving for Adobe PDF content streaming.
• The FileNet LDAP authentication retrieves full name mapped to UserID and displays the full name for the CS library.
• Provides the ability to send a multipage IS document as an e-mail attachment.
• The toolbar icons now appear enabled by default and the permission checking operation is delayed until the user performs a particular operation from the toolbar icons.
• The availability of Index Content checkbox can be configured, during the add/check-in wizard of a CS library.
• Supports the feature to configure the number of rows to be displayed in the List View.
• The source document file name can be specified as the default document title during Add and check-in operations in CS library.
• Supports remote printing of sticky notes annotation using Java Viewer.
• The default action on document icon click can be configured using the new site preference named "Document Icon Default Action". The default action is “Open” that uses the native application.
• Filter option on the Process toolbar enables creation of filters to display work items that meet specific criteria.
• Administrator-defined data fields exposed in Configuration Console can be displayed in the lists of work items.

Detailed documentation on the last two features in the above list is available on the CSS website (http://www.css.filenet.com) at the following locations for eProcess 5.0 and 5.1:

Products > Image Manager (IM) > eProcess Services > Product Documentation > eProcess 5.0.0
Products > Image Manager (IM) > eProcess Services > Product Documentation > eProcess 5.1.0

Important Notes for Developers

See the Compatibility and Dependency document for the supported development environments, and see the Release Notes for information on known problems that affect API calls. In addition, note the following:

• We support any fully COM-compliant development environment but we validate only with Visual Basic and Visual C++. Note that we do not validate PowerBuilder application development. If a problem occurs in a PowerBuilder development environment and you can reproduce it in a validated development environment, please contact Customer Support.
• Support for IDM COM objects in a .NET development effort is limited to the ASP.NET environment (in the way the objects are accessed in Open Client). In general, ASP.NET can call the IDM COM objects provided the application uses the correct threading model. The Data Provider and User Controls are reusable and callable from ASP.NET. See the Open Client Developer's Guide for tips provided by FileNet Engineering that may be useful in developing ASP.NET applications. In addition, application developers can leverage the full source code delivered with Open Client. Using IDM COM objects in an environment other than ASP.NET (for example, from .NET remoting, Windows Services, Microsoft XML Web Services, VB.NET, or C#) is not currently supported.
• In an IS numeric mask, the hash (#) sign suppresses all leading zeros. If an IS fpnumber property value is zero and the hash mask is used, the property field will show the zero when it is selected, but will appear to be empty when the focus is not on the cell.  If you want to retain the zero after formatting, use a mask of ‘0'.
• If you specify the idmDeletePrevious option on the QueueQuerySpecification.Fetch call when more than one entry was previously retrieved, only the last of the previously retrieved entries is deleted.