Infosrv Pre Install Checklist v801

Information Platform and Solutions
Center of Excellence
IBM Information Server

Preinstallation Checklist
IBM Information Platform and Solutions

April 25, 2008
IBM Information Server Preinstallation Checklist April 25, 2008 1 of 50

© Copyright IBM Corp. 2008. All rights reserved.
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 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 is for planning purposes only. The information herein is subject to change before the products
described become available.
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. If you are viewing this information softcopy, the
photographs and color illustrations may not appear.

Trademarks
IBM trademarks and certain non-IBM trademarks are marked at their first occurrence in this document.
See www.ibm.com/legal/copytrade.shtml for information about IBM trademarks.
The following terms are trademarks or registered trademarks of other companies:
Adobe, Acrobat, Portable Document Format (PDF), and PostScript are either registered trademarks or trademarks of
Adobe Systems Incorporated in the United States, other countries, or both.
Cell Broadband Engine and Cell/B.E. are trademarks of Sony Computer Entertainment, Inc. in the United States,
other countries, or both and is used under license therefrom.
Intel®, Intel logo, Intel Inside® logo, Intel Centrino™, Intel Centrino logo, Celeron®, Intel Xeon™, Intel
SpeedStep®, Itanium® and Pentium® are trademarks of Intel Corporation in the United States, other countries, or
both.
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.
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.

Document Goals
Intended Use This document provides a checklist of prerequisites that must be verified before installing
IBM Information Server. It is intended to minimize the time required to successfully install
and configure IBM Information Server and to document the requirements in one area.
The information in this document is based on field experiences. In some cases, the
recommendations documented here may differ from the product documentation. Except
where noted, this document is intended to supplement, not replace the product
documentation.
Target Audience The primary audience for this document is administrators of IBM Information Server.
Information in certain sections may also be relevant for technical architects, system
administrators, and developers.
Product Version This document is intended for the following product releases:
IBM Information Server 8.0.1 and 8.0.1 Fix Pack 1a.
Document Conventions
This document uses the following conventions:
Convention Usage
Bold In syntax, bold indicates commands, function names, keywords, and options that must be
input exactly as shown. In text, bold indicates keys to press, function names, and menu
selections.
Italic In syntax, italic indicates information that you supply. In text, italic also indicates UNIX
commands and options, file names, and pathnames.
Plain In text, plain indicates Microsoft Windows commands and options, file names, and
pathnames.
Bold Italic Indicates: important information.
Lucida Indicates examples of source code and system output.
Console
Lucida Bold In examples, indicates characters that you type or keys that you press (for example,
<Return>).
Lucida Blue In examples, illustrates the operating system command prompt.
Î A right arrow between menu commands indicates that you should choose each command in
sequence. For example, “Choose File ÎExit” means that you should choose File from the
menu bar, and then choose Exit from the File pull-down menu.
This line The continuation character ¬ is used in source code examples to indicate a line that is too
¬ continues long to fit on the page but that must be entered as a single line on the screen.
The following are also used:

• Syntax definitions and examples are indented for ease in reading.
• All punctuation marks that are included in the syntax—for example, commas, parentheses, or
quotation marks—are required unless otherwise indicated.
• Syntax lines that do not fit on one line in this manual are continued on subsequent lines. The
continuation lines are indented. When entering syntax, type the entire syntax entry, including
the continuation lines, on the same input line.
• Text enclosed in parentheses and quoted (“like this”) following the first use of proper terms will
be used instead of the proper term.

Interaction with our example system will usually include the system prompt (in blue) and the
command, most often on two or more lines.
If appropriate, the system prompt will include the user name and directory for context. For example:
%etl_node%:dsadm /opt/ibm >

/bin/tar –cvf /dev/rmt0 /opt/ibm/InformationServer
Feedback
We value your input and suggestions for continuous improvement to this content. Direct any questions,
comments, corrections, or suggested additions to cedifeed@us.ibm.com.

Table of Contents
1 IBM INFORMATION SERVER PREINSTALLATION OVERVIEW ...................................................................8
2 PREINSTALLATION CHECKLIST ........................................................................................................................10
2.1 REVIEW RELEASE NOTES ......................................................................................................................................11
2.2 REVIEW PLANNING, INSTALLATION, AND CONFIGURATION GUIDE .......................................................................12
2.3 (IF APPLICABLE) REVIEW MIGRATING TO IBM INFORMATION SERVER .................................................................12
2.4 CHOOSE AND VALIDATE AN INSTALLATION ARCHITECTURE / TOPOLOGY ............................................................13
2.5 VALIDATE IBM INFORMATION SERVER SYSTEM REQUIREMENTS FOR ALL TIERS .................................................17
2.6 VERIFY DOMAIN AND WEBSPHERE APPLICATION SERVER REQUIREMENTS .........................................................17
2.7 VERIFY DATABASE REQUIREMENTS FOR THE METADATA REPOSITORY................................................................18
2.8 (IF APPLICABLE) VERIFY THE DATABASE REQUIREMENTS FOR THE WEBSPHERE INFORMATION ANALYZER
ANALYSIS DATABASE..........................................................................................................................................................19
2.9 VERIFY AND CONFIGURE DISKS, VOLUME GROUPS, AND FILE SYSTEMS ..............................................................20
2.10 VERIFY AND CONFIGURE OPERATING SYSTEM AND RESOURCE LIMITS ................................................................26
2.11 VERIFY CONNECTIVITY AND NETWORK CONFIGURATION.....................................................................................34
2.12 CONFIGURE OPERATING SYSTEM USERS, GROUPS, AND PERMISSIONS .................................................................35
2.13 VERIFY AND INSTALL C++ COMPILER AND/OR RUNTIME LIBRARIES ....................................................................39
2.14 VERIFY IBM INFORMATION SERVER CONNECTOR REQUIREMENTS ......................................................................39
2.15 DOWNLOAD IBM INFORMATION SERVER INSTALLATION AND FIX PACK PACKAGES ............................................39
2.16 PERFORM COMPLETE SYSTEM BACKUP .................................................................................................................40
APPENDIX A: PREINSTALLATION CHECKLIST .......................................................................................................41
APPENDIX B: INSTALLATION AND CONFIGURATION CHECKLIST ..................................................................42
APPENDIX C: IBM INFORMATION SERVER INSTALLATION SETTINGS ..........................................................43
APPENDIX D: ONLINE DOCUMENTATION RESOURCES........................................................................................45
APPENDIX E: NETWORK PORTS USED BY IBM INFORMATION SERVER ........................................................46
APPENDIX F: GLOSSARY.................................................................................................................................................47
APPENDIX G: UTILIZING HP-UX 11 MEMORY WINDOWS.....................................................................................48
APPENDIX H: EXAMPLE USER SETUP FOR UNIX ENVIRONMENTS ..................................................................50

1 IBM Information Server Preinstallation Overview

IBM Information Server provides a unified foundation for enterprise information architectures,
combining the capabilities of the following product modules:
IBM WebSphere DataStage
IBM WebSphere QualityStage
IBM WebSphere Information Analyzer
IBM WebSphere Business Glossary
IBM WebSphere Information Services Director
IBM Metadata Workbench
IBM Information Server is installed in four logical tiers (also called layers in the installation wizard
and documentation):
Client
Domain (platform services)
Metadata repository
Engine
Product components are installed in each tier depending on the installation selections that are made.
The IBM Information Server documentation (PDF books) can be installed on any machine. The IBM
Information Server information center (HTML) is always installed with the platform services and
available from the IBM Information Server console and Web console. The information center contains
information that is common to all IBM Information Server product modules (such as installation
information), as well as complete information for the following product modules: IBM WebSphere
Business Glossary, IBM WebSphere Information Analyzer, and IBM WebSphere Information Services
Director. Other product modules are documented in HTMLHelp and PDF books.
To ensure a successful installation that meets functional and performance requirements, it is critical
that overall planning and prerequisites be met for all tiers. This document provides a detailed
methodology for planning an IBM Information Server installation.
IMPORTANT: Establishing an IBM Information Server environment that meets performance

expectations requires a capacity planning exercise: reviewing deployment architecture, server,
disk, network configuration, data sources, targets, data volumes, processing requirements, and
service level agreements.
Although minimum system requirements are referenced in this checklist, capacity planning is
outside the scope of this document.
Where possible, links are provided for additional details and product documentation. The information
in this document is based on field experiences. In some cases, the recommendations documented here

may differ from the product documentation. Except where noted, this document is intended to
supplement, not replace the product documentation.
To install the product documentation in PDF format, choose “Documentation” during the product
installation. Additional and updated documentation for select product modules is available through the
IBM Information Server Information Center at the following URL:
http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r0/index.jsp

2 Preinstallation Checklist
The following checklist outlines the areas that must be reviewed and the steps that must be completed
prior to installing IBM Information Server. A copy of this checklist is also included in Appendix A:
Complete Task
1) Review the release notes for IBM Information Server, IBM WebSphere
Application Server, and (if applicable) IBM DB2.
2) Review
IBM Information Server Planning, Installation and Configuration Guide.
3) If migrating from previous versions of WebSphere DataStage or WebSphere
QualityStage, review Migrating to IBM Information Server Version 8.
4) Choose and validate the installation architecture and topology.
5) Validate system requirements for all tiers: engine, domain, repository, and
client.
6) Verify domain (WebSphere Application Server) requirements.
7) Verify database requirements for the metadata repository.
8) (if applicable) Verify database requirements
for the WebSphere Information Analyzer analysis database.
9) Verify and configure disks, volume groups, and file systems.
10) Verify and configure operating system and resource limits.
11) Verify connectivity and network configuration.
12) Configure operating system users, groups, and associated permissions.
13) Verify and install a C++ compiler and/or runtime libraries.
14) Verify IBM Information Server connector requirements.
15) Download installation and fix pack packages for IBM Information Server,
WebSphere Application Server, and DB2.
16) Perform a complete system backup.
Specific details on each step may be found in subsequent sections of this document, the release notes,
and IBM Information Server Planning, Installation, and Configuration Guide.

2.1 Review Release Notes

Release notes contain the latest information on a particular release of IBM Information Server
including known issues and workarounds. There are separate release notes that should be consulted for
IBM WebSphere Application Server and (if applicable) DB2.
2.1.1 IBM Information Server Release Notes

Although a copy of the IBM Information Server Release Notes is included with a product installation, a
more current version may be available online in the IBM Information Server Information Center and
should be consulted before any installation, at the following URL:
http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r0/topic/com.ibm.swg.im.iis.productization.iisinfsv
.nav.doc/containers/cont_iisinfsrv_rnote.html
When reviewing release notes, be sure to choose the version that matches the base installed version of
IBM Information Server, for example 8.0.1.
Any IBM Information Server fix packs and patches that are applied after a base installation have
separate, corresponding release notes that should also be reviewed. For example, 8.0.1 Fix Pack 1a
would be applied to an existing 8.0.1 base installation.
2.1.2 WebSphere Application Server Release Notes

The domain tier of IBM Information Server 8.0.1 requires IBM WebSphere Application Server Version
6.0.2. On most platform configurations, WebSphere Application Server is included in the IBM
Information Server installation program, but there are some exceptions (namely, 64-bit platforms).
Release notes for WebSphere Application Server Version 6.0.2 are available at:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.base.doc/info/aes/ae/
v6rn.html
Complete documentation for WebSphere Application Server Version 6.0.2 is available through the
WebSphere Application Server Information Center at:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.base.doc/info/welco
me_base.html
2.1.3 DB2 Enterprise Server Edition Release Notes

The IBM Information Server metadata repository can be installed in DB2 Version 9.1 Enterprise Server
Edition, Oracle Database 10g Release 2, or Microsoft SQL Server 2005.
When installing IBM Information Server, if you choose to install the “Repository Layer” option, a new
copy of DB2 V9.1 will be installed. Release notes for DB2 V9.1 can be found at:
http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.doc/doc/c0023859.htm

2.2 Review Planning, Installation, and Configuration Guide

Although this preinstallation checklist provides a methodology and supplemental information on
preparing for an installation of IBM Information Server, detailed content is available in IBM
Information Server Planning, Installation, and Configuration Guide:
Planning to install IBM Information Server
Preparing your system for installation
Installing IBM Information Server
Configuring IBM Information Server
Installing additional components
Troubleshooting installations
Removing IBM Information Server
IBM Information Server Planning, Installation, and Configuration Guide is part of the IBM
Information Server documentation, which is included with the product installation package and on the
IBM Web site:
PDF book: http://www.ibm.com/support/docview.wss?uid=swg27008803

Information center:
http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r0/topic/com.ibm.swg.im.iis.productization.
iisinfsv.nav.doc/containers/cont_iisinfsrv_install.html
Note that the PDF documentation (the “Documentation layer” option) can be installed separately,
without installing the rest of the IBM Information Server.
2.3 (if applicable) Review Migrating to IBM Information Server

If you are migrating from earlier versions of IBM WebSphere DataStage or WebSphere QualityStage,
review the content of Migrating to IBM Information Server Version 8, which is included with the
product installation package and on the IBM Web site:
PDF book: http://www.ibm.com/support/docview.wss?uid=swg27008803

Information center:
http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r0/topic/com.ibm.swg.im.iis.productization.
iisinfsv.nav.doc/containers/cont_iisinfsrv_migrating.html
Note that the PDF documentation (the “Documentation layer” option) can be installed separately,
without installing the rest of the IBM Information Server.

2.4 Choose and Validate an Installation Architecture / Topology

The architecture of IBM Information Server is organized into four major logical tiers (layers):
Layer Description Architectural Notes

Client Administration, analysis, and Multiple clients can access a single instance of IBM
development user interfaces. Information Server. The client and server versions
must match.
Optional MetaBrokers and bridges for
importing and exporting metadata. Using the Multi-client Manager, multiple client
versions can be installed on a single workstation.
Requires 32-bit versions of Windows XP, Windows

Vista, or Windows 2003.
Metadata Database that stores IBM Information A single metadata repository database is defined for
repository Server settings, configuration, design each IBM Information Server installation.
and runtime metadata.
DB2 V9.1 (included or customer-supplied)
Oracle Database 10g R2 (customer-supplied)
Microsoft SQL Server 2005 (customer-supplied)
Domain IBM Information Server common and A single domain is defined for each IBM Information
product-specific services. Server installation.
Requires WebSphere Application Server

(included or customer-supplied)
Version 6.0.2 Fix Pack 11 or later fix pack
Standalone (non-network) profile only
Engine Runtime engine that executes all IBM Multiple engines on separate server environments may
Information Server tasks. Includes be registered in a single IBM Information Server
engine, connectors, packs, and related domain (cluster or grid deployment).
service agents (logging agent, ASB
communication agent, Job Monitor, and Only one V8 engine can be installed on a single
Performance Monitor). server. May coexist with multiple WebSphere
DataStage Version 7 engines.
In any IBM Information Server installation, the release level (version + fix pack + patches) must match
on all layers.
IMPORTANT: Although the architecture of IBM Information Server offers many theoretical
deployment architectures, only the following subset of configurations is recommended and
supported.
Any deviation from these deployments must be reviewed by IBM Support and Engineering.

2.4.1 Two-Tier Deployment
Client(s): Client applications on Windows systems.

Server 1: All other components (metadata repository, domain, engine) on the same Linux,
UNIX, or Windows server.
Although the IBM Information Server System Requirements state a minimum of 4GB of RAM, in this
configuration the single server housing the metadata repository, domain, and engine should have 8GB
of RAM, in addition to meeting the combined disk requirements outlined in the IBM Information
Server System Requirements.
The IBM Information Server versions of all components must match.
Because the complexity of tracking the state of different layers is simplified, the two-tier deployment is
optimal for high availability (failover) scenarios.

2.4.2 Three-Tier Deployment

Server 1: Metadata repository and domain on the same Linux, UNIX, or Windows server.
Server 2: Engine on Linux, UNIX, or Windows server.
In the three-tier configuration, both back-end servers must be located in the same physical data center
and should be connected to the same network subnet.
The operating system of the two servers should be the same.

2.4.3 Four-Tier Deployment

For performance reasons, this configuration is not recommended unless the metadata repository and
domain servers are connected by a dedicated, private, high-speed network connection.

Server 1: Metadata repository on Linux, UNIX, or Windows server.
Server 2: Domain on Linux, UNIX, or Windows server.
Server 3: Engine on Linux, UNIX, or Windows server.
In the four-tier configuration, all servers must be located in the same physical data center and should be
connected to the same network subnet.
2.4.4 Cluster and Grid Deployments

In all configurations, multiple IBM Information Server Version 8 engines may be installed on
physically separate servers. By including these servers in a parallel configuration file at runtime, IBM
Information Server processing can span across a single server boundary.
In a cluster or grid deployment, all engine servers must be the same operating system, must be located
in the same physical data center, and should be connected by a dedicated, private high-speed network
connection.
2.4.5 Wide Area Network (WAN) Deployments

Due to the data exchanges that occur between the IBM Information Server components, it is strongly
recommended that all tiers be located in the local area network (LAN).
When the clients connect to IBM Information Server via a Wide Area Network (WAN), a remote
desktop solution like Citrix or Windows Terminal Server can be used to minimize the amount of data
that is normally transmitted between the IBM Information Server clients and server. It is important to
note that the system that is hosting Citrix or Windows Terminal Server be installed in the same subnet
in LAN that is used for the IBM Information Server systems.

2.5 Validate IBM Information Server System Requirements for all Tiers
After selecting the installation topology, verify the IBM Information Server system requirements for
the client, metadata repository, domain, and engine.
IBM Information Server System Requirements:

http://www.ibm.com/support/docview.wss?uid=swg27008923
2.6 Verify Domain and WebSphere Application Server Requirements

The domain layer requires WebSphere Application Server Version 6.0.2 Fix Pack 11 or later fix packs
only. Specific hardware and software requirements for WebSphere Application Server Version 6 can
be found online:
WebSphere Application Server 6.0.2 Hardware Requirements:

http://www.ibm.com/support/docview.wss?rs=180&uid=swg27007250
WebSphere Application Server 6.0.2 Software Requirements:

On most platforms, when you install IBM Information Server, you can install a new copy of
WebSphere Application Server or use an existing installation.
On some 64-bit platforms (64-bit Red Hat Linux, 64-bit SUSE-Intel Linux, HP-UX Itanium), you must
download the WebSphere Application Server 6.0.2 installation program and fix packs from IBM
Passport Advantage . Specific instructions are included in the IBM Information Server System
Requirements:
To install the domain layer in an existing installation of WebSphere Application Server, the
configuration must meet the following requirements:
WebSphere Application Server Version 6.0.2 Fix Pack 11 or later fix pack
Standalone (not network) deployment
New, empty profile
IMPORTANT: To minimize risk and to ensure that the domain requirements are satisfied, use
the version of WebSphere Application Server that is bundled with the IBM Information Server
installation program, except in specific configurations (64-bit installations of Red Hat Linux,
SUSE-Intel Linux, or HP-UX Itanium).

2.7 Verify Database Requirements for the Metadata Repository

The metadata repository can be installed on DB2 V9.1, Oracle Database 10g R2, or Microsoft SQL
Server 2005. By default, the metadata repository database is named “xmeta”.
When you install IBM Information Server, you can install a new copy of DB2 V9.1 or use an existing
installation. If you want to use Microsoft SQL Server or Oracle, you must install and configure them
before you install IBM Information Server.
Specific hardware and software requirements for DB2 can be found online:
DB2 V9.1 Requirements:

http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.uprun.doc/doc/r0025127.h
tm
To install the metadata repository on an existing installation of DB2, it must meet the following
requirements:
DB2 Enterprise Server Edition Version 9.1
Database cannot be partitioned
On some 64-bit platforms (64-bit Red Hat Linux, 64-bit SUSE-Intel Linux, HP-UX Itanium) you must
download the DB2 V9.1 installation program and fix packs from IBM Passport Advantage. Specific
instructions are included in the IBM Information Server System Requirements:
During the installation of IBM Information Server, if you choose to install the metadata repository on a
new copy of DB2, the metadata repository database will be created as part of the installation.
If you choose to install the metadata repository on an existing installation of DB2, Oracle Database
10g, or Microsoft SQL Server 2005 the metadata repository database must be created before the IBM
Information Server installation.
Database creation scripts are included in the DatabaseSupport subdirectory of the IBM Information
Server installation. Full details on creating the metadata repository database can be found in the IBM
Information Server Planning, Installation, and Configuration Guide.
IMPORTANT: Although the IBM Information Server System requirements recommend a

minimum of 3GB for the metadata repository, you should plan for this to grow to 40GB.
The metadata repository database should be closely monitored as the database grows to ensure
that sufficient space is available in the tablespaces and underlying file systems.

2.8 (if applicable) Verify the Database Requirements for the WebSphere
Information Analyzer Analysis Database
If you are deploying WebSphere Information Analyzer, the analysis database can be installed on DB2
V9.1, Oracle Database 10g R2, or Microsoft SQL Server 2005. By default, the analysis database is
named “iadb”.
When you install IBM Information Server, you can install a new copy of DB2 V9.1 or use an existing
installation. If you want to use Microsoft SQL Server or Oracle, you must install and configure them
before you install IBM Information Server.
If you choose to install the WebSphere Information Analyzer analysis database on an existing
installation of DB2, Oracle Database 10g, or SQL Server 2005:
The analysis database must be created before the IBM Information Server installation
Database connectivity must be configured from the domain tier to the analysis database.
Database creation scripts are included in the DatabaseSupport subdirectory of the IBM Information
Server installation. Full details on creating the analysis database can be found in the IBM Information
Server Planning, Installation, and Configuration Guide.
IMPORTANT: While the IBM Information Server System Requirements recommend a

minimum of 3GB for the WebSphere Information Analyzer analysis database, the actual size
depends on the size of the sources to be analyzed. Unless you are using sampled analysis, the
analysis database can be significantly larger than the combined size of all analyzed data
sources.
As a rough guideline for analysis database sizing, start with a minimum of 300GB and
plan to grow to 4x the total size of all analyzed source data.
Actual analysis database sizing depends on the source analysis requirements, total size of all
analyzed source data, number of keys and attributes, and the retention policy for existing
analysis results and baselines. A detailed sizing guideline for the WebSphere Information
Analyzer analysis database is available from IBM Information Server Support.

2.9 Verify and Configure Disks, Volume Groups, and File Systems
2.9.1 RAID / SAN Configuration
IBM Information Server uses file system mount points for its installation, libraries, temporary storage,
and Data Set storage.
Ultimate performance of an IBM Information Server job (WebSphere DataStage, WebSphere

QualityStage, and WebSphere Information Analyzer) depends on all components being optimized.
When discussing disk (including RAID/SAN) configuration, maximum performance is a combination
of maximum bandwidth (controllers, disk) and minimized contention.
The following guidelines can assist in the configuration of RAID or SAN technologies:
a) Minimize contention between temporary (scratch, buffer, and sort) and data file systems.
b) Minimize contention between the disks and controllers associated with IBM Information Server
file systems and other applications or servers.
c) Consider isolating multiple mount points to separate high-speed disk interconnects and
controllers.
d) Consider the tradeoff between the granularity of file system(s) and underlying configuration vs.
available, unused storage.
e) Don’t create overly-complex device configurations because these can be difficult to administer
and may not offer noticeable performance improvement.
f) If possible, test your configuration with expertise from hardware, storage, operating system, and
application (IBM Information Server) resources.
g) Remember that previous experience in designing I/O systems for non-parallel engines might
lead to non-optimal configurations for IBM Information Server.
The optimal disk configuration will strike a balance between cost, complexity, ease of administration,
and ultimate performance.

2.9.2 IBM Information Server File Systems

IBM Information Server requires file systems for:
Software installation directories
- IBM Information Server
- Domain (WebSphere Application Server)
- Database Server
Database storage
- Metadata repository (“xmeta”)
- (if applicable) WebSphere Information Analyzer analysis database (“iadb”)
IBM Information Server project (runtime shadow repository) directories

- Used to capture runtime metadata (such as error messages and logging information) for the
IBM Information Server parallel engine; synchronized to the metadata repository
Data file storage

- IBM Information Server engine temporary storage (scratch, temp, buffer)
- IBM Information Server artifacts (such as surrogate key files)
- IBM Information Server parallel Data Set segment files
- Staging and archival storage for any source file(s)
File System Requirements:

a) File systems should be expandable without requiring destruction and re-creation.
b) Local file systems should be reserved for temporary and scratch storage.
c) Data and installation directories should be created on high-performance shared file systems.
d) Avoid the use of NFS soft mounts.
e) Some components and plug-ins may require additional file system permissions. For example,
the DB2/UDB Enterprise stage requires that the db2instance ID has read access to a
subdirectory under $TMPDIR for db2load.
IMPORTANT: Each storage class should be isolated in separate file systems to accommodate
their different performance and capacity characteristics and backup requirements.
The default installation directories are best suited for small prototype environments.

2.9.3 Software Installation Directories
Installation Contents Default UNIX Path

Directory
Information IBM Information Server engine, libraries, /opt/IBM/InformationServer/
Server communication agents, Job Monitor, Performance
Monitor, Java JRE, uninstallation files.
Domain WebSphere Application Server executables, libraries. /opt/IBM/WebSphere/AppServer/
IBM Information Server common services and product-
specific services.
Database Server DB2 V9.1 database server executables, libraries. /opt/IBM/db2/V9/
Installation File System Requirements:

a) Do not install IBM Information Server components (IBM Information Server, WebSphere
Application Server, or DB2) on a top-level mount point. Always install IBM Information
Server components to a subdirectory within a mount point. The installation program
components change ownership and permissions of directories that are installed, and not all
mount points allow these changes, causing the installation to fail.
b) On Windows platforms, IBM Information Server cannot be installed on virtual drives (mapped
or SUBST drives).
c) The installation directories for WebSphere Application Server and (if applicable) DB2 must be
empty. If the target directory is not empty, the installation program will attempt to create
another directory, which will not be properly referenced by the IBM Information Server paths.
d) All file systems used by IBM Information Server for installation must have read and write
permissions for the primary WebSphere DataStage users and groups. Ensure that each level of
the target installation directories is set to 755 permissions.
e) The IBM Information Server installation program configures the security and permissions of
various file systems. You should not change the access rights of any of the directories after the
installation unless they pertain to the scratch, resource, temp areas, or projects because they can
compromise the security of the system.
f) IBM Information Server, WebSphere Application Server, and (if applicable) DB2 must be
installed into separate directories. They cannot be installed in the same directory level.
g) On UNIX platforms, the DB2 installation program must have write access to several file
systems, including /var and /usr/local/bin. This requirement is not always satisfied when these
directories are mounted from network file systems such as AFS, or when these directories are
configured as read-only file systems.
h) For cluster or grid implementations, it is generally best to share the installation file systems
across all servers (at the same mount point).

2.9.4 Database Storage

Metadata repository (“xmeta”)
(if applicable) WebSphere Information Analyzer analysis database (“iadb”)
On UNIX platforms, using the supplied DB2 database engine, databases are created in the home
directory of the DB2 instance owner, by default:
/home/db2inst1/
If you pre-create the DB2 user accounts, you can choose the target file system for this home directory.
When using an existing installation of DB2 V9.1, Oracle Database 10g, or Microsoft SQL Server 2005,
tablespaces are created by the database administrator using existing file systems or raw disk devices.
IMPORTANT: The metadata repository and (if applicable) WebSphere Information Analyzer
analysis databases should be closely monitored to ensure that sufficient space is available in the
tablespaces and underlying file systems as the databases grow. Regular, scheduled backups
should be performed on these databases.
2.9.5 IBM Information Server Project (runtime shadow repository) Directories

The IBM Information Server Project directory is used to capture runtime metadata (such as error
messages and logging information) for the IBM Information Server parallel engine. This data is
synchronized into the metadata repository on periodic intervals for later reporting. The IBM
Information Server Project directory may also store legacy IBM WebSphere DataStage Server Edition
hash files. Project directories can grow to contain thousands of files and subdirectories depending on
the number of projects, the number of jobs, and the volume of logging information retained about each
job.
During the installation process, the Projects subdirectory is created in the IBM Information Server
installation directory. By default, the WebSphere DataStage and QualityStage Administrator client
creates projects in this Projects subdirectory:
/opt/IBM/InformationServer/Server/Projects/
During installation, WebSphere Information Analyzer also creates its own WebSphere DataStage
project within this directory, which is used to run all analysis jobs.
IBM Information Server Project directory guidelines:

a) It is a bad practice to create WebSphere DataStage projects in the default directory within the
installation file system, as disk space is typically limited. Projects should be created in their
own file system.

b) On most operating systems, it is possible to create file systems at non-root levels. Create a
separate file system for the Projects directory within the IBM Information Server installation.
Be sure to backup any existing projects (retaining ownership and permissions) before mounting
a separate file system over the existing /opt/IBM/InformationServer/Projects directory.
c) For cluster or grid implementations, it is generally best to share the Projects file system across
servers (at the same mount point).
2.9.5.1 Project Naming Considerations

The name of an IBM Information Server Project is limited to a maximum of 18 characters. The project
name can contain alphanumeric characters and underscores.
Project names cannot use the following reserved words: ds, DS, uv, or UV.
Projects names should be maintained in unison with source code control. As projects are promoted
through source control, the name of the phase and the project name should reflect the version, in the
form:
<Phase>_<ProjectName>_<version>
Where Phase corresponds to the phase in the application development lifecycle:
Phase Name Phase Description

dev Development
it Integration test
uat User acceptance test
prod Production
2.9.5.2 Project Directory Monitoring and Maintenance

Effective management of space is important to the health and performance of a project. As jobs are
added to a project, new directories are created in this file tree, and as jobs are run, their log entries
multiply. These activities cause file-system stress. (For example, more time to insert or delete
WebSphere DataStage components or longer update times for logs.) Failure to perform routine projects
maintenance (for example, removing obsolete jobs and managing log entries) can cause project obesity
and performance issues. When no jobs are running, you should purge the &PH& project subdirectory
as part of this maintenance.
IMPORTANT: The project file system should be monitored to ensure adequate free space
remains. If the Project file system runs out of free space during runtime activity, the repository
may become corrupted, requiring a restore from backup.

2.9.6 Dataset and Scratch Directories

During installation, two directories are created in the IBM Information Server installation directory tree
for storage of temporary and intermediate data files used by the parallel engine:
/opt/IBM/InformationServer/Server/Datasets - persistent storage between jobs

/opt/IBM/InformationServer/Server/Scratch - temp storage for sort and buffer overflow
The IBM Information Server installation program creates a default parallel configuration file that
references the default Datasets and Scratch directories:
/opt/IBM/InformationServer/Configurations/default.apt
Parallel configuration files are used to assign resources (such as processing nodes, disk and scratch file
systems) at runtime when a job is run by the IBM Information Server engine. Parallel configuration
files are discussed in detail in the IBM WebSphere DataStage Parallel Job Developer Guide (provided
as part of the installed PDF documentation).
Dataset and Scratch Directory Guidelines:

a) Dataset and Scratch file systems should be created outside of the IBM Information Server
installation directory.
b) Scratch file systems should be created on local (internal) storage.
c) Dataset and installation directories should be created on high-performance, shared file systems
with the same mount point available on all servers. Using a shared file system also facilitates
high-availability failover scenarios.
d) The default.apt configuration file should be edited to reference the newly-created Dataset and
Scratch file systems and to ensure that these directories are used by any other parallel
configuration files.
e) For optimal performance, file systems should be created in high performance, low contention
storage.
f) For best performance and to minimize storage impact on development activities, separate file
systems should be created for each Data and Scratch resource partition.
g) On systems where multiple phases are shared on the same server, consider separating Data and
Scratch storage to different file systems for each deployment phase to completely isolate each
environment.

2.9.7 Extending the WebSphere DataStage Project for External Entities

For WebSphere DataStage and QualityStage environments, you should create another directory
structure to integrate all aspects of a WebSphere DataStage application that are managed outside of the
WebSphere DataStage Projects repository. This hierarchy should include directories for secured
parameter files, Data Set header files, custom components, Orchestrate schemas, and SQL and shell
scripts. It may also be useful to store custom job logs and reports in this extended directory structure.
2.9.8 File Staging

You should use a separate staging file system and directory structure for storing, managing, and
archiving various source data files.
2.10 Verify and Configure Operating System and Resource Limits

On most platforms, IBM Information Server, WebSphere Application Server, and the database server
have specific operating system (kernel) and user (shell) resource requirements. The latest versions of
these requirements can be found at the URLs below.

WebSphere Application Server 6.0.2 Software Requirements:

DB2 V9.1 Requirements:

http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.uprun.doc/doc/r0025127.htm
If you are using an existing Oracle Database 10g R2 or Microsoft SQL Server 2005 database server for
the metadata repository or WebSphere Information Analyzer analysis database, reference the database
vendor’s system requirements.
Notes on Operating System Requirements:

a) On UNIX installations of IBM Information Server, the following tables list minimum
requirements for UNIX kernel parameters. These settings give the generic names for the kernel
parameters. The actual name and the capitalization vary for each UNIX platform.
b) Always make a backup of the kernel settings before making these changes. On many platforms,
this can be accomplished by backing up the /etc/system file.
c) On some platforms, it may be necessary to rebuild the kernel with changes to these parameters.
All changes should only be made by a trained UNIX system administrator.
d) For readability, the table values in this section include commas; omit them when setting the
actual parameters.

2.10.1 UNIX Kernel Parameters for all Platforms

On all UNIX platforms, the following table lists minimum requirements for kernel parameters. These
settings give the generic names for the kernel parameters. The actual name and the capitalization vary
for each platform.
(For readability, the table values in this section include commas; omit them when setting parameters.)
Kernel Description IBM DB2 Notes

Parameter Information Minimum
Server
Minimum
MAXUPROC Maximum number of 100 per Set to at least 100 processes per
processes processor node
NOFILES Number of open files 1,000
per process
2.10.2 UNIX User (Shell) Parameters for all Platforms

On all UNIX platforms, the user (shell) parameters should be adjusted to ensure that the IBM
Information Server parallel engine has sufficient resources.
User Parameter Description Recommended Setting

umask Default file permissions 022
ulimit Maximum number of user processes 8192
2.10.3 AIX System Configuration

On AIX systems, if you intend to use the WebSphere DataStage Job Scheduler, the permissions on the
directory /usr/spool/cron/atjobs must be changed from 770 to 775 (rwxrwxr-x).
2.10.3.1 AIX Kernel Parameters

On AIX installations of IBM Information Server, the following table lists minimum requirements for
UNIX kernel parameters.
Kernel Description IBM Notes

Parameter Information
Server
Minimum
SHMMAX Maximum shared memory 307,200,000 If disk caching is turned on and
segment size DISKCACHE is larger than 512, then this
must be set higher.
SHMMNI Shared memory identifiers 2000

Kernel Description IBM Notes

Parameter Information
Server
Minimum
SHMSEG Maximum number of shared 200
memory segments per process
2.10.3.2 AIX User (Shell) Parameters

On AIX, the following additional user (shell) parameters should be adjusted to ensure that the IBM
Information Server parallel engine has sufficient resources:
User Description Recommended Setting

Parameter
fsize Largest file a user may create unlimited
data Largest data segment (heap) a program can have unlimited
stack Largest stack size a program can have 32MB minimum

(65,536 512-byte blocks)
rss Maximum amount of physical memory a users unlimited
process may use
On AIX platforms, tuning the following additional kernel parameters may improve performance for the
IBM Information Server parallel engine. Work with your AIX system administrator to determine
optimal values:
User Parameter Description Recommendation

maxperm Maximum number of Tune to limit the amount of physical memory used for
permanent buffer pages for file system I/O so more memory is dedicated for parallel
file I/O processes.
somaxconn Maximum number of socket May need to increase this value for large parallel jobs
connections with lots of processes. When increasing maxuproc is not
enough, increase this kernel parameter.
rbr Release-behind-when-reading Consider setting this file system mount option for
permanent Data Set storage. Since large permanent Data
Sets are always read sequentially and never in reverse or
random order, this might improve performance.
CIO Concurrent I/O Investigate the use of CIO for both disk and scratchdisk
resources. CIO results in a performance similar to raw
devices, which might benefit access to both permanent
Data Sets and temporary sort files. CIO is good for I/O
with large block sizes.

2.10.4 HP-UX System Configuration
2.10.4.1 HP-UX Kernel Parameters

On HP-UX installations of IBM Information Server, the following table lists minimum requirements
for UNIX kernel parameters.
After installing DB2 on HP-UX, run the db2osconf command to verify recommended kernel settings.
Kernel Description IBM WebSphere Notes

Parameter Information Application
Server Server Minimum
Minimum
MAXFILES Maximum number of open 1448
files per process
MSGMAP Number of entries in SystemV 2319
IPC message space resource
map
MSGMAX Maximum message size in 32,768 65,535
bytes
MSGMNB Maximum bytes per message 32,768 65,535
queue
MSGMNI Maximum number of system- 2317
wide SystemV IPC message
queues
MSGSEG Number of system VIPC 7,168 32,767
message segments
MSGSZ Message size 32
MSGTQL Maximum number of 2317
SystemV IPC messages
NFILE Maximum number of files 16,219
open simultaneously
NFLOCKS Maximum number of file 5793
locks
NIDNOE Maximum number of HFS file 4055
system open inodes
NPROC Number of simultaneous 2912
processes
SEMMNI Number of semaphore 2896
identifiers (system wide)
SEMMNS Total number of semaphores 5794
SEMMNU Maximum number of undo 2896
structures
SHMMAX Maximum shared memory 307,200,000 2,897,215,488 If disk caching is
segment size turned on and
DISKCACHE is larger
than 512, then this must


Minimum
be set higher.
On 32-bit platforms, HP-UX limits the maximum size of a shared memory segment to 1.75GB. When
processing extremely large in-memory reference tables in a WebSphere DataStage Lookup stage, it
may be necessary to configure HP-UX memory windowing. This process is detailed in Appendix G:
Utilizing HP-UX 11 Memory Windows.
2.10.4.2 HP-UX User (Shell) Parameters

On HP-UX, the following additional user (shell) parameters should be adjusted to ensure that the IBM
Information Server parallel engine has sufficient resources.
User Parameter Description Recommended Setting

maxdsiz Maximum size of data segment 2,039,480,320 (1945MB)
maxssiz Maximum size of stack 82,837,504 (79MB)
maxtsiz Maximum size of text segment 1,073,741,824
rss Maximum amount of physical memory a users process unlimited
may use

2.10.5 Red Hat and SUSE Linux System Configuration

You cannot install IBM Information Server on a version of Red Hat Linux 4 that has been upgraded
from Red Hat v3 because the upgrade configurations are missing required libraries.
2.10.5.1 Red Hat and SUSE Linux Kernel Parameters

On Red Hat Linux installations of IBM Information Server, the following table lists minimum
requirements for UNIX kernel parameters.
Kernel Description IBM DB2 Notes

Parameter Information Minimum
Server
Minimum
bytes
MSGMNB Maximum bytes per 16,384 65,536
message queue
MSGMNI Maximum queue system N/A 1024
wide
SEMMNI Number of semaphore 1024 1024
identifiers (systemwide)
SEMMNS Total number of semaphores 128,000 256,000
SEMMSL Maximum number of 250 250

semaphores per ID list
SEMOPM Number of operations per 32 32
semop call
SHMALL Maximum total shared N/A 838608 Kbytes
memory
SHMMAX Maximum shared memory 307,200,000 32,768 Kbytes If disk caching is turned
segment size on and DISKCACHE is
larger than 512, then this
must be set higher.
SHMMNI Shared memory identifiers 2000 4096

memory segments per
process

2.10.6 Solaris 9 System Configuration
2.10.6.1 Solaris Kernel Parameters

On Solaris 9 installations of IBM Information Server, the following table lists minimum requirements
for UNIX kernel parameters.
After installing DB2 on Solaris 9, run the db2osconf command to verify recommended kernel settings.

Minimum
MSGMAP Number of entries in message 1026
map
bytes
MSGMNB Maximum bytes per message 16,384
queue
MSGMNI Maximum message queues 1024
(system wide)
SEMAEM Maximum adjust-on-exit 16,384
SEMMAP Number of entries in 1024
semaphore map
identifiers (system wide)
SEMMNS Total number of semaphores 128,000 16,384
SEMMNU Maximum number of undo 2048

structures
semaphores per id list
SEMOPM Maximum number of 32 100
semaphore operations
SEMUME Maximum number of undo 256
structures per process
SHMMAX Maximum shared memory 307,200,000 4,294967,295 If disk caching is turned
must be set higher.


2.10.7 Solaris 10 System Configuration

IBM Information Server has not been certified to run in Solaris 10 zones or projects. If you choose to
deploy IBM Information Server on a Solaris zone or project, any issues raised with IBM Support must
first be reproduced in a native operating system environment.
2.10.7.1 Solaris 10 Kernel Parameters

On Solaris 10 installations of IBM Information Server, the following table lists minimum requirements
for UNIX resource parameters. Note that starting with Solaris 10, many older kernel parameters have
been superseded by resource limits.
After installing DB2 on Solaris 10, run the db2osconf command a to verify recommended kernel
settings.

Minimum
bytes
MSGMNB Maximum bytes per message 16,384
queue
identifiers (systemwide)
semaphores per id list
SEMOPM Maximum number of 1024 100
semaphore operations
SHMMAX Maximum shared memory 6 GB 5 If disk caching is turned
must be set higher.

2.11 Verify Connectivity and Network Configuration

IBM Information Server relies on TCP/IP network infrastructure for communication between:
IBM Information Server clients and IBM Information Server domain
IBM Information Server clients and Information Sever engine
IBM Information Server domain and engine
IBM Information Server domain and metadata repository
IBM Information Server domain and WebSphere Information Analyzer analysis database
IBM Information Server engine and source/target data stores
o Databases
o File transfer through FTP or named pipes
o WebSphere MQ
o Third-party applications such as SAS, Siebel, PeopleSoft, or SAP
IBM Information Server engines in a clustered or grid configuration
IBM Information Server Job Monitor and IBM Information Server engine(s)
IBM Information Server Performance Monitor and IBM Information Server engine(s)
IBM Information Server requires access to a number of TCP ports, which must be open if necessary,
through firewall configuration. Note that related connectivity (for example, databases, and enterprise
applications) may require additional port assignments. Consult vendor-supplied documentation for
their requirements.
A complete list of network ports used by IBM Information Server is included in 0
Network Ports used by IBM Information Server.
IBM Information Server Network Requirements:

a) TCP/IP network is required.
b) All servers must be resolvable by name, between tiers and from clients to servers.
c) For optimal performance, all layers of IBM Information Server should be installed on the same
high-speed, low-latency local area network.
d) In a cluster or grid deployment, all engine servers must be located in the same physical data
center and should be connected by a dedicated, private high-speed network connection.
e) The domain and metadata repository should be installed on the same server. If they are installed
on separate servers, the domain and metadata repository should be connected by a dedicated,
private, high-speed network connection.
f) Due to the data exchanges that occur between the IBM Information Server layers, it is strongly
recommended that all tiers be located in the local area network (LAN). When deploying in a
Wide Area Network (WAN) configuration, a network hosting tool (such as Citrix, Windows
Terminal Server) should be used to host the IBM Information Server clients.
2.12 Configure Operating System Users, Groups, and Permissions

2.12.1 Privileged Installation User
IBM Information Server requires a privileged user account for installation.
On UNIX platforms, the installation must be performed by root or by a user account with root
privileges (including root privileges granted through sudo).
On Windows environments, the installation program must be run from a local Administrator
account. This user must have read/write access to the target installation directories. The
installation cannot be run from a Windows Domain administrator or by a Domain administrator
that is part of the local Administrators group.
2.12.2 Required Operating System Users

IBM Information Server requires a set of operating system user accounts to install the engine and
metadata repository database. These accounts are used by the IBM Information Server engine and
domain services.
User Account Default Primary Secondary Notes

Username Group Group
DataStage administrator dsadm dstage
DB2 administration server dasusr1 dasadm1 Only needed for DB2
DB2 instance owner db2inst1 db2iadm1 dasadm1 Only needed for DB2
DB2 fenced user db2fenc1 db2fadm1 Only needed for DB2
IBM Information Server xmeta xmeta DB2 uses OS authentication
metadata repository owner
WebSphere Information iauser iauser DB2 uses OS authentication
Analyzer analysis database
owner
IMPORTANT: These users can be created by the installation program, but this is not
recommended.
The security configuration of many operating systems (for example, AIX) requires new users to
login before an account is activated.
Instructions on creating users can be found in the IBM Information Server Planning, Installation, and
Configuration Guide and in the IBM Information Server Administration Guide. A simple UNIX user
setup is provided in Appendix H: Example User Setup for UNIX Environments.
Operating System User Requirements:
a) Because of the way the IBM Information Server installation program parses its parameters,
passwords should not include embedded dollar signs (“$”).

2.12.3 Domain (WebSphere Application Server) User Registry

IBM Information Server users log in and authenticate through the domain (WebSphere Application
Server). During installation, two domain accounts must be specified:
User Account Default Username Notes

WebSphere Application Server Administrator wasadmin
IBM Information Server Administrator isadmin Should be different from the
WebSphere Application Server
Administrator
WebSphere Application Server User Requirements:

a) During the IBM Information Server installation, WebSphere Application Server can be
configured to authenticate using an internal registry or using operating system users. This
option can be changed later through the WebSphere Application Server Administration console.
b) When using OS authentication, user accounts must be created and activated before running the
IBM Information Server installation program.
c) WebSphere Application Server does not support the use of NIS as a user registry. The
supported user registries are LDAP, OS (operating system), or IBM Information Server’s
internal user registry.
d) When installing in an LDAP environment, choose internal user registry. LDAP authentication is
configured after the IBM Information Server installation.
LDAP servers supported by IBM Information Server are those supported by WebSphere
Application Server 6.0.2. A complete list of supported LDAP servers can be found in
the WebSphere Application Server 6.0.2 Software Requirements at
e) Because of the way the IBM Information Server installation program parses its parameters,
passwords should not include embedded dollar signs (“$”)
2.12.4 Engine (WebSphere DataStage) User Setup

The IBM Information Server engine must have at least one operating system user defined. WebSphere
DataStage and QualityStage jobs, as well as WebSphere Information Analyzer jobs run on the engine
server using operating system user permissions.
When using the internal user registry, IBM Information Server users must be mapped to at least
one operating system user.
When using the WebSphere Application Server OS or LDAP configuration, IBM Information
Server can be configured to share the user registry with the engine (WebSphere DataStage and
QualityStage) registry. This eliminates the need to individually map each IBM Information
Server user to an engine operating system user.

WebSphere DataStage supports three basic categories of users: Managers, Developers, and Operators.
These are implemented as the secondary group for each category of user. That is, the primary group ID
(GID) of every WebSphere DataStage user must be the same as the WebSphere DataStage
Administrator (for example, dstage), and the secondary GID of a user in one of these categories must
be one of these groups. The WebSphere DataStage and QualityStage Administrator client is used to
assign roles to those users who are members of each group. Minimally, the only group that must be
created is the primary group of the WebSphere DataStage super-user. This group and the super-user
(dsadm) are used to secure files and perform software maintenance.
An effective method of specifying the groups and users is a table such as the one below. On our
example system, users and groups in bold already exist. The remaining groups and users are to be
created. Note that we describe our requirements in terms of business functions wherever possible and
identify employees, contractors and “virtual users” such as dsadm.
Primary Secondary User Role

Group Group
dstage dsmgr dsadm WebSphere DataStage software and project manager. This user ID
manages the software and project population and must exist on all
systems: development, test, and production systems. The password will
be closely controlled.
dsmgr johnl WebSphere DataStage project manager. This user is an employee who
manages the development and testing project environments, is
responsible for project backup and recovery, job migration to and from
development, source control, and production, and must exist on both
development and production systems.
dsmgr paulm Paul is an employee who is John’s back up. He has the same roles as
John, and he must have access to both production and development
systems.
dstage dsopr,autosys asys This user ID runs the jobs in the system integration and production
environments.1
dstage dsdev,users georgeh WebSphere DataStage developer. This user is an employee who needs
access to the development and test systems.
dsdev,users richards WebSphere DataStage developer. This user is an employee who needs
dsdev,users mannie WebSphere DataStage developer. This user is a contractor who needs
dsdev,users moe WebSphere DataStage developer. This user is a contractor who needs
dsdev,users jack WebSphere DataStage developer. This user is a contractor who needs
1
Autosys is a popular job scheduler for UNIX and is used as an example.
2.12.4.1 Engine (WebSphere DataStage) User Setup on UNIX

WebSphere DataStage can be administered on a UNIX platform by a special non-root user. This is
dsadm by default, but you can specify a different administrative user during installation. You must set
up this user before installing WebSphere DataStage. All WebSphere DataStage users should belong to
the same UNIX group, and this should be the administrative user’s primary group. We recommend you
name the group dstage.
If you want to set up the system so that it distinguishes between product managers, developers, and
operators, you should set up secondary groups for each class of user. Each user is then allocated to the
product manager, developer, or operator secondary group (but not to more than one secondary group).
You can then use the WebSphere DataStage and QualityStage Administrator client to assign the
appropriate WebSphere DataStage user role to the secondary groups. Operators cannot use the
WebSphere DataStage and QualityStage Designer client, and they only see released jobs in the
WebSphere DataStage and QualityStage Director client. Neither Operators nor Developers can create
protected projects or add anything to them. IBM Information Server adds the Super Operator role,
which removes the restrictions on the Operator role.
For more information about setting up users, see “Setting up security” in IBM Information Server
Administration Guide and “Assigning WebSphere DataStage roles” in IBM WebSphere DataStage and
QualityStage Administrator Client Guide, both of which are installed with the PDF documentation. The
IBM Information Server Administration Guide is also available on the IBM Web site:
PDF: http://www.ibm.com/support/docview.wss?rs=14&uid=swg27008803
IBM Information Server Information Center:
http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r0/index.jsp.
2.12.4.2 Engine (WebSphere DataStage) User Setup on Windows

On Windows 2003 Server, if you are using parallel jobs, then WebSphere DataStage must be installed
by a user that has local administrator rights. This user must also have read/write permission to the
target directory used to install the engine.
If you are logged into a domain account, it must be part of the local administrators group on the server
you are installing, and you must have network access to the Windows domain controller for
authentication.
The administrative user that you are logged in as during installation of WebSphere DataStage will
become the “owner” or administrator of the WebSphere DataStage installation.
After installation of WebSphere DataStage, you can use the Windows user management tools to define
groups of associated users to restrict access to individual WebSphere DataStage projects. By default,
every user (the “Everyone” group) is given access to newly-created projects. However, you can use the
Windows user management tools to create multiple Windows groups with assigned users, and then use
the WebSphere DataStage and QualityStage Administrator client to restrict access on a per-project
basis.
For more information about setting up users, see “Setting up security” in IBM Information Server
Administration Guide and “Assigning WebSphere DataStage roles” in IBM WebSphere DataStage and
QualityStage Administrator Client Guide, both of which are installed with the PDF documentation. The
IBM Information Server Administration Guide is also available on the IBM Web site:
PDF: http://www.ibm.com/support/docview.wss?rs=14&uid=swg27008803
IBM Information Server Information Center:
http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r0/index.jsp.
2.13 Verify and Install C++ Compiler and/or Runtime Libraries

To develop parallel jobs with WebSphere DataStage, you need to install the C++ compiler that is
specific to your platform on same server as the IBM Information Server engine. In development
environments, WebSphere DataStage uses the C compiler to generate parallel Transformer and
BuildOp components.
Many compilers are licensed on a per-user basis. WebSphere DataStage only invokes the C++ compiler
when the developer compiles a parallel job with Transformer stages or compiles a BuildOp component.
In other words, the maximum number of simultaneous WebSphere DataStage parallel job developers
would determine the maximum number of concurrent C++ compiler licenses.
On each platform, only one C++ compiler is supported. Check the IBM Information Server System
Requirements for information on supported compilers, and compiler installation requirements:
For deployment (production) systems, a C++ compiler is not required; some platforms, however, may
require C++ runtime libraries to be installed. This information is also contained in the IBM Information
Server System Requirements.
2.14 Verify IBM Information Server Connector Requirements

IBM Information Server uses connectors to access source and target data stores. Each connector (for
example, ODBC, DB2, or Teradata) has specific requirements for setup and configuration. Consult the
connector documentation and release notes for specific connector requirements.
2.15 Download IBM Information Server Installation and Fix Pack Packages
The installation packages for IBM Information Server are available through IBM Passport Advantage.
If you don’t already have an account (login) for IBM Passport Advantage, you will need to create one
and make sure it is associated with your customer ID to access all downloads that you have licensed.
IBM Passport Advantage Software Downloads:

http://www.ibm.com/software/howtobuy/passportadvantage/index.html

On some platforms (specifically, 64-bit installations of Red Hat Linux, SUSE Linux, and HP-UX), you
may also need to download WebSphere Application Server and DB2 packages. Details of specific
packages required by platform are found in the IBM Information Server System Requirements.

The list of packages to download includes:

IBM Information Server V8.0.1 installation program
IBM Information Server V8.0.1 update installation program
(if applicable) WebSphere Application Server V6.0.2 installation program
(if applicable) WebSphere Application Server Fix Pack installation program
(if applicable) DB2 Enterprise Server Edition V9.1 installation program
(if applicable) DB2 Enterprise Server Edition V9.1 Fix Pack installation program
In addition, product-specific patches may be required for issues discovered after the latest fix pack
release. Contact IBM Support for details on obtaining product patches.
2.16 Perform Complete System Backup

Before beginning an IBM Information Server installation, it is important to perform a complete system
backup, so that you can recover in the event that the installation fails or there is a need to bring the
system back to the state before the installation began.
This backup should be performed by the system administrator on all target installation server
computers, and it should include both operating system and user directories.

Appendix A: Preinstallation Checklist

The following checklist outlines the areas that must be reviewed and the steps that must be completed
prior to installing IBM Information Server.
Specific details on each step may be found in this document, the release notes, and IBM Information
Server Planning, Installation, and Configuration Guide.
Complete Task
1) Review the release notes for IBM Information Server, IBM WebSphere
Application Server, and (if applicable) IBM DB2.
2) Review
IBM Information Server Planning, Installation and Configuration Guide.
3) If migrating from previous versions of WebSphere DataStage or
WebSphere QualityStage, review Migrating to IBM Information Server
Version 8.
4) Choose and validate the installation architecture and topology.
5) Validate system requirements for all tiers: engine, domain, repository, and
client.
6) Verify domain (WebSphere Application Server) requirements.
7) Verify database requirements for the metadata repository.
8) (if applicable) Verify database requirements
for the WebSphere Information Analyzer analysis database.
9) Verify and configure disks, volume groups, and file systems.
10) Verify and configure operating system and resource limits.
11) Verify connectivity and network configuration.
12) Configure operating system users, groups, and associated permissions.
13) Verify and install a C++ compiler and/or runtime libraries.
14) Verify IBM Information Server connector requirements.
15) Download installation and fix pack packages for IBM Information Server,
WebSphere Application Server, and DB2.
16) Perform a complete system backup.

Appendix B: Installation and Configuration Checklist

The following checklist outlines the steps necessary to install and configure IBM Information Server.
For specific details, see the IBM Information Server Planning, Installation, and Configuration Guide
and the IBM Information Server Release Notes.
Complete Task
1) Complete all items on the Preinstallation Checklist (Appendix A).
2) If you are migrating from an earlier version of WebSphere DataStage or
WebSphere QualityStage, complete the preinstallation migration tasks.
3) If you are not using the installation of DB2 that is provided with IBM
Information Server, create and configure the metadata repository (“xmeta”).
4) If you are using WebSphere Information Analyzer, create and configure the
analysis database (“iadb”).
5) If you are not using the installation of WebSphere Application Server that is
provided with IBM Information Server, install and configure WebSphere
Application Server to be the domain server for IBM Information Server.
6) Install IBM Information Server.
7) Review all installation logs.
8) Check for an install any applicable IBM Information Server fix packs and
patches.
9) Review the fix pack and patch installation program log files.
10) Install and configure optional IBM Information Server components.
11) (if applicable) Configure any applicable post-installation operating system
settings.
12) (if applicable) Verify cluster/grid configuration.
13) Configure and verify IBM Information Server environment and defaults.
14) Verify IBM Information Server administration (shell) environment.
15) Configure IBM Information Server users, roles, and permissions.
16) Configure and verify IBM Information Server connectors.
17) Configure and verify client installation(s).
18) (where applicable) Install client fix packs, patches, and optional components.
19) Review client installation, client fix pack, and client patch installation log
files.
20) Create and verify parallel configuration files.
21) Create and verify IBM Information Server projects.
22) Verify project permissions and security settings/roles.

Appendix C: IBM Information Server Installation Settings

The following table summarizes the various settings and values supplied to the IBM Information
Server installation program, in the order they are supplied to the program.
It is important to note that not all options in this table will appear, depending on the options chosen in
the installation program.
Configuration Topic Installation Option Default Value Installation

Value
Install Response File /root/is_install.rsp
Install Directory /opt/IBM/InformationServer/
Components Engine TRUE
Domain TRUE
Metadata Repository TRUE
Documentation TRUE
License File Name and Location /root/license.xml
Product Module and Metadata Server TRUE
Component Selection Business Glossary TRUE
Information Analyzer TRUE
(Depends on license) Federation Server TRUE FALSE
DataStage and QualityStage TRUE
WebSphere Information TRUE
Services Director
Install Type Typical or Custom Typical
DataStage Server Install New or Upgrade Install New
Metadata Server Type (DB2 v8, DB2 v9, Oracle DB2 v9
Database Connection 10, SQLServer)
Host Localhost
TCP-IP Port 50000
Database Name xmeta
Database Owner xmeta
Password xmeta1
WebSphere Install Type: New or Configure New
Application Server Existing
WAS Profile (for existing) default
Destination Directory /opt/IBM/WebSphere/AppServer
Metadata Server User Internal vs. Local OS registry Internal registry
Registry AppSvr administrator user wasadmin
AppSvr administrator pass
Information Server Suite isadmin
Administrator user
Information Server Suite
Administrator password
DataStage Projects Project Name and Path
Information Analyzer Type (DB2 v8, DB2 v9, Oracle DB2 v9
Database Connection 10, SQLServer)
Host Localhost

Configuration Topic Installation Option Default Value Installation

Value
TCP-IP Port 50000
Database Name iadb
Database Owner iauser
Password
DB2 Configuration Language Selection (English always installed)
Install Location /opt/IBM/db2/V9
Admin Server user dasusr1
Admin Server password
Admin Server group dasadm1
Admin Server Home /home/dasusr1
Instance Owner user db2inst1
Instance Owner password
Instance Owner group db2iadm1
Instance Owner Home /home/db2inst1
Instance Port 50000
Fenced user db2fenc1
Fenced password
Fenced group db2fadm1
Fenced Home /home/db2fenc1
DataStage DataStage Administrator dsadm
Configuration DataStage Instance Tag ade
DataStage RPC Port 31538
Install NLS for DataStage FALSE TRUE
MQ Plug-In Enabled FALSE
MQ Plug-In Type Server
Oracle Operator Enabled FALSE
Oracle Operator Version 10g
Legacy SAS Operator Enabled FALSE
Legacy SAS Operator Version 8.0

Information Integration Solutions
Appendix D: Online Documentation Resources

Complete documentation for IBM Information Server is only available through the product installation
program. A subset is available and periodically refreshed online. This appendix summarizes the various
online references required for preinstallation tasks. These references are discussed in detailed sections
of this document.
Description URL
IBM Passport Advantage http://www.ibm.com/software/howtobuy/passportadvantage/index.html
Software Downloads
IBM Information Server 8.0.1 http://www.ibm.com/support/docview.wss?uid=swg24017220
Fix Pack 1a Download
IBM Software Support Handbook http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html
IBM Information Server
IBM Information Server Information http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r0/index.jsp
Center
IBM Information Server Publications http://www.ibm.com/support/docview.wss?rs=14&uid=swg27008803
Library (PDF and hardcopy books)
IBM Information Server Release http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r0/topic/com.ibm.swg.
Notes im.iis.productization.iisinfsv.nav.doc/containers/cont_iisinfsrv_rnote.html
IBM Information Server System http://www.ibm.com/support/docview.wss?uid=swg27008923
Requirements
IBM Information Server Product http://www.ibm.com/software/data/integration/support/info_server/
Support
IBM developer Works – Information http://www.ibm.com/developerworks/db2/products/integration/index.html
Integration ?S_TACT=105AGX11&S_CMP=FP
WebSphere Application Server 6.0
WebSphere Application Server 6.0 http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.web
Information Center sphere.base.doc/info/welcome_base.html
WebSphere Application Server 6.0.2 http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.web
Release Notes sphere.base.doc/info/aes/ae/v6rn.html
WebSphere Application Server 6.0.2 http://www.ibm.com/support/docview.wss?rs=180&uid=swg27007250
Hardware Requirements
WebSphere Application Server 6.0.2 http://www.ibm.com/support/docview.wss?rs=180&uid=swg27007256
Software Requirements
DB2 V9.1
DB2 Database for Linux, UNIX, and http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp
Windows V9.1 Information Center
DB2 V9.1 Release Notes http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.ud
b.doc/doc/c0023859.htm
DB2 v9.1 System Requirements http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.ud
b.uprun.doc/doc/r0025127.htm
DB2 V9.1 Fix Pack Downloads http://www.ibm.com/support/docview.wss?rs=71&uid=swg21255572

Appendix E: Network Ports used by IBM Information Server

The following table summarizes the list of network ports used by IBM Information Server.
Component Description Default Port Numbers

Metadata repository: DB2 When using DB2 for the metadata repository 50000
listener port
Metadata repository: Oracle When using Oracle for the metadata repository 1521
listener port
IBM Information Server IBM Information Server admin 31531, 31533
agents
IBM Information Server IBM Information Server admin 9080 *
Web console
Report Server DHTML Reports Server 16581 *
DataStage RPC daemon DataStage client listener 31538 *
DataStage and QualityStage Job Monitor listener port 1 13400
job monitor Job Monitor listener port 2 13401
IBM Information Server Engine Conductor / Section Leader >= 10000
parallel engine ($APT_PM_START_PORT)
Engine Player to Player Data Transfer for >= 11000
cluster/grid
($APT_PLAYER_CONNECTION_PORT)
Domain server ports WebSphere Application Server Administrative 9060 *
(WebSphere Application Console port (WC_adminhost)
Server) HTTPS transport port (WC_defaulthost_secure) 9443
WebSphere Application Server Administrative 9043 *
Console secure port (WC_adminhost_secure)
Bootstrap port (BOOTSTRAP_ADDRESS) 2809 *
Bootstrap port for deployment manager 9809
(BOOTSTRAP_ADDRESS)
SOAP connector port 8880
(SOAP_CONNECTOR_ADDRESS)
ORB listener port (ORB_LISTENER_ADDRESS) 9100 *
SSL listener ports 9401-9403 *
High Availability Manager communication port 9353
(DCS_UNICAST_ADDRESS)
Service integration port 7276
(SIB_ENDPOINT_ADDRESS)
Service integration secure port 7286
(SIB_ENDPOINT_SECURE_ADDRESS)
MQ Transport port 5558
(SIB_MQ_ENDPOINT_ADDRESS)
MQ Transport secure port 5578
(SIB_MQ_ENDPOINT_SECURE_ADDRESS)
Ports listed with an asterisk (*) need to be configured for firewall access when clients are on the other
side of the firewall from the engine, domain, and metadata repository components.

Appendix F: Glossary
Term Definition
domain tier IBM Information Server platform services (common and
product-specific services) and the application server in which
they run (WebSphere Application Server).
engine tier IBM Information Server engine and associated components.
The parallel engine is used to run WebSphere DataStage and
QualityStage parallel jobs. It’s also used by WebSphere
Information Analyzer to perform analysis. The engine tier
also includes the components required to manage multiple
instances of the engine and the components to run server jobs.
layer or tier A set of IBM Information Server components that must be
installed on the same computer. The four logical tiers are
engine, domain, metadata repository, and client.
metadata repository tier The database used to store IBM Information Server design,
configuration, and runtime metadata.
Metadata Server A product module that is comprised of the metadata
repository and the IBM Information Server common services.

Appendix G: Utilizing HP-UX 11 Memory Windows

Memory windows allow applications to utilize more than the 1.75 GB limit imposed on 32-bit
processes by HP-UX 11 and 11i. In order to use this feature for IBM Information Server parallel jobs,
you first need to understand exactly how much memory is being utilized by the job. For parallel jobs,
this can be estimated by calculating the total data size of all lookup tables used by a particular job.
Let’s take the example of a 32 processor machine with 32 GB of memory, called hptest. The default
configuration file for this machine would contain 16 nodes, each with the fast name entry “hptest”. If
the jobs that are going to be run on this will utilize a maximum of 8 GB, we would want to use at least
8 memory windows, because each window can hold up to 1 GB of memory. Below are the instructions
on how you would go about setting up the system and IBM Information Server’s parallel engine to
utilize 8 memory windows.
1. Change the kernel tunable max_mem_window from 0 to 40 and reboot the machine.
2. Create seven new entries in the /etc/hosts file, all pointing to the current machine. For example,
if the machine is called hptest, the original /etc/hosts file probably looks like:
# @(#)hosts $Revision: 1.9.214.1 $ $Date: 96/10/08 13:20:01 $

#
# The form for each entry is:
# <internet address> <official hostname> <aliases>
#
# For example:
# 192.1.2.34 hpfcrm loghost
#
# See the hosts(4) manual page for more information.
# Note: The entries cannot be preceded by a space.
# The format described in this file is the correct format.
# The original Berkeley manual page contains an error in
# the format description.
#
134.168.56.29 hptest
Add the following line:
134.168.56.29 hptest1 hptest2 hptest3 hptest4 hptest5 hptest6 hptest7
3. If your machine is set up to trust a limited number of machines, then add each of the new
hostnames (hptest1, … , hptest7) to your ~/.rhosts or /ext/hosts.equiv file.
4. Create an entry in the /etc/services.window file for each hostname alias being used. For
example:
#
# /etc/services.window
#
# The format of this file is name followed by a space/tab followed
# by a unique user key. A memory window application uses the
# getmemwindow(1M) command to extract the user key and then passes

# that key to the setmemwindow(1M) command. Using the same key
# places those applications in the same memory window.
#
# For example:
#
# winid=getmemwindow database1
# setmemwindow -i $winid startup_script arg1 arg2 arg3.
#
hptest 10
hptest1 11
hptest2 12
hptest3 13
hptest4 14
hptest5 15
hptest6 16
hptest7 17
5. Modify your 16 node $APT_CONFIG_FILE, so the fastname entries are divided between
evenly across hptest through hptest7.
6. Ensure that the user can run remsh to the current node by trying the following command:
remsh hptest ls
7. Add the following file (named startup.apt) in the $APT_ORCHHOME/etc directory and make
sure it is executable. If you want to disable the use of memory windows in the future, you can
do so by setting the $APT_NO_STARTUP_SCRIPT environment variable.
#!/bin/sh
shift 2
winid=$(getmemwindow $8)
echo "hostname="$8 "windowid="$winid
setmemwindow -i $winid -p $$
exec $*
8. Test this new configuration with a sample parallel job and the new $APT_CONFIG_FILE. (A
simple Column Generator to Peek will work as a test.)
NOTE: When using memory windowing technique for large lookup tables, you must hash
partition the incoming data and all reference tables using the same key columns. The default
“Entire” partitioning will not use memory windowing.

Appendix H: Example User Setup for UNIX Environments

The following UNIX commands will create the following groups and users required to install and
configure IBM Information Server:
User Account Default Primary Secondary Notes

User name Group Group
WebSphere DataStage dsadm dstage
administrator
DB2 administration server dasusr1 dasadm1 Only needed for DB2
DB2 instance owner db2inst1 db2iadm1 dasadm1 Only needed for DB2
DB2 fenced user db2fenc1 db2fadm1 Only needed for DB2
IBM Information Server metadata xmeta xmeta DB2 uses OS authentication
repository owner
WebSphere Information Analyzer iauser iauser DB2 uses OS authentication
analysis database owner
groupadd db2iadm1
groupadd db2fadm1
groupadd dasadm1
groupadd dstage
useradd -gdb2fadm1 -pdb2fenc1 -m -d /home/db2fenc1 db2fenc1

useradd -gdb2iadm1 -Gdasadm1 -pdb2inst1 -m -d /home/db2inst1 db2inst1
useradd -gdasadm1 -pdasusr1 -m -d /home/dasusr1 dasusr1
useradd -gdstage -pdsadm -m -d /home/dsadm dsadm
useradd -piasuer -m -d /home/iauser iauser
useradd -pxmeta100 -m -d /home/xmeta xmeta


Infosrv Pre Install Checklist v801

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Infosrv Pre Install Checklist v801

Transféré par

Droits d'auteur :

Formats disponibles

Information Platform and Solutions

IBM Information Server

IBM Information Platform and Solutions

April 25, 2008

IBM Information Server Preinstallation Checklist April 25, 2008 1 of 50

IBM Director of Licensing

IBM World Trade Asia Corporation

IBM Information Server Preinstallation Checklist April 25, 2008 2 of 50

IBM Information Server Preinstallation Checklist April 25, 2008 3 of 50

See www.ibm.com/legal/copytrade.shtml for information about IBM trademarks.

The following terms are trademarks or registered trademarks of other companies:

IBM Information Server Preinstallation Checklist April 25, 2008 4 of 50

The following are also used:

IBM Information Server Preinstallation Checklist April 25, 2008 5 of 50

%etl_node%:dsadm /opt/ibm >

IBM Information Server Preinstallation Checklist April 25, 2008 6 of 50

IBM Information Server Preinstallation Checklist April 25, 2008 7 of 50

1 IBM Information Server Preinstallation Overview

IMPORTANT: Establishing an IBM Information Server environment that meets performance

IBM Information Server Preinstallation Checklist April 25, 2008 8 of 50

IBM Information Server Preinstallation Checklist April 25, 2008 9 of 50

IBM Information Server Preinstallation Checklist April 25, 2008 10 of 50

2.1 Review Release Notes

2.1.1 IBM Information Server Release Notes

2.1.2 WebSphere Application Server Release Notes

2.1.3 DB2 Enterprise Server Edition Release Notes

IBM Information Server Preinstallation Checklist April 25, 2008 11 of 50

2.2 Review Planning, Installation, and Configuration Guide

 PDF book: http://www.ibm.com/support/docview.wss?uid=swg27008803

2.3 (if applicable) Review Migrating to IBM Information Server

 PDF book: http://www.ibm.com/support/docview.wss?uid=swg27008803

IBM Information Server Preinstallation Checklist April 25, 2008 12 of 50

2.4 Choose and Validate an Installation Architecture / Topology

Layer Description Architectural Notes

Requires 32-bit versions of Windows XP, Windows

Requires WebSphere Application Server

IBM Information Server Preinstallation Checklist April 25, 2008 13 of 50

2.4.1 Two-Tier Deployment

 Client(s): Client applications on Windows systems.

The IBM Information Server versions of all components must match.

IBM Information Server Preinstallation Checklist April 25, 2008 14 of 50

2.4.2 Three-Tier Deployment

 Client(s): Client applications on Windows systems.

The operating system of the two servers should be the same.

IBM Information Server Preinstallation Checklist April 25, 2008 15 of 50

2.4.3 Four-Tier Deployment

 Client(s): Client applications on Windows systems.

2.4.4 Cluster and Grid Deployments

2.4.5 Wide Area Network (WAN) Deployments

IBM Information Server Preinstallation Checklist April 25, 2008 16 of 50

IBM Information Server System Requirements:

2.6 Verify Domain and WebSphere Application Server Requirements

WebSphere Application Server 6.0.2 Hardware Requirements:

WebSphere Application Server 6.0.2 Software Requirements:

IBM Information Server Preinstallation Checklist April 25, 2008 17 of 50

2.7 Verify Database Requirements for the Metadata Repository

DB2 V9.1 Requirements:

IMPORTANT: Although the IBM Information Server System requirements recommend a

IBM Information Server Preinstallation Checklist April 25, 2008 18 of 50

IMPORTANT: While the IBM Information Server System Requirements recommend a

IBM Information Server Preinstallation Checklist April 25, 2008 19 of 50

Ultimate performance of an IBM Information Server job (WebSphere DataStage, WebSphere

IBM Information Server Preinstallation Checklist April 25, 2008 20 of 50

2.9.2 IBM Information Server File Systems

PDF book: http://www.ibm.com/support/docview.wss?uid=swg27008803

PDF book: http://www.ibm.com/support/docview.wss?uid=swg27008803

Client(s): Client applications on Windows systems.

Client(s): Client applications on Windows systems.

Client(s): Client applications on Windows systems.

IBM Information Server project (runtime shadow repository) directories

Data file storage