You are on page 1of 503

IBM InfoSphere Information Server

Version 8 Release 5

Planning, Installation, and
Configuration Guide 

GC19-1048-08

IBM InfoSphere Information Server
Version 8 Release 5

Planning, Installation, and
Configuration Guide 

GC19-1048-08

Note
Before using this information and the product that it supports, read the information in “Notices and trademarks” on page
475.

© Copyright IBM Corporation 2005, 2010.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.

Contents
Information road maps . . . . . . . . ix Project naming conventions . . . . . . . . . 78
New installation road map (no high availability) . . 79
Sample scenario A: Basic client-server topology 84
Part 1. Planning for the installation Sample scenario B: Topology with isolated engine
of IBM InfoSphere Information tier and parallel engine configuration. . . . . 88
Server . . . . . . . . . . . . . . . 1 New installation road map (high availability
active-passive configuration). . . . . . . . . 93
Sample scenario C: Two-server active-passive
Chapter 1. Planning Step 1: Reviewing
high availability topology . . . . . . . . 99
system requirements and release notes . 3 New installation road map (high availability
clustered topology) . . . . . . . . . . . 105
Chapter 2. Planning Step 2: Sample scenario D: Topology with clustered
Understanding tiers and components . . 5 metadata repository tier and services tier . . . 114
Client tier . . . . . . . . . . . . . . . 6 Adding product modules to an existing installation 122
Engine tier . . . . . . . . . . . . . . . 7
Services tier . . . . . . . . . . . . . . 10 Part 2. Preparing the tier
Metadata repository tier . . . . . . . . . . 12
Tier relationships . . . . . . . . . . . . 12
computers . . . . . . . . . . . . 125

Chapter 3. Planning Step 3: Designing Chapter 5. Computer preparation road
an installation topology . . . . . . . 15 maps . . . . . . . . . . . . . . . 127
Basic installation topologies . . . . . . . . . 15 Preparation road map for the metadata repository
Single computer topology . . . . . . . . 16 tier computer . . . . . . . . . . . . . 127
Client/server topology . . . . . . . . . 16 Preparation road map for the services tier
Dedicated engine tier topology . . . . . . . 17 computer . . . . . . . . . . . . . . . 128
Dedicated computer for each tier topology . . . 18 Preparation road map for the engine tier
Locations for the analysis databases . . . . . 19 computers . . . . . . . . . . . . . . 128
Locations for the Match Designer database . . . 21 Preparation road map for the client tier computers 129
Multiple instances of IBM InfoSphere Information
Server . . . . . . . . . . . . . . . 22 Chapter 6. Obtaining IBM InfoSphere
Multiple server engines . . . . . . . . . 26 Information Server software . . . . . 131
High availability configurations . . . . . . . 27
Active-passive topology . . . . . . . . . 28 Chapter 7. Preparation steps for all
IBM WebSphere Application Server Network
tier computers . . . . . . . . . . . 133
Deployment clustering. . . . . . . . . . 31
Verifying the network and opening ports . . . . 133
IBM DB2 high availability options . . . . . . 42
Modifying kernel parameters and user limits
Oracle database high availability options . . . 47
(Linux, UNIX) . . . . . . . . . . . . . 137
Other considerations when designing for high
Setting up administrator and owner accounts. . . 142
availability . . . . . . . . . . . . . 48
Naming restrictions for user IDs and passwords 145
Designing a high availability topology . . . . 49
Parallel processing and grid topologies . . . . . 53
Parallel processing configurations . . . . . . 53 Chapter 8. Additional preparation
Grid configurations . . . . . . . . . . . 55 steps for the metadata repository tier
Capacity planning . . . . . . . . . . . . 57 computer . . . . . . . . . . . . . 147
Preinstalling the IBM DB2 database system . . . 147
Chapter 4. Planning Step 4: Preparing an existing DB2 database system . . . 148
Determining your installation strategy . 59 Preparing an existing DB2 database system by
Determining your database installation strategy . . 61 using the installation program . . . . . . . 148
Determining your database topology . . . . . 61 Preparing an existing DB2 database system by
Determining the database installation method . . 63 using scripts. . . . . . . . . . . . . 149
Sizing the analysis databases . . . . . . . 65 Using an IBM DB2 for z/OS database system
Determining how to install WebSphere Application for the databases . . . . . . . . . . . 150
Server . . . . . . . . . . . . . . . . 66 Using a database system other than DB2 . . . . 152
Planning volume groups and file systems . . . . 67
Secure Sockets Layer (SSL) configuration . . . . 76

© Copyright IBM Corp. 2005, 2010 iii

Chapter 9. Additional preparation Installing IBM InfoSphere Business Glossary Client
steps for the services tier computer . 153 for Eclipse . . . . . . . . . . . . . . 221
Preinstalling WebSphere Application Server . . . 153 Installing z/OS components for IBM InfoSphere
Configuring an existing WebSphere Application DataStage MVS Edition . . . . . . . . . . 224
Server installation (non-clustered installation) . . 154 Installing COBOL copybook files . . . . . . 225
Configuring the front-end HTTP server for HTTPS 155 Installing the runtime library for z/OS jobs . . 226
Installation verification process for z/OS
components . . . . . . . . . . . . . 227
Chapter 10. Additional preparation Installing IBM InfoSphere Blueprint Director . . . 228
steps for the engine tier computers . . 157
Setting the locale for the target computer . . . . 157
Character encodings supported by IBM Part 4. Configuring the software
InfoSphere Information Server. . . . . . . 158 after installation . . . . . . . . . 229
Installing a C++ compiler for job development . . 159
Chapter 15. Firewall exceptions for
Chapter 11. Preparing for the IBM client-side executable files (Windows). 231
InfoSphere QualityStage Match
Designer database . . . . . . . . . 161 Chapter 16. Enablement of Secure
Sockets Layer (SSL) . . . . . . . . 233
Part 3. Installing IBM InfoSphere Enabling SSL for inbound RMI/IIOP . . . . . 233
Manually configuring InfoSphere Information
Information Server software . . . . 165
Server components to use HTTPS . . . . . . 234
Running UpdateSignerCerts after enabling SSL or
Chapter 12. Installing new software 167 changing SSL at the cell level . . . . . . . . 236
Creating an installation . . . . . . . . . . 167 Replacing WebSphere Application Server
Adding product modules to an installation . . . 173 certificates . . . . . . . . . . . . . . 239
Adding an additional software tier to a computer 175 Switching from HTTPS back to HTTP . . . . . 240
Starting the installation program . . . . . . . 177
Preparing to run the installation program . . . 177 Chapter 17. Configuring security for
Graphical mode . . . . . . . . . . . 180
Silent mode . . . . . . . . . . . . . 186
IBM InfoSphere Information Server . . 243
setup command syntax . . . . . . . . . 189
Response files . . . . . . . . . . . . 191 Chapter 18. Configuring product
Monitoring installation progress . . . . . . . 194 modules in the suite . . . . . . . . 245
Monitoring the IBM InfoSphere Information Configuring IBM InfoSphere DataStage and IBM
Server installation . . . . . . . . . . . 194 InfoSphere QualityStage . . . . . . . . . . 245
Monitoring the IBM WebSphere Application Ensuring that InfoSphere DataStage users have
Server installation . . . . . . . . . . . 195 the correct localization settings (Linux, UNIX) . 246
Monitoring the IBM WebSphere Application Configuring access to ODBC data sources . . . 247
Server enterprise archive deployment . . . . 196 Tuning the InfoSphere Information Server
Monitoring IBM InfoSphere DataStage engine for large numbers of users or jobs
component installations . . . . . . . . . 196 (Windows Server) . . . . . . . . . . . 252
Installation verification and troubleshooting . . . 197 Configuring IBM InfoSphere QualityStage
Installation program sample scenarios . . . . . 198 Match Designer . . . . . . . . . . . 253
Running the installation program for Scenario A 198 Setting up application servers to run SQA or
Running the installation program for Scenario B 201 investigation reports . . . . . . . . . . 253
Running the installation program for Scenario C 204 Testing the installation of IBM InfoSphere
Running the installation program for Scenario D 207 QualityStage and IBM InfoSphere DataStage . . 254
Testing the IBM InfoSphere Information Services
Chapter 13. Updating products and Director installation . . . . . . . . . . . 256
components . . . . . . . . . . . . 213 Configuring IBM InfoSphere Information Analyzer 256
Configuring IBM InfoSphere Business Glossary . . 258
Configuring IBM InfoSphere Metadata Workbench 258
Chapter 14. Installing components Configuring IBM InfoSphere FastTrack . . . . . 258
that are not in the suite installation
program . . . . . . . . . . . . . 215 Chapter 19. Configuring a parallel
Installing the IBM InfoSphere Business Glossary processing environment. . . . . . . 261
Anywhere client . . . . . . . . . . . . 215
Adding computers to share engine processing . . 261
Preparing for enterprise-wide distribution . . . 215
Configuring a computer to be a processing node
Installing the client . . . . . . . . . . 219
for MPP (Linux, UNIX) . . . . . . . . . 261

iv Planning, Installation, and Configuration Guide

Copying the parallel engine components to Example: Setting up an active-passive
system nodes (Linux, UNIX) . . . . . . . 264 configuration by using IBM Tivoli System
Copying parallel engine components to Automation for Multiplatforms . . . . . . 301
processing nodes (Windows) . . . . . . . 265 Creating an active-passive configuration (Microsoft
Configuring a computer to be a processing node Windows) . . . . . . . . . . . . . . 313
for MPP (Windows) . . . . . . . . . . 265 Example: Setting up an active-passive
Setting environment variables for the parallel configuration by using the Microsoft Cluster
engine . . . . . . . . . . . . . . . . 267 service (MSCS) . . . . . . . . . . . . 315
Environment variables for the parallel engine 267 High availability control scripts included with IBM
Specifying C++ compiler settings . . . . . . 269 InfoSphere Information Server. . . . . . . . 320
Configuring the parallel engine (Linux, UNIX) . . 270
Setting the maximum number of processes for Chapter 23. WebSphere Application
parallel jobs (AIX) . . . . . . . . . . . 270 Server clustering for high availability
Setting per-user kernel parameters for parallel
jobs (AIX) . . . . . . . . . . . . . 271
and scalability . . . . . . . . . . . 323
Setting the paging space for the parallel engine 272 Implementing a WebSphere Application Server
Updating the /etc/magic file . . . . . . . 275 cluster for InfoSphere Information Server . . . . 324
Configuring the parallel engine (Windows Server) 275 Installing IBM WebSphere Application Server
Configuring the Windows Registry: Enabling Network Deployment for a cluster installation . 324
auto-tuning for paged pool size . . . . . . 276 Creating a deployment manager profile . . . 325
Configuring the Windows Registry: Enabling Creating a custom profile . . . . . . . . 326
auto-tuning for system page size . . . . . . 277 Creating a cluster and cluster members for the
Configuring the Windows registry: Setting the application server . . . . . . . . . . . 326
threshold for de-committing memory . . . . 278 Installing a front-end Web server . . . . . . 328
Configuring the Windows registry: Increasing Installing a front-end load balancer (Optional) 329
the noninteractive desktop heap size . . . . 278 Running the installation program (clustered
Configuring the Windows registry: Specifying installation) . . . . . . . . . . . . . 330
TCP/IP settings . . . . . . . . . . . 279 Changing the front-end dispatcher location . . . 331
Configuring Windows: Changing swap area size 280 Configuring a cluster to run as a service
Configuring Windows: Editing the boot.ini file 281 (Windows) . . . . . . . . . . . . . . 333
Configuring database connectivity in a parallel
environment. . . . . . . . . . . . . . 282 Chapter 24. Metadata repository tier
Configuring access to DB2 databases . . . . 282 clustering for high availability . . . . 337
Configuring access to Oracle databases . . . . 284 Configuring the metadata repository database in
Configuring access to Teradata databases . . . 285 an IBM DB2 cluster . . . . . . . . . . . 337
Configuring access to Informix XPS databases 286 Preparing the servers, file system, and storage 338
Installing high availability software on DB2
Chapter 20. Stopping and starting the database system servers . . . . . . . . . 339
server engine . . . . . . . . . . . 287 Installing the DB2 database system and creating
the cluster and metadata repository database . . 340
Running the installation program for a setup
Chapter 21. Changing host names and that includes DB2 clustering . . . . . . . 341
ports . . . . . . . . . . . . . . . 289 Configuring automatic client reroute . . . . 342
Changing the WebSphere Application Server HTTP Specifying the alternate database address and
port . . . . . . . . . . . . . . . . 289 port for IBM WebSphere Application Server . . 342
Changing other WebSphere Application Server Verifying the IBM DB2 database cluster . . . 345
ports . . . . . . . . . . . . . . . . 291 Setting up the metadata repository database in an
Changing the metadata repository database host IBM DB2 database HADR configuration . . . . 345
name and port . . . . . . . . . . . . . 292 Preparing the servers, storage, and network . . 346
Installing the DB2 database system and creating
Part 5. Creating highly available, the metadata repository database . . . . . . 347
Running the installation program for an HADR
scalable configurations . . . . . . 297 configuration . . . . . . . . . . . . 348
Configuring the HADR primary server . . . . 348
Chapter 22. Creating a two-server Configuring the HADR standby server . . . . 350
active-passive high availability Specifying the alternate database address and
configuration . . . . . . . . . . . 299 port for IBM WebSphere Application Server . . 351
Creating an active-passive configuration (Linux, Starting HADR . . . . . . . . . . . . 353
UNIX) . . . . . . . . . . . . . . . . 299 Validating the HADR configuration . . . . . 355
Configuring the metadata repository database in
an Oracle RAC cluster . . . . . . . . . . 356

Contents v

Oracle RAC requirements . . . . . . . . 357 Chapter 30. Application server
Creating the metadata repository database and problems . . . . . . . . . . . . . 407
running the installation program within an Resolving IBM WebSphere Application Server
Oracle RAC configuration . . . . . . . . 357 installation problems . . . . . . . . . . . 407
Connecting to an Oracle RAC configuration . . 358 Installation fails when the IBM WebSphere
Application Server port is changed after
Part 6. Removing IBM InfoSphere installation . . . . . . . . . . . . . . 408
Information Server software . . . . 359 Resolving connection problems . . . . . . . 408
Unable to start IBM WebSphere Application Server
after the user name changes or expires . . . . . 409
Chapter 25. Software removal by Adding an IBM WebSphere Application Server
using the software removal program . 361 administrator user to an internal user registry . . 411
Shutting down tasks and applications before Repairing the WebSphere Application Server
removing software . . . . . . . . . . . 361 registry after switching to LDAP . . . . . . . 412
Removing an IBM InfoSphere Information Server Services tier performance . . . . . . . . . 413
installation . . . . . . . . . . . . . . 362
Removing individual product modules . . . . . 363 Chapter 31. IBM InfoSphere
Removing a software tier . . . . . . . . . 366
Information Server reporting problems 415
Starting the software removal program . . . . . 367
Cannot view report result from InfoSphere
Preparing to run the software removal program 368
Information Server console or InfoSphere
Graphical mode . . . . . . . . . . . 369
Information Server Web console . . . . . . . 415
Silent mode . . . . . . . . . . . . . 375
Enabling and disabling trace logging of the
Completing software removal (Windows) . . . . 378
reporting engine . . . . . . . . . . . . 415
Completing software removal (Linux, UNIX) . . . 380

Chapter 26. Manual software removal 383 Chapter 32. Client and console
Manually removing IBM InfoSphere Information problems . . . . . . . . . . . . . 417
Server (Windows) . . . . . . . . . . . . 383 Java Virtual Machine fails to load . . . . . . 417
Manually removing IBM InfoSphere Information Rich client login failure . . . . . . . . . . 417
Server (Linux, UNIX) . . . . . . . . . . . 386 Resolving problems logging in to the IBM
WebSphere Application Server administrative
console . . . . . . . . . . . . . . . 419
Part 7. Troubleshooting Connection problems after IBM WebSphere
installations . . . . . . . . . . . 391 Application Server cluster members are removed . 420

Chapter 27. Log files . . . . . . . . 393 Chapter 33. Removal problems . . . . 423
Installation log files . . . . . . . . . . . 393 IBM InfoSphere Information Server installation
Temporary files generated by installation program 393 fails repeatedly . . . . . . . . . . . . . 423
IBM WebSphere Application Server system log files 394 Ignoring runtime error during uninstallation . . . 423
MKS Toolkit errors occur when uninstalling clients 424
Chapter 28. General installation
problems . . . . . . . . . . . . . 397 Part 8. Appendixes . . . . . . . . 427
"User credentials are not valid" error appears
unexpectedly during installation . . . . . . . 397 Appendix A. Response file parameters
IWAV0003E warning in installation log file . . . 397 (Linux, UNIX) . . . . . . . . . . . 429
Warnings occur during installation of DB2. . . . 398
Installation problems with VMware ESX . . . . 399
User creation errors appear in log files (Linux, Appendix B. Response file parameters
UNIX) . . . . . . . . . . . . . . . . 399 (Windows). . . . . . . . . . . . . 441
"The publisher could not be verified" message . . 400
"There is no script engine for file extension '.js'" Appendix C. Naming restrictions for
message appears during installation . . . . . . 400 user IDs and passwords. . . . . . . 451
Installation process hangs when a web browser
session is closed . . . . . . . . . . . . 401
Appendix D. Installation checklists 453
Installation checklist with separate engine tier . . 453
Chapter 29. Authentication problems 403 Installation checklist with IBM WebSphere
Directory and user permissions . . . . . . . 403 Application Server cluster and IBM DB2 cluster . . 459
User privileges . . . . . . . . . . . . . 406
Product accessibility . . . . . . . . 467

vi Planning, Installation, and Configuration Guide

Accessing product documentation 469 Notices and trademarks . . . . . . . 475

Reading command-line syntax . . . . 471 Contacting IBM . . . . . . . . . . 479

Links to non-IBM Web sites . . . . . 473 Index . . . . . . . . . . . . . . . 481

Contents vii

viii Planning, Installation, and Configuration Guide

im. 2.com/infocenter/iisinfsv/v8r5/topic/ com. 2010 ix .iisinfsv.doc/topics/ cont_iisinfsrv_install. 2005. The current version and the translated versions of this information are on the Web at publib. Read this manual to perform the installation.ibm.Information road maps IBM® InfoSphere™ Information Server includes a set of collaborative product modules and components that can be distributed across multiple computers.productization. Review the Release Notes for the latest information to ensure successful installations. © Copyright IBM Corp. 3.iis. To learn about the installation process: 1.install.swg. Read the Quick Start Guide for the installation overview.boulder. Review the system requirements and download the product if you have not already documented it.ibm.html The following table provides road maps for different InfoSphere Information Server installation paths. 4.

Part 1. “Installing IBM InfoSphere Information Server software. This section includes detailed software installation road maps for different topologies. and determine your installation strategy. Also determine which application server to install or repurpose.” on page 125 Prepare each of your computers for the components that you will install on them.” on page 297 Use this section if you plan to implement high availability or scalability for different software tiers.” on page 1 Review system requirements. “Creating highly available. Learn about software tiers and components. and Configuration Guide . “Preparing the tier computers.Table 1. “Configuring the software after installation. Also install components that the installation program does not install. Part 2.” on page 165 Run the InfoSphere Information Server installation program on each target computer and verify the installation. Installation. Part 5. Installation information road maps Task Information resources Create a new installation of InfoSphere Information Appendix D. scalable configurations. “Planning for the installation of IBM InfoSphere Information Server. x Planning. “Installation checklists.” on page 229 Complete additional configuration tasks for the product modules that you installed or the features that you want to enable. or if you plan to configure the InfoSphere Information Server parallel engine to use multiple computers. Part 3.” on page 453 Server These checklists guide you through the complete installation process for specific scenarios. Design your topology. Part 4. Determine which database system to install or repurpose.

5 installation and then migrate your data to the new installation.” on page 215 installation of InfoSphere Information Server. “Troubleshooting installations. You install these components after you install InfoSphere Information Server.5 Some components have their own installation programs.” on page 391 issues Resolve installation problems with this installation troubleshooting information.” on page 1 Review system requirements to ensure that your existing installation meets all requirements. Information road maps xi . “Preparing the tier computers. Part 3. Version 8.” on page 125 Prepare each of your target computers for the components that you will install on them. Remove a product module or an entire installation of Part 6. Upgrade from an earlier version of InfoSphere To upgrade an existing installation. You can find more troubleshooting information in the information centers and customer support technotes for various product modules and components.” on page 165 Run the InfoSphere Information Server installation program on each target computer and verify the installation. For upgrade information. Troubleshoot InfoSphere Information Server installation Part 7. Version 8. “Installing components that are not in the Information Server installation program to an existing suite installation program. run the InfoSphere Information Server installation program. see the IBM InfoSphere Information Server Migration Guide. refer to “Installation verification and troubleshooting” on page 197. “Installing IBM InfoSphere Information Server software. Add hardware if necessary. “Planning for the installation of IBM InfoSphere Information Server Version 8. Part 2.5 software. Add a component that is not included in the InfoSphere Chapter 14. “Removing IBM InfoSphere Information Server InfoSphere Information Server. Installation information road maps (continued) Task Information resources Add a product module to an existing InfoSphere Part 1. For more information. “Configuring the software after installation.” on page 359 Run the InfoSphere Information Server software removal program on each target computer. To upgrade a client workstation.Table 1. Also install components that the installation program does not install. create a new Version Information Server 8. Part 4.” on page 229 Complete additional configuration tasks that correspond to the product modules that you installed or the features that you want to enable.5 installation Information Server.

and Configuration Guide .xii Planning. Installation.

learn about tiers and components. do these tasks: 1. 3. To plan an installation of InfoSphere Information Server. Learn about InfoSphere Information Server tiers and components. Review the system requirements and release notes. design your topology. review the system requirements. 2005.Part 1. Planning for the installation of IBM InfoSphere Information Server Before you install IBM InfoSphere Information Server. 2010 1 . Design the topology of your installation. 2. and determine your installation steps. Install product modules on your computers. 4. © Copyright IBM Corp.

and Configuration Guide .2 Planning. Installation.

productization. 2005.html.ibm.wss?rs=14 &uid=swg27016382. see these resources: v The system requirements at www.doc/topics/ iisihrinfo_infsv_rnote_v85.iisinfsv.relinfo.boulder.com/support/docview. 2010 3 .swg. To obtain the most up-to-date information about the installation requirements.com/infocenter/iisinfsv/v8r5/topic/ com. v The release notes at publib.ibm.im.iis. Planning Step 1: Reviewing system requirements and release notes Ensure that all computers meet the hardware and software requirements for the product modules that you want to install.ibm.Chapter 1. © Copyright IBM Corp.

4 Planning. Installation. and Configuration Guide .

The services tier provides common services (such as metadata and logging) and services that are specific to certain product modules. if installed. common services. The analysis database stores extended analysis data for InfoSphere Information Analyzer. IBM WebSphere® Application Server hosts the services. Each tier includes a subgroup of the components that make up the InfoSphere Information Server product modules. and user concurrency. to multiple-computer highly available configurations. The tiers provide services. The following table describes each tier. service agents. and so on) and the computer where those components are installed. you first design the hardware and software topology for each tier. © Copyright IBM Corp. and metadata and other data storage for your product modules. The services tier also hosts InfoSphere Information Server applications that are Web-based. data. performance and throughput. Your installation can range from simple single-computer configurations. Engine The logical group of components (the InfoSphere Information Server engine components. A tier is a logical group of components within InfoSphere Information Server and the computers on which those components are installed. 2005. Tiers Tier Description Client The client programs and consoles that are used for development and administration and the computers where they are installed. 2010 5 . Services The application server. The metadata repository database contains the shared metadata. The engine runs jobs and other tasks for product modules. On the tier. Planning Step 2: Understanding tiers and components You install IBM InfoSphere Information Server product modules in logical tiers. and configuration information for InfoSphere Information Server product modules. the IBM InfoSphere Information Analyzer analysis database and the computer where these components are installed. Table 2. and product services for the suite and product modules and the computer where those components are installed. Metadata repository The metadata repository and. to complex and powerful clusters with many computers. job execution.Chapter 2. To install InfoSphere Information Server. You optimize your topology design for the product modules that you install and your requirements for high availability.

After you design your topology. Commands for IBM InfoSphere Information Analyzer. in the appropriate tiers. Client tier InfoSphere InfoSphere Information Server console InfoSphere DataStage and InfoSphere Information InfoSphere QualityStage InfoSphere FastTrack Server Information Adminis. You also install any other components that the product module uses. based on the products and components that you select: v IBM InfoSphere Information Server console v IBM InfoSphere DataStage® and QualityStage Administrator client v IBM InfoSphere DataStage and QualityStage Designer client v IBM InfoSphere DataStage and QualityStage Director client v IBM InfoSphere FastTrack client v IBM MetaBroker®s and bridges v IBM InfoSphere Connector Migration Tool v IBM InfoSphere Information Server istool command line. to specify which tier or tiers to install on the computer. The following diagram shows the client tier. and Configuration Guide . Services clients Manager tration Analyzer Designer. The istool framework is installed on the engine tier and client tier. you install the product module components in their tiers. IBM InfoSphere Business Glossary. The following tools are installed as part of the client tier. You install InfoSphere Information Server tier by tier. and Director client client Director clients client Multi-client IBM MetaBrokers InfoSphere Connector istool manager and bridges Migration Tool command line Figure 1. When you run the installation program. Client tier components Other client programs The IBM InfoSphere Business Glossary Anywhere client has a separate installation program that is provided on the installation media. Installation. and InfoSphere FastTrack are installed on the clients only when those products are installed. and it installs the appropriate product module components in the tiers that you specify. This program is not installed by using the InfoSphere Information Server installation program: 6 Planning. Information Administrator. it prompts you to select the product modules to install. Client tier The client tier consists of the client programs and consoles that are used for development and administration and the computers where they are installed.

Windows Only one InfoSphere Information Server engine can be installed on a single computer. you can switch between Version 8. v IBM InfoSphere Information Server Web console. v IBM InfoSphere Metadata Workbench client v InfoSphere Business Glossary Browser client v IBM InfoSphere Information Server Manager client The Multi-Client Manager is installed when you install a product that includes InfoSphere DataStage and InfoSphere QualityStage client tier components. These components import metadata into and export metadata out of the metadata repository. Also use the Web console to work with InfoSphere Business Glossary and with the Information Services Catalog for IBM InfoSphere Information Services Director. The MKS Toolkit is installed in the client tier. Windows IBM MetaBrokers and bridges can be installed on Microsoft Windows. Several product modules require the engine tier for certain operations. IBM InfoSphere Business Glossary. You install the engine tier components as part of the installation process for these product modules. and so on) and the computer where those components are installed. The Multi-Client Manager enables you to switch between multiple versions of InfoSphere DataStage clients. and IBM InfoSphere Business Glossary Anywhere do not require an engine tier. The InfoSphere Information Server installation program also installs several Web-based clients. This toolset is used by the InfoSphere QualityStage migration utility. Chapter 2. A browser shortcut to the IBM InfoSphere Information Server Web console is created during the InfoSphere Information Server installation.5 and Version 7. if these product modules are installed. The following product modules require the engine tier: v IBM InfoSphere DataStage v IBM InfoSphere Information Analyzer v IBM InfoSphere Information Services Director v IBM InfoSphere Metadata Workbench v IBM InfoSphere QualityStage v IBM InfoSphere Information Server istool command line. IBM InfoSphere FastTrack. The istool framework is installed on the engine tier and client tier. These clients are installed as part of the services tier. For example. Planning Step 2: Understanding tiers and components 7 .5 clients. service agents. Engine tier The engine tier consists of the logical group of engine components (the IBM InfoSphere Information Server engine components. on engine tiers. The Web console provides access to all administrative and reporting features. Commands for InfoSphere Information Analyzer and InfoSphere Metadata Workbench are installed on the engine tier only when those products are installed. not the client tier.

Installation. The engine includes the server and parallel engines and other components that make up the runtime environment for InfoSphere Information Server and its product components. Linux UNIX The agent runs as a daemon that is named ASBAgent. each engine must be registered to a different services tier. or transformation. v Multiple engines on the same computer. Windows The agent runs as a service that is named LoggingAgent. In this configuration. The installation program installs the following engine components as part of each engine tier: InfoSphere Information Server engine Runs tasks or jobs such as discovery. ASB agents include: Connector access services agent Conveys service requests between the ODBC driver components on the engine tier and the connector access services component on the services tier. all registered to the same InfoSphere Information Server services tier. These drivers provide connectivity to source and target data. and Configuration Guide . Resource Tracker The installation program installs the Resource Tracker for parallel jobs with the engine components for InfoSphere DataStage and InfoSphere 8 Planning. This configuration is called an ITAG installation. When a service that runs on the services tier receives a service request that requires processing by an engine tier component. ODBC drivers The installation program installs a set of ODBC drivers on the engine tier that works with InfoSphere Information Server components. InfoSphere Information Analyzer agent Conveys service requests between the engine components on the engine tier and the InfoSphere Information Analyzer services component on the services tier. cleansing. the agent receives and conveys the request. Linux UNIX The agent runs as a daemon that is named LoggingAgent. InfoSphere Information Services Director agent Conveys service requests between the engine components on the engine tier and the InfoSphere Information Services Director services component on the services tier. analysis. Linux The following configurations are supported: UNIX v Multiple engines. each on a different computer. Logging agent Logs events to the metadata repository. ASB agents A Java process that runs in the background on each computer that hosts an InfoSphere Information Server engine tier. Windows The agent runs as a service that is named ASBAgent.

Windows DataStage engine resource service Establishes the shared memory structure that is used by server engine processes. The server controller process updates various files in the metadata repository with statistics such as the number of inputs and outputs. Windows This process runs as the DSRPC Service. Engine tier components Chapter 2. memory. The following diagram shows the components that make up the engine tier. Linux UNIX This process runs as a daemon (dsrpcd). Windows DataStage Telnet service Allows users to connect to the server engine by using Telnet. operator start time. The information is routed to the server controller process for the parallel engine job. Useful for debugging server engine-related issues. Items marked with asterisks (*) are only present in Microsoft Windows installations. dsrpcd (DSRPC Service) Allows InfoSphere DataStage clients to connect to the server engine. Does not need to be started for normal InfoSphere DataStage processing. Job monitor A Java application (JobMonApp) that collects processing information from parallel engine jobs. Engine tier Server engine Connectivity ASB agents (ODBC drivers) Connector access services agent Parallel InfoSphere Information engine Analyzer agent InfoSphere Information Services Director agent DataStage *IBM DataStage istool Logging *MKS Engine Job DSRPC Resource Metabrokers Telnet command agent Toolkit Resource monitor service Tracker and bridges Service line service Source and target data Figure 2. and I/O usage on each computer that runs parallel jobs. Planning Step 2: Understanding tiers and components 9 . QualityStage. the external resources that are accessed. and the number of rows processed. The Resource Tracker logs the processor. Windows MKS Toolkit Used by the InfoSphere Information Server parallel engine to run jobs.

Other services are specific to the product modules that you install. IBM InfoSphere DataStage. IBM InfoSphere QualityStage. Services tier services Product module-specific IBM InfoSphere Information Analyzer.Services tier The services tier consists of the application server. They also include connector access services that provide access to external data sources through the ODBC driver components and the connector access services agent on the engine tier. The following diagram shows the services that run on the application server on the services tier. The application server is included with the suite for supported operating systems. and product module-specific services and the computer where those components are installed. you can use an existing instance of WebSphere Application Server. common services for the suite. IBM InfoSphere Information Services Director. 10 Planning. For a list of supported versions. IBM InfoSphere FastTrack. if the version is supported by InfoSphere Information Server. Alternatively.com/support/ docview. and IBM InfoSphere Metadata Workbench are included on the services tier. The services tier must have access to the metadata repository tier and the engine tier.wss?rs=14&uid=swg27016382. Installation. Services tier Application server Product module-specific Common services services Connector access Scheduling services IBM InfoSphere Information Logging Analyzer services IBM InfoSphere Information Directory Services Director services IBM InfoSphere Security FastTrack services IBM InfoSphere Reporting QualityStage services IBM InfoSphere DataStage services Core services IBM InfoSphere Business Glossary services Metadata services IBM InfoSphere Metadata Workbench services Figure 3. IBM InfoSphere Business Glossary. and Configuration Guide . Services for IBM InfoSphere Information Server Some services are common to all product modules. see the system requirements at www.ibm. An instance of IBM WebSphere Application Server hosts these services.

You can create product module-specific reports for InfoSphere DataStage. scheduling. delete. a report run and the analysis job within InfoSphere Information Analyzer are scheduled tasks. InfoSphere Information Server Web-based applications The following InfoSphere Information Server Web-based applications are installed as part of the services tier. and agent services. You can view the logs and resolve problems by using the InfoSphere Information Server console and Web console. and roles within InfoSphere Information Server. view their status. persistence management. Metadata services Implement the integrated metadata management within InfoSphere Information Server. access-control services. and purge report results contents from an associated scheduled report execution. Functions include repository management. InfoSphere QualityStage. you can use external user registries such as the local operating system user registry. Alternatively. and InfoSphere Information Analyzer. and purge them from the system. Logging services Help you manage logs across all the InfoSphere Information Server suite components.The common services include: Scheduling services Help plan and track activities such as logging and reporting and suite component tasks such as data monitoring and trending. Directory services Act as a central authority that can authenticate resources and manage identities and relationships among identities. If the user registry internal to InfoSphere Information Server is used. Each InfoSphere Information Server suite component defines relevant logging categories. and security services. You can access. v IBM InfoSphere Metadata Workbench Chapter 2. You can set up and run all reporting tasks from the InfoSphere Information Server Web console. Core services Low-level services such as service registration. and model management. Security services Manage role-based authorization of users. For example. binding services. life cycle management. and encryption that complies with many privacy and security regulations. history. monitoring. and forecast. Planning Step 2: Understanding tiers and components 11 . You can also create cross-product reports for logging. administrators can use the InfoSphere Information Server console and Web console to add users. Within the consoles. You can use the InfoSphere Information Server console and Web console to maintain the schedules. You can base directories on the InfoSphere Information Server internal user registry. Reporting services Manage run time and administrative aspects of reporting for InfoSphere Information Server. groups. or Lightweight Directory Access Protocol (LDAP) or Microsoft Active Directory registries. you can define schedules. Logs are stored in the metadata repository.

and other metadata for product modules in the InfoSphere Information Server suite. The database is a shared component that stores design-time. The following diagram shows the components that make up the metadata repository tier. The following diagram illustrates the tier relationships. v The IBM InfoSphere Information Server Web console. runtime. Installation. If InfoSphere Information Analyzer is installed. The metadata repository tier includes the metadata repository database for IBM InfoSphere Information Server. When product modules store or retrieve metadata. the engine tier and the client tier must also have direct access to the analysis databases. and Configuration Guide . the metadata repository also includes one or more analysis databases. The services tier must have access to the metadata repository tier. the IBM InfoSphere Information Analyzer database and the computer where these components are installed. Metadata repository tier Metadata repository database Information Analyzer analysis databases Figure 4. 12 Planning. The analysis databases are used by InfoSphere Information Analyzer when it runs analysis jobs. and metadata and other data storage for the product modules that you install. job execution. and the following clients: – IBM InfoSphere Business Glossary – Information Services Catalog for InfoSphere Information Services Director – The metadata repository management tool Metadata repository tier The metadata repository tier consists of the metadata repository database and. if installed. The Web console consists of administration and reporting tools. services on the services tier connect to the metadata repository tier and manage the interaction between the databases and the product modules. glossary. For InfoSphere Information Analyzer. Metadata repository tier components Tier relationships The tiers provide services.

The InfoSphere Information Analyzer client also communicates directly with the analysis databases. Common specific services services Data Metadata repository tier Figure 5. Planning Step 2: Understanding tiers and components 13 . Some InfoSphere Metabrokers and bridges can export data. the engine tier communicates directly with the analysis databases on the metadata repository tier. Chapter 2. The IBM InfoSphere DataStage and QualityStage clients also communicate with the engine tier. v ODBC drivers on the engine tier communicate with external databases. Client tier Console Engine tier Services tier ODBC drivers Engine Product module. Tier relationships The tiers relate to one another in the following ways: v Relationships differ depending on which product modules you install. v Client programs on the client tier communicate primarily with the services tier. v IBM InfoSphere Metabrokers and bridges on the client tier can import data from external sources. v With the IBM InfoSphere Information Analyzer product module. v Metadata services on the services tier communicate with the metadata repository tier. v Various services within the services tier communicate with agents on the engine tier.

and Configuration Guide . Installation.14 Planning.

The engine tier is installed on another computer. The client tier is installed on separate computers. In these topology descriptions. the engine tier. 2005. you must provide a location for the analysis database. and services tier are all installed on a single computer. Locations for the IBM InfoSphere QualityStage Match Designer database If you install InfoSphere QualityStage. the services tier and metadata repository tier are installed on a computer. © Copyright IBM Corp. metadata repository tier. Client/server In this topology. the term computers refers to separate physical servers. choose a basic topology.Chapter 3. and user concurrency. and client tier are all installed on a single computer. performance and throughput. The client tier is installed on separate computers. These topologies are described in the following sections. Multiple instances of InfoSphere Information Server You can install more than one instance of InfoSphere Information Server on a set of computers. logical partitions (LPARs). services. Locations for the IBM InfoSphere Information Analyzer database If you install InfoSphere Information Analyzer. The overall topology of an installation can range widely in complexity. Dedicated engine tier In this topology. Multiple server engines You can create an installation with more than one engine tier. Planning Step 3: Designing an installation topology Design the hardware and software topology for each tier. 2010 15 . and repository tiers. or virtual machines. you must create the Match Designer database manually. Dedicated computer for each tier You can host each tier on a separate computer. The following are some basic topologies for IBM InfoSphere Information Server. Optimize the design of the topology to accommodate the product modules that you install and any requirements for high availability. Single computer In this topology. metadata repository tier. This topology is specific to Microsoft Windows configurations. Basic installation topologies If you do not need a high availability solution and do not anticipate scaling the installation for higher capacity in the future. IBM InfoSphere FastTrack topologies IBM InfoSphere FastTrack places code on the client. services tier. the engine tier.

metadata repository tier. and Configuration Guide . disk space. This topology centralizes administration and isolates it from client users. you can include multiple client tier computers. The following diagram illustrates this topology. the engine tier. The following diagram illustrates this topology. Installation. the computer must run Microsoft Windows and meet all system requirements for this platform. The computer that hosts the other tiers can run any operating system that IBM InfoSphere Information Server supports. and services tier are all installed on a single computer. The client tier computers must run Microsoft Windows. The computer must be a server-class computer that meets all system requirements. 16 Planning. To support the client tier. The client tier is installed on separate computers. metadata repository tier. services tier. Computer A Client tier Engine Services tier tier Metadata repository tier Figure 6. the engine tier. Single computer topology In this topology. Single computer topology Client/server topology In this topology. such as memory. and other requirements. This topology is suitable for demonstration systems and for small-scale development. and client tier are all installed on a single computer. Note: Although the diagram shows only one client tier computer.

higher engine tier activity does not affect the operations of the services tier and metadata repository tier. The client tier is installed on separate computers. Also. Planning Step 3: Designing an installation topology 17 . The client tier computer must run Microsoft Windows. Installing the metadata repository tier with the services tier provides optimal performance because there is no network latency between the tiers. Chapter 3. The following diagram illustrates this topology. the services tier and metadata repository tier are installed on one computer. The engine tier is installed on another computer. This topology is suitable for environments that have high IBM InfoSphere DataStage and QualityStage job requirements and for IBM InfoSphere Information Analyzer installations. Computer A Client tier Network Computer B Engine Services tier tier Metadata repository tier Figure 7. Basic client/server topology Dedicated engine tier topology In this topology. you can include multiple client tier computers. Note: Although the diagram shows only one client tier computer. The other computers can run any operating system that IBM InfoSphere Information Server supports.

Topology with separate server dedicated to engine tier Dedicated computer for each tier topology You can host each tier on a separate computer. Computer A Client tier Network Computer B Computer C Services tier Engine tier Metadata repository tier Figure 8. Note: Although the diagram shows only one client tier computer. The services tier and the metadata repository tier must be on the same subnet. Installation. and Configuration Guide . The following diagram illustrates this topology. you must have a high-bandwidth connection between the services tier and the metadata repository tier. minimize network latency between all tiers. If you choose this topology. 18 Planning. This topology provides each tier with dedicated computational resources. In particular. you can include multiple client tier computers.

Computer A Client tier Network Computer B Computer C Computer D Metadata Services tier Engine tier repository tier Figure 9. you can add additional databases by using the IBM InfoSphere Information Server console. The analysis database is a component that InfoSphere Information Analyzer uses when it runs analysis jobs. or they might share the same analysis database. Planning Step 3: Designing an installation topology 19 . The InfoSphere Information Server engine must have access to one or more analysis databases. At installation time. Each InfoSphere Information Analyzer project is associated with a specific analysis database. Topology with dedicated computer for each tier Locations for the analysis databases If you install IBM InfoSphere Information Analyzer. Chapter 3. two InfoSphere Information Analyzer projects might use two different analysis databases. you specify the location for the first analysis database. you can locate analysis databases and the metadata repository on different computers. After the installation. The analysis database might be used by a single InfoSphere Information Analyzer project. or it might be shared by multiple InfoSphere Information Analyzer projects. For example. You can locate an analysis database and the metadata repository in the same database server installation as distinct databases. you must provide the location for one or more analysis databases. Alternatively.

For example. you can use an IBM DB2® database for the metadata repository and an Oracle database for an analysis database. The following diagram illustrates a three-computer topology where an analysis database and the metadata repository database are located in the same database server installation. 20 Planning. Topology with analysis database and metadata repository database in the same database server installation The following diagram illustrates a four-computer topology where an analysis database and the metadata repository database are located on different computers. Computer A Client tier Network Computer B Computer C Services tier Engine tier Metadata repository tier Information Metadata Analyzer repository analysis database database Figure 10. Installation. and Configuration Guide . The database system for the analysis databases can be different from the database system for the metadata repository.

you must configure the database to receive double-byte data if the Match Designer processes Asian data. you configure it to use a database that you create. Planning Step 3: Designing an installation topology 21 . Topology with analysis database and metadata repository database on different computers Locations for the Match Designer database IBM InfoSphere QualityStage requires that you provide a location for the Match Designer database. use a new or existing database that is dedicated to storing the results of match test passes. Do not use the metadata repository or the analysis database to store these results. Match specifications consist of match passes that identify duplicate entities within one or more files. The InfoSphere QualityStage Match Designer is a component of InfoSphere QualityStage that is used to design and test match specifications. The IBM InfoSphere Information Server installation program does not create the Match Designer results database. For example. You must configure the database to receive the type of data that is processed in the Match Designer. Chapter 3. After you install InfoSphere QualityStage. Computer A Client tier Network Computer B Computer C Computer D Services tier Engine tier Metadata repository tier Metadata Information repository Analyzer database analysis database Figure 11. as long as the database is configured and accessible when you use the Match Designer. You create the database before or after the installation. You can create the database on a computer where the client or engine tier is installed or on any computer that is accessible to both of these tiers. If you intend to develop match specifications.

you can configure a single client tier instance to communicate with multiple InfoSphere Information Server instances. The database system for the Match Designer database can be different from the database system for the other databases. You cannot install more than one InfoSphere Information Server instance on a Microsoft Windows computer. A single client tier installation communicates with both instances. The instances can reside on the same computer in different installation directories or on different computers. Multiple instances of IBM InfoSphere Information Server In a Linux or UNIX installation. services tiers. Version 8. Installation. you can install more than one instance of InfoSphere Information Server on the same set of computers. and metadata repository tiers. The instances are isolated from one another. Alternatively. You can locate the Match Designer database within the same database system instance as the metadata repository or IBM InfoSphere Information Analyzer analysis database. The following diagram shows a topology with two separate InfoSphere Information Server. For example. with separate engine tiers. that are installed on two separate computers. If the instances are the same InfoSphere Information Server version. The instances can be the same software version or different versions. These tiers cannot be shared between instances. 22 Planning. you can locate the databases in separate instances. you can use an IBM DB2 database for the metadata repository and an Oracle database for the Match Designer database. and Configuration Guide .5 instances.

the client tier must contain clients for each version. The instances are different versions. The Multi-Client Manager is used to switch from one client version to the other. The following diagram shows a topology with two separate InfoSphere Information Server instances that are installed on two separate computers. Planning Step 3: Designing an installation topology 23 . Topology with separate instances on separate computers If the instances are different versions. The client tier contains clients for both versions. Chapter 3.5 Network InfoSphere InfoSphere Information Information Server Server instance instance Computer B Computer C Engine Services Engine Services tier tier tier tier Metadata Metadata repository tier repository tier Figure 12. Computer A Client tier Clients for Version 8.

24 Planning. Each services tier communicates with a separate engine tier installed on a separate computer. Version Version n Computer B Computer C 8. Server. The following diagram shows a topology where the services tiers and metadata repository tiers for two different InfoSphere Information Server version instances are installed on the same computer. Computer A Client tier Multi-client manager Clients Clients for for Version Version n 8. specify different ports for each services tier. and Configuration Guide .5 Engine Services Engine Services tier tier tier tier Metadata Metadata repository tier repository tier Figure 13. Installation.5 Network InfoSphere InfoSphere Information Information Server. Topology with separate different version instances on separate computers If the services tiers for more than one instance reside on the same computer.

run the installation program multiple times to create multiple engine tier instances. Topology where services tiers share a common computer To install more than one instance of the InfoSphere Information Server engine on the same computer. The following diagram shows a topology where the engine tiers for two InfoSphere Information Server instances are installed on the same computer. Version n repository tier Computer D InfoSphere Information Metadata Services Engine tier Server.5 Network Computer B Computer C InfoSphere Information Metadata Services Engine tier Server. Each engine tier instance must be registered to a different InfoSphere Information Server service instance. During the installation. Computer A Client tier Multi-client manager Clients Clients for for Version Version n 8. Chapter 3. To perform this install. create an ITAG installation. All projects and jobs associated with a server engine instance are assigned the tag for the server engine instance.5 repository tier Figure 14. Planning Step 3: Designing an installation topology 25 . Version 8. Each engine tier has an associated ITAG. assign each instance a unique identification tag and port number.

and Configuration Guide . each engine tier consists of an IBM InfoSphere Information Server engine and a parallel engine. The following diagram shows a topology with two engine tiers that are installed on separate computers.5 repository tier ITAG "Y" Figure 15. In this topology. You cannot configure the services tier to communicate with multiple engine tiers that are installed on the same computer. each with its own analysis database. Multiple server engines You can create an installation topology that includes more than one engine tier. ITAG installation Note: Windows ITAG installations are not supported on Microsoft Windows computers. Or you might dedicate multiple engine tiers to separate sets of InfoSphere Information Analyzer jobs. Installation. A single services tier instance communicates with both engine tiers. Version 8. Version n repository tier ITAG "X" InfoSphere Information Metadata Services Engine tier Server. you might dedicate one engine tier to IBM InfoSphere DataStage jobs and another engine tier to IBM InfoSphere Information Analyzer jobs. For example.5 Network Computer B Computer C InfoSphere Information Metadata Services Engine tier Server. Computer A Client tier Multi-client manager Clients Clients for for Version Version n 8. Each engine tier instance must reside on a separate computer. You might choose this topology for project and resource management reasons. 26 Planning.

such as IBM Tivoli® System Automation for Multiplatforms Chapter 3. from relatively simple setups to complex installations. you implement topologies and technologies that introduce redundancy. Topology with two engine tiers High availability configurations IBM provides different high availability solutions for each IBM InfoSphere Information Server tier. Each solution allows you to design many different highly available configurations. The following table lists high availability solutions for each tier: Table 3. To increase availability. Planning Step 3: Designing an installation topology 27 . Computer A Client tier Network Computer B Computer C Computer D Engine tier Services tier Engine tier Metadata repository tier Figure 16. IBM provides different high availability solutions for each InfoSphere Information Server tier. Tiers and high availability solutions Tier Solutions Engine Active-passive configuration managed by high availability cluster-management software. Single points of failure are elements whose failure causes critical aspects of the system to stop operating. Increasing availability (implementing a high availability solution) refers to maximizing the percentage of time that the system services are operational. The aim is to reduce or eliminate the number of single points of failure (SPOF).

and devices. The computers are clustered by using high availability (HA) software. and services tier are all installed on the SAN. To deploy a highly available topology. Successfully deploying highly available topologies. 28 Planning. In this topology. the more complex the system that you must design and maintain. Note: Although the diagram shows only one client tier computer. install it on a file system that is shared by two or more computers. and Configuration Guide . especially one that includes clustering. the higher the level of overall availability that you want to achieve. you can include multiple client tier computers. Tiers and high availability solutions (continued) Tier Solutions Services Either of the following solutions: v Active-passive configuration managed by high availability cluster-management software such as Tivoli System Automation for Multiplatforms v IBM WebSphere Application Server clustering Metadata repository Any of the following solutions: v Active-passive configuration managed by high availability cluster-management software such as Tivoli System Automation for Multiplatforms v IBM DB2 clustering v DB2 high-availability data recovery (HADR) v Oracle Real Application Clusters (RAC) In general. The metadata repository tier. engine tier. is a technically complex process that requires a high degree of technical expertise. You might want a different level of availability within your development system than you have within your production system. The HA software maintains a heartbeat: a periodic signal that is sent from the active server to the passive server and that indicates that the active server is operational. One of the computers (the active server) hosts the InfoSphere Information Server instance. The following diagram illustrates this topology. High availability systems generally require more hardware. Installation. For these reasons. give careful consideration to the level of availability that you require within each software tier in the system. Table 3. tiers. but does not run any tier software. two computers share a storage area network (SAN). The other computer (the passive server) is started. Active-passive topology To create a basic level of availability for IBM InfoSphere Information Server. A high availability software product such as IBM Tivoli System Automation for Multiplatforms is installed on both the active server and the passive server. you must have a solid understanding of network technologies such as protocols.

The HA software restarts all InfoSphere Information Server services on the passive server. This process is called a failover. the heartbeat also fails. Planning Step 3: Designing an installation topology 29 . Computer A Client tier Computer B Computer C (Active) (Passive) Engine Services tier tier Database instance HA management HA management software software SAN Engine Services tier tier (installed) (installed) Database Figure 17. The following diagram illustrates this process. Active-passive server cluster configuration If the active server fails. Chapter 3.

Other software monitors the health of individual InfoSphere Information Server processes. any jobs that were running fail and must be restarted after the passive server has taken over. If the active server fails. Active-passive server cluster configuration with a failed computer At installation time. The software initiates a failover only if one of these elements fails. but does not trigger a failover if a process fails. The topology provides a basic level of high 30 Planning. Also. All client programs connect to the system by using this address or host name. a failover is not transparent to client users. Installation. the HA software monitors the health only of the server hardware and operating-system-level processes. and Configuration Guide . all InfoSphere Information Server services are unavailable until the failover is complete and the passive server is operational. Computer A Client tier Computer B Computer C (Inoperative) (Newly active) Engine Services tier tier Heartbeat Signal Database instance (broken) HA management HA management software software SAN Engine Services tier tier (installed) (installed) Database Figure 18. Instead.to medium-sized companies with few concurrent system users. If the active server fails. This design allows a system administrator to correct the problem. the information is automatically reassociated with the passive server. you create a host name alias for the system. This information is associated with the active server. the system administrator is notified. so client programs do not need to connect to a different address. The failover process can take several minutes. instead of simply allowing the problem to be reproduced on the passive server. In this configuration. The active-passive topology is appropriate for small. However.

and allow your IT department to trigger a failover manually when necessary. and designing a front-end configuration that balances loads and optimizes traffic. Concurrency is the number of clients that can use the system simultaneously with a reasonable level of system responsiveness. As long as at least one member of the cluster is operational. For example. there is no interruption in service. throughput. A backup load Chapter 3. other cluster members continue to provide services. Computer C also takes over the services tier and the metadata repository tier. To simplify the configuration further. This configuration is suitable mainly for systems that run scheduled production jobs. This topology also includes a sophisticated front-end configuration that includes dual Web servers and a load balancer. not directly with a specific application server in the cluster. Computer C hosts the engine tier. You can scale a clustered configuration as needed to meet increased concurrency requirements. The metadata repository tier is located on a separate computer. The types of activities involved in a development environment make it more likely that a failover would cause dynamic file corruption or synchronization problems. for example: v Computer B hosts the services tier and the metadata repository tier. create a cluster of IBM WebSphere Application Server Network Deployment (ND) application servers across two or more computers. performance. Deploy an instance of the services tier (common services and product-specific services) in each application server. A third computer hosts the WebSphere Application Server Deployment Manager. These variations are beyond the scope of this documentation. if Computer B fails. only one instance of each tier component is running in the configuration. Components in other tiers communicate with the cluster. When a member of the cluster fails. This topology is not scalable. the engine tier is still set up in an active-passive server cluster configuration. However. Planning Step 3: Designing an installation topology 31 . v Computer B hosts the services tier and the metadata repository tier. In the diagram. The following diagram shows a topology with a services tier where application server clustering is implemented across two computers. HTTP clients such as the WebSphere Application Server Web console access the server-side components through the load balancer. These systems are set up outside the firewall. Some other variations of this topology are possible. Implementing an IBM WebSphere Application Server Network Deployment cluster. Another computer (Computer D) serves as backup server for both Computer B and Computer C. Computer C hosts the engine tier. You can add alternate passive servers if necessary. and concurrency are not affected because at any specific time. you can eliminate the HA software from your implementation. Computer B also hosts the engine tier. availability without incurring significant additional server hardware costs. also improves concurrency. The computers can fail over to one another. If Computer C fails. IBM WebSphere Application Server Network Deployment clustering To provide high availability of the services tier.

EJB clients such as the IBM InfoSphere Information Server console and the IBM InfoSphere DataStage and QualityStage Designer communicate directly with the WebSphere Application Server nodes. Note: High availability configurations that include WebSphere Application Server clustering typically also include metadata repository clustering. The database cluster ensures that the metadata repository is not a single point of failure. the other WebSphere Application Server cluster members continue to operate. Client tier Client workstations HTTP clients EJB clients Backup load Load balancer balancer Web Web server 1 server 2 Firewall Services tier Cluster WebSphere Application WebSphere WebSphere Server Application Application Deployment Server Server Node 1 Manager Node 2 Engine tier Metadata repository tier Active Passive Metadata Computer Computer Repository computer HA mgt sw HA mgt sw DBMS SAN Database Figure 19. and Configuration Guide . balancer ensures that the load balancer computer is not a single point of failure. Installation. Topology with WebSphere Application Server cluster If a server in the cluster fails. The following diagram illustrates this failover process: 32 Planning.

The node agents communicate with a deployment manager (DMgr). Chapter 3. The group of application servers plus their associated node agent is called a managed node. These processes run on one or more computers or logical partitions (LPARs). Deployment managers are administrative agents that provide a centralized management view for the nodes. create an IBM WebSphere Application Server Network Deployment cell across your computers. WebSphere Application Server cluster with failed node Implementing IBM WebSphere Application Server clustering To implement clustering. and define a cluster that contains application servers within the cell. A node agent monitors the application servers and routes administrative requests to them. Planning Step 3: Designing an installation topology 33 . An IBM WebSphere Application Server Network Deployment implementation consists of one or more application server processes. Client tier Client workstations HTTP clients EJB clients Backup load Load balancer balancer Web Web server 1 server 2 Firewall Services tier Cluster WebSphere WebSphere WebSphere Application Application Application Server Server Server Node 1 Deployment Node 2 (failed) Manager Engine tier Metadata repository tier Active Passive Metadata Computer Computer Repository computer HA mgt sw HA mgt sw DBMS SAN Database Figure 20. You can have multiple managed nodes per implementation. IBM WebSphere Application Server Network Deployment allows you to set up a node agent to manage a subgroup of the application server processes in the implementation. The group of processes (application servers and node agents) managed by a deployment manager is called a cell.

all application servers on the computer fail). 6. The application servers within a cluster are called members of that cluster. 34 Planning. or stand-alone application servers. v All computers spanned by a cluster must run the same operating system and fix pack level. Master Data Management (MDM) servers. Installation. if an application server in a managed node fails. Vertical scaling improves performance and throughput. You can also vertically scale the cluster by adding application servers to managed nodes on the same computer.n. The cluster is managed by the Deployment Manager in the cell. you can horizontally scale the cluster by adding more managed nodes on other computers. The diagram also shows a cluster that contains the application servers in each node. The following diagram shows a cell that contains two managed nodes that are managed by a Deployment Manager. Cell Node Application Node Agent Server Deployment Manager Node Application Cluster Node Agent Server Figure 21.n. other application servers in the node continue to function. If an entire computer fails. v You must deploy a front-end HTTP server. Each node agent communicates with the Deployment Manager. see “Building a highly available and scalable front-end configuration to an IBM WebSphere Application Server cluster” on page 36. a load balancer (hardware or software). WebSphere Application Server supports several cluster topologies. A cluster is a logical subgroup of the application servers within the cell that are all running the same set of applications and services. v You must deploy each InfoSphere Information Server cluster in its own dedicated cell. but does not improve availability except at the application server level (that is. with the following restrictions. Adding more nodes also enhances performance and throughput. For more information.n). Each node contains multiple application servers that are managed by a node agent. and Configuration Guide . The cell cannot contain other clusters. v The application servers within the cluster must be the same version: the same major release (for example. Cell that contains two managed nodes that are managed by a Deployment Manager To further enhance the high availability of the services tier. because the nodes in the cluster share the workload. or a mix of HTTP servers and load balancers (IP sprayer topology).0) and the same fix pack version (for example. fix pack n. IBM InfoSphere Information Server supports most WebSphere Application Server cluster topologies for the services tier.1 or 7.

InfoSphere Information Server cell Node (Linux) Application server running InfoSphere Information Server services Cluster (horizontally and vertically scaled) Node (Linux) Application server running InfoSphere Information Server services Stand-alone node Application server running InfoSphere Not allowed Information Server The cell must be dedicated to the cluster services Node Not allowed Older application server version The cell must be dedicated to the cluster. Chapter 3. Local operating system registries do not work in cluster environments. (The InfoSphere Information Server installation program enforces this restriction. Planning Step 3: Designing an installation topology 35 . v An InfoSphere Information Server cluster member and a stand-alone application server cannot share the same metadata repository. The following diagram illustrates vertical and horizontal InfoSphere Information Server cluster topologies. Vertical and horizontal cluster topologies (allowed and not allowed) Additional restrictions to assigning metadata repositories to InfoSphere Information Server clusters include: v Each InfoSphere Information Server cluster must be assigned only one metadata repository. running InfoSphere and all application servers must be the Information Server same application server version services Cluster Node (AIX) Not allowed Application server All nodes in the cell must run the same running InfoSphere operating system Information Server services Cluster Figure 22. v InfoSphere Information Server cluster members that are not part of the same cluster cannot share the same metadata repository. and shows some topology elements that are not allowed in an InfoSphere Information Server cell.) v You must use a distributed user registry such as the InfoSphere Information Server custom registry or an LDAP registry. v Members of a given InfoSphere Information Server cluster cannot be associated with multiple metadata repositories.

and relationships that are allowed and not allowed between the cluster members and metadata repositories. The following diagram shows an InfoSphere Information Server cluster. running on one of the computers. so the Deployment Manager must be running for you to use this console. Application server node agents and Deployment Manager in a sample configuration Building a highly available and scalable front-end configuration to an IBM WebSphere Application Server cluster If you deploy a WebSphere Application Server cluster within your IBM InfoSphere Information Server implementation. InfoSphere Information Server cell Node Application server running InfoSphere Deployment Information Server Node Agent Manager services Metadata repository Node Application server Node Agent running InfoSphere Information Server services Cluster Figure 24. If the node agents are running. 36 Planning. and Configuration Guide . a cluster can continue to perform most runtime functions if the Deployment Manager is not active. Installation. There is only one Deployment Manager per cell. Allowed and not allowed relationships between cluster members and metadata repositories The following diagram shows the location of application server node agents and the Deployment Manager in a sample configuration. so the Deployment Manager is not a single point of failure for these operations. InfoSphere Information Server cell Node Application server running InfoSphere Information Server services Metadata repository Node Application server running InfoSphere Metadata Information Server services repository Cluster Figure 23. the Deployment Manager must be running. for administration operations such as IBM InfoSphere Information Services Director application deployment. Also. However. you must provide a front-end configuration for the cluster. the WebSphere Application Server console is hosted in the Deployment Manager.

InfoSphere Information Server supports IBM HTTP Server and Apache HTTP Server. Cluster with front-end Web server If you choose IBM HTTP Server. The Web server can be defined either as a managed node or an unmanaged node. deploy a backup dedicated Web server to take over in case the active one fails.com/support/docview. you can set up the Deployment Manager to manage configuration and administration of the Web server. To prevent single points of failure at the Web server level.ibm. Chapter 3. deploy firewalls at various key points within the topology that you select. you can also deploy caching proxy servers upstream of the Web servers and load balancers. The front-end configuration can consist of any of the following components located upstream of the cluster: v A front-end Web server v A load balancer v A load balancer upstream of the Web servers (IP sprayer topology) To maximize security. To improve delivery response. It performs the dispatches according to policies that are preconfigured in the WLM plug-in. A backup Web server is also deployed. go to the system requirements at www. A front-end Web server manages servlet and JSP requests.wss?rs=14&uid=swg27016382. The Web server typically uses an internal workload management (WLM) plug-in to dispatch Web requests to the appropriate cluster members and their Web containers. you can provide a front-end Web server upstream of the cluster. InfoSphere Information Server cell Node Cluster Application server Web running InfoSphere container Information Server Web server services WLM plug-in Node Application server Web running InfoSphere container Information Server services Backup Web server Figure 25. Planning Step 3: Designing an installation topology 37 . The front-end Web server increases performance and security because the Web server provides a unique HTTP entry point to the cluster. These software products are not shipped with InfoSphere Information Server. For information on supported versions. Front-end Web servers: If you deploy an IBM WebSphere Application Server cluster within your IBM InfoSphere Information Server implementation. The following diagram shows an InfoSphere Information Server cluster with a front-end Web server.

38 Planning. and Configuration Guide . or to install the IBM HTTP Server plug-in configuration file that contains the workload management policies that are defined for the cluster). A firewall separates the server from the cell. The Deployment Manager manages the IBM HTTP Server instance by using the IBM HTTP Server Admin Process. define the Web servers as managed nodes. In this case. IBM HTTP Server instance that is defined as a managed node The following diagram shows an IBM HTTP Server instance that is defined as an unmanaged node on a stand-alone server. you must define the instances as unmanaged nodes. v If you want to use the Deployment Manager to manage Web servers in the same manner as any other managed nodes in the cell (for example. Stand-alone InfoSphere Information Server cell Cluster server Node Application server IBM HTTP Server Deployment Web running InfoSphere Node agent Admin Process manager container Information Server services Firewall Application server IBM HTTP Web running InfoSphere Node agent Server container Information Server services plug-in Node Figure 27. You cannot manage them by using the Deployment Manager. InfoSphere Information Server cell Node Deployment manager Application server Web running InfoSphere Node agent container Information Server Cluster Node services Node agent Node Application server IBM HTTP Web running InfoSphere Server Node agent container Information Server services plug-in Figure 26. Installation. For example. you can manage the Web servers with the Deployment Manager by enabling the IBM HTTP Server Admin Process on the computer. The Deployment Manager manages IBM HTTP Server through the local node agent. to start or stop IBM HTTP Server. define the Web servers as unmanaged nodes. IBM HTTP Server instance that is defined as an unmanaged node on a stand-alone server If you use the Apache HTTP Server. The following diagram shows an IBM HTTP Server instance that is defined as a managed node. v If you deploy the Web servers upstream of a firewall that protects the cluster members.

when a node is added or removed). InfoSphere Information Server supports many load balancer solutions manufactured by IBM and by other vendors. Planning Step 3: Designing an installation topology 39 . including advanced load-based balancing strategies that monitor usage levels on individual computers Disadvantages of deploying a load balancer v Additional configuration required: you must perform additional configuration to maintain persistent connections between clients and servers (Web server plug-ins handle persistent connection maintenance automatically) and re-configure the load balancer whenever the downstream cluster topology changes (for example. you must copy the Web server plug-in configuration file to each Web server manually. you can provide a load balancer upstream of the cluster. Apache HTTP Server Load balancing: If you deploy an IBM WebSphere Application Server cluster within your IBM InfoSphere Information Server implementation. Table 4. Advantages and disadvantages of a load balancer approach Advantages of deploying a load balancer v Easier deployment: you do not have to set up a network of Web servers and then configure the Web server plug-ins v More load balancing algorithm alternatives: load balancers often offer more algorithms than the ones provided by Web server plug-ins. Stand-alone InfoSphere Information Server cell Cluster server Node Application server Deployment Web running InfoSphere Node agent manager container Information Server services Application server Apache Web running InfoSphere Node agent Web Server container Information Server services plug-in Node Figure 28. v Load balancers do not serve static HTML v Hardware-based load balancers typically cost more Chapter 3. The following table lists the advantages and disadvantages of a load balancer approach.

IBM InfoSphere Information Server supports many IP sprayer solutions manufactured by IBM and by other vendors. This arrangement also spreads the load of Web requests across multiple Web servers. There are several methods to achieve session affinity. Session affinity is typically implemented in this manner with HTTP servers. Choose this topology to eliminate a single point of failure at the Web server level. A load 40 Planning. Network Access Translation/Network Address Port Translation (NAT/NAPT) forwarding. deploy a backup load balancer to take over in case the active one fails. The diagram shows an InfoSphere Information Server cluster with two front-end Web servers. and Configuration Guide . Mechanisms include media access control (MAC) address forwarding. Layer 3 and higher load balancers (load balancers that operate at the IP layer and above) typically achieve session affinity by using passive cookies or a content-based technique. To prevent single points of failure at the load balancer level. InfoSphere Information Server cell Node Cluster Application server Web running InfoSphere container Information Server services Load balancer Node Application server Web running InfoSphere container Information Server services Backup Web server Figure 29. To prevent single points of failure at the load balancer level. and content-based forwarding. Layer 2 load balancers (load balancers that operate at the MAC layer) generally achieve session affinity by using a "stickiness to source IP address" approach. The following diagram shows an InfoSphere Information Server cluster with a front-end load balancer. deploy a load balancer upstream of a group of Web servers. A backup load balancer is also deployed. consider deploying a backup load balancer to take over in case the active one fails. The load balancer performs intelligent balancing among the Web servers based on server availability and workload capacity. The following diagram shows an IP sprayer topology. The method you choose depends on the product that you use and the forwarding mechanism that you configure. See the load balancer documentation for more information IP sprayer topology: To obtain high availability and the maximum balancing of server and workload capacity. Make sure to configure session affinity in the load balancer. Installation. Cluster with a front-end load balancer You cannot manage the load balancers by using the Deployment Manager.

InfoSphere Information Server cell Cluster Node Application server running InfoSphere Information Server services Server Server Server Caching Load Web proxy balancer server Node Application server running InfoSphere Information Server Server Server Server services Backup Backup Web caching proxy load balancer server Figure 31. Planning Step 3: Designing an installation topology 41 . IBM InfoSphere Information Server supports any caching proxy that can cache static and dynamic Web requests. The following diagram shows a caching proxy server upstream of an IP sprayer configuration. You cannot manage the caching proxies by using the Deployment Manager. If caching proxy functionality is not embedded within your load balancer hardware. you can also deploy caching proxies. Caching proxy configuration Firewalls: Chapter 3. balancer is deployed upstream of the Web servers. InfoSphere Information Server cell Cluster Node Application server running InfoSphere Information Server services Server Server Load Web balancer server Node Application server running InfoSphere Information Server Server Server services Backup Web load balancer server Figure 30. The Web servers and load balancers are installed on separate servers. IP sprayer topology Caching proxies: To improve delivery response and reduce downstream traffic. A backup caching proxy server is also deployed. you can deploy caching proxy servers upstream of the Web servers and load balancers. A backup load balancer is also deployed.

you can use DB2 automatic client reroute to enable IBM InfoSphere Information Server processes to reconnect to a standby node when a failover occurs. A firewall is located between the DMZ and the outside world. you can place a firewall between the DMZ and the cluster. make sure to open any ports through the firewalls that are used by InfoSphere Information Server. To secure access to your IBM InfoSphere Information Server cluster. deploy firewalls at various key points in the topology that you select. and Configuration Guide . For example. or between nodes and the Deployment Manager in a cell. add a firewall in front of the caching proxies. Isolate them within a demilitarized zone (DMZ) to deny direct access to internal components from clients that you do not trust. Cluster with firewalls If you deploy firewalls. The following diagram shows an InfoSphere Information Server cluster behind a DMZ. For example. a firewall is also located between the cluster and the metadata repository database. the application server does not support firewalls between nodes in a cell. Alternatively. A firewall is also located between the cluster and the DMZ. IBM DB2 high availability options IBM offers several high availability DB2 configurations. You can also add a firewall between the services tier and the metadata repository database. For maximum security. 42 Planning. The configurations discussed in this documentation are: v DB2 clustering by using high availability clustering software v DB2 with high availability disaster recovery (HADR) In either configuration. load balancers. Note: IBM WebSphere Application Server does not support deployment of firewalls between components within a cell. and Web servers. Installation. InfoSphere Information Server cell Node DMZ Application server running InfoSphere Information Server services Server Server Firewall Load Web Metadata balancer server repository Firewall Firewall Node Application server running InfoSphere Information Server Server Server services Backup Web load balancer server Figure 32.

The following diagram shows a topology that includes a clustered metadata repository tier. If the DB2 instance encounters a problem or fails. repeats certain transactions and undoes other transactions. implement high availability disaster recovery (HADR). set up your cluster in an active-passive configuration with a single active DB2 instance on one computer and one or more passive instances on the other computers. the software initiates failover to another node. With this configuration. the DB2 failover is automatic. configure DB2 automatic client reroute. In this case. it provides high availability for database client processes and smoothes the reconnection to the new node. Planning Step 3: Designing an installation topology 43 . To provide redundancy for the database itself. Chapter 3. a passive instance can take over. In this configuration. you can choose between several high availability clustering management software products. If the heartbeat fails on the active node. To minimize interruption and manual intervention.IBM DB2 clustering To provide a high availability DB2 configuration. This software maintains a "heartbeat" signal between the nodes in the cluster. the metadata repository database is shared between nodes in the cluster. If a failover occurs. This configuration does not provide redundancy for the database itself. but might take several minutes as the new instance acquires resources. Instead. you can create a DB2 cluster across computers. This function causes other IBM InfoSphere Information Server components such as IBM WebSphere Application Server to automatically reconnect to the new DB2 instance. another node in the cluster provides DB2 functionality. HA cluster management software on the metadata repository computers monitors DB2 processes specific to DB2. To manage this configuration. The software also monitors the health of the computer hardware and the network. To provide high availability.

Installation. and Configuration Guide . the passive database instance becomes the active instance. Topology with a clustered metadata repository tier If the active database instance fails. 44 Planning. Client tier Client workstations HTTP clients EJB clients Backup load Load balancer balancer Web Web server 1 server 2 Firewall Services tier Cluster WebSphere Application WebSphere WebSphere Server Application Application Deployment Server Server Node 1 Manager Node 2 Engine tier Metadata repository tier Active Passive Metadata Metadata computer computer Repository Repository computer computer HA mgt sw HA mgt sw (standby) (active) HA mgt sw HA mgt sw SAN DB2 DBMS DB2 DBMS DB2 DB Figure 33. This process is shown in the following diagram.

DB2 processes normally access only the primary copy of the database. The primary DB2 database processes transactions. It uses internal HADR processes to replicate transaction logs to the standby node. You can set up automatic client reroute to make the failover behavior virtually transparent. an administrator triggers the standby copy to take over the transactional workload. Client tier Client workstations HTTP clients EJB clients Backup load Load balancer balancer Web Web server 1 server 2 Firewall Services tier Cluster WebSphere Application WebSphere WebSphere Server Application Application Deployment Server Server Node 1 Manager Node 2 Engine tier Metadata repository tier Active Passive Metadata Metadata computer computer Repository Repository computer computer HA mgt sw HA mgt sw (standby) (failed) HA mgt sw SAN DB2 DBMS DB2 DB Figure 34. you can create a DB2 high availability disaster recovery (HADR) configuration. automatic client reroute retries the connection to the failed primary copy. a complete. The two copies are maintained in synchronization or near-synchronization with each other. where the logs are stored. separate copy of the database is maintained on a standby node at a local or remote location. If the reconnection fails. Planning Step 3: Designing an installation topology 45 . Clustered metadata repository tier with failed server IBM DB2 high availability disaster recovery (HADR) To provide high availability at the DB2 database level. Pending transactions are rolled Chapter 3. automatic client reroute determines whether or not the standby copy is available. If the primary copy becomes unavailable. If the server is available. automatic client reroute reroutes the application server connection to the standby copy. However. if the primary copy fails. A process at the standby node then replays the logged transactions directly to the standby database. In this configuration.

The following diagram shows an IBM InfoSphere Information Server implementation in which the metadata repository tier is set up in an HADR configuration. 46 Planning. All transactions are directed to the standby copy. Failover is quick (normally 10 seconds to 15 seconds if the servers are on the same LAN segment). If the unavailable database becomes available again. it is automatically reintegrated as the new standby database and is resynchronized. and Configuration Guide . Automatic client reroute can also be configured to reconnect to an alternate standby copy if the first standby copy is unavailable. Client tier Client workstations HTTP clients EJB clients Backup load Load balancer balancer Web Web server 1 server 2 Firewall Services tier Cluster WebSphere Application WebSphere WebSphere Server Application Application Deployment Server Server Node 1 Manager Node 2 Engine tier Metadata repository tier Active Passive Metadata Metadata computer computer Repository Repository computer computer HA mgt sw HA mgt sw (HADR standby) (HADR primary) DB2 DBMS DB2 DBMS SAN Secondary Primary database database Transaction log records are copied to the standby server and replayed on standby database Figure 35. HADR configuration The following diagram shows an HADR configuration after the primary database copy has failed. Installation. back and then reissued on the standby copy.

An Oracle RAC configuration consists of multiple computers. Oracle database cluster management software (Oracle Clusterware) monitors and manages the Oracle RAC configuration and tries to restart failed Oracle instances. HADR configuration after server failure Oracle database high availability options If you use an Oracle database system to host the metadata repository database or the IBM InfoSphere Information Analyzer analysis database. Client tier Client workstations HTTP clients EJB clients Backup load Load balancer balancer Web Web server 1 server 2 Firewall Services tier Cluster WebSphere Application WebSphere WebSphere Server Application Automatic client Application Deployment Server reroute (ACR) Server Node 1 reestablishes Manager Node 2 client connection to the standby database Engine tier Metadata repository tier Active Passive Metadata Metadata computer computer Repository Repository computer computer HA mgt sw HA mgt sw (HADR standby) (failed) DB2 DBMS SAN Secondary Primary database database Figure 36. the virtual IP address fails over to another node. increase the availability of the metadata repository tier by implementing Oracle Real Application Clusters (RAC). a virtual IP address is assigned to each server in the cluster. If a computer or Oracle instance process fails. With Oracle RAC 11g. Chapter 3. Client processes access the Oracle RAC configuration in the same way that they access a single Oracle database instance. other Oracle instances continue to provide service. which is made up of processes that enable access to stored data. Each Oracle instance has access to a common database file system across a high-speed network. Then client processes can automatically reconnect. each of which runs an Oracle instance. Planning Step 3: Designing an installation topology 47 . If a node in the cluster fails.

install to a single node in the configuration. nodes in the cluster are located in physically separated sites. Installation. Nodes in an Oracle RAC cluster require a separate. This network is called the interconnect. other nodes continue to provide service. private high-speed network for messaging between nodes. Then perform additional steps to cause InfoSphere Information Server to operate with the complete Oracle RAC configuration. Other considerations when designing for high availability You must also introduce redundancy at a number of different levels to reduce or eliminate single points of failure. and Configuration Guide . Topology with Oracle RAC configuration If a node in the RAC cluster fails. The following figure shows an IBM InfoSphere Information Server topology that includes Oracle RAC. Client tier Client workstations HTTP clients EJB clients Backup load Load balancer balancer Web Web server 1 server 2 Firewall Services tier Cluster WebSphere Application WebSphere WebSphere Server Application Application Deployment Server Server Node 1 Manager Node 2 Engine tier Metadata repository tier Active Passive Metadata Metadata computer computer Repository Repository computer computer HA mgt sw HA mgt sw Oracle Real Application Clusters (RAC) cluster SAN Database farm Figure 37. For greater high availability. 48 Planning. To install InfoSphere Information Server in an Oracle RAC configuration. you can implement an Oracle RAC on Extended Distance Clusters configuration. The two Oracle RAC node computers share access to a database farm. In this configuration.

throughput. You must also introduce redundancy at a number of different levels to reduce or eliminate single points of failure. Chapter 3. Performance and throughput requirements Refer to “Capacity planning” on page 57 to analyze your performance. testing system. The server and software topology that you choose is only part of a high availability solution. For example. Choose the implementation that fits your needs. or production system. how important is it that the development system or testing system is highly available? v Consider the level of high availability that you require for different software tiers. evaluate the level of high availability that you require: v Consider the amount of downtime that you can tolerate. The tiers are also used differently depending upon the product modules that you have installed. and storage needs. Note: A failure on one tier typically renders the entire system nonoperational until the problem is fixed or failover occurs. restore and disaster recovery contingencies v Availability of support staff to respond to problems Designing a high availability topology There are many ways to implement high availability and scalability within an IBM InfoSphere Information Server installation. consider the following factors: v The level of high availability that you require for each system you implement v The degree to which the system is likely to scale in the future v Your security needs v Complexity factors v Maintainability factors v Cost High-availability level When considering your topology. or is a system administrator available to intervene? v Consider how your needs might differ depending upon how the system is used: whether it is a development system. Must the system take care of failover and recovery automatically. Planning Step 3: Designing an installation topology 49 . Here are some areas to consider: v Your storage solution v Your network v Security within your network and within your sites v Your electrical infrastructure v Your backup. The tiers are used differently depending upon whether the system is used primarily for development or in production. Can you afford to have a nonoperational system for 15 minutes? For 5 minutes? v Consider the amount of automation that you need. When determining which topology and implementation to choose.

com/infocenter/wasinfo/v6r1/topic/ com. For more information about security. and between the system and external data sources and targets. Security requirements Different topologies lend themselves to different security possibilities.ibm. Begin with a relatively simple system that is well within your ability to support. consider the amount of complexity that your IT staff must support.com/infocenter/wasinfo/v7r0/topic/ com.websphere. Consider how you want to implement firewalls and other security precautions between the different tiers.doc/info/ae/ae/welc6topsecuring. When you architect your system. As your IT group becomes familiar with support of the system. For example. High availability features can simplify system maintenance. refer to the IBM WebSphere Application Server documentation: v IBM WebSphere Application Server ND 6.ibm.boulder. in an organization where a group of database 50 Planning. Determine what aspects of maintenance to automate.html v IBM WebSphere Application Server ND 7. between the computers in each tier.boulder. Is there sufficient in-house expertise to support the system that you design? If your high availability features fail.multiplatform.websphere. you can take servers offline for certain updates without rendering the entire system nonoperational. These considerations are important for the services tier and the engine tier that must have fast communications paths with external systems.ibm.0 security: http:// publib. Eliminating single points of failure requires implementation of complex redundant hardware and software components.nd. see the scenario comparisons. For examples of how the solutions differ.1 security: http:// publib. Installation. consider how the system might need to scale to support greater performance and throughput requirements in the future. implement the high availability features on a staggered schedule until your entire system is in place. For example.multiplatform. consider isolating the tiers on separate computers so each department can "own" a tier. the amount of time you need to bring the system online again might negate any uptime gains that your features provide.nd. This approach also gives the group experience with changing the system and provides them with knowledge for future system scaling.doc/info/ae/ae/welc6topsecuring. When you are choosing a topology and architecture. and which aspects to leave in the hands of support personnel. in a clustered system. and Configuration Guide . The amount of scalability that each high availability solution offers differs from solution to solution.ibm. Maintainability factors Consider the maintenance costs of the system that you design. In an organization where specific departments are responsible for different systems.html Complexity factors High availability and scalability add layers of complexity to the installation.

High availability (HA) software such as IBM Tivoli System Automation for Multiplatforms is installed on both the active server and the passive server. Scenario analysis: Two-server. active-passive topology Consideration Advantages and disadvantages Level of high availability v A host failure causes all tiers to be restarted. Maintainability Failover allows you to take one server offline for maintenance. Complexity v Complexity is fairly low. consider isolating the metadata repository tier on computers that are within their control. In this topology. Extra hardware. The other computer (the passive server) is started. The HA software maintains a heartbeat that indicates that the active server is operational. Cost This topology requires minimal hardware and software. v To increase engine performance. while the rest of the system remains operational. add parallel engine compute nodes. Scenario: Two-server. v If any component fails. software.administrators is responsible for corporate databases. Planning Step 3: Designing an installation topology 51 . One computer (the active server) hosts the tiers. v HA software might be difficult to implement. Chapter 3. Scalability v The topology is difficult to scale: adding nodes does not increase performance or throughput. Cost Implementing high availability typically adds to the initial cost of the system. the productivity gains that the highly available system provides might make up for these costs. training. Security v Complexity is fairly low. v Software failure might not cause a failover. All server-side tiers are installed on the SAN. there might be up to a 10-minute outage. but is not running any tier software. active-passive topology. active-passive topology This scenario describes a two-server. two computers share a storage area network (SAN). However. there is the potential for job design loss (client disconnected). Table 5. v A security breech on the server might jeopardize the entire system. v When a node fails. This topology is described in “Active-passive topology” on page 28. v No IBM WebSphere Application Server or database clustering experience is required. and other costs make the initial outlay larger.

while failover occurs and the other node takes over. Other computers host the metadata repository tier. add additional parallel engines. A topology that is similar to this one is described in “IBM DB2 clustering” on page 43. Security v The topology requires a complex security setup that includes multiple firewalls and other security considerations. v You can add nodes to the WebSphere Application Server cluster to improve the performance and throughput of the application server. v If the security of one node or tier is compromised. Scalability v The topology is highly scalable. Other computers host the services tier. Scenario analysis: Fully clustered topology Consideration Notes Level of high availability v The failure of a node in the WebSphere Application Server cluster does not cause service interruption. and Configuration Guide . a slight degradation of performance might occur. Two of the computers host the engine tier in an active-passive server cluster. v To increase engine performance. the entire system is not necessarily compromised. v For metadata repository configurations within an Oracle Real Application Clusters (RAC) cluster. add nodes to improve the performance and throughput of the metadata repository. However. However. Installation. activities that do not require the engine tier continue without interruption. where the database system is set up in a cluster. v The failure of a node in the engine tier causes up to a 10-minute interruption in engine operation. Table 6. Scenario: Fully clustered topology This scenario describes a topology in which all tiers are implemented within clusters. where the WebSphere Application Server is set up in a cluster. both IBM WebSphere Application Server clustering and metadata repository tier clustering are implemented: This topology includes several computers. 52 Planning. v The topology supports many concurrent users. In this topology. v The failure of a node in the metadata repository tier cluster causes minimal or no service interruption.

the workload for each job is distributed across several processors on one or more computers. Table 6. the user modifies a configuration file to define multiple processing nodes. Normally. Within InfoSphere DataStage. In these topologies. Parallel processing environments are categorized as symmetric multiprocessing (SMP) or cluster or massively parallel processing (MPP) systems. you design and run jobs to process data. and loads it into one or more new locations. called compute nodes. Parallel processing and grid topologies To maximize the IBM InfoSphere Information Server engine efficiency and throughput. Planning Step 3: Designing an installation topology 53 . which might be difficult to implement. A conductor node computer orchestrates the work. create a parallel processing or grid topology. and the rest of the system remains operational. the workload for each job is distributed across several processors. v The isolation of each tier on one or more separate computers allows groups of users within the organization to "own" particular tiers. v The topology is highly flexible: you can take a server offline for maintenance. v The topology might require the implementation of high-availability cluster-management software. Scenario analysis: Fully clustered topology (continued) Consideration Notes Complexity v The topology is highly complex. a job extracts data from one or more sources. The InfoSphere Information Server parallel engine uses the processors and computers concurrently to complete each job. These nodes work concurrently to complete each job quickly and efficiently. The parallel engine and the InfoSphere Information Server engine make up the engine tier. Maintainability v The maintenance of this topology is complex. The processors can be located on the same computer or on different computers that are connected over a network. In IBM InfoSphere DataStage. Install a supported resource manager to enable the dynamic assignment of available computer nodes (physical computers) at runtime. the workload for each job is distributed across several processors. In a parallel processing configuration. Parallel processing configurations In a parallel processing configuration. Cost The cost is high. v You must have knowledge of WebSphere Application Server clustering and either IBM DB2 clusters or Oracle RAC clusters. Chapter 3. transforms the data. You can configure the InfoSphere Information Server parallel framework for grid computing processing.

The actual speed at which the job completes might be limited by the shared resources in the system. Symmetric multiprocessing (SMP) systems In a symmetric multiprocessing (SMP) environment. To scale the system. Cluster or massively parallel processing (MPP) systems In a massively parallel processing (MPP) system. Installation. or increase storage. such as memory or storage. Disk CPU CPU CPU CPU Shared Memory Figure 38. Massively parallel processing (MPP) system 54 Planning. multiple processors share other hardware resources. The scalability strategy that you implement depends on how your job is limited within your current system. They have a single operating system. add memory. many computers are physically housed in the same chassis. and Configuration Guide . as shown in the following diagram: Figure 39. Symmetric multiprocessing (SMP) system The workload for a parallel job is distributed across the processors in the system. you can increase the number of processors.

For each job. Cluster system In a cluster or MPP environment. you can add computers and associated memory and disk resources. This architecture makes the association of nodes used by a job static. Grid topologies vary widely. The system minimizes the idle time for each processor and helps ensure that resources are used in the most efficient manner. Chapter 3. a resource manager dynamically allocates resources for job processing. you modify the configuration file to include the new number of nodes and associated servers. A cluster system is physically dispersed. performance is improved because no resources must be shared among physical computers. the resource manager waits until resources are available and then generates a configuration file that assigns resources to the job. In an IBM InfoSphere Information Server parallel processing configuration. in any grid topology. However. a file system is commonly shared across the network. a resource manager manages the pool of available resources and dynamically allocates them as jobs are submitted for processing. With a grid implementation. This configuration allows program files to be shared instead of installed on individual nodes in the system. Grid configurations In a grid configuration. They depend in part on the storage implementation such as Network Attached Storage (NAS) or storage area networks (SAN). Note: In an MPP system. as shown in the following diagram: Network Processing node Figure 40. Planning Step 3: Designing an installation topology 55 . one server is designated as the conductor node. or the servers on which a job runs. To change the degree of parallelism. you modify a configuration file to assign resources to a job. To scale the system.

the InfoSphere Information Server metadata repository and services tier are installed on the first blade (node 1). The standard InfoSphere Information Server suite supports grid implementations on Red Hat Enterprise Linux only. add additional nodes and register them with the resource manager. The following diagram shows a typical grid configuration. The client tier is installed on a workstation that is connected to the blade system (this computer is not shown). with minimum additional costs. and one parallel engine are installed on the second blade (node 2). External disk storage is a Network Attached Storage (NAS) system. The storage is accessible from all blades through the NFS server installed in the first node (node 0). The server engine. and other servers are designated as compute nodes. Each computer in the grid must use the same operating system and release level. All jobs are initiated from the conductor node. with IBM LoadLeveler®. and processed on the compute nodes. and Configuration Guide . You can take nodes out of service without halting processing of jobs within the grid. Installation. resource manager. 56 Planning. The computers must be connected and accessible within the same high-speed local area network. All other blades (nodes 3 through 14) are compute nodes that provide processing power for the grid. You can set up this implementation by using the instructions in this documentation. In the diagram. A grid can be implemented on relatively low-cost hardware. To scale the grid. The diagram shows an IBM BladeCenter® chassis with 14 blades.

continue monitoring the file systems to ensure that sufficient space is available. Planning Step 3: Designing an installation topology 57 . and file system resources to create an optimal operating environment for IBM InfoSphere Information Server. RAID and SAN configurations Performance of a job (for IBM InfoSphere DataStage. As part of capacity planning for your installation. maximum performance is a combination of maximum bandwidth (controllers and disk) and minimized contention. InfoSphere Information Server stops functioning correctly. and IBM InfoSphere Information Analyzer) depends on all components being optimized. For RAID (Redundant Array of Independent Disks) and SAN (system area network) configurations. IBM InfoSphere QualityStage. size your file systems and databases to accommodate your anticipated needs. After the installation. Chapter 3. Grid configuration Capacity planning You plan the use of disk. volume group. Attention: If the file system runs out of space. NAS NAS Engine Services NFS RM Repository server Node2 Node1 Node0 Node3 Node4 Node5 Node6 Node7 Node8 Node9 Node10 Node11 Node12 Node13 Node14 Figure 41.

The following guidelines can assist in the configuration of RAID or SAN
technologies:
v Ensure that your database is optimally tuned.
v Ensure that computers where you install the metadata repository tier and the
services tier are on a high-speed network.
v Minimize contention between temporary systems (scratch, buffer, and sort) and
data file systems. For temporary storage, do not use a network file system
(NFS). Consider using the local disk for temporary storage.
v Minimize contention between the disks and controllers that are associated with
InfoSphere Information Server file systems and other applications or servers.
v Consider isolating multiple mount points to separate high-speed disk
interconnects and controllers.
v Consider the trade-off between the granularity of file systems and the
underlying configuration in comparison to the available, unused storage.
v Do not create overly complex device configurations. These configurations can be
difficult to administer and might not offer noticeable performance improvement.
v If possible, check your configuration with experts in hardware, storage,
operating systems, and InfoSphere Information Server.
v Systems with parallelism require different expertise than systems with engines
that do not feature parallelism.

The optimal disk configuration balances cost, complexity, ease of administration,
and ultimate performance.

58 Planning, Installation, and Configuration Guide

Chapter 4. Planning Step 4: Determining your installation
strategy
Determine the specific set of steps to take to install IBM InfoSphere Information
Server within your topology.

To install InfoSphere Information Server, you perform the following tasks:
1. Plan and build your topology.
v Decide:
– What the topology of your network will be
– What hardware to use for each portion of the product
– Whether to implement high availability at various levels
v Determine whether you need to preinstall any components before you install
InfoSphere Information Server. Alternatively, you might choose to use
components that you already have installed and running. For example, you
might use a database system or application server that is supported by
InfoSphere Information Server. Components that might need preinstallation
are:
– The database systems for the InfoSphere Information Server databases.
– The metadata repository database.
– IBM InfoSphere Information Analyzer analysis databases, if you plan to
install this product module.
– IBM WebSphere Application Server.
– High availability software, if required by your configuration.
You do not have to preinstall these components for a basic topology that
satisfies these requirements:
– The topology does not involve high availability.
– You plan to use IBM DB2 for the InfoSphere Information Server databases.
The installation program can install and configure DB2 on a local
computer when it installs other InfoSphere Information Server
components.
v Build the topology and test it.
2. Install InfoSphere Information Server. InfoSphere Information Server
components are logically organized into groups, or tiers. You install InfoSphere
Information Server components on a tier by tier basis.
For an implementation on multiple computers, install the tiers in the following
order:
v Metadata repository tier
v Services tier
v Engine tier
You can install the client tier at any time.
Not all products require an engine tier. IBM InfoSphere FastTrack, IBM
InfoSphere Business Glossary, and IBM InfoSphere Business Glossary Anywhere
do not require an engine tier.
Complete the following phases for each tier.

© Copyright IBM Corp. 2005, 2010 59

v Preparation: prepare your computers for the installation, and preinstall any
components that require it.
v InfoSphere Information Server installation: run the installation program to
install InfoSphere Information Server components on the tier computers.
You do not run the installation program for the metadata repository tier
computers if you have preinstalled the database system and configured the
databases within the database system.
v Tier-specific postinstallation tasks: some installations require you to do
additional tasks that are specific to one or more tiers after installing
InfoSphere Information Server.
3. After your product modules are installed, complete additional configuration
tasks. Some of the tasks are common to all installations. Other tasks are specific
to installations of certain product modules only.

You can install more than one software tier on the same computer. In this case, you
run the installation program only once for that computer, installing the software
for the tiers at the same time.

The following flowchart illustrates the installation process in a topology where all
tiers except the client tier are installed on the same computer (computer Host1).
The client tier is installed on computer Host2.

Start

Planning Plan, build, and test your topology

Prepare computer Host1 for the metadata repository tier, services tier,
and engine tier. Preinstall any components if necessary

Run installation program on computer Host1

Tier-by-tier
installation Do tier-specific postinstallation tasks for computer Host1 (if any)

Prepare computer Host2 for the client tier

Run installation program on computer Host2

Postinstallation
configuration Complete postinstallation configuration tasks

End

Figure 42. Installation process flowchart: two-computer topology

60 Planning, Installation, and Configuration Guide

The following flowchart illustrates the installation process in a more complex
topology. In this topology, the metadata repository tier and services tier
components are installed on the same computer (computer Host1). The engine tier
and client tier are each installed on separate computers (computers Host2 and
Host3). In this case, you run the installation program three times. First, you install
metadata repository and services tier components on computer Host1. Then you
install engine tier components on computer Host2. Then you install the client tier
components on computer Host3.

Start

Planning Plan, build, and test your topology

Prepare computer Host1 for the metadata repository tier, services tier,
and engine tier. Preinstall any components if necessary

Run installation program on computer Host1

Do tier-specific postinstallation tasks for computer Host1 (if any)

Tier-by-tier Prepare computer Host2 for the services tier
installation
Run installation program on computer Host2

Do tier-specific postinstallation tasks for computer Host2 (if any)

Prepare computer Host3 for the client tier

Run installation program on computer Host3

Postinstallation
configuration Complete postinstallation configuration tasks

End

Figure 43. Installation process flowchart: three-computer topology

Determining your database installation strategy
Determine the database system to install for your metadata repository and plan
your installation strategy. If installing IBM InfoSphere Information Analyzer, also
determine the database system to install for the analysis databases and how you
will install it (or whether to use the database system that you are using for the
metadata repository database).

Determining your database topology
For each database, decide whether to use an existing database system installation
or whether to create a new database system installation. If you are creating a new

Chapter 4. Planning Step 4: Determining your installation strategy 61

database system installation for a database, determine which database system to
use and where to locate the instance and the database.

Depending on the product modules that you choose to install, you must install one
or more of the following databases:
v The metadata repository. All databases that are used with IBM InfoSphere
Information Server share a single metadata repository.
v The IBM InfoSphere Information Analyzer analysis database (if you install this
product module). You can create one or more of these databases.
v The IBM InfoSphere QualityStage Match Designer match database (if you install
this product module).

Determining where to install each database

You can install an analysis database and the metadata repository in the same
database system instance as distinct databases. This topology is the default.

Alternatively, you can install the analysis databases and the metadata repository in
different instances.

If you create a match database for InfoSphere QualityStage, it must be in a
different database system instance.

Determining the database system to use for each database

InfoSphere Information Server supports IBM DB2, Oracle, and Microsoft SQL
Server database systems.

InfoSphere Information Server supports IBM DB2 clustering, high-availability
disaster recovery (HADR), and Oracle Real Application Clusters (RAC).

For supported database system versions for each operating system, see the system
requirements at www.ibm.com/support/docview.wss?uid=swg27016382.

The database system type for each database can be different. For example, the
metadata repository can be in the IBM DB2 database system, and the analysis
database can be an Oracle database system.

Note: In this documentation, the IBM DB2 database system refers to DB2 Database
for Linux, UNIX, and Windows, unless the documentation describes general DB2
support or specifically states that the information is relevant only to DB2 for
z/OS®.

Determining whether to use an existing database system
instance for a database

Instead of installing a new database system for a database, you can configure the
database in an existing database system instance. The database system must satisfy
the following requirements:
v It must be a supported DB2 database system and version, or another supported
database system type and version. See www.ibm.com/support/
docview.wss?uid=swg27016382.
v It must be located on a computer that is accessible by the computers where the
services tier and engine tiers are installed.

62 Planning, Installation, and Configuration Guide

v For the analysis database for InfoSphere Information Analyzer, the computer
must also be accessible to computers that host the client tier.

See “Preparing an existing DB2 database system” on page 148 or “Using a
database system other than DB2” on page 152.

Determining the database installation method
Determine how to install the database system for each database, and how to create
the database within the database system.

The procedure for setting up IBM InfoSphere Information Server databases differs
depending upon the database system that you use and the location of the database
system.
v For IBM DB2, set up the databases by using one of the following methods:
– Use the InfoSphere Information Server installation program to install DB2 9.7
on the target computer and create the database within it. DB2 9.7 is bundled
with InfoSphere Information Server. Within the installation program, select
the Metadata Repository tier installation option to install DB2 and create the
databases.
– Before you run the installation program, preinstall the DB2 database system
(any supported version) on the target computer or another computer. (See
“Preinstalling the IBM DB2 database system” on page 147.) Then create the
databases by using one of the following methods:
- If the DB2 instance is located on the target computer, use the InfoSphere
Information Server installation program to create the databases within the
instance. Within the installation program, select the Metadata Repository
tier installation option to create the databases.
- If the DB2 instance is not located on the target computer, create the
databases within the instance before running the InfoSphere Information
Server installation program. To create the databases, use scripts that are
provided with the InfoSphere Information Server software. In this case,
when you run the installation program you do not use the Metadata
Repository tier installation option at all.
For more information about the database creation scripts, see “Preparing an
existing DB2 database system by using scripts” on page 149.
If you decide to preinstall DB2 9.7, you can use the copy that is bundled with
InfoSphere Information Server, and install it by using the DB2 database
system installation program instead of the InfoSphere Information Server
installation program. See “Preinstalling the IBM DB2 database system” on
page 147.
v For another supported database system, set up the databases by using one of the
following methods:
– Preinstall the database system and create the databases within it before
running the InfoSphere Information Server installation program. To create the
databases, use scripts that are provided with the InfoSphere Information
Server software.
– Use an existing database system installation. Before you run the InfoSphere
Information Server installation program, create the databases within the
database system by using scripts that are provided with the InfoSphere
Information Server installation media.
In either case, when you run the installation program you do not use the
Metadata Repository tier option at all.

Chapter 4. Planning Step 4: Determining your installation strategy 63

For more information about the database creation scripts, see “Using a database
system other than DB2” on page 152.

After you create a database, it begins to fill with data when you start working with
the product modules that use the database.

To use a clustered database configuration for high availability, such as a DB2
cluster, DB2 high-availability disaster recovery (HADR) configuration, or Oracle
Real Application Clusters (RAC) setup, you must first install the database system
and configure the cluster. Then use the scripts on the InfoSphere Information
Server installation media to create the databases within the instance. When you
run the InfoSphere Information Server installation program, specify the database
system for the installation.

The following table summarizes the installation options.
Table 7. Summary: database system installation and database creation options for
supported configurations
Database system installation
Configuration options Database creation options
DB2 9.1, non-clustered Preinstall before you run the Use either of the following
configuration InfoSphere Information methods:
Server installation program v Use the InfoSphere
Information Server
installation program.
v Use the scripts on the
InfoSphere Information
Server installation media.
DB2 9.5, non-clustered Preinstall before you run the Use either of the following
configuration InfoSphere Information methods:
Server installation program v Use the InfoSphere
Information Server
installation program.
v Use the scripts on the
InfoSphere Information
Server installation media.
DB2 9.5, clustered Preinstall, and then create Use the scripts on the
configuration the cluster. InfoSphere Information
Server installation media.
DB2 9.5, high availability Preinstall, and then create Use either of the following
disaster recovery (HADR) the HADR configuration. methods to create the
configuration database on the primary
node:
v Use the InfoSphere
Information Server
installation program.
v Use the scripts on the
InfoSphere Information
Server installation media.

64 Planning, Installation, and Configuration Guide

Table 7. Summary: database system installation and database creation options for
supported configurations (continued)
Database system installation
Configuration options Database creation options
DB2 9.7, non-clustered Use either of the following Use either of the following
configuration methods: methods:
v Use InfoSphere v Use the InfoSphere
Information Server Information Server
installation program to installation program.
install v Use the scripts on the
v Preinstall before you run InfoSphere Information
the InfoSphere Information Server installation media.
Server installation
program
DB2 9.7, clustered Preinstall, and then create Use the scripts on the
configuration the cluster. InfoSphere Information
Server installation media.
DB2 9.7, high availability Use either of the following Use either of the following
disaster recovery (HADR) methods: methods to create the
configuration v Use InfoSphere database on the primary
Information Server node:
installation program to v Use the InfoSphere
install Information Server
v Preinstall before you run installation program.
the InfoSphere Information v Use the scripts on the
Server installation InfoSphere Information
program Server installation media.
Oracle database system (any Preinstall before you run the Use scripts on InfoSphere
supported version), InfoSphere Information Information Server
non-clustered configuration Server installation program. installation media.
Oracle Real Application Preinstall, and then create Use the scripts on the
Clusters (RAC) cluster (any the RAC setup. InfoSphere Information
supported version) Server installation media.
Microsoft SQL Server Preinstall before you run the Use the scripts on the
database system (any InfoSphere Information InfoSphere Information
supported version), Server installation program. Server installation media.
non-clustered configuration

Sizing the analysis databases
An analysis database is a component that IBM InfoSphere Information Analyzer
uses when it runs analysis jobs.

The extended analysis information is stored in the analysis databases. The
extended analysis information includes the high-volume, detailed analysis results,
such as column analysis, primary key analysis, and domain analysis. Additionally,
the metadata repository contains the information analysis projects that contain the
analysis results.

Before you create the analysis databases, review the quantity of data to be
analyzed. This review helps you to determine an appropriate storage size, location,
and configuration of the analysis databases.

Chapter 4. Planning Step 4: Determining your installation strategy 65

When you plan for the size of your databases, consider these factors that affect the
size of each database:
v Number of tables to be analyzed
v Number of columns in tables to be analyzed
v Number of unique records within these tables
v Number of char and varchar columns
v Types of analysis to be done
Unless you use sampled analysis, an analysis database might be larger than the
combined size of all the analyzed data sources.

Determining how to install WebSphere Application Server
As part of the services tier configuration, determine which version of IBM
WebSphere Application Server to install and how to install it.

The central component within the services tier is WebSphere Application Server.
This application server hosts the common and product-specific services for IBM
InfoSphere Information Server.

InfoSphere Information Server supports the following WebSphere Application
Server versions:
v WebSphere Application Server Network Deployment (ND) version 6.1
v WebSphere Application Server Network Deployment (ND) version 7.0

For 64-bit platforms, WebSphere Application Server ND 6.1 and 7.0 are available in
both 32-bit and 64-bit versions. Either version might be more appropriate as you
plan for longer-term performance and number of users.

Linux For Linux and Linux for System z®, the target version of WebSphere
Application Server is 64-bit.

WebSphere Application Server ND version 7.0 is bundled with InfoSphere
Information Server. For 64-bit platforms, the bundled version is 64-bit. For 32 bit
platforms, the bundled version is 32-bit.

To set up WebSphere Application Server, use one of the following methods:
v Use the InfoSphere Information Server installation program to install WebSphere
Application Server ND 7.0 as part of the services tier installation. The
installation program creates a server profile that is named InfoSphere and an
application server instance that is named server1. This application server is
licensed for use only with InfoSphere Information Server.
v Preinstall WebSphere Application Server ND 6.1 or 7.0, or use an existing
installation of one of these versions. In this case, you must create the profiles
manually.

To set up a clustered WebSphere Application Server ND configuration for high
availability and scalability, preinstall WebSphere Application Server ND. Configure
the cluster, profiles, and front-end dispatcher before you install InfoSphere
Information Server. See Chapter 23, “WebSphere Application Server clustering for
high availability and scalability,” on page 323.

66 Planning, Installation, and Configuration Guide

Planning volume groups and file systems
Before installing IBM InfoSphere Information Server, carefully plan your disk,
volume group, and file system resources to accommodate InfoSphere Information
Server and to provide for future growth. Some of the directories must be present
before you start the installation.

Note: Before you make changes to your computers, back up those computers
where you plan to install InfoSphere Information Server. See the IBM InfoSphere
Information Server Administration Guide.

Plan for the following separate file systems:
v Temporary storage.
v Program code: InfoSphere Information Server installation directory, database
server installation directory, IBM WebSphere Application Server installation
directory.
v Database storage directories for the metadata repository database, and for the
IBM InfoSphere Information Analyzer databases and IBM InfoSphere
QualityStage Match Designer database if you are installing these product
modules).

Isolate each functional subgroup of components in its own separate file system to
accommodate different performance and capacity characteristics and backup
requirements. File systems should be expandable without requiring destruction or
recreation, if the operating system that you are installing on permits it.

The following sections describe the directories for InfoSphere Information Server.
Most of the directories are created by the InfoSphere Information Server
installation program or other installation programs during installation. Other
directories must be present before you start the installation.
v “Directories that must be present on all tier computers before installation”
v “The InfoSphere Information Server installation directory (all tiers)” on page 69
v “Additional directories created on the metadata repository tier computer (IBM
DB2 only)” on page 71
v “Additional directory created on the services tier computer” on page 73
v “Additional directories created on each engine tier computer” on page 74
v “Additional directories created on each client tier computer” on page 75

Directories that must be present on all tier computers before
installation

The following directories are required on all tier computers before you run the
InfoSphere Information Server installation program.
Temporary directories
The temporary directories will contain temporary files required by the
installation program. The files are not needed after installation and can be
safely removed. You do not have to back up temporary directories.
The root user, the user who runs the installation program, and all other
InfoSphere Information Server users must have read, write, and execute
permissions to the temporary directories.
Put the temporary directories on a file system that has high-speed
read-write performance.

Chapter 4. Planning Step 4: Determining your installation strategy 67

Temporary directories: operating system-specific information Operating system Default directory path Additional requirements AIX Linux v /tmp The file system that contains the temporary directory must UNIX meet the system requirements for temporary space on its physical partition. This directory is directory path and the path typically the “x:\Documents of the files that the and Settings\user_name\ installation program extracts Local Settings\temp” into the path cannot exceed directory. On Windows Server 2008 and Windows 7. The following table provides operating system-specific information about the temporary directories. Installation. Long path the Microsoft Windows login names might cause the name of the user doing the installation to fail. If the command results do not list the directory or its parent directory. use the amount on the root file system (/). Table 8. and Configuration Guide . Solaris v /tmp None v /var/tmp Home directory for user IDs The home directory contains existing user IDs and (by default) the IDs that the installation program creates. 68 Planning. Use the df command to see the amount of available disk space per file system. Regularly back up this directory. where user_name is 256 characters. this directory is typically the “x:\Users\user_name\ AppData\Local\Temp” directory. The Administrator ID or the root user ID that performs the installation must be able to write to the directory and all subdirectories. installation. Windows The directory specified by The total number of the TEMP environment characters in the temporary variable. The following table provides operating system-specific information about the home directory.

Depending on the tier. the root user must have write access to the following files and directories on all logical computers: v / (root) v /etc v /etc/services v /etc/inittab v /etc/rc v /tmp v /var v /var/tmp v /usr/local/bin The InfoSphere Information Server installation directory (all tiers) This directory will contain the installed software for InfoSphere Information Server. and uninstallation files. If the home directory is on a network file system (NFS). Resource Tracker. libraries. this directory structure might include the engine. write.Table 9. Home directory: operating system-specific information Operating system Default directory path Additional requirements Linux UNIX /home/user_name Owners must have at least 755 permissions for their directories and parent directories. and execute permissions to the InfoSphere Information Server installation directory. configuration files. Job Monitor. Windows “c:\Documents and None Settings\user_name” or c:\Users\user_name Solaris zones allow you to divide a Solaris computer into multiple Solaris logical computers. Both the root user and the user who runs the installation program must have read. communication agents. This directory is created by the InfoSphere Information Server installation program. You cannot install InfoSphere Information Server into a Sparse Zone. Plan for this directory on high performance file systems. You can install InfoSphere Information Server into a global zone or a non-global zone. export the file system with the no_root_squash option enabled and the nosetuid option off. and have read/write/execute access to all subdirectories. Java runtime environment. When installing into a global zone or a non-global zone. Back up this directory after the installation and after any InfoSphere Information Server updates. Planning Step 4: Determining your installation strategy 69 . Chapter 4.

(period) 70 Planning. causing the installation to fail. Instead. install in separate subdirectories within a mount point. Installation. InfoSphere Information Server installation directory: operating system-specific information Operating system Default directory path Additional requirements Linux UNIX /opt/IBM/InformationServer v The dsadm account (administrator for the InfoSphere Information Server engine) must have these permissions: Read and execute For everything under the /opt/IBM/ InformationServer directory Read For the /opt. Windows C:\IBM\InformationServer Do not install on virtual drives (mapped. substituted. or SAN drives). and Configuration Guide . and /opt/IBM/ InformationServer directories Important: Directory ownership and permissions are set when you run the InfoSphere Information Server installation program. export the file system with the no_root_squash option enabled and the nosetuid option off. Tip: The installation directory path can contain only the following characters: v 0-9 v [a-z][A-Z] v . and not all mount points allow these changes. The installation changes ownership and permissions of directories that you install. v If the installation directory is on a network file system (NFS). Table 10.(hyphen) v _ (underscore) v . The following table provides operating system-specific information about the InfoSphere Information Server installation directory. v Do not install the software on the top-level mount point. /opt/IBM.

Table 11. Planning Step 4: Determining your installation strategy 71 . DB2 supports running the database software from a mounted NFS volume. Database server installation directory This directory contains the database server executable files and libraries. If these directories are on network mounted file systems such as the IBM AFS® file system. For other database system types. double byte characters.On Windows. (period) On Windows. { } [ ] Additional directories created on the metadata repository tier computer (IBM DB2 only) The following directories are created if a new DB2 instance is installed by the InfoSphere Information Server installation program or the DB2 installation program. Do not use accented characters. Linux UNIX The user who runs the installation program must have write access to file systems including /var and /usr/local/bin directories. The following table provides operating system-specific information about the database server installation directory. DB2 must reside on a local file system. double byte characters. space characters are also allowed. but does not support installation to a mounted NFS volume. or the following special characters in the path: ` ! @ # $ % ^ & * ( ) | \/ ? > <. Do not use accented characters. { } [ ] DB2 instance owner home directory The following table provides operating system-specific information about the DB2 instance owner home directory. or the following special characters in the path: ` ! @ # $ % ^ & * ( ) | \/ ? > <. Chapter 4. refer to the database system documentation. confirm that the installation user ID has write access.(hyphen) v _ (underscore) v . Database server installation directory: operating system-specific information Operating system Default directory path Additional requirements Linux UNIX /opt/IBM/db2 None Windows C:\IBM\SQLLIB None Tip: The installation directory path can contain only the following characters: v 0-9 v [a-z][A-Z] v . space characters are also allowed.

and read user ID: /home/dasusr1 permission to its parent directory. v Analysis databases for IBM InfoSphere Information Analyzer. v Test results database for IBM InfoSphere QualityStage (no default directory) The directory is created by the InfoSphere Information Server installation program. you back up a database by using the method provided by the database system. If the directory is on a network file system (NFS). and Configuration Guide . In general. export the file system with the no_root_squash option enabled and the nosetuid option off. Put the directory on a file system that has high-speed read-write performance. Solaris To install into a global zone or a non-global zone. c:\Users\db2admin Database storage directory This directory will contain data for the operations of InfoSphere Information Server. it is typically named iadb. Installation. 72 Planning. and execute permissions to its v DB2 Administration Server home directory. DB2 instance owner home directory: operating system-specific information Operating system Default directory path Additional requirements Linux UNIX v DB2 instance owner: The DB2 instance owner /home/db2inst1 must have read. This database is typically named xmeta. Regularly back up this directory. Windows DB2 instance owner: The DB2 instance owner “c:\Documents and must have full control of its Settings\db2admin” or own home directory. write. and can include the following databases: v Metadata repository. If there is only one analysis database. the root user must have write access to these directories. The following table provides operating system-specific information about the database storage directory. This data is separate and distinct from the data in your data sources. Table 12.

Application server installation directory This directory will contain WebSphere Application Server executable files and libraries. Windows C:\DB2 None Additional directory created on the services tier computer The following directory is created on the services tier computer by the InfoSphere Information Server installation program or WebSphere Application Server installation program. v If the directory is on a network file system (NFS). Application server installation directory: operating system-specific information Operating system Default directory path Additional requirements Linux UNIX /opt/IBM/WebSphere/ If the directory is on a AppServer network file system (NFS). Do not use accented characters. Table 14.(hyphen) v _ (underscore) v . { } [ ] Chapter 4. (period) On Windows. export the file system with the no_root_squash option enabled and the nosetuid option off. space characters are also allowed. or the following special characters in the path: ` ! @ # $ % ^ & * ( ) | \/ ? > <. Additional requirements and default paths for the database storage directory Operating system Default directory path Additional requirements Linux UNIX /opt/IBM/ v The DB2 database instance InformationServer/ owner (db2inst1) must Repository own the directories that store the metadata repository and the analysis databases. export the file system with the no_root_squash option enabled and the nosetuid option off. double byte characters. Planning Step 4: Determining your installation strategy 73 . Windows C:\IBM\WebSphere\AppServer None Tip: The installation directory path can contain only the following characters: v 0-9 v [a-z][A-Z] v .Table 13. including the following services: v Shared services of InfoSphere Information Server v Product module-specific services The following table provides operating system-specific information about the application server installation directory.

jobs. shell scripts. Windows C:\IBM\InformationServer\ None Server\Projects Directories for IBM InfoSphere DataStage and IBM InfoSphere QualityStage application files (excluding project data) These directories will contain items such as secured parameter files. and runtime metadata for each job. In addition. Project directories (runtime shadow repository) for the InfoSphere Information Server engine These directories will contain the following project-related items: v Job executables v Compiled routines v Buildop stage types v Job runtime artifacts v Job status records v Cached versions of design objects v Message handler files v DSParams file for project-specific variables that the IBM InfoSphere DataStage administrator defines v Files that the Hashed File stage creates for server jobs (default location). Because disk space typically is limited in the default directory within the installation file system. Installation. a better practice is to create the files for the Hashed File stage on a separate file system. and reports. data set header files. The InfoSphere DataStage project directories are located on the engine tier at the location that is configured in InfoSphere DataStage. schemas. InfoSphere Information Analyzer creates its own project directory for operations such as column analysis. Table 15. each InfoSphere Information Analyzer project is associated with an InfoSphere DataStage project within InfoSphere Information Analyzer. Project directories can grow to contain thousands of files and subdirectories depending on the number of projects. its source is extracted from the metadata repository and stored in the runtime repository to facilitate job compilation. However. SQL. Project directories: operating system-specific information Operating system Default directory path Additional requirements Linux UNIX /opt/IBM/ If the directory is on a InformationServer/Server/ network file system (NFS). The directories are created by the InfoSphere Information Server installation program. custom components. 74 Planning. The following table provides operating system-specific information about the project directories. and Configuration Guide . Projects export the file system with the no_root_squash option enabled and the nosetuid option off. you might want to create projects in their own file system. custom job logs. Additional directories created on each engine tier computer The following directories are created on each engine tier computer. When a job is compiled.

separate the data and scratch directories for each team on different file systems to create separate environments. and buffer) v InfoSphere Information Server artifacts. if the development and the production teams share an installation. edit the parallel configuration files to assign resources. create separate file systems for each data and scratch resource partition. temp. and other clients. Server/Datasets export the file system with the no_root_squash option v /opt/IBM/ enabled and the nosetuid InformationServer/ option off. InfoSphere Information Server client installation directory This directory will contain the installed software for IBM InfoSphere Information Server console. Chapter 4. Server/Scratch Windows v C:\IBM\ None InformationServer\ Server\Datasets v C:\IBM\ InformationServer\ Server\Scratch Additional directories created on each client tier computer The following directory is created on each client tier computer by the InfoSphere Information Server installation program. For example. InfoSphere DataStage and QualityStage Administrator clients. shared file system with the same mount point that is available on all servers. Planning Step 4: Determining your installation strategy 75 . Use local (internal) storage that is on a high-performance. Data file storage directories: operating system-specific information Operating system Default directory path Additional requirements Linux UNIX v /opt/IBM/ If the directories are on a InformationServer/ network file system (NFS). such as the disk and scratch file systems. After installation. Table 16.Data file storage directories These directories will contain temporary and intermediate data files for the parallel engine: v Engine temporary storage (scratch. to jobs at run time. Plan for these directories outside of the installation directory for InfoSphere Information Server. see the IBM InfoSphere DataStage and QualityStage Parallel Job Developer's Guide The following table provides operating system-specific information about data file storage directories. such as surrogate key files v Segment files for parallel data sets v Staging and archival storage for source files The engine uses temporary storage to hold data sets and to temporarily buffer virtual data set records. For better performance. For more information about the parallel engine configuration file.

Installation. v Identification: Communication is allowed only if the server is positively verified. The signature in the certificate is decrypted by the client to verify the authenticity of the sender. or the following special characters in the path: ` ! @ # $ % ^ & * ( ) | \/ ? > <. Therefore. do the following tasks: v Configure the application server to communicate by using SSL. and Configuration Guide . If you install a client tier on a computer where an engine tier is installed. you can enable SSL. but also requires more administrative work and can be error-prone. C:\IBM\InformationServer). If you do not configure HTTPS. SSL is not enabled by default within InfoSphere Information Server. space characters are also allowed. Table 17. SSL provides two benefits: v Encryption: Data sent over an SSL connection is encrypted. double byte characters. 76 Planning. If your environment requires confidentiality at the EJB or HTTP level. SSL configuration is optional. SSL adds greater security to your system. Before communications begin. the client tier and engine tier must share the same base directory (for example. v Inbound RMI/IIOP (EJB communication). the server sends the client a certificate. To enable SSL. You might not need SSL if you have a strong firewall in place. (period) On Windows. InfoSphere Information Server client installation directory Operating system Default directory path Additional requirements Windows C:\IBM\InformationServer\ None client Tip: The installation directory path can contain only the following characters: v 0-9 v [a-z][A-Z] v . { } [ ] Secure Sockets Layer (SSL) configuration IBM InfoSphere Information Server supports Secure Sockets Layer (SSL) communication between the application server and client components. Do not use accented characters. carefully consider the benefits and drawbacks before enabling SSL.(hyphen) v _ (underscore) v . The following table provides operating system-specific information about the InfoSphere Information Server client installation directory. HTTP is used instead. You can enable SSL for the following types of client-server communication: v Inbound secure HTTP (HTTPS). Do not install multiple versions of the client on a system that also has an engine tier. There is also a performance impact.

you must use the manual method after installation to configure the client tier for HTTPS. Application server HTTPS and SSL for inbound RMI/IIOP configuration Application server HTTPS configuration differs depending upon how the application server is installed: v If you install IBM WebSphere Application Server by using the InfoSphere Information Server installation program. Designer. you must also manually configure the tiers that you install in the pass for HTTPS.v Configure InfoSphere Information Server components to use SSL. In this case. and services tier computer – Rich client programs on the client tier computers. In this case. See “Manually configuring InfoSphere Information Server components to use HTTPS” on page 234. you must use the completely manual method in the following scenarios: – You install WebSphere Application Server by using the InfoSphere Information Server installation program. – If you set up a separate front-end HTTP server. v Automatically configure the components from within the installation program during installation. and Administrator clients. client tier computers. Planning Step 4: Determining your installation strategy 77 . both the HTTP and HTTPS protocols are enabled in WebSphere Application Server. Use the WebSphere Application Server administrative console to reenable this communication protocol in the application server. and install the HTTPS certificate on the computer. manually configure HTTPS. v If you preinstall WebSphere Application Server before running the InfoSphere Information Server installation program: – If you use the built-in WebSphere Application Server HTTP server. the IBM InfoSphere DataStage and QualityStage Director. either on a computer that has no other tiers installed. Do this task after InfoSphere Information Server is installed. use one of the following methods: v Manually edit configuration files on each computer that contains the components. – You install the client tier only in an installation pass. This method is available for most installation scenarios. and the IBM InfoSphere FastTrack client. Application server SSL for RMI/IIOP is disabled by the InfoSphere Information Server installation program. However. Chapter 4. See “Configuring the front-end HTTP server for HTTPS” on page 155. InfoSphere Information Server component HTTPS configuration To configure InfoSphere Information Server components to communicate with the application server by using HTTPS. These programs include the InfoSphere Information Server console. you must use the manual method after installation to configure the services tier for HTTPS. See “Enabling SSL for inbound RMI/IIOP” on page 233. These components include: – Agents on the engine tier computers – Command-line tools on the engine tier computers. or on a computer that has other tiers installed. If you install the client tier or the engine tier in the same installation pass. both the HTTP and HTTPS protocols are enabled in WebSphere Application Server. Do this task before InfoSphere Information Server is installed.

including underscores (_). The project name can contain alphanumeric characters. the certificate must be installed on the host computer to allow HTTPS communication. and Configuration Guide . The InfoSphere Information Server UpdateSignerCerts tool retrieves server signer certificates. the certificate must be installed on the host computer and added to the Java Runtime Executable (JRE) truststore. As projects are promoted through the source control. the user must specify an HTTPS URL and port in the browser. See “Running UpdateSignerCerts after enabling SSL or changing SSL at the cell level” on page 236. and IBM InfoSphere Information Analyzer store jobs. Project naming conventions Use these conventions when you name your projects. See Installing the Business Glossary Anywhere client. IBM InfoSphere Business Glossary. Installation. analysis. or IBM InfoSphere Metadata Workbench. The name of a project is limited to a maximum of 40 characters. You need to choose the name of one InfoSphere DataStage project during the initial installation. and logs in these projects. other steps are required: v For IBM InfoSphere Business Glossary Anywhere. v For rich client tools. Connection to the SSL-enabled server After SSL is enabled: v To access Web-based InfoSphere Information Server client tools such as the InfoSphere Information Server Web console. Project names cannot use these reserved letter combinations: v ds v DS v uv v UV Example A useful naming scheme has project names that you maintain in unison with the source code control. IBM InfoSphere QualityStage. v For IBM InfoSphere Business Glossary Client for Eclipse. the user must specify the HTTPS-enabled port when logging in. You must run the UpdateSignerCerts tool manually on all computers that host components that communicate with WebSphere Application Server by using SSL. When the server certificate changes (for example. a certificate expires or a new managed node is added to a WebSphere Application Server cluster). See “Installing IBM InfoSphere Business Glossary Client for Eclipse” on page 221. InfoSphere Information Server clients do not dynamically retrieve the new server certificates. For certain product modules. IBM InfoSphere DataStage. the name of the phase and the project reflect the version in this form: Phase_ProjectName_version where Phase corresponds to the phase in the application development life cycle: dev Development 78 Planning.

Verify groups and file systems” on page 67. if they do not already exist. Table 18. Linux UNIX On each computer. write. “Planning Step 4: Determining your installation strategy. Build and test the hardware infrastructure. also determine the database system to install for the analysis databases and how you will install it (or whether to use the database system that you are using for the metadata repository database). “Planning Step 1: Reviewing system requirements and release notes. that you have sufficient storage space in your file systems. Plan and build your topology 2. Chapter 1. Refer to the hardware documentation. Plan and build your topology To plan and build your topology. The root user must have read. Chapter 3. Chapter 2. and execute permissions to these directories.” on page 59 Determine the database system to install for your “Determining your database installation strategy” on metadata repository and plan your installation strategy. Planning Step 4: Determining your installation strategy 79 . The installation program must be run as root. follow the steps in the following task list. Install and configure each tier 3. Topology planning and building tasks Description For more information Review the system requirements. and “Planning volume are installing IBM InfoSphere Information Server.” on page 5 Design the topology of your installation. “Planning Step 3: Designing an installation topology. Plan the volume groups and file systems on which you See the system requirements. “Planning Step 2: Understanding tiers and components. page 61 If installing IBM InfoSphere Information Analyzer. Chapter 4. (Optional) Review the tasks necessary to enable Secure “Secure Sockets Layer (SSL) configuration” on page 76 Sockets Layer (SSL) within your installation. create the “Planning volume groups and file systems” on page 67 temporary directories /tmp and /var/tmp. 1. use the task lists in the following sections. Complete the following steps: 1. Perform postinstallation configuration tasks To complete these steps. it Integration test uat User acceptance test prod Production New installation road map (no high availability) Use this road map to complete a new installation of a configuration where there is no redundancy for high availability. Chapter 4. Determine whether to preinstall IBM WebSphere “Determining how to install WebSphere Application Application Server or preconfigure an existing Server” on page 66 installation of WebSphere Application Server.” on page 3 Learn about tiers and components.” on page 15 Plan your installation.

” on page 131 each tier computer. UNIX)” on page 137 Prepare each computer to run the InfoSphere Information “Preparing to run the installation program” on page 177 Server installation program. installing the software for the tiers. Installation of engine tier components on computer Host2. verify name resolution. 5. Install and configure the tiers in this order: v Metadata repository tier v Services tier v Engine tier v Client tier You can install more than one software tier on the same computer. Client tier preparation tasks on computer Host3. Installation of client tier components on computer Host3 by using the installation program. Installation of metadata repository tier and services tier components on computer Host1 by using the installation program. and the engine tier and client tier are each installed on computers Host2 and Host3. Engine tier preparation tasks on computer Host2. 4. 3. user limits on each computer. Metadata repository tier and services tier preparation tasks on computer Host1. Uncompress the software onto Server software. On all tier computers. In this case. 2. you complete the planning and preparation tasks for the tiers on the computer. 6. 80 Planning. complete the computer preparation tasks. and Configuration Guide . by using the installation program. Then complete the postinstallation tasks for the tiers on the computer. Linux UNIXUpdate the kernel parameters and “Modifying kernel parameters and user limits (Linux. Then run the installation program only once for that computer. 2a. “Obtaining IBM InfoSphere Information any applicable fix packs. 1. For example. complete the tasks in this order. and IBM InfoSphere Business Glossary Anywhere do not require an engine tier. follow the steps in the following task list. and open “Verifying the network and opening ports” on page 133 TCP ports for InfoSphere Information Server across any applicable firewalls. Then install IBM InfoSphere Information Server components. Not all product modules require an engine tier. IBM InfoSphere FastTrack. if the metadata repository tier and services tier components are installed on computer Host1. Metadata repository tier installation task list To configure the metadata repository tier. and back up any critical data on the computers. 2.Table 18. and perform postinstallation tasks. Install and configure each tier For each tier. Installation. IBM InfoSphere Business Glossary. Topology planning and building tasks (continued) Description For more information Obtain the InfoSphere Information Server software and Chapter 6.

See Part 3. do not run the installation program for this tier. Log in to each 142 account to confirm that it functions properly: v Owner of the metadata repository v (If installing InfoSphere Information Analyzer) The owner of the analysis database v If installing the DB2 database system: – (All operating systems) DB2 database administrator user – Linux UNIX DB2 database instance owner – Linux UNIX DB2 fenced user If you decide to preinstall DB2 or another supported Database system documentation.Table 19. If you preinstalled another database system. see “Preinstalling the IBM DB2 database system” on page 147 If you preinstalled DB2. Planning Step 4: Determining your installation strategy 81 . 2b. system. program for this tier in either of the following situations: v To install the DB2 database system on the target computer and create the metadata repository and analysis databases within it. if you decide “Preinstalling WebSphere Application Server” on page not to use the InfoSphere Information Server installation 153 program to install it. Table 20. installation (non-clustered installation)” on page 154 Chapter 4. For the DB2 database database system.” on page 165. v To create the metadata repository and analysis database within a local preinstalled supported DB2 database system instance. Services tier installation task list To configure the services tier. configure the scripts” on page 149 databases when you run the InfoSphere Information Server installation program. install the database system now. See “Preparing an existing DB2 database system by using scripts” on page 149. Alternatively. Installation tasks: Services tier Description For more information Preinstall WebSphere Application Server. “Installing IBM InfoSphere Information Server software. configure the databases within “Preparing an existing DB2 database system by using DB2 by using scripts. Preconfigure an existing WebSphere Application Server “Configuring an existing WebSphere Application Server installation if necessary. configure the databases by using scripts. If you preinstall the DB2 database system or another database system and create the databases within it by using scripts that are provided with the InfoSphere Information Server software. follow the steps in the following task list. Run the InfoSphere Information Server installation Run the InfoSphere Information Server installation program if necessary. Installation tasks: Metadata repository tier Description For more information Create the following administration accounts on the “Setting up administrator and owner accounts” on page metadata repository tier computer.

2d. Do this configuration if you are preinstalling WebSphere Application Server or preconfiguring an existing installation. “Installing IBM InfoSphere Information Server program. and you are configuring a separate front-end HTTP server. software. 82 Planning. Note: If you install WebSphere Application Server by using the InfoSphere Information Server installation program. follow the steps in the following task list to plan and configure the tier. Engine tier installation task list If your installation requires an engine tier. Create an administrator account for the InfoSphere “Setting up administrator and owner accounts” on page Information Server engine. Log in to the account to 142 activate the password. Note: If you are creating a configuration with more than one client computer. The installation program uses the locale and encoding information of the computer to determine whether it can provide language support. Note: If you are creating a configuration with more than one server engine. Run the InfoSphere Information Server installation Part 3. repeat these steps for each client computer. Installation. Installation tasks: Engine tier Description For more information Linux UNIX For non-English locales.Table 20.” on page 165 2c. repeat these steps for each server engine. make sure “Setting the locale for the target computer” on page 157 that the locale and encoding are set correctly. both the HTTP and HTTPS protocols are enabled in WebSphere Application Server. software.” on page 165 Review the system requirements to choose a supported “Installing a C++ compiler for job development” on page C++ compiler for job development. Table 21. and install it in its 159 default location. “Installing IBM InfoSphere Information Server program. configure the WebSphere “Configuring the front-end HTTP server for HTTPS” on Application Server front-end Web server to communicate page 155 by using secure HTTP (HTTPS). Run the InfoSphere Information Server installation Part 3. Client tier installation task list To configure your client tier. and Configuration Guide . Installation tasks: Services tier (continued) Description For more information (Optional) To increase security. These protocols are also enabled if you preinstall WebSphere Application Server but use the built-in HTTP server. follow the steps in the following task list.

v Configure InfoSphere Information Server agents for non-root administration. Planning Step 4: Determining your installation strategy 83 . Configure InfoSphere Information Server engine security. Map credentials if necessary.” on page 165 program. the Tier Selection page does not display. Double-click the setup icon to start the installation software. 4. “Installing IBM InfoSphere Information Server 1. accept all defaults. The program windows display in your default Web browser. When you install on page 233 InfoSphere Information Server in an IBM WebSphere Application Server Network Deployment 6. Note: If you are using the client-only installation media. In the installation program. “Configuring security for IBM InfoSphere 1. Postinstallation configuration tasks (all tiers) Description For more information Windows If necessary. 2. set up explicit firewall exceptions for client-side executable files that require network access. components to use HTTPS” on page 234 3. 2. also: v Configure IBM WebSphere Application Server for non-root administration. except in the Tier Selection page. Choose a user registry and configure it for InfoSphere Information Server. Create users and groups in the user registry. Configure security within InfoSphere Information Server: Chapter 17. choose Client only. Assign project roles if required by the installed suite components. Complete the rest of the installation. Installation tasks: Client tier Description For more information Run the installation program: Part 3. “Enablement of Secure Sockets Layer (SSL). perform these tasks: Table 23.1 or later environment. Perform postinstallation configuration tasks After you run the InfoSphere Information Server installation program for each tier. v If the installation program did not configure HTTPS for a tier computer during IBM InfoSphere Information Server installation.” v Enable SSL for inbound RMI/IIOP. manually configure HTTPS for that tier computer. (Optional) Manually configure secure HTTP (HTTPS) for “Manually configuring InfoSphere Information Server the client tier. The program installs the client tier only. Optionally. SSL for inbound RMI/IIOP communications is disabled by default. 5. (Optional) Configure Secure Sockets Layer (SSL): Chapter 16. Assign security roles to users and groups. 3. v Configure the Auditing service. 3.” on page 243 Information Server. Chapter 4.Table 22.

Table 23. Postinstallation configuration tasks (all tiers) (continued)
Description For more information
Configure IBM InfoSphere DataStage and IBM “Configuring IBM InfoSphere DataStage and IBM
InfoSphere QualityStage (if installed): InfoSphere QualityStage” on page 245
1. If you installed globalization support (NLS), ensure
that IBM InfoSphere DataStage users have the correct
settings specified for localization.
2. Configure access to ODBC data sources.
3. For systems that have large numbers of
simultaneously connected users or large numbers of
simultaneously running jobs, tune the server engine.

Optionally, also:
v Configure the parallel processing environment.
v Migrate jobs that you created in an earlier version of
InfoSphere DataStage to the current version.
v Configure the IBM InfoSphere QualityStage Match
Designer.
v Set up the application server to run SQA or
investigation reports.
v Test the installation.
Test the IBM InfoSphere Information Services Director “Testing the IBM InfoSphere Information Services
installation (if installed). Director installation” on page 256
Configure IBM InfoSphere Information Analyzer (if “Configuring IBM InfoSphere Information Analyzer” on
installed). page 256
Configure IBM InfoSphere Business Glossary (if “Configuring IBM InfoSphere Business Glossary” on
installed). page 258
Configure IBM InfoSphere Metadata Workbench (if “Configuring IBM InfoSphere Metadata Workbench” on
installed). page 258
Configure IBM InfoSphere FastTrack (if installed). “Configuring IBM InfoSphere FastTrack” on page 258
(Optional) Run the IBM Support Assistant Lite for “Installation verification and troubleshooting” on page
InfoSphere Information Server tool to verify the 197
installation.

Sample scenario A: Basic client-server topology
Sample scenario A is an installation on a single computer, plus client workstations.
There are no provisions for high availability.

A small retail chain wants to integrate its forecasting, distribution, replenishment,
and inventory management processes. As part of the integration, they want to
migrate financial reporting data from several systems to a single system of record.
They decide to create two separate IBM InfoSphere Information Server
installations: a small development system where they build and test projects and
jobs, and a larger production system (see “Sample scenario B: Topology with
isolated engine tier and parallel engine configuration” on page 88). For the
development system, a simple topology will be used where a single server with a
storage mechanism (Host1 in the following diagram) services five client
workstations.

84 Planning, Installation, and Configuration Guide

Client
workstations

Client tier

Network

Host1

Engine Services
tier tier

Metadata
repository tier

Figure 44. Sample scenario A topology

The following tables describe the installation tasks for this scenario.

Planning and building the topology

To plan and build the installation topology, the user completes the following tasks.
Table 24. Scenario A: Planning and building the topology
Task User action
Review the system requirements. Review the system requirements.
Determine the topology of the system. For the server, 64-bit Red Hat Enterprise Linux 5
Advanced Platform will be used on an AMD platform.

For the clients, existing Microsoft Windows XP
workstations will be used.
Determine the database configuration. Decide to use IBM DB2 for the metadata repository.
Decide to use the InfoSphere Information Server
installation program to create a stand-alone DB2 instance
on the server.
Determine whether to preinstall IBM WebSphere Decide to use the InfoSphere Information Server
Application Server, or preconfigure an existing installation program to create a stand-alone WebSphere
installation of WebSphere Application Server. Application Server ND instance on the server.

Chapter 4. Planning Step 4: Determining your installation strategy 85

Table 24. Scenario A: Planning and building the topology (continued)
Task User action
Plan the volume groups and file systems on which you Plan for the following directories:
are installing InfoSphere Information Server. v The home directory for user accounts. Verify that the
root user account has write access to this directory.
v Temporary storage for the installation program, as
recommended within the system requirements.
v The InfoSphere Information Server installation path on
a high-performance file system. The default path is to
be used.
v The WebSphere Application Server path. The default
path is to be used.
v A location for data set and scratch directories, outside
the InfoSphere Information Server installation
directory.

Verify all permissions, verify that all installation
directories are empty, and verify that all file systems
have sufficient free space.

On each computer, create the temporary directories /tmp
and /var/tmp, if they do not already exist. The root user
must have read, write, and execute permissions to these
directories. The installation program must be run as root.
(Optional) Review the tasks necessary to enable Secure To avoid complexity, SSL will not be enabled in this
Sockets Layer (SSL) within your installation. installation.
Build and test the hardware infrastructure. Set up the server and install the operating system. Set up
a high-speed network to allow the server and the client
systems to communicate.
Obtain the installation software. Obtain the InfoSphere Information Server software and
any applicable fix packs. Uncompress the software onto
each computer.
Verify the network and open ports. Verify the short and long host name resolution between
the server and the client workstations. Open all
necessary ports through the firewall.
Modify kernel parameters and user limits. Verify that the DB2 and WebSphere Application Server
kernel parameter and user limit requirements are met on
the server.
Prepare to run the installation program. Prepare each computer to run the InfoSphere Information
Server installation program, and back up any critical
data on the computers.

Installing and configuring the metadata repository, services, and
engine tiers

Because all tiers except the client tier are installed on the same server, the user
completes all preparation tasks for the metadata repository tier, services tier, and
engine tier together, runs the InfoSphere Information Server installation program,
and then completes postinstallation tasks for the three tiers.
Table 25. Scenario A: Metadata repository, services, and engine tier installation tasks
Task User action
Set the locale for the target computer. Since globalization (NLS) support will be enabled, ensure
that the locale and encoding are set correctly.

86 Planning, Installation, and Configuration Guide

Table 25. Scenario A: Metadata repository, services, and engine tier installation tasks (continued)
Task User action
Set up administrator and component owner accounts. Create the following administration accounts on the
server. Log in to each account to confirm that it functions
correctly:
v Owner of the metadata repository
v DB2 database administrator user
v DB2 database instance owner
v DB2 fenced user
v Administrator account for the InfoSphere Information
Server engine.
Preinstall the database system if necessary. Decide to install DB2 when the InfoSphere Information
Server installation program is run. Decide to configure
the metadata repository within the DB2 when the
InfoSphere Information Server installation program is
run.
Preinstall WebSphere Application Server if necessary. Decide to install WebSphere Application Server when the
InfoSphere Information Server installation program is
run.
Run the InfoSphere Information Server installation Run the installation program for this computer as
program. described in “Running the installation program for
Scenario A” on page 198.
Install a C++ compiler for job development. Review the system requirements to choose a supported
C++ compiler for job development, and install it in its
default location.

Installing the client tier

After reviewing the system requirements, the user completes the following tasks on
each client workstation:
Table 26. Scenario A: Client tier installation tasks
Task User action
Run the InfoSphere Information Server installation Run the installation program as described in “Running
program. the installation program for Scenario A” on page 198.

Postinstallation tasks

After installing all of the InfoSphere Information Server tiers, complete the tasks
that are described in the following table.
Table 27. Scenario A: Postinstallation configuration tasks
Task User action
Set up firewall exceptions for client-side executable files. No additional port exceptions are required for this
scenario.

Chapter 4. Planning Step 4: Determining your installation strategy 87

Table 27. Scenario A: Postinstallation configuration tasks (continued)
Task User action
Configure security within InfoSphere Information Server. v Use the WebSphere Application Server Administrative
Console to configure the system to use the local
operating system user registry.
v Use operating system administration tools to create
IBM InfoSphere DataStage users and groups within the
registry.
v Use the InfoSphere Information Server console to
assign security roles to the users and groups.
v Use the InfoSphere Information Server Web console to
set up the engine tier to use the local operating system
user registry. No credential mapping is required.
Ensure that InfoSphere DataStage users have the correct Decide to run the InfoSphere Information Server engine
settings specified for localization. by using the default locale settings that are inherited by
the operating system users. No action is necessary.
Configure access to ODBC data sources. Configure the ODBC drivers to access ODBC data
sources.
(Optional) Run the IBM Support Assistant Lite for “Installation verification and troubleshooting” on page
InfoSphere Information Server tool to verify the 197
installation.

Sample scenario B: Topology with isolated engine tier and
parallel engine configuration
Sample scenario B is installation with a computer that is dedicated to the IBM
InfoSphere Information Server engine.

The retail chain that built the Scenario A development system also wants to build a
larger production system. They are expecting a relatively high volume of job
throughput. They decide to create a configuration in which the engine tier is built
on a dedicated server (Host2 in the following diagram). To provide additional
capacity, they set up a separate computer (Host3) to serve as a parallel processing
compute node. The metadata repository tier and services tier share a server
(Host1). For higher security, HTTPS communication will be enabled between the
servers and the client workstations.

88 Planning, Installation, and Configuration Guide

Client
workstations

Client tier

Network

Host1 Host2 Host3

Services tier Engine tier Parallel processing

Metadata
repository tier

Figure 45. Sample scenario B topology

The following tables describe the installation tasks for this scenario.

Planning and building the topology

To plan and build the installation topology, the user completes the following tasks.
Table 28. Scenario B: Planning and building the topology
Task User action
Review the system requirements. Review the system requirements.
Determine the topology of the system. For the servers, 64-bit Red Hat Enterprise Linux 5
Advanced Platform will be used on an AMD CPU or
processor.

Decide to use the same Microsoft Windows XP
workstations that host the client tier in Scenario A. No
additional client tier installation is required.
Determine the database configuration. Decide to use IBM DB2 for the metadata repository.
Decide to use the InfoSphere Information Server
installation program to create a stand-alone DB2 instance
on the server.
Determine whether to preinstall IBM WebSphere Decide to use the InfoSphere Information Server
Application Server, or preconfigure an existing installation program to create a stand-alone WebSphere
installation of WebSphere Application Server. Application Server ND instance on the server.

Chapter 4. Planning Step 4: Determining your installation strategy 89

Table 28. Scenario B: Planning and building the topology (continued)
Task User action
Plan the volume groups and file systems on which you Plan for the following directories on all tier computers:
are installing InfoSphere Information Server. v The home directory for user accounts. Verify that the
root user account has write access to this directory.
v Temporary storage for the installation program, as
recommended within the system requirements.
v The InfoSphere Information Server installation path on
a high-performance file system. The default path is to
be used.
v A location for data set and scratch directories, outside
the InfoSphere Information Server installation
directory.

On Host1, also plan for the WebSphere Application
Server path. The default path is to be used.

Verify all permissions, verify that all installation
directories are empty, and verify that all file systems
have sufficient free space.

On each computer, create the temporary directories /tmp
and /var/tmp, if they do not already exist. The root user
must have read, write, and execute permissions to these
directories. The installation program must be run as root.
(Optional) Review the tasks necessary to enable Secure Decide to implement SSL within the installation, to
Sockets Layer (SSL) within your installation. enhance security.
Build and test the hardware infrastructure. Set up the server and install the operating system. Set up
a high-speed network to allow the server and the client
systems to communicate.
Obtain the installation software. Obtain the InfoSphere Information Server software and
any applicable fix packs. Uncompress the software onto
each computer.
Verify the network and open ports. Verify the short and long host name resolution between
all servers and the client workstations. Open all
necessary ports through the firewall.
Modify kernel parameters and user limits. Verify that the DB2 and WebSphere Application Server
kernel parameter and user limit requirements are met on
the servers.
Prepare to run the installation program. Prepare each computer to run the InfoSphere Information
Server installation program, and back up any critical
data on the computers.

Installing and configuring the metadata repository and services
tiers

The user completes all preparation tasks for the metadata repository tier and
engine tier together on Host1, then runs the IBM InfoSphere Information Server
installation program, and then completes postinstallation tasks for the two tiers.
Table 29. Scenario B: Metadata repository and services tier installation tasks
Task User action
Set the locale for the target computer. Because globalization (NLS) support will be enabled,
ensure that the locale and encoding are set correctly.

90 Planning, Installation, and Configuration Guide

Table 29. Scenario B: Metadata repository and services tier installation tasks (continued)
Task User action
Set up administrator and component owner accounts. Create the following administration accounts. Log in to
each account to confirm that it functions correctly:
v Owner of the metadata repository
v The owner of the analysis database
v DB2 database administrator user

v UNIX Linux DB2 database instance owner

v UNIX Linux DB2 fenced user
Preinstall the database system if necessary. Decide to install DB2 when the InfoSphere Information
Server installation program is run. Decide to configure
the metadata repository within the DB2 when the
InfoSphere Information Server installation program is
run.
Preinstall WebSphere Application Server if necessary. Decide to install WebSphere Application Server when the
InfoSphere Information Server installation program is
run.
(Optional) Configure the WebSphere Application Server Since WebSphere Application Server will be installed by
front-end Web server to accept secure HTTP (HTTPS) using the InfoSphere Information Server installation
calls. program, the WebSphere Application Server built-in Web
server is configured for both HTTP and HTTPS.
Run the InfoSphere Information Server installation Run the installation program for this computer as
program. described in “Running the installation program for
Scenario B” on page 201.

Installing and configuring the engine tier

After installing the metadata repository tier and services tier, the user reviews the
system requirements. Then the user installs the engine tier as described in the
following table.

Note: The user does not create a parallel engine configuration yet. Parallel engine
configuration is completed at the end of the installation procedure.
Table 30. Scenario B: Engine tier installation tasks
Task User action
Set the locale for the target computer. Since globalization (NLS) support will be enabled, ensure
that the locale and encoding are set correctly.
Set up administrator and component owner accounts. Create the Administrator account for the InfoSphere
Information Server engine. Log in to the account to
confirm that it functions correctly.
Run the InfoSphere Information Server installation Run the installation program for this computer as
program. described in “Running the installation program for
Scenario B” on page 201.
Install a C++ compiler for job development. Review the system requirements to choose a supported
C++ compiler for job development, and install it in its
default location.

Chapter 4. Planning Step 4: Determining your installation strategy 91

Installing the client tier

Because the same Microsoft Windows XP workstations for Scenario A are used for
Scenario B, no additional client tier installation is required. However, the
workstations must still be configured for HTTPS.

Task User action
(Optional) Configure HTTPS. Manually configure each client tier computer for HTTPS.

Postinstallation configuration tasks

After installing all InfoSphere Information Server tiers, the user configures the
system as described in the following table.
Table 31. Scenario B: Postinstallation configuration tasks
Task User actions
Set up firewall exceptions for client-side executable files. No additional port exceptions are required for this
scenario.
(Optional) Configure Secure Sockets Layer (SSL). v Enable SSL for inbound RMI/IIOP. When you install
InfoSphere Information Server in an IBM WebSphere
Application Server Network Deployment 6.1 or later
environment, SSL for inbound RMI/IIOP
communications is disabled by default.
v Manually configure the metadata repository/services
tier computer for HTTPS. Since WebSphere
Application Server was installed by the InfoSphere
Information Server installation program, the program
did not prompt the user to enable HTTPS.
Configure security within InfoSphere Information Server. v Use the WebSphere Application Server Administrative
Console to configure the system to use the local
operating system user registry.
v Use operating system administration tools to create
IBM InfoSphere DataStage users and groups within the
registry.
v Use the InfoSphere Information Server console to
assign security roles to the users and groups.
v Use the InfoSphere Information Server Web console to
set up the engine tier to use the local operating system
user registry on its own computer. Use the InfoSphere
Information Server Web console to map credentials
between local operating system user registry on the
engine tier computer and the local operating system
user registry on the metadata repository/services tier
computer.
v In new InfoSphere Information Server installations,
Secure Sockets Layer (SSL) is disabled by default. The
user reenables SSL to maximize system security.
Ensure that InfoSphere DataStage users have the correct Decide to run the InfoSphere Information Server engine
settings specified for localization. by using the default locale settings that are inherited by
the operating system users. No action is necessary.
Configure access to ODBC data sources. Configure the ODBC drivers to access ODBC data
sources.

92 Planning, Installation, and Configuration Guide

Table 31. Scenario B: Postinstallation configuration tasks (continued)
Task User actions
Create parallel engine nodes. v Copy the parallel engine components to the target
computer.
v Configure the parallel engine to run the remote shell
(rsh) or the Secure Shell (ssh) without a password.
v Set user privileges to run parallel jobs.
v Set environment variables for the parallel engine.
v Set the maximum number of processes for parallel
jobs, and the paging space for the parallel engine. Also
update the /etc/magic file.
v Configure connectivity to source databases.
v Stop and restart the InfoSphere Information Server
engine.
(Optional) Run the IBM Support Assistant Lite for “Installation verification and troubleshooting” on page
InfoSphere Information Server tool to verify the 197
installation.

New installation road map (high availability active-passive
configuration)
Use this road map to complete a new installation of a two-server active-passive
configuration where all components can fail over from one server to the other.

Complete the following steps:
1. Plan and build your topology.
2. Install and configure high availability cluster management software.
3. Install and configure the metadata repository tier, services tier, and engine tier
within the two-server configuration.
4. Install the client tier.
5. Perform postinstallation configuration tasks.

To complete these steps, use the task lists in the following sections.

1. Plan and build your topology

To plan and build your topology, follow the steps in the following task list.
Table 32. Topology planning and building tasks
Description For more information
Review the system requirements. Chapter 1, “Planning Step 1: Reviewing system
requirements and release notes,” on page 3
Verify that you are installing the correct packages for Chapter 1, “Planning Step 1: Reviewing system
your operating system. requirements and release notes,” on page 3
Learn about tiers and components. Chapter 2, “Planning Step 2: Understanding tiers and
components,” on page 5
Learn about the topology of the active-passive high “Active-passive topology” on page 28
availability configuration.

Chapter 4. Planning Step 4: Determining your installation strategy 93

and open “Verifying the network and opening ports” on page 133 TCP ports for InfoSphere Information Server across any applicable firewalls. 2a. services tier. UNIX)” on page 137 Prepare both computers to run the InfoSphere “Preparing to run the installation program” on page 177 Information Server installation program. and the storage v Linux UNIX “Setting up the servers. and storage (System Automation for Multiplatforms example)” on page 303 v Windows “Setting up the servers. device. and Configuration Guide . and “Planning volume are installing IBM InfoSphere Information Server. if they do not already exist. the network. network. Linux UNIX On both computers. To manage the cluster and enable failover. page 61 If installing IBM InfoSphere Information Analyzer. Then run the installation program on each client tier computer to install the client tier software. Determine if you need to preinstall IBM WebSphere “Determining how to install WebSphere Application Application Server or preconfigure an existing Server” on page 66 installation of WebSphere Application Server. Configure the servers. Obtain the InfoSphere Information Server software and Chapter 6. InfoSphere Information Server metadata repository. The root user must have read. run the IBM InfoSphere Information Server installation program only once to install the software on the mass storage device. install high availability software such as IBM Tivoli System Automation for Multiplatforms. “Obtaining IBM InfoSphere Information any applicable fix packs. and storage (MSCS example)” on page 317 Plan the volume groups and file systems on which you See the system requirements. and engine tier software installation task list 94 Planning. write. services. Linux UNIXUpdate the kernel parameters and “Modifying kernel parameters and user limits (Linux. and back up any critical data on the computers. Topology planning and building tasks (continued) Description For more information Determine the database system to install for your “Determining your database installation strategy” on metadata repository and plan your installation strategy. verify name resolution. user limits on both computers. 2. and engine tier. network. create the “Planning volume groups and file systems” on page 67 temporary directories /tmp and /var/tmp.” on page 131 each computer. Installation. (Optional) Review the tasks necessary to enable Secure “Secure Sockets Layer (SSL) configuration” on page 76 Sockets Layer (SSL) within your installation. that you have sufficient storage space in your file systems. On both computers. The installation program must be run as root.Table 32. Uncompress the software onto Server software. Install and configure the tiers The servers will accommodate the metadata repository tier. For this reason. and execute permissions to these directories. also determine the database system to install for the analysis databases and how you will install it (or whether to use the database system that you are using for the metadata repository database). Verify groups and file systems” on page 67.

make sure that the locale and “Setting the locale for the target computer” on page 157 encoding are set correctly. Refer to the documentation for your high availability cluster management software. 142 If you decide to preinstall DB2 or another supported For DB2. configure the databases by using scripts. Set up administrator and component owner accounts on “Setting up administrator and owner accounts” on page the shared storage device. configurations. For example cluster. configure the databases within v “Preparing an existing DB2 database system” on page DB2 by using scripts. and engine tiers Description For more information Acquire and install high availability cluster management Refer to the documentation for your high availability software on both engine tier servers. see the following topics: v Linux UNIX “Installing the high availability software (System Automation for Multiplatforms example)” on page 304 v Windows “Setting up the cluster (MSCS example)” on page 317 Set the service IP address. and set up the cluster management software. See “Defining and starting the resource group (System Automation for Multiplatforms example)” on page 306. To configure your tier software. see “Preinstalling the IBM DB2 database database system. Preinstall WebSphere Application Server Network “Preinstalling WebSphere Application Server” on page Deployment on the shared storage device. services. see the following topics: v Linux UNIX “Setting up the virtual IP address (System Automation for Multiplatforms example)” on page 305 v Windows “Setting up the virtual IP address (MSCS example)” on page 318 Linux UNIX Define and start a resource group. The installation program uses the locale and encoding information of the computer to determine whether it can provide language support. For other database systems. install the database system now. if you decide 153 not to use the InfoSphere Information Server installation program to install it. For example configurations. system” on page 147. If you preinstalled DB2. configure the 148 databases when you run the InfoSphere Information v “Using a database system other than DB2” on page Server installation program. see the database system documentation. 152 If you preinstalled another database system. Planning Step 4: Determining your installation strategy 95 . Chapter 4. Refer to the documentation for your high availability cluster management software. Installation tasks: Metadata repository. Alternatively. Table 33. For non-English locales. follow the steps in the following task list.

Installation tasks: Metadata repository. For an example based on Tivoli System Automation for Multiplatforms. enter the virtual host name that was created when the HA software was configured. “Preparing for the IBM InfoSphere Designer database. see “Testing the configuration (System Automation for Multiplatforms example)” on page 311. Do this configuration if you are preinstalling WebSphere Application Server or configuring an existing installation. In the Port field. specify a path on the shared storage device. 96 Planning. and engine tiers (continued) Description For more information (Optional) To increase security. 159 Preconfigure the IBM InfoSphere QualityStage Match Chapter 11. services. type the HTTP dispatcher port number on which secure HTTP (HTTPS) has previously been configured. v Whenever prompted for an installation directory. In the Virtual host name field. open the URL that the ./setup -verbose v Windows “Installing IBM InfoSphere Information 2. Installation. Install a C++ compiler on the shared storage device for “Installing a C++ compiler for job development” on page job development. v In the High Availability Server Cluster Configuration page. Using a supported web browser on a Windows Server in the cluster (MSCS example)” on page 318 computer. and you are configuring a separate front-end HTTP server. configure the WebSphere “Configuring the front-end HTTP server for HTTPS” on Application Server front-end Web server to accept secure page 155 HTTP (HTTPS) calls.” on page 161 Run the installation program: For example configurations. click Server cluster configuration. see the following topics: v Linux UNIX “Setting up the high availability control scripts (System Automation for Multiplatforms example)” on page 309 v Windows “Setting up high availability control scripts (MSCS example)” on page 319 Test the high availability configuration. and Configuration Guide . Follow the prompts in the wizard. run the following command to start the Information Server in the cluster (System Automation installation program: for Multiplatforms example)” on page 309 . For example configurations. Go to the documentation for your high availability cluster management software. QualityStage Match Designer database. These protocols are also enabled if you preinstall WebSphere Application Server but use the built-in HTTP server. v (Optional) To configure HTTPS. Note: If you install WebSphere Application Server by using the InfoSphere Information Server installation program. 3./setup command displays. both the HTTP and HTTPS protocols are enabled in WebSphere Application Server. click Use Secure Sockets Layer (SSL) for HTTP communication.Table 33. Set up the resource agent scripts. Simulate active cluster node failures and network failures and observe the results. see the following topics: 1. when the installation program prompts you. From the is-suite directory on the installation v Linux UNIX “Installing IBM InfoSphere media.

The program windows display in your default Web browser. manually configure HTTPS. Note: If you are using the client-only installation media. follow the steps in the following task list.” v Enable SSL for inbound RMI/IIOP.” on page 167 1. The program installs the client tier only. For example configurations. repeat these steps for each client computer. 3. choose Client only. Note: If you are creating a configuration with more than one client computer. the Tier Selection page does not display. 2b. except in the Tier Selection page.” on page 231 access. Perform postinstallation configuration tasks After you run the InfoSphere Information Server installation program for each tier. In the installation program. “Enablement of Secure Sockets Layer (SSL). (Optional) Configure Secure Sockets Layer (SSL): Chapter 16. “Firewall exceptions for client-side executable for client-side executable files that require network files (Windows). Complete the rest of the installation. Go to the documentation for your high availability cluster management software. Test the engine tier failover function. Double-click the setup icon to start the installation program. Planning Step 4: Determining your installation strategy 97 . set up explicit firewall exceptions Chapter 15. Installation tasks: Client tier Description For more information Run the installation program: Chapter 12. perform these tasks: Table 35.1 or later environment. SSL for inbound RMI/IIOP communications is disabled by default. 2. v If the installation program did not configure HTTPS during IBM InfoSphere Information Server installation. “Installing new software. Table 34. components to use HTTPS” on page 234 3. Client tier installation task list To configure your client tier. (Optional) Manually configure secure HTTP (HTTPS) for “Manually configuring InfoSphere Information Server the client tier. Postinstallation configuration tasks (all tiers) Description For more information Windows If necessary. see the following topics: v Linux UNIX “Testing the configuration (System Automation for Multiplatforms example)” on page 311 v Windows “Testing the configuration (MSCS example)” on page 319 Chapter 4. When you install on page 233 InfoSphere Information Server in an IBM WebSphere Application Server Network Deployment 6. accept all defaults.

If you installed globalization support (NLS). v Test the installation. v Configure InfoSphere Information Server agents for non-root administration. 5. Configure IBM InfoSphere DataStage and IBM “Configuring IBM InfoSphere DataStage and IBM InfoSphere QualityStage (if installed): InfoSphere QualityStage” on page 245 1. Configure access to ODBC data resources. “Configuring IBM InfoSphere FastTrack” on page 258 (Optional) Run the IBM Support Assistant Lite for See “Installation verification and troubleshooting” on InfoSphere Information Server tool to verify the page 197 installation. Choose a user registry and configure it for InfoSphere Information Server. Optional: v Configure the parallel processing environment. Optionally. Configure InfoSphere Information Server engine security. Assign project roles if required by the installed suite components. 4. Assign security roles to users and groups. Postinstallation configuration tasks (all tiers) (continued) Description For more information Configure security within InfoSphere Information Server: Chapter 17. 2. page 256 Configure IBM InfoSphere Business Glossary (if “Configuring IBM InfoSphere Business Glossary” on installed).” on page 243 Information Server. 98 Planning. For systems that have large numbers of simultaneously connected users or large numbers of simultaneously running jobs. page 258 Configure IBM InfoSphere Metadata Workbench (if “Configuring IBM InfoSphere Metadata Workbench” on installed). v Configure the Auditing service. also: v Configure IBM WebSphere Application Server for non-root administration. v Set up the application server to run SQA or investigation reports. Director installation” on page 256 Configure IBM InfoSphere Information Analyzer (if “Configuring IBM InfoSphere Information Analyzer” on installed). v Configure the IBM InfoSphere QualityStage Match Designer. ensure that IBM InfoSphere DataStage users have the correct settings specified for localization. Map credentials if necessary.Table 35. 3. Create users and groups in the user registry. tune the server engine. page 258 Configure IBM InfoSphere FastTrack (if installed). v Migrate jobs that you created in an earlier version of InfoSphere DataStage to the current version. Test the IBM InfoSphere Information Services Director “Testing the IBM InfoSphere Information Services installation (if installed). Installation. and Configuration Guide . “Configuring security for IBM InfoSphere 1. 3. 2.

network. and IBM InfoSphere Information Analyzer for data integration. they decide to implement a two-server active-passive topology for this system. Several client workstations will access both systems. the system must be highly available. the system is nonoperational.Sample scenario C: Two-server active-passive high availability topology Sample scenario C is a topology that includes two computers that can fail over to one another in case of failure. the passive node will be used as a parallel engine compute node while the primary node is active. They do not expect a great deal of volume on their production system. v A more highly available production system. IBM InfoSphere QualityStage. However. Planning Step 4: Determining your installation strategy 99 . All components are to run on one server and fail over to the other server if a hardware. or operating system failure occurs. using the two-server active-passive configuration with a storage mechanism. To increase processing throughput. The configuration is identical to “Sample scenario A: Basic client-server topology” on page 84. To minimize hardware costs. A small industrial company has purchased IBM InfoSphere Information Server and plans to use IBM InfoSphere DataStage. While the failover is occurring. or if an administrator forces a failover for maintenance purposes. They decide to create two separate IBM InfoSphere Information Server installations: v A small development system where projects and jobs are built and tested. Chapter 4. They expect to have three or four developers for the project. The following diagram illustrates this topology.

or preconfigure an existing installation program to create a stand-alone WebSphere installation of WebSphere Application Server. For the servers. Uncompress the software onto each computer. Obtain the installation software. For the clients. Planning and building the topology To plan and build the installation topology. Scenario C: Planning and building the topology Task User action Review the system requirements. Sample scenario C topology The following tables describe the installation tasks for this scenario. Client workstations Client tier Host1 Host2 (Active) (Passive) Engine Services Parallel processing tier tier Database instance HA management HA management software software SAN Engine Services tier tier (installed) (installed) Database Figure 46. Review the system requirements. existing Microsoft Windows XP workstations will be used. Installation. 100 Planning. 64-bit Red Hat Enterprise Linux 5 Advanced Platform will be used on an AMD platform. and Configuration Guide . Obtain the InfoSphere Information Server software and any applicable fix packs. Determine your installation topology. the user completes the following tasks. Determine whether to preinstall IBM WebSphere Decide to use the InfoSphere Information Server Application Server. Table 36. Application Server ND instance on the SAN.

and back up critical data on the computers. and verifies that all file systems have sufficient free space. networks. verify name resolution. This directory is on the SAN. v Temporary storage for the installation program. v The InfoSphere Information Server installation path. On both computers. v The WebSphere Application Server path. services tier. administrator. and then completes postinstallation tasks for the three tiers. SSL will be enabled in this configuration. Prepare to run the installation program. Set up the servers with redundant connections to two separate high-speed networks. Update the kernel parameters and user limits on both servers. and storage device. Prepare both computers to run the InfoSphere Information Server installation program. This directory is on the SAN. Create an /opt/IBM directory on each server and mount the storage device on the active server.Table 36. verifies that all installation directories are empty. This directory is located on the primary server local storage. Make sure that the directory is shared and has the correct permissions. and engine tiers Because all tiers except the client tier are installed on the same server. services. Plan for the following directories and paths: v The home directory for user accounts. because the metadata repository tier and services tier are to be installed in this server configuration. Chapter 4. as recommended within the system requirements. ensure that the following directories on the storage device are shared and have the correct permissions: v The /opt/IBM/WebSphere directory for WebSphere Application Server v The /opt/IBM/db2 directory.. Verify all permissions. and fenced user directories for DB2 Plan volume groups and file systems. This directory is on the SAN. then runs the InfoSphere Information Server installation program. Planning Step 4: Determining your installation strategy 101 . and engine tier together. and open TCP ports for InfoSphere Information Server across any applicable firewalls. Review Secure Sockets Layer (SSL) configuration tasks. Verify the network and open ports. Verify that the root user account has write access to this directory. outside the InfoSphere Information Server installation directory. Also. Modify kernel parameters and user limits. v A location for data set and scratch directories. The heartbeat signal is to travel over a serial network. and the IBM DB2 instance owner. Installing and configuring the metadata repository. Create an identical directory on both servers. the user completes all preparation tasks for the metadata repository tier. Scenario C: Planning and building the topology (continued) Task User action Configure the servers.

services. ensure that the locale and encoding are set correctly on both servers. Create the following administration accounts on the shared storage device. Allocate IP addresses and verify that they are valid across the network. Set up the service IP address. Scenario C: Metadata repository. Set the locale for the target computer. Define and start a resource group. Download the software packages and install them on both servers. Inform Tivoli System Automation for Multiplatforms that the network adapters on the nodes are appropriate and equivalent for the service IP address. InfoSphere Information Server installation program is run. and engine tier installation tasks Task User action Acquire and install high-availability cluster management Decide to use IBM Tivoli System Automation for software on both servers. and install it in its default location. Define the resource group and create the automation policy by using relationship definitions. Because WebSphere Application Server is installed in this manner. Configure the network. Decide to install DB2 when the InfoSphere Information Server installation program is run. Decide to configure the metadata repository database and analysis database in the new DB2 instance when the InfoSphere Information Server installation program is run. Review the system requirements to choose a supported C++ compiler for job development. Preinstall the database system if necessary. Since globalization (NLS) support will be enabled. to configure HTTPS no additional WebSphere Application Server-specific changes must be made before running the installation program. Installation. and Configuration Guide . 102 Planning. Log in to each account to confirm that it functions correctly: v Owner of the metadata repository v DB2 database administrator user v DB2 database instance owner v DB2 fenced user v Administrator account for the InfoSphere Information Server engine. Define the service (virtual) IP address. Set up administrator and component owner accounts.Table 37. Install a C++ compiler for job development. Multiplatforms. Create a network tiebreaker. and activate the resource group. Preinstall WebSphere Application Server Network Decide to install WebSphere Application Server when the Deployment if necessary.

enter the virtual host name that was created when the high availability software was configured. 3. Using a supported web browser on a Windows computer. Note: If you are using the client-only installation media. In the installation program. open the URL that the . Double-click the setup icon to start the installation program. Installing the client tier After reviewing the system requirements. 4. From the is-suite directory on the installation media. Follow the prompts in the wizard. click Use Secure Sockets Layer (SSL) for HTTP communication. v Whenever prompted for an installation directory. tier. The program windows display in your default Web browser. Chapter 4. accept all defaults. run the following command to start the installation program: . Scenario C: Metadata repository. Scenario C: Client tier installation tasks Task User action Run the InfoSphere Information Server installation Run the installation program: program. 3. v In the High Availability Server Cluster Configuration page. Complete the rest of the installation. and engine tier installation tasks (continued) Task User action Run the InfoSphere Information Server installation Run the installation program: program. Manually configure InfoSphere Information Server Manually configure secure HTTP (HTTPS) for the client components to use HTTPS. once on each client workstation: Table 38. In the Port field. stop. The program installs the client tier only.Table 37. 1. the Tier Selection page does not display. click Server cluster configuration. Set up the resource agent scripts. Planning Step 4: Determining your installation strategy 103 . and monitor the servers. Test the high-availability configuration. Simulate active cluster node failures and network failures and observe the results. 1. the user completes the following tasks 5 times. specify a path on the shared storage device./setup command displays. type the HTTP dispatcher port number on which secure HTTP (HTTPS) has previously been configured. On the product selection page. Create the application resource. select InfoSphere DataStage and InfoSphere Information Analyzer. Implement the scripts to start. 2. Replicate the /etc/services entries on both servers. v (Optional) When the installation program prompts you. choose Client only. services. In the Virtual host name field./setup -verbose 2. except in the Tier Selection page.

v Copy the parallel engine components to the target computer. v The system will use the InfoSphere Information Server internal user registry. v Set user privileges to run parallel jobs. v Configure the parallel engine to run the remote shell (rsh) or the Secure Shell (ssh) without a password. Since WebSphere Application Server was installed by the InfoSphere Information Server installation program. Simulate active server failures and network failures and observe the results. the program did not prompt the user to enable HTTPS. SSL for inbound RMI/IIOP communications is disabled by default. v Configure connectivity to source databases. Postinstallation configuration tasks After installing all InfoSphere Information Server tiers. v Enable SSL for inbound RMI/IIOP. default locale settings that are inherited by the operating system users. v Use the InfoSphere Information Server Web console to set up the engine tier to use the local operating system user registry. 104 Planning. Configure security. and Configuration Guide . and the paging space for the parallel engine. When you install InfoSphere Information Server in an IBM WebSphere Application Server Network Deployment 6. Table 39. v Stop and restart the InfoSphere Information Server engine.1 or later environment. Use the InfoSphere Information Server Web console to map credentials between local operating system user registry and the InfoSphere Information Server internal user registry. v Set environment variables for the parallel engine. and to assign security roles to users and groups. Ensure that IBM InfoSphere DataStage users have the The InfoSphere Information Server engine will use the correct settings specified for localization. Installation. Configure the parallel processing environment. Test the engine tier failover function. v Manually configure the metadata repository/services tier computer for HTTPS. Scenario C: Postinstallation configuration tasks Task User action Enable Secure Sockets Layer (SSL). Configure the ODBC drivers to access ODBC data sources. Configure access to ODBC data sources. Also update the /etc/magic file. v Set the maximum number of processes for parallel jobs. v Use the InfoSphere Information Server consoles to create users and groups from the registry. No action is required. the user configures the system as described in the following table.

Prepare the IBM InfoSphere Information Server databases within the cluster. v Set up security for the project. 9. New installation road map (high availability clustered topology) Use this road map to complete a new installation where the metadata repository database system and services tier (IBM WebSphere Application Server) are set up in a clustered topology. Run the InfoSphere Information Server installation program to install InfoSphere Information Server software for the services tier and cause it to communicate with the database cluster. 2. v Verify credentials. Plan the topology. and configure settings. 5. See “Setting up the metadata repository database in an IBM DB2 database HADR configuration” on page 345. 3. associate imported metadata with the project. 7. configure HADR after you install InfoSphere Information Server. 6. v Define the Data Source Name (DSN) to the analysis database and source databases. v Import metadata into the metadata repository. Planning Step 4: Determining your installation strategy 105 . The engine tier is set up in an active-passive high availability configuration. Prepare the database cluster. 8. Chapter 4. Install and configure high-availability cluster management software on the engine tier servers. v Create a project. If you are setting up an IBM DB2 high-availability disaster recovery (HADR) topology. Install and configure the client tier. Scenario C: Postinstallation configuration tasks (continued) Task User action Configure the IBM InfoSphere QualityStage Match Do the following tasks: Designer. Install and configure the engine tier. 10. 4. Prepare the WebSphere Application Server cluster. To complete these steps. Complete the following steps: 1. Configure WebSphere Application Server to communicate with the database cluster.Table 39. (Optional) Run the IBM Support Assistant Lite for See “Installation verification and troubleshooting” on InfoSphere Information Server tool to verify the page 197 installation. use the task lists in the following sections. Perform postinstallation configuration tasks.

” on page 5 Design the topology of your installation. and storage (System Automation for Multiplatforms example)” on page 303 v Windows “Setting up the servers. network. “IBM WebSphere Application Server Network Deployment clustering” on page 31 Build and test the hardware infrastructure. “Planning Step 2: Understanding tiers and components. Linux UNIX Update the kernel parameters and “Modifying kernel parameters and user limits (Linux. verify name resolution. you have sufficient storage space in your file systems. Topology planning and building tasks Description For more information Review the system requirements.” on page 131 each tier computer. user limits on each tier computer. “Determining your database topology” on page 61 Determine your cluster architecture. Obtain the InfoSphere Information Server software and Chapter 6.” on page 3 Learn about tiers and components. network. and storage (MSCS example)” on page 317 Plan the volume groups and file systems on which you See the system requirements. “Obtaining IBM InfoSphere Information any applicable fix packs. and open “Verifying the network and opening ports” on page 133 TCP ports for InfoSphere Information Server across any applicable firewalls. 1. Metadata repository tier: v DB2 clustered installation: “Preparing the servers. On all tier computers. if they do not already exist. Chapter 1. and Configuration Guide . Uncompress the software onto Server software. and execute permissions to these directories. Plan and build your topology To plan and build your topology. create the “Planning volume groups and file systems” on page 67 temporary directories /tmp and /var/tmp. UNIX)” on page 137 106 Planning. file system. storage. follow the steps in the following task list. Table 40. Chapter 2. write. The root user must have read. Linux UNIX On each computer. and “Planning volume are installing InfoSphere Information Server . “High availability configurations” on page 27 Determine your database system topology. and network” on page 346 v Oracle Real Application Clusters (RAC) installation: “Oracle RAC requirements” on page 357 Services tier: v “IBM WebSphere Application Server Network Deployment clustering” on page 31 Engine tier: v Linux UNIX “Setting up the servers. (Optional) Review the tasks necessary to enable Secure “Secure Sockets Layer (SSL) configuration” on page 76 Sockets Layer (SSL) within your installation. “Planning Step 1: Reviewing system requirements and release notes. The installation program must be run as root. Installation. Verify that groups and file systems” on page 67. and storage” on page 338 v DB2 HADR installation: “Preparing the servers.

Install and configure the tiers in this order: v Metadata repository tier v Services tier v Engine tier v Client tier 2a. Create the following administration accounts on each “Setting up administrator and owner accounts” on page computer that will host the database system. complete planning tasks and preinstallation tasks. Metadata repository tier installation task list To configure your metadata repository tier. Then install IBM InfoSphere Information Server components. follow the steps in the following task list.Table 40. for an IBM DB2 clustered topology. Log in to each account to confirm that it functions properly: v Owner of the metadata repository v (If installing IBM InfoSphere Information Analyzer) The owner of the analysis database v If installing the DB2 database system: – (All operating systems) DB2 database administrator user – Linux UNIX DB2 database instance owner – Linux UNIX DB2 fenced user Install the database system. Table 41. Topology planning and building tasks (continued) Description For more information Prepare each tier computer to run the InfoSphere “Preparing to run the installation program” on page 177 Information Server installation program. Planning Step 4: Determining your installation strategy 107 . The 142 accounts on each computer must be identical. Install and configure the tiers For each tier. and perform postinstallation tasks. Installation tasks: Metadata repository tier Description For more information (Optional.) Install “Installing high availability software on DB2 database high-availability (HA) software to monitor the health of system servers” on page 339 the servers and to manage failover. create the database cluster. 2. repository database” on page 340 v DB2 HADR installation: “Installing the DB2 database system and creating the metadata repository database” on page 347 v Oracle RAC installation: “Creating the metadata repository database and running the installation program within an Oracle RAC configuration” on page 357 Chapter 4. v DB2 clustered installation: “Installing the DB2 database and preconfigure the database by using scripts that are system and creating the cluster and metadata supplied with the installation media. and back up any critical data on the computers.

and do other Web server configuration. “Installing a front-end load balancer (Optional)” on page firewalls. Install a front-end Web server and the Web server “Installing a front-end Web server” on page 328 plug-in module. Installation tasks: Services tier Description For more information Install WebSphere Application Server Network “Installing IBM WebSphere Application Server Network Deployment on all the computers that will host the Deployment for a cluster installation” on page 324 services tier. "Administering IBM InfoSphere Information Server IBM verify that you can start and stop the deployment WebSphere Application Server services" in the manager process.websphere. Installation. Note: Start with a minimal cluster topology that contains a single node. see publib. (Optional) Install backup Web servers.doc/info/ihs/ihs/ tihs_startihs. Note: Do not run the InfoSphere Information Server installation program at this time. (Optional) To increase security. “Creating a deployment manager profile” on page 325 create a deployment manager profile that contains the deployment manager process. expand the cluster. Do this configuration if you are preinstalling WebSphere Application Server or configuring an existing installation.com/ Then start the Web server. This profile will contain the node agent process and the managed server process that will be part of the cluster. Make sure that Administrative Security is disabled. Use the WebSphere Application Server administrative “Creating a cluster and cluster members for the console to create a cluster with one cluster member application server” on page 326 definition. and you are configuring a separate front-end HTTP server. Note: If you install WebSphere Application Server by using the InfoSphere Information Server installation program. 329 Make sure that you can start and stop the Web server. both the HTTP and HTTPS protocols are enabled in WebSphere Application Server. use the “Creating a custom profile” on page 326 Profile Management Tool to create a custom profile. Also install any required WebSphere Application Server fix packs and patches. These protocols are also enabled if you preinstall WebSphere Application Server but use the built-in HTTP server.html On the computer that hosts the deployment manager. Run the configurewebserver_name script to create a Web server definition in WebSphere Application Server. configure the WebSphere “Configuring the front-end HTTP server for HTTPS” on Application Server front-end Web server to accept secure page 155 HTTP (HTTPS) calls. Services tier installation task list Table 42.ibm. and Configuration Guide .ihs. For IBM HTTP Server. After the installation procedure is complete. and other architectural components. 108 Planning.ibm. Then start the process and verify that it Administration Guide is running. infocenter/wasinfo/v7r0/topic/ com. On the computer that hosts the managed node. Run the installation program when you configure the services tier. This installation includes the deployment manager system and all computers that will host a managed node in the cluster. On the computer that hosts the deployment manager.boulder. 2b. load balancers.

3. In the HTTP Port field. choose Services only. In the HTTP Port field. c. In the installation program. Using a supported web browser on a Windows computer. repeat these steps for each server engine. verify "Administering IBM InfoSphere Information Server IBM that you can start and stop the managed node and node WebSphere Application Server services" in the agent that you created. accept all defaults. Installation tasks: Services tier (continued) Description For more information On the computer that hosts the managed node. run the following command to start the installation program: . f. 2c. d. choose Use an existing WebSphere Application Server installation. Then start the process and verify Administration Guide that it is running. In the Database Management System Selection page. Complete the rest of the installation steps. follow the steps in the following task list. (Optional) Click Use Secure Sockets Layer (SSL) for HTTP communication. From the is-suite directory on the installation media./setup command displays. Engine tier installation task list To configure your engine tier. choose the Deployment Manager profile. In the WebSphere Application Server Profile page. In the Application Server page. 4. Chapter 4. open the URL that the . type the port number of the front-end HTTP dispatcher. Verify that it does not have global security on. b. Planning Step 4: Determining your installation strategy 109 . Note: If you are creating a topology with more than one server engine. specify the metadata repository tier connection and database information. specify the URL of the front-end HTTP dispatcher for the WebSphere Application Server cluster. e./setup -verbose 2. In the Database Connection page. Run the installation program on the computer where the “Running the installation program (clustered WebSphere Application Server deployment manager is installation)” on page 330 installed: 1. type the HTTP dispatcher port number on which secure HTTP (HTTPS) has previously been configured. In the Tier Selection page.Table 42. except these items: a. choose Use existing database management system installation. In the WebSphere Application Server Cluster Information page.

Installation. configurations. Go to the documentation for your high-availability cluster management software. The installation program uses the locale and encoding information of the computer to determine whether it can provide language support. Create an administrator account for the InfoSphere “Setting up administrator and owner accounts” on page Information Server engine. and set up the cluster management software. See “Defining and starting the resource group (System Automation for Multiplatforms example)” on page 306. Install a C++ compiler for job development. “Installing a C++ compiler for job development” on page 159 110 Planning. make sure that the locale and “Setting the locale for the target computer” on page 157 encoding are set correctly. Installation tasks: Engine tier Description For more information Acquire and install high-availability cluster management Go to the documentation for your high-availability software on both engine tier servers. and Configuration Guide . Log in to the account to 142 activate the password. Go to the documentation for your high-availability cluster management software. see the following topics: v Linux UNIX “Installing the high availability software (System Automation for Multiplatforms example)” on page 304 v Windows “Setting up the cluster (MSCS example)” on page 317 Set the service IP address. For non-English locales.Table 43. For example configurations. see the following topics: v Linux UNIX “Setting up the virtual IP address (System Automation for Multiplatforms example)” on page 305 v Windows “Setting up the virtual IP address (MSCS example)” on page 318 Linux UNIX Define and start a resource group. For example cluster.

For example configurations. Go to the documentation for your high-availability cluster management software. choose Engine only. (Optional) Click Use Secure Sockets Layer (SSL) for HTTP communication. open the URL that the . accept all defaults. follow the steps in the following task list. Installation tasks: Engine tier (continued) Description For more information Run the installation program: For example configurations. Enter the InfoSphere Information Server administrator account name and password. v In the High Availability Server Cluster Configuration page. enter the virtual host name that was created when the HA software was configured. In the Port field. Planning Step 4: Determining your installation strategy 111 .Table 43. In the Virtual host name field. In the installation program. type the HTTP dispatcher port number on which secure HTTP (HTTPS) has previously been configured. except: v In the Tier Selection page. v Whenever prompted for an installation directory. From the is-suite directory on the installation v Linux UNIX “Installing IBM InfoSphere media. 4. run the following command to start the Information Server in the cluster (System Automation installation program: for Multiplatforms example)” on page 309 . 5. type the port number of the front-end HTTP dispatcher./setup -verbose v Windows “Installing IBM InfoSphere Information 2. specify the URL of the front-end HTTP dispatcher for the WebSphere Application Server cluster. Note: If you are creating a topology with more than one client computer. see the following topics: v Linux UNIX “Setting up the high availability control scripts (System Automation for Multiplatforms example)” on page 309 v Windows “Setting up high availability control scripts (MSCS example)” on page 319 2d. Client tier installation task list To configure your client tier. repeat these steps for each client computer. In the Port field. 3. Using a supported web browser on a Windows Server in the cluster (MSCS example)” on page 318 computer. Complete the rest of the installation steps. click Server cluster configuration. specify a path on the shared storage device./setup command displays. Set up the resource agent scripts. v In the IBM InfoSphere Information Server Location page. see the following topics: 1. Chapter 4.

” on page 167 1.” on page 243 InfoSphere Information Server in an IBM WebSphere Application Server Network Deployment 6. choose Client only. the Tier Selection page does not display. set up explicit firewall exceptions Chapter 16. Installation tasks: Client tier Description For more information Run the installation program: Chapter 12.1 or later environment. (Optional) Configure Secure Sockets Layer (SSL): Chapter 17. Perform postinstallation configuration tasks After you run the InfoSphere Information Server installation program for each tier. (Optional) Manually configure secure HTTP (HTTPS) for “Manually configuring InfoSphere Information Server the client tier. 3. “Installing new software. accept all defaults. reroute” on page 342 v DB2 HADR installation: – “Configuring the HADR primary server” on page 348 – “Configuring the HADR standby server” on page 350 112 Planning. Windows (Optional) Configure the cluster to run as a “Configuring a cluster to run as a service (Windows)” on service. “Enablement of Secure Sockets Layer (SSL). v If the installation program did not configure HTTPS for a tier computer during InfoSphere Information Server installation. Postinstallation configuration tasks (all tiers) Description For more information Windows If necessary. When you install Information Server. components to use HTTPS” on page 234 4. 2. SSL for inbound RMI/IIOP communications is disabled by default. Note: If you are using the client-only installation media. “Configuring security for IBM InfoSphere v Enable SSL for inbound RMI/IIOP. Installation. manually configure HTTPS for that tier computer. perform these tasks: Table 45. The program installs the client tier only. page 333 DB2 clustered and HADR installations: Configure the v DB2 cluster installation: “Configuring automatic client primary and secondary servers. Complete the rest of the installation. In the installation program. except in the Tier Selection page.” for client-side executable files that require network on page 233 access. Double-click the setup icon to start the installation program. The program windows display in your default Web browser.Table 44. and Configuration Guide .

Create users and groups in the user registry. 5. Choose a user registry and configure it for InfoSphere Information Server. “Starting HADR” on page 353 Test the engine tier failover function. Chapter 4. 4. Assign project roles if required by the installed suite components. For example configurations. database address and port for IBM WebSphere Application Server” on page 342 v DB2 HADR installation: “Specifying the alternate database address and port for IBM WebSphere Application Server” on page 351 v Oracle RAC installation: “Connecting to an Oracle RAC configuration” on page 358 (Optional) Add additional WebSphere Application Server "Adding a new cluster member" in the IBM InfoSphere nodes or other components to the cluster.xml file.xml file to the front-end Web cluster configuration to the front-end Web server. v Configure InfoSphere Information Server agents for non-root administration. Optionally. DB2 HADR installation: Start HADR.” on page 243 Information Server. If you are using IBM HTTP Server. you can automatically propagate the file to your Web servers by using the WebSphere Application Server administrative console. Assign security roles to users and groups.Table 45. 3. see the following topics: v Linux UNIX “Testing the configuration (System Automation for Multiplatforms example)” on page 311 v Windows “Testing the configuration (MSCS example)” on page 319 Configure security within InfoSphere Information Server: Chapter 17. also: v ConfigureWebSphere Application Server for non-root administration. v Configure the Auditing service. Go to the documentation for your high-availability cluster management software. Configure InfoSphere Information Server engine security. Map credentials if necessary. Postinstallation configuration tasks (all tiers) (continued) Description For more information Configure WebSphere Application Server to work with v DB2 clustered installation: “Specifying the alternate the metadata repository tier cluster. run the server" in the Administration Guide WebSphere Application Server administrative console to generate the plugin-cfg. and then manually copy it to each Web server. “Configuring security for IBM InfoSphere 1. Information Server Administration Guide To communicate the WebSphere Application Server "Propagating the plugin-cfg. 2. Then restart the Web server. Planning Step 4: Determining your installation strategy 113 .

They plan to use the full suite of components for future data integration projects. also: v Configure the parallel processing environment. The company has existing WebSphere Application Server and IBM DB2 installations. and Configuration Guide . Optionally. ensure that InfoSphere DataStage users have the correct settings specified for localization. page 258 Configure IBM InfoSphere Metadata Workbench (if “Configuring IBM InfoSphere Metadata Workbench” on installed). “Configuring IBM InfoSphere FastTrack” on page 258 (Optional) Run the IBM Support Assistant Lite for See “Installation verification and troubleshooting” on InfoSphere Information Server tool to verify the page 197 installation. Test the IBM InfoSphere Information Services Director “Testing the IBM InfoSphere Information Services installation (if installed). Sample scenario D: Topology with clustered metadata repository tier and services tier Sample scenario D is a topology that includes IBM WebSphere Application Server clustering and IBM DB2 clustering for high availability. v Test the installation. This topology also allows for 114 Planning. page 258 Configure IBM InfoSphere FastTrack (if installed). The large number of concurrent users requires a clustered WebSphere Application Server topology that permits almost no downtime. They recently purchased IBM InfoSphere Information Server. They are each managed within different support groups within the company IT department. 2. Configure access to ODBC data sources. Each group understands how to provide high availability solutions for the component under their supervision. Postinstallation configuration tasks (all tiers) (continued) Description For more information Configure IBM InfoSphere DataStage and IBM “Configuring IBM InfoSphere DataStage and IBM InfoSphere QualityStage (if installed): InfoSphere QualityStage” on page 245 1. “Configuring IBM InfoSphere Information Analyzer” on page 256 Configure IBM InfoSphere Business Glossary (if “Configuring IBM InfoSphere Business Glossary” on installed). Installation. If you installed globalization support (NLS). A large company uses both IBM WebSphere Application Server Network Deployment (ND) and DB2 for other applications.Table 45. tune the server engine. 3. Windows For systems that have large numbers of simultaneously connected users or large numbers of simultaneously running jobs. v Configure the InfoSphere QualityStage Match Designer. Director installation” on page 256 Configure InfoSphere Information Analyzer (if installed). v Migrate jobs that you created in an earlier version of InfoSphere DataStage to the current version. v Set up the application server to run SQA or investigation reports.

future expansion to accommodate additional capacity. Chapter 4. Planning Step 4: Determining your installation strategy 115 . For the servers. Sample scenario D topology The following tables describe the installation tasks for this scenario. The engine tier will be configured in an active-passive server cluster topology. 64-bit Red Hat Enterprise Linux 5 Advanced Platform will be used on an AMD CPU or processor. The following diagram illustrates the topology that they will build. the passive node will be used as a parallel engine node while the primary node is active. The cluster management software will be IBM Tivoli System Automation for Multiplatforms. The WebSphere Application Server group plans to create a WebSphere Application Server cluster for InfoSphere Information Server. For the clients. Client tier Client workstations HTTP clients EJB clients Backup load Load balancer balancer Web Web server 1 server 2 FIREWALL Services tier Cluster Analysis WebSphere database Application WebSphere WebSphere Server Application Application DB2 Deployment Server Server Node 1 DB Manager Node 2 Engine tier Metadata repository tier Active Passive Metadata Metadata Computer Computer Repository Repository computer computer HA mgt sw HA mgt sw (standby) (active) HA mgt sw HA mgt sw SAN DB2 DBMS DB2 DBMS DB2 DB Figure 47. To increase processing throughput. existing Microsoft Windows XP workstations will be used. The DB2 group will provide clustering of the metadata repository database and IBM InfoSphere Information Analyzer database to minimize downtime.

On all tier computers. Obtain the InfoSphere Information Server software and any applicable fix packs. IBM DB2 will be preinstalled and preconfigured. Obtain the installation software. and Configuration Guide . Planning and building the topology To plan and build the installation topology. and open TCP ports for InfoSphere Information Server across any applicable firewalls. Plan the volume groups and file systems on which you are installing InfoSphere Information Server. Table 46. Determine your database installation strategy. Scenario D: Planning and building the topology Task User action Review the system requirements. Verify that you have sufficient storage space in your file systems. verify name resolution. Uncompress the software onto each tier computer. Since the database cluster must be operational before the InfoSphere Information Server installation program runs. Modify kernel parameters and user limits. Determine whether to preinstall IBM WebSphere Since the application server cluster must be operational Application Server. Update the kernel parameters and user limits on all tier servers. and back up critical data on the computers. Plan volume groups and file systems. Prepare each tier computer to run the InfoSphere Information Server installation program. Review Secure Sockets Layer (SSL) configuration tasks. program runs. non-clustered DB2 installation. Prepare to run the installation program. SSL will be enabled in this configuration. WebSphere Application Server will be preinstalled and preconfigured. or preconfigure an existing before the InfoSphere Information Server installation installation of WebSphere Application Server. The metadata repository database and InfoSphere Information Analyzer analysis database will run in a clustered DB2 installation. complete the following tasks. Review the system requirements. take the following actions to prepare the metadata repository tier computers for the databases: 116 Planning. Verify the network and open ports. The IBM InfoSphere QualityStage Match Designer database will run in a separate. Installing and configuring the metadata repository tier After reviewing the system requirements. Installation.

3. QualityStage Match Designer database. memory. configure Tivoli System servers. Scenario D: Metadata repository tier preinstallation tasks Planning task User action Install the servers.Table 47. and activate the resource group. isolated network to carry a heartbeat signal for the HA software. Define the service (virtual) IP address and host name. and preconfigure the metadata repository cluster. Create the automation policy by using relationship definitions. Installing and configuring the services tier After reviewing the system requirements. Inform Tivoli System Automation for Multiplatforms that the network adapters on the nodes are appropriate and equivalent for the service IP address. create To configure the metadata repository database in the the cluster. Install Tivoli System Automation for Multiplatforms on both servers. These servers will support the metadata repository database and analysis database in a nonpartitioned topology. Set up two servers with identical internal storage. Install the database system for the IBM InfoSphere On the dedicated server. 2. install the DB2 database system. and the database is created by using the scripts. installation media. and a separate. Create a network tiebreaker. network. and storage device. Designate one server as "primary" and the other as "standby". Install high availability (HA) software on the DB2 cluster On the two DB2 cluster servers. Automation for Multiplatforms to monitor the health of the servers and to manage failover: 1. Install the database system on the cluster servers. 4. Do not run the InfoSphere Information Server installation program because the database system is preinstalled. take the following actions to create a clustered topology of WebSphere Application Server for the InfoSphere Information Server services tier: Chapter 4. Note: Do not run the InfoSphere Information Server installation program on the metadata repository tier computer. Create identical users and user groups on each server. Install a storage device and configure it so it is shared by both nodes in the cluster. and processing power. Define the resource group. Set up a separate server for the non-clustered DB2 instance that will support the IBM InfoSphere QualityStage Match Designer database and IBM InfoSphere Information Analyzer analysis database. Planning Step 4: Determining your installation strategy 117 . Configure a high-speed network between the servers. run the scripts that are supplied with the database in the cluster.

For IBM HTTP Server.Table 48. Create a Deployment Manager profile. This profile will contain the node agent process and the managed server process that will be part of the cluster. Scenario D: Services tier preinstallation tasks Preinstallation task User action Install the servers and network. Create a cluster and cluster members. As a front end to the cluster. set up two additional servers to host the cluster. create a deployment manager profile named Dmgr01 that contains the deployment manager process. reconfigure the load balancer to accommodate the change and balance the loads on the Web servers. for example. On the computer that hosts the deployment manager.ihs.html 118 Planning. Install WebSphere Application Server Network Deployment on all the computers that will host the services tier. use the Profile Management Tool to create a custom profile named Custom01. Install a front-end Web server. On the computer that hosts the managed node.boulder. refer to the IBM Load Balancer documentation.ibm.doc/info/ihs/ihs/ tihs_startihs. (Optional) Install a front-end load balancer. Make sure that Administrative Security is disabled. Use the WebSphere Application Server administrative console to create a cluster with one cluster member definition.websphere. refer to the IBM HTTP Server documentation. Configure the front-end Web server for HTTPS. For management of HTTP sessions in the cluster environment. Enable IBM HTTP Server to accept secure HTTP (HTTPS) calls. Also install any required WebSphere Application Server fix packs and patches. Because InfoSphere Information Server must have dedicated nodes within a WebSphere Application Server cluster. For information about installing IBM Load Balancer. For information about installing IBM HTTP Server. and do other Web server configuration. This installation includes the deployment manager system and all computers that will host a managed node in the cluster. If you modify the Web server configuration. to add or remove a Web server. Create a custom profile. Configure the load balancer to balance the loads on the downstream Web servers. Install IBM Load Balancer on two separate computers. infocenter/wasinfo/v7r0/topic/ com. and Configuration Guide .com/ Then start the Web server. Make sure that you can start and stop the Web server. Installation. Install IBM HTTP Server on two separate computers. One computer serves as backup for the other. Install WebSphere Application Server.ibm. set up an IP sprayer with backup servers. One computer serves as backup for the other. Run the configurewebserver_name script to create a Web server definition in WebSphere Application Server. see publib. HTTP session memory-to-memory replication will be used.

Set up the servers with redundant connections to two separate high-speed networks. and the node agents are started on all nodes. Tivoli System Automation for Multiplatforms will be used.Table 48. Then start the process and verify that it is running. run the installation program as described in “Running the installation program for Scenario D” on page 207. Create an /opt/IBM directory on each server and mount the storage device on both servers. Scenario D: Services tier preinstallation tasks (continued) Preinstallation task User action Verify the deployment manager. To manage high availability across the cluster. The heartbeat signal is to travel over a serial network. See "Administering IBM InfoSphere Information Server and IBM WebSphere Application Server services" in the Administration Guide. See "Administering IBM InfoSphere Information Server and IBM WebSphere Application Server services" in the Administration Guide. take the following actions to configure the engine tier: Table 49. Run the InfoSphere Information Server installation Use the WebSphere Application Server console to make program. Installing and configuring the engine tier The engine tier is to be configured in a two-server active-passive server cluster topology. Verify the managed node and node agent. On the computer that hosts the managed node. sure that the WebSphere Application Server Deployment Manager is running. Then start the process and verify that it is running. Scenario D: Engine tier preinstallation tasks Preinstallation task User action Configure the servers. After reviewing the system requirements. Make sure that the directory is shared and has the correct permissions. Chapter 4. On the computer that hosts the deployment manager. On the computer that hosts the deployment manager. networks. The application server processes on the nodes must be stopped. verify that you can start and stop the deployment manager process. verify that you can start and stop the managed node and node agent that you created. Planning Step 4: Determining your installation strategy 119 . Verify that it does not have global security on. Make sure that the IBM DB2 cluster is running. and storage device.

120 Planning. Scenario D: Engine tier preinstallation tasks (continued) Preinstallation task User action Install high availability (HA) software. tier. and install it in its default location. and monitor the servers. configure the system as described in the following table. Postinstallation tasks After installing all InfoSphere Information Server tiers. Review the system requirements to choose a supported C++ compiler for job development. Manually configure InfoSphere Information Server Manually configure secure HTTP (HTTPS) for the client components to use HTTPS. 3. Globalization (NLS) support will be enabled. Create the automation policy by using relationship definitions. Scenario D: Client tier preinstallation tasks Preinstallation task User action Run the InfoSphere Information Server installation Run the installation program for the client tier as program. Create the application resource. Implement the scripts to start. Set the locale for the target computer. Install a C++ compiler for job development. Define the service (virtual) IP address and host name. Configure Tivoli System Automation for Multiplatforms to monitor the health of the servers and to manage failover: 1. described in “Running the installation program for Scenario D” on page 207. Create identical users and user groups on each server. Inform Tivoli System Automation for Multiplatforms that the network adapters on the nodes are appropriate and equivalent for the service IP address. Installation. Set up the resource agent scripts. and Configuration Guide . Create an administrator account for the InfoSphere Information Server engine. 2. stop. Run the InfoSphere Information Server installation Run the installation program for the engine tier as program. Log in to the account to activate the password. Ensure that the locale and encoding are set correctly on both engine tier servers. complete the following tasks for each client workstation: Table 50. Install Tivoli System Automation for Multiplatforms on both servers. Installing the client tier After reviewing the system requirements. and activate the resource group. Define the resource group. Set up administrator and component owner accounts. Create a network tiebreaker. 4.Table 49. described in “Running the installation program for Scenario D” on page 207.

See "Administering WebSphere Application Server clusters" in the IBM InfoSphere Information Server Administration Guide. Planning Step 4: Determining your installation strategy 121 . Configure automatic client reroute to switch between the primary and secondary servers. v Install Pluggable Authentication Modules (PAM) on the engine tier computers. Configure access to ODBC data sources. Configure the primary and secondary servers. Ensure that IBM InfoSphere DataStage users have the The InfoSphere Information Server engine will use the correct settings specified for localization. Test the engine tier failover function.xml file if necessary. and then manually copy it to each Web server. v Within new InfoSphere Information Server installations.Table 51. v Enable SSL for inbound RMI/IIOP. When you install InfoSphere Information Server in an IBM WebSphere Application Server Network Deployment 6. No credential mapping is required. Add other WebSphere Application Server cluster Add additional WebSphere Application Server nodes or members. v Use the InfoSphere Information Server Web console to set up the engine tier to use the LDAP user registry. See "Adding a new cluster member" in the IBM InfoSphere Information Server Administration Guide. v Use the InfoSphere Information Server console to assign security roles to the users and groups. Chapter 4. v Manually configure the metadata repository/services tier computer for HTTPS. To communicate the cluster configuration to the front-end Web server. other components to the cluster. Secure Sockets Layer (SSL) is disabled by default. Set up WebSphere Application Server to communicate To cause WebSphere Application Server to communicate with the DB2 cluster.xml the file. Scenario D: Postinstallation tasks Task User action Enable Secure Sockets Layer (SSL). v Use the WebSphere Application Server Administrative Console to configure the system to use the LDAP user registry. run the WebSphere Application Server administrative console to specify an alternate database address and port. v Use LDAP administration tools to create InfoSphere DataStage users and groups within the registry. An external Lightweight Directory Access Protocol (LDAP) user registry will be used. SSL for inbound RMI/IIOP communications is disabled by default. Configure the ODBC drivers to access ODBC data sources.1 or later environment. Propagate the plugin. with the DB2 cluster instead of a single node. default locale settings that are inherited by the operating system users. run the WebSphere Application Server administrative console to generate plugin-cfg. the program did not prompt the user to enable HTTPS. Reenable SSL to maximize system security. Since WebSphere Application Server was installed by the InfoSphere Information Server installation program. No action is necessary. Simulate active server failures and network failures and observe the results. Configure security.

v Set environment variables for the parallel engine. Scenario D: Postinstallation tasks (continued) Task User action Configure the parallel processing environment. v Configure connectivity to source databases. v Configure the parallel engine to run the remote shell (rsh) or the Secure Shell (ssh) without a password. When you first install IBM InfoSphere Information Server. Assign roles to users and administrators. v Define the Data Source Name (DSN) to the analysis database and source databases. associate imported metadata with the project. v Create a project. v Define the Data Source Name (DSN) to the analysis database and source databases. and configure settings. v Set up security for the project. Also update the /etc/magic file. v Configure viewing permissions. and Configuration Guide . Configure IBM InfoSphere Business Glossary.Table 51. and configure settings. Adding product modules to an existing installation To add product modules to an existing installation. v Stop and restart the InfoSphere Information Server engine. Complete the following tasks: v Assign security roles to glossary users. v Create a project. associate imported metadata with the project. (Optional) Run the IBM Support Assistant Lite for See “Installation verification and troubleshooting” on InfoSphere Information Server tool to verify the page 197 installation. and the paging space for the parallel engine. 122 Planning. v Set the maximum number of processes for parallel jobs. v Configure general settings. you run the installation program on all tier computers. v Import metadata into the metadata repository. Configure the IBM InfoSphere QualityStage Match Do the following tasks: Designer. use the installation program to install the product module components on one or more tiers. Complete the following tasks: v Verify credentials. v Copy the parallel engine components to the target computer. the program installs the product modules that you select. Configure IBM InfoSphere Metadata Workbench. Configure IBM InfoSphere Information Analyzer. Configure IBM InfoSphere FastTrack. v Set up security for the project. v Verify credentials. During the initial installation. Create administrator and user IDs. The components reside on all the tiers. and also installs a framework of components that all product modules use. v Set user privileges to run parallel jobs. v Import metadata into the metadata repository. Installation.

Also use the tool if you are entitled to an additional edition or trade up to a different edition. Chapter 4. make sure that you have an up-to-date backup of all computers in the installation. depending on the product modules that you select. However. you run the installation program again. you might not have to run the installation program for all tiers. Refer to the IBM InfoSphere Information Server Administration Guide. you do not use the InfoSphere Information Server installation program to add them. To install additional product modules. Product modules and the tiers on which you must run the installation program Tier computers on which to run the Product module installation program IBM InfoSphere FastTrack Services. Planning Step 4: Determining your installation strategy 123 . See the IBM InfoSphere Information Server Administration Guide. All others All tier computers Before you add product modules to an existing installation. If you acquire entitlements for additional IBM InfoSphere DataStage editions or feature packs after initial installation.Note: If you preinstall the database system for the metadata repository tier and configure the databases within the database system by using the scripts that are supplied with the installation media. The following table lists product modules and indicates the tier computers on which you must run the installation program. Client IBM InfoSphere Business Glossary Services Anywhere (requires InfoSphere Business Glossary). Not all product modules have components on all tiers. Engine IBM InfoSphere Business Glossary Services. you do not run the installation program on the metadata repository tier computers. Table 52. The client is installed separately. Instead. Client IBM InfoSphere Metadata Workbench Services. enable them by using the LicensingServiceAdmin tool.

124 Planning. Installation. and Configuration Guide .

prepare each target computer for the installation. 2010 125 .Part 2. 2005. © Copyright IBM Corp. Preparing the tier computers Before you run the IBM InfoSphere Information Server installation program.

and Configuration Guide .126 Planning. Installation.

Computer preparation road maps Follow these road maps to prepare each tier computer for IBM InfoSphere Information Server installation. configure the databases when v “Using a database system other than you run the InfoSphere Information Server DB2” on page 152 installation program. © Copyright IBM Corp.Chapter 5. follow these steps to configure the metadata repository tier. configure the v “Preparing an existing DB2 database databases within DB2 by using scripts. instead follow the procedures in Chapter 24. If you preinstalled another database system. accounts” on page 142 If you decide to preinstall DB2 or another Database system documentation. “Metadata repository tier clustering for high availability. configure the databases by using scripts. determine the database system or page 61 systems to install for the analysis databases v “Determining the database installation and how to install them. method” on page 63 decide whether to use existing installations.” on page 3 Determine the database system to install for v “Determining your database topology” on your metadata repository and how you are page 61 installing it (or whether to use an existing v “Determining the database installation installation). Table 53. “Verifying the network and opening ports” on page 133 Linux UNIX Modify kernel “Modifying kernel parameters and user parameters and user limits. IBM DB2 database system” on page 147 If you preinstalled DB2.” on page 131 packs. 2010 127 . Preparation road map for the metadata repository tier computer If you are creating a metadata repository tier without a clustered database system installation. Verify the network and open ports. Note: If you are using a clustered database system setup. install the DB2 database system. UNIX)” on page 137 Set up administrator and component owner “Setting up administrator and owner accounts. or the metadata repository database system. “Planning Step 1: Reviewing system requirements and release notes. Uncompress the software onto each tier computer. Chapter 1. method” on page 63 If installing IBM InfoSphere Information v “Determining your database topology” on Analyzer. 2005. limits (Linux. For the supported database system. see “Preinstalling the database system now. Alternatively. system” on page 148 Alternatively. Metadata repository tier computer preparation checklist (non-clustered installation) Metadata repository tier preparation step Procedure Review the system requirements. v “Sizing the analysis databases” on page 65 Obtain the IBM InfoSphere Information Chapter 6.” on page 337. “Obtaining IBM InfoSphere Server software and any applicable fix Information Server software.

If you are creating a WebSphere Application Server cluster. Note: If you install WebSphere Application Server by using the InfoSphere Information Server installation program. Chapter 1. follow these steps to configure the engine tier. Table 54. Obtain the InfoSphere Information Server Chapter 6. Services tier computer preparation checklist (non-clustered installation) Services tier computer preparation step Procedure Review the system requirements. both the HTTP and HTTPS protocols are enabled in WebSphere Application Server. and you are configuring a separate front-end HTTP server. and Configuration Guide . Server” on page 153 Preconfigure an existing WebSphere “Configuring an existing WebSphere Application Server installation if necessary. 128 Planning.” on page 323. configure the “Configuring the front-end HTTP server for WebSphere Application Server front-end HTTPS” on page 155 Web server to accept secure HTTP (HTTPS) calls. or Application Server” on page 66 preconfigure an existing WebSphere Application Server installation. accounts” on page 142 Preinstall WebSphere Application Server if “Preinstalling WebSphere Application necessary. UNIX)” on page 137 Set up administrator and component owner “Setting up administrator and owner accounts. Linux UNIX Modify kernel “Modifying kernel parameters and user parameters and user limits. If you are creating a configuration with more than one server engine. limits (Linux.” on page 131 Uncompress the software onto each tier computer.Preparation road map for the services tier computer If you are creating a services tier without a clustered IBM WebSphere Application Server installation. follow these steps to configure the services tier. Installation. Application Server installation (non-clustered installation)” on page 154 (Optional) To increase security. “Obtaining IBM InfoSphere software and any applicable fix packs. These protocols are also enabled if you preinstall WebSphere Application Server but use the built-in HTTP server. “Planning Step 1: Reviewing system requirements and release notes. repeat these steps for each server engine. Preparation road map for the engine tier computers If you are creating an engine tier without high-availability (HA) server clustering. Do this configuration if you are preinstalling WebSphere Application Server or configuring an existing installation.” on page 3 Determine if you need to preinstall “Determining how to install WebSphere WebSphere Application Server. instead follow the procedures in Chapter 23. “WebSphere Application Server clustering for high availability and scalability. Information Server software.

confirm that the current code page is supported. UNIX)” on page 137 Linux UNIX If you are not “Setting the locale for the target computer” installing in English.” on page 299. or if you are enabling on page 157 globalization (NLS) support. Client tier computer preparation checklist Client tier computer preparation step Procedure Review the system requirements. Chapter 1. Table 55. change to a supported code page. and IBM InfoSphere Business Glossary Anywhere do not require an engine tier. “Planning Step 1: Reviewing system requirements and release notes. Uncompress the software onto each tier computer.” on page 131 packs. Uncompress the software onto each tier computer. Set up administrator and component owner “Setting up administrator and owner accounts. accounts” on page 142 Install C++ compiler for job development. “Obtaining IBM InfoSphere Server software and any applicable fix Information Server software.” on page 3 Obtain the IBM InfoSphere Information Chapter 6. IBM InfoSphere Business Glossary. Chapter 5. Not all product modules require an engine tier. “Planning Step 1: Reviewing system requirements and release notes.” on page 3 Obtain the IBM InfoSphere Information Chapter 6. “Installing a C++ compiler for job development” on page 159 Preparation road map for the client tier computers Follow these steps to prepare each client tier workstation computer. Engine tier computer preparation checklist (non-HA) Engine tier computer preparation step Procedure Review the system requirements. “Creating a two-server active-passive high availability configuration.” on page 131 packs. Verify the network and open ports. “Verifying the network and opening ports” on page 133 Linux UNIX Modify kernel “Modifying kernel parameters and user parameters and user limits. limits (Linux. If it is not supported. see Chapter 22. Computer preparation road maps 129 . Table 56. For information about creating a highly available engine tier. Chapter 1. IBM InfoSphere FastTrack. “Obtaining IBM InfoSphere Server software and any applicable fix Information Server software.

and Configuration Guide . Installation.130 Planning.

com/infocenter/iisinfsv/v8r5/topic/ com.Chapter 6. About this task The installation media for installing InfoSphere Information Server is available either as physical CDs or as downloadable installation image files from Passport Advantage®.ibm.trblsh. Obtaining IBM InfoSphere Information Server software Obtain InfoSphere Information Server software and applicable fix packs. See http://www.doc/topics/ts_fixcentral.wss?uid=swg21443006 to determine the image files that are appropriate for your operating systems and configurations. do not use the Microsoft Windows uncompression utility to uncompress the files. 2010 131 . uncompress the installation image files onto each tier computer.html. 2. © Copyright IBM Corp.im. 2005.swg. 3. Use another standard uncompression utility. If you do not have CDs.boulder. download the installation image files from Passport Advantage. Fix packs are available as downloadable installation image files from Fix Central.ibm. If you obtained InfoSphere Information Server in the form of physical CDs. Windows To avoid corrupting the files in the image. Procedure 1.ibm. Download any applicable fix packs from Fix Central. See publib.iis. check that you have all of the installation disks.sup. If you downloaded installation image files.com/support/docview. 4.

132 Planning, Installation, and Configuration Guide

Chapter 7. Preparation steps for all tier computers
Complete the following preparation steps for each computer in your installation.

Verifying the network and opening ports
Before you install IBM InfoSphere Information Server, make sure that your
network has sufficient connectivity for high data volumes.

About this task

For performance reasons, do not install InfoSphere Information Server in a wide
area network (WAN) configuration because of the data exchanges that are required.
Clients can work over a WAN if the latency is low. When the network latency
increases, it has a detrimental effect on the clients. If the WAN has a higher latency,
you can use the clients with Microsoft Windows Remote Desktop.

Procedure

To assess your network:
1. Ensure that a TCP/IP network is used for all communications in the
installation.
2. Set up the name resolution.
a. Verify that the computers in the installation can resolve all the other
computers by both the short and long name (fully qualified domain name),
for example mycomputer.mydomain.com and mycomputer.
b. Verify that both the short and long host names resolve to the same IP
address.
c. Ensure that the host name, localhost, resolves to 127.0.0.1. Specifically,
verify that you can resolve the IP addresses for both short and long host
names of the following nodes:
Metadata repository
On the computer where the metadata repository tier is installed
Services
On the computer where the services tier is installed
On the computer where the engine tier is installed
On the computer where the client tier is installed
Engine
On the computer where the engine tier is installed
On the computer where the services tier is installed
On the computer where the client tier is installed
d. Ensure that the localhost host name and the computer host name are not
both mapped to the IP address 127.0.0.1. Map only localhost to 127.0.0.1.
Ensure that there is no entry that maps localhost to the IP address of the
local computer. This example shows how these entries are configured in the
/etc/hosts file:
127.0.0.1 localhost.localdomain localhost
xx.xx.xx.xx longhostname shorthostname

© Copyright IBM Corp. 2005, 2010 133

localdomain
The domain name
xx.xx.xx.xx
The unique IP address for the computer
longhostname shorthostname
The long and short names for the computer
3. Ensure that you install the metadata repository and engine tiers in the same
network segment.
4. Open and make TCP ports available through firewalls for InfoSphere
Information Server and the application server. The following tables identify the
TCP ports that must be available for each tier:
v Port numbers for the metadata repository tier
v Port numbers for the services tier
v Port numbers for the engine tier
Table 57. Port numbers for the metadata repository tier
Component Default port numbers Tiers that use the port
IBM DB2 database for the metadata 50000 Services
repository (default database)
IBM DB2 database for the analysis 50000 Services, engine, client
database (default database)
Oracle database for the metadata 1521 Services
repository (if used)
Oracle database for the analysis 1521 Services, engine, client
database (if used)
Microsoft SQL Server database for 1433 Services
the metadata repository (if used)
Microsoft SQL Server database for 1433 Services, engine, client
the analysis database (if used)

Table 58. Port numbers for the services tier
Default port numbers for Default port numbers for
Component stand-alone configuration cluster configuration Tiers that use the port
DHTML reports server 16581 (DHTML reports server Client
functionality is not
supported in clustered
configurations.)
InfoSphere Information WC_defaulthost (9080) Firewall between the client Services, engine, client
Server Web-based clients and dispatcher (if any):
usually 80. This value varies
depending on the
configuration of the
front-end dispatcher.

Firewall between dispatcher
and cluster members (if
any): WC_defaulthost of all
cluster members (for
example, 9080, 9081, and so
on).

134 Planning, Installation, and Configuration Guide

Table 58. Port numbers for the services tier (continued)
Default port numbers for Default port numbers for
Component stand-alone configuration cluster configuration Tiers that use the port
InfoSphere Information WC_defaulthost_secure Firewall between the client Client
Server Web-based clients (9443) and dispatcher (if any):
(HTTPS) usually 443. This value If HTTPS is configured, the
varies depending on the services tier and engine tier
configuration of the also use this port.
front-end dispatcher.

Firewall between the
dispatcher and cluster
members (if any):
WC_defaulthost_secure of
all cluster members (for
example, 9443, 9444, and so
on)
IBM WebSphere WC_adminhost (9060) WC_adminhost (9060) Client
Application Server
administrative console
(redirects to HTTPS)
IBM WebSphere WC_adminhost_secure WC_adminhost_secure Client
Application Server (9043) (9043)
administrative console
(HTTPS)
InfoSphere Information BOOTSTRAP_ADDRESS BOOTSTRAP_ADDRESS of Services, engine, client
Server services (2809) all cluster members (9810,
(RMI/IIOP) 9811, and so on)
ORB_LISTENER_ADDRESS
(9100) ORB_LISTENER_ADDRESS
of all node agents (9100,
SAS_SSL_SERVERAUTH_ 9101, and so on)
LISTENER_ADDRESS
(9401) SAS_SSL_SERVERAUTH_
LISTENER_ADDRESS,
CSIV2_SSL_ CSIV2_SSL_SERVERAUTH_
MUTUALAUTH_ LISTENER_ADDRESS,
LISTENER_ADDRESS CSIV2_SSL_
(9402) MUTUALAUTH_
LISTENER_ADDRESS
CSIV2_SSL_SERVERAUTH_ of all cluster members:
LISTENER_ADDRESS (9410, 9411, 9412),
(9403) (9411, 9414, 9415),
and so on

Chapter 7. Preparation steps for all tier computers 135

Table 58. Port numbers for the services tier (continued)
Default port numbers for Default port numbers for
Component stand-alone configuration cluster configuration Tiers that use the port
IBM InfoSphere SIB_ENDPOINT_ADDRESS SIB_ENDPOINT_ADDRESS Client
Information Services (7276) of all cluster members
Director services with JMS (7277, 7278, and so on)
bindings SIB_ENDPOINT_SECURE_
ADDRESS (7286) SIB_ENDPOINT_SECURE_
ADDRESS of all cluster
SIB_MQ_ENDPOINT_ members
ADDRESS (5558) (7287, 7288, and so on)

SIB_MQ_ENDPOINT_ SIB_MQ_ENDPOINT_
SECURE_ADDRESS (5578) ADDRESS of all cluster
members
(5559, 5560, and so on)

SIB_MQ_ENDPOINT_
SECURE_ADDRESS of all
cluster members
(5579, 5580, and so on)

Important: IBM WebSphere Application Server Network Deployment does not
support deployment of firewalls between components within a cell (for
example, between the dmgr and nodes).
Table 59. Port numbers for the engine tier
Component Default port numbers Tiers that use the port
InfoSphere Information Server ASB agent 31531, and a random port Services
number greater than 1024

Instead of using a random port
number, you can fix this to a
specific port by specifying
agent.objectport=# in the
C:\IBM\InformationServer\
ASBNode\conf\agent.properties
file after you complete the
installation. After designating a
specific port, restart the logging
agent and the ASB agent so that
the change takes effect.
InfoSphere Information Server logging agent 31533 Engine
IBM InfoSphere DataStage and QualityStage DSRPC (31538) Engine, client
Administrator services
Parallel job monitors 13400 (port 1) and 13401 (port 2) Engine

Access to port 1 is required only
from the conductor node. Access
to port 2 is required from the
conductor node and the node
where the InfoSphere DataStage
and QualityStage Administrator
engine is installed, if that node is
different from the conductor
node.

136 Planning, Installation, and Configuration Guide

Table 59. Port numbers for the engine tier (continued)
Component Default port numbers Tiers that use the port
Parallel engine APT_PM_STARTUP_PORT Engine
(multiple ports, uses a port
number of 10240 or greater)
Parallel engine remote process startup 22514 Engine
(rsh/ssh, multiple nodes only)
Parallel engine (multiple nodes only) APT_PLAYER_CONNECTION_ Engine
PORT (multiple ports, uses a
port number of 11000 or
greater)

5. For connectivity to data sources, see the vendor-supplied documentation for
additional port assignments.

Modifying kernel parameters and user limits (Linux, UNIX)
For Linux and UNIX installations, modify the kernel parameters and user limits
and restart the computer before you start the installation program.

The kernel parameter and user limit requirements are minimum requirements for
IBM InfoSphere Information Server. The optimal value for each parameter might be
higher depending on the topology of your installation and the operational data
load. Additional kernel parameter and user limit changes might be required. When
more than one value is provided for your configuration, use the largest minimum
value.

All changes must be made by a trained system administrator. Make a backup copy
of the kernel parameters and user limits before you modify them. After you
modify the kernel parameters and user limits with the suggested values, restart the
computer, and then install InfoSphere Information Server.

Minimum kernel parameters

The following sections describe the minimum kernel parameter requirements for
each tier:
Metadata repository tier
“Minimum kernel parameters for DB2 Database for Linux, UNIX, and
Windows (metadata repository tier)” on page 138
Engine and services tiers
v AIX “Minimum AIX kernel parameters (engine and services tiers)”
on page 139
v HPUX “Minimum HP-UX kernel parameters (engine and services
tiers)” on page 139
v Linux “Minimum Linux kernel parameters (engine and services
tiers)” on page 140
v Solaris “Minimum Solaris kernel parameters (engine and services
tiers)” on page 140
You can find additional system tuning information in the IBM WebSphere
Application Server documentation:

Chapter 7. Preparation steps for all tier computers 137

v WebSphere Application Server, Version 6.1 Information Center: Preparing
the operating system for product installation: publib.boulder.ibm.com/
infocenter/wasinfo/v6r1/topic/com.ibm.websphere.base.doc/info/aes/
ae/tins_prepare.html
v WebSphere Application Server, Version 7.0 Information Center: Preparing
the operating system for product installation: publib.boulder.ibm.com/
infocenter/wasinfo/v7r0/topic/
com.ibm.websphere.installation.base.doc/info/aes/ae/tins_prepare.html

Minimum kernel parameters for DB2 Database for Linux, UNIX,
and Windows (metadata repository tier)

The minimum metadata repository kernel parameter requirements apply only to
IBM DB2 database installations. Before you install IBM DB2 as part of InfoSphere
Information Server, ensure that your computer meets the following minimum
kernel parameter requirements for DB2:
v AIX For IBM AIX®, the default kernel parameter values are sufficient.
v HPUX For HP-UX or Solaris, run the db2osconf utility to suggest
Solaris
appropriate kernel parameter values for your system. If you have not yet
installed the DB2 server, you can obtain the db2osconf utility from the
InfoSphere Information Server installation media in the db2osconf.tar file.
Unpack the tar file onto the computer and run it.
v Linux For Linux, see the minimum Linux kernel parameter values described
in the following table:
Table 60. Minimum Linux kernel parameters and user limits for the metadata repository tier
on DB2
Parameter Metadata repository tier
MSGMAX 65535
MSGMNB 65535
MSGMNI 1024
RANDOMIZE_VA_SPACE 0
SEMMNI 1024
SEMMNS 256000
SEMMSL 250
SEMOPM 32
SHMALL 8388608 or 90% of physical memory (whichever
value is greater)
SHMMAX 32-bit: 268435456
64-bit: 1073741824

Set this value to be equal to the amount of physical
memory on your computer.
SHMMNI 4096

When the DB2 kernel requirements are different from the InfoSphere Information
Server kernel parameter requirements, use the largest minimum value. If you use a
different database system for the metadata repository, consult the product
documentation for that database system to find information about kernel
parameter requirements.

138 Planning, Installation, and Configuration Guide

For more information about the kernel parameter requirements and user limits for
IBM DB2, see the following topics in the IBM DB2 Database for Linux, UNIX, and
Windows Information Center:
v Linux UNIX DB2 9.7: OS user limit requirements (Linux and UNIX):
publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/
com.ibm.db2.luw.qb.server.doc/doc/r0052441.html
v HPUX DB2 9.7: Kernel parameters (HP-UX): publib.boulder.ibm.com/
infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.qb.server.doc/doc/
t0006477.html
v Solaris DB2 9.7: Kernel parameters (Solaris): publib.boulder.ibm.com/
infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.qb.server.doc/doc/
t0006476.html
v Linux DB2 9.7: Kernel parameters (Linux): publib.boulder.ibm.com/
infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.qb.server.doc/doc/
t0008238.html

For DB2 9.5 kernel parameter requirements, see the IBM DB2 Database for Linux,
UNIX, and Windows Information Center at publib.boulder.ibm.com/infocenter/
db2luw/v9r5/.

For DB2 9.1 kernel parameter requirements, see the IBM DB2 Database for Linux,
UNIX, and Windows Information Center at publib.boulder.ibm.com/infocenter/
db2luw/v9/.

Minimum AIX kernel parameters (engine and services tiers)

The following table contains the minimum kernel parameters and user limits for
the installation:
Table 61. Minimum AIX kernel parameters and user limits (engine and services tiers)
Parameter Engine and services tiers
SHMMAX 536870912
SHMMNI 2000
SHMSEG 200
MAXUPROC 1000 or unlimited
NOFILES 10240

Minimum HP-UX kernel parameters (engine and services tiers)

The following table contains the minimum kernel parameters and user limits for
the installation:
Table 62. Minimum HP-UX kernel parameters and user limits (engine and services tiers)
Parameter Engine and services tiers
MAXFILES 8000
MSGMAP 32768
MSGMAX 65535
MSGMNB 65535 (single profile)
131070 (more than one profile)
MSGMNI 50

Chapter 7. Preparation steps for all tier computers 139

Table 62. Minimum HP-UX kernel parameters and user limits (engine and services
tiers) (continued)
Parameter Engine and services tiers
MSGSEG 32767
MSGTQL 2046
NFILE 58145
NFLOCKS 3000
NPROC 4116
SEMMNI 2048
SEMMNS 16384
SEMMNU 1024
SHMMAX 307200000
SHMMNI 2000
SHMSEG 1024
MAXUPRC 1000 or unlimited
NOFILES 10240

Minimum Linux kernel parameters (engine and services tiers)

The following table contains the minimum kernel parameters and user limits for
the installation:
Table 63. Minimum Linux kernel parameters and user limits (engine and services tiers)
Parameter Engine and services tiers
MSGMAX 8192
MSGMNB 16384
MSGMNI No requirement
SEMMNI 1024
SEMMNS 128000
SEMMSL 250
SEMOPM 32
SHMALL 2511724800
SHMMAX 307200000
SHMMNI 2000
SHMSEG 200
nproc 1000 or unlimited
nofile 10240

Minimum Solaris kernel parameters (engine and services tiers)

On Solaris 10, modify the /etc/project file instead of the /etc/system file.

In the /etc/project file, each entry must be specified on the same line. In the
following example, the ⇒ character represents the continuation of the default
parameter line.

140 Planning, Installation, and Configuration Guide

system:0::::
user.root:1::::
noproject:2::::
default:3::::project.max-msg-ids=(priv,3584,deny);projec⇒
t.max-sem-ids=(priv,4096,deny);project.max-shm-ids=(priv⇒
,4096,deny);project.max-shm-memory=(priv,7682162688,deny)
group.staff:10::::
db2fenc1:100::db2fenc1::
db2inst1:101::db2inst1::
dasusr1:102::dasusr1::
dsadm:103::dsadm::

The following tables contain the minimum kernel parameters and user limits for
the installation.
Table 64. Minimum Solaris 10 kernel parameters and user limits (engine and services tiers)
Resource control name Engine and services tiers
process.max-msg-qbytes 16384 or use default operating system value
process.max-msg-messages No requirement
process.max-sem-ops 100 or use default operating system value
process.max-sem-nsems 1024
project.max-shm-memory 307200000
project.max-shm-ids 2000
project.max-msg-ids 1024
project.max-sem-ids 1024

Table 65. Minimum Solaris 9 kernel parameters and user limits (engine tier)
Parameter Engine and services tiers
MSGMAP 1026
MSGMAX 65535
MSGMNB 16384
MSGMNI 1024
SEMAEM 16384
SEMMAP 1026
SEMMNI 1024
SEMMNS 128000
SEMMNU 2048
SEMMSL 1024
SEMOPM 100
SEMUME 256
SEMVMX No requirement
SHMMAX 4294967295
SHMMIN No requirement
SHMMNI 2000
SHMSEG 1024
MAXUPRC 1000 or unlimited
NOFILES 10240

Chapter 7. Preparation steps for all tier computers 141

After the installation is complete. do not interfere with the installation program use of the accounts. v Windows A user account in the local Administrators group. Then specify each name and password when the installation program prompts you for that information. On the operating systems where you install InfoSphere Information Server. Minimum Solaris 9 kernel parameters and user limits (engine tier) (continued) Parameter Engine and services tiers rlim_fd_cur Greater than 8193 rlim_fd_max Greater than 8193 Setting up administrator and owner accounts Before installing IBM InfoSphere Information Server. you can change the InfoSphere Information Server setup to use LDAP. Procedure 1. Create the accounts as local operating system accounts. make sure that the user who installs InfoSphere Information Server can log in using these accounts: v Linux UNIX The root user account. The InfoSphere Information Server installation program cannot use the accounts if they are lightweight directory access protocol (LDAP) or Active Directory accounts. Linux UNIX On the operating systems where you install each engine tier. such as requiring a password change at the first login. When you create the accounts. Installation. Table 65. This account must be one of the following types: – A local account that is directly assigned to the Windows local Administrators group. 2. When you run the InfoSphere Information Server installation program. About this task Creating administrator and owner accounts before you install InfoSphere Information Server ensures that operating system policies. record the name and password for each user. create the required administrator and owner accounts. The user must log in using one of these accounts to install InfoSphere Information Server. specify the names and passwords of these accounts for the program. – A domain account that is directly assigned to the Windows local Administrators group. and Configuration Guide . 142 Planning. Before you begin Make sure that you are familiar with the naming restrictions described in “Naming restrictions for user IDs and passwords” on page 145. create the following additional accounts and record the passwords.

Table 66. 3. This account must have read/write/execute permission to the following directories: v The home directory for the DB2 instance owner (by default. On the operating system where you install the metadata repository. Accounts that you create for an engine tier (Linux. This account must be an account on the local operating system. create a separate user with the developer role. v Linux v Linux server user operating system UNIX dasusr1 UNIX dasadm1 account. UNIX only) Account description Default user name Primary group Secondary group Notes Linux UNIX dsadm dstage You customize this This user performs group to apply to your administrative tasks. Note: If your installation does not include an engine tier. Accounts that you create on the metadata repository tier Account description Default user name Primary group Secondary group Notes DB2 administration None DB2 database only. the path is /home/dasusr1) v /tmp v /var/tmp Linux UNIX db2inst1 db2iadm1 dasadm1 DB2 database only. operating system DB2 fenced user account Chapter 7. This account must have v Windows db2admin v Windows db2admns read/write/execute and Administrators permission to the following directories: v The home directory for the DB2 administration server user (by default. Preparation steps for all tier computers 143 . the path is /home/db2inst1) v /tmp v /var/tmp Linux UNIX db2fenc1 db2fadm1 None DB2 database only. Administrator for the security model. During installation time. To run jobs. you cannot specify a Lightweight Directory Access Protocol (LDAP) account as the engine administrator account. operating system DB2 instance owner account. create the following additional accounts and record the passwords. such as adding new InfoSphere Information projects and defining Server engine their properties. Table 67. you can skip this step.

The program does not create these accounts as local accounts. permissions might not be adequate to perform a successful installation. Linux UNIX The InfoSphere Information Server installation program must have root access. Some operating systems are set up to force a password change during the first login. and Configuration Guide . Log in to each account to confirm that it functions correctly. 6. If any directories are mounted from network file systems such as AFS. database uses the authentication for the operating system for connection requests. 5. DB2 database databases db2inst1 as the uses the authentication InfoSphere Information for the operating system. repository Important: Do not operating system specify db2admin or account. After installation. Instead. Installation. Verify permissions for all users including root. Information Analyzer: Important: Do not operating system owner of the analysis specify db2admin or account. Administrator accounts set up by the installation program Account description Default user name Administrator for IBM WebSphere Application Server wasadmin Administrator for InfoSphere Information Server isadmin Do not create these two administrator accounts as local operating system accounts. When you use db2inst1 as the the DB2 database for the metadata repository user repository. Analyzer database user name.Table 67. Root must have write permissions to the following directories: v /tmp v /var v /var/tmp v /usr/local/bin 4. Accounts that you create on the metadata repository tier (continued) Account description Default user name Primary group Secondary group Notes Owner of the metadata xmeta xmeta None DB2 database only. The installation program stores this account information in the internal InfoSphere Information Server user registry. a manual login is required to activate the accounts appropriately. specify the account names and passwords when the InfoSphere Information Server installation program prompts for this information. the DB2 name. Examples These sample UNIX commands create some of the user accounts and groups: /usr/sbin/groupadd db2iadm1 /usr/sbin/groupadd db2fadm1 /usr/sbin/groupadd dasadm1 144 Planning. you can modify the InfoSphere Information Server setup so it uses a local operating system user registry or lightweight directory access protocol (LDAP) user registry. IBM InfoSphere iauser iauser None DB2 database only. Therefore. Determine the names and passwords to use for the following administrator accounts: Table 68.

/usr/sbin/groupadd xmeta /usr/sbin/groupadd isuser /usr/sbin/groupadd dstage /usr/sbin/useradd -g db2iadm1 -d /opt/IBM/db2inst1 db2inst1 /usr/sbin/useradd -g db2fadm1 -d /opt/IBM/db2fenc1 db2fenc1 /usr/sbin/useradd -g dasadm1 -d /opt/IBM/dasusr1 dasusr1 /usr/sbin/useradd -g xmeta -d /home/xmeta xmeta /usr/sbin/useradd -g isuser -d /home/isuser isuser /usr/sbin/useradd -g dstage -d /opt/IBM/dsadm dsadm Run the passwd command to set the password for each account. Naming restrictions for user IDs and passwords Some restrictions apply to the names that you choose for user IDs and passwords. tabs. Internal user registry user IDs Only alphanumeric characters and the following characters are permitted: _ (underscore) .(hyphen) \ (backslash) = (equal sign) Chapter 7. All user IDs and passwords The following characters are not permitted: ! (exclamation point) : (colon) $ (dollar sign) % (percent sign) { (left brace) } (right brace) ' (single quotation mark) " (double quotation mark) (white space) \ (backslash) Leading or trailing white space. is removed by the installation program. and line continuation characters. Preparation steps for all tier computers 145 . Any existing user IDs and passwords cannot have leading or trailing white space characters as part of their definitions. such as spaces. These sample AIX commands create some of the user accounts and groups: /usr/bin/mkgroup -’a’ id=’202’ db2iadm1 /usr/bin/mkgroup -’a’ id=’203’ db2fadm1 /usr/bin/mkgroup -’a’ id=’204’ dasadm1 /usr/bin/mkgroup -’a’ id=’205’ xmeta /usr/bin/mkgroup -’a’ id=’206’ isuser /usr/bin/mkgroup -’a’ id=’207’ dstage /usr/bin/mkuser -d /opt/IBM/db2inst1 -g db2iadm1 db2inst1 /usr/bin/mkuser -d /opt/IBM/db2fenc1 -g db2fadm1 db2fenc1 /usr/bin/mkuser -d /opt/IBM/dasusr1 -g dasadm1 dasusr1 /usr/bin/mkuser -d /home/xmeta -g xmeta xmeta /usr/bin/mkuser -d /home/isuser -g isuser isuser /usr/bin/mkuser -d /opt/IBM/dsadm -g dstage dsadm Run the passwd command to set the password for each account.

These account names cannot begin with these characters: SQL SYS IBM v In addition. and Configuration Guide .) Linux and UNIX user names and passwords cannot start with a numeric digit. and instance names must be in lowercase letters. (period) IBM WebSphere Application Server administrator password The following characters are not permitted: v Space characters v ^ (caret) IBM DB2 database user names v You can use these characters in IDs if permitted by the operating system: A through Z 0 through 9 # (number sign) ! (exclamation point) % (percent sign) ( (opening parenthesis) ) (closing parenthesis) $ (dollar sign. Installation. v On UNIX. Must not be the first character. and DB2 administrator. v UNIX and Linux users. Character length limits v AIX operating system user IDs: 8 v WebSphere Application Server IDs: 60 v DB2 user IDs and passwords: – UNIX and Linux: 8 – Microsoft Windows: 30 146 Planning. these account names cannot use these words: USERS ADMINS GUESTS PUBLIC LOCAL Any SQL reserved word in the SQL reference for the database system v Names cannot include accented characters. . DB2 fenced user. groups. the DB2 database requires these user accounts: DB2 instance owner.

To preinstall Version 9.html.com/infocenter/db2luw/v9r5/index. Additional preparation steps for the metadata repository tier computer To prepare a computer for the metadata repository tier installation.db2. Obtain a DB2 database system installation package from IBM. UNIX.ibm.com/infocenter/db2luw/v9r7/index.doc/doc/r0000306. and Windows: publib. the DB2 database system installation packages are in the following directories: v Linux UNIX installable_image_directory/payloads/Shared/DB2/ payload v Windows installable_image_directory\payloads\Shared\DB2\payload 2.7 before you run the InfoSphere Information Server installation program.jsp v IBM DB2 Database.luw. Optional: If you are using DB2 diagnostics. About this task Preinstall the DB2 database system in the following situations: v To use a supported version of the DB2 database system other than 9.boulder.admin. run the following command to set the DB2 Database Monitor Heap size to 192 or greater: Note: The DB2 Database Monitor Heap is used for various database event monitors and snapshots.Chapter 8. Preinstalling the IBM DB2 database system Preinstall the DB2 database system if necessary before you run the IBM InfoSphere Information Server installation program. you can run the DB2 database system installation program that is included in the InfoSphere Information Server installation media. On the installation media.7 for Linux. UNIX.ibm.boulder. and Windows: publib.7 for Linux. Install the DB2 database system as described in the DB2 database system documentation: v IBM DB2 Database. db2 update dbm cfg using MON_HEAP_SZ 192 immediate Restart DB2 for changes to take effect.com/infocenter/db2luw/v9r7/topic/ com.7 with InfoSphere Information Server v To build a DB2 database cluster or high availability disaster recovery (HADR) architecture for high availability Procedure 1. Version 9.boulder.config. 2005.ibm.jsp 3. Version 9. 2010 147 . UNIX. complete these tasks in addition to the tasks that are common to all tier computers. See publib. © Copyright IBM Corp.5 for Linux. The IBM InfoSphere Information Server installation package includes installation packages for IBM DB2 Enterprise Server Edition. Version 9.ibm. These monitoring tools do not work under the default size setting. and Windows.

“Preparation steps for all tier computers. v Make sure that the database does not contain any user objects. See “Preparing an existing DB2 database system by using scripts” on page 149. v You must run the installation program locally on the computer where the DB2 instance is installed. See Chapter 24.” on page 337. and Configuration Guide . See the system requirements at www. or use the database creation scripts.wss?rs=14&uid=swg27016382. the computer must also be accessible to computers that host the client tier. do all tasks that are listed in Chapter 7. “Metadata repository tier clustering for high availability. Preparing an existing DB2 database system Instead of installing the IBM DB2 database system.ibm. What to do next Configure the databases within DB2. v For the analysis database for IBM InfoSphere Information Analyzer. Installation. v It must be located on a computer that is accessible by the computers where the services tier and engine tiers are installed. Use the InfoSphere Information Server installation program.com/support/docview. the database system must satisfy the following requirements: v It must be a supported version. If you cannot run the program locally on the target computer. you can use an existing installation of DB2. v If installing into a DB2 cluster. These changes affect all the databases in the DB2 instance: db2set DB2_INLIST_TO_NLJN=YES db2set DB2_USE_ALTERNATE_PAGE_CLEANING=ON db2set DB2_REDUCED_OPTIMIZATION=YES db2 update dbm cfg using MON_HEAP_SZ 192 immediate Before you proceed. set up the cluster and configure the databases within the cluster. v DB2 Fault Monitoring components must be enabled. Before you begin To configure the DB2 database system by using the InfoSphere Information Server. This type of environment and the fast communications manager (FCM) are not supported for use with InfoSphere Information Server. 148 Planning. use the installation scripts instead. v The existing installation cannot be set up as a partitioned database environment. The db2fmcd command must point to the actual executable location.” on page 133. Preparing an existing DB2 database system by using the installation program You can use the IBM InfoSphere Information Server to configure an existing IBM DB2 database system installation for InfoSphere Information Server. Then use the installation scripts to install the databases. Make sure that the path to the fault monitor (db2fmcd) is included in the /etc/inittab file. For example: fmc:234:respawn:/ul/IBM/db2/V9/bin/db2fmcd #DB2 Monitor Coordinator Attention: The InfoSphere Information Server installation program runs the following commands when it configures the DB2 database system.

v Linux UNIX In the IBM DB2 Instance User page. v Linux In the DB2 Fenced User Information page. See “Starting the installation program in graphical mode” on page 180.html. 3. v In the DB2 Administrator User Information page. 2. See publib. v In the Tier selection page. specify the name of the DB2 instance owner account that you created.luw.db2. These monitoring tools do not work under the default size setting. click Metadata repository. v In the Metadata Repository Configuration page. See “Setting up administrator and owner accounts” on page 142. Select the path to the database instance in the menu. Procedure 1. If you use DB2 diagnostics. and save the file: db2c_instanceName port/tcp instanceName is the DB2 instance name. specify the UNIX name of the DB2 fenced user account that you created.ibm. Verify that the following line appears in the file.com/infocenter/db2luw/v9r7/topic/ com. specify the name of the DB2 administrator server user account that you created. v In the Database Management System Selection page.doc/doc/r0000306. Open the services file. select the port number of the DB2 instance. In the Instance port number menu. The services file is located in one of the following directories: v Linux UNIX /etc v Windows %SystemRoot%\system32\drivers\etc\services Note: %SystemRoot% is the installation directory of the Windows operating system. specify the analysis database and owner information in the IBM InfoSphere Information Analyzer Repository Configuration page. add the line. db2 update dbm cfg using MON_HEAP_SZ 192 immediate Restart DB2 for changes to take effect.admin. Run the InfoSphere Information Server installation program on the target computer.boulder. For example: c:\windows. Make sure that the DB2 installation instance is defined in the services file a. Preparing an existing DB2 database system by using scripts You can scripts that are shipped with IBM InfoSphere Information Server to configure an existing IBM DB2 database system installation for InfoSphere Information Server. If the line does not appear in the file.config. b. run the following command to set the DB2 Database Monitor Heap size to 192 or greater: Note: The DB2 Database Monitor Heap is used for various database event monitors and snapshots. specify the metadata repository database information and database owner account information. v If you are installing InfoSphere Information Analyzer. click Use an existing DB2 instance on this computer.ibm. Chapter 8. port is the port number of the DB2 instance. Additional preparation steps for the metadata repository tier computer 149 .

v For the analysis database for IBM InfoSphere Information Analyzer.admin. “Preparation steps for all tier computers.boulder. v The existing installation cannot be set up as a partitioned database environment.db2.ibm. You run a provided script to create the database before you install IBM InfoSphere Information Server.wss?rs=14&uid=swg27016382. See Chapter 24. the computer must also be accessible to computers that host the client tier. About this task You can run a script to create a metadata repository or IBM InfoSphere Information Analyzer analysis database. For a DB2 installation.” on page 337. Before you proceed. db2 update dbm cfg using MON_HEAP_SZ 192 immediate Restart DB2 for changes to take effect. See publib. If installing into a DB2 cluster. use the scripts in the following situations: v You are configuring a DB2 cluster for the databases. set up the cluster and configure the databases within the cluster before running the scripts. “Metadata repository tier clustering for high availability.doc/doc/r0000306. Refer to the appropriate readme file in the DatabaseSupport directory of the InfoSphere Information Server installation media for more details on how to create the databases by using the scripts. 2. Create the databases by using the database creation scripts. Before you begin The DB2 database system must satisfy the following requirements: v It must be a supported version. 150 Planning.com/support/docview.config. “Metadata repository tier clustering for high availability. 3. Procedure 1. This type of environment and the fast communications manager (FCM) are not supported for use with InfoSphere Information Server.luw.com/infocenter/db2luw/v9r7/topic/ com. See the system requirements at www. v You cannot run the installation program locally on the target computer. See Chapter 24. If you use DB2 diagnostics.” on page 133.” on page 337. v Make sure that the database does not contain any user objects. run the following command to set the DB2 Database Monitor Heap size to 192 or greater: Note: The DB2 Database Monitor Heap is used for various database event monitors and snapshots.ibm. Using an IBM DB2 for z/OS database system for the databases You can use a DB2 for z/OS database as the metadata repository. Installation. These monitoring tools do not work under the default size setting. v You do not want to use the InfoSphere Information Server installation program to configure the database.html. and Configuration Guide . do all tasks that are listed in Chapter 7. v It must be located on a computer that is accessible by the computers where the services tier and engine tiers are installed.ibm.

com/support/docview. 2. which allows for name collisions on multiple databases. the computer must also be accessible to computers that host the client tier.” on page 133. the table namespace is defined only by the DB2 user ID. tables under the user ID might be overwritten and data might be destroyed. Note: It is not necessary to use different user IDs for analysis databases. Before you proceed.wss?rs=14&uid=swg27016382. If you choose to use the same DB2 for z/OS subsystem as the metadata repository for more than one InfoSphere Information Server installation. If you ignore the check failure when the database is not empty. After installation is complete. Do this bind action from the DB2 command prompt interface that is provided with the Linux operating system that is running on System z.Before you begin The DB2 database system must satisfy the following requirements: v It must be a supported version. This is a system-wide parameter and requires a database administrator to set it. Note: IBM InfoSphere Information Services Director deployment requires that the DB2 IDTHTOIN parameter be set to a value longer than the time required to deploy an application. For details on installing the z/OS Application Connectivity to DB2 for z/OS. Procedure 1. The InfoSphere Information Server installation program does not validate that other analysis databases exist for the DB2 user ID. Consequently.x for z/OS Application Programming Guide and Reference for Java.ibm. Chapter 8. v The existing installation cannot be set up as a partitioned database environment. see IBM DB2 Version 9. This type of environment and the fast communications manager (FCM) are not supported for use with InfoSphere Information Server. In DB2 for z/OS. v It must be located on a computer that is accessible by the computers where the services tier and engine tiers are installed. Set the DB2 DSNZPARM parameter IDTHTOIN (in the DSN6FAC macro) to 600 seconds before installing the services tier. Bind the DB2 Universal Driver JDBC packages before installing InfoSphere Information Server. Additional preparation steps for the metadata repository tier computer 151 . v Make sure that the database does not contain any user objects. The installation program checks prerequisites to determine if the database is empty. do all tasks that are listed in Chapter 7. Refer to the appropriate readme file in the DatabaseSupport directory of the InfoSphere Information Server installation media for more details on how to create a DB2 database for the metadata repository. the DB2 user ID that is used for the InfoSphere Information Server metadata repository must not be used for any other database. v For the analysis database for IBM InfoSphere Information Analyzer. you must use a different DB2 user ID for each. 4. “Preparation steps for all tier computers. Table names are created with generated tags and are very unlikely to collide even when multiple analysis databases are created under the same DB2 user ID. 3. See the system requirements at www. you can restore this parameter to its original value.

152 Planning. the computer must also be accessible to computers that host the client tier. v It must be located on a computer that is accessible by the computers where the services tier and engine tiers are installed. and Configuration Guide . See the system requirements at www. Installation. If this option is turned on. do all tasks that are listed in Chapter 7.” on page 133.Using a database system other than DB2 To prepare a database system other than IBM DB2 for IBM InfoSphere Information Server. Procedure Refer to the appropriate readme file in the DatabaseSupport directory of the InfoSphere Information Server installation media for more details on how to create the databases by using the database creation scripts. use scripts to create the metadata repository and analysis databases.wss?rs=14&uid=swg27016382.ibm.com/support/docview. Before you proceed. “Preparation steps for all tier computers. Before you begin The database system must satisfy the following requirements: v It must be a supported database system and version. turn it off before installing IBM InfoSphere Information Server. v For the analysis database for IBM InfoSphere Information Analyzer. v (Oracle database system) The Advanced Security option is not supported.

multiplatform.ibm.boulder.0. Additional preparation steps for the services tier computer To prepare a computer for the services tier installation. Run the IBM WebSphere Application Server installation program to install IBM WebSphere Application Server Network Deployment.1 and 7. For a cluster installation. see “Installing IBM WebSphere Application Server Network Deployment for a cluster installation” on page 324.html v For IBM WebSphere Application Server Network Deployment. Java SDK fix number.boulder.websphere. Version 7. Install any required fix pack and iFixes. About this task This task describes the installation of IBM WebSphere Application Server Network Deployment in a non-cluster (stand-alone) installation.installation. complete these tasks in addition to the tasks that are common to all tier computers. © Copyright IBM Corp.ibm.ibm. refer to the InfoSphere Information Server system requirements page: www.nd. you can run the WebSphere Application Server installation program that is included in the InfoSphere Information Server installation media. Version 7. To preinstall WebSphere Application Server. Version 7. You must install one of these versions. 2010 153 .ibm. Within the installation media. and iFixes that are required for your installed version of IBM WebSphere Application Server Network Deployment. To find the supported fix pack level. 2005.0: publib. Version 6.wss?rs=14&uid=swg27016382.Chapter 9.doc/info/ae/ae/ welc6topinstalling.0. Install IBM WebSphere Application Server Network Deployment on the InfoSphere Information Server services tier.com/ support/docview. Versions 6. See the WebSphere Application Server documentation for more information: v For IBM WebSphere Application Server Network Deployment. the WebSphere Application Server installation packages are in the following directories: v Linux UNIX installation_image_directory/payloads/Shared/WAS/ payload/WAS v Windows installation_image_directory/payloads\Shared\WAS/payload/WAS 2.1: publib.jsp?topic=/ com.html The IBM InfoSphere Information Server installation package includes installation packages for IBM WebSphere Application Server Network Deployment.0 before you run the InfoSphere Information Server installation program.jsp?topic=/ com.websphere.com/infocenter/wasinfo/v6r1/index.ibm.nd. Procedure 1. Preinstalling WebSphere Application Server IBM InfoSphere Information Server supports IBM WebSphere Application Server Network Deployment.doc/info/ae/ae/welc6topinstalling.com/infocenter/wasinfo/v7r0/index.

you can configure an existing installation to use with InfoSphere Information Server.nd.wss?rs=14&uid=swg27016382. and Configuration Guide .com/infocenter/wasinfo/v6r1/topic/ com. About this task The InfoSphere Information Server installation program enables security as part of its configuration.websphere.ibm. 2.boulder.html 154 Planning. If you do not have a supported version. 1.0: publib. v Linux UNIX /opt/IBM/WebSphere/AppServer64/bin/versionInfo.doc/info/ae/ae/tpro_profiles. Installation.ibm. InfoSphere Information Server does not support WebSphere Application Server Extended Deployment (XD) or the WebSphere Application Server base version.ibm.com/infocenter/wasinfo/v7r0/topic/ com.sh /opt/IBM/WebSphere/AppServer64/java/bin/java -fullversion v Windows C:\IBM\WebSphere\AppServer\bin\versionInfo. For information about creating a profile. Configuring an existing WebSphere Application Server installation (non-clustered installation) Instead of installing a new IBM WebSphere Application Server instance for IBM InfoSphere Information Server. At a command prompt.websphere.1: publib. Before you begin The WebSphere Application Server installation must satisfy the following requirements: v It must be on the same computer where you install the services tier.com/support/docview. Create a new application server profile with security disabled. Version 7.nd. Note: If you use the installation packages for IBM WebSphere Application Server Network Deployment. enter one of the following commands to verify that you have a supported version of WebSphere Application Server and the Java SDK.bat C:\IBM\WebSphere\AppServer\bin\java -fullversion Compare the values that are returned by these commands to the version numbers in the system requirements to determine if you have a supported version.doc/info/ae/ae/tpro_profiles. you do not need to install additional fix packs or iFixes.0 that is included in the installation package.boulder. See the system requirements at www.ibm.html v Version 7. see the WebSphere Application Server documentation: v Version 6. v It must be a supported version. Procedure Configure your WebSphere Application Server installation before you install InfoSphere Information Server.ibm. do not attempt to configure it for use with InfoSphere Information Server.

websphere.html What to do next When you run the installation program.ibm.Configuring the front-end HTTP server for HTTPS If you preinstall IBM WebSphere Application Server and install a separate front-end HTTP server before you run the IBM InfoSphere Information Server installation program.boulder.com/infocenter/wasinfo/v6r1/topic/ com. HTTPS adds greater security to your system. Additional preparation steps for the services tier computer 155 .nd.0: publib.com/infocenter/wasinfo/v7r0/topic/ com. click the Use Secure Sockets Layer (SSL) for HTTP communication check box if it appears within the installation program wizard. HTTP is used instead.websphere.html v Version 7.ibm.nd. HTTPS configuration is optional. Chapter 9.ibm. You might not need HTTPS if you have a strong firewall in place. but also requires more administrative work and can be error-prone.ibm. to enable WebSphere Application Server to accept HTTPS calls you must manually configure the HTTP server.doc/info/ae/ae/tsec_securecomm. If you do not configure HTTPS. carefully consider the benefits and drawbacks before enabling HTTPS.multiplatform.1: publib. After the installation. There is also a performance impact. both the HTTP and HTTPS protocols are enabled in WebSphere Application Server.doc/info/ae/ae/tsec_securecomm.boulder. follow the steps in “Manually configuring InfoSphere Information Server components to use HTTPS” on page 234 to configure HTTPS on any tier computers on which the installation program did not configure this protocol. Procedure Follow the instructions in the WebSphere Application Server documentation: v Version 6. These protocols are also enabled if you preinstall WebSphere Application Server but use the built-in HTTP server. About this task Note: If you install WebSphere Application Server by using the InfoSphere Information Server installation program. Therefore.multiplatform.

156 Planning. Installation. and Configuration Guide .

About this task When you install IBM InfoSphere Information Server with globalization (NLS) support enabled. Enter the following command to list all available locales: locale -a The locale names that are returned by locale and locale -a might be full locale names or alias locale names. If the target computer does not use a supported locale and encoding. For example. If you do not set the target computer to use a supported locale and encoding. Additional preparation steps for the engine tier computers To prepare a computer for an engine tier installation. For languages other than English. Linux UNIX To set the locale in Linux or UNIX: 1. the installation program configures InfoSphere Information Server for the English language. An alias locale name does not include the encoding name. Setting the locale for the target computer The installation program uses the locale and encoding information of the target computer to determine whether it can provide language support. For UNIX installations. you can set the encoding to UTF-8 to support a wide variety of languages. To ensure that server jobs run and compile correctly. 2010 157 . in the last component.utf8 contains the encoding name. change the LANG value to a combination that is available on your computer and that © Copyright IBM Corp. 2. see the Microsoft documentation. utf8. you can run the following command: LANG=alias_name locale charmap where alias_name is the alias name. you must ensure that the locale and encoding are set correctly. A full locale name contains the encoding name in the last component. the following command returns utf8 on a system where the locale ja_JP uses the utf8 encoding: LANG=ja_JP locale charmap 4. 2005. Enter the following command to determine the current locale: locale 3. complete these tasks in addition to the tasks that are common to all tier computers.Chapter 10. the installation program chooses the globalization configuration that is the most suitable for the locale and encoding of the target computer. For example. Procedure Windows For information about setting the locale in Windows. To determine the encoding. Log in to the computer. make sure that the target computer uses a supported locale and encoding. the full locale name ja_JP. including globalization support.

Supported encodings for InfoSphere Information Server Globalization Supported Supported Supported Supported configuration Windows Linux HP-UX Supported UNIX Language name encodings encodings encodings AIX encodings encodings Chinese DS-CHINESE. SIMPLIFIED GB18030. GBK. UTF-8 UTF-8 UTF-8 UTF-8 UTF-8 UTF8 German DS-GERMAN MS1252 ISO8859-1 ISO8859-1 ISO8859-1 ISO8859-1 German DS-GERMAN. Table 69. MS950 BIG5 BIG5 BIG5 BIG5 Traditional TRADITIONAL Chinese. run the export command with the following format: export LANG={locale. UTF-8 UTF-8 UTF-8 UTF-8 UTF-8 Traditional TRADITIONAL- UTF8 English DS-ENGLISH MS1252 ISO8859-1 ISO8859-1 ISO8859-1 ISO8859-1 English DS-ENGLISH.utf8 export LC_ALL=ja_JP. GB2312.utf8 Character encodings supported by IBM InfoSphere Information Server Verify that the operating system of the target computer uses a supported character encoding. is supported by IBM InfoSphere Information Server. GB2312. and Configuration Guide . GB2312.charmap} For example. GB2312. UTF-8 UTF-8 UTF-8 UTF-8 UTF-8 SIMPLIFIED-UTF8 Chinese. the following commands change the locale to ja_JP and the encoding to UTF-8: export LANG=ja_JP. DS-CHINESE. UTF-8 UTF-8 UTF-8 UTF-8 UTF-8 UTF8 Japanese DS-JAPANESE MS932. MS936 EUC-CN. MS31J 158 Planning. GB18030. The following table lists the languages and encodings that are supported by InfoSphere Information Server on various operating systems. UTF-8 UTF-8 UTF-8 UTF-8 UTF-8 UTF8 French DS-FRENCH MS1252 ISO8859-1 ISO8859-1 ISO8859-1 ISO8859-1 French DS-FRENCH. GBK. IBMEUCCN IBMEUCCN IBMEUCCN Chinese DS-CHINESE. To ensure that server jobs run and compile correctly. Installation.charmap} export LC_ALL={locale. the operating system of the target computer must use an encoding that is supported by the globalization configuration that is used during installation. XEUCCN GB18030. EUC-CN. DS-CHINESE. To change the locale and encoding. GBK. EUC-CN. UTF-8 UTF-8 UTF-8 UTF-8 UTF-8 UTF8 Italian DS-ITALIAN MS1252 ISO8859-1 ISO8859-1 ISO8859-1 ISO8859-1 Italian DS-ITALIAN.

UTF-8 UTF-8 UTF-8 UTF-8 UTF-8 PORTUGUESE- BRAZILIAN-UTF8 Spanish DS-SPANISH MS1252 ISO8859-1 ISO8859-1 ISO8859-1 ISO8859-1 Spanish DS-SPANISH. IBM943. UTF-8 UTF-8 UTF-8 UTF-8 UTF-8 UTF8 Korean DS-KOREAN MS949 EUC. Not supported Not supported Not supported EUC supported IBM33722. PCK. For production environments. Additional preparation steps for the engine tier computers 159 . The job compilation process uses it to compile parallel jobs with transformer stages. PCK. PCK. IBM33722C. each developer must have a license at the time that the developer compiles the job with the Designer client. IBM932. For some compilers. Installing a C++ compiler for job development The computer where you will install the IBM InfoSphere Information Server engine must have a C++ compiler. SJIS SHIFT_JIS. IBM943. you do not need a C++ compiler.Table 69. Not EUC-JP. but some operating systems require additional C++ runtime libraries. SJIS IBM943. Install only one compiler on each engine for development environments. EUC. IBMEUCJP. IBM943C. IBM932. Supported encodings for InfoSphere Information Server (continued) Globalization Supported Supported Supported Supported configuration Windows Linux HP-UX Supported UNIX Language name encodings encodings encodings AIX encodings encodings Japanese DS-JAPANESE. IBM943C. SJIS SHIFT_JIS. UJIS. IBM932. MS1252 ISO8859-1 ISO8859-1 ISO8859-1 ISO8859-1 PORTUGUESE- BRAZILIAN Portuguese DS. EUC-KR EUC-KR KSC5601 KSC5601 Korean DS-KOREAN. the transform feature of the parallel canvas requires the compiler. UTF-8 UTF-8 UTF-8 UTF-8 UTF-8 UTF8 Portuguese DS. IBM943C. The parallel canvas requires that the compiler and SDK be installed in their default locations. XEUCJPOPEN Japanese DS-JAPANESE. To function correctly. PCK. SHIFT_JIS. UTF-8 UTF-8 UTF-8 UTF-8 UTF-8 UTF8 Thai DS-THAI PC874 TIS620 TIS620 TIS620 TIS620 Turkish DS-TURKISH MS1254 ISO8859-9 ISO8859-9 ISO8859-9 ISO8859-9 For more information. IBM943C. The maximum number of simultaneous processes that compile jobs determines the number of licenses. Chapter 10. buildop components. SJIS Japanese DS-JAPANESE. IBM932. see the IBM InfoSphere DataStage and QualityStage Globalization Guide. and some lookup stages. IBM943. SJIS SHIFT_JIS.

Installation. the compiler settings are preset. see the system requirements for your operating system: www. 160 Planning.wss?rs=14&uid=swg27016382. When InfoSphere Information Server is installed. However. for some compilers you might need to alter the settings after installation. and Configuration Guide . For the list of supported C++ compilers.com/support/docview.ibm.

which you can install during the IBM InfoSphere Information Server installation v Oracle database system v Microsoft SQL Server database system Database requirements The InfoSphere Information Server installation program does not create the Match Designer results database. IBM DB2 database system Configure the following settings: v Set Default Buffer Pool and Table Space Page Size to 32K. The Match Designer database can be hosted by the following database systems: v IBM DB2 database system. use a new or existing database that is dedicated to storing the results of match test passes. you must configure the database to receive double-byte data if the Match Designer processes Asian data. Configuration requirements by database Database Configuration requirements All databases Configure as an empty database. If you intend to develop match specifications. v Set Code Set to UTF-8. You create the database before or after the installation. 2010 161 . Preparing for the IBM InfoSphere QualityStage Match Designer database The IBM InfoSphere QualityStage Match Designer is a component of InfoSphere QualityStage that is used to design and test match specifications. You can create the database on a computer where the client or engine tier is installed or on any computer that is accessible to both of these tiers. © Copyright IBM Corp.Chapter 11. The following table lists the supported databases and describes the configuration requirements: Table 70. 2005. For example. Match specifications consist of match passes that identify duplicate entities in one or more files. as long as the database is configured and accessible when you use the Match Designer. Do not use the metadata repository or the analysis database to store these results. The Match Designer creates the table structure that it requires when it stores the match pass results in the database. You must configure the database to receive the type of data that is processed in the Match Designer.

keep in mind that most Match Designer input records will be preprocessed through an InfoSphere QualityStage Standardization Stage. This stage will add 500 bytes to a source record or 1000 bytes if the source record is double-byte. Review the factors described in Table 2. select the Enable N-CHAR Support option. When calculating frequency record volume. Table 70. consider whether the data values for the source columns that participate in your matches typically have high or low rates of duplication. you need to make some assumptions about the type and volume of matching that you will do. and Configuration Guide . v Set National Character Set to AL32UTF8. your frequency record count will be significantly less than your data record count. Installation. your frequency record count will be similar to your data record count. For example. Also. For data that has a high rate of duplication. use WE8ISO8859P1 for English and for Western European languages. For data that is highly unique. assume that VarChar columns contain maximum width values. use automatic storage management to allocate database space as needed. To estimate initial space requirements and plan for the appropriate hardware. Configuration requirements by database (continued) Database Configuration requirements Oracle database system Configure the following settings: v Set Character Set for the data being processed. Then use the factors in the following formula to estimate how many megabytes of space the Match Designer results database is likely to require.000. Database space requirements After you create the database.000 162 Planning. Microsoft SQL Server database system No special settings are required. (number of match specifications x (match size + (match size x 10%) + frequency size) x replication factor) / 1. Note: If you use the IBM Wire Protocol driver. Consider the following factors: v Estimated number of match specifications v Average number of match passes per match specification v Average number of input data records per match specification v Average number of bytes per input data record v Average number of input frequency records per match specification When you calculate the number of bytes in a Match Designer input record.

specification (used in the Match Size calculation) Data record length Data records define the Average number of bytes per content and format of match match specification input specification input. Frequency size (in bytes) Frequency size estimates the (Frequency record count per space requirement for the match) x 360 frequency component of a single match specification. Match size (in bytes) Match size aggregates the (Match pass count) x (data match pass and data record record count) x (data record count and length factors into length) the estimated space requirements for the data component of a single match specification. For frequency record count. Preparing for the IBM InfoSphere QualityStage Match Designer database 163 . Frequency record count Frequency records indicate Average number of how often a particular value frequency records per match appears in a particular specification column. expect to retain in your database Match pass count Match passes define the Average number of match column-level matching passes per match criteria applied during a specification (used in the single pass through match Match Size calculation) specification input. Chapter 11. data record (used in the Match Size calculation) When calculating data record length. consider high or low rates of duplication for the data values in source columns. Data record count Data records define the Average number of input content and format of match data records per match specification input. assume sizing scenarios that require the most space. Space requirement factors and calculations Factor Description Calculation Match specification count Match specifications define Approximate number of and test criteria for matching match specifications you data.Table 71.

v Unduplicate matches take use a factor of 1 input from one source. Table 71. Installation. 164 Planning. use a factor of 5 matches compare a record on the data source to a record on the reference source. v For one-to-one reference then group and match the matches. use a factor of 2 data. and Configuration Guide . v Many-to-one reference matches can match any reference source record with many data source records. v For many-to-one reference v One-to-one reference matches. Space requirement factors and calculations (continued) Factor Description Calculation Replication factor Replication factors account Select the replication factor for significant differences in for the match type you space requirements of expect to run most often: different match types: v For unduplicate matches.

2005. Installing IBM InfoSphere Information Server software You can create an installation of IBM InfoSphere Information Server or update an existing installation with a patch or fix pack. 2010 165 .Part 3. © Copyright IBM Corp.

Installation.166 Planning. and Configuration Guide .

5 tier.5 installation that includes IBM InfoSphere DataStage or other product modules. The installation program presents wizard pages for you to select options. you can add IBM InfoSphere FastTrack to an existing Version 8. When you have selected your options. As it performs the installation. Installing new software Use the IBM InfoSphere Information Server installation program to create an installation. If the check succeeds. Then the program performs a prerequisites check. if a target computer hosts a services tier instance. After you have planned your installation and prepared your computers. 2005. Instead. The installation program can run in either of two modes: Graphical mode In this mode. you can use the installation program to add product modules to the installation. It performs a prerequisites check. the program saves them to a response file on the target computer. If the check succeeds. Silent mode In this mode. the program installs the software. For example. 2010 167 . you can use the program to add an engine tier instance to that computer. the installation program runs within a standard Web browser. You can also use the installation program to add product modules or software tiers to an existing installation. © Copyright IBM Corp. Alternatively. either locally on the target computer or remotely. it can save the report to a text file or display results on the console. Creating an installation You can create an installation of IBM InfoSphere Information Server product modules and components by running the installation program. Do not use the InfoSphere Information Server installation program to add InfoSphere DataStage editions or feature packs after initial installation. Instead. the program installs the software. For example. Refer to the IBM InfoSphere Information Server Administration Guide. the installation program does not present a user interface. enable them by using the LicensingServiceAdmin tool. run the InfoSphere Information Server installation program to install InfoSphere Information Server product modules and components. The program can also install IBM DB2 and IBM WebSphere Application Server Network Deployment (ND) if your installation requires stand-alone configurations of these components. the installation program can set up InfoSphere Information Server to use preinstalled instances of these components. You can also use the installation program to add a software tier to a computer that is already hosting a Version 8.Chapter 12. or other supported database systems and application servers. After you install the suite. it reads settings from a response file.

Services. the installation program immediately adds them on the computer. IBM InfoSphere Business Glossary. See “Configuring your browser” on page 179. Installation. v If you chose Engine in the Tier Selection page but did not choose Services. 2. Run the installation program for this tier unless you have preinstalled a database system and configured the databases within it as described in “Using a database system other than DB2” on page 152. and IBM InfoSphere Business Glossary Anywhere do not require an engine tier. Prepare your computers as described in Part 2. install the Version 8. “Planning for the installation of IBM InfoSphere Information Server. Run the installation program for this tier unless you are only installing product modules that do not require an engine tier. Procedure Run the installation program on the computer as described in “Graphical mode” on page 180. 3. in the following order: 1.5 client tier before you install the earlier version clients on the computer. v Runs a short prerequisites check on the target computer. For client tier installations. IBM InfoSphere FastTrack. and Configuration Guide . 2. v Prompts you for the tier or tiers to install on the target computer.” on page 125. delete the user accounts manually from the computer. The installation program installs the tier components in the correct order on the computer. specify the host name and port number of the front-end HTTP dispatcher. Before you begin 1. v Prompts you for the installation location. 4. Perform the additional preparation steps that are described in “Preparing to run the installation program” on page 177. The installation program: v Prompts you to accept the license agreement. prompts you for the IBM InfoSphere Information Server location. “Preparing the tier computers. Use the directories that you determined during the installation preparation phase. The client tier installation can take place at any point in the sequence. 3. Make sure that your browser is configured correctly. 168 Planning.” on page 1. if you want to include multiple versions of the clients on the same computer. See “Planning volume groups and file systems” on page 67. You only need to run the installation program one time on each computer even if the computer is to host more than one tier. v Prompts you for the installation type. Metadata repository. Note: If you create operating system user accounts from the installation program. Engine. About this task Run the installation program on each tier computer. Select New installation. If you exit the installation program before you complete the installation. If your services tier is set up in a clustered IBM WebSphere Application Server implementation. Plan your installation as described in Part 1.

asks you if this install is a two-server active-passive high availability configuration. Installing new software 169 . specify the host name of the services tier computer and the port number for WebSphere Application Server (typically 9080). See “Determining how to install WebSphere Application Server” on page 66. Select the same set of product modules for each computer. Table 72.Prompts you for the application server installation location. See “Setting up administrator and owner accounts” on page 142. InfoSphere DataStage editions and optional features Installable item Features IBM InfoSphere DataStage v InfoSphere DataStage job features v Parallel canvas v Server canvas IBM InfoSphere DataStage Server v InfoSphere DataStage job features v Server canvas ™ IBM InfoSphere DataStage MVS Edition v InfoSphere DataStage job features v MVS (mainframe) canvas IBM InfoSphere DataStage Pack for SAS v SAS features IBM InfoSphere DataStage Balanced v InfoSphere DataStage balanced Optimization optimization features v Linux UNIX If you chose Services. or Engine in the Tier Selection page. – If you choose to install WebSphere Application Server: . Most installations do not use this option. v If you chose Services in the Tier Selection page. The table also lists the features that are included with each item. Otherwise. and if you are installing IBM InfoSphere DataStage. Use the information that you determined during the installation preparation phase. Select Use Secure Sockets Layer (SSL) for HTTP communication if the HTTP server is configured to allow HTTPS traffic only. or to configure an existing application server instance. v If you chose Services in the Tier Selection page: – Prompts you to choose either to install IBM WebSphere Application Server Network Deployment (ND) in a stand-alone configuration. prompts you to choose InfoSphere DataStage editions and optional features to install. you can still set up the client components to use HTTPS. If you do not select this option. Metadata repository. Chapter 12. or you want to configure InfoSphere Information Server to use an HTTPS-only connection. If you select this option. See “Active-passive topology” on page 28. If yes. Also enter the InfoSphere Information Server administrator user name and password. v Prompts you for the list of product modules to install. provide a port number that is configured for HTTPS. it prompts you to enter the preconfigured floating host name to share between the servers. The following table lists the InfoSphere DataStage editions and optional features that the InfoSphere Information Server installation program can install. Note: Select this option only if the HTTP port has been disabled in your WebSphere Application Server installation.

Prompts you for the DB2 database system installation directory. it installs InfoSphere Information Server on a WebSphere Application Server cluster. It is highly recommended that you start with a small cluster that has only one WebSphere Application Server deployment manager node and one WebSphere Application Server node for installation . you can alternately connect to a DB2 installation on a remote computer. If the installation program detects that the type of the selected profile is “dmgr”. – If you choose to configure an existing application server instance: . v If you chose Metadata repository or Services in the Tier Selection page: – Prompts you to choose whether to install the DB2 database system or configure an existing DB2 instance on the local computer for use. Installation.Prompts you for the application server administrator user name and password. Use the information that you determined during the installation preparation phase. .Prompts you for the application server administrator user name and password. You must have at least one profile available for installation. provide a port number that is configured for HTTPS. v If you chose Services or Engine in the Tier Selection page. the DB2 database system is installed in this directory. If you select this option. and Configuration Guide . . prompts you to specify whether or not to use Secure Sockets Layer (SSL) for HTTP communications. Select this option if the HTTP server is configured to allow HTTPS traffic only. If you choose to install the DB2 database system: . If you chose Services in the Tier Selection page. .If the selected profile is not a deployment manager profile. See “Setting up administrator and owner accounts” on page 142.Prompts you to specify an application server profile to use. In this case. allows you to define custom port assignments for WebSphere Application Server within the profile. Linux UNIX 170 Planning.If Customize WebSphere Application Server profile ports is selected. Use the information that you determined during the installation preparation phase. See “Setting up administrator and owner accounts” on page 142.Prompts you to specify the application server instance to use. If you are configuring an existing DB2 instance. prompts you for the InfoSphere Information Server administrator user name and password (if the information was not collected earlier). your cluster must have been properly configured so that you can restart all node agents and nodes properly. or another database system.If the application server profile is a WebSphere Application Server deployment manager. If you are installing the DB2 database system. . or you want to configure InfoSphere Information Server to use an HTTPS-only connection. the installation program prompts the user to provide an HTTP server host name and port number. See “Determining your database topology” on page 61. . See “Preparing an existing DB2 database system” on page 148 and “Using a database system other than DB2” on page 152. The profile you selected for installation must not have security settings on. You must have created the database within the database system before running the installation program. specify the location of the existing DB2 database system installation and the port number for connecting to the instance. .

If you choose to configure an existing database (local or remote. Also specify the database name. v If you chose Engine in the Tier Selection page: – Prompts you for the ports for the InfoSphere Information Server ASB agent (communication agent) and logging agent to use. If you did not create the DB2 administrator user account before starting the installation program. See “Setting up administrator and owner accounts” on page 142. Specify the user name that you created before starting the installation program. This user is the DB2 Administration Server (DAS) user. . The installation program creates the account. If you did not create the DB2 instance owner account before starting the installation program. instead click Create a user as an instance owner and specify the user information. Linux UNIX Prompts you for the DB2 fenced user. The ASB agent facilitates communication between tiers. prompts you for the metadata repository database owner account and database information. This option is not available if the user registry is LDAP or NIS. instance name. The installation program creates the account. The installation program creates the account. instead click Create a new user as a fenced user and specify the user information. This option is not available if the user registry is LDAP or NIS. See “Setting up administrator and owner accounts” on page 142. If you did not create the fenced user account before starting the installation program. Installing new software 171 . DB2 or other database system). Chapter 12. Prompts you for the DB2 instance owner. Specify the account information that you created before starting the installation program. Any fenced user-defined functions (UDFs) and stored procedures run under this user and group. host computer name and port. and metadata repository owner information. and location. Click Existing user and specify the DB2 instance owner name that you created before starting the installation program. the installation program creates the account. If you did not create the metadata repository database owner account before starting the installation program. This option is not available if the user registry is LDAP or NIS. Click Existing user and specify the DB2 fenced user name that you created before starting the installation program. Specify ports that are not used by other services. This option is not available if the user registry is Lightweight Directory Access Protocol (LDAP) or NIS.Prompts you for the DB2 administrator user.) Also specify a port number for the new instance. The default port settings work in most configurations. instead click Create the user as administrator user and specify the user information.Prompts you for the metadata repository owner information and database name. you are prompted for the database type. The logging agent logs events to the metadata repository database. The instance owner controls all the DB2 processes and owns all the file systems and devices that are used by the databases within the DB2 instance. Click Existing user and specify the user name that you created before starting the installation program. . . (See “Setting up administrator and owner accounts” on page 142. z/OS Also specify the database collection ID and tablespace name. The installation program creates the account. v If you chose Services in the Tier Selection page.

. instance name. and location. Also specify the database name. .5 connector stages. The default port settings work in most configurations.Prompts you for the TCP/IP ports for the IBM InfoSphere DataStage and QualityStage job monitor to use. which supersedes the IBM WebSphere MQ Plug-in. or IBM InfoSphere Information Analyzer: . You cannot change this option after installation. The performance of parallel jobs is not affected. . If you have existing jobs that use SAS. . instead click Create a user as the IBM InfoSphere DataStage administrator and specify the user information. change to a supported code page and restart the installation program. Select this option if you have existing jobs that depend on the plug-in. Linux UNIX Prompts you for the InfoSphere DataStage administrator. For new jobs. The code page that is currently configured on the target computer must be supported by InfoSphere Information Server. Specify the account information that you created before starting the installation program. If you want this installation to handle data in a non-English language. The installation program creates the account. . You access the job monitor through the IBM InfoSphere DataStage Director. install localization support. and you want to install another engine instance on the same computer. Some server jobs might run more slowly after you install globalization. v If you chose Services in the Tier Selection page and are installing IBM InfoSphere Information Analyzer. See “Setting the locale for the target computer” on page 157. If the code page is not supported. Specify ports that are not used by other services. If you did not create the user account before starting the installation program. Click Existing user and specify the InfoSphere DataStage administrator account name that you created before starting the installation program. Otherwise. you can restructure the jobs to use the Version 8.Prompts you to choose whether to install the IBM WebSphere MQ Plug-in. Linux UNIX Prompts you for InfoSphere Information Server engine instance tag information. enable this configuration and select the version of SAS that you want to configure. prompts you for the analysis database owner account and database information. and Configuration Guide .Prompts you to choose whether to install globalization support. Installation. The job monitor uses one port to request job information and the second port to report job information. See “Multiple instances of IBM InfoSphere Information Server” on page 22. The installation wizard defaults to creating a project called “dstage1”. You must create at least one project during installation. – If you are installing InfoSphere DataStage. IBM InfoSphere QualityStage. The job monitor provides snapshots of job performance. Specify two ports. you can use the IBM WebSphere MQ Connector. Linux UNIX Prompts you to choose whether to enable a legacy SAS configuration. Specify a tag if an installed instance of the InfoSphere Information Server engine exists on the target computer.Prompts you to specify InfoSphere DataStage projects to create. 172 Planning. .

Version 8. Make sure that your browser is configured correctly. If you did not create the analysis database owner account before starting the installation program.” on page 125. v (All tier installations) Saves a response file that contains the information that you specified in the installation wizard. “Planning for the installation of IBM InfoSphere Information Server. You can run the IBM Support Assistant Lite for InfoSphere Information Server tool to verify the installation. Do not use the IBM InfoSphere Information Server installation program to add IBM InfoSphere DataStage editions or feature packs after initial installation. configure the software as described in Part 4. 2. 3. Refer to the IBM InfoSphere Information Server Administration Guide. The following table lists product modules and indicates the tier computers on which you must run the installation program: Table 73.” on page 229. Do the preparation steps that are described in “Preparing to run the installation program” on page 177. See “Configuring your browser” on page 179.” on page 1. v (All tier installations) Runs a longer prerequisites check on the target computer. What to do next When the installation is successful for all computers. Product modules and the tiers on which you must run the installation program Tier computers on which to run the Product module installation program IBM InfoSphere FastTrack Services. The installation program creates the analysis database within DB2.5 installation by running the installation program. “Preparing the tier computers. Installing new software 173 . enable them by using the LicensingServiceAdmin tool. the installation program creates the account. Refer to “Installation verification and troubleshooting” on page 197 for more information. About this task Depending on the product modules that you select. Client Chapter 12. “Configuring the software after installation. If you start the process. You can skip tier computers that do not contain components for the product modules. Prepare your target computers as described in Part 2. the installation program installs the product module components on the target computer. Adding product modules to an installation You can add product modules to an existing IBM InfoSphere Information Server. you might not have to run the installation program for all tiers. Not all product modules have components on all tiers. v (All tier installations) Prompts you whether to begin the installation process. Instead. Plan your installation as described in Part 1. 4. Before you begin 1. You only need to run the installation program on the tier computers that contain components for the product modules.

The installation process for this product module is faster if InfoSphere DataStage or InfoSphere QualityStage is already installed. All others All tier computers The installation program only installs the appropriate software for the tiers on a computer. you do not run the installation program on the metadata repository tier computers. first run the installation program on the metadata repository tier computer. 2. You can run the installation program on all of the computers in your configuration. 174 Planning. Client. You only need to run the installation program one time on each computer even if the computer hosts more than one tier. Lastly. The client is installed separately. if the product modules you are installing require changes to this tier. and Configuration Guide . For this reason. if you add one of these product modules to a system on which the other product module is installed. Engine IBM InfoSphere Business Glossary Services. If the product modules you are installing require an engine tier installation. The installation program installs the tier components in the correct order on the computer. Services. Client IBM InfoSphere Business Glossary Services Anywhere (requires InfoSphere Business Glossary). to install IBM InfoSphere Information Analyzer. and the engine tier is not present. Installation. first install the engine tier as described in the procedure. You can run the installation program on the client tier computers at any point in the sequence. run the program on the engine tier. Table 73. Refer to the table to determine whether you need to run the installation program on the engine tier. the installation process runs faster. 4. v Many of these components are also shared by IBM InfoSphere Information Analyzer. Then run it on the services tier computer. if needed. Run the program on the computers in the following order: 1. Product modules and the tiers on which you must run the installation program (continued) Tier computers on which to run the Product module installation program IBM InfoSphere Metadata Workbench Services. If you preinstalled the database system for the metadata repository tier and configured the databases within the database system by using the scripts that are supplied with the installation media. Notes about specific product module addition tasks: v InfoSphere DataStage and IBM InfoSphere QualityStage share many components. For example. The installation program determines automatically which tiers exist on each computer and adds the appropriate components. All product module additions require changes to the services tier. and select the products to be installed each time. if the product modules you are installing require changes to this tier. The client tier installation can take place at any point in the sequence. 3. Engine. Metadata repository.

v Prompts you whether to begin the installation process.” For example. v Saves a response file that contains the information that you specified in the installation program. Make sure you have an up-to-date backup of your entire InfoSphere Information Server installation.” on page 229. 2. What to do next Configure the newly installed product modules as described in Part 4. If you disabled scheduled tasks or deployed applications before running the installation program. If you start the process. Installing new software 175 . v Detects the existing installation. first create an engine tier. Run the installation program on the computers as described in “Graphical mode” on page 180. You can run the IBM Support Assistant Lite for InfoSphere Information Server tool to verify the installation. v Runs a prerequisites check on the target computer. restart the tasks and reenable the applications. 4. “Planning for the installation of IBM InfoSphere Information Server. your installation does not have an engine tier. by running the installation program. the installation program installs the product module components on the target computer. v Prompts you for the product modules to install. Refer to “Installation verification and troubleshooting” on page 197 for more information. Select the InfoSphere Information Server installation directory. To add InfoSphere DataStage. 3. Select the same set of product modules for each tier computer. “Configuring the software after installation. Plan your installation as described in Part 1. See “Adding an additional software tier to a computer. Before you begin 1. Select the product modules that you want to install. if you installed only IBM InfoSphere FastTrack. The installation program: v Prompts you for the installation location. v Select Add products. v Prompts you for information that is specific to the product modules that you have selected. and prompts you to choose whether to add additional products or tiers. Chapter 12. install and configure the tier. If a required tier is not present. See the IBM InfoSphere Information Server Administration Guide. The components that the installation program installs are appropriate for the tiers that the computer hosts. Adding an additional software tier to a computer You can add a software tier to a computer that already hosts one or more tiers.” on page 1. Consult the table above to determine what software tiers must be present in your installation to install the product module. Repeat the process for each target computer. Procedure 1.

176 Planning. v Prompts you for information that is specific to the tiers that you have selected to install. You only need to run the installation program one time on each computer even if you are adding more than one tier. If you start the process. “Configuring the software after installation. the client tier and engine tier must share the same base directory (for example. restart the tasks and reenable the applications. 2. 4. v Detects the existing installation. Prepare your target computer as described in Part 2. the software installs the tier on the target computer. Select the InfoSphere Information Server installation directory. Do the preparation steps that are described in “Preparing to run the installation program” on page 177. See the IBM InfoSphere Information Server Administration Guide. install the Version 8. For client tier installations. v Saves a response file that contains the information that you specified in the installation wizard. 3. If you disabled scheduled tasks or deployed applications before running the installation program. v Runs a prerequisites check on the target computer. If you are installing a client tier on a computer where an engine tier is installed.” on page 125. v Prompts you whether to begin the installation process. The installation program: v Prompts you for the installation location. “Preparing the tier computers. Procedure 1. C:\IBM\InformationServer). About this task To add an additional software tier to a computer that already hosts one or more tiers. if you want to include multiple versions of the clients on the same computer. v Prompts you for the tier or tiers to install on the target computer. 2. Installation. Make sure that your browser is configured correctly.” on page 229. Tiers that are already installed are disabled in the window. run the installation program on the target computer. Run the installation program on the computer as described in “Graphical mode” on page 180. What to do next Configure the software as described in Part 4. Make sure you have an up-to-date backup of your entire IBM InfoSphere Information Server installation. The installation program installs the tiers in the correct order on the computer. See “Configuring your browser” on page 179. and Configuration Guide . v Select Add tiers.5 client tier before you install the earlier version clients on the computer. and prompts you to choose whether to add additional products or tiers.

“Planning Step 1: Reviewing system requirements and release notes.jvm_args: v Linux UNIX cp . If redirection is required. 3. The installation program writes required temporary files to a location defined by the environment variable %temp% (Windows) or TMP (Linux. 4.” on page 1. “Preparing the tier computers. /etc/inittab.jvm_args_debug . Edit . back up the following items: Linux UNIX Back up /etc/services. If you removed a previous installation of InfoSphere Information Server on the computer. 2.jvm_args_debug . Before you begin 1.” on page 3. 2.jvm_args b. copy the file . back up the existing InfoSphere Information Server components and critical data. Back up all critical data that is on the target computers. You can run the IBM Support Assistant Lite for InfoSphere Information Server tool to verify the installation. Installing new software 177 . Preparing to run the installation program Before you run the installation program to create an installation or add product modules or tiers. Also. Also back up critical data. Plan your installation as described in Part 1. See “Configuring your browser” on page 179. UNIX). and /etc/group.jvm_args: Chapter 12. Starting the installation program You can start the IBM InfoSphere Information Server installation program in graphical mode or silent mode. Prepare your target computers as described in Part 2.jvm_args v Windows copy . Review the system requirements and release notes as described in Chapter 1. Procedure Follow this procedure for each target computer: 1.” on page 125. If you are adding another IBM InfoSphere Information Server instance to a computer that already hosts an instance. Refer to “Installation verification and troubleshooting” on page 197 for more information. make sure that the browser is configured correctly. “Planning for the installation of IBM InfoSphere Information Server. /etc/passwd. make sure that the computers are ready for installation. See the IBM InfoSphere Information Server Administration Guide. 3. At the root of the installation package directory. You can redirect the temporary files to a different temporary directory. Windows Back up the Microsoft Windows registry and the C:\Windows\ System32\drivers\etc directory. do the following steps before you run the installation program: a. If you plan to run the installation program in graphical mode. reboot the computer before continuing.jvm_args_debug to .

Linux IBM WebSphere Application Server is not compatible with Security Enhanced Linux (SELinux). 8. 1) Remove the contents of the file. Disable SELinux or set it to permissive mode before installing InfoSphere Information Server. For information about setting the locale: v Windows See your Microsoft documentation. 178 Planning. If necessary. For more information about how to disable SELinux. see “Character encodings supported by IBM InfoSphere Information Server” on page 158. the product modules are configured to use English and globalization support is enabled. ensure that the computer where you install the services tier has network connectivity.io. copy the contents of the installation media to a local file system or optical drive. 10. Linux UNIX The Linux Pluggable Authentication Modules (PAM) must be installed on the target computer.com/support/docview. Windows The installation program requires the Windows Script Engine to operate. 13. Run the installation program from this location. Preserve these files for troubleshooting and verification purposes. and Configuration Guide . 2) Add the following line: -Djava. To test your Windows Script Engine installation. if MKS Toolkit is installed Windows on the computer. To determine if your locale is supported. To ensure uninterrupted connectivity to the installation media.ibm. see www. turn it off before installing InfoSphere Information Server. remove any existing installations of Metabrokers and bridges from the target computer before you run the InfoSphere Information Server installation program. For a client tier or engine tier installation. After installation is finished. Windows If you are installing Metabrokers and bridges. see “"There is no script engine for file extension '. Installation. For more information about these and other software requirements for these components. Also install the correct Microsoft XML Core Services (MSXML) Service Pack.tmpdir=installation_program_tempdir 3) Save the file. the installation program uses the system locale setting. If you plan to use an existing database on a different computer as your metadata repository. If the system locale setting is not supported.com/support/docview.ibm.js'" message appears during installation” on page 400. uninstall it and reboot the computer before you run the InfoSphere Information Server installation program. 7. For details on supported versions. v Linux UNIXSee “Setting the locale for the target computer” on page 157. 9. In a non-English environment. (Oracle database system) The Advanced Security option is not supported. go to the system requirements at www. 5.wss?rs=14 &uid=swg27016382. see the Linux documentation. If this option is turned on. 12.wss?rs=14 &uid=swg27018060 11. do not delete the installation log files that are in the temporary directory. 6. set the locale for the computer.

17.ibm. 15. WindowsMake sure that the following directories are in your system path. and configure it so that the installation program runs correctly. For details.com/support/docview. Then log in as root. Add additional nodes as business needs dictate post-installation.wss?rs=14&uid=swg27016382. Microsoft Internet Explorer Make sure that the security zone for the computer allows the installation program to run: 1. scheduled tasks. Installing new software 179 . and restart node agents. log in as the non-root user and stop the processes. Windows When you run the installation program in graphical mode. Ensure that the system PATH does not include paths to Java executables. 20. From Microsoft Internet Explorer. v Verify that you can stop and start the Web server. v Make sure that JavaScript is enabled. 16. If the WebSphere Application Server processes or node agents are currently running under a non-root user. All browsers v Verify that you have a supported browser. scheduled reports. v Verify that you can start and stop the cluster. Also." You can safely ignore the message and continue the installation. sufficient file descriptor resources must be allocated to the processes by using the ulimit command.14.. go to the system requirements at www. v For optimal results. Locate your browser type in the following sections. Then start WebSphere Application Server as root. Chapter 12. install into a cluster that has one Deployment Manager and one WebSphere Application Server node. Remove any paths to Java executables. and enabled IBM InfoSphere Information Services Director applications before updating an existing installation with a patch or fix pack. in the Tools menu. For an installation that involves WebSphere Application Server clustering: v All management processes including the node agents must be started before the installation. See “Running the installation program (clustered installation)” on page 330.. See the IBM InfoSphere Information Server Administration Guide. Configuring your browser Make sure that the browser is configured so that the installation program runs in graphical mode. Disable firewall software and antivirus software before starting the installation. a message might be displayed in the browser that reads "The publisher cannot be verified. Disable all scheduled jobs. change the ownership of the WebSphere Application Server installation directory and profile directory to be root. 19. and exist on the target computer: v %SystemRoot%\ v %SystemRoot%\system32 v %SystemRoot%\system32\wbem 18. This message does not indicate a security risk when it is displayed during InfoSphere Information Server installation. select Internet Options.

Installation. Make sure that your browser is configured correctly. After you enter your settings in the wizard pages. Enable Enable JavaScript. 4. Click OK.” on page 125. Mozilla Firefox Make sure that images load automatically and that JavaScript is enabled: 1. Graphical mode In graphical mode. To run the installation program in graphical mode. 3. 3. See “Configuring your browser” on page 179. 2. Before you begin 1. type http://hostname where hostname is the host name of the computer on which the install program will run. the installation program automatically launches the default Web browser on the local computer to display the graphical interface. 4. 4. 5. 5. “Planning for the installation of IBM InfoSphere Information Server. The Options window displays. Alternatively. you can use a browser on any system that has network access to the computer where the program is running. 2. the program stores your settings in a response file. and Configuration Guide . Prepare your target computers as described in Part 2. Click Sites. If you run the installation program again. “Preparing the tier computers. Click the Security tab. On Microsoft Windows computers. 6. it presents a non-graphical interface. Enable Load images automatically. 2.” on page 1. Do the preparation steps that are described in “Preparing to run the installation program” on page 177. 3. In the Tools menu. you can load your settings from this file into the program instead of entering them again. Click Add. Click OK. In the Add this Website to the zone field. the installation program displays the user interface to a standard Web browser. The program starts a self-contained Web server on the computer. 180 Planning. You can then start a Web browser on the computer or on a remote computer and access the graphical interface. Click OK. Plan your installation as described in Part 1. When you first start the installation program. 7. Starting the installation program in graphical mode The installation program provides a graphical interface that leads you step-by-step through the process of installing IBM InfoSphere Information Server. Click the Trusted Sites icon. 8. Click Content. you can use a Web browser locally on the target computer. click Options.

exe – Open an elevated command window. If you exit the wizard before you complete the installation. Linux UNIX Make these additional settings to help ensure that the installation is successful: v Set the file creation mask to 022: Chapter 12. v If you close your browser while the wizard is running. install. select the Continue option.exe. 3. sh: export IBM_JAVA_OPTIONS= csh. make sure that the session does not shut down or timeout for the duration of the installation. If you use telnet or ssh. Installing new software 181 . v Linux UNIX Log in as the root user. Press Ctrl-Shift-Enter. Log in to the computer. Open the window on the target computer. v If your browser displays a "server busy" message.exe. v The wizard times out if there is no activity within two hours. When a security notification opens. vWindows Log in to the target computer as a local administrator or as a local or domain user who is directly assigned to the local Administrators group. v Linux UNIX Open a command prompt or shell window. 2. Keep the shell window open during the entire installation process. To do so.About this task The installation program displays a wizard that prompts you for parameters. or use a graphical desktop sharing system. Procedure 1. Open a command prompt window. In the newly created session. click the Start menu and type cmd in the Start Search box. and other data. tcsh: unsetenv IBM_JAVA_OPTIONS v Windows set IBM_JAVA_OPTIONS= 4. delete the user accounts manually from the computer. db2setup. the installation program immediately creates them on the computer. Click Continue to accept the prompt asking for your permission to continue. you can continue the same session by opening the browser again and reconnecting to the session. user names. v Windows Microsoft Windows 2008. Microsoft Windows 7. v You might see a security warning or notification when any of the Windows following programs are run during installation: setup. passwords.exe. java.exe. Microsoft Windows Vista: Start an administrator session by using either of the following methods: – Run the following command: runas /user:Administrator cmd. While you are using the wizard: v If you create new user accounts from the wizard. click Run or Yes to allow the program to run and continue with the installation. run the following command to clear any Java options that might be set: v Linux UNIX bash. You can also close the browser and then reconnect to same session.

select the language in the Select a language field. Note: Windows The installation program automatically launches the default Web browser on the local computer and navigates to the HTTP address.exe [-verbose] The -verbose option is optional. The wizard page displays each 182 Planning. To display messages in a language other than English. 8. the program runs a short prerequisites check. Later in the installation process. A Login Installation window is displayed in the Web browser window. Then the program describes how to access the graphical interface: ======> Enter one of the following URLs to your web browser to begin the installation process: http://localhost:8080/ISInstall https://localhost:8443/ISInstall 7. A message might appear in the browser that reads "The publisher cannot be verified. For example: ulimit -n 10240 v Check that the current setting for the NOFILES kernel parameter is set to a value that is at least equal to the value that you specify for ulimit. and Configuration Guide . Note: This language selection only applies to this installation session. 5. a higher value. Set the file descriptor limit to 10240. The first wizard page is displayed. umask 022 v Ensure that you have enough file descriptor resources allocated for the installation. v Linux If the target installation directory for InfoSphere Information Server. IBM WebSphere Application Server. Installation. Several messages are displayed." You can safely ignore the message and continue the installation. 10. Change to the is-suite directory within the directory that contains the installation media. log messages are written to the log file only. refer to your operating system documentation for the preferred method of starting daemon services. 9. The option causes the installation program to display log messages to the console and also write them to the log file. and navigate to one of the addresses that are listed in the messages that are displayed in the previous step. After you accept the license agreement./setup [-verbose] Windows setup. If the -verbose option is not specified. Click Login. Follow the prompts in the wizard. ensure that the lock daemon is running. you select the language to apply to the InfoSphere Information Server installation. or IBM DB2 is an NFS file system. This message does not indicate a security risk when it appears during InfoSphere Information Server installation.. Open a Web browser on the computer or on a remote computer. ps -ef | grep -i lockd If the lock daemon is not running. 6.. or unlimited. Run the installation program: Linux UNIX .

check. and type Ctrl+c in the session window to end the installation session. it analyzes your computer resources and file system to determine whether the installation is likely to succeed. If the check found issues that might cause problems with the installation. you must first edit the response file and add passwords. or add a software tier to a computer that already hosts tiers. If you receive FAILED or WARNING messages: a. click Install IBM InfoSphere Information Server and save my settings in a response file and then click Next. 14. click Cancel. While the installation is running: v Leave the terminal window open until the installation is complete. Then click Check Again in the Prerequisites Check page. Then the wizard prompts you for information that is specific to the type of installation that you selected. Chapter 12. If you have to exit the installation program. and type Ctrl+c in the session window to end the installation session. During this check. If the check found issues that might cause problems with the installation. To continue. When you click Next. b. the installation program displays a Response File Review page. Click OK in the confirmation window that appears. close the browser window. specify a name and location for the response file. To use the response file in a subsequent installation pass. 15. After the installation program has collected your selections. If the check fails. In the Response file location field. b. Try to resolve each issue without exiting the installation program. v To cancel the installation. it is marked FAILED in the page. v To continue with the installation. After the prerequisite check is complete. If you have to exit the installation program. Resolve the issues and then restart the installation program. continue to follow the prompts in the wizard. 16. add product modules to existing installation. If you choose to continue with the installation. When all prerequisites checks pass. use a text editor. you can choose to cancel the installation and use the saved response file in a later session. the program displays a summary of the choices that you made in the wizard. Double-click each message to learn more about resolving it. c. Resolve the issues and then restart the installation program with your response file as described in “Restarting in graphical mode with a response file” on page 184. If the check fails. The wizard page displays each check. Then click Check Again in the Prerequisites Check page. the program begins the installation. Note: Passwords are not saved in the response file. At this point. it is marked FAILED in the page. it runs a detailed prerequisites check based on your selections. it is marked WARNING in the page. c. close the browser window. Double-click each message to learn more about resolving it. 11. You can create an installation. it is marked WARNING in the page. The installation program prompts you for the installation type. click Cancel. click Do not install IBM InfoSphere Information Server and save my settings in a response file and then click Next. Try to resolve each issue without exiting the installation program. click Next. Installing new software 183 . To edit the response file. 13. If you receive FAILED or WARNING messages: a. 12.

v Do not continue an installation if there are errors. b. an Installation Summary window is displayed. check for pop-up windows displayed behind the browser window. “Log files. Occasionally a pop-up window might be displayed behind the browser window. you can load the settings into the graphical interface instead of entering them again. Remove the passwords from the file after the installation. Restarting in graphical mode with a response file You can load settings from a response file into the IBM InfoSphere Information Server installation program graphical interface. v Pop-up windows might be displayed. the program saves your settings in a response file before it begins the installation. If you close the Web browser. v The system might occasionally request a response from you if it encounters an error. About this task After you enter settings in the InfoSphere Information Server installation program graphical interface. Click Finish or close the browser window. 17. If the issue can be resolved. Installation. the installation continues to the end. You can also monitor the installation process by reading log files. fix the issue and then click Retry. If the installation pauses for a long time. v Windows Depending upon your security settings. keep the browser window open to monitor progress and to respond if there is an error. Ignore the warnings and click OK to continue the installation. it might fail. When the installation is complete. Check periodically to make sure that the system is not waiting for you to respond. v If this is the first time that the installation program has encountered this problem. 184 Planning. and Configuration Guide . and so on) are saved in the response file that is created by the installation program. Review the last statements in the log file. If the installation program encounters a problem. See Chapter 27. click Retry failed action and click OK. Before you begin Use a response file that the installation program created. Note: No passwords (administrator passwords. an Installation Exception window appears. You can reconnect to the session by opening a new browser session to the same URL. database passwords. warning windows might display during the installation of the IBM DB2 database system or other components. 18.” on page 393. that you must respond to for the installation to proceed. The following message is written to the log file: Installation Engine completed all steps successfully. Before you use the response file. If the installation halts for a long interval. edit the file by using a text editor to add any passwords. or create one by using a text editor. v After you have started the installation process. Windows Restart the computer. v If the problem reoccurs: a. See “Response files” on page 191. When you run the installation program.

or unlimited. Procedure 1. sh: export IBM_JAVA_OPTIONS= csh. In this mode. v Windows Microsoft Windows 2008. Installing new software 185 . ensure that the lock daemon is running. 3. make sure that the session does not shut down or timeout for the duration of the installation. a higher value. For example: ulimit -n 10240 v Check that the current setting for the NOFILES kernel parameter is set to a value that is at least equal to the value that you specify for ulimit. To do so. or IBM DB2 is an NFS file system. Click Continue to accept the prompt asking for your permission to continue.Alternatively. Chapter 12. refer to your operating system documentation for the preferred method of starting daemon services. the program installs the software by using the settings in the response file without displaying a graphical interface. IBM WebSphere Application Server. 2. ps -ef | grep -i lockd If the lock daemon is not running. Linux UNIX Make these additional settings to help ensure that the installation is successful: v Set the file creation mask to 022: umask 022 v Ensure that you have enough file descriptor resources allocated for the installation. Set the file descriptor limit to 10240. Log in to the computer. tcsh: unsetenv IBM_JAVA_OPTIONS v Windows set IBM_JAVA_OPTIONS= 4. v Linux UNIX Log in as the root user. v Log in to the target computer as a local administrator or as a local Windows or domain user who is directly assigned to the local Administrators group. run the following command to clear any Java options that might be set: v Linux UNIX bash. Microsoft Windows 7. Open a command prompt window. In the newly created session. v Linux UNIX Open a command prompt or shell window. or use a graphical desktop sharing system. Press Ctrl-Shift-Enter. Keep the shell window open during the entire installation process. click the Start menu and type cmd in the Start Search box. If you use telnet or ssh.exe – Open an elevated command window. you can run the installation program in silent mode. v Linux If the target installation directory for InfoSphere Information Server. Open the window on the target computer. Microsoft Windows Vista: Start an administrator session by using either of the following methods: – Run the following command: runas /user:Administrator cmd.

Open a Web browser on the computer or on a remote computer. In this mode./setup -rsp response_file_name -uiMode graphical [-verbose] Windows setup. For example. and navigate to one of the addresses that are listed in the messages that the installation program displays. For more information. Also it allows you to do multiple similar installations quickly. see “setup command syntax” on page 189. 6.” on page 1. “Preparing the tier computers.exe -rsp response_file_name -uiMode graphical [-verbose] where response_file is the path and name of your response file. Do the preparation steps that are described in “Preparing to run the installation program” on page 177. If the check succeeds. Each wizard page displays the settings that you specified in the response file. 8. The -verbose option is optional. if you want to install identical client tier software on multiple workstations. Plan your installation as described in Part 1. Silent mode In silent mode. you can create a single response file and install the software on each workstation in silent mode instead of using the graphical user interface each time. and Configuration Guide . 2. Instead. If necessary. 5. you can change the values in the wizard. It performs a prerequisites check. Before you begin 1. “Planning for the installation of IBM InfoSphere Information Server. Silent mode allows you to run an unattended installation. 186 Planning. 7. Starting the installation program in silent mode You can install IBM InfoSphere Information Server without starting the graphic interface. See “Response files” on page 191. Follow the steps in “Starting the installation program in graphical mode” on page 180 to log in and use the wizard. If the -verbose option is not specified. Run the installation program: Linux UNIX . the program installs the software. Installation. 3. Prepare your target computers as described in Part 2. Change to the is-suite directory within the directory that contains the installation media.” on page 125. log messages are written to the log file only. About this task The following procedure describes how to start the installation program in silent mode with the most commonly used command-line options. the installation program reads your installation choices from a response file. 4. The option causes the installation program to display log messages to the console and also write them to the log file. the installation program does not display a user interface. Create a response file. it reads settings from a response file that you create.

For example: ulimit -n 10240 v Check that the current setting for the NOFILES kernel parameter is set to a value that is at least equal to the value that you specify for ulimit. click the Start menu and type cmd in the Start Search box.exe – Open an elevated command window. Open the window on the target computer. Click Continue to accept the prompt asking for your permission to continue. v Linux UNIX Log in as the root user. ps -ef | grep -i lockd If the lock daemon is not running. Log in to the computer. Microsoft Windows Vista: Start an administrator session by using either of the following methods: – Run the following command: runas /user:Administrator cmd. v Windows Microsoft Windows 2008. v Linux UNIX Open a command prompt or shell window. Keep the shell window open during the entire installation process. 2. Microsoft Windows 7. If you use telnet or ssh. 3. or use a graphical desktop sharing system. 6. Installing new software 187 . v Log in to the target computer as a local administrator or as a local Windows or domain user who is directly assigned to the local Administrators group. ensure that the lock daemon is running. v Linux If the target installation directory for InfoSphere Information Server. make sure that the session does not shut down or timeout for the duration of the installation. Press Ctrl-Shift-Enter. refer to your operating system documentation for the preferred method of starting daemon services. Open a command prompt window. 5. Set the file descriptor limit to 10240. run the following command to clear any Java options that might be set: v Linux UNIX bash. or unlimited. Linux UNIX Make these additional settings to help ensure that the installation is successful: v Set the file creation mask to 022: umask 022 v Ensure that you have enough file descriptor resources allocated for the installation. Run the following command to start the installation program: Chapter 12. In the newly created session. a higher value. To do so. or IBM DB2 is an NFS file system. Change to the is-suite directory within the directory that contains the installation media. IBM WebSphere Application Server.Procedure 1. tcsh: unsetenv IBM_JAVA_OPTIONS v Windows set IBM_JAVA_OPTIONS= 4. sh: export IBM_JAVA_OPTIONS= csh.

the program begins to display messages in the window if the -verbose option is specified. The installation program runs through a prerequisites check phase. The -verbose option is optional. The system might also display a firewall warning if the firewall is not shutdown or disabled. If one or more prerequisite checks fail. v If the problem reoccurs: a. the installation program halts with an error message. About this task By default. the installation displays errors and stops. click Yes.” on page 393. v The system might occasionally request you to grant permissions to execute a process. When the installation is complete. If the installation program encounters a problem. Error handling in silent mode You can specify the action that the installation program takes if an error occurs while it is running in silent mode. If the issue can be resolved. If all prerequisite checks pass. v Do not continue an installation if there are errors. b. 8. Installation. installation continues until the installation process finishes. it displays an exception handling message. Click through the warning to allow the installation program to continue. The option causes the installation program to display log messages to the console and also write them to the log file. choose Retry. correct the problem and restart the installation. such as Java. “Log files. the following message appears in the log file: Installation Engine completed all steps successfully./setup -rsp response_file -verbose Windows setup. Windows While the installation is running: v Monitor the installation as described in “Monitoring installation progress” on page 194. log messages are written to the log file only.exe -rsp response_file -verbose where response_file is the path and name of your response file. When this prompt is displayed. and Configuration Guide . 7. you can change this behavior by setting an environment variable. 188 Planning. if an error occurs during an installation while the program is running in silent mode. If the -verbose option is not specified. fix the issue and then choose Retry.exe or db2setup. The prerequisites check report contains messages like the following line: FAIL . For true unattended operation. Review the last statements in the log file. Linux UNIX . v If this is the first time that the installation program has encountered this problem.exe. When you start the installation program. 9. v Leave the terminal window open until the installation is complete. Windows Restart the computer. If a prerequisites check fails. See Chapter 27.The DB2 installation directory C:\IBM\SQLLIB must be empty.

you must also specify the -uiMode graphical parameter. and terminates. To run in graphical mode with a response file. or might cause existing installed software to stop functioning. Procedure 1. Start the installation program. -rsp rspfile Specifies the response file to use for this installation. the installation program runs in silent mode by default. -uiMode mode Specifies the mode to run in. setup command syntax You use the setup command to run the IBM InfoSphere Information Server installation program. On the target computer. If you specify the -rsp parameter. Installing new software 189 . Important: Continuing an installation after an error occurs might result in a nonoperational installation. For a graphical mode installation. 3 Exit on error For example: v Linux UNIX setenv EXCEPTION_POLICY=1 v Windows set EXCEPTION_POLICY=1 2. EXCEPTION_POLICY values Value Description 1 Prompt user to retry on error (default behavior) 2 Continue on error. -help Displays this usage information. the settings in the response file that you specify appear in the wizard and you do not have to enter them again. For a silent mode installation. set the EXCEPTION_POLICY environment variable to one of the following values: Table 74. Use this option only if directed by IBM Support. mode can be graphical (default) or silent. you must specify a response file by using this parameter. Chapter 12. Command syntax setup [-help] [-uimode mode] [-rsp rspfile] [-reportOnly | -force] [-reportFile rptfile] [-language languagecode] [-verbose] [-secure] Parameters Entering the setup command without parameters causes the installation program to start in graphical mode.

Table 75. The following table lists valid language codes. Important: Prerequisites check FAILED and WARNING messages indicate items that might cause a failed installation. Performs the prerequisites check but does not perform the installation. Use the -force option only if directed by IBM Support. If a reportFile value is not specified. If -force is not specified. In silent mode. the check box is not shown and the Next button is disabled. -force Use -force to permit the installation program to continue even if prerequisites check tests fail. -reportOnly For a silent mode installation only. log messages are displayed to the console and are also written to the log file. if -force is specified on the command line and a prerequisites check fails. 190 Planning. the report is displayed to the console. the parameter is ignored. and Configuration Guide . If -force is not specified. Language codes Language Codes Chinese (Simplified) zh_CN Chinese (Traditional) zh_TW English en or en_US French fr or fr_FR German de or de_DE Italian it or it_IT Japanese ja or ja_JP Korean ko or ko_KR Portuguese (Brazilian) pt_BR Spanish es or es_ES -verbose Starts the installation session in trace mode. Use with the -reportFile parameter to store the results of the prerequisites check in a text file. If this parameter is specified for a software removal. To continue the installation. the installation process continues. You can use this option in silent mode or graphical mode. -language languagecode Specifies the language that displays for the installation. -reportFile rptfile For a silent mode installation only. In graphical mode. Specifies a text file for the prerequisites check report. if -force is specified on the command line and a prerequisites check fails. click this check box and then click Next. or cause malfunctions in the installed software. Installation. the installation process halts if prerequisites check tests fail. an Ignore FAILED items and continue check box is shown in the window. In this mode.

. The installation program stops after the prerequisites check without installing the software. It stores log messages in a log file. The password is used to authenticate access to the installation program from the browser.txt. You can also use a response file during software removal. log messages are written to the log file only. When the prerequisites check runs. Different sets of parameters and values are used depending on the type of software installation or removal.txt response file. The password can include white-space characters. results are stored in prq.txt -reportFile prq. The installation program uses the settings in the rsp. It stores log messages in a log file. The user enters the password in the login window to access the installation program. It stores log messages in a log file and also displays them to the console. a certain set of parameters and values is used Chapter 12.txt -reportFile prq. Installing new software 191 ./setup -rsp rsp.txt. a login window is displayed./setup -rsp rsp.txt -verbose Response files A response file contains parameters and values that tell the IBM InfoSphere Information Server installation program how to perform an installation. The installation program uses the settings in the rsp. If you do not specify this parameter.txt response file. When the prerequisites checks run. -secure For a graphical mode installation only./setup -rsp rsp. results are stored in prq. ./setup The following command causes the installation program to prompt for a password and then start in graphical mode. It stores log messages in a log file. When the user accesses the installation program by using the browser./setup -secure -rsp rsp.txt response file. or by modifying the sample templates that are included on the installation media. The password can be any string of alphanumeric characters. . The installation program uses the settings in the rsp. The installation program stops if a prerequisite check test fails. The installation program uses the settings in the rsp.txt The following command causes the installation program to start in silent mode. Examples The following command causes the installation program to start in graphical mode on a Linux or UNIX system: .txt -reportFile prq.txt. .txt -reportOnly The following command causes the installation program to start in silent mode. results are stored in prq.txt response file. For example. Prompts you to create a password when the installation program starts. Create a response file by using the InfoSphere Information Server installation or software removal program. When the prerequisites checks run. ./setup -secure The following command causes the installation program to prompt for a password and then start in graphical mode.txt -uiMode graphical The following command causes the installation program to start in silent mode.

The program then either performs the operation or exits. for an installation that includes application server clustering. parameters and values are specified one per line. depending upon your selections in the window. Modify one of the sample response file templates that are included with the installation media. the parameter is separated from the value with an equals sign (=). Parameters and values are case sensitive. go to the following topics: v Linux UNIX Appendix A. omit the parameter value or specify the parameter without a value. include two backslashes.installLocation=C:\\IBM\\InformationServer To set a parameter to a null value. Installation. For example: suite.” on page 441 Creating a response file Create a response file using either of the following methods: Create the response file by using the installation or removal program wizard. 3. Either selection causes a response file to be created. To specify a backslash in the response file. In each line. Run the installation program or software removal program in graphical mode. A line that begins with a pound sign (#) indicates a comment.db. To use the wizard to create the file: 1. “Response file parameters (Linux. 2. “Response file parameters (Windows). The templates are included in the following locations: v Linux UNIX media_location/is-suite/samples/responses v Windows media_location\is-suite\samples\responses See the readme file included that is included with the templates for more information about them. Blank lines are ignored. For example: xmeta. Another set is used for an installation where the application server is set up in a stand-alone configuration. When the Response File Review page is displayed.” on page 429 v Windows Appendix B. In the file. UNIX). Several different templates are included for different installation types. For lists and descriptions of response file parameters and values. Specify a file name and location and click Next. 4.tablespace= 192 Planning. The program saves your parameters in a response file in the specified location. Response file syntax A response file is a text file. Specify your parameters in the wizard. select either Install IBM InfoSphere Information Server and save my settings in a response file or Do not install IBM InfoSphere Information Server and save my settings in a response file. and Configuration Guide .

Installing new software 193 . The genkey command is located in the tools directory on your installation media: v Linux UNIX install_media/tools/genkey.cmd info_to_encrypt For example: C:\is-suite\tools\genkey.password.” Encrypting information in a response file You can encrypt passwords and other information in response files. If the file is created by the installation or software removal program. Run the genkey command to generate encrypted information.server. Replace the value with the encrypted version.encrypted={xor}8Y3lImYJo0sxGOl4igw/pA== Chapter 12. follow this procedure to encrypt information and include it in the files. About this task By default. For example: {xor}8Y3lImYJo0sxGOl4igw/pA== 3. append the extension . Create a response file.password=mypassword If you want to include passwords in encrypted format.encrypted to the parameter. In the response file. Instead. Then the command displays the encrypted version of the specified information. this procedure is typically used to encrypt passwords. the program does not store the passwords in the file. See “Response files” on page 191. If you want to encrypt passwords or other information in your response files. information is stored in plain text in response files. For example: v Original parameter specification: app.server. For example: app. For example: app.server.Passwords in a response file To use a response file.password=<CHANGE_TO_YOUR_PASSWORD> v Encrypted parameter specification: app. see “Encrypting information in a response file.cmd mypassword Messages are displayed in the terminal window. you must specify passwords in the file. However. You can encrypt any values in a response file. locations in the file where passwords must be included are indicated with markers.sh info_to_encrypt v Windows install_media\tools\genkey.server. 2. Procedure 1.password=<CHANGE_TO_YOUR_PASSWORD> Replace the markers with your passwords.

To view updates.) If the tail command is not available. You can monitor log files to track the following installation processes: v The overall IBM InfoSphere Information Server suite installation v The IBM WebSphere Application Server application installation v The IBM WebSphere Application Server enterprise archive (EAR) deployment v Individual IBM InfoSphere DataStage component installations To monitor a log file. The command is also available if you have installed the IBM InfoSphere DataStage client or server-side software. Installation. open the log file in a text editor that does not lock the file for editing while it is open. substitute your path when you perform the procedures.) About this task To follow the progress of the InfoSphere Information Server suite installation. This path is: v Windows C:\IBM\InformationServer v Linux UNIX /opt/IBM/InformationServer If your installation is located in a different path. (The MKS Toolkit is installed with these product modules. monitor the installation log file. navigate to the directory that contains the log file: v AIX Linux UNIX 194 Planning. The monitoring procedures assume that you have installed InfoSphere Information Server in the default installation path. (The MKS Toolkit is installed with these product modules. you can use the tail command. and Configuration Guide . close the file and then reopen it. WindowsThe tail command is available on Microsoft Windows systems if you have installed Microsoft Windows Resource Toolkit or a third-party tail utility. Monitoring the IBM InfoSphere Information Server installation You can follow the progress of the IBM InfoSphere Information Server suite installation by monitoring the installation log file. On the computer on which the installation program is running. use the command tail -f logfilename where logfilename is the path and name of the log file. The command is also available if you have installed the InfoSphere DataStage client or server-side software. Before you begin To monitor log files as they are created.Monitoring installation progress You can follow the progress of an installation by monitoring log files. Windows The tail command is available on Microsoft Windows systems if you have installed Microsoft Windows Resource Toolkit or a third-party tail utility. Procedure 1.

To view updates. open the log file in a text editor that does not lock the file for editing while it is open.log is the log file with the most recent date-time stamp. Enter the following command: tail -f ISInstall*. Installing new software 195 . go to that location instead. Note: The installation process updates the WebSphere Application Server suite installation log file sporadically. open the log file in a text editor that does not lock the file for editing while it is open. close the file and then reopen it.) About this task To follow the progress of the WebSphere Application Server installation. Windows The tail command is available on Microsoft Windows systems if you have installed Microsoft Windows Resource Toolkit or a third-party tail utility. if you redirected the installation program's temporary files to a different directory. cd /tmp cd ibm_is_logs v Windows cd %temp% cd ibm_is_logs Note: In Preparing to run the installation program. Enter the following command: tail -f WebSphereInstall. navigate to the directory that contains the log file: v Windows cd c:\IBM\InformationServer\logs v Linux UNIX cd /opt/IBM/InformationServer/logs 2. Procedure 1. monitor the installation log file. Chapter 12. To view updates. The command is also available if you have installed the IBM InfoSphere DataStage client or server-side software. On the computer on which the installation program is running.log where ISInstall*. you can use the tail command.log If the tail command is not available. If the tail command is not available. Before you begin To monitor log files as they are created. Monitoring the IBM WebSphere Application Server installation You can follow the progress of the WebSphere Application Server installation by monitoring the installation log file. close the file and then reopen it. There might be gaps of up to 20 minutes when no updates are displayed. 2. (The MKS Toolkit is installed with these product modules.

(The MKS Toolkit is installed with these product modules. Enter the following command: tail -f SystemOut. Note: Some EAR deployments can take up to 25 minutes. On the computer on which the installation program is running.log If the tail command is not available. Before you begin To monitor log files as they are created. Windows The tail command is available on Microsoft Windows systems if you have installed Microsoft Windows Resource Toolkit or a third-party tail utility. you can use the tail command. you can use the tail command. (The MKS Toolkit is installed with these product modules. Procedure 1.) About this task To follow the progress of the IBM WebSphere Application Server EAR deployment. navigate to the directory that contains the log file: v Windows cd c:\IBM\WebSphere\AppServer\Profiles\InfoSphere\log\server1 v Linux UNIX cd /opt/IBM/WebSphere/AppServer/profiles/InfoSphere/log/server1 v AIX cd /usr/IBM/WebSphere/AppServer/profiles/InfoSphere/log/server1 2. Monitoring the IBM WebSphere Application Server enterprise archive deployment You can follow the progress of the IBM WebSphere Application Server enterprise archive (EAR) deployment by monitoring the installation log file. To view updates. monitor the installation log file. and Configuration Guide . Installation. close the file and then reopen it. Monitoring IBM InfoSphere DataStage component installations You can follow the progress of individual IBM InfoSphere DataStage component installations by monitoring the component installation log file. Windows The tail command is available on Microsoft Windows systems if you have installed Microsoft Windows Resource Toolkit or a third-party tail utility. open the log file in a text editor that does not lock the file for editing while it is open. The command is also available if you have installed the IBM InfoSphere DataStage client or server-side software. Before you begin To monitor log files as they are created.) 196 Planning. which can cause the installation program to seem as if it has stopped running. The command is also available if you have installed the InfoSphere DataStage client or server-side software.

navigate to the directory that contains the log file: v Windows cd c:\IBM\InformationServer\Server\StagingArea\Log v Linux UNIX cd /opt/IBM/InformationServer/Server/StagingArea/Log 2. run the General Diagnostic Health Checker and other product-specific health checkers. The health checkers are available under the All Diagnostic Tools menu. If the tail command is not available.log is the log file with the most recent date-time stamp.log where ISInstall*. close the file and then reopen it. To verify the installation. the plug-in installation can take considerable time. If you have many projects. The IBM Support Assistant Lite for InfoSphere Information Server tool reduces the effort and amount of time it takes you to send the appropriate diagnostic data to IBM Customer Support by automating the gathering and collection process. The tool FTPs the results to IBM Support and attaches them to an existing PMR (problem management record). files. open the log file in a text editor that does not lock the file for editing while it is open. Information pertinent to a problem is collected and analyzed to identify the origin of the problem. On the computer on which the installation program is running. Enter the following command: tail -f ISInstall*. Chapter 12. and artifacts from the local installation of IBM InfoSphere Information Server. The tool focuses on automatic collection of problem data and provides diagnostic verifications of an InfoSphere Information Server installation. Installing new software 197 . It focuses on performing non-destructive tests and passive collection of data to report the system health and verify the correct configuration of the installation. Procedure 1. Additionally. To view updates. About this task You can monitor the installation of the following InfoSphere DataStage components: v InfoSphere DataStage plug-ins v PX operators v Connectors Each component must be installed into each project on each host system. Installation verification and troubleshooting The IBM® Support Assistant Lite for InfoSphere Information Server tool provides functionality to collect data. What the tool offers The IBM® Support Assistant (ISA) Lite for InfoSphere Information Server tool helps you troubleshoot InfoSphere Information Server problems. the tool performs symptom analysis to help streamline the problem determination process.

the metadata repository tier. services tier.wss?rs=14&uid=swg24022700. IBM Support Assistant Lite for InfoSphere Information Server User's Guide Provides a detailed description of the ISALite tool. run the installation program as described in these topics. and Configuration Guide . Scenario A: Metadata repository tier and services tier installation Wizard page title User action Early Requirements Check After all tests pass. Documentation Refer to the following documentation that is available under the \doc folder of the ISALite installation.com/support/docview.ibm. Updates to the documentation are available at www. Installation. In this configuration. Installation program sample scenarios For the sample scenarios that are described in the planning portion of this documentation. For information about how to get the tool for previous releases and for any updates that are available. refer to www. If all checks pass. and the client tier is installed on five separate workstations. IBM Support Assistant Lite for InfoSphere Information Server Quick Start Guide Provides an overview of the ISALite tool and what you must configure to get started. run the installation program as described in this topic. Running the installation program for Scenario A For sample scenario A. services tier. IBM InfoSphere Information Server Click Next to accept the default installation Installation Directory directory. Metadata repository tier. click Next. Tier Selection Choose Metadata repository.ibm. Then run the installation program on the computer in graphical mode. and Engine.wss?rs=14 &uid=swg24022700. and engine tier are installed on one server. 198 Planning. The user response to each wizard page is described in the following table: Table 76. “Sample scenario A: Basic client-server topology” on page 84 describes a simple IBM InfoSphere DataStage installation. and engine tier installation Set up the hardware and the network. the installation proceeds. The program runs a basic requirements check. Installation Type Selection Choose New installation. Where to find the tool IBM Support Assistant Lite for InfoSphere Information Server tool is installed in the ISALite folder under IS_HOME when you run the installation program. and complete all other preinstallation tasks.com/support/ docview. Services. Product Selection Choose IBM InfoSphere DataStage.

Click Next to accept the default installation directory. High Availability Server Cluster This is not a high availability active-passive Configuration configuration. Installing new software 199 . DB2 Administrator User Information Click Existing user. DB2 Installation Directory Click Next to accept the default installation directory. instance name.Table 76. IBM WebSphere Application Server Profile Click Next to accept the specified ports. IBM DB2 Instance User As the instance name. IBM WebSphere Application Server Leave the Customize the port values check Installation Directory box selected. IBM InfoSphere Information Server Specify isadmin as the user name and Administrator provide a password. and location. Enter the user name of the DB2 administrator user that the user created on the target computer before starting the installation program. DB2 Fenced User Information Click Existing user. Application Server Administrator Accept the default user name (wasadmin) and provide a password. Also enter the port number to use for the DB2 instance. Also specify the database name. Leave This is an active-passive server cluster configuration cleared. Application Server Options Choose Install WebSphere Application Server. Job Monitor Ports Configuration Click Next to accept the default values in this page. The installation program installs DB2 in this directory. Clear Options all other check boxes. Database Management System Selection Choose Install IBM DB2 9. enter the user name of the DB2 instance owner account that the user created before running the installation program. Metadata Repository Configuration Enter the account information of the DB2 database owner that was created before running the installation program. Enter the user name of the DB2 fenced user that the user created on the target computer before starting the installation program.7 Enterprise Server Edition. Chapter 12. IBM InfoSphere DataStage Administrator Enter the user name of the IBM InfoSphere DataStage administrator that the user created on the target computer before starting the installation program. The Ports Assignment port values are selected automatically based on the current system configuration. Scenario A: Metadata repository tier and services tier installation (continued) Wizard page title User action IBM InfoSphere DataStage Installation Choose IBM InfoSphere DataStage. IBM InfoSphere Information Server Agent Click Next to accept the default values in Ports Configuration this page.

and click Next to start Computer the installation. do the postinstallation configuration steps that are described in “Sample scenario A: Basic client-server topology” on page 84. Leave the Enable a legacy SAS configuration check box cleared. Response File Review Click Next to save the file in its default location. click Next. and Configuration Guide . run the installation program in graphical mode. Leave the Install WebSphere MQ Plug-in check box cleared. Click Next. System Requirements Check After all tests pass. and click Next to start Computer the installation. Table 76. and respond to wizard pages as described in the following table: Table 77. Installation Type Selection Choose New installation. IBM InfoSphere DataStage Projects No additional projects are required at this time. InfoSphere QualityStage Globalization Leave the Install globalization support for IBM InfoSphere DataStage and IBM InfoSphere QualityStage check box selected. Installation. After all client installations are completed. Product Selection Choose IBM InfoSphere DataStage. Scenario A: Client tier installation Wizard page User action Early Requirements Check After all tests pass. SAS Configuration There are no existing jobs that require SAS. Scenario A: Metadata repository tier and services tier installation (continued) Wizard page title User action IBM InfoSphere DataStage Instance Tag A single instance of the IBM InfoSphere Information Information Server engine is to be installed on the computer. 200 Planning. IBM WebSphere MQ Plug-in Selection No existing jobs depend on the IBM WebSphere MQ plug-in. System Requirements Check After all tests pass. Tier Selection Choose Client. IBM InfoSphere DataStage and IBM International code pages must be supported. Response File Review Click Next to save the file in its default location. Client installation On each of the five client workstations. IBM InfoSphere Information Server Click Next to accept the default installation Installation Directory directory. Preinstallation Summary for the Current Review the summary. Preinstallation Summary for the Current Review the summary. click Next. click Next. Leave the Configure Engine Instance tag instance check box cleared.

Run the installation program in graphical mode. the metadata repository tier and services tier are installed on one computer. click Next. In this configuration. IBM InfoSphere Information Server Click Next to accept the default installation Installation Directory directory. the engine tier is installed on another computer. IBM DB2 Instance User As the instance name. run the installation program as described in this topic. and respond to wizard pages as described in the following table: Table 78. enter the user name of the DB2 instance owner account that you created before running the installation program. IBM WebSphere Application Server Profile Click Next to accept the specified ports. Application Server Administrator Accept the default user name (wasadmin) and provide a password. Product Selection Choose IBM InfoSphere DataStage. Scenario B: Metadata repository tier and services tier installation Wizard page title User action Early Requirements Check After all tests pass. Leave This is an active-passive server cluster configuration cleared. DB2 Installation Directory Click Next to accept the default installation directory. Chapter 12. Sample scenario B describes an IBM InfoSphere DataStage installation with a dedicated server for the engine tier. Metadata repository tier and services tier installation Set up the hardware and the network. Clear all other check boxes. and complete all other preinstallation tasks. Tier Selection Choose Metadata repository and Services. Database Management System Selection Choose Install IBM DB2 9. Installing new software 201 . Installation Type Selection Choose New installation. High Availability Server Cluster This is not a high availability active passive Configuration configuration. IBM InfoSphere Information Server Specify isadmin as the user name and Administrator provides a password. Click Next to accept the default installation directory. IBM InfoSphere DataStage Installation Choose IBM InfoSphere DataStage (parallel Options and server canvas). and the client tier is installed on other computers.7 Enterprise Server Edition. The Ports Assignment port values are selected automatically based on the current system configuration. Also enter the port number of the DB2 instance.Running the installation program for Scenario B For sample scenario B. IBM WebSphere Application Server Leave the Customize the port values check Installation Directory box selected. Application Server Options Choose Install WebSphere Application Server.

Specify the host name of the services tier computer. and complete all other preinstallation tasks. Metadata Repository Configuration Enter the account information of the DB2 database owner that was created before running the installation program. Clear Options all other check boxes. Enter the administrator ID and password of the IBM InfoSphere Information Server administrator user that you created on the servers before running the installation program. Leave This is an active-passive server cluster configuration cleared. Installation. IBM InfoSphere Information Server Click Next to accept the default installation Installation Directory directory. Table 78. and click Next to start Computer the installation. click Next. IBM InfoSphere DataStage Installation Choose IBM InfoSphere DataStage. Also specify the database name. Run the installation program in graphical mode. IBM InfoSphere Information Server Location Select Use Secure Sockets Layer (SSL) for HTTP communication. High Availability Server Cluster This is not a high availability active passive Configuration configuration. IBM InfoSphere Information Server Agent Click Next to accept the default values in Ports Configuration this page. Response File Review Click Next to save the file in its default location. and the port number of the front-end Web server on which secure HTTP (HTTPS) has previously been configured. System Requirements Check After all tests pass. Engine tier installation Set up the hardware and the network. and location. DB2 Administrator User Information Click Existing user and enter the user name of the DB2 administrator user that was created before running the installation program. Preinstallation Summary for the Current Review the summary. Scenario B: Engine tier installation Wizard page title User action Early Requirements Check After all tests pass. Product Selection Choose IBM InfoSphere DataStage. and Configuration Guide . instance name. Tier Selection Choose Engine. click Next. and respond to wizard pages as described in the following table: Table 79. Installation Type Selection Choose New installation. 202 Planning. Scenario B: Metadata repository tier and services tier installation (continued) Wizard page title User action DB2 Fenced User Information Click Existing user and enter the user name of the DB2 fenced user that was created before running the installation program.

System Requirements Check After all tests pass. IBM WebSphere MQ Plug-in Selection No existing jobs depend on the IBM WebSphere MQ plug-in. IBM InfoSphere DataStage and IBM International code pages need to be InfoSphere QualityStage Globalization supported. Do not select the Configure Engine Instance tag instance check box. IBM InfoSphere DataStage Projects No additional projects are needed at this stage. and respond to wizard pages as described in the following table: Table 80. Installation Type Selection Choose New installation. Tier Selection Choose Client. Response File Review Click Next to save the file in its default location. System Requirements Check After all tests pass. Chapter 12. Preinstallation Summary for the Current Review the summary. Click Next. Job Monitor Ports Configuration Click Next to accept the default values in this page. IBM InfoSphere Information Server Click Next to accept the default installation Installation Directory directory. click Next. Response File Review Click Next to save the file in its default location. click Next. SAS Configuration There are no jobs that require SAS. Scenario B: Client tier installation Wizard page User action Early Requirements Check After all tests pass. Product Selection Choose IBM InfoSphere DataStage. run the installation program in graphical mode. click Next. and click Next to start Computer the installation. Installing new software 203 . Preinstallation Summary for the Current Review the summary. and click Next to start Computer the installation. Scenario B: Engine tier installation (continued) Wizard page title User action IBM InfoSphere DataStage Administrator Enter the user name of the IBM InfoSphere DataStage administrator that you created on both servers before starting the installation program. IBM InfoSphere DataStage Instance Tag A single instance of the InfoSphere Information Information Server engine is to be created. Leave the Install WebSphere MQ Plug-in check box cleared. Client installation On each of the client workstations. Leave the Enable a legacy SAS configuration check box cleared.Table 79. Do not clear the Install globalization support for IBM InfoSphere DataStage and IBM InfoSphere QualityStage check box.

After all client installations are completed, do the postinstallation configuration
steps that are described in “Sample scenario B: Topology with isolated engine tier
and parallel engine configuration” on page 88.

Running the installation program for Scenario C
For sample scenario C, run the installation program as described in this topic.

Sample scenario C describes a two-server active-passive high availability topology.
In this sample topology, two computers share a storage area network (SAN). The
metadata repository tier, engine tier, and services tier are all installed on the SAN.
One of the computers (the active server) hosts the tiers. The other computer (the
passive server) is started, but is not running any tier software. IBM Tivoli System
Automation for Multiplatforms is installed on both the active server and the
passive server. The HA software maintains a heartbeat: a periodic signal from the
active server to the passive server that indicates that the active server is
operational. If the active server fails, the heartbeat also fails. The HA software
restarts all services on the passive server. This process is called a failover.

When the installation program is run for this scenario, a floating IP address and
virtual host name are specified for the system. This information is associated with
the active server. All client programs connect to the system by using this address
or host name. If the active server fails, the information is automatically
reassociated with the passive server. Client programs do not need to connect to a
different address.

Metadata repository tier, services tier, and engine tier installation

Set up the hardware and the network, install and configure the HA software, and
complete all other preinstallation tasks. The SAN mount point is configured as
/opt/IBM. Create identical sets of users and groups, including administrator users,
on both servers. Run the installation program on the computer in graphical mode,
and respond to wizard pages as described in the following table:
Table 81. Scenario C: Metadata repository tier, services tier, and engine tier installation
Wizard page title User action
Early Requirements Check After all tests pass, click Next.
IBM InfoSphere Information Server To install the software on the SAN, click
Installation Directory Next to accept the default installation
directory. The default directory
(/opt/IBM/InformationServer) is within the
preconfigured SAN shared directory.
Installation Type Selection Choose New installation.
Tier Selection Choose all tiers. The metadata repository
tier, services tier, and engine tier software
will all be located on the SAN. (The client
tier is not offered for a non-Microsoft
Windows installation.)
Product Selection Choose IBM InfoSphere DataStage, IBM
InfoSphere QualityStage, and IBM
InfoSphere Information Analyzer.
IBM InfoSphere DataStage Installation Choose IBM InfoSphere DataStage (parallel
Options and server canvas). Clear all other check
boxes.

204 Planning, Installation, and Configuration Guide

Table 81. Scenario C: Metadata repository tier, services tier, and engine tier
installation (continued)
Wizard page title User action
High Availability Server Cluster This panel applies specifically to the target
Configuration installation (an active-passive configuration).

Select This is an active-passive server
cluster configuration. In the Virtual host
name field, type the preconfigured floating
host name to share between the servers.
Application Server Options Choose Install WebSphere Application
Server.
IBM WebSphere Application Server Leave the Customize the port values check
Installation Directory box selected. Click Next to accept the default
installation directory. The default directory
(/opt/IBM/WebSphere/AppServer) is within
the preconfigured SAN shared directory.
IBM WebSphere Application Server Profile Click Next to accept the specified port. The
Ports Assignment port values are selected automatically based
on the current system configuration.
Application Server Administrator Enter the user name and password of the
IBM WebSphere Application Server
administrator, which will be created in the
internal registry.
IBM InfoSphere Information Server Enter the user name and password of the
Administrator IBM InfoSphere Information Server
administrator user, which will be created in
the internal registry.
Database Server Select Install IBM DB2 Enterprise Edition.
DB2 Installation Directory Click Next to accept the default installation
directory. The default directory
(/opt/IBM/db2/V9.7) is within the
preconfigured SAN shared directory.
IBM DB2 Instance User Click Existing user. Enter the instance name
and port number that you created on both
servers before starting the installation
program.
DB2 Fenced User Information Click Existing user. Enter the user name of
the DB2 fenced user that you created on
both servers before starting the installation
program.
DB2 Administrator User Information Click Existing user. Enter the user name of
the DB2 administrator user that you created
on both servers before starting the
installation program.
Metadata Repository Configuration Enter the account information of the DB2
database owner that the user created on
both servers before starting the installation
program. Specify the database name,
instance name, and location.
IBM InfoSphere Information Server Agent Click Next to accept the default values in
Ports Configuration this page.

Chapter 12. Installing new software 205

Table 81. Scenario C: Metadata repository tier, services tier, and engine tier
installation (continued)
Wizard page title User action
IBM InfoSphere DataStage Administrator Enter the user name of the IBM InfoSphere
DataStage administrator that you created on
both servers before starting the installation
program.
Job Monitor Ports Configuration Click Next to accept the default values in
this page.
IBM InfoSphere DataStage Instance Tag A single instance of the InfoSphere
Information Information Server engine is to be created.
Do not select the Configure Engine Instance
tag instance check box.
IBM InfoSphere DataStage and IBM International code pages must be supported.
InfoSphere QualityStage Globalization Do not clear the Install globalization
support for IBM InfoSphere DataStage and
IBM InfoSphere QualityStage check box.
IBM WebSphere MQ Plug-in Selection No existing jobs depend on the IBM
WebSphere MQ plug-in. Leave the Install
WebSphere MQ Plug-in check box cleared.
SAS Configuration There are no existing jobs that require SAS.
Leave the Enable a legacy SAS
configuration check box cleared.
IBM InfoSphere DataStage Projects No additional projects are required at this
stage. Click Next.
IBM InfoSphere Information Analyzer Enter the user name and password of the
Repository Configuration IBM InfoSphere Information Analyzer
analysis database owner that you created on
both servers before starting the installation
program.

Click Next to accept the default database
location. The default directory
(/opt/IBM/InformationServer/Repos/iadb) is
within the preconfigured SAN shared
directory.
System Requirements Check After all tests pass, click Next.
Response File Review Click Next to save the file in its default
location. The default directory
(/opt/IBM/InformationServer/response.txt)
is within the preconfigured SAN shared
directory. This location allows the user to
run the installation program again from
either server to make changes if necessary.
Preinstallation Summary for the Current Review the summary, and click Next to start
Computer the installation.

Client installation

On each of the client workstations, run the installation program in graphical mode,
and respond to wizard pages as described in the following table:

206 Planning, Installation, and Configuration Guide

Table 82. Scenario C: Client tier installation
Wizard page User action
Early Requirements Check After all tests pass, click Next.
IBM InfoSphere Information Server Click Next to accept the default installation
Installation Directory directory.
Installation Type Selection Choose New installation.
Tier Selection Choose Client.
Product Selection Choose IBM InfoSphere DataStage, IBM
InfoSphere QualityStage, and IBM
InfoSphere Information Analyzer.
System Requirements Check After all tests pass, click Next.
Response File Review Click Next to save the file in its default
location.
Preinstallation Summary for the Current Review the summary, and click Next to start
Computer the installation.

After all client installations are completed, do the postinstallation configuration
steps that are described in “Sample scenario C: Two-server active-passive high
availability topology” on page 99.

Running the installation program for Scenario D
For sample scenario D, run the installation program as described in this topic.

Sample scenario D describes a configuration that includes IBM WebSphere
Application Server clustering for high availability. The configuration also includes
IBM DB2 clustering for the metadata repository database. The engine tier is set up
in an active-passive high availability configuration.

When the IBM InfoSphere Information Server installation program is run, the
program installs InfoSphere Information Server components on the target
computers and create connections to the components.

Metadata repository tier installation

Set up the hardware and the network that creates a DB2 cluster. Run the
installation scripts to create the metadata repository database within the cluster.

Set up a separate DB2 installation for the IBM InfoSphere Information Analyzer
analysis database. Run the installation script to create the analysis database within
this DB2 instance.

The InfoSphere Information Server installation program is not run for this tier.

Services tier installation

Set up the hardware and the network. Install IBM WebSphere Application Server
Network Deployment for a clustered installation. Create a deployment manager
profile, a custom profile, a cluster, and cluster members. Install a front-end Web
server. Run the installation program in graphical mode, and respond to wizard
pages as described in the following table:

Chapter 12. Installing new software 207

Table 83. Scenario D: Services tier installation
Wizard page title User action
Early Requirements Check After all tests pass, click Next.
IBM InfoSphere Information Server Click Next to accept the default installation
Installation Directory directory which is /opt/IBM/
InformationServer.
Installation Type Selection Choose New installation.
Tier Selection Choose Services.
Product Selection Choose all product modules.
IBM InfoSphere DataStage Installation Choose IBM InfoSphere DataStage. Clear
Options all other check boxes.
High Availability Server Cluster This tier is not set up in an active-passive
Configuration configuration. Leave This is an
active-passive server cluster configuration
cleared and click Next.
Application Server Options Choose Use an existing WebSphere
Application Server installation.
IBM WebSphere Application Server Specify the WebSphere Application Server
Installation Directory installation directory.
WebSphere Application Server Profile Select the WebSphere Application Server
Deployment Manager (dmgr) profile.
WebSphere Application Server Cluster Select Use Secure Sockets Layer (SSL) for
Information HTTP communication. Specify the host
name and port number of the front-end Web
server on which secure HTTP (HTTPS) has
previously been configured.
Application Server Administrator Enter the name and password of the
WebSphere Application Server administrator
user, which will be created in the internal
registry.
IBM InfoSphere Information Server Enter the name and password of the
Administrator InfoSphere Information Server administrator
user, which will be created in the internal
registry.
Database Management System Selection Click Use existing database management
system installation (do not create the
database).
Database Connection In the Database type menu, select IBM DB2
V9. Enter the host name and port of the DB2
database. Also enter the database name and
database owner name and password.
IBM InfoSphere Information Analyzer Enter the account information of the IBM
Repository Configuration InfoSphere Information Analyzer analysis
database owner that you created on the
servers before running the installation
program. Also specify the database name,
instance name, and location of the DB2
instance that was created for this database.
System Requirements Check After all tests pass, click Next.
Response File Review Click Next to save the file in its default
location (/opt/IBM/InformationServer/
response.txt).

208 Planning, Installation, and Configuration Guide

Table 83. Scenario D: Services tier installation (continued)
Wizard page title User action
Preinstallation Summary for the Current Review the summary, and click Next to start
Computer the installation.

After the services tier installation is completed, do the configuration steps for the
tier that are described in “Sample scenario D: Topology with clustered metadata
repository tier and services tier” on page 114.

Engine tier installation

Set up the hardware and the network, install and configure the HA software, and
do all other preinstallation tasks. Configure the SAN mount point as /opt/IBM.
Create identical sets of users and groups, including administrator users, on both
servers. Run the installation program in graphical mode. Run the installation
program in graphical mode, and respond to wizard pages as described in the
following table:
Table 84. Scenario D: Engine tier installation
Wizard page title User action
Early Requirements Check After all tests pass, click Next.
IBM InfoSphere Information Server To install the software on the SAN, click
Installation Directory Next to accept the default installation
directory which is /opt/IBM/
InformationServer.
Installation Type Selection Choose New installation.
Tier Selection Choose Engine.
IBM InfoSphere Information Server Location Select Use Secure Sockets Layer (SSL) for
HTTP communication. Specify the host
name of the services tier computer, and the
port number of the front-end Web server on
which secure HTTP (HTTPS) has previously
been configured. Enter the administrator ID
and password of the IBM InfoSphere
Information Server administrator user that
you created on the servers before running
the installation program.
Product Selection Choose all product modules.
IBM InfoSphere DataStage Installation Choose IBM InfoSphere DataStage. Clear
Options all other check boxes.
High Availability Server Cluster This panel applies specifically to this portion
Configuration of the installation (an active-passive
configuration).

Select This is an active-passive server
cluster configuration. In the Virtual host
name field, type the preconfigured floating
host name to share between the servers.
IBM InfoSphere Information Server Enter the name and password of the IBM
Administrator InfoSphere Information Server administrator
user, which will be created in the internal
registry.

Chapter 12. Installing new software 209

Table 84. Scenario D: Engine tier installation (continued)
Wizard page title User action
IBM InfoSphere Information Server Agent Click Next to accept the default values in
Ports Configuration this page.
IBM InfoSphere DataStage Administrator Enter the user name of the IBM InfoSphere
DataStage administrator that you created on
both servers before running the installation
program.
Job Monitor Ports Configuration Click Next to accept the default values in
this page.
IBM InfoSphere DataStage Instance Tag A single instance of the InfoSphere
Information Information Server engine is to be created.
Do not select the Configure Engine Instance
tag instance check box.
IBM InfoSphere DataStage and IBM International code pages need to be
InfoSphere QualityStage Globalization supported. Do not clear the Install
globalization support for IBM InfoSphere
DataStage and IBM InfoSphere
QualityStage check box.
IBM WebSphere MQ Plug-in Selection No existing jobs depend on the IBM
WebSphere MQ plug-in. Leave the Install
WebSphere MQ Plug-in check box cleared.
SAS Configuration No existing jobs use SAS. Leave the Enable
a legacy SAS configuration check box
cleared.
IBM InfoSphere DataStage Projects No additional projects are needed at this
stage. Click Next.
IBM InfoSphere Information Analyzer Enter the name and password of the IBM
Repository Configuration InfoSphere Information Analyzer analysis
database owner that you created on both
servers before running the installation
program.

Click Next to accept the default database
location. This location (/opt/IBM/
InformationServer/Repos/iadb) is within the
preconfigured SAN shared directory.
System Requirements Check After all tests pass, click Next.
Response File Review Click Next to save the file in its default
location. This location (/opt/IBM/
InformationServer/response.txt) is within
the preconfigured SAN shared directory.
This location allows you to run the
installation program again from either server
to make changes if necessary.
Preinstallation Summary for the Current Review the summary, and click Next to start
Computer the installation.

After the engine tier installation is completed, do the configuration steps for the
tier that are described in “Sample scenario D: Topology with clustered metadata
repository tier and services tier” on page 114.

210 Planning, Installation, and Configuration Guide

Client installation

On each of the client workstations, run the installation program in graphical mode,
and respond to wizard pages as described in the following table:
Table 85. Scenario D: Client tier installation
Wizard page User action
Early Requirements Check After all tests pass, click Next.
IBM InfoSphere Information Server Click Next to accept the default installation
Installation Directory directory.
Installation Type Selection Choose New installation.
Tier Selection Choose Client.
Product Selection Choose all product modules.
System Requirements Check After all tests pass, click Next.
Response File Review Click Next to save the file in its default
location.
Preinstallation Summary for the Current Review the summary, and click Next to start
Computer the installation.

After all client installations are completed, do the postinstallation configuration
steps that are described in “Sample scenario D: Topology with clustered metadata
repository tier and services tier” on page 114.

Chapter 12. Installing new software 211

212 Planning, Installation, and Configuration Guide

Chapter 13. Updating products and components
Use the Update Installer to update IBM InfoSphere Information Server and
associated product modules.

About this task

The Update Installer is installed as part of InfoSphere Information Server in the
following directories:
v Windows C:\IBM\InformationServer\_uninstall\InstallUpdates.exe
v Linux UNIX /opt/IBM/InformationServer/_uninstall/installUpdates

Procedure

For information about how to use the Update Installer, go to www.ibm.com/
support/docview.wss?rs=14&uid=swg27016531.

© Copyright IBM Corp. 2005, 2010 213

214 Planning. Installation. and Configuration Guide .

You install these components after you install IBM InfoSphere Information Server. For detailed information about the name and port number requirements. Installing the IBM InfoSphere Business Glossary Anywhere client To use IBM InfoSphere Business Glossary Anywhere. From the shared directory. About this task You must install and configure the InfoSphere Business Glossary Anywhere client separately from the installation of IBM InfoSphere Information Server. 2005. v User computers can be automatically updated when a software update to the InfoSphere Business Glossary Anywhere client becomes available. each user can install the client on his own computer. Preparing for enterprise-wide distribution To take advantage of IBM InfoSphere Business Glossary Anywhere enterprise-wide installation and update features.Chapter 14. and want to take advantage of the automatic update feature.) InfoSphere Business Glossary Anywhere provides the following enterprise-wide installation features: v Users can install the client from a central location. config. see “Server configuration parameters” on page 216. To install the client from a central location. administrators must create a directory that is shared over the network that contains the installation files. administrators can edit a configuration file whose values are propagated to all the clients during this initial installation. Installing components that are not in the suite installation program Some components have their own installation programs. v You must know the name and port number of the system where IBM InfoSphere Business Glossary is installed. you must know the directory path where the previous client installation files are located.ini. The configuration file. v If you are installing an update to the client such as a patch or fix pack. 2010 215 . The client runs on individual user computers running Microsoft Windows operating systems. Before you begin v The InfoSphere Business Glossary Anywhere server must already be installed in the services tier. you must install and configure the client. Optionally. specifies connection information between the server and the InfoSphere Business Glossary Anywhere clients. © Copyright IBM Corp. administrators can copy the installation files for IBM InfoSphere Business Glossary Anywhere client to a shared directory and edit a configuration file. (See the InfoSphere Information Server system requirements for specific system requirements.

To use the automatic update feature.ini configuration file contains the parameters to configure the connection between the server and all the clients for IBM InfoSphere Business Glossary Anywhere. Then. For subsequent installations (updates). See “Installing the client” on page 219. All clients that are installed from the server on which a particular config. 2. this file is BGA_WIN_85.5. v If you are updating to a fix pack or other interim release and you install the interim release files from the same directory from which the files of the prior major version were installed. Version 8. Version 8. and Configuration Guide . Note: The automatic update feature works for updates.2 to InfoSphere Business Glossary Anywhere.ini file configure the settings in the Server Configuration tab in the client for InfoSphere Business Glossary Anywhere the first time that the client is installed. such as fix packs.zip is the name of the file containing the InfoSphere Business Glossary Anywhere client.ini file take effect the first time you install the InfoSphere Business Glossary Anywhere client on each user computer. For example.ini with a text editor. configuration changes must be made manually within each client. open config. Copy the file file_name.) In the root of the installation directory. Note: The values configured in the config. it is automatically updated. where file_name. the next time a user starts the client. 216 Planning. Note: If the client has already been installed at your site. you must copy the compressed file containing the updated InfoSphere Business Glossary Anywhere client to the same shared directory that was used for the previous version. Version 8. then users must manually install the client. What to do next Next.zip. This file is a compressed file that contains all the files required for installing InfoSphere Business Glossary Anywhere. install the InfoSphere Business Glossary Anywhere client in either of the following ways: v If a client of this version of InfoSphere Business Glossary Anywhere has not been previously installed from the same directory in which new installation files are now located. to a particular InfoSphere Business Glossary Anywhere version. Procedure 1.1. Server configuration parameters The config. copy the installation files to the same directory where the installation files of the current version are located to take advantage of the automatic update feature. for InfoSphere Business Glossary Anywhere. Change the configuration values for your site. No user intervention is needed. from the Settings screen.zip to a shared directory that can be accessed by users.5. (First-time installation only.ini file resides will be affected by the settings in that file. this feature cannot be used to update the client from InfoSphere Business Glossary Anywhere. then the client is updated automatically the first time that the user runs the client. Installation. Purpose The parameters in the config. For example. but it cannot update from one version to another.

The password is not encrypted and can be seen by anyone who opens the config. Chapter 14. The default value is true. The default directory is C:\Documents and Settings\user account\Application Data\IBM\BusinessGlossaryAnywhere\Logs where user account is the name of the Microsoft Windows user account on the client computer.Note: To change these parameters after the initial installation of the client. LogToFile Writes messages to a log file. Do not use the port of a particular cluster member. If clustering is set up Port is the port of the front-end dispatcher (either the Web server or the load balancer). The default text is blank. Optional: Type the complete directory path on the local disk of the client computer. LogFileDirectory Writes log messages to the log file in this directory. edit the parameters in the Server Configuration tab of each client. the LogToEventViewer and LogFileDirectory parameters are ignored. There is no default value. Optional: Type true or false. Parameters You can set the value for each parameter or accept the default value. The text does not extend beyond the width of the window and is truncated at the end of the last complete word. Password Specifies the password of the user account in the UserName parameter. If clustering is not set up Port is the port that is assigned to the IBM InfoSphere Information Server Web console. If LogToFile is false.ini file. Optional: Type in any alphanumeric text. CustomizedText Text you enter here is displayed on the Welcome screen beneath the product title. Port Specifies the port number of the Web console of the server or front-end dispatcher that is specified in the ServerName parameter. The value of Port depends on whether IBM WebSphere Application Server clustering is set up within your services tier configuration. The client installation program automatically determines the name of the user account on each client computer. Do not include graphics such as company logos. Installing components that are not in the suite installation program 217 . if one exists.

the client language setting is changed to that of the server. If clustering is set up ServerName is the name or IP address and the port of the front-end dispatcher (either the Web server or the load balancer). If clustering is not set up ServerName is the host name or IP address of the computer where WebSphere Application Server is installed. UILanguageCode Defines the language for the client to use. There is no default value. The user must have a Business Glossary Basic User role or higher. and Configuration Guide .ini file This sample file configures InfoSphere Business Glossary Anywhere to write informational messages to a log file in C:\IBM\BGA\LOGS. is 218 Planning. Errors are also sent to the Microsoft Windows Event Viewer. The default setting is English (United States). Do not use the host name of a particular cluster member.ini file is not found. The following values are supported: Value Language en-US English (United States) de-DE German es-ES Spanish fr-FR French it-IT Italian ja-JP Japanese ko-KR Korean pt-BR Portuguese (Brazil) ru-RU Russian zh-CN Simplified Chinese zh-TW Traditional Chinese UserName Specifies the name of a user account that has access to IBM InfoSphere Business Glossary on the server in the ServerName parameter. The user is prompted to restart the client for the new setting to take effect. Installation. Note: If the config. JK Enterprises. the default is still English (United States). The company name. Sample config. If the server is set to a different language than the client. ServerName The value of ServerName depends on whether WebSphere Application Server clustering is set up within your services tier configuration. then when the client connects to the server.

Procedure 1. you must first uninstall the earlier version. 4. If you are updating with an interim release. 2. LogToFile=true LogToConsole=false LogFileDirectory=C:\IBM\BGA\LOGS ServerName=sample_server Port=9080 UserName=sample_user Password=sample_password CustomizedText=JK Enterprises UILanguageCode=ja-JP Installing the client Install and configure the IBM InfoSphere Business Glossary Anywhere client on your computer. the client is automatically updated if an interim release (such as a Fix Pack) of InfoSphere Business Glossary Anywhere for this version of InfoSphere Business Glossary Anywhere is installed from the initial installation directory. Configure the method that you want to use to capture text. Before you begin v You must know the location of the directory where the InfoSphere Business Glossary Anywhere client installation files are located and you must be able to access them. Contact your IBM InfoSphere Business Glossary administrator or IBM InfoSphere Information Server administrator for this information. Right-click the open book icon and click Settings → Server Configuration. When the installation is complete. Chapter 14. copy file_name. Some parameters might have been preconfigured by an administrator. About this task You can install the InfoSphere Business Glossary Anywhere client and define user preferences and configuration parameters. Installing components that are not in the suite installation program 219 .5.exe to start the installation. After the initial installation for a particular version.zip to a directory. Configure. for either initial installation or an update. Note: If you want to install InfoSphere Business Glossary Anywhere from a different directory than was used for an earlier version. server port. included in the Welcome and Getting Started windows. or update if necessary. an Open Book icon is displayed in your system tray.zip to the same directory from which the earlier version was installed to take advantage of the automatic update feature.zip is the name of the file containing the InfoSphere Business Glossary Anywhere client. and extract the files. Double-click BGAsetup. for InfoSphere Business Glossary Anywhere. Right-click the Open Book icon and click Settings → Text Capture. user name. this file is BGA_WIN_85. the server name. For example. Version 8.zip. InfoSphere Business Glossary is installed on a server called sample_server. and password. v You must have a user account on IBM InfoSphere Information Server with a Business Glossary Basic User role or higher. where file_name. 3. Copy the file file_name.

where host_server is the Server Name and port is the Server Port as configured in the Server Configuration tab of the InfoSphere Business Glossary Anywhere Settings screen. and click Finish. d. On the page that warns you about a problem with the security certificate. user preferences. click Yes to install the certificate. In the address field. One method of doing so is by following these steps with your Microsoft Windows Internet Explorer web browser: a. Click the User Preferences tab to define other user parameters.ini file. day. the first time that you access InfoSphere Business Glossary Anywhere a message about HTTPS is displayed if the certificate from the server is not trusted. 7.) c. then you must install a security certificate. The name of the log file is BusinessGlossaryAnywhereyyyymmddhhmmss. i. If you have connection errors. Note: The following steps describe the procedure to follow with Windows Internet Explorer 7. month. check the log file. and configuration values at any time by using the options available from the Settings tab. Double click on the open book icon to reopen InfoSphere Business Glossary Anywhere and connect to the business glossary. a log file is created on the client computer. g. Click the Certification Path tab. double-click the Open Book icon in your system tray. What to do next To confirm that you can connect to the business glossary. then click on View certificates. Other Internet Explorer versions might require slightly different steps. minute. 220 Planning. Installation. (Required if HTTPS is enabled. f. and second when the application was started. Click View Certificate. e. 5.) If the IBM InfoSphere Information Server port being connected to uses HTTPS.log. port number. h. j. and password are correct. If you receive such a message. Click the Search Items tab to define what business glossary content you want to include in searches. Verify with the InfoSphere Business Glossary administrator that the server name. Click Install Certificate to launch the Certificate Import Wizard. You can change the text capture method. Click the root path that is displayed at the top of the Certification Path window. You can store the certificate in any security store. On the Security Warning screen. b. hour. click Continue to this website (Not recommended.0. type the connection information to connect to the IBM InfoSphere Business Glossary browser. user name. and Configuration Guide . Click OK to save the settings and close the configuration window. where yyyymmddhhmmss is the year. Click Certificate Error at the top of the window. 6. Use the following format: https://host_server:port/bg. The log file is in the directory that has been defined in the LogFileDirectory parameter in the config. Each time that the client is started. Open Windows Internet Explorer. Follow the Certificate Import Wizard prompts.

UML Profile feature. You install this component. Also includes the InfoSphere Business Glossary Client for Eclipse UML Profile API. This directory becomes the archive site for the client. contact your system administrator to put the certificate in a known directory. If the InfoSphere Information Server host that you connect to uses HTTPS. your computer must have a digital security certificate installed that corresponds to the InfoSphere Information Server host. Before you begin Make sure that your system meets the prerequisites described for InfoSphere Business Glossary Client for Eclipse in the IBM InfoSphere Information Server system requirements.Installing IBM InfoSphere Business Glossary Client for Eclipse IBM InfoSphere Business Glossary Anywhere provides an Eclipse plug-in component that enables you to access business glossary content directly from Eclipse-based applications. The first time that you connect to the server. Depending on your needs. If you receive such a message. separately from the rest of IBM InfoSphere Business Glossary and InfoSphere Business Glossary Anywhere. Core glossary from within their Eclipse-based application. you can install all of the features or a subset of them. Feature name Description Feature dependencies InfoSphere Business Glossary Users can view business No other features required. InfoSphere Business Glossary Users can apply the Business No other features required. Chapter 14. UML Profile Glossary profile to their UML model and to view preexisting term assignments. Installing components that are not in the suite installation program 221 . InfoSphere Business Glossary Users can incorporate term Requires InfoSphere Business Data Model Integration information into logical and Glossary Core feature and physical data model InfoSphere Business Glossary elements. You need access to that directory to install the certificate on your computer. The feature also includes the InfoSphere Business Glossary Client for Eclipse Core API. InfoSphere Business Glossary Users can incorporate term Requires InfoSphere Business UML Integration information into UML model Glossary Core feature and elements.zip file) that contains the installation files for InfoSphere Business Glossary Client for Eclipse to a directory. terms to model elements. a message about HTTPS is displayed if the certificate from the server is not trusted. including assigning InfoSphere Business Glossary terms to model elements. About this task You must copy the compressed file (. The client consists of the Eclipse features that are described in the following table. including assigning UML Profile feature. InfoSphere Business Glossary Client for Eclipse.

Note: If you are an administrator who is providing the client to multiple users. > Add Site..1. d. c.5.zip. For Eclipse version 3.org/releases/galileo in the Location field. click Help > Install New Software > Add. Procedure To install a client feature: Procedure 1. Click Manage Sites.eclipse. b. Navigate to the file BGA_ALL_85. (These Eclipse components are provided with InfoSphere Data Architect and supported Rational Software Architect products. Click OK.. click Add and enter http://download. so in these cases this step is not necessary. For Eclipse version 3.4.4. Make sure that the Galileo Update Site is in the list of Available Software Sites. you might need to update the Eclipse plug-ins that correspond to your version of Eclipse. Installation. follow the instructions in step 4. Click the Available Software tab.1. For Eclipse version 3. 2. Make sure that Contact all update sites during install to find required software is checked. Click Archive.5. Configure Eclipse to update publicly available components of Eclipse 3. 3. You must follow different steps depending on what version of Eclipse you have installed. a. a. 4. Click the Available Software Sites hyperlink. click Help > Software Updates. and enabled. and Configuration Guide . If your installation of Eclipse does not include them. 222 Planning. Copy the file BGE_ALL_85. The InfoSphere Business Glossary Client for Eclipse features are added to the list of available software. Later versions of Eclipse might have different steps to follow. b. and checked. Click Help > Install New Software. If the Ganymede Update Site is not in the list. 5. Click OK. follow the instructions in step 5.. Add the InfoSphere Business Glossary Client for Eclipse update site. c.eclipse.4.1.5. d. e. For Eclipse version 3. If the Galileo Update Site is not in the list. b. Click OK. Configure Eclipse to update publicly available components of Eclipse 3.2.2. d.) InfoSphere Business Glossary Client for Eclipse depends on specific publicly available Eclipse components. copy the file to a shared directory that can be accessed by all users. Make sure that the Ganymede Update Site is in the list of Available Software Sites.zip to a directory on your hard disk.. 6. The list expands to include the available features. If you are working with Eclipse applications other than IBM InfoSphere Data Architect or a supported Rational® Software Architect product.org/releases/ganymede in the Location field. Start the Eclipse application to which you are adding InfoSphere Business Glossary Client for Eclipse. Click Help > Software Updates. a. click Add and enter http://download.2. c. Navigate to the site you have added and expand the contents.. make sure that your Eclipse application is set up to install publicly available Eclipse components.

port If your installation has a separate front-end dispatcher. make sure that Group items by category is not checked. d. g. Select the check boxes for each of the features you want to install. Note: The following steps describe the procedure to follow with Windows Internet Explorer 7. use the WebSphere Application Server secure transport port if HTTPS is configured.CER) and then click Next. then you must install a security certificate by following these steps: a. For example. or use the HTTP transport port if HTTPS is not configured.0.1. Store the certificate in any directory and then click Finish. Select Base-64 encoded X. On the page that warns you about a problem with the security certificate. See the "Feature dependencies" column in the table in this document to ensure that you install all the features that you need. a message about HTTPS is displayed if the certificate from the server is not trusted. If your installation does not have a separate front-end dispatcher.5. and then click Next. Otherwise. use the host name of the front-end dispatcher. f. if you want to use the InfoSphere Business Glossary Data Model Integration feature. v InfoSphere Business Glossary Data Model Integration Note: If you are using Eclipse 3. h. Other Internet Explorer versions might require slightly different steps. click Continue to this website (Not recommended). c.509 (.. e. type the connection information to connect to the IBM InfoSphere Business Glossary browser. InfoSphere Data Architect or IBM Rational Software Architect). Click Certificate Error at the top of the window. use the host name of the services tier computer. then the first time that you connect to the server. use the HTTPS port of the front-end dispatcher if it is configured for HTTPS. 8. Click Install. If your installation does not have a separate front-end dispatcher. Open Microsoft Windows Internet Explorer. The certificate name with its full directory path are needed in a later step. Click the Details tab. Make sure to select the check boxes for all of the dependent features. Click Copy to File. If the InfoSphere Information Server host that you connect to uses HTTPS. Use the following format: https://host_server:port/bg host_server If your installation has a separate front-end dispatcher. select the check boxes for the following features: v InfoSphere Business Glossary Core feature v InfoSphere Business Glossary UML Profile feature. If you receive such a message. e. go to the directory of the JRE binary that is associated with the Eclipse application that you use (for example. use the HTTP port of the front-end dispatcher. Chapter 14. then click View certificates. 7. In a command prompt window.. Follow the remaining prompts to finish the installation. In the address field. b. Installing components that are not in the suite installation program 223 .

Check that Business Glossary is one of the Preference page titles listed in the left pane. An example of the command might be keytool -import -v -file "C:\SSL\bge_certificate" -keystore . 3. You must enclose the file in quotation marks (").\lib\security\cacerts The keystore utility accesses the certificate and prepares to import it. Follow the instructions in the online help to fill out the connection settings. Run the command: keytool -import -v -file "certificate_name" -keystore . Then review the documentation to learn how to use the client. type Y. Enter the following information: 1) At the Enter keystore password prompt. What to do next Validate that InfoSphere Business Glossary Client for Eclipse is installed and configure the client to connect to InfoSphere Business Glossary. If it is visible. Installation. then InfoSphere Business Glossary Client for Eclipse has been installed.\lib\security\cacerts The file certificate_name is the certificate name with its full directory path. select Window > Preferences to see the list of available Preference page titles. 4. To connect to InfoSphere Business Glossary: 1. Press F1 or click the Help icon ? to display the online help for the connection settings page. Installing z/OS components for IBM InfoSphere DataStage MVS Edition To compile and run IBM InfoSphere DataStage jobs on a server that runs IBM z/OS. select Window > Preferences to see the list of available Preference page titles.. 3. An example of the directory might be C:\Program Files\IBM\SDP\jdk\jre\ bin. and Configuration Guide . To learn how to use the client. From the list of Preference page titles. Start your Eclipse application if it is not already started. 2. 2. To validate that the InfoSphere Business Glossary Client for Eclipse is installed: 1. 224 Planning. Start your Eclipse application. you must first install COBOL copybook files and the Runtime Library (RTL). i. click Business Glossary. 2) At the Trust this certificate prompt. From the menu bar. The certificate is installed and added to the keystore. type changeit. Results The features that you selected are installed. review the documentation by selecting Help > Help Contents > IBM InfoSphere Business Glossary Client for Eclipse. 5. From the menu bar..

cob ARDTIMSG ArdtMsg1. In the SYSLIB DD statement of each COBCOMP step. Copybook to copylib associations Copy these files To these copylib members ArdtIMSg. See “Installing COBOL copybook files.cob RTLMSGS 2.cob ARDTUCOD ArdtUDat. Start the Designer client. The library contains routines that are used when a job is run. the files are in the Mainframe Components directory.cob ARDTUFDF RTLMsgs. DB2CompileLinkBind. The IVP validates that a z/OS environment is configured for compiling and running z/OS jobs. Procedure To install the components: 1. Table 86. Using FTP. specify the name of the copylib that contains the uploaded copybook files. Installing components that are not in the suite installation program 225 . See “Installing the runtime library for z/OS jobs” on page 226. Under the Tools menu option.cob ARDTMSG2 ArdtUBgn. specify the copylib. a. b. On the installation media.cob ARDTMSG1 ArdtMsg2. edit the CompileLink. Chapter 14.” 2. upload the COBOL copybook files to copylib members. Install the runtime library for z/OS jobs.cob ARDTUEND ArtdtUFct.cob ARDTUFCT ArtdtuFdf. In the JCL templates for compiling the COBOL program. Procedure 1. Run the installation verification process (IVP). Installing COBOL copybook files Upload the COBOL copybook files to add them as members of a copybook library (copylib). 3.cob ARDTUBGN ArdtUCod. Upload the COBOL copybook files to add them as members of a copybook library (copylib). See “Installation verification process for z/OS components” on page 227. Copylib members The copylib members for IBM InfoSphere DataStage contain message text or code templates that you can customize. and TDCompileLink JCL templates.cob ARDTUDAT ArdtUEnd. c.

access function 3. Installing the runtime library for z/OS jobs The runtime library for z/OS jobs contains routines that are used when a job is run. b. type a data set name. ARDTUFDF FD statements at the end of the FILE SECTION in the DATA DIVISION. such as SELECT. Tab to the Data Set Name prompt. and press Enter. a. In the Allocate New Data Set panel. Log in to the computer that runs z/OS. For example. ARDTUFCT Statements. In the Allocate New Data Set panel. c.2 (Data Set Utility). e. Table 87. Copylib members that can control the operation of generated COBOL programs copylib member Adds ARDTUBGN Program initialization code for the generated COBOL program. type A. d. Message text The following table describes copylib members that contain runtime message text. 2. you can add WORKING-STORAGE variables and a LINKAGE SECTION. ARDTUDAT Code before the PROCEDURE DIVISION statement of the generated COBOL program. Procedure 1. In ISPF. type TRKS. In the Option line. Table 88. Allocate a runtime library data set. type the following values: Field Value Primary quantity 10 Secondary quantity 10 Directory blocks 0 Record format FB 226 Planning. in the Space units field. and Configuration Guide . ARDTUEND Program termination code before each GOBACK statement. ARDTUCOD Paragraphs to the end of the generated COBOL program. to the end of FILE-CONTROL paragraph in the ENVIRONMENT division. Copylib members with message text that you can customize copylib member Customizes ARDTIMSG Message text for IMS™ DB errors ARDTMSG1 Message text that displays after a job runs ARDTMSG2 Message text about file processing errors RTLMSGS Message text about errors and warnings that the runtime library generates Templates The following table describes copylib members that can control the initialization or termination of the generated COBOL program for a job. Installation.

change the DSN value to the name of the link library to contain the contents of the InfoSphere DataStage runtime library. Start the Designer client. In the LKED step. Field Value Record length 80 Block size 3120 3. Transfer the runtime library data file to the allocated runtime library data set. Installing components that are not in the suite installation program 227 . b. start FTP. This output data set is a sequential file that is used by the job that you create and run in steps 5. 6. Transfer the file ArdtRTL. b. 8. 5. and 7. a. a. On your workstation. change the ARDTLIB DD statement to use the data set name that you specified in the PDS2 statement in Step 6c. b. The installation verification process uses IBM InfoSphere DataStage jobs to validate a z/OS environment. This file contains sample JCL to create the runtime library. Use the PUT command to send the ArdtRTL. Connect to the computer that runs z/OS and log in. Run the TSO RECEIVE command: RECEIVE INDA('input_dataset_name') input_dataset_name is the data set that you specified in Step 2. The output data set is the source data set for an IEBCOPY operation. 6. 7. Set the transfer mode to BIN. change the DSN value to the name of the output data set that the TSO RECEIVE command creates in Step 4b. On the computer that runs z/OS. a. 9. At the prompt. start FTP.data file to the allocated runtime library data set. On your workstation. The link library is the target for the IEBCOPY operation. In the PDS2 statement. type DA('output_dataset_name') output_dataset_name is the name of the data set that the TSO RECEIVE command creates. Chapter 14. edit the JCL library member specified in step 5d. On the computer that runs z/OS. Modify the JOB statement to meet your site standards. Edit the JCL templates for CompileLink and DB2CompileLinkBind. Set the transfer mode to ASCII. Submit the JCL file from the previous step to copy the data set to the link library. d. b. Use the PUT command to send the ArdtRTL. 4. receive the runtime library data set. a. Installation verification process for z/OS components The installation verification Process (IVP) validates that a z/OS environment is configured for compiling and running z/OS jobs. d. Connect to the computer that runs z/OS and log in.jcl to z/OS. This file contains the IBM InfoSphere DataStage runtime library in binary format.jcl file to a member of a JCL library. c. c. c. In the SEQ1 statement.

For information about installing and running the installation verification process. see the \Utilities\Supported\IVP\IVP Installation Instructions. InfoSphere Blueprint Director strengthens the alignment of business and information technology by enabling the business and IT teams to collaborate on actionable information blueprints that connect the business vision with the corresponding technical metadata. and Configuration Guide . In the Blueprint directory. Procedure 1. InfoSphere Blueprint Director directs the team to apply best practices based on reference architectures and methodology. The release notes are located in the same directory as the InfoSphere Blueprint Director setup program. For complete details about system requirements and compatible software. In the InfoSphere Information Server installation directory. Job Purpose IVPFLAT Tests the runtime library. Follow the instructions in the release notes to install InfoSphere Blueprint Director. About this task When you install IBM InfoSphere Information Server on a computer that is running Microsoft Windows. The User's Guide is located in the same directory as the InfoSphere Blueprint Director setup program. Installing IBM InfoSphere Blueprint Director IBM InfoSphere Blueprint Director is included with IBM InfoSphere Information Server. locate the Blueprint directory. Before you begin InfoSphere Blueprint Director is supported in Microsoft Windows environments. 228 Planning. IVPDB2 Tests connectivity to IBM DB2 for z/OS and the runtime library.doc file on the installation media. 2. the installation program creates a directory that contains the InfoSphere Blueprint Director documentation and setup program. locate the release notes. What to do next To learn how to configure and use InfoSphere Blueprint Director. IVPIMS Tests connectivity to the IMS database and the runtime library. Installation. read the release notes. Results InfoSphere Blueprint Director is installed. see the help or the IBM InfoSphere Blueprint Director User's Guide. This directory is created on the client tiers and for all product modules and components.

Configuring the software after installation To finish setting up IBM InfoSphere Information Server. complete the tasks that correspond to the product modules that you installed or the features that you want to enable. 2005. For additional setup steps.Part 4. © Copyright IBM Corp. see the documentation for your specific product modules. 2010 229 .

and Configuration Guide . Installation.230 Planning.

exe Data set management for IBM InfoSphere DataStage and QualityStage Designer C:\IBM\InformationServer\ASBNode\apps\ Processes used to run Java programs. Unless otherwise noted. The default location of these files is C:\IBM\InformationServer\Clients\Classic\.exe C:\IBM\InformationServer\Clients\ InfoSphere Information Server Manager istools\cli\istool. 2010 231 . set up firewall exceptions for the following executable files. However. the default location of these files is C:\IBM\ InformationServer\Clients\Classic\. For normal client use.exe Command-line administration tool dscc. you can avoid specifying firewall exceptions by opening ports when you prepare a Microsoft Windows computer for installation. 2005.exe Information Services Director console and IBM InfoSphere Information Analyzer console C:\IBM\InformationServer\Clients\ IBM InfoSphere Information Server Manager istools\manager\manager.exe IBM InfoSphere DataStage and QualityStage Designer dsviewer.exe C:\IBM\InformationServer\Clients\ Program that runs the IBM InfoSphere Classic\ISC\isc. you might prefer to set up explicit firewall exceptions for client-side executable files that require network access.bat command-line interface For stand-alone tools. Firewall exceptions for client-side executable files (Windows) In most cases. Firewall exceptions for stand-alone tools Executable file Description diffapicmdline. Table 90.Chapter 15.exe dsadmin. Firewall exceptions for normal client use Executable file Description admin. Table 89.exe Command-line export tool © Copyright IBM Corp. These jre\bin\java.exe Multi-job compiler used by IBM InfoSphere DataStage and QualityStage Designer DSDesign.exe IBM InfoSphere DataStage and QualityStage Administrator director.exe processes are needed by all clients.exe IBM InfoSphere DataStage and QualityStage Director DSCompilerWizard.exe Compare command-line tool dsdiffexporter. C:\IBM\InformationServer\ASBNode\apps\ jre\bin\javaw. set up firewall exceptions for the following executable files.exe Command-line compiler tool dscmdexport.

exe Command-line job administration tool NLVAdmin. Table 90.exe Import tool dsjob.exe Command-line import tool dsexport.exe XML table definition importer XMLMDImporter.exe Metadata importer utility XMLImporter. and Configuration Guide . Firewall exceptions for stand-alone tools (continued) Executable file Description dscmdimport.exe Support tool for switching to English for a non-English installation XMDICmd.exe 232 Planning. Installation.exe Export tool dsimport.

you must enable SSL. v For cluster installations. see the IBM InfoSphere Information Server Administration Guide. v For IBM WebSphere Application Server Network Deployment. For information about starting application server processes. you can optionally enable SSL for RMI/IIOP by using the IBM WebSphere Application Server administrative console. start the WebSphere Application Server deployment manager by running the startManager command. Enablement of Secure Sockets Layer (SSL) After running the installation program.1 and 7. Version 8. For example. select SSL-supported.sh/bat script. when a certificate expires or. Select the SSL settings that correspond to an SSL transport. Log in to the WebSphere Application Server administrative console. Version 6. Click RMI/IIOP security → CSIv2 inbound transport. In the Authentication area.1: a. ensure that all node agents are up and running. you must enable SSL after installing Version 8. v For stand-alone installations: – Linux UNIX Start WebSphere Application Server by running the MetadataServer. in a cluster environment. 2010 233 . – Windows Start WebSphere Application Server by starting the Microsoft Windows service. © Copyright IBM Corp. under Transport. For information about starting application server processes. Remember: You must run the UpdateSignerCerts tool on all client systems when any SSL changes occur in the cell. Click Security → Global Security. After you install or upgrade to Version 8. Start the WebSphere Application Server processes. see the IBM InfoSphere Information Server Administration Guide.0: a. you must run the tool on every client system. Enabling SSL for inbound RMI/IIOP In IBM InfoSphere Information Server.5. select the type of transport and the SSL settings. you can enable Secure Sockets Layer (SSL) for IBM WebSphere Application Server.5. b. c. If you prefer to use SSL or if your system requires confidentiality at the EJB level. 2005. About this task If you are upgrading from a previous version of InfoSphere Information Server that used SSL and you want to continue using SSL. Version 7. In a cluster environment. To set up your security settings: v For IBM WebSphere Application Server Network Deployment. 2. Versions 6. You can also configure your environment to use secure HTTP (HTTPS) communication with the services tier. applications.Chapter 16. Procedure 1.0. and infrastructure. Click Security → Secure administration. SSL for RMI/IIOP is disabled by default. when you add a managed node to the cell.5. In the General Properties area.

when SSL is first enabled. For more information about starting application server processes. (Client tier. Manually configuring InfoSphere Information Server components to use HTTPS If the installation program did not configure HTTPS for a tier computer during IBM InfoSphere Information Server installation. Procedure 1. About this task The services and engine tiers are properly configured for HTTPS if you select HTTPS during the installation of these tiers. Click RMI/IIOP security → CSIv2 inbound communications. and Configuration Guide . you can manually configure HTTPS communications as described in this procedure. Windows v installdir\ASBServer\conf v installdir\ASBNode\conf v The typical installdir is C:\IBM\InformationServer. click Transport → SSL-supported. See “Running UpdateSignerCerts after enabling SSL or changing SSL at the cell level” on page 236. where installdir is the location of your InfoSphere Information Server installation directory: Linux UNIX v installdir/ASBServer/conf v installdir/ASBNode/conf The typical installdir is /opt/IBM/InformationServer. v For cluster installations. select the type of transport and the SSL settings. c. What to do next Run the IBM InfoSphere Information Server UpdateSignerCerts tool on every client system. Store the file in the following locations. for example. 234 Planning. v For stand-alone installations. Select the SSL settings that correspond to an SSL transport. or a new managed node is added to the cluster. and services tier computers) Create an empty text file called https. restart the WebSphere Application Server process. follow this procedure to manually configure HTTPS for that tier computer. node agents. restart all the WebSphere Application Server processes in the cell by stopping all application servers. all node agents. Stop and restart all WebSphere Application Server processes. Each client tier must be manually configured to enable HTTPS communications with the services tier. You must run this tool whenever an SSL-related change occurs in the cell. If you did not select HTTPS during the installation of these tiers. In the Authentication area. Installation. and then the Deployment Manager. In the CSIv2 Transport Layer area. b. Then start the Deployment Manager. 3. 4. engine tier. see the IBM InfoSphere Information Server Administration Guide. Click OK and save all changes. and then all application servers. or a server certificate expires.conf.

port" persistent="true" readonly="true" value="80"/> c.http. d. In the file. locate the following XML element: <PersistedVariable encrypted="false" name="isf. You can find this file in the following location: v Linux UNIX installdir/ASBNode/eclipse/plugins/ com.ibm. b. You can find this file in the following location: v Linux UNIX installdir/ASBServer/conf/ v Windows installdir\ASBServer\conf\ Edit the file as follows: a. Modify the port for all <asb-server> elements to reflect the secure port for the services tier. 2. 5. engine tier.client_8.console. Save your changes. and services tier computers) Use the updateSignerCerts command to install the HTTPS certificate on the computer. (Client tier.0 Chapter 16. 3.5. b.xml files: v The file that is on the server that hosts the engine tier v The file that is on the server that hosts the services tier On each server. Open the file in a text editor.isf. (Engine tier computer) Modify the registered-servers.xml file. Note: The ASBServer directory is present only if the computer hosts the services tier. (Services tier computer) Modify the registered-servers.port" persistent="true" readonly="true" value="port" /> g. In the file. Enablement of Secure Sockets Layer (SSL) 235 . locate the following XML element: <PersistedVariable encrypted="false" name="is.xml file is located in the IBM InfoSphere Information Server installation directory.xml file.0. These files contain the installation records that are used by the installation program.isf. In the file.xml files.xml file. Change the value attribute to true. Update the following Version. Keeping these files current avoids problems with future installations.ibm.0 v Windows installdir\ASBNode\eclipse\plugins\ com. 4.xml file.5. See “Running UpdateSignerCerts after enabling SSL or changing SSL at the cell level” on page 236. In the file. locate the following XML element: <PersistedVariable encrypted="false" name="is. Update the port value. locate the following XML element: <asb-server name="host" host-name="host" port="9080" is-primary-server="true" /> There might be multiple <asb-server> elements in the registered- servers. Change the value attribute to the HTTPS port number. f. d.client_8. Change the value attribute to the HTTPS port number.https" persistent="true" readonly="true" value="false"/> e.0.Edit each file as follows: a. Use a text editor to open the Version. c. (Engine tier and services tier computers) Update the port value in the Version. the Version.

Optional: (Client tier computers) Modify the registered-servers.xml file. the old host name and port continue to display in the lists in some client application login pages unless you modify the registered-servers. locate the following XML element: <asb-server name="host" host-name="host" port="9080" is-primary-server="true" /> There might be multiple <asb-server> elements in the registered- servers. Change each item so it uses https:// instead of http://. Also run the UpdateSignerCerts tool whenever an SSL change occurs in an IBM WebSphere Application Server cell. In the file. and so it references the HTTPS port instead of the HTTP port. Examples of changes include when server certificates expire or when a new managed node is added to a WebSphere Application Server cluster. The list of servers in these files is used to populate the server lists in the login pages for some client applications. Modify the port for all <asb-server> elements to reflect the secure port for the services tier. To retrieve the certificate.xml file. Note: On client-only computers. b. run the UpdateSignerCerts tool. Modify the file in either of the following ways: v Change the file in the same way that you modified the registered- servers.sh -remove -hostname host -port port – Windows cd installdir\ASBNode\bin RegistrationCommand. 236 Planning.bat -remove -hostname host -port port 7. the is-primary-server="true" attribute does not appear in the <asb-server> element. Save your changes./RegistrationCommand.xml file on the computer. run the RegistrationCommand command as follows: – Linux UNIX cd installdir/ASBNode/bin . c. (Client tier computers) Update the browser bookmarks and URL shortcuts. Alternatively. and Configuration Guide . However.xml files on the engine tier computers. you must retrieve the certificate from the server. Running UpdateSignerCerts after enabling SSL or changing SSL at the cell level To enable SSL on a computer. v To remove old server entries. Edit the file as follows: a. you can enter the new value in the login page the next time you log in. d. 6. Installation. Update the port value. Open the file in a text editor. You can update these files if you want to have the updated port values shown on the next login attempt.

clustered WebSphere The following path on the computer that Application Server environment hosts the Deployment Manager: v Linux UNIX installdir/ASBServer/bin v Windows installdir\ASBServer\bin Services tier computer. After installing a new IBM New client tiers and new Stand-alone and cluster InfoSphere Information engine tiers (only if SSL is configurations of WebSphere Server client or engine tier. Table 91. Enablement of Secure Sockets Layer (SSL) 237 . Procedure 1. The location depends upon which computer you are running it on and how WebSphere Application Server is configured: Computer and configuration Run UpdateSignerCerts from this location Services tier computer. engine tiers. When and where to run the UpdateSignerCerts tool When to run the Where to run the WebSphere Application UpdateSignerCerts tool UpdateSignerCerts tool Server configurations After reenabling SSL for Client tiers.About this task The following table describes when and where to run the UpdateSignerCerts tool. enabled) Application Server After adding a new managed Client tiers. After replacing or updating a Client tiers. and Stand-alone and cluster RMI/IIOP or HTTPS for the services tiers. engine tiers. and WebSphere Application node to the cluster and a services tiers (only if SSL is Server cluster configuration new custom profile is created enabled) only (horizontal clustering). engine tiers. configurations of WebSphere first time (after a new Application Server installation or after an upgrade). The following table indicates the location from which to run the tool. non-clustered The following path on the services tier (stand-alone) WebSphere Application Server computer: environment v Linux UNIX installdir/ASBServer/bin v Windows installdir\ASBServer\bin Engine tier computers The following path on each engine tier computer: v Linux UNIX installdir/ASBNode/bin v Windows installdir\ASBNode\bin Chapter 16. Change to the directory in which the UpdateSignerCerts tool is located. and Stand-alone and cluster server certificate (for services tiers configurations of WebSphere example. when a certificate Application Server expires).

use the host name of the services tier computer. 2.sh –host host_name –port port_number v Windows UpdateSignerCerts. This is the host and port that were specified during the services tier or engine tier installation unless the registered-servers. This is the host and port that were 238 Planning. the tool connects to the host and port that are designated as the primary-server in the registered-servers. the tool connects to the host and port that are designated as the primary-server in the registered-servers. depending on your configuration: When the tool is run on a computer that hosts the services tier (other tiers might or might not be installed on the same computer): If the tool is run from the ASBServer/bin directory. Installation. Computer and configuration Run UpdateSignerCerts from this location Client tier computers The following path on each client tier computer: v Linux UNIX installdir/ASBNode/bin v Windows installdir\ASBNode\bin Metadata repository tier computer You do not need to run the tool on this computer. If your installation does not have a separate front-end dispatcher. v Linux UNIX . If you do not specify a -host or -port value. When the tool is run on a computer that hosts an engine tier (other tiers might or might not be installed on the same computer): If the tool is run from the ASBNode/bin directory.xml file. Accept the certificate to let the tool finish its tasks. use the WebSphere Application Server secure transport port if HTTPS is configured. use the host name of the front-end dispatcher.xml file was manually updated because of a change in the front-end dispatcher or a change in the HTTP or HTTPS port for the services tier. These values might or might not work. the tool might prompt you to accept an HTTPS certificate. and Configuration Guide . Note: If HTTPS is used. -port port_number If your installation has a separate front-end dispatcher./UpdateSignerCerts. run the UpdateSignerCerts tool in both the ASBServer/bin and ASBNode/bin directories on the computer. If your installation does not have a separate front-end dispatcher.bat –host host_name –port port_number -host host_name If your installation has a separate front-end dispatcher. If the computer that hosts the services tier also has the engine tier or client tier installed on it. or the HTTP transport port if HTTPS is not configured. use the HTTP port of the front-end dispatcher. Otherwise. the tool uses the following set of default values.xml file. use the HTTPS port of the front-end dispatcher if it is configured for HTTPS. Use the following command to run the UpdateSignerCerts tool.

all signer certificates must be stored in the CellDefaultTrustStore truststore.ibm. Version 7. you can replace a certificate by completing the steps in the following technote: http://www.wss?rs=180&uid=swg21305596.1. When the tool is run on a client tier computer without an engine tier installed on the same computer: The -host and -port values are mandatory.html.com/infocenter/wasinfo/v7r0/ index. Enablement of Secure Sockets Layer (SSL) 239 . you can replace a certificate with your own certificate. About this task In clustered IBM InfoSphere Information Server installations. when certificates expire or if the nodes are out of synchronization. Log in to the WebSphere Application Server administrative console. In a stand-alone environment. In the WebSphere Application Server administrative console. Version 6.com/support/ docview.boulder. In a clustered environment. click Security → SSL certificate and key management → Manage endpoint security configurations. Procedure 1.doc/info/iseries/ae/ tsec_7renewcecacert. use the startManager command to start the deployment manager. you replace an expired certificate with another certificate that is generated by WebSphere Application Server. In stand-alone InfoSphere Information Server installations. specified during the services tier or engine tier installation unless the registered-servers. You can renew self-signed certificates and chained certificates by completing the steps in the following WebSphere Application Server documentation: http://publib. In WebSphere Application Server. b. Refer to the WebSphere Application Server documentation for details. or you can use a certificate signed by a certificate authority. 3. or to use your own certificate. WebSphere Application Server generates a new certificate that replaces the old certificate. 2. use the MetadataServer. you can renew certificates. Chapter 16. Note: In these steps.ibm. all signer certificates must be stored in the NodeDefaultTrustStore truststore.xml file was manually updated because of a change in the front-end dispatcher or a change in the HTTP or HTTPS port for the services tier.base. In WebSphere Application Server.iseries.0. This configuration is the default for WebSphere Application Server. Replacing WebSphere Application Server certificates To replace a certificate before it expires.websphere.ibm. Alternatively.sh/bat script to start the application server. a. Expand Inbound and click the node that uses the default certificate that you want to replace. you can replace an IBM WebSphere Application Server certificate by specifying a different certificate for each and any endpoint.jsp?topic=/com.

and Configuration Guide . Switching from HTTPS back to HTTP If your IBM InfoSphere Information Server installation is configured for secure HTTP (HTTPS).xml file. You can create a self-signed certificate generated by WebSphere Application Server. and services tiers. Installation. refer to “Running UpdateSignerCerts after enabling SSL or changing SSL at the cell level” on page 236. Specify an alias. click the node again. 2. The files are found in the following locations. Keeping these files current avoids problems with future installations. Windows v installdir\ASBServer\conf v installdir\ASBNode\conf The typical installdir is C:\IBM\InformationServer. 6. Click OK and Save. engine tier. 240 Planning. engine tiers.xml files. Procedure 1. 8. For more information. 7. 4. Click OK and Save. These files contain the installation records that are used by the installation program. and then click Manage certificates to view the old and new certificates. 9. you can configure it to use HTTP instead.Edit each file as follows: a. Select the new certificate and select the Delete old certificate and Delete old signers check boxes. the Version. and organization for the new certificate.xml file is located in the IBM InfoSphere Information Server installation directory. (Client tier. Update these Version. Click Manage certificates.xml files: v The file that is on the server that hosts the engine tier v The file that is on the server that hosts the services tier On each server. On the Manage endpoint security configuration page. Stop and restart all IBM WebSphere Application Server Network Deployment processes. or import an existing certificate. 10.conf files. Select the old certificate and click Replace. (Engine tier and services tier computers) Change the port value in the Version. Use a text editor to open the Version. Complete the form. Note: The ASBServer directory is present only if the computer hosts the services tier. see the IBM InfoSphere Information Server Administration Guide What to do next Run the UpdateSignerCerts tool on the client tiers. receive a certificate from a certificate authority. For more information about restarting application server processes. common name. Click Create a self-signed certificate. where installdir is the location of your InfoSphere Information Server installation directory: Linux UNIX v installdir/ASBServer/conf v installdir/ASBNode/conf The typical installdir is /opt/IBM/InformationServer. and services tier computers) Delete the https. 5.

b. Open the file in a text editor.http. locate the following XML element: <asb-server name="host" host-name="host" port="port" is-primary-server="true" /> There might be multiple <asb-server> elements in the registered- servers. d. Save your changes. Modify the port for all <asb-server> elements to reflect the HTTP port for the services tier. Change the value attribute to false. (Services tier computer) Modify the registered-servers. The list of servers in these files is used to populate the server lists in the login windows for some client applications. Save your changes.ibm. You can update these Chapter 16. In the file.https" persistent="true" readonly="true" value="true"/> e. Open the file in a text editor. Update the port value.xml file.isf. d.0 v Windows installdir\ASBNode\eclipse\plugins\ com. In the file.0. You can find this file in the following location: v Linux UNIX installdir/ASBNode/eclipse/plugins/ com.xml file. d.port" persistent="true" readonly="true" value="port" /> c.0 Edit the file as follows: a.client_8.ibm. In the file. locate the following XML element: <PersistedVariable encrypted="false" name="is. b.port" persistent="true" readonly="true" value="port" /> g.xml file. c. 5. Modify the port for all <asb-server> elements to reflect the HTTP port for the services tier. c. You can find this file in the following location: v Linux UNIX installdir/ASBServer/conf/ v Windows installdir\ASBServer\conf\ Edit the file as follows: a. (Engine tier computer) Modify the registered-servers. 3. 4. Optional: (Optional. locate the following XML element: <PersistedVariable encrypted="false" name="is. In the file. Update the port value. Change the value attribute to the HTTP port to use. b. In the file.xml file. Change the value attribute to the HTTP port to use. Enablement of Secure Sockets Layer (SSL) 241 . for client tier computers) Modify the registered- servers. f.5.5. locate the following XML element: <asb-server name="host" host-name="host" port="port" is-primary-server="true" /> There might be multiple <asb-server> elements in the registered- servers.console.client_8.isf.0.xml file. locate the following XML element: <PersistedVariable encrypted="false" name="isf.

(Client tier computers) Update the browser bookmarks and URL shortcuts. you can enter the new value in the login window the next time you log in. run the RegistrationCommand command as follows: – Linux UNIX cd installdir/ASBNode/bin . the old host name and port are still listed in some client application login windows unless you modify the registered-servers. Modify the file in either of the following ways: v Change the file in the same way that you modified the registered- servers. files if you want to have the updated port values shown on the next login attempt. v To remove old server entries. and so it includes the HTTP port instead of the HTTPS port. the is-primary-server="true" attribute is not included in the <asb-server> element./RegistrationCommand. Change each item so it uses http:// instead of https://.sh -remove -hostname host -port port – Windows cd installdir\ASBNode\bin RegistrationCommand. Installation. Note: On client-only computers.xml files on the engine tier computers. However. 242 Planning. and Configuration Guide .bat -remove -hostname host -port port 6.xml file on the computer. Alternatively.

also enable Secure Sockets Layer (SSL) communication. you might have to map credentials between the InfoSphere Information Server user registry and the local operating system user registry on the computer where the engine is installed. and configure the Auditing service. 2010 243 . As part of security setup. choose a user registry configuration. About this task The following list outlines the tasks that you do to set up security for IBM InfoSphere Information Server. Some suite components also require that you assign project-specific roles to users. 5. For details on doing each task. By default. Configuring security for IBM InfoSphere Information Server To configure security. create users and groups by using the InfoSphere Information Server console or the InfoSphere Information Server Web console. you can optionally enable SSL for RMI/IIOP by using the WebSphere Application Server administrative console. Configure InfoSphere Information Server engine security. To log in to InfoSphere Information Server. 4. If the user registry configuration that you choose cannot be shared between the services tier and engine tier. set up the registry. The installation program configures InfoSphere Information Server to use its internal user registry. If InfoSphere Information Server is configured to use an external user registry. Optionally. Depending upon your user registry configuration. also map credentials between the user registry that is used by InfoSphere Information Server and the user registry that is used by the engine. Create users and groups in the user registry. 6. If InfoSphere Information Server is configured to use the internal user registry. Assign security roles to users and groups. Choose a user registry and configure it for InfoSphere Information Server. you can also configure the tier by using a manual procedure. Procedure 1. Assign project roles if required by the installed suite components.Chapter 17. 3. 7. A user registry contains valid user names and passwords. Assign project roles to users. and assign security roles to those users. © Copyright IBM Corp. use standard operating system utilities or user registry utilities. configure IBM WebSphere Application Server or InfoSphere Information Server agents for non-root administration. a user must have a user name and password in the user registry. WebSphere Application Server runs as root. refer to the IBM InfoSphere Information Server Administration Guide. The InfoSphere Information Server engine performs user authentication separately from other InfoSphere Information Server components. 2005. Security roles determine which suite components each user or group has access to and what level of access that user or group has in the suite component. create users. 2. you can configure InfoSphere Information Server to use an external user registry such as the local operating system user registry or a Lightweight Directory Access Protocol (LDAP) user registry. Optional: Configure IBM WebSphere Application Server for non-root administration. After running the installation program. If the installation program did not configure a tier for HTTPS. Optional: Enable Secure Sockets Layer (SSL) communication.

You can configure which audit events to log and how much information to include based on your auditing requirements. they can also be run by using a non-root user ID. You can configure and set appropriate file system permissions for the agents to "run-as" a non-root user ID. and Configuration Guide . 244 Planning. You can configure and set appropriate file system permissions for WebSphere Application Server to "run-as" a non-root user ID. Optional: Configure InfoSphere Information Server agents for non-root administration. the InfoSphere Information Server agents (such as the ASB and logging agents) run as root. Installation. By default. These events include all security-related settings changes and user login and logout operations. it can also be run by using a non-root user ID. 8. 9. The Auditing service creates an audit trail of security-related events. Optional: Configure the Auditing service. However. However.

© Copyright IBM Corp. “Configuring a parallel processing environment. Procedure Do the following tasks to configure and administer IBM InfoSphere DataStage and IBM InfoSphere QualityStage. 2010 245 . Linux UNIX Ensure that InfoSphere DataStage users have the correct localization settings. Configure database connectivity. lock table entries. also map credentials between the user registry that is used by InfoSphere Information Server and the user registry that is used by the engine. and configure the parallel engine. 1. you must perform several configuration tasks. See “Tuning the InfoSphere Information Server engine for large numbers of users or jobs (Windows Server)” on page 252.Chapter 18. 2. configure the server engine to support the required number of open files. Optional: Configure the IBM InfoSphere QualityStage Match Designer. ensure that IBM InfoSphere DataStage users have the correct settings specified for localization. Set environment variables for the parallel engine. Configuring product modules in the suite Depending on which products you installed or the tasks that you want to complete. See “Configuring IBM InfoSphere QualityStage Match Designer” on page 253. To tune the engine. See Chapter 19. The drivers are installed with the client tier or the engine tier. 2005. 7. 6. Migrate jobs that you created in an earlier version of InfoSphere DataStage to the current version. See Chapter 17. 3. The IBM InfoSphere QualityStage Match Designer requires an ODBC data source name (DSN) to connect to the database where the Match Designer stores match pass results. Optional: Migrate jobs. ensure that a new or existing supported database is available to receive test pass results for the Match Designer. Windows Optional: Tune the server engine. Configure security. “Configuring security for IBM InfoSphere Information Server. Configuring IBM InfoSphere DataStage and IBM InfoSphere QualityStage Before you use IBM InfoSphere DataStage and IBM InfoSphere QualityStage. 5. If you intend to develop InfoSphere QualityStage matches. you must complete some configuration tasks. set up the registry. create users. Also assign project-specific roles to users. 4.” on page 243. Configure access to ODBC data sources. For systems that have large numbers of simultaneously connected users or large numbers of simultaneously running jobs. Optional: Configure the parallel processing environment.” on page 261. If the user registry configuration that you choose cannot be shared between the services tier and engine tier. Configure the ODBC drivers to access ODBC data sources. Add computers to share engine processing. modify settings in the uvconfig file. and locks that are necessary for correct engine operation. and assign security roles to those users. If you installed globalization support (NLS). Choose a user registry configuration.

use the IBM InfoSphere DataStage and QualityStage Administrator client or the IBM InfoSphere DataStage and QualityStage Designer client. in some cases. for ISO8859-1. The investigation reports and Standardization Quality Assessment (SQA) reports can read data from a sequential file or a database table. See “Setting up application servers to run SQA or investigation reports” on page 253. you can edit the environment variables in the dsenv file. Determine the locale and encoding name to use. Procedure 1. 9. The encoding must correspond to one of the encodings that InfoSphere DataStage supports. Log in to the operating system as the user who ran the installation program. UNIX) In Linux or UNIX. 2. The environment variables in the dsenv file affect the entire InfoSphere DataStage environment. You must use the operating system-specific name for the encoding. or if a user set a private locale (for example. Perform this task as soon as possible after installation. use iso8859_1. Installation. The table gives the names of encodings as they appear to the InfoSphere Information Server engine. if you installed globalization support (NLS). and Configuration Guide .profile). However. Test the installation. test the installation by logging in to the Administrator and Designer clients. use the locale command: locale 246 Planning. See “Testing the installation of IBM InfoSphere QualityStage and IBM InfoSphere DataStage” on page 254. then you do not need to perform the steps that are described in this task. on Linux systems. The encoding names for the operating system might be slightly different. before any jobs are stored or compiled. You must set up the application server to find the applicable data source. To define the environment variables on a per-project or per-job basis. Ensuring that InfoSphere DataStage users have the correct localization settings (Linux. For example. 8. After you install and configure InfoSphere DataStage and InfoSphere QualityStage. If the user who performed the installation used this default and all InfoSphere DataStage users are expected to inherit the same default. the locale that is set for an InfoSphere DataStage user might be different from the locale that was set during installation. See “Character encodings supported by IBM InfoSphere Information Server” on page 158. To ensure that InfoSphere DataStage users have the correct locale and environment settings. See your operating system documentation for more information. For example. For example. ensure that IBM InfoSphere DataStage users have the correct settings specified for localization. the locale for individual users is set by using a system-wide default. Optional: Set up the application server to run SQA or investigation reports. in their $HOME/. To determine the current locale that is set for the server operating system. this default is defined in /etc/sysconfig/i18n. About this task On most systems. this problem might occur if the user who performed the installation used a locale that was not the default.

Configuring the dsenv file: Linux UNIX Chapter 18. 6. Restart the InfoSphere Information Server engine.export LC_NUMERIC LC_TIME="ja_JP.utf8". Save the file.utf8".config files to set up access to ODBC data sources. Wire protocol drivers require information about the database itself.export LC_ALL LC_CTYPE="ja_JP. #LANG="langdef".utf8".export LANG LC_ALL="ja_JP.utf8".export LC_MONETARY LC_NUMERIC="ja_JP. see the DataDirect Connect and Connect XE for ODBC Reference manual (a PDF file) in the $DSHOME/Server/branded_odbc/books/odbc directory. Replace the occurrences of langdef with the locale and encoding name that were specified during installation. the following settings specify that the locale is ja_JP and the encoding is UTF-8: LANG="ja_JP. Non-wire drivers require information about the location of the database client software.export LC_TIME #LC_MESSAGES="langdef". export LC_MESSAGES 4.ini.export LANG #LC_ALL="langdef".export LC_NUMERIC #LC_TIME="langdef". Also review the odbcread. UNIX) If you installed Linux or UNIX ODBC drivers. 3.export LC_MONETARY #LC_NUMERIC="langdef".export LC_COLLATE LC_MONETARY="ja_JP. By default. Non-wire protocol drivers require different setup information from wire drivers. For example.utf8".export LC_CTYPE #LC_COLLATE="langdef". Configuring product modules in the suite 247 .utf8".export LC_COLLATE #LC_MONETARY="langdef". you must configure the drivers to access ODBC data sources.export LC_TIME LC_MESSAGES="ja_JP. Linux. What to do next Before performing any work from the InfoSphere DataStage command line. Remove the comment marker (#) that is at the beginning of each line.utf8".utf8". Documentation for configuring the ODBC drivers is provided within this directory tree.export LC_CTYPE LC_COLLATE="ja_JP. export LC_MESSAGES 5.me file in the branded_odbc directory and an HTML file in the branded_odbc/odbchelp directory.export LC_ALL #LC_CTYPE="langdef". and UNIX operating systems. and uvodbc. this file is located in /opt/IBM/InformationServer/Server/DSEngine. $DSHOME/dsenv Configuring access to ODBC data sources You can configure ODBC access on Windows. Locate the following section in the dsenv file. The DataDirect Technologies Connect ODBC drivers are installed in install_home/Server/branded_odbc. Configuring ODBC access (Linux. odbc. InfoSphere DataStage users must issue the following command: . Edit the dsenv. For information about configuring the ODBC environment for a specific database.

See the data source documentation for more information. For some ODBC connections. Interactive users. and for interactions with external applications such as IBM WebSphere MQ. For a connection that uses a wire protocol driver. The file is located in $DSHOME/DSEngine. plug-ins. and Configuration Guide . $DSHOME identifies the InfoSphere DataStage installation directory. Edit the dsenv file. you do not have to modify the dsenv file. you must add environment variables to enable interactive use of ODBC drivers to make a connection to an ODBC data source.solnew2 export ONCONFIG LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$INFORMIXDIR/lib:$INFORMIXDIR/lib/ 248 Planning.3 INFORMIXDIR=/space/informix export INFORMIXDIR INFORMIXSERVER=solnew2. Before you begin You must be logged in as an InfoSphere DataStage administrator with the operating system credentials on the server for the InfoSphere DataStage administrator. Procedure 1. Installation. The entries vary slightly depending on your operating system. Back up the dsenv file before you edit it. and connectors. 2. Specify the following information in the dsenv file: v Environment variables for the database client software v Database home location v Database library directory Table 92. other programs. by operating system Operating system Library path environment variable IBM AIX LIBPATH HP-UX SHLIB_PATH HP-UX on Intel Itanium LD_LIBRARY_PATH Linux LD_LIBRARY_PATH Solaris LD_LIBRARY_PATH The following examples show typical entries for commonly used databases. Names of the library path environment variable. The default directory is /opt/IBM/InformationServer/Server/DSEngine. The dsenv file contains a series of shell arguments that are used when the engine starts.1 export INFORMIXSERVER ONCONFIG=onconfig. and scripts can use the dsenv file. Sybase 11 LANG= export LANG SYBASE=/export/home/sybase/sybase export SYBASE LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$SYBASE/lib:/usr/lib:/lib export LD_LIBRARY_PATH Informix® XPS 9. This lets IBM InfoSphere DataStage inherit the correct environment for ODBC connections.

config file and. 4.” on page 287. The /opt/IBM/InformationServer/Server/branded_odbc/IBM_Tools directory contains example odbc. Use the contents of these files to create the odbc.5 export DB2DIR DB2INSTANCE=db2inst1 export DB2INSTANCE INSTHOME=/export/home/db2inst1 export INSTHOME PATH=$PATH:$INSTHOME/sqllib/bin:$INSTHOME/sqllib/adm: $INSTHOME/sqllib/misc export PATH LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$INSTHOME/sqllib/lib export LD_LIBRARY_PATH THREADS_FLAG=native export THREADS_FLAG 3. About this task There are several copies of the uvodbc.5 DB2DIR=/opt/IBM/db2/V9. Create a soft link for the . See Chapter 20. IBM InfoSphere DataStage searches the current project directory for a uvodbc. use the command: ln -s odbc.ini Specifying data source names in the uvodbc.config file: <DSN_name> DBMSTYPE = ODBC Chapter 18.ini . “Stopping and starting the server engine. if it finds one.config file is also in each project directory. Stop and restart the IBM InfoSphere Information Server engine. Procedure 1.odbc.config file must specify the ODBC data source name (DSN) for each database.ini file must provide information about connecting to all the databases and database client applications that you use. the default path for projects on Linux is /opt/IBM/WDIS/Server/Projects.config file: Linux UNIX The uvodbc. v A copy of the uvodbc. In the <installation-directory>/Server/DSEngine folder. Configuring product modules in the suite 249 .ini file. This file arrangement allows you to configure data sources that are known to some projects but not others.odbc. By default.ini file to point to the odbc.ini file: Linux UNIX The odbc. For example.config file: v A copy is in the $DSHOME directory. Configuring the odbc.ini files for each supported Linux and UNIX platform. esql:$INFORMIXDIR/lib/cli export LD_LIBRARY_PATH LANG=C export LANG DB2 Version 9. uses this file instead of $DSHOME.ini file for the $DSHOME directory. Save your changes. Use this syntax to add entries to the uvodbc.

0. The following example shows a typical uvodbc. Red Brick®. you cannot use drivers from other vendors at the same time that you use the IBM InfoSphere DataStage drivers. In the dsenv file. you must bind it to each DB2 data source name (DSN). If you alter uvodbc. As a result. Installation. 3. Configuring other ODBC drivers: Linux UNIX You can use ODBC drivers from other vendors to connect to data sources. and change to the $DSHOME/./branded_odbc/bin directory.0. comment lines begin with a number sign (#).1 <Sybase1> DBMSTYPE = ODBC <Sybase2> DBMSTYPE = ODBC <Oracle8> DBMSTYPE = ODBC <Informix> DBMSTYPE = ODBC <DB2> DBMSTYPE = ODBC 2. Add comments only to the comment block that is at the top of the uvodbc.config file: [ODBC DATA SOURCES] <localuv> DBMSTYPE = UNIVERSE network = TCP/IP service = uvserver host = 127. Install the ODBC manager and drivers. copy the edited file to the project directories. You can use only one ODBC Manager at a time. You might be required to connect to a database not supported by the DataDirect driver pack. Use the documentation that the driver vendor provides. Comments that are not in the comment block at the top of the file cause processing errors.config after creating projects. where DSN_name is the ODBC DSN. 250 Planning. Type this command: bind22 dsn where dsn is the ODBC data source name. Procedure 1. 2.config file. 2. In the uvodbc. a. The space on each side of the equal sign is required. add the required environment variables. Creating and binding a DB2 package to a data source name: Linux UNIX To use a DB2 package.odbc. Procedure 1.. This name must be the same name that is specified in the . Specify your user ID and password. Configure the computer to connect to the driver.config file. and Configuration Guide . and you must perform some reconfiguration to switch between the two types. Open a terminal window. if you are prompted to provide them. for example.ini file.

After you install and configure the driver. 4. Chapter 18. Enter this command to obtain a list of available data source names: DS_CONNECT 5.) Edit the dsenv file and ensure that the path to the ODBC Manager precedes the path to $DSHOME/./bin/dssh 3. set up the connection to the database or to the database client application.config file./branded_odbc/lib in the shared library path environment variable. In the odbc. b.. Enter . Testing ODBC driver connectivity: Linux UNIX After you configure ODBC connectivity. Enter this command to test the connection: DS_CONNECT dsn where dsn is the data source name of the connection to test. Procedure To test the connectivity of the ODBC connections that you defined for IBM InfoSphere DataStage: 1. You must specify the Data Source Name (DSN). you must configure the drivers to access ODBC data sources. driver name. Configuring product modules in the suite 251 ./dsenv 2. See your ODBC driver vendor documentation for information about how to configure the driver.Q to quit the connection. 4. 6. c. the suffix is so. Enter this command to start the IBM InfoSphere Information Server engine shell: . 3. test the configuration to verify your connection to the data source. 7. specify the DSN to use to connect to the database. Results To use the DataDirect drivers again. Include the shared library libodbc. Enter this command to log in to the project: LOGTO project_name where project_name is case-sensitive. and login information. test the connectivity. Enter your user name and password to connect to the specified database. Documentation for configuring the ODBC drivers is provided within this directory tree. (On HP-UX.sl for the ODBC Manager in the InfoSphere DataStage load library path. Change directories to $DSHOME and set up the environment by running the following command: . Configuring ODBC access (Microsoft Windows) If you installed ODBC drivers. reverse the procedure in Step 3 and ensure that the InfoSphere DataStage ODBC driver library precedes any other ODBC driver libraries. The DataDirect Technologies Connect ODBC drivers are installed in install_home\ODBCDrivers. .ini file. In the uvodbc.

“Stopping and starting the server engine. Perform the following steps to verify that no InfoSphere DataStage jobs or osh. 2.txt extension. By default. click the Processes tab. lock table entries. About this task For new installations of IBM InfoSphere Information Server.exe 7. verify that the following processes are not running: dsapi_server.exe and dsapi_slave.” on page 287. To tune the engine. In the list of processes. Verify that the Show processes from all users check box is selected.exe processes are running on the server and that no connections are active: a. change the settings described in this task if you are configuring production systems that have 80 or more simultaneously connected users or 50 or more simultaneously running jobs. modify settings in the uvconfig file. 3. Tuning the InfoSphere Information Server engine for large numbers of users or jobs (Windows Server) For Microsoft Windows Server systems that have large numbers of simultaneously connected users or large numbers of simultaneously running jobs. Before you begin v Back up the uvconfig file. verify that the following processes are not running: uvsh. this file is located in the following directory: C:\IBM\InformationServer\Server\DSEngine. For existing installations. For example. See Chapter 20. By default. From the Windows command prompt.exe and osh. Save the uvconfig file. change to the directory that contains the uvconfig file. Restart the InfoSphere Information Server engine.exe.exe. Installation. there are no active InfoSphere DataStage connections. d. c. Specify the following settings MFILES 200 T30FILES 300 RLTABSZ 300 MAXRLOCK 299 4. The uvconfig file cannot have a file extension. If these processes are not running. change these settings if you encounter resource problems while running InfoSphere DataStage jobs. change to the following directory: C:\IBM\InformationServer\Server\DSEngine 6. and locks that are necessary for correct engine operation. b. 5. 252 Planning. From the Microsoft Windows Task Manager. and Configuration Guide . Issue the following command to regenerate the binary uvconfig file: bin\uvregen. In the list of processes. Stop the InfoSphere Information Server engine. Use a text editor to edit the uvconfig file. If these processes are not running. and then click the Image Name column to sort the process list by name. Procedure 1. Make sure that you do not save the file with a . this file is located in the following directory: C:\IBM\InformationServer\Server\DSEngine. you can configure the tIBM InfoSphere Information Server engine to support the number of open files. there are no InfoSphere DataStage jobs running on the server. v Stop all IBM InfoSphere DataStage jobs and ask all users to log out of InfoSphere DataStage.

Procedure 1. the connection to the Match Designer database is established and your encrypted credentials are retained. 2. On each client tier computer. Ensure that the file paths are identical on both the engine tier computer and the services tier computer. open the Match Designer and run a Test Environment Update for your match specification. Setting up application servers to run SQA or investigation reports The investigation reports and Standardization Quality Assessment (SQA) reports can read data from a sequential file or a database table.” on page 161. Oracle database. 2. perform the action that corresponds to the topology of your installation. These drivers are convenient because their functionality does not depend on the presence of any additional database-specific client software. or Microsoft SQL Server database dedicated to the storage of Match Designer output. Topology Action v IBM InfoSphere Information Server engine No additional steps are necessary. Configuring product modules in the suite 253 . If the stage writes the report data to a sequential file. server. v InfoSphere Information Server engine and The sequential file exists only on the engine. You must set up the application server to find the applicable data source. See Chapter 11. define a System DSN that points to the Match Designer database.Configuring IBM InfoSphere QualityStage Match Designer The IBM InfoSphere QualityStage Match Designer requires an ODBC data source name (DSN) to connect to the database where the Match Designer stores match pass results. Chapter 18. The ODBC DSN must have the same name on each computer. perform one of the following steps: v Create a network shared directory that both the engine and application server can access. perform the action that corresponds to the topology and operating system of your installation. Procedure 1. On each client tier and engine tier computer. Before you begin Designate a new or existing IBM DB2 database. “Preparing for the IBM InfoSphere QualityStage Match Designer database. If the stage writes the report data to a database table. and the services tier are on the same computer. When you run this function. v Copy the sequential file from the engine tier computer to the local file system of the services tier. You might want to select from the set of IBM Wire Protocol ODBC drivers installed as part of the IBM InfoSphere Information Server environment. the services tier are on different Because the reports run on the application computers.

For more information.0 Information Center: publib. test the installation by logging in to the Administrator and Designer clients. perform the v InfoSphere Information Server engine and following steps: the services tier are on the same computer 1. v UNIX or Linux Because the ODBC DSN is not visible to the engine as the system DSN. Installation.html Testing the installation of IBM InfoSphere QualityStage and IBM InfoSphere DataStage After you install and configure InfoSphere DataStage and InfoSphere QualityStage. Topology and operating system Action v Microsoft Windows No additional steps are necessary. Start the IBM InfoSphere DataStage and QualityStage Administrator client: 254 Planning. or Linux Because the necessary ODBC drivers are not installed on the application server. 2.doc/info/aes/ae/ tdat_tccrtprovds. If the services and engine tier do not share a user registry. Before you begin To run these tests.ibm. see the IBM WebSphere Application Server documentation: v "Configuring a JDBC provider and data source" in the WebSphere Application Server . Set up the JDBC data source on the application server.html v "Configuring a JDBC provider and data source" in the WebSphere Application Server .websphere.ibm.ibm. v InfoSphere Information Server engine and The reports run on the application server. UNIX.com/ infocenter/wasinfo/v7r0/topic/com. Ensure that the Java Naming and Directory Interface (JNDI) name is the same as the ODBC DSN on the engine.ibm. and Configuration Guide . perform v InfoSphere Information Server engine and the following steps: the services tier are on different computers 1.boulder.base. Set up the Java Database Connectivity (JDBC) data source on the application server.doc/info/aes/ae/ tdat_tccrtprovds. refer to the IBM InfoSphere Information Server Administration Guide. Ensure that the JNDI name is the same as the ODBC DSN on the engine.com/ infocenter/wasinfo/v6r1/topic/com. especially to connect to the IBM InfoSphere DataStage and QualityStage Designer client. 2. you must be either an InfoSphere DataStage administrator or a lower-level user with specific project access granted by an administrator (in the Administrator client). the services tier are on the same computer They can find the database table by using the Open Database Connectivity (ODBC) data source name (DSN) that was set up on the engine.websphere. v Microsoft Windows. Version 6. then you must set up credential mapping.boulder.1 Information Center: publib. For more information about configuring JDBC data sources. Version 7. Procedure 1.base.

c. Select the engine server name in the Host name of the Information Server engine list. The URL is in the form server_name:port_number. c. Use your suite credentials to log in to the Administrator client. Configuring product modules in the suite 255 . or type it into the field if it is not in the list. select a URL in the Host name of the services tier list. Specify the server and project as follows: server_name/project_name. Host and port values for different configurations WebSphere Application Server Port value (HTTP Port value (HTTPS configuration Host value protocol) protocol) WebSphere The host name or HTTP port of the HTTPS secure port of the Application Server IP address of the front-end dispatcher front-end dispatcher (for clustering is set up front-end (for example. select the server and project in the Project list. type them into the field. Do not use dispatcher (either Do not use the port the port number of a the Web server or number of a particular cluster member. particular cluster Do not use the host member. name of a particular cluster member. If the values are not in the list. If the URL is not in the list. if the engine is installed on the xyz server (in a non-clustered application server configuration) and the project is named my-project. type the URL into the field. b. Use the same server name and port number that you used in the previous step. On the computer where you installed the Administrator client. The server name and port values depend on whether IBM WebSphere Application Server clustering is set up within your services tier configuration and whether the services tier and engine tier are configured to use secure HTTP (HTTPS). d. type the URL into the field. 2. click Start → All Programs → IBM InfoSphere Information Server → IBM InfoSphere DataStage and QualityStage Designer. type xyz/my-project. Default: 9443 is installed. Default: 9080 d. The URL is in the form server_name:port_number. Use your suite credentials to log in to the Designer client. Start the IBM InfoSphere DataStage and QualityStage Designer client: a. When you are prompted for the server where the services tier is installed. 80). Clustering is not set The host name or HTTP transport HTTPS transport secure up IP address of the port (configured as port (configured as computer where WC_defaulthost in WC_defaulthost_secure in WebSphere WebSphere WebSphere Application Application Server Application Server). Chapter 18. the load balancer). Server). 443). When you are prompted for the server where the services tier is installed. example. For example. On the computer where you installed the Designer client. b. a. select a URL in the Hostname of the services tier list. click Start → All Programs → IBM InfoSphere Information Server → IBM InfoSphere DataStage and QualityStage Administrator. If the URL is not in the list. Table 93. When you are prompted for the server and project.

Configuring IBM InfoSphere Information Analyzer Before you use IBM InfoSphere Information Analyzer. Server). type the URL into the field. Host and port values for different configurations WebSphere Application Server Port value (HTTP Port value (HTTPS configuration Host value protocol) protocol) WebSphere The host name or HTTP port of the HTTPS secure port of the Application Server IP address of the front-end dispatcher front-end dispatcher (for clustering is set up front-end (for example. you must perform several configuration tasks. On the computer where you installed the InfoSphere Information Services Director client. Table 94. name of a particular cluster member. Log in to the console with credentials that have the Information Services Director Administrator role or suite administrator credentials. particular cluster Do not use the host member. Clustering is not set The host name or HTTP transport HTTPS transport secure up IP address of the port (configured as port (configured as computer where WC_defaulthost in WC_defaulthost_secure in WebSphere WebSphere WebSphere Application Application Server Application Server). cataloging and registering services. c. Before you begin You must have suite administrator credentials or have already set up credentials that have user authority. example. select a URL in the Host name of the services tier list. b. and setting up credentials. Expand the Enabling Information Services section in the Getting Started pane to begin deploying integration logic as services. the load balancer). 256 Planning. The URL is in the form server_name:port_number. Default: 9443 is installed. click Start → All Programs → IBM InfoSphere Information Server → IBM InfoSphere Information Server console. Start the IBM InfoSphere DataStage and QualityStage Administrator client: a. 80). If the URL is not in the list. The server name and port values depend on whether IBM WebSphere Application Server clustering is set up within your services tier configuration and whether the services tier and engine tier are configured to use secure HTTP (HTTPS). 443).Testing the IBM InfoSphere Information Services Director installation After you install and configure IBM InfoSphere Information Services Director. and Configuration Guide . Procedure 1. Default: 9080 2. Do not use dispatcher (either Do not use the port the port number of a the Web server or number of a particular cluster member. Installation. test the installation. When you are prompted for the server where the services tier is installed.

associate the imported metadata with the project. To avoid additional changes to the DSN information. 6. 3. This step completes the global settings for InfoSphere Information Analyzer. and save the connection information. Provide the data source name. In the Analysis Engine. On Windows. 11. Verify the credentials that are used to connect to the analysis database. You can validate the settings in the IBM InfoSphere Information Server console. Configuring product modules in the suite 257 . c. 5. For the analysis database. match this DSN to the name that you defined in step 1. Verify the credentials that are used to connect to the source databases by using the source DSNs that are defined in step 1. 12. in the Home → Configuration → Analysis Settings → Analysis Database tab. Import metadata into the metadata repository. and click Add data source. Select the host. On the Overview menu in the console. the data connection name. e. When you create new InfoSphere Information Analyzer projects. 4. they inherit these global settings. 13. and the connector to use. Procedure 1. b. Modify the project and data source analysis settings. d. see the IBM InfoSphere Information Analyzer User's Guide. validate the DSNs before you do the next step. the DSN must be a system DSN. change values as needed in the Home → Configuration → Analysis Settings → Analysis Settings tab. Match the source DSN with one of the available DSNs that are listed in the Connection String field. a. 8. In the Project Properties tab. Set up security for the project. define the Data Source Name (DSN) to the analysis database and source databases. Create an InfoSphere Information Analyzer project and provide basic project details. 2. Customize the project dashboard. On the computer that hosts the engine. In the IBM InfoSphere Information Server console. select Project Properties. 10. Analysis Database. 9. and Analysis Settings tabs. Open Home → Configuration → Sources. For detailed information about analysis configuration. About this task Do the following high-level tasks to initially configure and administer this product module. Chapter 18. Verify the credentials that are used to connect to the IBM InfoSphere Information Server engine. Click Connect. in the Home → Configuration → Analysis Settings → Analysis Engine tab. you can set project-specific settings by performing the tasks that are described in steps 2 through 4. 7. You can validate the settings in the IBM InfoSphere Information Server console.Before you begin You must have Information Analyzer Data Administrator authority.

Most configuration tasks are optional. and Configuration Guide . Configure viewing permissions. Installation. Configure support for right-to-left reading languages (bidirectional language support). Procedure The configuration tasks are as follows: 1. 2. the suite administrator must create InfoSphere FastTrack administrator and InfoSphere FastTrack user IDs. Procedure To assign roles to users and administrators. the suite administrator must assign roles to IBM InfoSphere Metadata Workbench users and administrators. 258 Planning. About this task You can configure InfoSphere Business Glossary to suit the needs of your organization.Configuring IBM InfoSphere Business Glossary You must configure some settings before you start using InfoSphere Business Glossary. Configuring IBM InfoSphere Metadata Workbench To use IBM InfoSphere Metadata Workbench. Before you begin The IBM InfoSphere Information Server suite administrator must assign security roles to glossary users. Configure general settings. such as "accepted" or "deprecated " v The order in which parts of user names are listed in relevant displays v Whether a history of changes to terms is displayed v Whether integration with Cognos® 8 Go! is enabled 3. Required: Assign security roles to glossary users. you can configure items such as the following: v The content of the display page when users log in to InfoSphere Business Glossary v An e-mail address to which users can send feedback v Whether a property name is displayed if its value is undefined v Restrict which terms are displayed based on their status. Most of them are performed by the Business Glossary Administrator. refer to the IBM InfoSphere Information Server Administration Guide. 4. From the Edit Settings page in the InfoSphere Business Glossary administrative interface. Configuring IBM InfoSphere FastTrack To use InfoSphere FastTrack. This allows you to restrict the access of selected glossary users to some glossary content. This must be done by the InfoSphere Information Server suite administrator.

Configuring product modules in the suite 259 . Chapter 18. see the IBM InfoSphere FastTrack documentation.Procedure For more information.

260 Planning. Installation. and Configuration Guide .

UNIX) After you have copied the parallel engine to each computer that is a member of the MPP environment. such as network. UNIX). 2005. Then configure the parallel engine on each computer. processor. Configuring remote and secure shells (Linux.Chapter 19. Before you begin Ensure that ssh servers are installed on all of the computers where the parallel engine runs. UNIX) You must configure the parallel engine to run the remote shell (rsh) or the secure shell (ssh) without a password on all processing nodes that run parallel jobs. and some tasks ensure the parallel engine is running smoothly. Procedure Repeat this procedure for each Linux or UNIX computer that is to be a parallel processing node in your environment. Configuring a parallel processing environment Some tasks are required to configure the parallel engine. and kernel parameter settings. Set user privileges to run parallel jobs. copy the parallel engine components to each computer. UNIX): The secure shell (ssh) program provides strong authentication and secure communications between computers on a network. 1. Configuring a computer to be a processing node for MPP (Linux. A well-performing parallel engine requires monitoring and adjustment to various settings.” 2. 2010 261 . Before you begin Each user who runs parallel jobs must have rsh or ssh access to each computer where the parallel engine components are copied. Adding computers to share engine processing To configure an MPP system that runs the parallel engine on multiple computers. UNIX)” on page 264. you must configure the computer to act as a processing node. See “Configuring remote and secure shells (Linux. © Copyright IBM Corp. Configure the parallel engine to run the remote shell (rsh) or the secure shell (ssh) without a password on all processing nodes that run parallel jobs. Configuring the parallel engine to use the secure shell (ssh) program (Linux. See “Setting user privileges to run parallel jobs (Linux.

6. UNIX): If you do not want to use a secure shell connection. This process must be repeated for each user that runs parallel jobs. and Configuration Guide .ssh 3.pub user@secondary_computer:~/. Run scp for each user on each secondary computer. depending on the version of ssh.pub The file that contains the authorized keys might be called authorized_keys or authorized_keys2. 4. It is also necessary to log in to each computer before it can run parallel jobs. run the following command to create public and private encryption keys.ssh/id_rsa The keys are saved in the ~/. you can choose instead to use rsh for each parallel engine connection. 5. About this task When you configure ssh to work with the parallel engine. On the primary computer. 2.pub > authorized_keys2 chmod 640 authorized_keys2 rm -f id_rsa.ssh cat id_rsa. This task must be completed for each user that runs parallel jobs. As with ssh. Press the Enter key twice when you run the command. In the following steps. run the following commands to send the public key to the other computers. Procedure 1. cd ~/. the connections must be able to be established without a password prompt.ssh scp id_rsa. run the following command for each user and secondary computer to test the ssh configuration: primary_computer% ssh secondary_computer ls If successful. cd . On the primary computer. 262 Planning. the primary computer is the computer that contains the IBM InfoSphere Information Server engine. using RSA public key encryption for authentication. create the remsh file in the /Server/PXEngine/etc/ directory with the following content: #!/bin/sh exec /usr/bin/ssh "$@" The /Server/PXEngine/etc/ directory is located in the directory where you installed the engine. Log in to each of the secondary computers and add the public key to the list of authorized keys. Give the file execute permission chmod 755 remsh Allowing users to run the remote shell program (rsh) without a password (Linux. The secondary computers are the other computers that contain parallel engines. Installation. On the primary computer. If the user home directories are not automatically mounted. ssh-keygen –b 1024 -t rsa -f ~/. you should be able to log in to the remote shell without providing a password.ssh/id_rsa directory. the engine connects from the primary computer to all of the other computers. The default directory is /opt/IBM/InformationServer/ Server/PXEngine/.

You must explicitly specify the path location in the remsh file if the rsh program is not in the engine list of paths. be owned by the user. this command prints a message displaying the time it has been up. which invokes /usr/bin/rsh: #!/bin/sh exec /usr/bin/rsh "$@" Chapter 19. one host name per line. where install_dir is the top-level directory where the engine tier is installed. Copy or rename the file install_dir/etc/remsh.equiv file or create a .example to install_dir/etc/remsh. In both cases.equiv file or the . Procedure 1. v Create a . v AIX /usr/lpp/ssp/rcmd/bin/rsh v /usr/ucb/rsh v /usr/bin/remsh v /bin/remsh v /usr/bin/rsh If the parallel engine cannot establish a remote shell connection using these paths. Procedure 1. add the host name of each parallel processing node to the /etc/hosts. explicitly specify the path to rsh in the first place the engine searches: install_dir/etc/remsh. On each node. use this command to verify that users can use rsh without a password: rsh host_name uptime where host_name is the name of a processing node that you use with the parallel engine. Configuring a parallel processing environment 263 . and grant read/write access to the user and no access to any other user (file mode of 600).rhosts file.equiv file. The file must be located in the home directory of each parallel user. and grant no access to any other user (file mode of 600).rhosts file for each user. If hostname is accessible. must grant read and write access to the root user. Use one of these methods to allow users to run rsh without a password: v Edit the /etc/hosts.rhosts file for each user. you can edit the /etc/hosts.About this task You achieve password-less rsh connections differently according to your type of system. UNIX): The parallel engine has a set of paths it uses when trying to establish a remote shell. For example. The file must be owned by the root user. 2. This file contains the following shell script. The host name that is included in this file must correspond to the setting of the node fastname parameter in the parallel configuration file. About this task The parallel engine searches the paths in the following order: v install_dir/etc/remsh. Specifying the location of the remote shell (rsh) program (Linux.

Test the shell script by runningrsh on each processing node: rsh node_name uptime Setting user privileges to run parallel jobs (Linux. The installation default is /ishome/Server/PXEngine. This configuration makes software upgrades more convenient than if the parallel engine components are installed on all processing systems. complete the following steps: 1. use the chmod command: chmod 755 install_dir/etc/remsh 4. a single directory on a single system containing the parallel engine software. write. Procedure For each user who runs a parallel job. On the computer where you installed the IBM InfoSphere Information Server engine. mount it using the soft link option. you must copy the parallel engine components to all computers in your MPP system. Copying the parallel engine components to system nodes (Linux. Installation. Edit the last line of the shell script to invoke the specific remote shell command that you are using. and modify access to these directories: – /ishome/Server/Scratch – /ishome/Server/Datasets – /tmp v Run permission on local copies of programs and scripts. and Configuration Guide . 264 Planning. UNIX) When you configure an MPP system. ensure that they have the following privileges: v Log in access v Read. typically via NFS. v Read access to the disk location is referred to by the $APT_ORCHHOME environment variable set in the project. UNIX) A user who runs a parallel job must have the necessary privileges on all processing nodes that the application uses. If you are using NFS to globally mount the directory. change the directory to the parallel engine directory (by default /opt/IBM/InformationServer/Server/PXEngine). About this task There are two ways to make the parallel engine available to all the nodes in the MPP system: v You can globally cross-mount. For example: #!/bin/sh exec /usr/local/remsh "$@" 3. 2. v You can use a script to copy the parallel engine components to a directory with the same path name on all processing systems that you designate for processing parallel jobs. To ensure that all users can run the command. Procedure To copy the parallel engine components to several nodes in a single operation. or overridden in the parameters for the job.

On each computer that is a node. Enter the following command: install_dir/install/copy-orchdist node1 node2 . Create a generic user account. run the InfoSphere Information Server installation program. 3. and also installs the MKS Toolkit on each node. 2. Procedure 1. 2. b. Configuring a parallel processing environment 265 . For information about the parallel engine configuration files. About this task Repeat this procedure for each Windows computer that is to be a parallel processing node in your environment. The installation program installs the parallel engine components. Add the nodes to the configuration files for jobs that will use the nodes. Procedure Repeat this procedure for each Windows computer that is to be a parallel processing node in your environment. nodeN Where node1 to nodeN is a space-separated list of the new node names. For more information about the parallel engine configuration file.. a. add an entry in the parallel engine configuration file for each additional node. complete these steps to configure a computer to be a member of your MPP environment. run the InfoSphere Information Server installation program on each target computer. Select the engine tier only. Copying parallel engine components to processing nodes (Windows) When you configure an MPP system with Microsoft Windows nodes.. About this task Instead of manually copying files. create a generic user named dstage: NET USER dstage password /ADD /COMMENT:"DataStage user account" /FULLNAME:"DataStage User" /ACTIVE:YES /EXPIRES:NEVER /PASSWORDCHG:NO Chapter 19. At a command prompt. Configuring a computer to be a processing node for MPP (Windows) If your parallel environment is a massively parallel processing environment (MPP). After you have installed the engine tier on each computer. Log in as a user with Administrator privileges. 1. see the IBM InfoSphere DataStage and QualityStage Parallel Job Developer's Guide. 3. you must run the IBM InfoSphere Information Server installation program to install the parallel engine components on all Windows computers in your MPP system. see the IBM InfoSphere DataStage and QualityStage Parallel Job Developer's Guide.

For testing purposes. Set APT_PM_NOWAITPID=1 at the project level. Read. You can set APT_ORCHHOME as an environment variable. This environment variable must be set for all jobs. After you are connected. e. b. replace the entire contents with the literal value of HOMEPATH. At a command prompt. All computers that participate in the MPP configuration must use the generic user name and password. 2. Modify 3. g. The new user must have sufficient access rights to run jobs. Installation. which is required by MKS. i. if you installed MKS in the default location. Set the remote shell permissions: a.equiv file located in the $ROOTDIR/etc folder. The default value is C:\IBM\InformationServer\Server\PXEngine. f. e. Enter the same password when prompted. This variable points to the parallel engine install directory. Set user permissions for the dstage account. run the ssh command to connect to the remote engine: ssh -l dstage hostname. where password is the password for the dstage user. You must restart the rshd service after setting up this variable. Read. If the entry contains other environment variables. Test the configuration by attempting a remote directory listing: rsh -l dstage hostname ls 266 Planning. Directory Permissions X:\tmp Write. add the following line: + + You might need to create this file if it does not already exist. g. Edit the User environment variable named HOME. h. run the rsetup command to add the dstage user and password to the Windows XP or Windows 2003 Server LSA database for use by the rshd service. for example %HOMEPATH%. Edit the . If prompted for an RSA certificate. d. The following table lists the minimum directories that you must set and the appropriate permissions. You might need to create the . Log off and log in as the dstage user. Modify X:\IBM\InformationServer\Server\Scratch Write. The path name is shown in UNIX format. Add the following line: + dstage f. From the ksh shell. Exit from the ssh session. c. d.rhosts file in the dstage user's home directory. The default location is typically C:\Documents and Settings\dstage. Modify X:\IBM\InformationServer\Server\Datasets Write. You must enter the password for the dstage user. Edit the hosts. MKS does not have the ability to resolve the environment variable when connecting remotely. accept it.rhosts file if it does not already exist. type ksh. and Configuration Guide . Read. That location is equivalent to C:\Program Files\MKS Toolkit\etc on the Windows file system. c. Log off as the dstage user and log back in as an Administrator user.

Click Properties. which is located in the PXEngine\etc directory. 5. Edit the script file to include the name of the dstage user: # The user (optional) # theUser=dstage c. a. This script enables jobs that contain compiled PX transforms to copy their transformer binaries to the remote nodes. Click the Project tab. Configuring a parallel processing environment 267 . Make a backup copy of the distribute-component script file. you must use a remote shell script. and log in to the Administrator client. Set the values for the environment variables as necessary.example is provided for this purpose. See the IBM InfoSphere DataStage and QualityStage Parallel Job Advanced Developer's Guide for a complete listing of environment variables you can set. set the APT_IO_MAXIMUM_OUTSTANDING environment variable to specify Chapter 19. Environment variables for the parallel engine Set the listed environment variables depending on whether your environment meets the conditions stated in each variable. To run parallel jobs on remote hosts. Save the changes. Network settings APT_IO_MAXIMUM_OUTSTANDING If the system connects to multiple processing nodes through a network. About this task You set the same environment variables for both Windows and UNIX or Linux operating systems. You can set the environment variables by using the IBM InfoSphere DataStage and QualityStage Administrator. Configure the distribute-component script. b. Procedure 1. This script installs and removes the PXEngine component binaries on remote compute nodes. Click Start → All Programs → IBM Information Server → IBM InfoSphere DataStage and QualityStage Administrator. b. and select a project. 2. 4. 3. click Environment. On the General tab. A sample script named remsh. The script is located in the PXEngine\etc folder. 4. Copy the sample script file. and rename it remsh. Configure the parallel engine for remote shell (rsh) or secure shell (ssh). Edit the script file to include the name of the dstage user: #!/bin/sh # Example $APT_ORCHHOME/etc/remsh rsh -l dstage "$@" 5. a. Environment variables are set on a per-project basis from the Administrator client. Setting environment variables for the parallel engine You set environment variables to ensure smooth operation of the parallel engine.

however. to reserve for the parallel engine on every node for TCP/IP communications. increment it by doubling the setting until performance improves. 268 Planning. These environment variables override the APT_IO_MAXIMUM_OUTSTANDING environment variable that sets the total amount of TCP/IP buffer space that is used by one partition of a stage. APT_RECVBUFSIZE If any of the stages within a job has a large number of communication links between nodes. specify this environment variable with the TCP/IP buffer space that is allocated for each connection. If you set one of these environment variables. the job monitor uses time-based monitoring in the InfoSphere DataStage and QualityStage Administrator Director. Specify the value in bytes. and Configuration Guide . To base monitoring on the number of new entries. APT_SENDBUFSIZE If any of the stages within a job has a large number of communication links between nodes. The job monitor window is updated every five seconds. set the APT_COPY_TRANSFORM_OPERATOR environment variable to true to enable Transformer stages to work in this environment. The APT_SENDBUFSIZE and APT_RECVBUFSIZE values are the same. The default value is 2 MB. The APT_SENDBUFSIZE and APT_RECVBUFSIZE values are the same. You can also specify that the monitoring is based on size. the setting is probably too high. Specify the value in bytes. the other is automatically set to the same value. If TCP/IP throughput at that setting is so low that there is idle processor time. These environment variables override the APT_IO_MAXIMUM_OUTSTANDING environment variable that sets the total amount of TCP/IP buffer space that is used by one partition of a stage. If you override the default setting for the APT_MONITOR_TIME. or if your job fails with messages about broken pipes or broken TCP connections. For example. If you set one of these environment variables. If the system is paging. specify this environment variable with the TCP/IP buffer space that is allocated for each connection. in bytes. the amount of memory. the setting of the APT_MONITOR_SIZE environment variable is also overridden. Transform library If you are working on a non-NFS MPP system. This environment variable is set to false by default. Installation. Job monitoring By default. IBM InfoSphere DataStage and QualityStage Administrator users must have the appropriate privileges to create project directory paths on all the remote nodes at runtime. the job monitor window is updated based on the number of new entries. the other is automatically set to the same value. set a value for the APT_MONITOR_SIZE environment variable.

assign the path name to a different directory by using the environment variable TMPDIR.from the end of the existing setting in the Value field. 3. you must change the default environment variables for every project by using the Administrator client. Specifying C++ compiler settings If you are using one of the compilers listed. Procedure v Linux For GCC: Use the IBM InfoSphere DataStage and QualityStage Administrator to configure compiler settings for each project.--allow-shlib-undefined v UNIX For Solaris 9 and 10: Use the IBM InfoSphere DataStage and QualityStage Administrator to configure compiler settings for each project.NET 2003: 1. C++ compiler The environment variables APT_COMPILER and APT_LINKER are set at installation time to point to the default locations of the supported compilers. and then log in to the Administrator client. Temporary directory By default. Configuring a parallel processing environment 269 . By default.-Bsymbolic. the parallel engine uses the C:\tmp directory for some temporary file storage. this environment variable is set to False. The compiler settings must be specified for each project that requires them. Select Start → IBM InfoSphere Information Server → IBM InfoSphere DataStage and QualityStage Administrator. then you must make the specified changes before you create and run parallel jobs. Chapter 19. – APT_COMPILEOPT: -c -O -xarch=v9 -library=iostream -KPIC – APT_COMPILER: /opt/SUNWspro/bin/CC – APT_LINKER: /opt/SUNWspro/bin/CC – APT_LINKOPT: -xarch=v9 -library=iostream -G -KPIC v Windows For Microsoft Visual Studio . Select Projects → Properties → Environment. If you do not want to use this directory. – APT_COMPILEOPT: -O -fPIC -Wno-deprecated -c -m32 – APT_COMPILER: g++ – APT_LINKER: g++ – APT_LINKOPT: -shared -m32 -Wl. Complete this task for every development engine computer or any production engine computer where jobs will be recompiled. If your compiler is installed on a different computer from the parallel engine. Select Parallel → Compiler → APT_COMPILEOPT and delete the string -W/Zc:wchar_t. Detailed information about jobs To produce detailed information about jobs as they run. set the APT_DUMP_SCORE value to True. 2.

a typical location is C:\Program Files\Microsoft SDKs\Windows\v6. ensure that you also installed the SDK and that its resources are available to the system environment. Set the LIB environment variable to the location of the library directory for the SDK. Installation. enter this command to increase it to 1000: 270 Planning. Complete the following steps on each computer that acts as a processing node in your parallel environment. If the value of the maxuproc parameter is less than 1000. Select Parallel → Compiler → APT_LINKOPT and delete the string -W/Zc:wchar_t. 3.from the end of the existing setting in the Value field. and Configuration Guide . UNIX) The following tasks must be performed to configure the parallel engine for Linux and UNIX. select System Advanced → Environment Variables → System Variables. 1. a typical location is C:\Program Files\Microsoft SDKs\Windows\v6. however. For example.NET 2008 Express Edition C++: The compiler settings for this version are correctly set by default. Large systems and symmetric multiprocessing (SMP) servers require more than 1000 processes.NET 2005 Express® Edition C++ and Microsoft Visual Studio . v Windows For Microsoft Visual Studio . For example. Issue this command to determine the current setting for the number of processes: /usr/sbin/lsattr -E -l sys0 | grep maxuproc 2. Note: The LIB and INCLUDE environment variable names must be specified in uppercase characters. Procedure 1. Configuring the parallel engine (Linux. Setting the maximum number of processes for parallel jobs (AIX) The setting of the maxuproc kernel parameter on each parallel engine node controls the maximum number of processes per user for that node. for Microsoft Visual Studio . Use the chdev command to set an appropriate value. From the Windows Control Panel. 2. v Windows For Microsoft Visual Studio 2005 Professional Edition C++: No additional changes are required to run the parallel engine transforms when this compiler is installed before you install IBM InfoSphere Information Server. for Microsoft Visual Studio . Note: You must restart the computer for the environment variable settings to take effect. 4. 4. Save the settings and restart the computer. About this task A user who runs parallel jobs must be able to run at least 1000 processes on each processing node.NET 2008 Express Edition C++.0A\Include.NET 2008 Express Edition C++.0A\ Lib. Set the INCLUDE environment variable to the location of the include directory for the SDK.

303 512-byte blocks). Set the parameters for each user as defined by the values in Table 95. Complete the following steps for each user on each processing node in your parallel environment. Log in as the root user. 3. (4. /usr/sbin/chdev -l sys0 -a maxuproc=1000 This command must be issued on the node by a user with root privileges. data The largest data segment.194.144 512-byte heap. stack. For example: fsize=2097151 data=262144 stack=65536 rss=131072 These numbers represent the number of 512-byte blocks. The command has the form: /usr/sbin/chuser param=value user_name For example: /usr/sbin/chuser fsize=4194303 operator2 /usr/sbin/chuser data=262144 operator2 /usr/sbin/chuser stack=65536 operator2 /usr/sbin/chuser rss=131072 operator2 Chapter 19. dsh -a chdev -l sys0 -a maxuproc=1000 This command must be run from the control workstation with root privileges. About this task The following table describes the parameters that control memory resources and recommends a value for each parameter. have. Configuring a parallel processing environment 271 . Per-user kernel parameter values Parameter Description Value fsize The largest file that a user 2 GB minus 512 bytes can create. including fsize. In an AIX cluster.536 512-byte program can have. you can use the dsh command to set the maximum number of processes per user to 1000 on all cluster nodes. You can also use the smit or smitty commands to perform this action. specify -1. data. blocks) or more. stack The largest stack that a 32 MB (65. or 128 MB (262. Run the following command to determine the value of the memory size parameters for a user: /usr/sbin/lsuser -f user_name This command displays various parameters. 3. process can use. 2. For no limit. and rss. rss The maximum amount of 64 MB (131.072 512-byte physical memory that a user blocks) or more. Setting per-user kernel parameters for parallel jobs (AIX) Per-user kernel parameters ensure that users who run parallel jobs have sufficient resources. Procedure 1. that a program can blocks) or more. Table 95. Use the chuser command to set appropriate values.

Installation. In an AIX cluster. Running more than one job at a time requires more paging space. and Configuration Guide . About this task The minimum amount of paging space to run parallel jobs is 500 MB per processor for computers that have fewer than 20 processors and 1 GB per processor for computers that have 20 or more processors. This command must be issued from the control workstation. Run the lsps command on each node or workstation to display the current size of the paging space: lsps -a The lsps command displays information in the form shown in this table. Setting the paging space for the parallel engine (AIX) To process parallel jobs that have large amounts of data. Table 96. specify the minimum paging space settings. The design of the parallel jobs and the number of jobs that you plan to run at one time affect the paging space requirement. Procedure 1. specify the minimum paging space settings. Before you begin Attention: You must be a system administrator logged in as the root user to reset the system paging space. you can use the dsh command to set the kernel parameters on all cluster nodes. Complete this procedure on each computer in your parallel processing environment. Jobs that have many individual stages require more paging space than jobs that have fewer individual stages. 4. Results of lsps command Physical Page space volume Volume Group size % Used Active Auto Type paging01 hdisk1 pagevg 2000 MB 1 yes yes lv paging00 hdisk2 rootvg 192 MB 5 yes yes lv hd6 hdisk0 rootvg 64 MB 23 yes yes lv 272 Planning. Setting the paging space for the parallel engine To process parallel jobs that have large amounts of data. dsh -a chuser param=value user_name What to do next Users whose per-user kernel parameters have changed must log out and log in again for the changes to take effect. About this task Attention: You must be a system administrator logged in as the root user to reset the system paging space.

Increase the paging space as necessary for each node. Configuring a parallel processing environment 273 . The design of the parallel jobs and the number of jobs that you plan to run at one time affect the paging space requirement. 2.17 8 580600 553760 /dev/dsk/c0t1d0s6 32. the total for the node is 2000 MB + 192 MB + 64 MB = 2256 MB (approximately 2. Running more than one job at a time requires more paging space.2 GB). Setting the paging space for the parallel engine (Solaris) To process parallel jobs that have large amounts of data. Log in as the root user and run the following command on each node to determine the current paging size: $ swap -l The command displays the status of all the swap areas. such as in the following example output: swapfile dev swaplo blocks free /dev/dsk/c0t3d0s1 32. using the following command: swap -a Setting the paging space for the parallel engine (HP-UX) To process parallel jobs that have large amounts of data. About this task The minimum amount of paging space to run parallel jobs is 500 MB per processor for computers that have fewer than 20 processors and 1 GB per processor for computers that have 20 or more processors. specify the minimum paging space settings. In this example. Procedure 1.060.25 8 132040 103440 /dev/dsk/c0t2d0s1 32. the total paging space is 2. Complete this procedure on each computer in your parallel processing environment. or approximately 1 GB. Before you begin Attention: You must be a system administrator logged in as the root user to reset the system paging space. The Group Size column lists the paging size for each disk drive. Before you begin Attention: You must be a system administrator logged in as the root user to reset the system paging space. See the AIX documentation for additional information about setting the paging space. Chapter 19. In this case. Jobs that have many individual stages require more paging space than jobs that have fewer individual stages.14 8 1348192 1316864 A single block is 512 bytes. 2.832 blocks. specify the minimum paging space settings.

Running more than one job at a time requires more paging space. Sample results of the swapinfo command KB Start/ KB Type Available KB Used KB Free % Used Limit Reserve Priority Name dev 524288 0 524288 0% 0 1 /dev/ vg00/l vol2 dev 524288 60808 463480 12% 0 0 /dev/ vg01/1 vol1 reserve 240012 240012 memory 697588 602088 95500 86% In this example. About this task The minimum amount of paging space to run parallel jobs is 500 MB per processor for computers that have fewer than 20 processors and 1 GB per processor for computers that have 20 or more processors. Complete this procedure on each computer in your parallel processing environment. Before you begin Attention: You must be a system administrator logged in as the root user to reset the system paging space. The design of the parallel jobs and the number of jobs that you plan to run at one time affect the paging space requirement. and run the following command on each node to determine the current paging space: # swapinfo The command displays information in the form shown in the following table. Table 97. About this task The minimum amount of paging space to run parallel jobs is 500 MB per processor for computers that have fewer than 20 processors and 1 GB per processor for computers that have 20 or more processors. Setting the paging