IBM Corporation

Readme file for: IBM® FileNet® Application Connector for SAP® R/3®, J2EE Edition
Component Name: Application Connector for SAP® R/3®, J2EE Edition
Component Release: 2.1
Update Name: Interim Fix 7
Release Date: Apr 2010
Platforms: AIX, HP-UX, Linux, Solaris, Windows (as supported by application servers)
Online version of Readme: ReadMe.html (Follow the link on this page)
Note: The most current version of the Readme can always be found online.

Contents

Download location for Interim Fix 7

Application Connector for SAP 2.1 Interim Fix 7 can be downloaded from the following location:
http://www-01.ibm.com/support/docview.wss?rs=3247&context=SSCMRFF&context=SSC4JMD&uid=swg27011933&loc=en_US&cs=utf-8&lang=en

Below is a list of components, platforms, and file names that apply to this Readme file.

Prerequisites and co-requisites

ACSAP R/3 J2EE 2.1 must be installed before installing this interim fix.

Before downloading Application Connector for SAP 2.1 Interim Fix 7, perform the following steps:

1. Ensure that your system meets all of the system requirements. Please refer to the ACSAP R3/J2EE hardware and software requirements document accessible on the Product Documentation page for ACSAP.

   This action prevents technical problems that might occur after the installation and configuration of the interim fix.

2. Review the Flashes and open Authorized Problem Analysis Reports (APARs) on the IBM Software Support web site for FileNet Application Connector for SAP R/3.

   Open APARs describe defects that are not yet addressed in a fix release, and might contain workarounds that will impact your use of Interim Fix 7.

3. Read the "Known problems and workarounds" section of this readme.
4. If you already have ACSAP installed and have obtained special fixes, contact IBM® support to determine whether you need an updated version of the fixes before you install Interim Fix 7. This helps to ensure that your system is in a consistent state and that no special fixes are lost.

Known Issues and Limitations

Configuration Tool Subsystem (CTS)

• The ACSAP R3/J2EE CTS user interface is optimized for a screen resolution of 1024 x 768.
• Alignment problem in tree menu (DTS 123448)

  In the left pane of the Configuration Tool, strings that spill beyond the first line appear misaligned.

• Unable to retrieve SAP host name on Solaris (DTS 158383)

  On Solaris, ACSAP R3/J2EE may not able to retrieve the host name of the requesting SAP system; instead, it gets the IP Address. A suggested workaround is to enter the IP address instead of the host name of the SAP server when specifying the SAP system configuration.

• In some cases, the ‘Tree’ of the Configuration Tool Subsystem, running on the Secondary servers does not get refreshed automatically (DTS 158384)

  A suggested workaround is to press the F5 key or click Refresh on your browser to reload the new configuration.

• The configuration file export feature does not work on Solaris with Netscape 7.1 (DTS 158385)

  On Solaris with Netscape 7.1, an attempt to export the configuration file results in the error message "Unable to save temporary file". A suggested workaround is to upgrade to Netscape 7.2.

• In the Configuration Tool Subsystem, the usage of certain non-English characters in the "Document Class", "Workspace" and "Queue" fields when using the Create Queue option may result in an error (DTS 158390)

  This problem is due to ISRA restrictions. A suggested workaround is to avoid using non-English characters in those fields.

• A "Configuration Load Data Error" occurs while opening the Administrative Console on Sun Java System Application Server on UNIX and Linux platforms (DTS 190510)

  The following settings need to be added to the server.policy file of the application server. The default location of the file is /var/opt/sun/appserver/domains/domain1/config/server.policy .

  permission java.util.PropertyPermission "file.encoding", "write";
  permission java.security.SecurityPermission "putProviderProperty.IAIK", "write";
  permission java.security.SecurityPermission "insertProvider.IAIK", "write";
  permission java.net.SocketPermission "*", "connect, listen, resolve";
  permission java.lang.RuntimePermission "modifyThreadGroup";
  permission java.io.FilePermission "<<ALL FILES>>", "read, write, delete, execute";
  permission java.lang.RuntimePermission "setContextClassLoader";
  permission java.util.PropertyPermission "*", "read,write";
  permission java.util.PropertyPermission "javax.xml.parsers.SAXParserFactory", "write";
  permission java.lang.RuntimePermission "*", "write";

  Please also refer to the “Troubleshooting and Software Restrictions” section of the Installation and Configuration manual for ACSAP 2.1 for information on additional configuration settings.

• Errors may occur while adding an annotation to an IS document on WebSphere 5.1.x (DTS 197864)

  The following steps have to be performed to resolve the above problem:

  1. Extract the acsap.war contents using any available zip file tool, copy the ISRA.jar file into the web-inf/lib folder, and re-create the acsap.war file.
  2. Redeploy ACSAP on WebSphere.
  3. Change the Classloader Mode settings of the ACSAP application to PARENT_LAST on WebSphere.
  4. Set the WAR Classloader Policy to Application.

  Note: There is no need to change the Classloader Mode settings of the ACSAP application to PARENT_FIRST on WebSphere 6.0.2.13.

• Globalization: Unable to display the actual Document Class Name in the Document Class drop down menu (DTS 202299)

  The Document Class Symbolic Name is displayed in the Document Class drop down menu instead of the actual Document Class Name.

• The Default Workplace URL got deleted from the CTS (DTS 202560)

  If an ACSAP R3/J2EE 2.1 "CE adapter only" deployment is upgraded to an "IS and CE" deployment, the Default Workplace URL gets deleted from the CTS. The URL has to be restored manually.

• Globalization: Unable to retrieve configuration details (DTS 202567)

  In non-English environments involving CE, if an Object Store name or a Custom Folder name selected on the Document Class page contains non-English characters, configuration details are lost after a reboot. A suggested workaround is to avoid using non-English characters in the aforementioned labels.

• The Users/Groups field on IS Archive pages is enabled by default when the CTS is opened in Netscape 8.1 (DTS 202781)

  When using the CTS in Netscape 8.1, the Users/Groups field in the Archive page of an IS repository is enabled by default, irrespective of the status of the Custom Annotation field.

• Globalization: "Repository Name" and "Repository Description" fields get corrupted while creating a repository on WebSphere Application Server (DTS 203178)

  When connecting to ACSAP R3/J2EE with the browser language set to Japanese, the "Repository Name" and "Repository Description" fields get corrupted after entering Japanese Extended Characters on WebSphere Application Server.

• Globalization: Folder names with Japanese extended characters on Document Class pages are corrupted (DTS 203241)

  Folder names get corrupted when a folder with Japanese extended characters in its name is assigned to a Document Class.

• PE Router URL label incorrectly defined in Configuration Tool Subsystem for P8 4.0 (DTS 217777)

  On the Archive page, in the PE Router URL field, the user needs to provide either the PE Router URL or Connection Point depending on the P8 version. For P8 3.5.x, the user needs to provide the PE Router URL and for P8 4.0, provide the Connection Point.

ACSAP Client for P8 and Folder Display

• The CDDP request does not work in Netscape and in Internet Explorer on Windows 2003 (DTS 155330)

  The Display Local File (CDDP Request) does not work with Netscape and Internet Explorer on Windows 2003.

• Unable to create large documents using the CE OLE Client (DTS 153378)

  Creating large documents (for example, greater than 50 MB) using ACSAP Client for P8 results in poor response time compared to IDM Desktop for R/3.

• Opening documents using the Folder Display option in the SAP Document Viewer displays the login screen (DTS 155481)

  Instead of displaying a document from the Content Engine repository using the folder display functionality, the login window of Content Engine appears when a folder is opened using the SAP Document Viewer.

• FileNet Java Viewer control menu appears Black (DTS 158386)

  Using the HTML control to view a document from SAP using the "pure thin" mode displays the FileNet Java Viewer control menu in black.

• CE documents get linked to an IS repository successfully after changing the repository type in the CTS (DTS 201792)

  When using the JBoss application server on HP-UX, it is possible to link CE documents to an IS archive if the backend FileNet repository type is changed from CE to IS in the CTS.

SAP

• Incorrect format of multipart data from SAP 4.6c

  SAP 4.6c may send incorrect multipart data when creating a document. In this case, the multipart data does not have an end boundary string. ACSAP R3/J2EE does not handle such requests and may not be able to create the document. Please refer to SAP message number 0000795168 for details.

• Exception thrown with incompatible SAP 4.6b seculib

  A Security Exception is thrown with SAP 4.6b because of an incompatible seculib. Please refer to SAP message number 0000795176 for details. ACSAP R3/J2EE works as expected with disabled security settings on SAP 4.6b.

• A "Document not existing in repository" error uccurs during document verification (DTS 151348)

  The following error occurs when using SAP 4.7 patch level 692: "Error during HTTP access: IF_HTTP_CLIENT->RECEIVE 1 HTTPIO_PLG_NO_MPI_INIT". According to SAP note 631790, there are two solutions to this problem:

  1. As a workaround, you can define a port for HTTP or you can deactivate the use of the HTTP plug-in by means of an entry in table SDOKPROF (NAME = USEHTTPPLG, VALUE = OFF).
  2. As a result, SAPHTTP is always used, regardless of the availability of the plug-in. The error is corrected with the following Patch level of SAP 6.20: 759 (ICM Patch Collection (XIV)) and above.
  
  
• An “Invalid Path” error is displayed and a dialog box opens asking the user to browse and select a new document when document linking using OLE is attempted

  The ArchiveLink protocol specification and SAP transaction(s) need to have the same protocol level setting (either 0045 or 0046) for SAPGUI to work properly when linking.

General

• Possible size restrictions for archived documents

  The file size that can be archived depends on the underlying Application Server. Most Application Servers are able to support files up to 2 GB in size.

• Create, Append, mCreate and Update requests on a document with zero bytes cause the system to stop responding (DTS 157301)

  This behavior is only exerted on JBoss application servers.

• A document is created in IS even if the "create" request fails due to an invalid note component (DTS 153917)

  The document is created without the note component.

• Documents exceeding the size of 122MB are not archived when the SAP Web Application Server (WAS) is used (DTS 169270)
  

  A TCP/IP error occurs on SAP WAS when an attempt is made to archive a document with a size of more than 122MB. A suggested workaround is to modify the value of the MaxRequestContentLength parameter to the desired document size using the Visual Administrator tool of the J2EE Engine. This parameter is listed under Dispatcher->HTTP Provider Service with a default value of 131072 KB.

• From ACSAP R3/J2EE 2.0.1 interim fix 4 onwards, initial logging is suppressed if the <USER HOME> directory is read-only

  In this case, a message is displayed on the Logging page in CTS after logging in: “Log File Directory is Read Only. To maintain logs, please choose a valid Directory”.

• Globalization: Both the program code and the localization resources are included in the acsap.jar file (DTS 200549)

  The ACSAP R3/J2EE 2.1 release includes both the program code and the localization resources in the acsap.jar file.

• Unable to delete ACSAP R3/J2EE 2.1 entries from the web.xml file after uninstalling portlets 4.0 (DTS 202190)

  ACSAP R3/J2EE 2.1 entries are not deleted from the web.xml file in Workplace after uninstalling portlets 4.0 using the main installer.

• After upgrading to ACSAP R3/J2EE 2.1 on UNIX platforms, ACSAP R3/J2EE 2.0.1 is not uninstalled (DTS 202196)

  On all UNIX-based platforms, the folder structure of ACSAP R3/J2EE 2.0.1 is not deleted when upgrading to ACSAP R3/J2EE 2.1.

• Unable to install portlets 3.5.x with the main installer on the AIX platform (DTS 202668)

  When installing portlets 3.5.x along with the ACSAP R3/J2EE 2.1 installer on an AIX machine, the error “same process id” occurs.

• Unable to update the acsap.war file after uninstalling any of the adapters from a combined "IS and CE" installation (DTS 202919)

  The acsap.war file does not get updated when uninstalling any of the adapters from an ACSAP installation.

• Globalization: An exception "sun.io.MalformedInput" occurs while using Red Hat Linux with WebSphere Application Server 6.1 (DTS 204005)

  This error occurs if the value of the environment variable LANG is set to en_US.UTF-8. A suggested workaround is to reset the value en_US.

• ACSAP R3/J2EE only supports major versions of documents stored in Content Engine

  ACSAP R3/J2EE only supports major versions of documents stored in Content Engine. For desktop linking and barcode linking, the selected P8 document must have at least one major version in CE. If the document has more than one major version, the following logic is applied:

  1. For barcode linking: If a user tries to process barcode entries for documents with no major version, an "Exception" is thrown. In case at least one major version exists, the latest major version is linked with SAP. (DTS 206471)
  2. For desktop linking (Browse Portlet), the user has the following options:
     1. Select current version: every time a display request is executed for this document from SAP, the most recent major version of the document is displayed.
     2. Select a specific version from the list of major versions of that document: the selected major version is displayed.

SAP Namespace Support

“SAP Namespace Support” refers to the ability to configure two or more SAP systems with the same AuthID.

It is common practice for a site to clone SAP systems for development, test, and production purposes. As new software is implemented, these cloned systems allow an implementation team to develop and test, and ultimately deploy, the new software, in an otherwise identical environment. With Namespace Support, most of the ArchiveLink configuration details within SAP can be left identical on multiple cloned systems, while allowing the management of the SAP documents to be different for each cloned system. This is facilitated within ACSAP R3/J2EE in a fashion that is transparent to SAP.

Namespace Support is accomplished in CTS by configuring different hostnames for SAP systems with a common AuthId. When this is done, all aspects of the underlying configuration for each SAP system can differ, including document class assignments, content repositories for a given ArchiveId, repository type (IS or CE), etc.

In this context, there are three types of requests:

1. HTTP Requests originating from the SAP Server: When such a request arrives, ACSAP R3/J2EE uses the specified AuthId to determine if two (or more) systems are configured for that AuthId. If so, the hostname is retrieved from the J2EE Server. If that hostname has been configured, the request is processed accordingly. If that hostname is not configured, the request is processed as if it came from the default SAP System.
2. OLE Requests originating from SAP Client: The OLE commands in SAP need to be configured to include the “SapSystemName” (i.e., hostname of the SAP server). This is a static field, and needs to be changed for each cloned SAP system. When the SapSystemName is present in the OLE commands, the request is processed accordingly.
3. HTTP Requests originating from the SAP Client (aka thin-client viewing): This type of request cannot be fully supported with the Namespace feature. There is insufficient information in the request provided by the SAP Client, and ACSAP R3/J2EE will attempt to process the request as if it originated from the default SAP System.

Portlet Customization

var DISPLAY_GUID        = true;
var DISPLAY_SUBJECT     = false;
var DISPLAY_STEP_NAME   = true;
var DISPLAY_STATUS      = true;
var DISPLAY_RECEIVED_ON = true;

var DISPLAY_GUID        = false;
var DISPLAY_SUBJECT     = true;
var DISPLAY_STEP_NAME   = false;
var DISPLAY_STATUS      = false;
var DISPLAY_RECEIVED_ON = true;

Preprocessor Extension

Starting with ACSAP 2.1 Interim Fix 6, the preprocessor of ACSAP supports handling of multi-page documents. When the preprocessor is called a new additional file is provided. The new file contains the temporary filenames of the components of the processed document. This file allows a unique identification of the document components during preprocessing even if several instances of the preprocessor run in parallel.

The filename of the new file can be obtained by replacing the file extension of the input file by ".input". The input filename is handed over to the preprocessor as a parameter during invocation (see Installation and Configuration Manual for more details).

The content of the new file has the following structure:

[Data]
file1
file2
...

[Note]
file1
file2
...

[Desc]
file1
file2
...

The order of the document components within a section in the new file corresponds to the order of the components in the processed document. This is important to preserve the order of the pages in a multi-page document.

The ".input"-file provides additional information to the preprocessor about the processed document. If the additional information is not needed the ".input"-file can be ignored. Therefore older implementations of the preprocessor are not affected by the new preprocessor extension.

Shared Configuration

The ACSAP feature "Shared Configuration" has been extended by ACSAP 2.1 Interim Fix 7. The "Shared Configuration" page of CTS now includes the field "URL of this secondary server". This field is optional but lets you specify the URL of the secondary server. The URL must have the following format:

http://thisSecondaryServer:port/acsap

thisSecondaryServer can be a hostname, a fully qualified hostname or a IP address. The "URL of this secondary server" is added to the configuration file of the primary server and used by the primary server to contact the secondary server. If you leave the field "URL of this secondary server" empty, ACSAP behaves as before the addition of this field: Depending on your network setup, it adds the IP address of the originator of the configuration sharing request or the IP address of a proxy to the configuration file of the primary server. If the IP address of a proxy is added, the primary server cannot contact the secondary server and sharing the configuration fails.

After a secondary server is registered with a primary server, the "URL of primary server" and "URL of this secondary server" fields are disabled to prevent inconsistencies. To edit the fields, you must change the secondary server to a primary server before you can specify it as a secondary server again.

Installation Information

Before proceeding with the installation process, please view the online version of the Readme file to verify information has not changed since the Readme file download.

Notes

When installing the interim fix, make sure the directory name for the interim fix installation is the same as that of the original ACSAP R3/J2EE 2.1 installation.

Should there be no Java Runtime Environmnent installed on the machine, the installer won’t be able to create acsap.war file if the user selects WebSphere, Sun One or SAP NetWeaver as the application server during installation.

If necessary, the interim fix can be installed multiple times on the same machine. This has no adverse effects on the product functionality.

Java Runtime Environment (JRE) 1.4.2 is bundled with the installer. The JRE is required for the application to run.

Prior to installing Interim Fix 7

Before installing this interim fix, perform the following steps:

1. Download the fix pack to an appropriate location
2. Uncompress the fix pack

Uncompressing the interim fix installer on UNIX and Linux platforms

The installers for UNIX and Linux platforms are compressed using gzip. Before you can apply the fix from this format, copy the image to a temporary directory and use gunzip and tar to extract the fix pack installation image.

To uncompress the fix pack installation images, perform the following steps:

1. Copy the gzipped image to a temporary location.
2. Change to the directory where you copied the image.
3. Enter the following command to uncompress the file:

   gunzip -c filename.tar.gz | tar -xvf - 

   where filename is the fix pack you are applying.
   Note:
   gunzip is part of the AIX 5L^(TM) default installation setup. If you do not have gunzip, install the rpm.rte fileset from the AIX 5L installation media. The rpm.rte fileset contains gunzip. You can also download gzip for AIX 5L from the Web: http://www.ibm.com/servers/aix/products/aixos/linux/rpmgroups.html

Installing Interim Fix 7

Run the operating system specific executable installer to install the interim fix.

Installing the ACSAP portlets for Workplace

After installing the interim fix, the updated portlet installers can be used to install the ACSAP portlets for the appropriate P8 Application Engine version and operating system. Previous portlet versions should be uninstalled before installation. The portlet installers are located at <InstallHome>/FileNet/ACSAP/expanded/acsap/portlets-installer.

Necessary tasks after installing Interim Fix 7

Redeploy the updated ACSAP application on the application server. Please refer to the ACSAP installation and configuration manual for a detailed description of the necessary steps for your application server.

Uninstalling Interim Fix 7

ACSAP fixes can not be uninstalled separately. Should it become necessary to revert to an earlier product version, it is necessary to uninstall the product and install the required version afterwards.

List of fixes included in Interim Fix 7

Interim Fix 7 is cumulative, i.e. it contains all the fixes already included in previous Interim Fixes/Fix Packs of ACSAP R/3 J2EE 2.1. The following tables contain the defects included in Interim Fix 7. The defects are ordered according to the Interim Fix/Fix Pack in which they were included for the first time.

New Fixes in ACSAP 2.1 Interim Fix 7:

Starting with ACSAP Interim Fix 7 the ACSAP portlets (ACBrowsePortlet and ACQCimPortlet) are supported on IBM FileNet Workplace XT 1.1.4.

New Fixes in ACSAP 2.1 Interim Fix 6:

Additionally to the fixes this Interim Fix contains the ACSAP Portlets 4.0 for Workplace (Browse Portlet and QCim Portlet) with renewed Java Certificates.

New Fixes in ACSAP 2.1 Interim Fix 5:

New Fixes in ACSAP 2.1 Interim Fix 4

New Fixes in ACSAP 2.1 Fix Pack 3

New Fixes in ACSAP 2.1 Fix Pack 2

New Fixes in ACSAP 2.1 Fix Pack 1

Copyright and Trademark Information

IBM Copyright and Trademark Information

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:

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, 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.

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.

Each copy or any portion of these sample programs or any derivative work must include a copyright notice as follows:

(C) (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. (C) Copyright IBM Corp. _enter the year or years_. All rights reserved.

Trademarks

1. The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both:
   • IBM
   • AIX
   • DB2
   • Tivoli
   • WebSphere
2. FileNet is a registered trademark of FileNet Corporation, in the United States, other countries, or both.
3. ValueNet is a registered trademark of FileNet Corporation, in the United States, other countries, or both.
4. 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.
5. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
6. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
7. UNIX is a registered trademark of The Open Group in the United States and other countries.
8. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
9. Other company, product, or service names may be trademarks or service marks of others.

Java^TM 2 Runtime Environment License Agreement

Sun Microsystems, Inc.
Binary Code License Agreement

for the

JAVA^TM 2 RUNTIME ENVIRONMENT (J2RE), STANDARD EDITION, VERSION 1.4.2_X

SUN MICROSYSTEMS, INC. ("SUN") IS WILLING TO LICENSE THE SOFTWARE IDENTIFIED BELOW TO YOU ONLY UPON THE CONDITION THAT YOU ACCEPT ALL OF THE TERMS CONTAINED IN THIS BINARY CODE LICENSE AGREEMENT AND SUPPLEMENTAL LICENSE TERMS (COLLECTIVELY "AGREEMENT").  PLEASE READ THE AGREEMENT CAREFULLY.

1.      DEFINITIONS. "Software" means the identified above in binary form, any other machine readable materials (including, but not limited to, libraries, source files, header files, and data files), any updates or error corrections provided by Sun, and any user manuals, programming guides and other documentation provided to you by Sun under this Agreement. “Programs” mean Java applets and applications intended to run on the Java 2 Platform, Standard Edition (J2SE^TM platform) platform on Java-enabled general purpose desktop computers and servers.

2.      LICENSE TO USE. Subject to the terms and conditions of this Agreement, including, but not limited to the Java Technology Restrictions of the Supplemental License Terms, Sun grants you a non-exclusive, non-transferable, limited license without license fees to reproduce and use internally Software complete and unmodified for the sole purpose of running Programs. Additional licenses for developers and/or publishers are granted in the Supplemental License Terms.

3.      RESTRICTIONS. Software is confidential and copyrighted. Title to Software and all associated intellectual property rights is retained by Sun and/or its licensors. Unless enforcement is prohibited by applicable law, you may not modify, decompile, or reverse engineer Software.  Licensee acknowledges that Licensed Software is not designed or intended for use in the design, construction, operation or maintenance of any nuclear facility. Sun Microsystems, Inc. disclaims any express or implied warranty of fitness for such uses. No right, title or interest in or to any trademark, service mark, logo or trade name of Sun or its licensors is granted under this Agreement. Additional restrictions for developers and/or publishers licenses are set forth in the Supplemental License Terms.

4.      LIMITED WARRANTY.  Sun warrants to you that for a period of ninety (90) days from the date of purchase, as evidenced by a copy of the receipt, the media on which Software is furnished (if any) will be free of defects in materials and workmanship under normal use.  Except for the foregoing, Software is provided "AS IS".  Your exclusive remedy and Sun's entire liability under this limited warranty will be at Sun's option to replace Software media or refund the fee paid for Software. Any implied warranties on the Software are limited to 90 days. Some states do not allow limitations on duration of an implied warranty, so the above may not apply to you. This limited warranty gives you specific legal rights. You may have others, which vary from state to state.

5.      DISCLAIMER OF WARRANTY.  UNLESS SPECIFIED IN THIS AGREEMENT, ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

6.      LIMITATION OF LIABILITY.  TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.  In no event will Sun's liability to you, whether in contract, tort (including negligence), or otherwise, exceed the amount paid by you for Software under this Agreement.  The foregoing limitations will apply even if the above stated warranty fails of its essential purpose. Some states do not allow the exclusion of incidental or consequential damages, so some of the terms above may not be applicable to you.

7.      SOFTWARE UPDATES FROM SUN. You acknowledge that at your request or consent optional features of the Software may download, install, and execute applets, applications, software extensions, and updated versions of the Software from Sun ("Software Updates"), which may require you to accept updated terms and conditions for installation. If additional terms and conditions are not presented on installation, the Software Updates will be considered part of the Software and subject to the terms and conditions of the Agreement.

8.      SOFTWARE FROM SOURCES OTHER THAN SUN. You acknowledge that, by your use of optional features of the Software and/or by requesting services that require use of the optional features of the Software, the Software may automatically download, install, and execute software applications from sources other than Sun ("Other Software"). Sun makes no representations of a relationship of any kind to licensors of Other Software. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR RELATED TO THE USE OF OR INABILITY TO USE OTHER SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states do not allow the exclusion of incidental or consequential damages, so some of the terms above may not be applicable to you.

9.      TERMINATION.   This Agreement is effective until terminated.  You may terminate this Agreement at any time by destroying all copies of Software.  This Agreement will terminate immediately without notice from Sun if you fail to comply with any provision of this Agreement.  Either party may terminate this Agreement immediately should any Software become, or in either party's opinion be likely to become, the subject of a claim of infringement of any intellectual property right. Upon Termination, you must destroy all copies of Software.

10.  EXPORT REGULATIONS. All Software and technical data delivered under this Agreement are subject to US export control laws and may be subject to export or import regulations in other countries.  You agree to comply strictly with all such laws and regulations and acknowledge that you have the responsibility to obtain such licenses to export, re-export, or import as may be required after delivery to you.

11.  TRADEMARKS AND LOGOS. You acknowledge and agree as between you and Sun that Sun owns the SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET trademarks and all SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET-related trademarks, service marks, logos and other brand designations ("Sun Marks"), and you agree to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www.sun.com/policies/trademarks. Any use you make of the Sun Marks inures to Sun's benefit.

12.  U.S. GOVERNMENT RESTRICTED RIGHTS.  If Software is being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), then the Government's rights in Software and accompanying documentation will be only as set forth in this Agreement; this is in accordance with 48 CFR 227.7201 through 227.7202-4 (for Department of Defense (DOD) acquisitions) and with 48 CFR 2.101 and 12.212 (for non-DOD acquisitions).

13.  GOVERNING LAW.   Any action related to this Agreement will be governed by California law and controlling U.S. federal law.  No choice of law rules of any jurisdiction will apply.

14.  SEVERABILITY. If any provision of this Agreement is held to be unenforceable, this Agreement will remain in effect with the provision omitted, unless omission would frustrate the intent of the parties, in which case this Agreement will immediately terminate.

15.  INTEGRATION.   This Agreement is the entire agreement between you and Sun relating to its subject matter.  It supersedes all prior or contemporaneous oral or written communications, proposals, representations and warranties and prevails over any conflicting or additional terms of any quote, order, acknowledgment, or other communication between the parties relating to its subject matter during the term of this Agreement.  No modification of this Agreement will be binding, unless in writing and signed by an authorized representative of each party.

SUPPLEMENTAL LICENSE TERMS

These Supplemental License Terms add to or modify the terms of the Binary Code License Agreement. Capitalized terms not defined in these Supplemental Terms shall have the same meanings ascribed to them in the Binary Code License Agreement. These Supplemental Terms shall supersede any inconsistent or conflicting terms in the Binary Code License Agreement, or in any license contained within the Software.

A.     Software Internal Use and Development License Grant. Subject to the terms and conditions of this Agreement, including, but not limited to the Java Technology Restrictions of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable, limited license without fees to reproduce internally and use internally the Software complete and unmodified for the purpose of designing, developing, and testing your Programs.

B.     License to Distribute Software. Subject to the terms and conditions of this Agreement, including, but not limited to the Java Technology Restrictions of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable, limited license without fees to reproduce and distribute the Software, provided that ( i) you distribute the Software complete and unmodified (unless otherwise specified in the applicable README file) and only bundled as part of, and for the sole purpose of running, your Programs, (ii) the Programs add significant and primary functionality to the Software, (iii) you do not distribute additional software intended to replace any component(s) of the Software (unless otherwise specified in the applicable README file), (iv) you do not remove or alter any proprietary legends or notices contained in the Software, (v) you only distribute the Software subject to a license agreement that protects Sun's interests consistent with the terms contained in this Agreement, and (vi) you agree to defend and indemnify Sun and its licensors from and against any damages, costs, liabilities, settlement amounts and/or expenses (including attorneys' fees) incurred in connection with any claim, lawsuit or action by any third party that arises or results from the use or distribution of any and all Programs and/or Software.

C.     License to Distribute Redistributables. Subject to the terms and conditions of this Agreement, including but not limited to the Java Technology Restrictions of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable, limited license without fees to reproduce and distribute those files specifically identified as redistributable in the Software "README" file ("Redistributables") provided that: ( i) you distribute the Redistributables complete and unmodified (unless otherwise specified in the applicable README file), and only bundled as part of Programs, (ii) you do not distribute additional software intended to supersede any component(s) of the Redistributables (unless otherwise specified in the applicable README file), (iii) you do not remove or alter any proprietary legends or notices contained in or on the Redistributables, (iv) you only distribute the Redistributables pursuant to a license agreement that protects Sun's interests consistent with the terms contained in the Agreement, (v) you agree to defend and indemnify Sun and its licensors from and against any damages, costs, liabilities, settlement amounts and/or expenses (including attorneys' fees) incurred in connection with any claim, lawsuit or action by any third party that arises or results from the use or distribution of any and all Programs and/or Software.

D.     Java Technology Restrictions. You may not modify the Java Platform Interface ("JPI", identified as classes contained within the "java" package or any subpackages of the "java" package), by creating additional classes within the JPI or otherwise causing the addition to or modification of the classes in the JPI.  In the event that you create an additional class and associated API(s) which ( i) extends the functionality of the Java platform, and (ii) is exposed to third party software developers for the purpose of developing additional software which invokes such additional API, you must promptly publish broadly an accurate specification for such API for free use by all developers.  You may not create, or authorize your licensees to create, additional classes, interfaces, or subpackages that are in any way identified as "java", " javax", "sun" or similar convention as specified by Sun in any naming convention designation.

E.      Source Code. Software may contain source code that, unless expressly licensed for other purposes, is provided solely for reference purposes pursuant to the terms of this Agreement. Source code may not be redistributed unless expressly provided for in this Agreement.

F.      Third Party Code. Additional copyright notices and license terms applicable to portions of the Software are set forth in the THIRDPARTYLICENSEREADME.txt file. In addition to any terms and conditions of any third party opensource/freeware license identified in the THIRDPARTYLICENSEREADME.txt file, the disclaimer of warranty and limitation of liability provisions in paragraphs 5 and 6 of the Binary Code License Agreement shall apply to all Software in this distribution.

For inquiries please contact: Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A