IBM FileNet Image Services Resource Adapter 3.4 Fix Pack 1 Release Notes
© Copyright IBM Corporation 2001, 2008. All Rights Reserved.

Contents

Customer Issues Addressed

Layout of  Distribution
Supported Platforms
Installation and Deployment

Known Software Problems and Restrictions
General Notes
ISRA Support

Contact Customer Support

Notices and Trademarks

Customer Issues Addressed

In this 3.4 Fixpack 1 release, we addressed following customer issues apart from fixing several defects as mentioned in Readme 3.4 Fixpack 1.

• Scaling the terminal / instance count from 10 to 100: With this new release ISRA would be able to support 100 active instance compared to 10 active instance supported earlier per terminal / host / node while connecting to the same back end IS.

• ISRA startup independent of “Print Services” and WQS Services running on IS: Earlier ISRA startup required that Print Services and WQS Services be running on IS irrespective of whether they are being used or not. Hence from this release ISRA would be independent of Print and WQS services running on IS.

• ISRA Console: Dynamic Logging and Auto JNDI look up: The LoadISRA utility from ISRA 3.4.0 has now been replaced with the ISRA Console (in ISRA 3.4 fp1 and above). This ISRA console has been developed to show the ra.xml properties in a well formatted table and also features buttons to enable/disable/edit logging levels dynamically.
  The dynamic update of logging allows the user to enable and change logging levels while the ISRA is running and without needing to restart the appserver. The console also features links to launch Sample Application and to view JVM statistics. This console is available as a Web Module (ISRAConsole.war) within ISRAConsole.ear and gets deployed automatically during the deployment of ISRAConsole.ear. This console is supplemented with jndiISRA.properties file which holds the JNDI Names of configured Connection Factories. The Sample Application login page now uses the jndiISRA.properties for the configured JNDI Names instead of web.xml (within ISRASample.war).

Layout of Distribution

The fix pack released would contain

• A self extracting executable called ISRA_fixpack_3_4_0_1.exe specific for Microsoft Windows Operating Environment, which extracts to
  • ISRA.jar
  • ISRA.rar
  • ISRAConsole.ear
  • FNImageViewer.ear
• An archive called ISRA_fixpack_3_4_0_1.tar specific for UNIX and LINUX flavors, which extracts to
  • ISRA.jar
  • ISRA.rar
  • ISRAConsole.ear
  • FNImageViewer.ear
• Readme.html
• ReleaseNotes.html

This fix pack contains the files to be replaced/updated in the original ISRA.rar /jar, FNImageViewer.ear.

ISRA Sample Application is now bundled within ISRAConsole.ear.

ISRA.rar which contains the Image Services Resource Adapter has the following structure:

RAR file--
|
|---ISRA.jar
|---META-INF--
|---MANIFEST.MF
|---ra.xml

FNImageViewer.ear, which contains the latest build (Build# 3.1.126) of IBM FileNet ImageViewer for ISRA has the following structure:

EAR file--
|
|---FNImageViewer.war
|---META-INF--
|---MANIFEST.MF
|---application.xml

ISRAConsole.ear which contains the ISRA Sample Application 3.4 fp1 (with Annot.xsl Version: 31106) has the following structure:

EAR file--
|---ISRAConsole.war
|---ISRASampleWEB.war
|---META-INF--
|---MANIFEST.MF
|---application.xml

ISRA.jar contains updated ISRA class files.

Supported Platforms

 

 

·            BEA WebLogic Server 8.1 SP6/9.0/9.1 (WLS) on Microsoft Windows 2003 Service Pack 1, Sun Solaris 9/10, HPUX 11i v1, IBM AIX 5.2 SP2/5.3 SP3 and RedHat Linux AS 3.0/4.0.

·             IBM WebSphere Application Server 5.1.1.x/6.0.2/6.1 (WAS) on Microsoft Windows 2003 Service Pack 1, Sun Solaris 9/10, HPUX 11i v1, IBM AIX 5.2 SP2/5.3 SP3 and RedHat Linux AS 3.0/4.0.

·             JBoss 4.0.x Application Server on Microsoft Windows 2003 Service Pack 1, Sun Solaris 9/10, HPUX 11i v1, IBM AIX 5.3 SP3(JBoss 4.0.4 only) and RedHat Linux AS 3.0/4.0

·             Oracle 10g (9.0.4) and 10g Release 3 (10.1.3) Server on Microsoft Windows 2003 Service Pack 1, Sun Solaris 9/10, HPUX 11i v1, IBM AIX 5.2 SP2/5.3 SP3 and RedHat Linux AS 3.0/4.0 .

·             Sun One 8.1/9.0 Server on Microsoft Windows 2003 Service Pack 1, Sun Solaris 9/10, HPUX 11i v1 and RedHat Linux AS 3.0/4.0

·             SAP NetWeaver 6.4 Server on Microsoft Windows 2003 Service Pack 1.

·             Sample Application supports Netscape 7.x and Internet Explorer 6.0.

·             ConnectionFactory is qualified with a secured JAAS Authentication Realm on additional Application Servers.

·             Daeja qualified with new IDM COLD Module: ISRA is qualified with the new Daeja version that is bundled the IDM module for rendering of COLD documents. This module enhances the alignment of COLD and background templates.

Installation and Deployment

 

Please refer the Readme for deployment steps of fix pack.

For deployment of ISRA.rar / ISRAConsole.ear / FNImageViewer.ear on specifc Application Servers please refer the documentation on IBM - Product Documentation for FileNet Image Services Resource Adapter for detailed steps.

Known Software Problems and Restrictions

1. "All information (Doc Class information, Users/Groups information, Menu Values, Indices List, Printer Attributes etc.), which is stored in cache will be visible only if cache is refreshed (after cache refresh interval) or when application server is restarted". E.g.: 
   1. Suppose a new user is added to IS. Existing users will not be able to see the listing of new user in annotation security or setting document security, if cache has not been refreshed or application server has not been restarted. 
   2. If we update a document class in IS then user will not see the document class in the doc class listing in AddDoc interaction until the cache has been refreshed or application server has been restarted. 
   3. If a user is deleted from IS and recreated, the ObjectID of the user will change, however ISRA will continue to hold the invalid ObjectID until the ISRA cache is automatically updated at the CacheRefreshInterval period. In this scenario, interactions involving Security objects might fail until cached meta-data is refreshed. ISRA cache can also be rebuilt by restarting the application server.
2. Workspace and Queue names should start with an alphabet (A-Z, a-z). It is always advisable to use an alphabetic as the first character and then enter any double-byte characters, to create workspaces and queues.

Example, Steps:

1. Go to ISRA Sample Application > Queue Maintenance.
2. Create a new Workspace with double-byte characters.

This will fail with error no 2533359663. fn_msg 2533359663. <WQS,0,47> Workspace names must begin with a letter (upper or lower case). 

BEA WebLogic Application Server

On WebLogic 8.1 Application Server, a blank page is displayed during login in ISRA Sample Application. To fix this problem, edit the file <WebLogic Installation Directory>\user_projects\mydomain\startWebLogic.cmd (or startWebLogic.sh for UNIX platforms) to include ISRA.jar in CLASSPATH environment variable, and restart the server. Alternatively, you can set ISRA.jar in the CLASSPATH on the server.

SAP NetWeaver Application Server

While deploying FNImageViewer on SAP NetWeaver Application Server 6.4, an error is thrown as "At least one <welcome-file> tag must exist in the <welcome-file-list> tag. This problem will be fixed in SAP NetWeaver WAS 6.4 SP19. Until this service pack is released, please refer ISRA Deployment Guide for SAP NetWeaver Application Server for a workaround to resolve this problem.

IBM WebSphere Application Server

 

 

1.       IBM WebSphere 5.1.1.x/6.0.2/6.1 Application Servers destroy the CCI connection stored in HTTP Session object on exit of doPost()/doGet() methods of Servlets or JSPs. To fix this problem in IBM WebSphere 5 apply the IBM WebSphere 5 Fix Pack 2. Please refer http://www.ibm.com/Search?y=11&lang=en&cc=us&q=PQ73966&Search.x=28&Search.y=11 for details on how to apply the fix pack.
For IBM WebSphere 6.0.2 and 6.1, please refer http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg1PK25725 to fix this problem.

2.       IBM WebSphere Application Server does not provide the crimson implementation of DocumentBuilderFactory class. The Sample Application uses crimson implementation of DocumentBuilderFactory class to implement the Remote printing functionality. Please refer to the IBM WebSphere Deployment guide, which gives detailed steps on how to use the crimson.jar with the Sample Application. For reference, the PMR number for the case opened with IBM is PMR 83866,756,000.

3.       IBM WebSphere will not destroy the last connection with IBM FileNet IS. IBM WebSphere creates parked connections because of which one user always remains logged on to IS. To fix this problem in IBM WebSphere 5 apply the IBM WebSphere 5 Fix Pack PK00210. Please refer
http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP&q1=PQ86338&uid=swg27004936&loc=en_US&cs=utf-8&lang=en for details on how to apply the fix pack.

4.      In case of failover scenarios, there is a possibility that the user may have to perform the operation again to complete the request. For example, in case of AddDoc interaction in the Sample Application,    ISRA will throw the "Invalid InputStream object" error if the primary server goes down.

5.      If a client application packages any external jars in the WEB-INF/lib of the application and the Web Module class loader is set to Parent Last, then a ClassCastException occurs. To fix this problem in IBM WebSphere 6.x, apply the IBM WebSphere fixpacks 6.0.2.15 and 6.1.0.2. Please refer http://www-1.ibm.com/support/docview.wss?uid=swg1PK26233 to apply this patch.   

FileNetImageViewer Related Issues

For All platforms -

Treatment of special characters like &, ", < and >. 

While saving annotations, FNImageViewer generates an xml file containing the details of each annotation. In case of STAMP and TEXT  annotations, if the text contains these special characters then FNImageViewer substitutes &, ", < and > by &amp; , &quot; , &lt; and &gt; , respectively. 

While retrieving annotations, FNImageViewer reads from an xml file, the details of each annotation. In the case of STAMP and TEXT annotations, it performs recursive substitution of &amp; , &quot; , &lt; and &gt; by &, ", < and >, respectively. Therefore, for instance, an annotation containing text as &amp;amp;amp;lt; or &amp;amp;lt; or even &amp; lt; will all be substituted by '<'. 

General Notes

Supportability on Development Platforms

IBM FileNet has not qualified ISRA and the ISRA Sample Application to run under development platforms such as WSAD, BEA Workshop, or any other development platforms. This is primarily because IBM FileNet Engineering may not be able to keep up with the dependencies on specific development platform configuration.

However, ISRA and ISRA Sample should be able to run under any development platform that provides managed environment and runtime support for JCA 1.0. Since, IBM FileNet has not qualified these development platforms with ISRA and ISRA Sample, it is customer's responsibility to determine the proper setup and/or configuration that enable ISRA and Sample Application to work under the specific development platform. If there are any problems during configuration, deployment, development or runtime relating to ISRA under these development platforms, it is the customer's responsibility to verify if the same problem also occurs under the qualified Application Server environment.

Globalization

ISRA supports all character sets supported by Image Services, which are single byte character sets, as well as some multi-byte character sets. Unicode character sets, such as AL16UTF16, AL32UTF8, or UTF8 are not supported at this time. For a detailed overview of the supported character sets, please refer to the Image Services System Administrators manual.

ISRA Supports

Note: ISRA is currently supported for production deployment only in the Managed Environment. If you experience any difficulties with the product media or ISRA, please contact your IBM FileNet Customer Support personnel for assistance.

ISRA Support

If you experience any difficulties with the product media or ISRA, please contact your IBM FileNet Customer Support personnel for assistance.

Contact Customer Support

For information about contacting customer support:

1. Navigate to the Information Management support page here.www.ibm.com/software/data/support
2. Select the appropriate IBM FileNet product from the "Select a category" list.
3. From the Product Support page, click Flash 8 Oct. 2007: How to get support for IBM FileNet products.

Notices and Trademarks

• IBM is a registered trademark of International Business Machines Corporation in the United States, other countries, or both.
• Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
• Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.
• Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. 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.
• Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
• UNIX is a registered trademark of The Open Group in the United States and other countries.
• Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
• ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office.
• IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency, which is now part of the Office of Government Commerce.
• Other company, product, or service names may be trademarks or service marks of others.