This document provides information on configuration requirements, recommendations, and limitations along with information on collocation and compatibility with other FileNet products.
All client machines and servers must run TCP/IP.
Out-of-the-box user applications such as IDM Desktop are supported on servers only as required for administration and demonstation.
The chart below explains which libraries require installation of client libraries and configuration of an ODBC Data Source.
| Library/Database | Install client libraries | Configure ODBC Data Source |
| CS with SQL database | No, installed by Setup | Yes |
| CS with Oracle database | Yes, install from Oracle CD | Yes |
| IS with SQL or Oracle | No, installed by Setup | No, handled by IDM Configure |
Document classes are required on CS libraries. For details, see the FileNet Content Services Release Notes.
Support for matching releases
Web Services 3.2 supports only 3.2 clients.
Path-based URL retrievals
The path-based URL retrieval preference requires:
You can enable the preference for any CS 5.2 library but it will be ignored unless the library has the required patch.
CS libraries require Anonymous Authentication
To access CS libraries, Anonymous Authentication must be enabled in IIS. Anonymous Authentication is the default authentication setting in IIS.
If your site uses DNS for IP address resolution, each IDM Desktop machine's configuration must allow resolution of the appropriate IS server name.
IDM Desktop supports FAT file systems for Windows 98, and supports FAT and NTFS file systems for Windows NT, 2000 and XP.
It is not necessary to install a browser to run IDM Desktop applications. However, if a supported browser is installed, IDM Desktop includes the ActiveX Client (viewer.exe).
Microsoft Data Access Components (MDAC)
IDM Desktop Setup installs core MDAC 2.7 components, including OLE DB providers and ODBC drivers for various data sources. The MDAC setup does not install the Data Access SDK. For information about MDAC 2.7, see http://www.microsoft.com/data/doc.htm
You must recompile any projects that use IDM objects that reference an ADO object.
The MDAC 2.7 setup installs the following components:
ActiveX Data Objects (ADO)
ODBC
OLE DB
Remote Data Service (RDS)
For application integration, the entire application must be installed on the user's local hard drive (not run from a CD or network drive, and not installed using the "Install on first use" option).
Web Services 3.2 and IDM Desktop are qualified with Outlook 2000 and Outlook 2002. It is expected that using other MAPI-compliant email systems will work. However, if a problem arises with a MAPI-compliant email system, the problem must be replicated in a supported version of Outlook before FileNET can commit to resolving the issue.
If SSL is enabled on the web server, an SSL client certificate must be installed on each web client workstation.
Netscape browsers are supported for the HTML Samples and Open Client only.
To run Open Client 3.2.0 with McAfee NetShield Anti-Virus software on a Windows 2000 server, install NetShield v4.5 along with the required service pack for Windows NT or 2000 Server.
For best results, use Adobe Acrobat Reader 4.0 or 5.0 to display PDF documents
in the IDM Viewer. If the reader is installed, it runs as an IDM Viewer plug-in.
You can install the 4.0 reader from the IDM Desktop software CD, or you can
download the 5.0 reader from the Adobe web site.
Application integration
IDM Desktop application integration is not compatible with Web Services web client application integration. You cannot install both nor can you mix them in different applications. For example, you cannot have IDM Desktop application integration in Word and web client application integration in Excel.
IDM Desktop application integration is not compatible with P8 application integration. You cannot install both, nor can you mix them in different applications.
Web Services application integration is compatible with P8 application integration.
Web WorkFlo and Open Client
Open Client and WorkFlo Services must be kept in sync. When a WorkFlo Services hot fix pack or new release is made available, refer to the IDM Desktop, Web Services, an Open Client 3.2.0 Release Notes for steps to bring the Open Client web server up to the required sortware level.
Web Workflo 4.2.2 and Open Client cannot be collocated on the same web server and cannot share 4.2.2 WorkFlo Services. A web client can access both eProcess Web Workflo 4.2.2 web sites and Open Client web sites. However, Open Client and Web Workflo workflows are separately managed, which means Open Client users cannot participate in Web Workflo workflows and Web Workflo users cannot participate in Open Client workflows.
eProcess Web Workflo 5.0 and Open Client can be collocated on the same web server and can use the same eProcess 5.0 workflow server.
Clients can access both eProcess 5.0 web sites and Open Client web sites, and
can participate in workflows irrespective of which web site they were initiated
from. The workflow in which a user can participate is determined by the router/region
the user logs into and the username used to log on.
Web Services
Web Services includes its own web client and administrative tools. Do not
install IDM Desktop, IS, CS, or any CS server component on the same machine
with Web Services. Web Services is not supported on a CS remote Site Manager
Server.
IDM Desktop
IDM Deskop is supported on supported client platforms and is not supported on servers with the following exceptions:
IS and CS Servers
Using a web client on the same server as IS or CS is not supported.
Saros Document Manager (SDM)
IDM Desktop can coexist on the same PC as Saros Document Manager (SDM). IDM Desktop does not support the following legacy features of SDM: smart folders, document references, and stored searches saved using Mezzanine or the Mezzanine API.
Folders created using SDM 4.2.1 can have names containing forward slash characters. Web Services does not display these folder names correctly.
Capture and CS Capture Desktop
Web Services is not compatible with any version of FileNet Capture.
You must install IDM Desktop before installing Capture. IDM Desktop 3.2.0 supports Capture Desktop 3.1, 4.0, and 4.1. Refer to the Capture documentation for additional details.
PWP Station
Panagon Web Services cannot be collocated on the same system as PWP Station.
Panagon Print
IDM Desktop 3.2 works with FileNet Print 4.3.
Web Services cannot be collocated on the same PC with FileNet Print.
Report Manager
Web Services and IDM Desktop 3.2.0 can be used with Report Manager 4.0 and 4.1. You can collocate the thin and thick clients with a Report Manager desktop but not with the Report Manager server.
Before you can display Report Manager documents cross-cataloged to IS libraries,
refer to the Report Manager documentation for configuration information.