IBM DB2 Information Integrator OmniFind Edition
Installation Requirements for Enterprise Search
Version 8.2
Before using this information and the product it supports, be sure to read
the general information under "Notices."
This document contains proprietary information of IBM. It is provided under
a license agreement and Copyright law protects it. The information contained
in this publication does not include any product warranties, and any statements
provided in this manual should not be interpreted as such.
You can order IBM publications online or through your local IBM representative:
When you send information to IBM, you grant IBM a nonexclusive right to
use or distribute the information in any way it believes appropriate without
incurring any obligation to you.
Copyright International Business Machines Corporation 2004. All rights reserved.
US Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
About
the installation requirements
The Installation Requirements document describes supported operating system levels, prerequisite software, hardware requirements, supported data sources, and the installation program prompts for DB2(R) Information Integrator OmniFind(TM) Edition (enterprise search).
DB2 Information Integrator
OmniFind Edition provides a
technology called enterprise search. To install the enterprise search
solution, ensure that you have the correct prerequisite software. The
installation program for enterprise search will help you install the
prerequisite software except for operating systems and
WebSphere(R)
Application Server fix packs.
Supported
operating systems and required software for enterprise search
Before you install enterprise search, ensure that you have the supported and required hardware and software.
Supported operating systems
Enterprise search is supported on
the following operating systems:
- AIX(R) 5L and 5.2 with the August 2004 C++ Runtime for
AIX PTF
- Red Hat Enterprise
Linux(TM) Advanced Server
Version 3.0, Update 2
- SUSE
Linux Enterprise Server 8,
service pack 3 (United Linux 1.0 SP3)
- Microsoft(R) Windows(R) 2000 Advanced Server, service pack
4
To download the AIX 5.2 PTF:
- Go to the following Web site:
www.ibm.com/software/awdtools/vacpp/support/
- Under download, click
All updates
(fixes, patches, etc.).
- In the
Additional
search terms field, type
AIX
PTF August 2004. In the
Platforms/Operating system field, select
AIX. In the
Download
type, select -Updates. Click
Go.
- In the search results list,
select the link for August 2004 C++ Runtime for AIX PTF.
See the AIX documentation for
instructions on installing PTFs.
Required software
Enterprise search requires the
following software:
- IBM(R) DB2 Universal Database(TM) Enterprise Server Edition,
Version 8.2
- IBM DB2 Universal Database
Information Center, Version 8.2
- IBM DB2 Universal Database
Run-time Client, Version 8.2 (required only for a multiple server
installation)
- IBM WebSphere Application Server Network Deployment,
Version 5.1.1, which includes the Web application server, the IBM HTTP
server, and Deployment Manager; version 5.1.1 refers to version 5.1 with
Fix Pack 1
Optional software
To crawl data sources such as
Lotus Domino databases, DB2 Content Manager databases, federated
relational databases, or create custom search applications, you can
install:
- IBM Lotus(R) Domino(R) Server 6.0.2 for Linux and AIX or Lotus Notes
6.0.2 or later for Windows (to search Lotus Notes databases). This
product is not required to install enterprise search. See the Lotus
Domino Server documentation for installation instructions.
- IBM
DB2 Content Manager
Toolkit, Version 8.2 for Linux or IBM
DB2 Information Integrator
for Content, Version 8.2 for Windows and AIX (to search DB2 Content
Manager databases). This product is not required to install enterprise
search. See the DB2 Content Manager documentation for installation
instructions.
- IBM DB2 Information Integrator
Standard Edition, Version 8.2 (to search federated relational data
sources). This product is not required to install enterprise search. See
the DB2 Information Integrator documentation for installation
instructions.
- Java(TM) Development Kit 1.3.x or 1.4.x. (JDK 1.5 is
not supported) is required to compile the
Java search
applications that are created with the enterprise search APIs. These
JDKs are not required to install enterprise
search.
Hardware
and disk space requirements for enterprise search
Hardware requirements depend on your operating system and your intended use for enterprise search.
Hardware requirements
Disk space requirements can vary
depending on the number of documents and the size of documents that you
want to crawl and index. These requirements assume that you build
indexes continually, which means that new documents are added, removed,
or updated in the index.
The following list describes the
minimum hardware requirements and minimum disk space requirements for a
single server configuration and a multiple server configuration:
- Small solutions
- Single server configuration:
- 2 or more processors: 2.0 GHz or
more for Intel and AMD; 1.5 GHz or more for RISC
- 4 - 6 GB of RAM (Add 1 to 2 GB of
RAM for each additional active collection.)
- 200 GB of disk space based on 1
000 000 documents in one or more collections with an average document
size of 20 KB
- Medium solutions
- Four-server configuration:
- 2 or more processors: 2.0 GHz or
more for Intel and AMD; 1.5 GHz or more for RISC
- 4 - 6 GB of RAM on each server
- 2 TB total disk space based on 7
000 000 documents in one or more collections with an average document
size of 20 KB
- Large solutions
- Four-server configuration:
- 4 or more processors: 2.0 GHz or
more for Intel and AMD; 1.5 GHz or more for RISC
- 8 GB of RAM on each server (4 GB
of RAM for Windows)
- 6 TB total disk space based on 10
000 000 documents in one or more collections with an average document
size of 20 KB
Supported
data sources for enterprise search
With enterprise search, you can gather data from many data sources. You can gather, or crawl, more data sources by installing the DB2 Content Manager script, the Lotus Notes(R) script, and DB2 Information Integrator.
The following table describes the
data sources, versions of the data sources, and the operating systems
that the enterprise search crawlers can crawl:
| Data source |
Version |
Operating system |
| IBM DB2
Content Manager |
8.2 |
Linux, AIX, Windows |
| IBM DB2
Information Integrator federated sources |
- DB2 Universal Database for
z/OS(R), Version 7.1 or
later
- Informix(R) IDS, Version 9 or later
- Oracle 9i
|
- Informix: Linux, AIX,
Windows
- Oracle: Linux, AIX,
Windows
|
| IBM DB2
Universal Database |
8.1 or
later |
Linux,
AIX, Windows, or Solaris |
| IBM
Lotus
Domino
Server |
Release
5.0.9a or later or Release 6.0 or later |
Linux,
AIX, Windows, or Solaris |
| Microsoft Exchange Server |
2000 or
2003 |
Windows |
| Microsoft
Windows file system |
Not
applicable |
Windows |
| Network
news transfer protocol (NNTP) |
Not
applicable |
Not
applicable |
| UNIX(R) file system |
Not
applicable |
UNIX,
Linux, and AIX |
| Venetica
sources |
FileNet
Panagon Content Services, Version 5.3 and Version 5.4 and Documentum,
Version 5 |
Not
applicable |
| Web (HTTP
or HTTPS) |
Not
applicable |
Not
applicable |
Enterprise
search installation prompts for Linux and AIX
Review the installation prompt information for enterprise search before you install any software.
Your installation will vary
depending on your current system configuration. For example, if you have
some or all of the prerequisite software already installed, you will see
different installation prompts than if you did not install the
prerequisite software. See Supported
operating systems and required software for enterprise search for information about supported software.
The following lists describe
installation prompts that you might see during the enterprise search
installation. Use the enterprise search installation program to help you
install the prerequisite software and then install the enterprise search
components.
Installation prompts for DB2 Universal Database
- CD image directory for DB2 UDB installation
- If DB2 UDB is not already
installed, provide the directory for the CD image.
- DB2 UDB installation directory
- If DB2 UDB is installed, provide
the installation directory.
- DB2 administrator user ID
- Provide the user ID for the DB2
administrator.
- DB2 administrator group
- Provide the group ID for the DB2
administrator.
- DB2 administrator password
- Provide the password for the for
the DB2 administrator user ID.
- DB2 administrator home directory
- Provide the home directory for
the DB2 administrator.
- DB2 instance ID
- Provide the DB2 instance
ID.
- DB2 instance group
- Provide the DB2 instance group
ID.
- DB2 instance password
- Provide the DB2 instance
password.
- DB2 instance home directory
- Provide the home directory for
the DB2 instance.
- DB2 fenced ID and password
- A fenced process runs in a
separate process from the database manager. Provide the ID and password
for the fenced user.
- DB2 fenced group
- Provide the group ID for the
fenced user.
- DB2 fenced home directory
- Provide the home directory for
DB2 UDB.
Installation prompts for WebSphere Application Server Network Deployment
- CD image directory for WebSphere Application Server
- If WebSphere Application Server
is not already installed, provide the directory for the CD image.
- CD image directory for WebSphere Application Server Deployment Manager
- If WebSphere Application Server
Deployment Manager is not already installed, provide the directory for
the CD image.
- Installation directories for WebSphere Application Server Deployment Manager and WebSphere Application Server
- If the WebSphere products are
already installed, provide the installation directories for the IBM HTTP
server, the application server, and Deployment Manager.
- Security user ID and security password for WebSphere Application Server
- Provide the user ID and
password if WebSphere Application Server is already installed and
WebSphere security is enabled.
Installation prompts for DB2 UDB Run-time Client
These prompts appear only when you
choose to install enterprise search on multiple servers. You do not
install the DB2 Universal Database Run-time Client for a single server
installation.
- DB2 UDB Run-time Client installation image
- If the DB2 UDB Run-time Client
is not already installed, provide the directory for the CD image.
- DB2 UDB Run-time Client user name
- Provide the user name for the
DB2 UDB Run-time Client.
- DB2 UDB Run-time Client group name
- Provide the group name for the
DB2 UDB Run-time Client.
- DB2 UDB Run-time Client password
- Provide the password for the
DB2 UDB Run-time Client user name.
- DB2 UDB Run-time Client home directory
- Provide the home directory for
the DB2 UDB Run-time Client.
Installation prompts for enterprise search
- Single server installation or multiple server installation
- Select whether you will install
enterprise search and its prerequisite software on one server or on
four, distributed servers.
- Enterprise search server component
- For a multiple server
installation, select which enterprise search component that you want to
install. You should install the enterprise search components in the
following order:
- Crawler server
- Search servers (two)
- Index server
You will
need to record the information that you specify when you install the
crawler server and the search servers so that you can provide that
information when you install the index server.
- License agreement
- Accept or decline the license
agreement. If you decline it, the installation program will stop.
- Enterprise search administrator ID and password
- Provide an administrator user
ID and password. This user ID and password must be the same on all
enterprise search servers in a multiple server configuration. Select the
check box Create a user to create a user that does not currently
exist on the system. Do not select this check box if you are using an
existing user ID and password.
- Installation directory
- Provide the installation
directory for enterprise search. The installation directory stores files
that do not usually change. The enterprise search documentation uses
ES_INSTALL_ROOT to refer to the enterprise search
installation directory.
Important:
For
a multiple server installation, this directory must be the same on all
four servers.
- Data directory
- Provide the data directory for
enterprise search. The data directory stores files from the crawlers,
the parser, the index, and other files that are regularly updated. The
enterprise search documentation uses
ES_NODE_ROOT to refer to the enterprise search data
directory.
- Host name and port for this computer
- Provide the host name and port
for the computer on which you are installing enterprise search. This
port is used for internal enterprise search communication.
- Languages
- Select one or more languages
for this installation. English is installed in addition to the language
that you select. If language files for the selected language are not
available for the product or the documentation or both, the system
defaults to English.
- DB2 UDB information
- Provide the following
information:
- DB2 database name: The default
database name is fountain. This is the database that is used by
the enterprise search crawlers.
- DB2 instance name: The default
instance name is db2inst1. This is the instance for the DB2
database that is used by the enterprise search crawlers.
- Table space path: The table space
is where the DB2 database that is used by enterprise search is stored.
The table space directory should be on a partition or file system that
can store a large amount of data.
- Install WebSphere Application Server Network Deployment or use an existing version
- If you choose to use an
existing version of WebSphere Application Server Network Deployment,
ensure that it is version 5.1. If you installed WebSphere Application
Server Network Deployment, Version 5.1, which includes WebSphere
Application Server, the HTTP server, and Deployment Manager, download
and install Fix Pack 1 for the base and ND. If you allow the enterprise
search installation program to install WebSphere Application Server
Network Deployment and its components, you install Fix Pack 1 after the
enterprise search installation. If you already installed the WebSphere
products, you can install the fix packs.
- Node name for the WebSphere Application Server instance and host name for WebSphere Application Server
- The node name, which is
typically the short host name, is used for administration, and it must
be unique within its group of nodes (cells). For example, if the host
name is mynode.mysite.us.ibm.com, type
mynode for the short name. Also, provide the
host name for this installation of WebSphere Application Server. Use the
fully qualified DNS name. For example, type
mynode.mysite.us.ibm.com.
- DB2 UDB server information for the crawler server for a multiple server installation
- Provide the following
information that is used on the index server to catalog the database
that is on the crawler server:
- Port: The port on the DB2 UDB
computer that DB2 UDB uses to communicate with remote clients.
- Database name on the crawler
server: The instance for the DB2 database that is used by the enterprise
search crawlers. The default database name is
fountain.
- Database alias: A local alias name
for the DB2 database. The default database alias name is
fountain.
- Node name: The name used by the
remote client when cataloging the database.
- Instance name: The DB2 instance
name. The default instance name is
db2inst1.
- Index server installation for a multiple server installation
- When you install the index
server, you must provide the following information about the other
enterprise search servers:
- The host name and port for the
crawler server
- The data directory for the
crawler server
- The host names and ports for each
search server
- The data directory for each
search server
- Launch First Steps
- Select this check box if you
want to start the First Steps program. From the First Steps program, you
can verify your installation, start the enterprise search system, start
the administration console, or review the documentation.
Enterprise
search installation prompts for Windows
Review the installation prompt information for enterprise search before you install any software.
The installation prompts will
vary depending on your current system configuration. For example, if you
have some or all of the prerequisite software already installed, you
will see different installation prompts than if you did not install the
prerequisite software. See Supported
operating systems and required software for enterprise search for information about supported software.
The following lists describe
installation prompts that you might see during the enterprise search
installation. Use the enterprise search installation program to help you
install the prerequisite software and then install the enterprise search
components.
Installation prompts for DB2 Universal Database
- CD image directory for DB2 UDB installation
- If DB2 UDB is not already
installed, provide the directory for the CD image.
- DB2 UDB installation directory
- If DB2 UDB is installed,
provide the installation directory.
- DB2 administrator user ID and password
- Provide the DB2 administrator
ID that has full authorities and privileges for DB2 UDB.
Installation prompts for WebSphere Application Server Network Deployment
- CD image directory for WebSphere Application Server
- If WebSphere Application
Server is not already installed, provide the directory for the CD
image.
- CD image directory for WebSphere Application Server Deployment Manager
- If WebSphere Application
Server Deployment Manager is not already installed, provide the
directory for the CD image.
- Installation directories for WebSphere Application Server Deployment Manager and WebSphere Application Server
- If the WebSphere products are
already installed, provide the installation directories for the IBM HTTP
server, the application server, and Deployment Manager.
- Setting up the IBM HTTP server as a Windows service
- You can choose to run the IBM
HTTP server as a Windows service.
- Setting up WebSphere Application Server as a Windows service
- You can choose to run
WebSphere Application Server as a Windows service.
- Windows service user ID and password for WebSphere Application Server
- Provide the ID and password
for the WebSphere Application Server Windows service.
- Setting up WebSphere Application Server Network Deployment as a Windows service
- You can choose to run
WebSphere Application Server Network Deployment as a background
service.
- Windows service user ID and password for WebSphere Application Server Network Deployment
- Provide the Windows service
user ID and password for the WebSphere Application Server Network
Deployment.
- Security user ID and security password for WebSphere Application Server
- Provide the user ID and
password if WebSphere Application Server is already installed and
WebSphere security is enabled.
Installation prompts for DB2 UDB Run-time Client
These prompts appear only when
you choose to install enterprise search on multiple servers. You do not
install the DB2 Universal Database Run-time Client for a single server
installation.
- DB2 UDB Run-time Client installation CD image directory
- If the DB2 UDB Run-time
Client is not already installed, provide the directory for the CD
image.
- DB2 UDB Run-time Client user name
- Provide the user name for
the DB2 UDB Run-time Client.
- DB2 UDB Run-time Client password
- Provide the password for the
DB2 UDB Run-time Client user name.
Installation prompts for enterprise search
- Single server installation or multiple server installation
- Select whether you will
install enterprise search and its prerequisite software on one server or
on four, distributed servers.
- Enterprise search server component
- For a multiple server
installation, select which enterprise search component that you want to
install. You should install these components in the following order:
crawler server, search server (two servers), and index server. You will
need to record the information that you specify when you install the
crawler server and the search servers so that you can provide that
information when you install the index server.
- License agreement
- Accept or decline the
license agreement. If you decline it, the installation program will
stop.
- Enterprise search administrator ID and password
- Provide an administrator
user ID and password. This user ID and password must be the same on all
enterprise search servers in a multiple server configuration. Select the
check box Create a user to create a user that does not currently
exist on the system. Do not select this check box if you are using an
existing user ID and password.
- Installation directory
- Provide the installation
directory for enterprise search. The installation directory stores files
that do not usually change. The enterprise search documentation uses
ES_INSTALL_ROOT to refer to the enterprise search
installation directory.
Important:
For
a multiple server installation, this directory must be the same on all
four servers.
- Data directory
- Provide the data directory
for enterprise search. The data directory stores files from the
crawlers, the parser, the index, and other files that are regularly
updated. The enterprise search documentation uses
ES_NODE_ROOT to refer to the enterprise search data
directory.
- Host name and port for this computer
- Provide the host name and
port for the computer on which you are installing enterprise search.
This port is used for internal enterprise search communication.
- Languages
- Select one or more languages
for this installation. English is installed in addition to the language
that you select. If language files for the selected language are not
available for the product or the documentation or both, the system
defaults to English.
- DB2 UDB information
- Provide the following
information:
- DB2 database name: The default
database name is fountain. This is the database that is used by
the enterprise search crawlers.
- DB2 instance name: The default
instance name is db2. This is the instance for the DB2 database
that is used by the enterprise search crawlers.
- Table space path: The table
space is where the DB2 database that is used by enterprise search is
stored. The table space directory should be on a partition or file
system that can store a large amount of data.
- Install WebSphere Application Server or use an existing version
- If you choose to use an
existing version of WebSphere Application Server Network Deployment,
ensure that it is version 5.1. If you installed WebSphere Application
Server Network Deployment, Version 5.1, which includes WebSphere
Application Server, the HTTP server, and Deployment Manager, download
and install Fix Pack 1 for the base and ND. If you allow the enterprise
search installation program to install WebSphere Application Server
Network Deployment and its components, you install Fix Pack 1 after the
enterprise search installation. If you already installed the WebSphere
products, you can install the fix packs.
- Node name for the WebSphere Application Server instance and host name for WebSphere Application Server
- The node name, which is
typically the short host name, is used for administration, and it must
be unique within its group of nodes (cells). For example, if the host
name is mynode.mysite.us.ibm.com, type
mynode for the short name. Also, provide the
host name for this installation of WebSphere Application Server. Use the
fully qualified DNS name or short DNS name. For example, type
mynode.mysite.us.ibm.com.
- DB2 UDB server information for the crawler server for a multiple server installation
- Provide the following
information that is used on the index server to catalog the database
that is on the crawler server:
- Port: The port on the DB2 UDB
computer that DB2 UDB uses to communicate with remote clients.
- Database name on the crawler
server: The instance for the DB2 database that is used by the enterprise
search crawlers. The default database name is
fountain.
- Database alias: A local alias
name for the DB2 database. The default database alias name is
fountain.
- Node name: The name used by the
remote client when cataloging the database.
- Instance name: The DB2 instance
name. The default instance name is
db2.
- Index server installation for a multiple server installation
- When you install the index
server, you must provide the following information about the other
enterprise search servers:
- The host name and port for the
crawler server
- The data directory for the
crawler server
- The host names and ports for
each search server
- The data directory for each
search server
- Restart now
- After you install the
enterprise search components, you can allow the installation program to
restart your system. For a multiple server installation, you must
restart each enterprise search server. After the system is restarted,
the First Steps program will start.
- Launch First Steps
- Select this check box if you
want to start the First Steps program. From the First Steps program, you
can verify your installation, start the enterprise search system, start
the administration console, or review the documentation.
Notices
This information was developed for
products and services offered in the U.S.A. IBM may not offer the
products, services, or features discussed in this document in all
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 give 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/region 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/region 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
that 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:
Outside In ((R)) Viewer
Technology, (C) 1992-2004 Stellent, Chicago, IL., Inc. All Rights
Reserved.
IBM XSLT Processor Licensed
Materials - Property of IBM (C) Copyright IBM Corp., 1999-2004. All
Rights Reserved.
Trademarks
This topic lists IBM trademarks and certain non-IBM trademarks.
The following terms are
trademarks of International Business Machines Corporation in the United
States, other countries, or both:
IBM
AIX
AIX 5L
DB2
DB2 Universal Database
Domino
Informix
Lotus
Lotus Notes
Notes
OmniFind
WebSphere
xSeries
z/OS
The following terms are
trademarks or registered trademarks of other companies:
Java and all Java-based
trademarks and logos are trademarks or registered 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 Inside (logos),
MMX and Pentium are trademarks of Intel 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.
Linux is a trademark of Linus
Torvalds in the United States, other countries, or both.
Other company, product or
service names may be trademarks or service marks of others.