FileNet Integrated Document Management Technical Bulletin

FileNet Integrated Document Management Technical Bulletin Version 4.0.3 Release May 2011 1

Contents Introduction... 3 Contact customer support... 3 Feedback... 3 Microsoft Windows Terminal Services... 4 Microsoft Windows Terminal Services IBM FileNet Desktop and Web Services support... 4 Microsoft Windows Terminal Services Open Client support... 4 Benefits of Using Open Client in a Microsoft Windows Terminal Services Environment... 4 Deploying and Using the IBM FileNet Open Client with Microsoft Windows Terminal Services... 7 Summary... 9 Citrix... 10 IBM FileNet IDM s support on Citrix... 10 Virtualization... 11 IBM FileNet IDM Support on Virtualization environment... 11 Revision Table... 12 Notices... 13 Trademarks... 14 2

Introduction IBM FileNet IDM 402 Technical Bulletin Introduction This document serves the technical information addressing the known issues and limitations on Microsoft Windows client and server operating systems, Microsoft Windows terminal services, Citrix environment and Virtualization with IBM FileNet IDM Desktop, Web Services and Open Client. The issues and limitations mentioned here are based on the occurrences during the development and testing activities in the lab. Contact customer support For information about contacting customer support: 1. Navigate to the IBM FileNet Product Family support page: http://www.ibm.com/software/data/contentmanagement/filenet-product-family/support.html. 2. Select a product under Select a product or search for a particular support topic under Enter search terms. Feedback Your feedback helps us to provide quality information. Send your comments about this publication or any other IBM FileNet documentation by e-mail to comments@us.ibm.com. Be sure to include the name of the product, the version number of the product, and the name and part number of the book (if applicable). If you are commenting on specific text, include the location of the text (for example, a chapter and section title, a table number, a page number, or a help topic title) 3

Microsoft Windows Terminal Services Microsoft Windows Terminal Services IBM FileNet Desktop and Web Services support Microsoft Windows Terminal Services Microsoft Windows Terminal Services IBM FileNet Desktop and Web Services support IBM FileNet IDM Desktop and Web Services do not work on Terminal Service. However, in limited tests conducted in development environment have shown that IDM Desktop and Web Services work in this environment. But specific environments in IBM with native operating systems might not match with many circumstances at customers end and that may not give real advantages and benefit to the customers. Hence, this environment is not supported; customers can proceed at their own risk. Microsoft Windows Terminal Services Open Client support This document describes the benefits of using the IBM FileNet Open Client in a Microsoft Windows Terminal Services environment, provides high level definitions of key technologies, provides examples of how to deploy and use the Open Client in a Microsoft Windows Terminal Services environment, and identifies the process required to optimize the performance of the Open Client Java Viewer in a Microsoft Windows Terminal Services environment. Benefits of Using Open Client in a Microsoft Windows Terminal Services Environment Increase Remote Network Availability Remote access to mission-critical information is key in today s progressively mobile business environment. Increasing remote network availability and lowering bandwidth usage adds business value, improves reliability, and enables remote office workers. Whether that information is stored on Image Manager, Content Services, Report Manager, SAP, Siebel, or a homegrown application, it is made immediately available to remote workers using the Open Client installed on Microsoft Windows Terminal Services. Reduce Desktop Management Costs The recent trend towards creating a mobile workforce provides an increased competitive edge for many companies. However, as the workforce becomes more mobile, challenges and costs associated with managing and supporting the remote workers desktops and applications increase. The Open Client, integrated with Microsoft Windows Terminal Services, allows an organization to meet these challenges by eliminating many of the costs associated with supporting and managing remote clients. Remote users are employees, business partners, and customers who require access to information stored in the system. Providing business partners and customers access to information poses the most significant challenge because they work in a client environment that is not controlled by IT. This challenge is eliminated when the user is accessing the Open Client via Microsoft Windows Terminal Services, since the server becomes the only environment IT must manage. IT Staff controls exactly what remote workers can access while also providing a cost-effective means to monitor progress and productivity. This reduces desktop management costs by providing a fast, easy-to-use solution that enables remote workers and a mobile sales force to instantaneously access all the tools required to do their job. Increase Sales Force Agility Today, increasing agility helps a mobile sales force keep their competitive edge. They must easily adapt to complex demonstration configurations and changing customer requirements. Improving network access to critical applications increases this agility. By integrating the Open Client and Microsoft Windows Terminal Services, the management of the network and application infrastructure is centralized. This allows an organization to simplify the delivery of rapidly evolving demonstration environments. Therefore,

Microsoft Windows Terminal Services Benefits of Using Open Client in a Microsoft Windows Terminal Services Environment complex demonstration configurations that require access to Siebel, SAP, and homegrown applications can be managed centrally, but accessed, adjusted on the fly, and delivered remotely. The increased agility of a sales force drives savings in labor, increases productivity, and reduces overhead costs. IBM FileNet IDM Open Client The IBM FileNet IDM Open Client is the thin client interface for IBM FileNet s Web Services server product. It allows users to quickly locate and access content from any Web browser anywhere across the enterprise. It improves overall efficiency and provides a competitive edge through faster processes. It requires no software download and provides maximum reach into the enterprise with minimal deployment costs. The Open Client enables a user to access documents stored in the IBM FileNet Image Manager, IBM FileNet Content Services, or IBM FileNet Report Manager repositories. The Open Client provides a suitable environment for deployments using Microsoft Windows Terminal Services because it installs a very small footprint and is certified against any HTML 3.2/HTTP 1.1 certified browser. The diagram below provides an architectural overview of IBM FileNet IDM Web Services/Open Client. The top set of boxes represents the three different web clients available with Web Services. The Open Client, shown in the top left side of the diagram, was specifically designed to support multi-user environments like Microsoft Windows Terminal Services and Citrix. Microsoft Windows Terminal Services Microsoft Windows Terminal Services delivers the Microsoft Windows desktop, as well as the latest Windows-based applications, including IBM FileNet IDM Open Client, to virtually any desktop computing device, including those that cannot run Microsoft Windows. This lets more people in an organization take advantage of the resources provided by a distributed computing environment. Terminal Services can also be used to remotely administer a Microsoft Windows server. When a user runs an application on a Microsoft Windows terminal server, all of the Open Client application execution takes place on the server, and only the keyboard, mouse and display information are transmitted over the network.

Microsoft Windows Terminal Services Benefits of Using Open Client in a Microsoft Windows Terminal Services Environment When a user runs an application on a Microsoft Windows terminal server, all of the Open Client application execution takes place on the server, and only the keyboard, mouse and display information are transmitted over the network. Each user sees only their individual session, which is managed transparently by the server operating system and is independent of any other client session. Unlike the traditional client/server environment, when Terminal Services are enabled in Microsoft Windows Server, all the Open Client application processing occurs on the server. The Terminal Services client performs no local processing of applications; it just displays the application output. The Terminal Services technology transmits only the application presentation the graphical user interface (GUI) to the client. Each user logs on and perceives his or her session only, which is transparently managed by the server operating system and is independent from any other client session. Citrix Metaframe Integration with Microsoft Windows Terminal Services Citrix Metaframe is a client add-on to Microsoft Windows Terminal Services and is manufactured by Citrix Systems, Inc. Microsoft Windows Terminal Services on Microsoft Windows is the infrastructure required for client products such as Citrix Metaframe to interact with Microsoft Windows Server applications. Citrix Metaframe does not interact directly with any IBM FileNet software; it interacts with Microsoft Windows Terminal Services, which in turn interacts with IBM FileNet software. IBM FileNet has not tested or sought certification with Citrix, and therefore cannot provide support for Citrix Metaframe. However, as show in the diagram below, Citrix Metaframe can interface with the same version of Microsoft Windows Terminal Services utilized by the Open Client. The diagram shows Windows 2000 as an example.

Microsoft Windows Terminal Services Deploying and Using the IBM FileNet Open Client with Microsoft Windows Terminal Services Deploying and Using the IBM FileNet Open Client with Microsoft Windows Terminal Services The following diagram depicts a typical deployment for Microsoft Windows Terminal Services and the IBM FileNet Open Client. Please note that traditional IBM FileNet desktop deployments are not recommended and not supported through a Microsoft Windows Terminal Services session because of the complexity of configuring such an environment. In fact, in some use cases, custom code would be required to support such an environment. As depicted by the light blue laptop icons connected to the Microsoft Windows Terminal Services server, users directly on the corporate LAN, remote users on the WAN, or even users external to the company connecting through a firewall under lower bandwidth network facilities would access the Open Client by launching a browser in a Microsoft Windows Terminal Services session running on the Microsoft Windows server. Users would connect to the appropriate URL to gain access to IBM FileNet IDM Web Services server where the Open Client has been deployed. It is important that the IBM FileNet IDM Web Services server have the appropriate patches as defined on the CSS web site for the Open Client to function properly. In addition, the server running Microsoft Windows Terminal Services should have the appropriate browser support needed for the Open Client. After the user has connected to the Open Client, the following diagram depicts how the out-of-the-box (OOTB) behavior would occur.

Microsoft Windows Terminal Services Deploying and Using the IBM FileNet Open Client with Microsoft Windows Terminal Services The boxes in red illustrate activity that occurs on the Microsoft Windows Terminal Services server. The boxes in blue illustrate activity that is generated from typical OOTB usage of the Open Client irrespective of whether it has been deployed through a Microsoft Windows Terminal Services session. Open Client Java Viewer Optimization For Microsoft Windows Terminal Services, IBM FileNet only supports the use of the lightweight Java Viewer. To optimize this viewer for Microsoft Windows Terminal Services deployment, the following lines of code must be added to the FnOpenClient project and recompiled. These changes are required for the Java Viewer image and annotation cache to operate successfully. To optimize the Open Client Java Viewer, the following procedure must be followed: In the second JavaScript block of the fnjavaview.aspx page, add the following Java script: document.write('< param name="cachepath" value="<%=getcachepath()%>">'); In the FnJavaView class of the fnjavaview.aspx.vb file, you will need to add the following procedure. Please note that the acachepath string value can contain a directory path of the administrator's choosing. The current user's login name will be concatenated to the end of this directory path, giving it a unique value for each user that logs into the system. ' Public Function getcachepath()

Microsoft Windows Terminal Services Summary ' Purpose: Gets a cache path name to use as the alternate Java Viewer cache path. Note the following: A forward slash must be used for directory separators. The ' cachepath parameter is only recognized on Windows platforms. ' Parameters: None ' Throws: None Public Function getcachepath() As String Dim acachepath As String acachepath = "c:/cache_directory_structure_of_choice_here/" + getuserid() Return acachepath End Function Summary By integrating the IBM FileNet IDM Open Client with Microsoft Windows Terminal Services, organizations can increase remote network availability, reduce desktop management costs, and increase sales force agility. With this integration, limiting factors like network bandwidth, modem speed, and the user s desktop environment are no longer an issue. Network bandwidth and modem speed is not a liming factor because the document/application remains on the server, and only the document/application display and the user input are transmitted between the server and the client. The desktop environment is no longer a limiting factor for IT because no matter what operating system or browser the client is using, only the server must be managed. Therefore, by integrating the IBM FileNet IDM Open Client with Microsoft Windows Terminal Services, a company s employees, business partners, and customers can access information from any desktop anywhere in the world.

Citrix IBM FileNet IDM s support on Citrix Citrix IBM FileNet IDM s support on Citrix IBM FileNet IDM Desktop and Web Services do not work on Citrix environment. However, in limited tests conducted in development environment have shown that IDM Desktop and Web Services work in this environment. But specific environments in IBM with native operating systems might not match with many circumstances at customers end and that may not give real advantages and benefit to the customers. Hence, this environment is not supported; customers can proceed at their own risk. The meaning for support of Citrix and IBM FileNet IDM The environments work with IDM Web Services, are not formally certified. Therefore: If customers choose to deploy IDM Web Services using Citrix, and in order to determine if a particular problem is due to Citrix, then customers may require reproducing the problem in a native (non-citrix) environment. The known issues in the testing history of Citrix and IBM FileNet IDM The testing performed with Citrix v4 on a subset of IDM functionality was not a comprehensive test, so customers might encounter issues beyond those noted below. The information below is the best data that we have at this time. 1. Writing to files Some issues are expected while writing to files (including logs), especially temporary files that store cache related data. One work-around available for this is to create user-session specific directory and files rather than application specific directory or files. IDM uses IS and CS as repositories. Logs generated by client libraries used to access these repositories, also need to be stored in user-session specific locations. IS and CS teams need to be contacted on how to configure these locations in IS/CS client libraries for Citrix kind of environment. Similarly IDM Trace files should also be stored in user-session specific locations. 2. Configuration Settings It is recommended that Citrix server be installed in INSTALL mode rather than EXECUTE mode in order to take advantage of its ability to monitor a user s HKCU hive (a hive is a set of structured registry keys) 3. Registry INSTALL mode of Citrix server keeps track of registry key changes using a 'shadow registry key' and timestamp so that if a user makes a change to his/her settings in one of the sessions, this change is reflected in all subsequent sessions for that user. This is another benefit of using INSTALL mode over EXECUTE mode. Note: IDM may not be supported on Citrix environment. Reference Hardware and Software Requirements url: http://www-01.ibm.com/support/docview.wss?rs=3346&uid=swg27009996

Virtualization IBM FileNet IDM Support on Virtualization environment Virtualization IBM FileNet IDM Support on Virtualization environment IBM software products do not specify support for Virtualized operating systems because the Virtual Environment products themselves provide transparency to the operating systems, applications, and middleware that operate above it. If you submit a standard usage or defect-related service request, and you are running on a virtual environment, IBM Support* will make commercially reasonable efforts to resolve the problem. We will assume that the problem is common to both native and Virtual operating environments, and we will only require you to recreate the problem in a native environment if there is an indication that the problem may be unique to the Virtual Environment. Application Products can be very sensitive to processor caching and overall memory constraints. Moreover, software virtualization resource availability for Application Products is completely unpredictable. IBM Products can make no guarantees with respect to performance or scalability in a virtualized environment. If IBM suspects that a problem is the result of the virtualization technology, we will require the problem be recreated in a native environment before providing continued defect support. That determination will then guide subsequent ownership of the problem. IBM support will not provide support or assistance with setting up and configuring Virtual Environments. Customers looking for support for setting up a virtual environment should consult respective vendors. This Virtualization Environment support statement applies to any virtualization technology providing binary compatibility between their stand-alone operating environment and virtualized partition deployment. The above applies to service requests within scope for Passport Advantage support as per the "Software Support Handbook" at url http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html Software support services for IBM SWG products in a VMware (virtualization) environment detail at: http://www-01.ibm.com/support/docview.wss?&uid=wws1e333ce0912f7b152852571f60074d175

Revision Table Month/Year Description IBM FileNet IDM 402 Technical Bulletin HRevision Table May 2011 The document includes technical bulletin on Windows terminal server, Citrix and Virtualization for IDM 4.0.3 release. 12

Notices This information was developed for products and services offered in the U.S.A. IBM FileNet IDM 402 Technical Bulletin Notices 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 grant 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: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd. 3-2-12, Roppongi, Minato-ku, Tokyo 106-8711 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. 13

Notices 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. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. 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. Portions of this product are: Copyright (C) 1991-2, RSA DATA SECURITY, Inc. created 1991. All Rights Reserved. Copyright (C) 1995-2005 Jean-loup Gailly and Mark Adler. All Rights Reserved. Copyright (c) 1995-2009 International Business Machines Corporation and others Copyright (C) 1991-2008 Unicode, Inc. All rights reserved. Copyright (c) 1998-2003 The OpenSSL Project. All rights reserved. Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) Copyright (C) 1994-2010 EMC Corporation. All rights reserved. Copyright (C) Snowbound Software Corporation 1993-2006, All rights reserved. Copyright (C) 2002-2010 Rogue Wave Software, Inc. All Rights Reserved. Copyright (C) 1984, 1989, 1990 Free Software Foundation, Inc. All Rights Reserved. Copyright (C) Oracle Outside In Viewer Technology, Copyright 1992, 2007, Oracle. All Rights Reserved. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ( or ), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml. Java is a trademark of Sun Microsystems, Inc. in the United States, other countries, or both. 14

Notices Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others. 15