Datastage 8.5 Installation Guide

IBM InfoSphere Information ServerVersion 8 Release 5

Planning, Installation, andConfiguration Guide

GC19-1048-08

��

IBM InfoSphere Information ServerVersion 8 Release 5

Planning, Installation, andConfiguration Guide

GC19-1048-08

��

NoteBefore using this information and the product that it supports, read the information in “Notices and trademarks” on page475.

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

Contents

Information road maps . . . . . . . . ix

Part 1. Planning for the installationof IBM InfoSphere InformationServer . . . . . . . . . . . . . . . 1

Chapter 1. Planning Step 1: Reviewingsystem requirements and release notes . 3

Chapter 2. Planning Step 2:Understanding tiers and components . . 5Client tier . . . . . . . . . . . . . . . 6Engine tier . . . . . . . . . . . . . . . 7Services tier . . . . . . . . . . . . . . 10Metadata repository tier . . . . . . . . . . 12Tier relationships . . . . . . . . . . . . 12

Chapter 3. Planning Step 3: Designingan installation topology . . . . . . . 15Basic installation topologies . . . . . . . . . 15

Single computer topology . . . . . . . . 16Client/server topology . . . . . . . . . 16Dedicated engine tier topology . . . . . . . 17Dedicated computer for each tier topology . . . 18Locations for the analysis databases . . . . . 19Locations for the Match Designer database . . . 21Multiple instances of IBM InfoSphere InformationServer . . . . . . . . . . . . . . . 22Multiple server engines . . . . . . . . . 26

High availability configurations . . . . . . . 27Active-passive topology . . . . . . . . . 28IBM WebSphere Application Server NetworkDeployment clustering. . . . . . . . . . 31IBM DB2 high availability options . . . . . . 42Oracle database high availability options . . . 47Other considerations when designing for highavailability . . . . . . . . . . . . . 48Designing a high availability topology . . . . 49

Parallel processing and grid topologies . . . . . 53Parallel processing configurations . . . . . . 53Grid configurations . . . . . . . . . . . 55

Capacity planning . . . . . . . . . . . . 57

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

Determining your database topology . . . . . 61Determining the database installation method . . 63Sizing the analysis databases . . . . . . . 65

Determining how to install WebSphere ApplicationServer . . . . . . . . . . . . . . . . 66Planning volume groups and file systems . . . . 67Secure Sockets Layer (SSL) configuration . . . . 76

Project naming conventions . . . . . . . . . 78New installation road map (no high availability) . . 79

Sample scenario A: Basic client-server topology 84Sample scenario B: Topology with isolated enginetier and parallel engine configuration. . . . . 88

New installation road map (high availabilityactive-passive configuration). . . . . . . . . 93

Sample scenario C: Two-server active-passivehigh availability topology . . . . . . . . 99

New installation road map (high availabilityclustered topology) . . . . . . . . . . . 105

Sample scenario D: Topology with clusteredmetadata repository tier and services tier . . . 114

Adding product modules to an existing installation 122

Part 2. Preparing the tiercomputers . . . . . . . . . . . . 125

Chapter 5. Computer preparation roadmaps . . . . . . . . . . . . . . . 127Preparation road map for the metadata repositorytier computer . . . . . . . . . . . . . 127Preparation road map for the services tiercomputer . . . . . . . . . . . . . . . 128Preparation road map for the engine tiercomputers . . . . . . . . . . . . . . 128Preparation road map for the client tier computers 129

Chapter 6. Obtaining IBM InfoSphereInformation Server software . . . . . 131

Chapter 7. Preparation steps for alltier computers . . . . . . . . . . . 133Verifying the network and opening ports . . . . 133Modifying kernel parameters and user limits(Linux, UNIX) . . . . . . . . . . . . . 137Setting up administrator and owner accounts. . . 142

Naming restrictions for user IDs and passwords 145

Chapter 8. Additional preparationsteps for the metadata repository tiercomputer . . . . . . . . . . . . . 147Preinstalling the IBM DB2 database system . . . 147Preparing an existing DB2 database system . . . 148

Preparing an existing DB2 database system byusing the installation program. . . . . . . 148Preparing an existing DB2 database system byusing scripts. . . . . . . . . . . . . 149Using an IBM DB2 for z/OS database systemfor the databases . . . . . . . . . . . 150

Using a database system other than DB2 . . . . 152

© Copyright IBM Corp. 2005, 2010 iii

Chapter 9. Additional preparationsteps for the services tier computer . 153Preinstalling WebSphere Application Server . . . 153Configuring an existing WebSphere ApplicationServer installation (non-clustered installation) . . 154Configuring the front-end HTTP server for HTTPS 155

Chapter 10. Additional preparationsteps for the engine tier computers . . 157Setting the locale for the target computer . . . . 157

Character encodings supported by IBMInfoSphere Information Server. . . . . . . 158

Installing a C++ compiler for job development . . 159

Chapter 11. Preparing for the IBMInfoSphere QualityStage MatchDesigner database . . . . . . . . . 161

Part 3. Installing IBM InfoSphereInformation Server software. . . . 165

Chapter 12. Installing new software 167Creating an installation . . . . . . . . . . 167Adding product modules to an installation . . . 173Adding an additional software tier to a computer 175Starting the installation program . . . . . . . 177

Preparing to run the installation program . . . 177Graphical mode . . . . . . . . . . . 180Silent mode . . . . . . . . . . . . . 186setup command syntax . . . . . . . . . 189Response files . . . . . . . . . . . . 191

Monitoring installation progress . . . . . . . 194Monitoring the IBM InfoSphere InformationServer installation . . . . . . . . . . . 194Monitoring the IBM WebSphere ApplicationServer installation . . . . . . . . . . . 195Monitoring the IBM WebSphere ApplicationServer enterprise archive deployment . . . . 196Monitoring IBM InfoSphere DataStagecomponent installations . . . . . . . . . 196

Installation verification and troubleshooting . . . 197Installation program sample scenarios . . . . . 198

Running the installation program for Scenario A 198Running the installation program for Scenario B 201Running the installation program for Scenario C 204Running the installation program for Scenario D 207

Chapter 13. Updating products andcomponents . . . . . . . . . . . . 213

Chapter 14. Installing componentsthat are not in the suite installationprogram . . . . . . . . . . . . . 215Installing the IBM InfoSphere Business GlossaryAnywhere client . . . . . . . . . . . . 215

Preparing for enterprise-wide distribution . . . 215Installing the client . . . . . . . . . . 219

Installing IBM InfoSphere Business Glossary Clientfor Eclipse . . . . . . . . . . . . . . 221Installing z/OS components for IBM InfoSphereDataStage MVS Edition . . . . . . . . . . 224

Installing COBOL copybook files . . . . . . 225Installing the runtime library for z/OS jobs . . 226Installation verification process for z/OScomponents . . . . . . . . . . . . . 227

Installing IBM InfoSphere Blueprint Director . . . 228

Part 4. Configuring the softwareafter installation . . . . . . . . . 229

Chapter 15. Firewall exceptions forclient-side executable files (Windows). 231

Chapter 16. Enablement of SecureSockets Layer (SSL) . . . . . . . . 233Enabling SSL for inbound RMI/IIOP . . . . . 233Manually configuring InfoSphere InformationServer components to use HTTPS . . . . . . 234Running UpdateSignerCerts after enabling SSL orchanging SSL at the cell level . . . . . . . . 236Replacing WebSphere Application Servercertificates . . . . . . . . . . . . . . 239Switching from HTTPS back to HTTP . . . . . 240

Chapter 17. Configuring security forIBM InfoSphere Information Server . . 243

Chapter 18. Configuring productmodules in the suite . . . . . . . . 245Configuring IBM InfoSphere DataStage and IBMInfoSphere QualityStage . . . . . . . . . . 245

Ensuring that InfoSphere DataStage users havethe correct localization settings (Linux, UNIX) . 246Configuring access to ODBC data sources . . . 247Tuning the InfoSphere Information Serverengine for large numbers of users or jobs(Windows Server) . . . . . . . . . . . 252Configuring IBM InfoSphere QualityStageMatch Designer . . . . . . . . . . . 253Setting up application servers to run SQA orinvestigation reports . . . . . . . . . . 253Testing the installation of IBM InfoSphereQualityStage and IBM InfoSphere DataStage . . 254

Testing the IBM InfoSphere Information ServicesDirector installation . . . . . . . . . . . 256Configuring IBM InfoSphere Information Analyzer 256Configuring IBM InfoSphere Business Glossary . . 258Configuring IBM InfoSphere Metadata Workbench 258Configuring IBM InfoSphere FastTrack . . . . . 258

Chapter 19. Configuring a parallelprocessing environment. . . . . . . 261Adding computers to share engine processing . . 261

Configuring a computer to be a processing nodefor MPP (Linux, UNIX) . . . . . . . . . 261

iv Planning, Installation, and Configuration Guide

Copying the parallel engine components tosystem nodes (Linux, UNIX) . . . . . . . 264Copying parallel engine components toprocessing nodes (Windows) . . . . . . . 265Configuring a computer to be a processing nodefor MPP (Windows) . . . . . . . . . . 265

Setting environment variables for the parallelengine . . . . . . . . . . . . . . . . 267

Environment variables for the parallel engine 267Specifying C++ compiler settings . . . . . . 269

Configuring the parallel engine (Linux, UNIX) . . 270Setting the maximum number of processes forparallel jobs (AIX) . . . . . . . . . . . 270Setting per-user kernel parameters for paralleljobs (AIX) . . . . . . . . . . . . . 271Setting the paging space for the parallel engine 272Updating the /etc/magic file . . . . . . . 275

Configuring the parallel engine (Windows Server) 275Configuring the Windows Registry: Enablingauto-tuning for paged pool size . . . . . . 276Configuring the Windows Registry: Enablingauto-tuning for system page size . . . . . . 277Configuring the Windows registry: Setting thethreshold for de-committing memory . . . . 278Configuring the Windows registry: Increasingthe noninteractive desktop heap size . . . . 278Configuring the Windows registry: SpecifyingTCP/IP settings . . . . . . . . . . . 279Configuring Windows: Changing swap area size 280Configuring Windows: Editing the boot.ini file 281

Configuring database connectivity in a parallelenvironment. . . . . . . . . . . . . . 282

Configuring access to DB2 databases . . . . 282Configuring access to Oracle databases . . . . 284Configuring access to Teradata databases . . . 285Configuring access to Informix XPS databases 286

Chapter 20. Stopping and starting theserver engine . . . . . . . . . . . 287

Chapter 21. Changing host names andports . . . . . . . . . . . . . . . 289Changing the WebSphere Application Server HTTPport . . . . . . . . . . . . . . . . 289Changing other WebSphere Application Serverports . . . . . . . . . . . . . . . . 291Changing the metadata repository database hostname and port . . . . . . . . . . . . . 292

Part 5. Creating highly available,scalable configurations . . . . . . 297

Chapter 22. Creating a two-serveractive-passive high availabilityconfiguration . . . . . . . . . . . 299Creating an active-passive configuration (Linux,UNIX) . . . . . . . . . . . . . . . . 299

Example: Setting up an active-passiveconfiguration by using IBM Tivoli SystemAutomation for Multiplatforms . . . . . . 301

Creating an active-passive configuration (MicrosoftWindows) . . . . . . . . . . . . . . 313

Example: Setting up an active-passiveconfiguration by using the Microsoft Clusterservice (MSCS) . . . . . . . . . . . . 315

High availability control scripts included with IBMInfoSphere Information Server. . . . . . . . 320

Chapter 23. WebSphere ApplicationServer clustering for high availabilityand scalability . . . . . . . . . . . 323Implementing a WebSphere Application Servercluster for InfoSphere Information Server . . . . 324

Installing IBM WebSphere Application ServerNetwork Deployment for a cluster installation . 324Creating a deployment manager profile . . . 325Creating a custom profile . . . . . . . . 326Creating a cluster and cluster members for theapplication server . . . . . . . . . . . 326Installing a front-end Web server . . . . . . 328Installing a front-end load balancer (Optional) 329Running the installation program (clusteredinstallation) . . . . . . . . . . . . . 330

Changing the front-end dispatcher location . . . 331Configuring a cluster to run as a service(Windows) . . . . . . . . . . . . . . 333

Chapter 24. Metadata repository tierclustering for high availability . . . . 337Configuring the metadata repository database inan IBM DB2 cluster . . . . . . . . . . . 337

Preparing the servers, file system, and storage 338Installing high availability software on DB2database system servers . . . . . . . . . 339Installing the DB2 database system and creatingthe cluster and metadata repository database . . 340Running the installation program for a setupthat includes DB2 clustering . . . . . . . 341Configuring automatic client reroute . . . . 342Specifying the alternate database address andport for IBM WebSphere Application Server . . 342Verifying the IBM DB2 database cluster . . . 345

Setting up the metadata repository database in anIBM DB2 database HADR configuration . . . . 345

Preparing the servers, storage, and network . . 346Installing the DB2 database system and creatingthe metadata repository database . . . . . . 347Running the installation program for an HADRconfiguration . . . . . . . . . . . . 348Configuring the HADR primary server . . . . 348Configuring the HADR standby server . . . . 350Specifying the alternate database address andport for IBM WebSphere Application Server . . 351Starting HADR . . . . . . . . . . . . 353Validating the HADR configuration . . . . . 355

Configuring the metadata repository database inan Oracle RAC cluster . . . . . . . . . . 356

Contents v

Oracle RAC requirements . . . . . . . . 357Creating the metadata repository database andrunning the installation program within anOracle RAC configuration . . . . . . . . 357Connecting to an Oracle RAC configuration . . 358

Part 6. Removing IBM InfoSphereInformation Server software. . . . 359

Chapter 25. Software removal byusing the software removal program . 361Shutting down tasks and applications beforeremoving software . . . . . . . . . . . 361Removing an IBM InfoSphere Information Serverinstallation . . . . . . . . . . . . . . 362Removing individual product modules . . . . . 363Removing a software tier . . . . . . . . . 366Starting the software removal program . . . . . 367

Preparing to run the software removal program 368Graphical mode . . . . . . . . . . . 369Silent mode . . . . . . . . . . . . . 375

Completing software removal (Windows) . . . . 378Completing software removal (Linux, UNIX) . . . 380

Chapter 26. Manual software removal 383Manually removing IBM InfoSphere InformationServer (Windows) . . . . . . . . . . . . 383Manually removing IBM InfoSphere InformationServer (Linux, UNIX) . . . . . . . . . . . 386

Part 7. Troubleshootinginstallations . . . . . . . . . . . 391

Chapter 27. Log files . . . . . . . . 393Installation log files . . . . . . . . . . . 393Temporary files generated by installation program 393IBM WebSphere Application Server system log files 394

Chapter 28. General installationproblems . . . . . . . . . . . . . 397"User credentials are not valid" error appearsunexpectedly during installation . . . . . . . 397IWAV0003E warning in installation log file . . . 397Warnings occur during installation of DB2. . . . 398Installation problems with VMware ESX . . . . 399User creation errors appear in log files (Linux,UNIX) . . . . . . . . . . . . . . . . 399"The publisher could not be verified" message . . 400"There is no script engine for file extension '.js'"message appears during installation . . . . . . 400Installation process hangs when a web browsersession is closed . . . . . . . . . . . . 401

Chapter 29. Authentication problems 403Directory and user permissions . . . . . . . 403User privileges . . . . . . . . . . . . . 406

Chapter 30. Application serverproblems . . . . . . . . . . . . . 407Resolving IBM WebSphere Application Serverinstallation problems . . . . . . . . . . . 407Installation fails when the IBM WebSphereApplication Server port is changed afterinstallation . . . . . . . . . . . . . . 408Resolving connection problems . . . . . . . 408Unable to start IBM WebSphere Application Serverafter the user name changes or expires . . . . . 409Adding an IBM WebSphere Application Serveradministrator user to an internal user registry . . 411Repairing the WebSphere Application Serverregistry after switching to LDAP . . . . . . . 412Services tier performance . . . . . . . . . 413

Chapter 31. IBM InfoSphereInformation Server reporting problems 415Cannot view report result from InfoSphereInformation Server console or InfoSphereInformation Server Web console . . . . . . . 415Enabling and disabling trace logging of thereporting engine . . . . . . . . . . . . 415

Chapter 32. Client and consoleproblems . . . . . . . . . . . . . 417Java Virtual Machine fails to load . . . . . . 417Rich client login failure . . . . . . . . . . 417Resolving problems logging in to the IBMWebSphere Application Server administrativeconsole . . . . . . . . . . . . . . . 419Connection problems after IBM WebSphereApplication Server cluster members are removed . 420

Chapter 33. Removal problems . . . . 423IBM InfoSphere Information Server installationfails repeatedly . . . . . . . . . . . . . 423Ignoring runtime error during uninstallation . . . 423MKS Toolkit errors occur when uninstalling clients 424

Part 8. Appendixes . . . . . . . . 427

Appendix A. Response file parameters(Linux, UNIX) . . . . . . . . . . . 429

Appendix B. Response file parameters(Windows). . . . . . . . . . . . . 441

Appendix C. Naming restrictions foruser IDs and passwords. . . . . . . 451

Appendix D. Installation checklists 453Installation checklist with separate engine tier . . 453Installation checklist with IBM WebSphereApplication Server cluster and IBM DB2 cluster . . 459

Product accessibility . . . . . . . . 467

vi Planning, Installation, and Configuration Guide

Accessing product documentation 469

Reading command-line syntax . . . . 471

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

Notices and trademarks . . . . . . . 475

Contacting IBM . . . . . . . . . . 479

Index . . . . . . . . . . . . . . . 481

Contents vii

viii Planning, Installation, and Configuration Guide

Information road maps

IBM® InfoSphere™ Information Server includes a set of collaborative productmodules and components that can be distributed across multiple computers.

To learn about the installation process:1. Review the system requirements and download the product if you have not

already documented it.2. Read the Quick Start Guide for the installation overview.3. Review the Release Notes for the latest information to ensure successful

installations.4. Read this manual to perform the installation.

The current version and the translated versions of this information are on theWeb at publib.boulder.ibm.com/infocenter/iisinfsv/v8r5/topic/com.ibm.swg.im.iis.productization.iisinfsv.install.doc/topics/cont_iisinfsrv_install.html

The following table provides road maps for different InfoSphere InformationServer installation paths.

© Copyright IBM Corp. 2005, 2010 ix

http://www.ibm.com/support/docview.wss?rs=14&uid=swg27016382



http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r5/topic/com.ibm.swg.im.iis.productization.iisinfsv.relinfo.doc/topics/iisihrinfo_infsv_rnote_v85.html

http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r5/topic/com.ibm.swg.im.iis.productization.iisinfsv.install.doc/topics/cont_iisinfsrv_install.html



Table 1. Installation information road maps

Task Information resources

Create a new installation of InfoSphere InformationServer Appendix D, “Installation checklists,” on page 453

These checklists guide you through thecomplete installation process for specificscenarios.

Part 1, “Planning for the installation of IBM InfoSphereInformation Server,” on page 1

Review system requirements. Learn aboutsoftware tiers and components. Design yourtopology, and determine your installationstrategy.

This section includes detailed softwareinstallation road maps for different topologies.

Part 5, “Creating highly available, scalableconfigurations,” on page 297

Use this section if you plan to implement highavailability or scalability for different softwaretiers, or if you plan to configure the InfoSphereInformation Server parallel engine to usemultiple computers.

Part 2, “Preparing the tier computers,” on page 125Prepare each of your computers for thecomponents that you will install on them.Determine which database system to install orrepurpose. Also determine which applicationserver to install or repurpose.

Part 3, “Installing IBM InfoSphere Information Serversoftware,” on page 165

Run the InfoSphere Information Serverinstallation program on each target computerand verify the installation. Also installcomponents that the installation program doesnot install.

Part 4, “Configuring the software after installation,” onpage 229

Complete additional configuration tasks for theproduct modules that you installed or thefeatures that you want to enable.

x Planning, Installation, and Configuration Guide

Table 1. Installation information road maps (continued)

Task Information resources

Add a product module to an existing InfoSphereInformation Server Version 8.5 installation Part 1, “Planning for the installation of IBM InfoSphere

Information Server,” on page 1Review system requirements to ensure that yourexisting installation meets all requirements. Addhardware if necessary.

Part 2, “Preparing the tier computers,” on page 125Prepare each of your target computers for thecomponents that you will install on them.


Run the InfoSphere Information Serverinstallation program on each target computerand verify the installation. Also installcomponents that the installation program doesnot install.

Part 4, “Configuring the software after installation,” onpage 229

Complete additional configuration tasks thatcorrespond to the product modules that youinstalled or the features that you want to enable.

Add a component that is not included in the InfoSphereInformation Server installation program to an existinginstallation of InfoSphere Information Server, Version 8.5

Chapter 14, “Installing components that are not in thesuite installation program,” on page 215

Some components have their own installationprograms. You install these components afteryou install InfoSphere Information Server.

Upgrade from an earlier version of InfoSphereInformation Server

To upgrade an existing installation, create a new Version8.5 installation and then migrate your data to the newinstallation. To upgrade a client workstation, run theInfoSphere Information Server installation program.

For upgrade information, see the IBM InfoSphereInformation Server Migration Guide.

Remove a product module or an entire installation ofInfoSphere Information Server, Version 8.5 Part 6, “Removing IBM InfoSphere Information Server

software,” on page 359Run the InfoSphere Information Server softwareremoval program on each target computer.

Troubleshoot InfoSphere Information Server installationissues Part 7, “Troubleshooting installations,” on page 391

Resolve installation problems with thisinstallation troubleshooting information. Youcan find more troubleshooting information inthe information centers and customer supporttechnotes for various product modules andcomponents. For more information, refer to“Installation verification and troubleshooting”on page 197.

Information road maps xi

xii Planning, Installation, and Configuration Guide

Part 1. Planning for the installation of IBM InfoSphereInformation Server

Before you install IBM InfoSphere Information Server, review the systemrequirements, learn about tiers and components, design your topology, anddetermine your installation steps.

To plan an installation of InfoSphere Information Server, do these tasks:1. Review the system requirements and release notes.2. Learn about InfoSphere Information Server tiers and components.3. Design the topology of your installation.4. Install product modules on your computers.

© Copyright IBM Corp. 2005, 2010 1

2 Planning, Installation, and Configuration Guide

Chapter 1. Planning Step 1: Reviewing system requirementsand release notes

Ensure that all computers meet the hardware and software requirements for theproduct modules that you want to install.

To obtain the most up-to-date information about the installation requirements, seethese resources:v The system requirements at www.ibm.com/support/docview.wss?rs=14

&uid=swg27016382.v The release notes at publib.boulder.ibm.com/infocenter/iisinfsv/v8r5/topic/

com.ibm.swg.im.iis.productization.iisinfsv.relinfo.doc/topics/iisihrinfo_infsv_rnote_v85.html.








Chapter 2. Planning Step 2: Understanding tiers andcomponents

You install IBM InfoSphere Information Server product modules in logical tiers. Atier is a logical group of components within InfoSphere Information Server and thecomputers on which those components are installed.

Each tier includes a subgroup of the components that make up the InfoSphereInformation Server product modules. The tiers provide services, job execution, andmetadata and other data storage for your product modules.

The following table describes each tier.

Table 2. Tiers

Tier Description

Client The client programs and consoles that areused for development and administrationand the computers where they are installed.

Engine The logical group of components (theInfoSphere Information Server enginecomponents, service agents, and so on) andthe computer where those components areinstalled. The engine runs jobs and othertasks for product modules.

Services The application server, common services,and product services for the suite andproduct modules and the computer wherethose components are installed. The servicestier provides common services (such asmetadata and logging) and services that arespecific to certain product modules. On thetier, IBM WebSphere® Application Serverhosts the services. The services tier alsohosts InfoSphere Information Serverapplications that are Web-based.

Metadata repository The metadata repository and, if installed, theIBM InfoSphere Information Analyzeranalysis database and the computer wherethese components are installed. Themetadata repository database contains theshared metadata, data, and configurationinformation for InfoSphere InformationServer product modules. The analysisdatabase stores extended analysis data forInfoSphere Information Analyzer.

To install InfoSphere Information Server, you first design the hardware andsoftware topology for each tier. Your installation can range from simplesingle-computer configurations, to multiple-computer highly availableconfigurations, to complex and powerful clusters with many computers. Youoptimize your topology design for the product modules that you install and yourrequirements for high availability, performance and throughput, and userconcurrency.


After you design your topology, you install the product module components intheir tiers. You also install any other components that the product module uses, inthe appropriate tiers.

You install InfoSphere Information Server tier by tier. When you run theinstallation program, it prompts you to select the product modules to install, tospecify which tier or tiers to install on the computer, and it installs the appropriateproduct module components in the tiers that you specify.

Client tierThe client tier consists of the client programs and consoles that are used fordevelopment and administration and the computers where they are installed.

The following tools are installed as part of the client tier, based on the productsand components that you select:v IBM InfoSphere Information Server consolev IBM InfoSphere DataStage® and QualityStage Administrator clientv IBM InfoSphere DataStage and QualityStage Designer clientv IBM InfoSphere DataStage and QualityStage Director clientv IBM InfoSphere FastTrack clientv IBM MetaBroker®s and bridgesv IBM InfoSphere Connector Migration Toolv IBM InfoSphere Information Server istool command line. The istool framework is

installed on the engine tier and client tier. Commands for IBM InfoSphereInformation Analyzer, IBM InfoSphere Business Glossary, and InfoSphereFastTrack are installed on the clients only when those products are installed.

The following diagram shows the client tier.

Other client programs

The IBM InfoSphere Business Glossary Anywhere client has a separate installationprogram that is provided on the installation media. This program is not installedby using the InfoSphere Information Server installation program:

InfoSphereFastTrack

clients

Client tier

Adminis-tration

InfoSphereDataStage andQualityStageAdministrator,Designer, andDirector clients

InfoSphereInformation

ServerManager

client

InfoSphere Information Server console


ServicesDirector

client

InfoSphereInformationAnalyzer

client

Multi-clientmanager

IBM MetaBrokersand bridges

InfoSphere ConnectorMigration Tool

istoolcommand line

Figure 1. Client tier components


The InfoSphere Information Server installation program also installs severalWeb-based clients. These clients are installed as part of the services tier, not theclient tier.v IBM InfoSphere Information Server Web console. The Web console provides

access to all administrative and reporting features. Also use the Web console towork with InfoSphere Business Glossary and with the Information ServicesCatalog for IBM InfoSphere Information Services Director, if these productmodules are installed.A browser shortcut to the IBM InfoSphere Information Server Web console iscreated during the InfoSphere Information Server installation.

v IBM InfoSphere Metadata Workbench clientv InfoSphere Business Glossary Browser clientv IBM InfoSphere Information Server Manager client

The Multi-Client Manager is installed when you install a product that includesInfoSphere DataStage and InfoSphere QualityStage client tier components. TheMulti-Client Manager enables you to switch between multiple versions ofInfoSphere DataStage clients. For example, you can switch between Version 8.5 andVersion 7.5 clients.

The MKS Toolkit is installed in the client tier. This toolset is used by theInfoSphere QualityStage migration utility.

Engine tierThe engine tier consists of the logical group of engine components (the IBMInfoSphere Information Server engine components, service agents, and so on) andthe computer where those components are installed.

Several product modules require the engine tier for certain operations. You installthe engine tier components as part of the installation process for these productmodules. The following product modules require the engine tier:v IBM InfoSphere DataStagev IBM InfoSphere Information Analyzerv IBM InfoSphere Information Services Directorv IBM InfoSphere Metadata Workbenchv IBM InfoSphere QualityStagev IBM InfoSphere Information Server istool command line. The istool framework is

installed on the engine tier and client tier. Commands for InfoSphereInformation Analyzer and InfoSphere Metadata Workbench are installed on theengine tier only when those products are installed.

IBM InfoSphere FastTrack, IBM InfoSphere Business Glossary, and IBM InfoSphereBusiness Glossary Anywhere do not require an engine tier.

Windows IBM MetaBrokers and bridges can be installed on Microsoft Windows,on engine tiers. These components import metadata into and export metadata outof the metadata repository.

Windows Only one InfoSphere Information Server engine can be installed on asingle computer.

Chapter 2. Planning Step 2: Understanding tiers and components 7

Linux UNIX The following configurations are supported:v Multiple engines, each on a different computer, all registered to the same

InfoSphere Information Server services tier.v Multiple engines on the same computer. In this configuration, each engine must

be registered to a different services tier. This configuration is called an ITAGinstallation.

The installation program installs the following engine components as part of eachengine tier:

InfoSphere Information Server engineRuns tasks or jobs such as discovery, analysis, cleansing, or transformation.The engine includes the server and parallel engines and other componentsthat make up the runtime environment for InfoSphere Information Serverand its product components.

ASB agentsA Java process that runs in the background on each computer that hosts anInfoSphere Information Server engine tier. When a service that runs on theservices tier receives a service request that requires processing by anengine tier component, the agent receives and conveys the request.

Linux UNIX The agent runs as a daemon that is named ASBAgent.

Windows The agent runs as a service that is named ASBAgent.

ASB agents include:

Connector access services agentConveys service requests between the ODBC driver components onthe engine tier and the connector access services component on theservices tier.

InfoSphere Information Analyzer agentConveys service requests between the engine components on theengine tier and the InfoSphere Information Analyzer servicescomponent on the services tier.

InfoSphere Information Services Director agentConveys service requests between the engine components on theengine tier and the InfoSphere Information Services Directorservices component on the services tier.

Logging agentLogs events to the metadata repository.

Linux UNIX The agent runs as a daemon that is namedLoggingAgent.

Windows The agent runs as a service that is named LoggingAgent.

ODBC drivers

The installation program installs a set of ODBC drivers on the engine tierthat works with InfoSphere Information Server components. These driversprovide connectivity to source and target data.

Resource Tracker

The installation program installs the Resource Tracker for parallel jobs withthe engine components for InfoSphere DataStage and InfoSphere


QualityStage. The Resource Tracker logs the processor, memory, and I/Ousage on each computer that runs parallel jobs.

dsrpcd (DSRPC Service)Allows InfoSphere DataStage clients to connect to the server engine.

Linux UNIX This process runs as a daemon (dsrpcd).

Windows This process runs as the DSRPC Service.

Job monitorA Java application (JobMonApp) that collects processing information fromparallel engine jobs. The information is routed to the server controllerprocess for the parallel engine job. The server controller process updatesvarious files in the metadata repository with statistics such as the numberof inputs and outputs, the external resources that are accessed, operatorstart time, and the number of rows processed.

Windows DataStage engine resource serviceEstablishes the shared memory structure that is used by server engineprocesses.

Windows DataStage Telnet serviceAllows users to connect to the server engine by using Telnet. Useful fordebugging server engine-related issues. Does not need to be started fornormal InfoSphere DataStage processing.

Windows MKS ToolkitUsed by the InfoSphere Information Server parallel engine to run jobs.

The following diagram shows the components that make up the engine tier. Itemsmarked with asterisks (*) are only present in Microsoft Windows installations.

DSRPCservice

Jobmonitor

DataStageEngine

Resourceservice

DataStageTelnet

Service

*MKSToolkit

Engine tier

Server engine

Parallelengine

Connectivity(ODBCdrivers)

ASB agents

Connector accessservices agent

InfoSphere InformationAnalyzer agent

InfoSphere InformationServices Director agent

Loggingagent

ResourceTracker

istoolcommand

line

Sourceand

targetdata

*IBMMetabrokersand bridges

Figure 2. Engine tier components


Services tierThe services tier consists of the application server, common services for the suite,and product module-specific services and the computer where those componentsare installed.

Services for IBM InfoSphere Information Server

Some services are common to all product modules. Other services are specific tothe product modules that you install. The services tier must have access to themetadata repository tier and the engine tier.

An instance of IBM WebSphere Application Server hosts these services. Theapplication server is included with the suite for supported operating systems.Alternatively, you can use an existing instance of WebSphere Application Server, ifthe version is supported by InfoSphere Information Server. For a list of supportedversions, see the system requirements at www.ibm.com/support/docview.wss?rs=14&uid=swg27016382.

The following diagram shows the services that run on the application server on theservices tier.

Product module-specific IBM InfoSphere Information Analyzer, IBM InfoSphereInformation Services Director, IBM InfoSphere FastTrack, IBM InfoSphereDataStage, IBM InfoSphere QualityStage, IBM InfoSphere Business Glossary, andIBM InfoSphere Metadata Workbench are included on the services tier. They alsoinclude connector access services that provide access to external data sourcesthrough the ODBC driver components and the connector access services agent onthe engine tier.

IBM InfoSphere BusinessGlossary services

Services tier

Application server

Commonservices

Core services

Connector accessservices

IBM InfoSphere InformationAnalyzer services

IBM InfoSphere InformationServices Director services

IBM InfoSphereFastTrack services

IBM InfoSphereQualityStage services

IBM InfoSphereDataStage services

IBM InfoSphere MetadataWorkbench services

Product module-specificservices

Reporting

Security

Directory

Logging

Scheduling

Metadata services

Figure 3. Services tier services




The common services include:

Scheduling servicesHelp plan and track activities such as logging and reporting and suitecomponent tasks such as data monitoring and trending. You can use theInfoSphere Information Server console and Web console to maintain theschedules. Within the consoles, you can define schedules, view their status,history, and forecast, and purge them from the system. For example, areport run and the analysis job within InfoSphere Information Analyzer arescheduled tasks.

Logging servicesHelp you manage logs across all the InfoSphere Information Server suitecomponents. You can view the logs and resolve problems by using theInfoSphere Information Server console and Web console. Logs are stored inthe metadata repository. Each InfoSphere Information Server suitecomponent defines relevant logging categories.

Directory servicesAct as a central authority that can authenticate resources and manageidentities and relationships among identities. You can base directories onthe InfoSphere Information Server internal user registry. Alternatively, youcan use external user registries such as the local operating system userregistry, or Lightweight Directory Access Protocol (LDAP) or MicrosoftActive Directory registries.

Security servicesManage role-based authorization of users, access-control services, andencryption that complies with many privacy and security regulations. Ifthe user registry internal to InfoSphere Information Server is used,administrators can use the InfoSphere Information Server console and Webconsole to add users, groups, and roles within InfoSphere InformationServer.

Reporting servicesManage run time and administrative aspects of reporting for InfoSphereInformation Server. You can create product module-specific reports forInfoSphere DataStage, InfoSphere QualityStage, and InfoSphereInformation Analyzer. You can also create cross-product reports forlogging, monitoring, scheduling, and security services. You can access,delete, and purge report results contents from an associated scheduledreport execution. You can set up and run all reporting tasks from theInfoSphere Information Server Web console.

Core servicesLow-level services such as service registration, life cycle management,binding services, and agent services.

Metadata servicesImplement the integrated metadata management within InfoSphereInformation Server. Functions include repository management, persistencemanagement, and model management.

InfoSphere Information Server Web-based applications

The following InfoSphere Information Server Web-based applications are installedas part of the services tier.v IBM InfoSphere Metadata Workbench


v The IBM InfoSphere Information Server Web console. The Web console consistsof administration and reporting tools, and the following clients:– IBM InfoSphere Business Glossary– Information Services Catalog for InfoSphere Information Services Director– The metadata repository management tool

Metadata repository tierThe metadata repository tier consists of the metadata repository database and, ifinstalled, the IBM InfoSphere Information Analyzer database and the computerwhere these components are installed.

The metadata repository tier includes the metadata repository database for IBMInfoSphere Information Server. The database is a shared component that storesdesign-time, runtime, glossary, and other metadata for product modules in theInfoSphere Information Server suite.

If InfoSphere Information Analyzer is installed, the metadata repository alsoincludes one or more analysis databases. The analysis databases are used byInfoSphere Information Analyzer when it runs analysis jobs.

The services tier must have access to the metadata repository tier. When productmodules store or retrieve metadata, services on the services tier connect to themetadata repository tier and manage the interaction between the databases and theproduct modules.

For InfoSphere Information Analyzer, the engine tier and the client tier must alsohave direct access to the analysis databases.

The following diagram shows the components that make up the metadatarepository tier.

Tier relationshipsThe tiers provide services, job execution, and metadata and other data storage forthe product modules that you install.

The following diagram illustrates the tier relationships.

Information Analyzeranalysis databases

Metadata repositorydatabase

Metadata repository tier

Figure 4. Metadata repository tier components


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.

The IBM InfoSphere DataStage and QualityStage clients also communicate withthe engine tier.

v Various services within the services tier communicate with agents on the enginetier.

v Metadata services on the services tier communicate with the metadata repositorytier.

v ODBC drivers on the engine tier communicate with external databases.v IBM InfoSphere Metabrokers and bridges on the client tier can import data from

external sources. Some InfoSphere Metabrokers and bridges can export data.v With the IBM InfoSphere Information Analyzer product module, the engine tier

communicates directly with the analysis databases on the metadata repositorytier. The InfoSphere Information Analyzer client also communicates directly withthe analysis databases.


Services tier

Commonservices

Client tier

Console

Engine tier

Engine

ODBCdrivers

Data

Productmodule-specificservices

Figure 5. Tier relationships



Chapter 3. Planning Step 3: Designing an installation topology

Design the hardware and software topology for each tier.

The overall topology of an installation can range widely in complexity. Optimizethe design of the topology to accommodate the product modules that you installand any requirements for high availability, performance and throughput, and userconcurrency.

Basic installation topologiesIf you do not need a high availability solution and do not anticipate scaling theinstallation for higher capacity in the future, choose a basic topology.

The following are some basic topologies for IBM InfoSphere Information Server. Inthese topology descriptions, the term computers refers to separate physical servers,logical partitions (LPARs), or virtual machines.

Single computerIn this topology, the engine tier, metadata repository tier, services tier, andclient tier are all installed on a single computer. This topology is specific toMicrosoft Windows configurations.

Client/serverIn this topology, the engine tier, metadata repository tier, and services tierare all installed on a single computer. The client tier is installed on separatecomputers.

Dedicated engine tierIn this topology, the services tier and metadata repository tier are installedon a computer. The engine tier is installed on another computer. The clienttier is installed on separate computers.

Dedicated computer for each tierYou can host each tier on a separate computer.

Locations for the IBM InfoSphere Information Analyzer databaseIf you install InfoSphere Information Analyzer, you must provide alocation for the analysis database.

Locations for the IBM InfoSphere QualityStage Match Designer databaseIf you install InfoSphere QualityStage, you must create the Match Designerdatabase manually.

IBM InfoSphere FastTrack topologiesIBM InfoSphere FastTrack places code on the client, services, andrepository tiers.

Multiple instances of InfoSphere Information ServerYou can install more than one instance of InfoSphere Information Server ona set of computers.

Multiple server enginesYou can create an installation with more than one engine tier.

These topologies are described in the following sections.


Single computer topologyIn this topology, the engine tier, metadata repository tier, services tier, and clienttier are all installed on a single computer.

The computer must be a server-class computer that meets all system requirements,such as memory, disk space, and other requirements. To support the client tier, thecomputer must run Microsoft Windows and meet all system requirements for thisplatform.

This topology is suitable for demonstration systems and for small-scaledevelopment.

The following diagram illustrates this topology.

Client/server topologyIn this topology, the engine tier, metadata repository tier, and services tier are allinstalled on a single computer. The client tier is installed on separate computers.

The client tier computers must run Microsoft Windows. The computer that hoststhe other tiers can run any operating system that IBM InfoSphere InformationServer supports.

This topology centralizes administration and isolates it from client users. Thefollowing diagram illustrates this topology.

Note: Although the diagram shows only one client tier computer, you can includemultiple client tier computers.

Computer A

Client tier

Enginetier

Servicestier


Figure 6. Single computer topology


Dedicated engine tier topologyIn this topology, the services tier and metadata repository tier are installed on onecomputer. The engine tier is installed on another computer. The client tier isinstalled on separate computers.

The client tier computer must run Microsoft Windows. The other computers canrun any operating system that IBM InfoSphere Information Server supports.

Installing the metadata repository tier with the services tier provides optimalperformance because there is no network latency between the tiers. Also, higherengine tier activity does not affect the operations of the services tier and metadatarepository tier. This topology is suitable for environments that have high IBMInfoSphere DataStage and QualityStage job requirements and for IBM InfoSphereInformation Analyzer installations.



Computer B

Enginetier

Servicestier

Metadatarepository tier

Network

Client tier

Computer A

Figure 7. Basic client/server topology

Chapter 3. Planning Step 3: Designing an installation topology 17

Dedicated computer for each tier topologyYou can host each tier on a separate computer.

This topology provides each tier with dedicated computational resources. If youchoose this topology, minimize network latency between all tiers. In particular, youmust have a high-bandwidth connection between the services tier and themetadata repository tier.

The services tier and the metadata repository tier must be on the same subnet.



Client tier

Engine tier

Computer CComputer B

Services tier


Computer A

Network

Figure 8. Topology with separate server dedicated to engine tier


Locations for the analysis databasesIf you install IBM InfoSphere Information Analyzer, you must provide the locationfor one or more analysis databases. At installation time, you specify the locationfor the first analysis database. After the installation, you can add additionaldatabases by using the IBM InfoSphere Information Server console.

Each InfoSphere Information Analyzer project is associated with a specific analysisdatabase. The analysis database might be used by a single InfoSphere InformationAnalyzer project, or it might be shared by multiple InfoSphere InformationAnalyzer projects. For example, two InfoSphere Information Analyzer projectsmight use two different analysis databases, or they might share the same analysisdatabase.

The analysis database is a component that InfoSphere Information Analyzer useswhen it runs analysis jobs. The InfoSphere Information Server engine must haveaccess to one or more analysis databases.

You can locate an analysis database and the metadata repository in the samedatabase server installation as distinct databases. Alternatively, you can locateanalysis databases and the metadata repository on different computers.

Client tier


Computer DComputer B

Services tier Engine tier

Computer A

Network

Computer C

Figure 9. Topology with dedicated computer for each tier


The database system for the analysis databases can be different from the databasesystem for the metadata repository. For example, you can use an IBM DB2®

database for the metadata repository and an Oracle database for an analysisdatabase.

The following diagram illustrates a three-computer topology where an analysisdatabase and the metadata repository database are located in the same databaseserver installation.

The following diagram illustrates a four-computer topology where an analysisdatabase and the metadata repository database are located on different computers.

Client tier

Engine tier


Services tier


Computer A

Network

InformationAnalyzeranalysisdatabase

Metadatarepositorydatabase

Figure 10. Topology with analysis database and metadata repository database in the same database server installation


Locations for the Match Designer databaseIBM InfoSphere QualityStage requires that you provide a location for the MatchDesigner database. After you install InfoSphere QualityStage, you configure it touse a database that you create.

The InfoSphere QualityStage Match Designer is a component of InfoSphereQualityStage that is used to design and test match specifications. Matchspecifications consist of match passes that identify duplicate entities within one ormore files.

If you intend to develop match specifications, use a new or existing database thatis dedicated to storing the results of match test passes. Do not use the metadatarepository or the analysis database to store these results.

The IBM InfoSphere Information Server installation program does not create theMatch Designer results database. You create the database before or after theinstallation, as long as the database is configured and accessible when you use theMatch Designer. You can create the database on a computer where the client orengine tier is installed or on any computer that is accessible to both of these tiers.You must configure the database to receive the type of data that is processed in theMatch Designer. For example, you must configure the database to receivedouble-byte data if the Match Designer processes Asian data.

Client tier

Engine tier

C DomputerC Bomputer

Services tier


Computer A

Network

InformationAnalyzeranalysisdatabase

Metadatarepositorydatabase

C Computer

Figure 11. Topology with analysis database and metadata repository database on different computers


You can locate the Match Designer database within the same database systeminstance as the metadata repository or IBM InfoSphere Information Analyzeranalysis database. Alternatively, you can locate the databases in separate instances.The database system for the Match Designer database can be different from thedatabase system for the other databases. For example, you can use an IBM DB2database for the metadata repository and an Oracle database for the MatchDesigner database.

Multiple instances of IBM InfoSphere Information ServerIn a Linux or UNIX installation, you can install more than one instance ofInfoSphere Information Server on the same set of computers. You cannot installmore than one InfoSphere Information Server instance on a Microsoft Windowscomputer.

The instances are isolated from one another, with separate engine tiers, servicestiers, and metadata repository tiers. These tiers cannot be shared betweeninstances. The instances can reside on the same computer in different installationdirectories or on different computers. The instances can be the same softwareversion or different versions.

If the instances are the same InfoSphere Information Server version, you canconfigure a single client tier instance to communicate with multiple InfoSphereInformation Server instances. The following diagram shows a topology with twoseparate InfoSphere Information Server, Version 8.5 instances, that are installed ontwo separate computers. A single client tier installation communicates with bothinstances.


If the instances are different versions, the client tier must contain clients for eachversion. The following diagram shows a topology with two separate InfoSphereInformation Server instances that are installed on two separate computers. Theinstances are different versions. The client tier contains clients for both versions.The Multi-Client Manager is used to switch from one client version to the other.

Computer C

Enginetier

Servicestier


Network

Client tier

Computer A

Clients forVersion 8.5

Computer B

Enginetier

Servicestier


InfoSphereInformationServerinstance


Serverinstance

Figure 12. Topology with separate instances on separate computers


If the services tiers for more than one instance reside on the same computer,specify different ports for each services tier. The following diagram shows atopology where the services tiers and metadata repository tiers for two differentInfoSphere Information Server version instances are installed on the samecomputer. Each services tier communicates with a separate engine tier installed ona separate computer.

Computer C

Enginetier

Servicestier


Network

Client tier

Computer A

Multi-client manager

Clientsfor

Versionn

Clientsfor

Version8.5

Computer B

Enginetier

Servicestier


InfoSphereInformationServer,Versionn


Server,Version

8.5

Figure 13. Topology with separate different version instances on separate computers


To install more than one instance of the InfoSphere Information Server engine onthe same computer, create an ITAG installation. To perform this install, run theinstallation program multiple times to create multiple engine tier instances. Duringthe installation, assign each instance a unique identification tag and port number.All projects and jobs associated with a server engine instance are assigned the tagfor the server engine instance.

Each engine tier instance must be registered to a different InfoSphere InformationServer service instance.

The following diagram shows a topology where the engine tiers for two InfoSphereInformation Server instances are installed on the same computer. Each engine tierhas an associated ITAG.

Computer D

Computer C

Engine tier

Network

Client tier

Computer A


Clientsfor

Versionn

Clientsfor

Version8.5

Computer B

Metadatarepository

Servicestier

InfoSphere InformationServer, Version n

InfoSphere InformationServer, Version 8.5

Metadatarepository

Servicestier

Engine tier

Figure 14. Topology where services tiers share a common computer


Note: Windows ITAG installations are not supported on Microsoft Windowscomputers.

Multiple server enginesYou can create an installation topology that includes more than one engine tier.

In this topology, each engine tier consists of an IBM InfoSphere Information Serverengine and a parallel engine.

You might choose this topology for project and resource management reasons. Forexample, you might dedicate one engine tier to IBM InfoSphere DataStage jobs andanother engine tier to IBM InfoSphere Information Analyzer jobs. Or you mightdedicate multiple engine tiers to separate sets of InfoSphere Information Analyzerjobs, each with its own analysis database.

Each engine tier instance must reside on a separate computer. You cannot configurethe services tier to communicate with multiple engine tiers that are installed on thesame computer.

The following diagram shows a topology with two engine tiers that are installedon separate computers. A single services tier instance communicates with bothengine tiers.

Clientsfor

Versionn

Clientsfor

Version8.5

Computer C

Engine tierITAG "Y"

Network

Client tier

Computer A


Computer B

Metadatarepository

Servicestier

InfoSphere InformationServer, Version n

InfoSphere InformationServer, Version 8.5

Metadatarepository

Servicestier

Engine tierITAG "X"

Figure 15. ITAG installation


High availability configurationsIBM provides different high availability solutions for each IBM InfoSphereInformation Server tier.

Increasing availability (implementing a high availability solution) refers tomaximizing the percentage of time that the system services are operational. Toincrease availability, you implement topologies and technologies that introduceredundancy. The aim is to reduce or eliminate the number of single points of failure(SPOF). Single points of failure are elements whose failure causes critical aspects ofthe system to stop operating.

IBM provides different high availability solutions for each InfoSphere InformationServer tier. Each solution allows you to design many different highly availableconfigurations, from relatively simple setups to complex installations.

The following table lists high availability solutions for each tier:

Table 3. Tiers and high availability solutions

Tier Solutions

Engine Active-passive configuration managed byhigh availability cluster-managementsoftware, such as IBM Tivoli® SystemAutomation for Multiplatforms

Client tier

Engine tier

Computer DComputer B

Engine tier Services tier

Computer A

Network

Computer C


Figure 16. Topology with two engine tiers


Table 3. Tiers and high availability solutions (continued)

Tier Solutions

Services Either of the following solutions:

v Active-passive configuration managed byhigh availability cluster-managementsoftware such as Tivoli SystemAutomation for Multiplatforms

v IBM WebSphere Application Serverclustering

Metadata repository Any of the following solutions:

v Active-passive configuration managed byhigh availability cluster-managementsoftware such as Tivoli SystemAutomation for Multiplatforms

v IBM DB2 clustering

v DB2 high-availability data recovery(HADR)

v Oracle Real Application Clusters (RAC)

In general, the higher the level of overall availability that you want to achieve, themore complex the system that you must design and maintain. High availabilitysystems generally require more hardware. For these reasons, give carefulconsideration to the level of availability that you require within each software tierin the system. You might want a different level of availability within yourdevelopment system than you have within your production system.

To deploy a highly available topology, you must have a solid understanding ofnetwork technologies such as protocols, tiers, and devices. Successfully deployinghighly available topologies, especially one that includes clustering, is a technicallycomplex process that requires a high degree of technical expertise.

Active-passive topologyTo create a basic level of availability for IBM InfoSphere Information Server, installit on a file system that is shared by two or more computers. The computers areclustered by using high availability (HA) software.

In this topology, two computers share a storage area network (SAN). The metadatarepository tier, engine tier, and services tier are all installed on the SAN. One of thecomputers (the active server) hosts the InfoSphere Information Server instance. Theother computer (the passive server) is started, but does not run any tier software. Ahigh availability software product such as IBM Tivoli System Automation forMultiplatforms is installed on both the active server and the passive server. TheHA software maintains a heartbeat: a periodic signal that is sent from the activeserver to the passive server and that indicates that the active server is operational.




If the active server fails, the heartbeat also fails. The HA software restarts allInfoSphere Information Server services on the passive server. This process is calleda failover. The following diagram illustrates this process.

Computer B(Active)

HA managementsoftware


Computer C(Passive)

Enginetier

Servicestier

Databaseinstance

Client tier

Computer A

Enginetier

(installed)

Servicestier

(installed)

Database

SAN

Figure 17. Active-passive server cluster configuration


At installation time, you create a host name alias for the system. This informationis associated with the active server. All client programs connect to the system byusing this address or host name. If the active server fails, the information isautomatically reassociated with the passive server, so client programs do not needto connect to a different address.

However, a failover is not transparent to client users. If the active server fails, allInfoSphere Information Server services are unavailable until the failover iscomplete and the passive server is operational. The failover process can takeseveral minutes. Also, any jobs that were running fail and must be restarted afterthe passive server has taken over.

In this configuration, the HA software monitors the health only of the serverhardware and operating-system-level processes. The software initiates a failoveronly if one of these elements fails. Other software monitors the health of individualInfoSphere Information Server processes, but does not trigger a failover if a processfails. Instead, the system administrator is notified. This design allows a systemadministrator to correct the problem, instead of simply allowing the problem to bereproduced on the passive server.

The active-passive topology is appropriate for small- to medium-sized companieswith few concurrent system users. The topology provides a basic level of high

Enginetier

(installed)

Servicestier

(installed)

Database

SAN

Computer B(Inoperative)



C Computer(Newly active)

Enginetier

Servicestier

Database instance

Client tier

C Aomputer

HeartbeatSignal

(broken)

Figure 18. Active-passive server cluster configuration with a failed computer


availability without incurring significant additional server hardware costs. Thisconfiguration is suitable mainly for systems that run scheduled production jobs.The types of activities involved in a development environment make it more likelythat a failover would cause dynamic file corruption or synchronization problems.

This topology is not scalable. You can add alternate passive servers if necessary.However, performance, throughput, and concurrency are not affected because atany specific time, only one instance of each tier component is running in theconfiguration.

Some other variations of this topology are possible, for example:v Computer B hosts the services tier and the metadata repository tier. Computer C

hosts the engine tier. The computers can fail over to one another. For example, ifComputer B fails, Computer C also takes over the services tier and the metadatarepository tier. If Computer C fails, Computer B also hosts the engine tier.

v Computer B hosts the services tier and the metadata repository tier. Computer Chosts the engine tier. Another computer (Computer D) serves as backup serverfor both Computer B and Computer C.

These variations are beyond the scope of this documentation.

To simplify the configuration further, you can eliminate the HA software from yourimplementation, and allow your IT department to trigger a failover manuallywhen necessary.

IBM WebSphere Application Server Network Deploymentclustering

To provide high availability of the services tier, create a cluster of IBM WebSphereApplication Server Network Deployment (ND) application servers across two ormore computers.

Deploy an instance of the services tier (common services and product-specificservices) in each application server. When a member of the cluster fails, othercluster members continue to provide services. Components in other tierscommunicate with the cluster, not directly with a specific application server in thecluster. As long as at least one member of the cluster is operational, there is nointerruption in service.

Implementing an IBM WebSphere Application Server Network Deployment cluster,and designing a front-end configuration that balances loads and optimizes traffic,also improves concurrency. Concurrency is the number of clients that can use thesystem simultaneously with a reasonable level of system responsiveness. You canscale a clustered configuration as needed to meet increased concurrencyrequirements.

The following diagram shows a topology with a services tier where applicationserver clustering is implemented across two computers. A third computer hosts theWebSphere Application Server Deployment Manager. In the diagram, the enginetier is still set up in an active-passive server cluster configuration. The metadatarepository tier is located on a separate computer.

This topology also includes a sophisticated front-end configuration that includesdual Web servers and a load balancer. These systems are set up outside thefirewall. HTTP clients such as the WebSphere Application Server Web consoleaccess the server-side components through the load balancer. A backup load


balancer ensures that the load balancer computer is not a single point of failure.EJB clients such as the IBM InfoSphere Information Server console and the IBMInfoSphere DataStage and QualityStage Designer communicate directly with theWebSphere Application Server nodes.

Note: High availability configurations that include WebSphere Application Serverclustering typically also include metadata repository clustering. The databasecluster ensures that the metadata repository is not a single point of failure.

If a server in the cluster fails, the other WebSphere Application Server clustermembers continue to operate. The following diagram illustrates this failoverprocess:

Cluster

SAN

HA mgt sw

Engine tier

Services tier


Client tier

Firewall

Client workstations

Backup loadbalancer

Loadbalancer

Webserver 1

Webserver 2

WebSphereApplication

ServerDeployment

Manager


ServerNode 2


Server Node 1

ActiveComputer

PassiveComputer

HA mgt sw

HTTP clients EJB clients

MetadataRepositorycomputer

DBMS

Database

Figure 19. Topology with WebSphere Application Server cluster


Implementing IBM WebSphere Application Server clusteringTo implement clustering, create an IBM WebSphere Application Server NetworkDeployment cell across your computers, and define a cluster that containsapplication servers within the cell.

An IBM WebSphere Application Server Network Deployment implementationconsists of one or more application server processes. These processes run on one ormore computers or logical partitions (LPARs). IBM WebSphere Application ServerNetwork Deployment allows you to set up a node agent to manage a subgroup ofthe application server processes in the implementation. A node agent monitors theapplication servers and routes administrative requests to them. The group ofapplication servers plus their associated node agent is called a managed node. Youcan have multiple managed nodes per implementation.

The node agents communicate with a deployment manager (DMgr). Deploymentmanagers are administrative agents that provide a centralized management viewfor the nodes. The group of processes (application servers and node agents)managed by a deployment manager is called a cell.

Cluster

SAN

HA mgt sw

Engine tier

Services tier


Clienttier

Database

Firewall

Backup loadbalancer

Loadbalancer

Webserver 1

Webserver 2


ServerDeployment

Manager


ServerNode 2


Server Node 1(failed)

ActiveComputer

PassiveComputer


HA mgt sw DBMS

Client workstations


Figure 20. WebSphere Application Server cluster with failed node


A cluster is a logical subgroup of the application servers within the cell that are allrunning the same set of applications and services. The application servers within acluster are called members of that cluster. The cluster is managed by theDeployment Manager in the cell.

The following diagram shows a cell that contains two managed nodes that aremanaged by a Deployment Manager. Each node contains multiple applicationservers that are managed by a node agent. Each node agent communicates withthe Deployment Manager. The diagram also shows a cluster that contains theapplication servers in each node.

To further enhance the high availability of the services tier, you can horizontallyscale the cluster by adding more managed nodes on other computers. Addingmore nodes also enhances performance and throughput, because the nodes in thecluster share the workload. You can also vertically scale the cluster by addingapplication servers to managed nodes on the same computer. Vertical scalingimproves performance and throughput, but does not improve availability except atthe application server level (that is, if an application server in a managed nodefails, other application servers in the node continue to function. If an entirecomputer fails, all application servers on the computer fail).

WebSphere Application Server supports several cluster topologies. IBM InfoSphereInformation Server supports most WebSphere Application Server cluster topologiesfor the services tier, with the following restrictions.v You must deploy each InfoSphere Information Server cluster in its own

dedicated cell. The cell cannot contain other clusters, Master Data Management(MDM) servers, or stand-alone application servers.

v The application servers within the cluster must be the same version: the samemajor release (for example, 6.1 or 7.0) and the same fix pack version (forexample, fix pack n.n.n.n).

v All computers spanned by a cluster must run the same operating system and fixpack level.

v You must deploy a front-end HTTP server, a load balancer (hardware orsoftware), or a mix of HTTP servers and load balancers (IP sprayer topology).For more information, see “Building a highly available and scalable front-endconfiguration to an IBM WebSphere Application Server cluster” on page 36.

Node Agent

Node Agent

Cell

DeploymentManager

ApplicationServer

ClusterApplicationServer

Node

Node

Figure 21. Cell that contains two managed nodes that are managed by a Deployment Manager


The following diagram illustrates vertical and horizontal InfoSphere InformationServer cluster topologies, and shows some topology elements that are not allowedin an InfoSphere Information Server cell.

Additional restrictions to assigning metadata repositories to InfoSphereInformation Server clusters include:v Each InfoSphere Information Server cluster must be assigned only one metadata

repository.v InfoSphere Information Server cluster members that are not part of the same

cluster cannot share the same metadata repository.v Members of a given InfoSphere Information Server cluster cannot be associated

with multiple metadata repositories.v An InfoSphere Information Server cluster member and a stand-alone application

server cannot share the same metadata repository. (The InfoSphere InformationServer installation program enforces this restriction.)

v You must use a distributed user registry such as the InfoSphere InformationServer custom registry or an LDAP registry. Local operating system registries donot work in cluster environments.

Application serverrunning InfoSphereInformation Server

services

Node (AIX)

Older applicationserver version

running InfoSphereInformation Server

services

Node


services

Stand-alonenode


services

Node (Linux)


services

Node (Linux)

Cluster

Cluster

Cluster (horizontallyand vertically scaled)

Not allowedThe cell must be dedicated to the cluster

Not allowedThe cell must be dedicated to the cluster,and all application servers must be thesame application server version

Not allowedAll nodes in the cell must run the sameoperating system

InfoSphere Information Server cell

Figure 22. Vertical and horizontal cluster topologies (allowed and not allowed)


The following diagram shows an InfoSphere Information Server cluster, andrelationships that are allowed and not allowed between the cluster members andmetadata repositories.

The following diagram shows the location of application server node agents andthe Deployment Manager in a sample configuration. There is only one DeploymentManager per cell, running on one of the computers. If the node agents are running,a cluster can continue to perform most runtime functions if the DeploymentManager is not active, so the Deployment Manager is not a single point of failurefor these operations. However, for administration operations such as IBMInfoSphere Information Services Director application deployment, the DeploymentManager must be running. Also, the WebSphere Application Server console ishosted in the Deployment Manager, so the Deployment Manager must be runningfor you to use this console.

Building a highly available and scalable front-end configurationto an IBM WebSphere Application Server clusterIf you deploy a WebSphere Application Server cluster within your IBM InfoSphereInformation Server implementation, you must provide a front-end configurationfor the cluster.

Cluster

Metadatarepository

Metadatarepository


services

Node


services

Node


Figure 23. Allowed and not allowed relationships between cluster members and metadata repositories

DeploymentManager

Cluster

Metadatarepository


services

Node


services

Node


Node Agent

Node Agent

Figure 24. Application server node agents and Deployment Manager in a sample configuration


The front-end configuration can consist of any of the following components locatedupstream of the cluster:v A front-end Web serverv A load balancerv A load balancer upstream of the Web servers (IP sprayer topology)

To maximize security, deploy firewalls at various key points within the topologythat you select. To improve delivery response, you can also deploy caching proxyservers upstream of the Web servers and load balancers.

Front-end Web servers:

If you deploy an IBM WebSphere Application Server cluster within your IBMInfoSphere Information Server implementation, you can provide a front-end Webserver upstream of the cluster.

InfoSphere Information Server supports IBM HTTP Server and Apache HTTPServer. For information on supported versions, go to the system requirements atwww.ibm.com/support/docview.wss?rs=14&uid=swg27016382. These softwareproducts are not shipped with InfoSphere Information Server.

A front-end Web server manages servlet and JSP requests. The Web server typicallyuses an internal workload management (WLM) plug-in to dispatch Web requests tothe appropriate cluster members and their Web containers. It performs thedispatches according to policies that are preconfigured in the WLM plug-in. Thefront-end Web server increases performance and security because the Web serverprovides a unique HTTP entry point to the cluster.

To prevent single points of failure at the Web server level, deploy a backupdedicated Web server to take over in case the active one fails.

The following diagram shows an InfoSphere Information Server cluster with afront-end Web server. A backup Web server is also deployed.

If you choose IBM HTTP Server, you can set up the Deployment Manager tomanage configuration and administration of the Web server. The Web server can bedefined either as a managed node or an unmanaged node.

Web server

ClusterApplication server


services

Node


services

Node


Webcontainer

Webcontainer

WLMplug-in

BackupWeb server

Figure 25. Cluster with front-end Web server



v If you want to use the Deployment Manager to manage Web servers in the samemanner as any other managed nodes in the cell (for example, to start or stopIBM HTTP Server, or to install the IBM HTTP Server plug-in configuration filethat contains the workload management policies that are defined for the cluster),define the Web servers as managed nodes.

v If you deploy the Web servers upstream of a firewall that protects the clustermembers, define the Web servers as unmanaged nodes. In this case, you canmanage the Web servers with the Deployment Manager by enabling the IBMHTTP Server Admin Process on the computer.

The following diagram shows an IBM HTTP Server instance that is defined as amanaged node. The Deployment Manager manages IBM HTTP Server through thelocal node agent.

The following diagram shows an IBM HTTP Server instance that is defined as anunmanaged node on a stand-alone server. A firewall separates the server from thecell. The Deployment Manager manages the IBM HTTP Server instance by usingthe IBM HTTP Server Admin Process.

If you use the Apache HTTP Server, you must define the instances as unmanagednodes. You cannot manage them by using the Deployment Manager. For example,

IBM HTTPServer

plug-in

Node agent


services

Application serverrunningInformation Server

services

InfoSphere

Webcontainer

Webcontainer

Deploymentmanager

Cluster

Node

Node


Node agent

Node agent

Node

Figure 26. IBM HTTP Server instance that is defined as a managed node

plug-in

Firew

all


services

Application serverrunningInformation Server

services

InfoSphere

Webcontainer

Webcontainer

Deploymentmanager

Cluster

Node

Node


Node agent

Node agentIBM HTTPServer

Stand-aloneserver

IBM HTTP ServerAdmin Process

Figure 27. IBM HTTP Server instance that is defined as an unmanaged node on a stand-alone server


you must copy the Web server plug-in configuration file to each Web servermanually.

Load balancing:

If you deploy an IBM WebSphere Application Server cluster within your IBMInfoSphere Information Server implementation, you can provide a load balancerupstream of the cluster.

InfoSphere Information Server supports many load balancer solutionsmanufactured by IBM and by other vendors.

The following table lists the advantages and disadvantages of a load balancerapproach.

Table 4. Advantages and disadvantages of a load balancer approach

Advantages of deploying a load balancer v Easier deployment: you do not have to setup a network of Web servers and thenconfigure the Web server plug-ins

v More load balancing algorithmalternatives: load balancers often offermore algorithms than the ones providedby Web server plug-ins, includingadvanced load-based balancing strategiesthat monitor usage levels on individualcomputers

Disadvantages of deploying a load balancer v Additional configuration required: youmust perform additional configuration tomaintain persistent connections betweenclients and servers (Web server plug-inshandle persistent connection maintenanceautomatically) and re-configure the loadbalancer whenever the downstreamcluster topology changes (for example,when a node is added or removed).

v Load balancers do not serve static HTML

v Hardware-based load balancers typicallycost more

plug-in


services


services

Webcontainer

Webcontainer

Deploymentmanager

Cluster

Node

Node


Node agent

Node agentApacheWeb Server

Stand-aloneserver

Figure 28. Apache HTTP Server


To prevent single points of failure at the load balancer level, consider deploying abackup load balancer to take over in case the active one fails.

The following diagram shows an InfoSphere Information Server cluster with afront-end load balancer. A backup load balancer is also deployed.

You cannot manage the load balancers by using the Deployment Manager.

Make sure to configure session affinity in the load balancer. There are severalmethods to achieve session affinity. The method you choose depends on theproduct that you use and the forwarding mechanism that you configure.Mechanisms include media access control (MAC) address forwarding, NetworkAccess Translation/Network Address Port Translation (NAT/NAPT) forwarding,and content-based forwarding. Layer 2 load balancers (load balancers that operateat the MAC layer) generally achieve session affinity by using a "stickiness to sourceIP address" approach. Layer 3 and higher load balancers (load balancers thatoperate at the IP layer and above) typically achieve session affinity by usingpassive cookies or a content-based technique. Session affinity is typicallyimplemented in this manner with HTTP servers. See the load balancerdocumentation for more information

IP sprayer topology:

To obtain high availability and the maximum balancing of server and workloadcapacity, deploy a load balancer upstream of a group of Web servers.

The load balancer performs intelligent balancing among the Web servers based onserver availability and workload capacity. Choose this topology to eliminate asingle point of failure at the Web server level. This arrangement also spreads theload of Web requests across multiple Web servers. IBM InfoSphere InformationServer supports many IP sprayer solutions manufactured by IBM and by othervendors.

To prevent single points of failure at the load balancer level, deploy a backup loadbalancer to take over in case the active one fails.

The following diagram shows an IP sprayer topology. The diagram shows anInfoSphere Information Server cluster with two front-end Web servers. A load

Loadbalancer

ClusterApplication server


services

Node


services

Node


Webcontainer

Webcontainer

BackupWeb server

Figure 29. Cluster with a front-end load balancer


balancer is deployed upstream of the Web servers. A backup load balancer is alsodeployed. The Web servers and load balancers are installed on separate servers.

Caching proxies:

To improve delivery response and reduce downstream traffic, you can also deploycaching proxies.

If caching proxy functionality is not embedded within your load balancerhardware, you can deploy caching proxy servers upstream of the Web servers andload balancers. IBM InfoSphere Information Server supports any caching proxythat can cache static and dynamic Web requests.

You cannot manage the caching proxies by using the Deployment Manager.

The following diagram shows a caching proxy server upstream of an IP sprayerconfiguration. A backup caching proxy server is also deployed.

Firewalls:

Webserver

Cluster


services

Node


services

Node


Webserver

Loadbalancer

Backupload balancer

Server Server

ServerServer

Figure 30. IP sprayer topology

Cluster


services

Node


services

Node


Webserver

Webserver

Server

Server

Loadbalancer

Backupload balancer

Server

Server

Cachingproxy

Backupcaching proxy

Server

Server

Figure 31. Caching proxy configuration


To secure access to your IBM InfoSphere Information Server cluster, deployfirewalls at various key points in the topology that you select.

For example, add a firewall in front of the caching proxies, load balancers, andWeb servers. Isolate them within a demilitarized zone (DMZ) to deny direct accessto internal components from clients that you do not trust. Alternatively, you canplace a firewall between the DMZ and the cluster. You can also add a firewallbetween the services tier and the metadata repository database.

Note: IBM WebSphere Application Server does not support deployment offirewalls between components within a cell. For example, the application serverdoes not support firewalls between nodes in a cell, or between nodes and theDeployment Manager in a cell.

The following diagram shows an InfoSphere Information Server cluster behind aDMZ. A firewall is located between the DMZ and the outside world. A firewall isalso located between the cluster and the DMZ. For maximum security, a firewall isalso located between the cluster and the metadata repository database.

If you deploy firewalls, make sure to open any ports through the firewalls that areused by InfoSphere Information Server.

IBM DB2 high availability optionsIBM offers several high availability DB2 configurations.

The configurations discussed in this documentation are:v DB2 clustering by using high availability clustering softwarev DB2 with high availability disaster recovery (HADR)

In either configuration, you can use DB2 automatic client reroute to enable IBMInfoSphere Information Server processes to reconnect to a standby node when afailover occurs.

DMZ Application serverrunning InfoSphereInformation Server

services

Node


services

Node

InfoSphere InformationServer cell

MetadatarepositoryF

ire

wa

ll

Fir

ew

all

Fir

ew

all

Webserver

Webserver

Server

Server

Loadbalancer

Backupload balancer

Server

Server

Figure 32. Cluster with firewalls


IBM DB2 clusteringTo provide a high availability DB2 configuration, you can create a DB2 clusteracross computers. In this configuration, the metadata repository database is sharedbetween nodes in the cluster. If a failover occurs, another node in the clusterprovides DB2 functionality.

To provide high availability, set up your cluster in an active-passive configurationwith a single active DB2 instance on one computer and one or more passiveinstances on the other computers. If the DB2 instance encounters a problem orfails, a passive instance can take over.

To manage this configuration, you can choose between several high availabilityclustering management software products. This software maintains a "heartbeat"signal between the nodes in the cluster. If the heartbeat fails on the active node,the software initiates failover to another node.

With this configuration, the DB2 failover is automatic, but might take severalminutes as the new instance acquires resources, repeats certain transactions andundoes other transactions. To minimize interruption and manual intervention,configure DB2 automatic client reroute. This function causes other IBM InfoSphereInformation Server components such as IBM WebSphere Application Server toautomatically reconnect to the new DB2 instance.

This configuration does not provide redundancy for the database itself. Instead, itprovides high availability for database client processes and smoothes thereconnection to the new node. To provide redundancy for the database itself,implement high availability disaster recovery (HADR).

The following diagram shows a topology that includes a clustered metadatarepository tier. In this case, HA cluster management software on the metadatarepository computers monitors DB2 processes specific to DB2. The software alsomonitors the health of the computer hardware and the network.


If the active database instance fails, the passive database instance becomes theactive instance. This process is shown in the following diagram.

MetadataRepositorycomputer(active)

HA mgt sw

DB2 DBMS

Cluster

SAN

HA mgt sw

Engine tier

Services tier


Clienttier

DB2DB

Firewall

Backup loadbalancer

Loadbalancer

Webserver 1

Webserver 2


ServerDeployment

Manager


ServerNode 2


Server Node 1

Activecomputer

Passivecomputer

MetadataRepositorycomputer(standby)

HA mgt sw

HA mgt sw

DB2 DBMS

Client workstations


Figure 33. Topology with a clustered metadata repository tier


IBM DB2 high availability disaster recovery (HADR)To provide high availability at the DB2 database level, you can create a DB2 highavailability disaster recovery (HADR) configuration.

In this configuration, a complete, separate copy of the database is maintained on astandby node at a local or remote location. The primary DB2 database processestransactions. It uses internal HADR processes to replicate transaction logs to thestandby node, where the logs are stored. A process at the standby node thenreplays the logged transactions directly to the standby database. The two copiesare maintained in synchronization or near-synchronization with each other.

DB2 processes normally access only the primary copy of the database. However, ifthe primary copy fails, an administrator triggers the standby copy to take over thetransactional workload. You can set up automatic client reroute to make thefailover behavior virtually transparent. If the primary copy becomes unavailable,automatic client reroute retries the connection to the failed primary copy. If thereconnection fails, automatic client reroute determines whether or not the standbycopy is available. If the server is available, automatic client reroute reroutes theapplication server connection to the standby copy. Pending transactions are rolled

Cluster

MetadataRepositorycomputer(failed)

SAN

HA mgt sw

Engine tier

Services tier


Clienttier

DB2DB

Firewall

Backup loadbalancer

Loadbalancer

Webserver 1

Webserver 2


ServerDeployment

Manager


ServerNode 2


Server Node 1

Activecomputer

Passivecomputer


HA mgt sw

HA mgt sw

DB2 DBMS

Client workstations


Figure 34. Clustered metadata repository tier with failed server


back and then reissued on the standby copy. Automatic client reroute can also beconfigured to reconnect to an alternate standby copy if the first standby copy isunavailable. Failover is quick (normally 10 seconds to 15 seconds if the servers areon the same LAN segment).

If the unavailable database becomes available again, it is automatically reintegratedas the new standby database and is resynchronized.

The following diagram shows an IBM InfoSphere Information Serverimplementation in which the metadata repository tier is set up in an HADRconfiguration.

The following diagram shows an HADR configuration after the primary databasecopy has failed. All transactions are directed to the standby copy.


(HADR primary)

DB2 DBMS

Cluster

SAN

HA mgt sw

Engine tier

Services tier


Clienttier

Firewall

Backup loadbalancer

Loadbalancer

Webserver 1

Webserver 2


ServerDeployment

Manager


ServerNode 2


Server Node 1

Activecomputer

Passivecomputer


(HADR standby)HA mgt sw

DB2 DBMS

Secondarydatabase

Primarydatabase

Transaction log records are copied to the standbyserver and replayed on standby database

Client workstations


Figure 35. HADR configuration


Oracle database high availability optionsIf you use an Oracle database system to host the metadata repository database orthe IBM InfoSphere Information Analyzer analysis database, increase theavailability of the metadata repository tier by implementing Oracle RealApplication Clusters (RAC).

An Oracle RAC configuration consists of multiple computers, each of which runsan Oracle instance, which is made up of processes that enable access to storeddata. Each Oracle instance has access to a common database file system across ahigh-speed network. If a computer or Oracle instance process fails, other Oracleinstances continue to provide service. Oracle database cluster managementsoftware (Oracle Clusterware) monitors and manages the Oracle RACconfiguration and tries to restart failed Oracle instances.

Client processes access the Oracle RAC configuration in the same way that theyaccess a single Oracle database instance. With Oracle RAC 11g, a virtual IP addressis assigned to each server in the cluster. If a node in the cluster fails, the virtual IPaddress fails over to another node. Then client processes can automaticallyreconnect.

Automatic clientreroute (ACR)reestablishesclient connectionto the standbydatabase

Cluster

MetadataRepositorycomputer(failed)

SAN

HA mgt sw

Engine tier

Services tier


Clienttier

Firewall

Backup loadbalancer

Loadbalancer

Webserver 1

Webserver 2


ServerDeployment

Manager


ServerNode 2


Server Node 1

Activecomputer

Passivecomputer


(HADR standby)HA mgt sw

Client workstations


DB2 DBMS

Secondarydatabase

Primarydatabase

Figure 36. HADR configuration after server failure


Nodes in an Oracle RAC cluster require a separate, private high-speed network formessaging between nodes. This network is called the interconnect.

The following figure shows an IBM InfoSphere Information Server topology thatincludes Oracle RAC. The two Oracle RAC node computers share access to adatabase farm.

If a node in the RAC cluster fails, other nodes continue to provide service.

For greater high availability, you can implement an Oracle RAC on ExtendedDistance Clusters configuration. In this configuration, nodes in the cluster arelocated in physically separated sites.

To install InfoSphere Information Server in an Oracle RAC configuration, install toa single node in the configuration. Then perform additional steps to causeInfoSphere Information Server to operate with the complete Oracle RACconfiguration.

Other considerations when designing for high availabilityYou must also introduce redundancy at a number of different levels to reduce oreliminate single points of failure.

Cluster


SAN

HA mgt sw

Engine tier

Services tier


Firewall

Backup loadbalancer

Loadbalancer

Webserver 1

Webserver 2


ServerDeployment

Manager


ServerNode 2


Server Node 1

Activecomputer

Passivecomputer


HA mgt sw

Databasefarm

Oracle Real Application Clusters(RAC) cluster

Clienttier

Client workstations


Figure 37. Topology with Oracle RAC configuration


The server and software topology that you choose is only part of a highavailability solution. You must also introduce redundancy at a number of differentlevels to reduce or eliminate single points of failure. Here are some areas toconsider:v Your storage solutionv Your networkv Security within your network and within your sitesv Your electrical infrastructurev Your backup, restore and disaster recovery contingenciesv Availability of support staff to respond to problems

Designing a high availability topologyThere are many ways to implement high availability and scalability within an IBMInfoSphere Information Server installation. Choose the implementation that fitsyour needs.

When determining which topology and implementation to choose, consider thefollowing factors:v The level of high availability that you require for each system you implementv The degree to which the system is likely to scale in the futurev Your security needsv Complexity factorsv Maintainability factorsv Cost

High-availability level

When considering your topology, evaluate the level of high availability that yourequire:v Consider the amount of downtime that you can tolerate. Can you afford to have

a nonoperational system for 15 minutes? For 5 minutes?v Consider the amount of automation that you need. Must the system take care of

failover and recovery automatically, or is a system administrator available tointervene?

v Consider how your needs might differ depending upon how the system is used:whether it is a development system, testing system, or production system. Forexample, how important is it that the development system or testing system ishighly available?

v Consider the level of high availability that you require for different softwaretiers. The tiers are used differently depending upon whether the system is usedprimarily for development or in production. The tiers are also used differentlydepending upon the product modules that you have installed.

Note: A failure on one tier typically renders the entire system nonoperationaluntil the problem is fixed or failover occurs.

Performance and throughput requirements

Refer to “Capacity planning” on page 57 to analyze your performance, throughput,and storage needs.


The amount of scalability that each high availability solution offers differs fromsolution to solution. When you are choosing a topology and architecture, considerhow the system might need to scale to support greater performance andthroughput requirements in the future. For examples of how the solutions differ,see the scenario comparisons.

Security requirements

Different topologies lend themselves to different security possibilities. Considerhow you want to implement firewalls and other security precautions between thedifferent tiers, between the computers in each tier, and between the system andexternal data sources and targets. These considerations are important for theservices tier and the engine tier that must have fast communications paths withexternal systems.

For more information about security, refer to the IBM WebSphere ApplicationServer documentation:v IBM WebSphere Application Server ND 6.1 security: http://

publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/welc6topsecuring.html

v IBM WebSphere Application Server ND 7.0 security: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/welc6topsecuring.html

Complexity factors

High availability and scalability add layers of complexity to the installation.Eliminating single points of failure requires implementation of complex redundanthardware and software components.

When you architect your system, consider the amount of complexity that your ITstaff must support. Is there sufficient in-house expertise to support the system thatyou design? If your high availability features fail, the amount of time you need tobring the system online again might negate any uptime gains that your featuresprovide.

Begin with a relatively simple system that is well within your ability to support.As your IT group becomes familiar with support of the system, implement thehigh availability features on a staggered schedule until your entire system is inplace. This approach also gives the group experience with changing the systemand provides them with knowledge for future system scaling.

Maintainability factors

Consider the maintenance costs of the system that you design. Determine whataspects of maintenance to automate, and which aspects to leave in the hands ofsupport personnel.

High availability features can simplify system maintenance. For example, in aclustered system, you can take servers offline for certain updates withoutrendering the entire system nonoperational.

In an organization where specific departments are responsible for differentsystems, consider isolating the tiers on separate computers so each department can"own" a tier. For example, in an organization where a group of database


http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/welc6topsecuring.html






administrators is responsible for corporate databases, consider isolating themetadata repository tier on computers that are within their control.

Cost

Implementing high availability typically adds to the initial cost of the system. Extrahardware, software, training, and other costs make the initial outlay larger.However, the productivity gains that the highly available system provides mightmake up for these costs.

Scenario: Two-server, active-passive topologyThis scenario describes a two-server, active-passive topology.

In this topology, two computers share a storage area network (SAN). Allserver-side tiers are installed on the SAN. One computer (the active server) hoststhe tiers. The other computer (the passive server) is started, but is not running anytier software. High availability (HA) software such as IBM Tivoli SystemAutomation for Multiplatforms is installed on both the active server and thepassive server. The HA software maintains a heartbeat that indicates that the activeserver is operational.

This topology is described in “Active-passive topology” on page 28.

Table 5. Scenario analysis: Two-server, active-passive topology

Consideration Advantages and disadvantages

Level of high availability v A host failure causes all tiers to berestarted.

v When a node fails, there might be up to a10-minute outage.

v If any component fails, there is thepotential for job design loss (clientdisconnected).

v Software failure might not cause afailover.

Scalability v The topology is difficult to scale: addingnodes does not increase performance orthroughput.

v To increase engine performance, addparallel engine compute nodes.

Security v Complexity is fairly low.

v A security breech on the server mightjeopardize the entire system.

Complexity v Complexity is fairly low.

v No IBM WebSphere Application Server ordatabase clustering experience is required.

v HA software might be difficult toimplement.

Maintainability Failover allows you to take one serveroffline for maintenance, while the rest of thesystem remains operational.

Cost This topology requires minimal hardwareand software.


Scenario: Fully clustered topologyThis scenario describes a topology in which all tiers are implemented withinclusters.

In this topology, both IBM WebSphere Application Server clustering and metadatarepository tier clustering are implemented:

This topology includes several computers. Two of the computers host the enginetier in an active-passive server cluster. Other computers host the services tier,where the WebSphere Application Server is set up in a cluster. Other computershost the metadata repository tier, where the database system is set up in a cluster.

A topology that is similar to this one is described in “IBM DB2 clustering” on page43.

Table 6. Scenario analysis: Fully clustered topology

Consideration Notes

Level of high availability v The failure of a node in the WebSphereApplication Server cluster does not causeservice interruption. However, a slightdegradation of performance might occur.

v The failure of a node in the metadatarepository tier cluster causes minimal orno service interruption.

v The failure of a node in the engine tiercauses up to a 10-minute interruption inengine operation, while failover occursand the other node takes over. However,activities that do not require the enginetier continue without interruption.

Scalability v The topology is highly scalable.

v The topology supports many concurrentusers.

v You can add nodes to the WebSphereApplication Server cluster to improve theperformance and throughput of theapplication server.

v For metadata repository configurationswithin an Oracle Real ApplicationClusters (RAC) cluster, add nodes toimprove the performance and throughputof the metadata repository.

v To increase engine performance, addadditional parallel engines.

Security v The topology requires a complex securitysetup that includes multiple firewalls andother security considerations.

v If the security of one node or tier iscompromised, the entire system is notnecessarily compromised.


Table 6. Scenario analysis: Fully clustered topology (continued)

Consideration Notes

Complexity v The topology is highly complex.

v You must have knowledge of WebSphereApplication Server clustering and eitherIBM DB2 clusters or Oracle RAC clusters.

v The topology might require theimplementation of high-availabilitycluster-management software, whichmight be difficult to implement.

Maintainability v The maintenance of this topology iscomplex.

v The topology is highly flexible: you cantake a server offline for maintenance, andthe rest of the system remains operational.

v The isolation of each tier on one or moreseparate computers allows groups of userswithin the organization to "own"particular tiers.

Cost The cost is high.

Parallel processing and grid topologiesTo maximize the IBM InfoSphere Information Server engine efficiency andthroughput, create a parallel processing or grid topology.

In these topologies, the workload for each job is distributed across severalprocessors. The processors can be located on the same computer or on differentcomputers that are connected over a network. The InfoSphere Information Serverparallel engine uses the processors and computers concurrently to complete eachjob. The parallel engine and the InfoSphere Information Server engine make up theengine tier.

You can configure the InfoSphere Information Server parallel framework for gridcomputing processing. Install a supported resource manager to enable the dynamicassignment of available computer nodes (physical computers) at runtime.

Parallel processing configurationsIn a parallel processing configuration, the workload for each job is distributedacross several processors.

In IBM InfoSphere DataStage, you design and run jobs to process data. Normally, ajob extracts data from one or more sources, transforms the data, and loads it intoone or more new locations.

In a parallel processing configuration, the workload for each job is distributedacross several processors on one or more computers, called compute nodes. WithinInfoSphere DataStage, the user modifies a configuration file to define multipleprocessing nodes. These nodes work concurrently to complete each job quickly andefficiently. A conductor node computer orchestrates the work.

Parallel processing environments are categorized as symmetric multiprocessing (SMP)or cluster or massively parallel processing (MPP) systems.


Symmetric multiprocessing (SMP) systems

In a symmetric multiprocessing (SMP) environment, multiple processors shareother hardware resources, such as memory or storage. They have a singleoperating system.

The workload for a parallel job is distributed across the processors in the system.The actual speed at which the job completes might be limited by the sharedresources in the system. To scale the system, you can increase the number ofprocessors, add memory, or increase storage. The scalability strategy that youimplement depends on how your job is limited within your current system.

Cluster or massively parallel processing (MPP) systems

In a massively parallel processing (MPP) system, many computers are physicallyhoused in the same chassis, as shown in the following diagram:

CPU CPU CPU CPU

Disk

SharedMemory

Figure 38. Symmetric multiprocessing (SMP) system

Figure 39. Massively parallel processing (MPP) system


A cluster system is physically dispersed, as shown in the following diagram:

In a cluster or MPP environment, performance is improved because no resourcesmust be shared among physical computers. To scale the system, you can addcomputers and associated memory and disk resources.

Note: In an MPP system, a file system is commonly shared across the network.This configuration allows program files to be shared instead of installed onindividual nodes in the system.

Grid configurationsIn a grid configuration, a resource manager dynamically allocates resources for jobprocessing.

In an IBM InfoSphere Information Server parallel processing configuration, youmodify a configuration file to assign resources to a job. To change the degree ofparallelism, or the servers on which a job runs, you modify the configuration fileto include the new number of nodes and associated servers. This architecturemakes the association of nodes used by a job static.

With a grid implementation, a resource manager manages the pool of availableresources and dynamically allocates them as jobs are submitted for processing. Foreach job, the resource manager waits until resources are available and thengenerates a configuration file that assigns resources to the job. The systemminimizes the idle time for each processor and helps ensure that resources areused in the most efficient manner.

Grid topologies vary widely. They depend in part on the storage implementationsuch as Network Attached Storage (NAS) or storage area networks (SAN).However, in any grid topology, one server is designated as the conductor node,

Network

Processingnode

Figure 40. Cluster system


and other servers are designated as compute nodes. All jobs are initiated from theconductor node, and processed on the compute nodes.

A grid can be implemented on relatively low-cost hardware, with minimumadditional costs. To scale the grid, add additional nodes and register them with theresource manager. You can take nodes out of service without halting processing ofjobs within the grid.

The standard InfoSphere Information Server suite supports grid implementationson Red Hat Enterprise Linux only, with IBM LoadLeveler®. Each computer in thegrid must use the same operating system and release level. The computers must beconnected and accessible within the same high-speed local area network. You canset up this implementation by using the instructions in this documentation.

The following diagram shows a typical grid configuration. The diagram shows anIBM BladeCenter® chassis with 14 blades. External disk storage is a NetworkAttached Storage (NAS) system. The storage is accessible from all blades throughthe NFS server installed in the first node (node 0).

In the diagram, the InfoSphere Information Server metadata repository andservices tier are installed on the first blade (node 1). The server engine, resourcemanager, and one parallel engine are installed on the second blade (node 2). Allother blades (nodes 3 through 14) are compute nodes that provide processingpower for the grid. The client tier is installed on a workstation that is connected tothe blade system (this computer is not shown).


Capacity planningYou plan the use of disk, volume group, and file system resources to create anoptimal operating environment for IBM InfoSphere Information Server.

As part of capacity planning for your installation, size your file systems anddatabases to accommodate your anticipated needs. After the installation, continuemonitoring the file systems to ensure that sufficient space is available.

Attention: If the file system runs out of space, InfoSphere Information Serverstops functioning correctly.

RAID and SAN configurations

Performance of a job (for IBM InfoSphere DataStage, IBM InfoSphere QualityStage,and IBM InfoSphere Information Analyzer) depends on all components beingoptimized. For RAID (Redundant Array of Independent Disks) and SAN (systemarea network) configurations, maximum performance is a combination ofmaximum bandwidth (controllers and disk) and minimized contention.

Node0Node1Node2

Node5Node4Node3

Node8Node7Node6

Node11Node10Node9

Node14Node13Node12

NASNAS

NFSserver

ServicesRepository

EngineRM

Figure 41. Grid configuration


The following guidelines can assist in the configuration of RAID or SANtechnologies: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 withInfoSphere Information Server file systems and other applications or servers.

v Consider isolating multiple mount points to separate high-speed diskinterconnects and controllers.

v Consider the trade-off between the granularity of file systems and theunderlying configuration in comparison to the available, unused storage.

v Do not create overly complex device configurations. These configurations can bedifficult 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 enginesthat do not feature parallelism.

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


Chapter 4. Planning Step 4: Determining your installationstrategy

Determine the specific set of steps to take to install IBM InfoSphere InformationServer 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 installInfoSphere Information Server. Alternatively, you might choose to usecomponents that you already have installed and running. For example, youmight use a database system or application server that is supported byInfoSphere Information Server. Components that might need preinstallationare:– 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 thatsatisfies 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 localcomputer when it installs other InfoSphere Information Servercomponents.

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 InfoSphereInformation Server components on a tier by tier basis.For an implementation on multiple computers, install the tiers in the followingorder:v Metadata repository tierv Services tierv Engine tierYou can install the client tier at any time.Not all products require an engine tier. IBM InfoSphere FastTrack, IBMInfoSphere Business Glossary, and IBM InfoSphere Business Glossary Anywheredo not require an engine tier.Complete the following phases for each tier.


v Preparation: prepare your computers for the installation, and preinstall anycomponents that require it.

v InfoSphere Information Server installation: run the installation program toinstall InfoSphere Information Server components on the tier computers.You do not run the installation program for the metadata repository tiercomputers if you have preinstalled the database system and configured thedatabases within the database system.

v Tier-specific postinstallation tasks: some installations require you to doadditional tasks that are specific to one or more tiers after installingInfoSphere Information Server.

3. After your product modules are installed, complete additional configurationtasks. Some of the tasks are common to all installations. Other tasks are specificto installations of certain product modules only.

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

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

End

Start

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)

Prepare computer Host2 for the client tier


Complete postinstallation configuration tasks

Planning

Tier-by-tierinstallation

Postinstallationconfiguration

Figure 42. Installation process flowchart: two-computer topology


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

Determining your database installation strategyDetermine the database system to install for your metadata repository and planyour installation strategy. If installing IBM InfoSphere Information Analyzer, alsodetermine the database system to install for the analysis databases and how youwill install it (or whether to use the database system that you are using for themetadata repository database).

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

End

Start

Plan, build, and test your topology

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



Prepare computer Host2 for the services tier



Prepare computer Host3 for the client tier


Complete postinstallation configuration tasks

Planning

Tier-by-tierinstallation

Postinstallationconfiguration

Figure 43. Installation process flowchart: three-computer topology

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

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

Depending on the product modules that you choose to install, you must install oneor 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 samedatabase system instance as distinct databases. This topology is the default.

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

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

Determining the database system to use for each database

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

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

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

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

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

Determining whether to use an existing database systeminstance for a database

Instead of installing a new database system for a database, you can configure thedatabase in an existing database system instance. The database system must satisfythe 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 theservices tier and engine tiers are installed.


http://www.ibm.com/support/docview.wss?uid=swg27016382



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

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

Determining the database installation methodDetermine how to install the database system for each database, and how to createthe database within the database system.

The procedure for setting up IBM InfoSphere Information Server databases differsdepending upon the database system that you use and the location of the databasesystem.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.7on the target computer and create the database within it. DB2 9.7 is bundledwith InfoSphere Information Server. Within the installation program, selectthe Metadata Repository tier installation option to install DB2 and create thedatabases.

– 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 thedatabases 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 theinstance. Within the installation program, select the Metadata Repositorytier installation option to create the databases.

- If the DB2 instance is not located on the target computer, create thedatabases within the instance before running the InfoSphere InformationServer installation program. To create the databases, use scripts that areprovided with the InfoSphere Information Server software. In this case,when you run the installation program you do not use the MetadataRepository tier installation option at all.For more information about the database creation scripts, see “Preparing anexisting 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 withInfoSphere Information Server, and install it by using the DB2 databasesystem installation program instead of the InfoSphere Information Serverinstallation program. See “Preinstalling the IBM DB2 database system” onpage 147.

v For another supported database system, set up the databases by using one of thefollowing methods:– Preinstall the database system and create the databases within it before

running the InfoSphere Information Server installation program. To create thedatabases, use scripts that are provided with the InfoSphere InformationServer software.

– Use an existing database system installation. Before you run the InfoSphereInformation Server installation program, create the databases within thedatabase system by using scripts that are provided with the InfoSphereInformation Server installation media.

In either case, when you run the installation program you do not use theMetadata Repository tier option at all.


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

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

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

The following table summarizes the installation options.

Table 7. Summary: database system installation and database creation options forsupported configurations

ConfigurationDatabase system installationoptions Database creation options

DB2 9.1, non-clusteredconfiguration

Preinstall before you run theInfoSphere InformationServer installation program

Use either of the followingmethods:

v Use the InfoSphereInformation Serverinstallation program.

v Use the scripts on theInfoSphere InformationServer installation media.


Preinstall before you run theInfoSphere InformationServer installation program




DB2 9.5, clusteredconfiguration

Preinstall, and then createthe cluster.

Use the scripts on theInfoSphere InformationServer installation media.

DB2 9.5, high availabilitydisaster recovery (HADR)configuration

Preinstall, and then createthe HADR configuration.

Use either of the followingmethods to create thedatabase on the primarynode:




Table 7. Summary: database system installation and database creation options forsupported configurations (continued)

ConfigurationDatabase system installationoptions Database creation options



v Use InfoSphereInformation Serverinstallation program toinstall

v Preinstall before you runthe InfoSphere InformationServer installationprogram




DB2 9.7, clusteredconfiguration

Preinstall, and then createthe cluster.


DB2 9.7, high availabilitydisaster recovery (HADR)configuration


v Use InfoSphereInformation Serverinstallation program toinstall

v Preinstall before you runthe InfoSphere InformationServer installationprogram

Use either of the followingmethods to create thedatabase on the primarynode:



Oracle database system (anysupported version),non-clustered configuration

Preinstall before you run theInfoSphere InformationServer installation program.

Use scripts on InfoSphereInformation Serverinstallation media.

Oracle Real ApplicationClusters (RAC) cluster (anysupported version)

Preinstall, and then createthe RAC setup.


Microsoft SQL Serverdatabase system (anysupported version),non-clustered configuration

Preinstall before you run theInfoSphere InformationServer installation program.


Sizing the analysis databasesAn analysis database is a component that IBM InfoSphere Information Analyzeruses when it runs analysis jobs.

The extended analysis information is stored in the analysis databases. Theextended 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 theanalysis results.

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


When you plan for the size of your databases, consider these factors that affect thesize of each database:v Number of tables to be analyzedv Number of columns in tables to be analyzedv Number of unique records within these tablesv Number of char and varchar columnsv Types of analysis to be done

Unless you use sampled analysis, an analysis database might be larger than thecombined size of all the analyzed data sources.

Determining how to install WebSphere Application ServerAs part of the services tier configuration, determine which version of IBMWebSphere 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 IBMInfoSphere Information Server.

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

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

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

WebSphere Application Server ND version 7.0 is bundled with InfoSphereInformation Server. For 64-bit platforms, the bundled version is 64-bit. For 32 bitplatforms, 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. Theinstallation program creates a server profile that is named InfoSphere and anapplication server instance that is named server1. This application server islicensed for use only with InfoSphere Information Server.

v Preinstall WebSphere Application Server ND 6.1 or 7.0, or use an existinginstallation of one of these versions. In this case, you must create the profilesmanually.

To set up a clustered WebSphere Application Server ND configuration for highavailability and scalability, preinstall WebSphere Application Server ND. Configurethe cluster, profiles, and front-end dispatcher before you install InfoSphereInformation Server. See Chapter 23, “WebSphere Application Server clustering forhigh availability and scalability,” on page 323.


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

Note: Before you make changes to your computers, back up those computerswhere you plan to install InfoSphere Information Server. See the IBM InfoSphereInformation 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 installationdirectory.

v Database storage directories for the metadata repository database, and for theIBM InfoSphere Information Analyzer databases and IBM InfoSphereQualityStage Match Designer database if you are installing these productmodules).

Isolate each functional subgroup of components in its own separate file system toaccommodate different performance and capacity characteristics and backuprequirements. File systems should be expandable without requiring destruction orrecreation, 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 Serverinstallation program or other installation programs during installation. Otherdirectories 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 69v “Additional directories created on the metadata repository tier computer (IBM

DB2 only)” on page 71v “Additional directory created on the services tier computer” on page 73v “Additional directories created on each engine tier computer” on page 74v “Additional directories created on each client tier computer” on page 75

Directories that must be present on all tier computers beforeinstallation

The following directories are required on all tier computers before you run theInfoSphere Information Server installation program.

Temporary directories

The temporary directories will contain temporary files required by theinstallation program. The files are not needed after installation and can besafely removed. You do not have to back up temporary directories.

The root user, the user who runs the installation program, and all otherInfoSphere Information Server users must have read, write, and executepermissions to the temporary directories.

Put the temporary directories on a file system that has high-speedread-write performance.


The following table provides operating system-specific information aboutthe temporary directories.

Table 8. Temporary directories: operating system-specific information

Operating system Default directory path Additional requirements

AIX Linux

UNIX

v /tmp The file system that containsthe temporary directory mustmeet the systemrequirements for temporaryspace on its physicalpartition. Use the dfcommand to see the amountof available disk space perfile system. If the commandresults do not list thedirectory or its parentdirectory, use the amount onthe root file system (/).

Windows The directory specified bythe TEMP environmentvariable. This directory istypically the “x:\Documentsand Settings\user_name\Local Settings\temp”directory, where user_name isthe Microsoft Windows loginname of the user doing theinstallation. On WindowsServer 2008 and Windows 7,this directory is typically the“x:\Users\user_name\AppData\Local\Temp”directory.

The total number ofcharacters in the temporarydirectory path and the pathof the files that theinstallation program extractsinto the path cannot exceed256 characters. Long pathnames might cause theinstallation to fail.

Solaris v /tmp

v /var/tmp

None

Home directory for user IDs

The home directory contains existing user IDs and (by default) the IDs thatthe installation program creates.

The Administrator ID or the root user ID that performs the installationmust be able to write to the directory and all subdirectories.

Regularly back up this directory.

The following table provides operating system-specific information aboutthe home directory.


Table 9. Home directory: operating system-specific information


Linux UNIX /home/user_name Owners must have at least755 permissions for theirdirectories and parentdirectories, and haveread/write/execute access toall subdirectories.

If the home directory is on anetwork file system (NFS),export the file system withthe no_root_squash optionenabled and the nosetuidoption off.

Windows “c:\Documents andSettings\user_name” orc:\Users\user_name

None

Solaris Solaris zones allow you to divide a Solaris computer into multiplelogical computers. You can install InfoSphere Information Server into a global zoneor a non-global zone. You cannot install InfoSphere Information Server into aSparse Zone. When installing into a global zone or a non-global zone, the root usermust have write access to the following files and directories on all logicalcomputers: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.Depending on the tier, this directory structure might include the engine, libraries,communication agents, Job Monitor, Resource Tracker, Java runtime environment,configuration files, and uninstallation files.

This directory is created by the InfoSphere Information Server installation program.

Both the root user and the user who runs the installation program must have read,write, and execute permissions to the InfoSphere Information Server installationdirectory.

Plan for this directory on high performance file systems.

Back up this directory after the installation and after any InfoSphere InformationServer updates.


The following table provides operating system-specific information about theInfoSphere Information Server installation directory.

Table 10. InfoSphere Information Server installation directory: operating system-specificinformation


Linux UNIX /opt/IBM/InformationServer v The dsadm account(administrator for theInfoSphere InformationServer engine) must havethese permissions:

Read and executeFor everythingunder the/opt/IBM/InformationServerdirectory

Read For the /opt,/opt/IBM, and/opt/IBM/InformationServerdirectories

Important: Directoryownership and permissionsare set when you run theInfoSphere InformationServer installation program.

v If the installation directory ison a network file system(NFS), export the file systemwith the no_root_squashoption enabled and thenosetuid option off.

v Do not install the softwareon the top-level mountpoint. Instead, install inseparate subdirectorieswithin a mount point. Theinstallation changesownership and permissionsof directories that youinstall, and not all mountpoints allow these changes,causing the installation tofail.

Windows C:\IBM\InformationServer Do not install on virtual drives(mapped, substituted, or SANdrives).

Tip: The installation directory path can contain only the following characters:v 0-9v [a-z][A-Z]v - (hyphen)v _ (underscore)v . (period)


On Windows, space characters are also allowed.

Do not use accented characters, double byte characters, or the following specialcharacters in the path: ` ! @ # $ % ^ & * ( ) | \/ ? > <, { } [ ]

Additional directories created on the metadata repository tiercomputer (IBM DB2 only)

The following directories are created if a new DB2 instance is installed by theInfoSphere Information Server installation program or the DB2 installationprogram. For other database system types, refer to the database systemdocumentation.

Linux UNIX The user who runs the installation program must have writeaccess to file systems including /var and /usr/local/bin directories. If thesedirectories are on network mounted file systems such as the IBM AFS® file system,confirm that the installation user ID has write access.

Database server installation directory

This directory contains the database server executable files and libraries.

DB2 must reside on a local file system. DB2 supports running the databasesoftware from a mounted NFS volume, but does not support installation toa mounted NFS volume.

The following table provides operating system-specific information aboutthe database server installation directory.

Table 11. Database server installation directory: operating system-specific information


Linux UNIX /opt/IBM/db2 None

Windows C:\IBM\SQLLIB None

Tip: The installation directory path can contain only the followingcharacters:v 0-9v [a-z][A-Z]v - (hyphen)v _ (underscore)v . (period)


Do not use accented characters, double byte characters, or the followingspecial characters in the path: ` ! @ # $ % ^ & * ( ) | \/ ? > <, { } [ ]

DB2 instance owner home directoryThe following table provides operating system-specific information aboutthe DB2 instance owner home directory.


Table 12. DB2 instance owner home directory: operating system-specific information


Linux UNIX v DB2 instance owner:/home/db2inst1

v DB2 Administration Serveruser ID: /home/dasusr1

The DB2 instance ownermust have read, write, andexecute permissions to itshome directory, and readpermission to its parentdirectory.

If the directory is on anetwork file system (NFS),export the file system withthe no_root_squash optionenabled and the nosetuidoption off.

Solaris To install into aglobal zone or a non-globalzone, the root user musthave write access to thesedirectories.

Windows DB2 instance owner:“c:\Documents andSettings\db2admin” orc:\Users\db2admin

The DB2 instance ownermust have full control of itsown home directory.

Database storage directoryThis directory will contain data for the operations of InfoSphereInformation Server. This data is separate and distinct from the data in yourdata sources, and can include the following databases:v Metadata repository. This database is typically named xmeta.v Analysis databases for IBM InfoSphere Information Analyzer. If there is

only one analysis database, it is typically named iadb.v Test results database for IBM InfoSphere QualityStage (no default

directory)

The directory is created by the InfoSphere Information Server installationprogram. Put the directory on a file system that has high-speed read-writeperformance.

Regularly back up this directory. In general, you back up a database byusing the method provided by the database system.

The following table provides operating system-specific information aboutthe database storage directory.


Table 13. Additional requirements and default paths for the database storage directory


Linux UNIX /opt/IBM/InformationServer/Repository

v The DB2 database instanceowner (db2inst1) mustown the directories thatstore the metadatarepository and the analysisdatabases.

v If the directory is on anetwork file system (NFS),export the file system withthe no_root_squash optionenabled and the nosetuidoption off.

Windows C:\DB2 None

Additional directory created on the services tier computer

The following directory is created on the services tier computer by the InfoSphereInformation Server installation program or WebSphere Application Serverinstallation program.

Application server installation directoryThis directory will contain WebSphere Application Server executable filesand libraries, including the following services:v Shared services of InfoSphere Information Serverv Product module-specific services

The following table provides operating system-specific information aboutthe application server installation directory.

Table 14. Application server installation directory: operating system-specific information


Linux UNIX /opt/IBM/WebSphere/AppServer


Windows C:\IBM\WebSphere\AppServer None





Additional directories created on each engine tier computer

The following directories are created on each engine tier computer. The directoriesare created by the InfoSphere Information Server installation program.

Project directories (runtime shadow repository) for the InfoSphere InformationServer engine

These directories will contain the following project-related items:v Job executablesv Compiled routinesv Buildop stage typesv Job runtime artifactsv Job status recordsv Cached versions of design objectsv Message handler filesv DSParams file for project-specific variables that the IBM InfoSphere

DataStage administrator definesv Files that the Hashed File stage creates for server jobs (default location).

However, a better practice is to create the files for the Hashed File stageon a separate file system.

Because disk space typically is limited in the default directory within theinstallation file system, you might want to create projects in their own filesystem. When a job is compiled, its source is extracted from the metadatarepository and stored in the runtime repository to facilitate jobcompilation. Project directories can grow to contain thousands of files andsubdirectories depending on the number of projects, jobs, and runtimemetadata for each job.

InfoSphere Information Analyzer creates its own project directory foroperations such as column analysis. In addition, each InfoSphereInformation Analyzer project is associated with an InfoSphere DataStageproject within InfoSphere Information Analyzer. The InfoSphere DataStageproject directories are located on the engine tier at the location that isconfigured in InfoSphere DataStage.

The following table provides operating system-specific information aboutthe project directories.

Table 15. Project directories: operating system-specific information


Linux UNIX /opt/IBM/InformationServer/Server/Projects


Windows C:\IBM\InformationServer\Server\Projects

None

Directories for IBM InfoSphere DataStage and IBM InfoSphere QualityStageapplication files (excluding project data)

These directories will contain items such as secured parameter files, dataset header files, custom components, schemas, SQL, shell scripts, customjob logs, and reports.


Data file storage directoriesThese directories will contain temporary and intermediate data files for theparallel engine:v Engine temporary storage (scratch, temp, and buffer)v InfoSphere Information Server artifacts, such as surrogate key filesv Segment files for parallel data setsv Staging and archival storage for source files

The engine uses temporary storage to hold data sets and to temporarilybuffer virtual data set records. Plan for these directories outside of theinstallation directory for InfoSphere Information Server.

Use local (internal) storage that is on a high-performance, shared filesystem with the same mount point that is available on all servers.

For better performance, create separate file systems for each data andscratch resource partition. For example, if the development and theproduction teams share an installation, separate the data and scratchdirectories for each team on different file systems to create separateenvironments.

After installation, edit the parallel configuration files to assign resources,such as the disk and scratch file systems, to jobs at run time. For moreinformation about the parallel engine configuration file, see the IBMInfoSphere DataStage and QualityStage Parallel Job Developer's Guide

The following table provides operating system-specific information aboutdata file storage directories.

Table 16. Data file storage directories: operating system-specific information


Linux UNIX v /opt/IBM/InformationServer/Server/Datasets

v /opt/IBM/InformationServer/Server/Scratch

If the directories are on anetwork file system (NFS),export the file system withthe no_root_squash optionenabled and the nosetuidoption off.

Windows v C:\IBM\InformationServer\Server\Datasets

v C:\IBM\InformationServer\Server\Scratch

None

Additional directories created on each client tier computer

The following directory is created on each client tier computer by the InfoSphereInformation Server installation program.

InfoSphere Information Server client installation directoryThis directory will contain the installed software for IBM InfoSphereInformation Server console, InfoSphere DataStage and QualityStageAdministrator clients, and other clients.


If you install a client tier on a computer where an engine tier is installed,the client tier and engine tier must share the same base directory (forexample, C:\IBM\InformationServer). Do not install multiple versions ofthe client on a system that also has an engine tier.

The following table provides operating system-specific information aboutthe InfoSphere Information Server client installation directory.

Table 17. InfoSphere Information Server client installation directory


Windows C:\IBM\InformationServer\client

None




Secure Sockets Layer (SSL) configurationIBM InfoSphere Information Server supports Secure Sockets Layer (SSL)communication between the application server and client components. If yourenvironment requires confidentiality at the EJB or HTTP level, you can enable SSL.

SSL provides two benefits:v Encryption: Data sent over an SSL connection is encrypted.v Identification: Communication is allowed only if the server is positively verified.

Before communications begin, the server sends the client a certificate. Thesignature in the certificate is decrypted by the client to verify the authenticity ofthe sender.

SSL is not enabled by default within InfoSphere Information Server. SSL addsgreater security to your system, but also requires more administrative work andcan be error-prone. There is also a performance impact. Therefore, carefullyconsider the benefits and drawbacks before enabling SSL. You might not need SSLif you have a strong firewall in place.

You can enable SSL for the following types of client-server communication:v Inbound secure HTTP (HTTPS).v Inbound RMI/IIOP (EJB communication).

SSL configuration is optional. If you do not configure HTTPS, HTTP is usedinstead.

To enable SSL, do the following tasks:v Configure the application server to communicate by using SSL.


v Configure InfoSphere Information Server components to use SSL. Thesecomponents include:– Agents on the engine tier computers– Command-line tools on the engine tier computers, client tier computers, and

services tier computer– Rich client programs on the client tier computers. These programs include the

InfoSphere Information Server console, the IBM InfoSphere DataStage andQualityStage Director, Designer, and Administrator clients, and the IBMInfoSphere FastTrack client.

Application server HTTPS and SSL for inbound RMI/IIOPconfiguration

Application server HTTPS configuration differs depending upon how theapplication server is installed:v If you install IBM WebSphere Application Server by using the InfoSphere

Information Server installation program, both the HTTP and HTTPS protocolsare enabled in WebSphere Application Server.

v If you preinstall WebSphere Application Server before running the InfoSphereInformation Server installation program:– If you use the built-in WebSphere Application Server HTTP server, both the

HTTP and HTTPS protocols are enabled in WebSphere Application Server.– If you set up a separate front-end HTTP server, manually configure HTTPS.

Do this task before InfoSphere Information Server is installed. See“Configuring the front-end HTTP server for HTTPS” on page 155.

Application server SSL for RMI/IIOP is disabled by the InfoSphere InformationServer installation program. Use the WebSphere Application Server administrativeconsole to reenable this communication protocol in the application server. Do thistask after InfoSphere Information Server is installed. See “Enabling SSL forinbound RMI/IIOP” on page 233.

InfoSphere Information Server component HTTPS configuration

To configure InfoSphere Information Server components to communicate with theapplication server by using HTTPS, use one of the following methods:v Manually edit configuration files on each computer that contains the

components, and install the HTTPS certificate on the computer.v Automatically configure the components from within the installation program

during installation. This method is available for most installation scenarios.However, you must use the completely manual method in the followingscenarios:– You install WebSphere Application Server by using the InfoSphere

Information Server installation program. In this case, you must use themanual method after installation to configure the services tier for HTTPS. Ifyou install the client tier or the engine tier in the same installation pass, youmust also manually configure the tiers that you install in the pass for HTTPS.

– You install the client tier only in an installation pass, either on a computerthat has no other tiers installed, or on a computer that has other tiersinstalled. In this case, you must use the manual method after installation toconfigure the client tier for HTTPS.

See “Manually configuring InfoSphere Information Server components to useHTTPS” on page 234.


For certain product modules, other steps are required:v For IBM InfoSphere Business Glossary Anywhere, the certificate must be

installed on the host computer to allow HTTPS communication. See Installingthe Business Glossary Anywhere client.

v For IBM InfoSphere Business Glossary Client for Eclipse, the certificate must beinstalled on the host computer and added to the Java Runtime Executable (JRE)truststore. See “Installing IBM InfoSphere Business Glossary Client for Eclipse”on page 221.

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, IBM InfoSphere Business Glossary,or IBM InfoSphere Metadata Workbench, the user must specify an HTTPS URLand port in the browser.

v For rich client tools, the user must specify the HTTPS-enabled port whenlogging in.

When the server certificate changes (for example, a certificate expires or a newmanaged node is added to a WebSphere Application Server cluster), InfoSphereInformation Server clients do not dynamically retrieve the new server certificates.The InfoSphere Information Server UpdateSignerCerts tool retrieves server signercertificates. You must run the UpdateSignerCerts tool manually on all computersthat host components that communicate with WebSphere Application Server byusing SSL. See “Running UpdateSignerCerts after enabling SSL or changing SSL atthe cell level” on page 236.

Project naming conventionsUse these conventions when you name your projects.

IBM InfoSphere DataStage, IBM InfoSphere QualityStage, and IBM InfoSphereInformation Analyzer store jobs, analysis, and logs in these projects.

You need to choose the name of one InfoSphere DataStage project during the initialinstallation. The name of a project is limited to a maximum of 40 characters. Theproject name can contain alphanumeric characters, including underscores (_).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 thesource code control. As projects are promoted through the source control, the nameof 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


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 isno redundancy for high availability.

Complete the following steps:1. Plan and build your topology2. Install and configure each tier3. 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 18. Topology planning and building tasks

Description For more information

Review the system requirements. Chapter 1, “Planning Step 1: Reviewing systemrequirements and release notes,” on page 3

Learn about tiers and components. Chapter 2, “Planning Step 2: Understanding tiers andcomponents,” on page 5

Design the topology of your installation. Chapter 3, “Planning Step 3: Designing an installationtopology,” on page 15

Plan your installation. Chapter 4, “Planning Step 4: Determining yourinstallation strategy,” on page 59

Determine the database system to install for yourmetadata repository and plan your installation strategy.If installing IBM InfoSphere Information Analyzer, alsodetermine the database system to install for the analysisdatabases and how you will install it (or whether to usethe database system that you are using for the metadatarepository database).

“Determining your database installation strategy” onpage 61

Determine whether to preinstall IBM WebSphereApplication Server or preconfigure an existinginstallation of WebSphere Application Server.

“Determining how to install WebSphere ApplicationServer” on page 66

Build and test the hardware infrastructure. Refer to the hardware documentation.

Plan the volume groups and file systems on which youare installing IBM InfoSphere Information Server. Verifythat you have sufficient storage space in your filesystems.

See the system requirements, and “Planning volumegroups and file systems” on page 67.

Linux UNIX On each computer, create thetemporary directories /tmp and /var/tmp, if they do notalready exist. The root user must have read, write, andexecute permissions to these directories. The installationprogram must be run as root.

“Planning volume groups and file systems” on page 67

(Optional) Review the tasks necessary to enable SecureSockets Layer (SSL) within your installation.

“Secure Sockets Layer (SSL) configuration” on page 76


Table 18. Topology planning and building tasks (continued)


Obtain the InfoSphere Information Server software andany applicable fix packs. Uncompress the software ontoeach tier computer.

Chapter 6, “Obtaining IBM InfoSphere InformationServer software,” on page 131

On all tier computers, verify name resolution, and openTCP ports for InfoSphere Information Server across anyapplicable firewalls.

“Verifying the network and opening ports” on page 133

Linux UNIX Update the kernel parameters anduser limits on each computer.

“Modifying kernel parameters and user limits (Linux,UNIX)” on page 137

Prepare each computer to run the InfoSphere InformationServer installation program, and back up any criticaldata on the computers.

“Preparing to run the installation program” on page 177

2. Install and configure each tier

For each tier, complete the computer preparation tasks. Then install IBMInfoSphere Information Server components, and perform postinstallation tasks.

Install and configure the tiers in this order:v Metadata repository tierv Services tierv Engine tierv Client tier

You can install more than one software tier on the same computer. In this case, youcomplete the planning and preparation tasks for the tiers on the computer. Thenrun the installation program only once for that computer, installing the softwarefor the tiers. Then complete the postinstallation tasks for the tiers on the computer.

For example, if the metadata repository tier and services tier components areinstalled on computer Host1, and the engine tier and client tier are each installedon computers Host2 and Host3, complete the tasks in this order.1. Metadata repository tier and services tier preparation tasks on computer Host1.2. Installation of metadata repository tier and services tier components on

computer Host1 by using the installation program.3. Engine tier preparation tasks on computer Host2.4. Installation of engine tier components on computer Host2, by using the

installation program.5. Client tier preparation tasks on computer Host3.6. Installation of client tier components on computer Host3 by using the

installation program.

Not all product modules require an engine tier. IBM InfoSphere FastTrack, IBMInfoSphere Business Glossary, and IBM InfoSphere Business Glossary Anywhere donot require an engine tier.

2a. Metadata repository tier installation task list

To configure the metadata repository tier, follow the steps in the following task list.


Table 19. Installation tasks: Metadata repository tier


Create the following administration accounts on themetadata repository tier computer. Log in to eachaccount to confirm that it functions properly:

v Owner of the metadata repository

v (If installing InfoSphere Information Analyzer) Theowner of the analysis database

v If installing the DB2 database system:

– (All operating systems) DB2 database administratoruser

– Linux UNIX DB2 database instance owner

– Linux UNIX DB2 fenced user

“Setting up administrator and owner accounts” on page142

If you decide to preinstall DB2 or another supporteddatabase system, install the database system now.

Database system documentation. For the DB2 databasesystem, see “Preinstalling the IBM DB2 database system”on page 147

If you preinstalled DB2, configure the databases withinDB2 by using scripts. Alternatively, configure thedatabases when you run the InfoSphere InformationServer installation program.

If you preinstalled another database system, configurethe databases by using scripts.

“Preparing an existing DB2 database system by usingscripts” on page 149

Run the InfoSphere Information Server installationprogram if necessary.

Run the InfoSphere Information Server installationprogram for this tier in either of the following situations:

v To install the DB2 database system on the targetcomputer and create the metadata repository andanalysis databases within it. See Part 3, “Installing IBMInfoSphere Information Server software,” on page 165.

v To create the metadata repository and analysisdatabase within a local preinstalled supported DB2database system instance. See “Preparing an existingDB2 database system by using scripts” on page 149.

If you preinstall the DB2 database system or anotherdatabase system and create the databases within it byusing scripts that are provided with the InfoSphereInformation Server software, do not run the installationprogram for this tier.

2b. Services tier installation task list

To configure the services tier, follow the steps in the following task list.

Table 20. Installation tasks: Services tier


Preinstall WebSphere Application Server, if you decidenot to use the InfoSphere Information Server installationprogram to install it.

“Preinstalling WebSphere Application Server” on page153

Preconfigure an existing WebSphere Application Serverinstallation if necessary.

“Configuring an existing WebSphere Application Serverinstallation (non-clustered installation)” on page 154


Table 20. Installation tasks: Services tier (continued)


(Optional) To increase security, configure the WebSphereApplication Server front-end Web server to communicateby using secure HTTP (HTTPS). Do this configuration ifyou are preinstalling WebSphere Application Server orpreconfiguring an existing installation, and you areconfiguring a separate front-end HTTP server.Note: If you install WebSphere Application Server byusing the InfoSphere Information Server installationprogram, both the HTTP and HTTPS protocols areenabled in WebSphere Application Server. Theseprotocols are also enabled if you preinstall WebSphereApplication Server but use the built-in HTTP server.

“Configuring the front-end HTTP server for HTTPS” onpage 155

Run the InfoSphere Information Server installationprogram.


2c. Engine tier installation task list

If your installation requires an engine tier, follow the steps in the following tasklist to plan and configure the tier.

Note: If you are creating a configuration with more than one server engine, repeatthese steps for each server engine.

Table 21. Installation tasks: Engine tier


Linux UNIX For non-English locales, make surethat the locale and encoding are set correctly. Theinstallation program uses the locale and encodinginformation of the computer to determine whether it canprovide language support.

“Setting the locale for the target computer” on page 157

Create an administrator account for the InfoSphereInformation Server engine. Log in to the account toactivate the password.




Review the system requirements to choose a supportedC++ compiler for job development, and install it in itsdefault location.

“Installing a C++ compiler for job development” on page159

2d. Client tier installation task list

To configure your client tier, follow the steps in the following task list.

Note: If you are creating a configuration with more than one client computer,repeat these steps for each client computer.


Table 22. Installation tasks: Client tier


Run the installation program:

1. Double-click the setup icon to start the installationprogram. The program windows display in yourdefault Web browser.

2. In the installation program, accept all defaults, exceptin the Tier Selection page, choose Client only.Note: If you are using the client-only installationmedia, the Tier Selection page does not display. Theprogram installs the client tier only.

3. Complete the rest of the installation.


(Optional) Manually configure secure HTTP (HTTPS) forthe client tier.

“Manually configuring InfoSphere Information Servercomponents to use HTTPS” on page 234

3. Perform postinstallation configuration tasks

After you run the InfoSphere Information Server installation program for each tier,perform these tasks:

Table 23. Postinstallation configuration tasks (all tiers)


Windows If necessary, set up explicit firewall exceptionsfor client-side executable files that require networkaccess.

(Optional) Configure Secure Sockets Layer (SSL):

v Enable SSL for inbound RMI/IIOP. When you installInfoSphere Information Server in an IBM WebSphereApplication Server Network Deployment 6.1 or laterenvironment, SSL for inbound RMI/IIOPcommunications is disabled by default.

v If the installation program did not configure HTTPSfor a tier computer during IBM InfoSphere InformationServer installation, manually configure HTTPS for thattier computer.

Chapter 16, “Enablement of Secure Sockets Layer (SSL),”on page 233

Configure security within InfoSphere Information Server:

1. Choose a user registry and configure it for InfoSphereInformation Server.

2. Create users and groups in the user registry.

3. Assign security roles to users and groups.

4. Configure InfoSphere Information Server enginesecurity. Map credentials if necessary.

5. Assign project roles if required by the installed suitecomponents.

Optionally, also:

v Configure IBM WebSphere Application Server fornon-root administration.

v Configure InfoSphere Information Server agents fornon-root administration.

v Configure the Auditing service.

Chapter 17, “Configuring security for IBM InfoSphereInformation Server,” on page 243


Table 23. Postinstallation configuration tasks (all tiers) (continued)


Configure IBM InfoSphere DataStage and IBMInfoSphere QualityStage (if installed):

1. If you installed globalization support (NLS), ensurethat IBM InfoSphere DataStage users have the correctsettings specified for localization.

2. Configure access to ODBC data sources.

3. For systems that have large numbers ofsimultaneously connected users or large numbers ofsimultaneously running jobs, tune the server engine.

Optionally, also:

v Configure the parallel processing environment.

v Migrate jobs that you created in an earlier version ofInfoSphere DataStage to the current version.

v Configure the IBM InfoSphere QualityStage MatchDesigner.

v Set up the application server to run SQA orinvestigation reports.

v Test the installation.

“Configuring IBM InfoSphere DataStage and IBMInfoSphere QualityStage” on page 245

Test the IBM InfoSphere Information Services Directorinstallation (if installed).

“Testing the IBM InfoSphere Information ServicesDirector installation” on page 256

Configure IBM InfoSphere Information Analyzer (ifinstalled).

“Configuring IBM InfoSphere Information Analyzer” onpage 256

Configure IBM InfoSphere Business Glossary (ifinstalled).

“Configuring IBM InfoSphere Business Glossary” onpage 258

Configure IBM InfoSphere Metadata Workbench (ifinstalled).

“Configuring IBM InfoSphere Metadata Workbench” onpage 258

Configure IBM InfoSphere FastTrack (if installed). “Configuring IBM InfoSphere FastTrack” on page 258

(Optional) Run the IBM Support Assistant Lite forInfoSphere Information Server tool to verify theinstallation.

“Installation verification and troubleshooting” on page197

Sample scenario A: Basic client-server topologySample 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 tomigrate financial reporting data from several systems to a single system of record.They decide to create two separate IBM InfoSphere Information Serverinstallations: a small development system where they build and test projects andjobs, and a larger production system (see “Sample scenario B: Topology withisolated engine tier and parallel engine configuration” on page 88). For thedevelopment system, a simple topology will be used where a single server with astorage mechanism (Host1 in the following diagram) services five clientworkstations.


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 5Advanced Platform will be used on an AMD platform.

For the clients, existing Microsoft Windows XPworkstations will be used.

Determine the database configuration. Decide to use IBM DB2 for the metadata repository.Decide to use the InfoSphere Information Serverinstallation program to create a stand-alone DB2 instanceon the server.

Determine whether to preinstall IBM WebSphereApplication Server, or preconfigure an existinginstallation of WebSphere Application Server.

Decide to use the InfoSphere Information Serverinstallation program to create a stand-alone WebSphereApplication Server ND instance on the server.

Host1

Enginetier

Servicestier


Network

Client tier

Clientworkstations

Figure 44. Sample scenario A topology


Table 24. Scenario A: Planning and building the topology (continued)

Task User action

Plan the volume groups and file systems on which youare installing InfoSphere Information Server.

Plan for the following directories:

v The home directory for user accounts. Verify that theroot user account has write access to this directory.

v Temporary storage for the installation program, asrecommended within the system requirements.

v The InfoSphere Information Server installation path ona high-performance file system. The default path is tobe used.

v The WebSphere Application Server path. The defaultpath is to be used.

v A location for data set and scratch directories, outsidethe InfoSphere Information Server installationdirectory.

Verify all permissions, verify that all installationdirectories are empty, and verify that all file systemshave sufficient free space.

On each computer, create the temporary directories /tmpand /var/tmp, if they do not already exist. The root usermust have read, write, and execute permissions to thesedirectories. The installation program must be run as root.


To avoid complexity, SSL will not be enabled in thisinstallation.

Build and test the hardware infrastructure. Set up the server and install the operating system. Set upa high-speed network to allow the server and the clientsystems to communicate.

Obtain the installation software. Obtain the InfoSphere Information Server software andany applicable fix packs. Uncompress the software ontoeach computer.

Verify the network and open ports. Verify the short and long host name resolution betweenthe server and the client workstations. Open allnecessary ports through the firewall.

Modify kernel parameters and user limits. Verify that the DB2 and WebSphere Application Serverkernel parameter and user limit requirements are met onthe server.

Prepare to run the installation program. Prepare each computer to run the InfoSphere InformationServer installation program, and back up any criticaldata on the computers.

Installing and configuring the metadata repository, services, andengine tiers

Because all tiers except the client tier are installed on the same server, the usercompletes all preparation tasks for the metadata repository tier, services tier, andengine 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, ensurethat the locale and encoding are set correctly.


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 theserver. Log in to each account to confirm that it functionscorrectly:


v DB2 database administrator user

v DB2 database instance owner

v DB2 fenced user

v Administrator account for the InfoSphere InformationServer engine.

Preinstall the database system if necessary. Decide to install DB2 when the InfoSphere InformationServer installation program is run. Decide to configurethe metadata repository within the DB2 when theInfoSphere Information Server installation program isrun.

Preinstall WebSphere Application Server if necessary. Decide to install WebSphere Application Server when theInfoSphere Information Server installation program isrun.


Run the installation program for this computer asdescribed in “Running the installation program forScenario A” on page 198.

Install a C++ compiler for job development. Review the system requirements to choose a supportedC++ compiler for job development, and install it in itsdefault location.

Installing the client tier

After reviewing the system requirements, the user completes the following tasks oneach client workstation:

Table 26. Scenario A: Client tier installation tasks

Task User action


Run the installation program as described in “Runningthe installation program for Scenario A” on page 198.

Postinstallation tasks

After installing all of the InfoSphere Information Server tiers, complete the tasksthat 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 thisscenario.


Table 27. Scenario A: Postinstallation configuration tasks (continued)

Task User action

Configure security within InfoSphere Information Server. v Use the WebSphere Application Server AdministrativeConsole to configure the system to use the localoperating system user registry.

v Use operating system administration tools to createIBM InfoSphere DataStage users and groups within theregistry.

v Use the InfoSphere Information Server console toassign security roles to the users and groups.

v Use the InfoSphere Information Server Web console toset up the engine tier to use the local operating systemuser registry. No credential mapping is required.

Ensure that InfoSphere DataStage users have the correctsettings specified for localization.

Decide to run the InfoSphere Information Server engineby using the default locale settings that are inherited bythe operating system users. No action is necessary.

Configure access to ODBC data sources. Configure the ODBC drivers to access ODBC datasources.



Sample scenario B: Topology with isolated engine tier andparallel engine configuration

Sample scenario B is installation with a computer that is dedicated to the IBMInfoSphere Information Server engine.

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





Table 28. Scenario B: Planning and building the topology

Task User action


Determine the topology of the system. For the servers, 64-bit Red Hat Enterprise Linux 5Advanced Platform will be used on an AMD CPU orprocessor.

Decide to use the same Microsoft Windows XPworkstations that host the client tier in Scenario A. Noadditional client tier installation is required.

Determine the database configuration. Decide to use IBM DB2 for the metadata repository.Decide to use the InfoSphere Information Serverinstallation program to create a stand-alone DB2 instanceon the server.


Decide to use the InfoSphere Information Serverinstallation program to create a stand-alone WebSphereApplication Server ND instance on the server.

Client tier


Host3Host1

Services tier Parallel processing

Clientworkstations

Network

Host2

Engine tier

Figure 45. Sample scenario B topology


Table 28. Scenario B: Planning and building the topology (continued)

Task User action

Plan the volume groups and file systems on which youare installing InfoSphere Information Server.

Plan for the following directories on all tier computers:

v The home directory for user accounts. Verify that theroot user account has write access to this directory.

v Temporary storage for the installation program, asrecommended within the system requirements.

v The InfoSphere Information Server installation path ona high-performance file system. The default path is tobe used.

v A location for data set and scratch directories, outsidethe InfoSphere Information Server installationdirectory.

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

Verify all permissions, verify that all installationdirectories are empty, and verify that all file systemshave sufficient free space.

On each computer, create the temporary directories /tmpand /var/tmp, if they do not already exist. The root usermust have read, write, and execute permissions to thesedirectories. The installation program must be run as root.


Decide to implement SSL within the installation, toenhance security.

Build and test the hardware infrastructure. Set up the server and install the operating system. Set upa high-speed network to allow the server and the clientsystems to communicate.


Verify the network and open ports. Verify the short and long host name resolution betweenall servers and the client workstations. Open allnecessary ports through the firewall.

Modify kernel parameters and user limits. Verify that the DB2 and WebSphere Application Serverkernel parameter and user limit requirements are met onthe servers.

Prepare to run the installation program. Prepare each computer to run the InfoSphere InformationServer installation program, and back up any criticaldata on the computers.

Installing and configuring the metadata repository and servicestiers

The user completes all preparation tasks for the metadata repository tier andengine tier together on Host1, then runs the IBM InfoSphere Information Serverinstallation 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.


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 toeach account to confirm that it functions correctly:


v The owner of the analysis database


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 InformationServer installation program is run. Decide to configurethe metadata repository within the DB2 when theInfoSphere Information Server installation program isrun.

Preinstall WebSphere Application Server if necessary. Decide to install WebSphere Application Server when theInfoSphere Information Server installation program isrun.

(Optional) Configure the WebSphere Application Serverfront-end Web server to accept secure HTTP (HTTPS)calls.

Since WebSphere Application Server will be installed byusing the InfoSphere Information Server installationprogram, the WebSphere Application Server built-in Webserver is configured for both HTTP and HTTPS.


Run the installation program for this computer asdescribed in “Running the installation program forScenario B” on page 201.

Installing and configuring the engine tier

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

Note: The user does not create a parallel engine configuration yet. Parallel engineconfiguration 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, ensurethat the locale and encoding are set correctly.

Set up administrator and component owner accounts. Create the Administrator account for the InfoSphereInformation Server engine. Log in to the account toconfirm that it functions correctly.


Run the installation program for this computer asdescribed in “Running the installation program forScenario B” on page 201.




Because the same Microsoft Windows XP workstations for Scenario A are used forScenario B, no additional client tier installation is required. However, theworkstations 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 thesystem 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 thisscenario.

(Optional) Configure Secure Sockets Layer (SSL). v Enable SSL for inbound RMI/IIOP. When you installInfoSphere Information Server in an IBM WebSphereApplication Server Network Deployment 6.1 or laterenvironment, SSL for inbound RMI/IIOPcommunications is disabled by default.

v Manually configure the metadata repository/servicestier computer for HTTPS. Since WebSphereApplication Server was installed by the InfoSphereInformation Server installation program, the programdid not prompt the user to enable HTTPS.

Configure security within InfoSphere Information Server. v Use the WebSphere Application Server AdministrativeConsole to configure the system to use the localoperating system user registry.

v Use operating system administration tools to createIBM InfoSphere DataStage users and groups within theregistry.


v Use the InfoSphere Information Server Web console toset up the engine tier to use the local operating systemuser registry on its own computer. Use the InfoSphereInformation Server Web console to map credentialsbetween local operating system user registry on theengine tier computer and the local operating systemuser registry on the metadata repository/services tiercomputer.

v In new InfoSphere Information Server installations,Secure Sockets Layer (SSL) is disabled by default. Theuser reenables SSL to maximize system security.

Ensure that InfoSphere DataStage users have the correctsettings specified for localization.

Decide to run the InfoSphere Information Server engineby using the default locale settings that are inherited bythe operating system users. No action is necessary.



Table 31. Scenario B: Postinstallation configuration tasks (continued)

Task User actions

Create parallel engine nodes. v Copy the parallel engine components to the targetcomputer.

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 paralleljobs, and the paging space for the parallel engine. Alsoupdate the /etc/magic file.

v Configure connectivity to source databases.

v Stop and restart the InfoSphere Information Serverengine.



New installation road map (high availability active-passiveconfiguration)

Use this road map to complete a new installation of a two-server active-passiveconfiguration 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.







Verify that you are installing the correct packages foryour operating system.

Chapter 1, “Planning Step 1: Reviewing systemrequirements and release notes,” on page 3


Learn about the topology of the active-passive highavailability configuration.

“Active-passive topology” on page 28




Determine the database system to install for yourmetadata repository and plan your installation strategy.If installing IBM InfoSphere Information Analyzer, alsodetermine the database system to install for the analysisdatabases and how you will install it (or whether to usethe database system that you are using for the metadatarepository database).

“Determining your database installation strategy” onpage 61

Determine if you need to preinstall IBM WebSphereApplication Server or preconfigure an existinginstallation of WebSphere Application Server.

“Determining how to install WebSphere ApplicationServer” on page 66

Configure the servers, the network, and the storagedevice. v Linux UNIX “Setting up the servers,

network, and storage (System Automation forMultiplatforms example)” on page 303

v Windows “Setting up the servers, network, andstorage (MSCS example)” on page 317

Plan the volume groups and file systems on which youare installing IBM InfoSphere Information Server. Verifythat you have sufficient storage space in your filesystems.


Linux UNIX On both computers, create thetemporary directories /tmp and /var/tmp, if they do notalready exist. The root user must have read, write, andexecute permissions to these directories. The installationprogram must be run as root.




Obtain the InfoSphere Information Server software andany applicable fix packs. Uncompress the software ontoeach computer.


On both computers, verify name resolution, and openTCP ports for InfoSphere Information Server across anyapplicable firewalls.


Linux UNIX Update the kernel parameters anduser limits on both computers.


Prepare both computers to run the InfoSphereInformation Server installation program, and back upany critical data on the computers.


2. Install and configure the tiers

The servers will accommodate the metadata repository tier, services tier, andengine tier. For this reason, run the IBM InfoSphere Information Server installationprogram only once to install the software on the mass storage device. Then run theinstallation program on each client tier computer to install the client tier software.

To manage the cluster and enable failover, install high availability software such asIBM Tivoli System Automation for Multiplatforms.

2a. InfoSphere Information Server metadata repository, services, and engine tiersoftware installation task list


To configure your tier software, follow the steps in the following task list.

Table 33. Installation tasks: Metadata repository, services, and engine tiers


Acquire and install high availability cluster managementsoftware on both engine tier servers, and set up thecluster.

Refer to the documentation for your high availabilitycluster management software. For exampleconfigurations, see the following topics:

v Linux UNIX “Installing the high availabilitysoftware (System Automation for Multiplatformsexample)” on page 304

v Windows “Setting up the cluster (MSCS example)”on page 317

Set the service IP address. Refer to the documentation for your high availabilitycluster management software. For exampleconfigurations, see the following topics:

v Linux UNIX “Setting up the virtual IPaddress (System Automation for Multiplatformsexample)” on page 305

v Windows “Setting up the virtual IP address (MSCSexample)” on page 318

Linux UNIX Define and start a resource group. Refer to the documentation for your high availabilitycluster management software. See “Defining and startingthe resource group (System Automation forMultiplatforms example)” on page 306.

For non-English locales, make sure that the locale andencoding are set correctly. The installation program usesthe locale and encoding information of the computer todetermine whether it can provide language support.


Set up administrator and component owner accounts onthe shared storage device.


If you decide to preinstall DB2 or another supporteddatabase system, install the database system now.

For DB2, see “Preinstalling the IBM DB2 databasesystem” on page 147. For other database systems, see thedatabase system documentation.

If you preinstalled DB2, configure the databases withinDB2 by using scripts. Alternatively, configure thedatabases when you run the InfoSphere InformationServer installation program.

If you preinstalled another database system, configurethe databases by using scripts.

v “Preparing an existing DB2 database system” on page148

v “Using a database system other than DB2” on page152

Preinstall WebSphere Application Server NetworkDeployment on the shared storage device, if you decidenot to use the InfoSphere Information Server installationprogram to install it.

“Preinstalling WebSphere Application Server” on page153


Table 33. Installation tasks: Metadata repository, services, and engine tiers (continued)


(Optional) To increase security, configure the WebSphereApplication Server front-end Web server to accept secureHTTP (HTTPS) calls. Do this configuration if you arepreinstalling WebSphere Application Server orconfiguring an existing installation, and you areconfiguring a separate front-end HTTP server.Note: If you install WebSphere Application Server byusing the InfoSphere Information Server installationprogram, both the HTTP and HTTPS protocols areenabled in WebSphere Application Server. Theseprotocols are also enabled if you preinstall WebSphereApplication Server but use the built-in HTTP server.


Install a C++ compiler on the shared storage device forjob development.

“Installing a C++ compiler for job development” on page159

Preconfigure the IBM InfoSphere QualityStage MatchDesigner database.

Chapter 11, “Preparing for the IBM InfoSphereQualityStage Match Designer database,” on page 161


1. From the is-suite directory on the installationmedia, run the following command to start theinstallation program:

./setup -verbose

2. Using a supported web browser on a Windowscomputer, open the URL that the ./setup commanddisplays.

3. Follow the prompts in the wizard.

v In the High Availability Server ClusterConfiguration page, click Server clusterconfiguration. In the Virtual host name field, enterthe virtual host name that was created when theHA software was configured.

v Whenever prompted for an installation directory,specify a path on the shared storage device.

v (Optional) To configure HTTPS, when theinstallation program prompts you, click Use SecureSockets Layer (SSL) for HTTP communication. Inthe Port field, type the HTTP dispatcher portnumber on which secure HTTP (HTTPS) haspreviously been configured.

For example configurations, see the following topics:

v Linux UNIX “Installing IBM InfoSphereInformation Server in the cluster (System Automationfor Multiplatforms example)” on page 309

v Windows “Installing IBM InfoSphere InformationServer in the cluster (MSCS example)” on page 318

Set up the resource agent scripts. Go to the documentation for your high availabilitycluster management software. For exampleconfigurations, see the following topics:

v Linux UNIX “Setting up the high availabilitycontrol scripts (System Automation for Multiplatformsexample)” on page 309

v Windows “Setting up high availability control scripts(MSCS example)” on page 319

Test the high availability configuration. Simulate active cluster node failures and network failuresand observe the results. For an example based on TivoliSystem Automation for Multiplatforms, see “Testing theconfiguration (System Automation for Multiplatformsexample)” on page 311.


2b. Client tier installation task list


Note: If you are creating a configuration with more than one client computer,repeat these steps for each client computer.







Chapter 12, “Installing new software,” on page 167








Chapter 15, “Firewall exceptions for client-side executablefiles (Windows),” on page 231



v If the installation program did not configure HTTPSduring IBM InfoSphere Information Server installation,manually configure HTTPS.


Test the engine tier failover function. Go to the documentation for your high availabilitycluster management software. For exampleconfigurations, see the following topics:

v Linux UNIX “Testing the configuration(System Automation for Multiplatforms example)” onpage 311

v Windows “Testing the configuration (MSCSexample)” on page 319










Optionally, also:

v Configure IBM WebSphere Application Server fornon-root administration.





1. If you installed globalization support (NLS), ensurethat IBM InfoSphere DataStage users have the correctsettings specified for localization.

2. Configure access to ODBC data resources.

3. For systems that have large numbers ofsimultaneously connected users or large numbers ofsimultaneously running jobs, tune the server engine.

Optional:



v Configure the IBM InfoSphere QualityStage MatchDesigner.






Configure IBM InfoSphere Information Analyzer (ifinstalled).

“Configuring IBM InfoSphere Information Analyzer” onpage 256







See “Installation verification and troubleshooting” onpage 197


Sample scenario C: Two-server active-passive high availabilitytopology

Sample scenario C is a topology that includes two computers that can fail over toone another in case of failure.

A small industrial company has purchased IBM InfoSphere Information Server andplans to use IBM InfoSphere DataStage, IBM InfoSphere QualityStage, and IBMInfoSphere Information Analyzer for data integration. They expect to have three orfour developers for the project.

They do not expect a great deal of volume on their production system. However,the system must be highly available. To minimize hardware costs, they decide toimplement a two-server active-passive topology for this system. All componentsare to run on one server and fail over to the other server if a hardware, network,or operating system failure occurs, or if an administrator forces a failover formaintenance purposes. While the failover is occurring, the system isnonoperational.

They decide to create two separate IBM InfoSphere Information Serverinstallations:v A small development system where projects and jobs are built and tested. The

configuration is identical to “Sample scenario A: Basic client-server topology” onpage 84.

v A more highly available production system, using the two-server active-passiveconfiguration with a storage mechanism.

Several client workstations will access both systems.

To increase processing throughput, the passive node will be used as a parallelengine compute node while the primary node is active.






Table 36. Scenario C: Planning and building the topology

Task User action


Determine your installation topology. For the servers, 64-bit Red Hat Enterprise Linux 5Advanced Platform will be used on an AMD platform.For the clients, existing Microsoft Windows XPworkstations will be used.


Decide to use the InfoSphere Information Serverinstallation program to create a stand-alone WebSphereApplication Server ND instance on the SAN.


Parallel processing

Host1(Active)



Host2(Passive)

Enginetier

Servicestier

Databaseinstance

Client tier

Clientworkstations

Enginetier

(installed)

Servicestier

(installed)

Database

SAN

Figure 46. Sample scenario C topology


Table 36. Scenario C: Planning and building the topology (continued)

Task User action

Configure the servers, networks, and storage device. Set up the servers with redundant connections to twoseparate high-speed networks. The heartbeat signal is totravel over a serial network.

Create an /opt/IBM directory on each server and mountthe storage device on the active server. Make sure thatthe directory is shared and has the correct permissions.

Also, because the metadata repository tier and servicestier are to be installed in this server configuration, ensurethat the following directories on the storage device areshared and have the correct permissions:

v The /opt/IBM/WebSphere directory for WebSphereApplication Server

v The /opt/IBM/db2 directory, and the IBM DB2 instanceowner, administrator, and fenced user directories forDB2

Plan volume groups and file systems.. Plan for the following directories and paths:

v The home directory for user accounts. Create anidentical directory on both servers. Verify that the rootuser account has write access to this directory.

v Temporary storage for the installation program, asrecommended within the system requirements. Thisdirectory is located on the primary server localstorage.

v The InfoSphere Information Server installation path.This directory is on the SAN.

v The WebSphere Application Server path. This directoryis on the SAN.

v A location for data set and scratch directories, outsidethe InfoSphere Information Server installationdirectory. This directory is on the SAN.

Verify all permissions, verifies that all installationdirectories are empty, and verifies that all file systemshave sufficient free space.

Review Secure Sockets Layer (SSL) configuration tasks. SSL will be enabled in this configuration.

Verify the network and open ports. On both computers, verify name resolution, and openTCP ports for InfoSphere Information Server across anyapplicable firewalls.

Modify kernel parameters and user limits. Update the kernel parameters and user limits on bothservers.

Prepare to run the installation program. Prepare both computers to run the InfoSphereInformation Server installation program, and back upcritical data on the computers.

Installing and configuring the metadata repository, services, andengine tiers

Because all tiers except the client tier are installed on the same server, the usercompletes all preparation tasks for the metadata repository tier, services tier, andengine tier together, then runs the InfoSphere Information Server installationprogram, and then completes postinstallation tasks for the three tiers.


Table 37. Scenario C: Metadata repository, services, and engine tier installation tasks

Task User action

Acquire and install high-availability cluster managementsoftware on both servers.

Decide to use IBM Tivoli System Automation forMultiplatforms. Download the software packages andinstall them on both servers.

Configure the network. Allocate IP addresses and verify that they are validacross the network.

Set up the service IP address. Define the service (virtual) IP address. Inform TivoliSystem Automation for Multiplatforms that the networkadapters on the nodes are appropriate and equivalent forthe service IP address.

Define and start a resource group. Define the resource group and create the automationpolicy by using relationship definitions. Create a networktiebreaker, and activate the resource group.

Set the locale for the target computer. Since globalization (NLS) support will be enabled, ensurethat the locale and encoding are set correctly on bothservers.

Set up administrator and component owner accounts. Create the following administration accounts on theshared storage device. Log in to each account to confirmthat it functions correctly:



v DB2 database instance owner

v DB2 fenced user

v Administrator account for the InfoSphere InformationServer engine.

Preinstall the database system if necessary. Decide to install DB2 when the InfoSphere InformationServer installation program is run. Decide to configurethe metadata repository database and analysis databasein the new DB2 instance when the InfoSphereInformation Server installation program is run.

Preinstall WebSphere Application Server NetworkDeployment if necessary.

Decide to install WebSphere Application Server when theInfoSphere Information Server installation program isrun.

Because WebSphere Application Server is installed in thismanner, to configure HTTPS no additional WebSphereApplication Server-specific changes must be made beforerunning the installation program.



Table 37. Scenario C: Metadata repository, services, and engine tier installation tasks (continued)

Task User action




./setup -verbose


3. Follow the prompts in the wizard.

v In the High Availability Server ClusterConfiguration page, click Server clusterconfiguration. In the Virtual host name field, enterthe virtual host name that was created when thehigh availability software was configured.


v (Optional) When the installation program promptsyou, click Use Secure Sockets Layer (SSL) forHTTP communication. In the Port field, type theHTTP dispatcher port number on which secureHTTP (HTTPS) has previously been configured.

Replicate the /etc/services entries on both servers.

Set up the resource agent scripts. Implement the scripts to start, stop, and monitor theservers. Create the application resource.

Test the high-availability configuration. Simulate active cluster node failures and network failuresand observe the results.


After reviewing the system requirements, the user completes the following tasks 5times, once on each client workstation:

Table 38. Scenario C: Client tier installation tasks

Task User action





3. On the product selection page, select InfoSphereDataStage and InfoSphere Information Analyzer.


Manually configure InfoSphere Information Servercomponents to use HTTPS.

Manually configure secure HTTP (HTTPS) for the clienttier.


Postinstallation configuration tasks

After installing all InfoSphere Information Server tiers, the user configures thesystem as described in the following table.

Table 39. Scenario C: Postinstallation configuration tasks

Task User action

Enable Secure Sockets Layer (SSL). v Enable SSL for inbound RMI/IIOP. When you installInfoSphere Information Server in an IBM WebSphereApplication Server Network Deployment 6.1 or laterenvironment, SSL for inbound RMI/IIOPcommunications is disabled by default.


Test the engine tier failover function. Simulate active server failures and network failures andobserve the results.

Configure security. v The system will use the InfoSphere Information Serverinternal user registry.

v Use the InfoSphere Information Server consoles tocreate users and groups from the registry, and toassign security roles to users and groups.

v Use the InfoSphere Information Server Web console toset up the engine tier to use the local operating systemuser registry. Use the InfoSphere Information ServerWeb console to map credentials between localoperating system user registry and the InfoSphereInformation Server internal user registry.

Ensure that IBM InfoSphere DataStage users have thecorrect settings specified for localization.

The InfoSphere Information Server engine will use thedefault locale settings that are inherited by the operatingsystem users. No action is required.


Configure the parallel processing environment. v Copy the parallel engine components to the targetcomputer.








Table 39. Scenario C: Postinstallation configuration tasks (continued)

Task User action

Configure the IBM InfoSphere QualityStage MatchDesigner.

Do the following tasks:

v Verify credentials.

v Define the Data Source Name (DSN) to the analysisdatabase and source databases.

v Import metadata into the metadata repository.

v Create a project, associate imported metadata with theproject, and configure settings.

v Set up security for the project.



New installation road map (high availability clustered topology)Use this road map to complete a new installation where the metadata repositorydatabase system and services tier (IBM WebSphere Application Server) are set upin a clustered topology. The engine tier is set up in an active-passive highavailability configuration.

Complete the following steps:1. Plan the topology.2. Prepare the database cluster.3. Prepare the IBM InfoSphere Information Server databases within the cluster.4. Prepare the WebSphere Application Server cluster.5. Run the InfoSphere Information Server installation program to install

InfoSphere Information Server software for the services tier and cause it tocommunicate with the database cluster.

6. Configure WebSphere Application Server to communicate with the databasecluster.

7. Install and configure high-availability cluster management software on theengine tier servers.

8. Install and configure the engine tier.9. Install and configure the client tier.

10. Perform postinstallation configuration tasks.

If you are setting up an IBM DB2 high-availability disaster recovery (HADR)topology, configure HADR after you install InfoSphere Information Server. See“Setting up the metadata repository database in an IBM DB2 database HADRconfiguration” on page 345.









Design the topology of your installation. “High availability configurations” on page 27

Determine your database system topology. “Determining your database topology” on page 61

Determine your cluster architecture. “IBM WebSphere Application Server NetworkDeployment clustering” on page 31

Build and test the hardware infrastructure. Metadata repository tier:

v DB2 clustered installation: “Preparing the servers, filesystem, and storage” on page 338

v DB2 HADR installation: “Preparing the servers,storage, 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 NetworkDeployment clustering” on page 31

Engine tier:

v Linux UNIX “Setting up the servers,network, and storage (System Automation forMultiplatforms example)” on page 303

v Windows “Setting up the servers, network, andstorage (MSCS example)” on page 317

Plan the volume groups and file systems on which youare installing InfoSphere Information Server . Verify thatyou have sufficient storage space in your file systems.


Linux UNIX On each computer, create thetemporary directories /tmp and /var/tmp, if they do notalready exist. The root user must have read, write, andexecute permissions to these directories. The installationprogram must be run as root.




Obtain the InfoSphere Information Server software andany applicable fix packs. Uncompress the software ontoeach tier computer.


On all tier computers, verify name resolution, and openTCP ports for InfoSphere Information Server across anyapplicable firewalls.


Linux UNIX Update the kernel parameters anduser limits on each tier computer.





Prepare each tier computer to run the InfoSphereInformation Server installation program, and back upany critical data on the computers.


2. Install and configure the tiers

For each tier, complete planning tasks and preinstallation tasks. Then install IBMInfoSphere Information Server components, and perform postinstallation tasks.

Install and configure the tiers in this order:v Metadata repository tierv Services tierv Engine tierv Client tier

2a. Metadata repository tier installation task list

To configure your metadata repository tier, follow the steps in the following tasklist.

Table 41. Installation tasks: Metadata repository tier


(Optional, for an IBM DB2 clustered topology.) Installhigh-availability (HA) software to monitor the health ofthe servers and to manage failover.

“Installing high availability software on DB2 databasesystem servers” on page 339

Create the following administration accounts on eachcomputer that will host the database system. Theaccounts on each computer must be identical. Log in toeach account to confirm that it functions properly:


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 administratoruser

– Linux UNIX DB2 database instance owner

– Linux UNIX DB2 fenced user


Install the database system, create the database cluster,and preconfigure the database by using scripts that aresupplied with the installation media.

v DB2 clustered installation: “Installing the DB2 databasesystem and creating the cluster and metadatarepository database” on page 340

v DB2 HADR installation: “Installing the DB2 databasesystem and creating the metadata repository database”on page 347

v Oracle RAC installation: “Creating the metadatarepository database and running the installationprogram within an Oracle RAC configuration” onpage 357


Note: Do not run the InfoSphere Information Server installation program at thistime. Run the installation program when you configure the services tier.

2b. Services tier installation task list

Table 42. Installation tasks: Services tier


Install WebSphere Application Server NetworkDeployment on all the computers that will host theservices tier. This installation includes the deploymentmanager system and all computers that will host amanaged node in the cluster. Also install any requiredWebSphere Application Server fix packs and patches.

“Installing IBM WebSphere Application Server NetworkDeployment for a cluster installation” on page 324

On the computer that hosts the deployment manager,create a deployment manager profile that contains thedeployment manager process. Make sure thatAdministrative Security is disabled.

“Creating a deployment manager profile” on page 325

On the computer that hosts the managed node, use theProfile Management Tool to create a custom profile. Thisprofile will contain the node agent process and themanaged server process that will be part of the cluster.

“Creating a custom profile” on page 326

Use the WebSphere Application Server administrativeconsole to create a cluster with one cluster memberdefinition.Note: Start with a minimal cluster topology that containsa single node. After the installation procedure iscomplete, expand the cluster.

“Creating a cluster and cluster members for theapplication server” on page 326

Install a front-end Web server and the Web serverplug-in module. Run the configurewebserver_name scriptto create a Web server definition in WebSphereApplication Server, and do other Web serverconfiguration.

“Installing a front-end Web server” on page 328

(Optional) To increase security, configure the WebSphereApplication Server front-end Web server to accept secureHTTP (HTTPS) calls. Do this configuration if you arepreinstalling WebSphere Application Server orconfiguring an existing installation, and you areconfiguring a separate front-end HTTP server.Note: If you install WebSphere Application Server byusing the InfoSphere Information Server installationprogram, both the HTTP and HTTPS protocols areenabled in WebSphere Application Server. Theseprotocols are also enabled if you preinstall WebSphereApplication Server but use the built-in HTTP server.


(Optional) Install backup Web servers, load balancers,firewalls, and other architectural components.

“Installing a front-end load balancer (Optional)” on page329

Make sure that you can start and stop the Web server.Then start the Web server.

For IBM HTTP Server, see publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.ihs.doc/info/ihs/ihs/tihs_startihs.html

On the computer that hosts the deployment manager,verify that you can start and stop the deploymentmanager process. Then start the process and verify that itis running.

"Administering IBM InfoSphere Information Server IBMWebSphere Application Server services" in theAdministration Guide


http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.ihs.doc/info/ihs/ihs/tihs_startihs.html




Table 42. Installation tasks: Services tier (continued)


On the computer that hosts the managed node, verifythat you can start and stop the managed node and nodeagent that you created. Then start the process and verifythat it is running. Verify that it does not have globalsecurity on.

"Administering IBM InfoSphere Information Server IBMWebSphere Application Server services" in theAdministration Guide

Run the installation program on the computer where theWebSphere Application Server deployment manager isinstalled:


./setup -verbose


3. In the installation program, accept all defaults, exceptthese items:

a. In the Tier Selection page, choose Services only.

b. In the Application Server page, choose Use anexisting WebSphere Application Serverinstallation.

c. In the WebSphere Application Server Profile page,choose the Deployment Manager profile.

d. In the WebSphere Application Server ClusterInformation page, specify the URL of thefront-end HTTP dispatcher for the WebSphereApplication Server cluster. In the HTTP Port field,type the port number of the front-end HTTPdispatcher.

(Optional) Click Use Secure Sockets Layer (SSL)for HTTP communication. In the HTTP Portfield, type the HTTP dispatcher port number onwhich secure HTTP (HTTPS) has previously beenconfigured.

e. In the Database Management System Selectionpage, choose Use existing database managementsystem installation.

f. In the Database Connection page, specify themetadata repository tier connection and databaseinformation.

4. Complete the rest of the installation steps.

“Running the installation program (clusteredinstallation)” on page 330

2c. Engine tier installation task list

To configure your engine tier, follow the steps in the following task list.

Note: If you are creating a topology with more than one server engine, repeatthese steps for each server engine.


Table 43. Installation tasks: Engine tier


Acquire and install high-availability cluster managementsoftware on both engine tier servers, and set up thecluster.

Go to the documentation for your high-availabilitycluster management software. For exampleconfigurations, see the following topics:

v Linux UNIX “Installing the high availabilitysoftware (System Automation for Multiplatformsexample)” on page 304

v Windows “Setting up the cluster (MSCS example)”on page 317

Set the service IP address. Go to the documentation for your high-availabilitycluster management software. For exampleconfigurations, see the following topics:

v Linux UNIX “Setting up the virtual IPaddress (System Automation for Multiplatformsexample)” on page 305

v Windows “Setting up the virtual IP address (MSCSexample)” on page 318

Linux UNIX Define and start a resource group. Go to the documentation for your high-availabilitycluster management software. See “Defining and startingthe resource group (System Automation forMultiplatforms example)” on page 306.

For non-English locales, make sure that the locale andencoding are set correctly. The installation program usesthe locale and encoding information of the computer todetermine whether it can provide language support.


Create an administrator account for the InfoSphereInformation Server engine. Log in to the account toactivate the password.


Install a C++ compiler for job development. “Installing a C++ compiler for job development” on page159


Table 43. Installation tasks: Engine tier (continued)




./setup -verbose


3.

4. In the installation program, accept all defaults,except:

v In the Tier Selection page, choose Engine only.

v In the High Availability Server ClusterConfiguration page, click Server clusterconfiguration. In the Virtual host name field, enterthe virtual host name that was created when theHA software was configured.


v In the IBM InfoSphere Information Server Locationpage, specify the URL of the front-end HTTPdispatcher for the WebSphere Application Servercluster. In the Port field, type the port number ofthe front-end HTTP dispatcher. Enter theInfoSphere Information Server administratoraccount name and password.

(Optional) Click Use Secure Sockets Layer (SSL)for HTTP communication. In the Port field, typethe HTTP dispatcher port number on which secureHTTP (HTTPS) has previously been configured.


For example configurations, see the following topics:

v Linux UNIX “Installing IBM InfoSphereInformation Server in the cluster (System Automationfor Multiplatforms example)” on page 309

v Windows “Installing IBM InfoSphere InformationServer in the cluster (MSCS example)” on page 318

Set up the resource agent scripts. Go to the documentation for your high-availabilitycluster management software. For exampleconfigurations, see the following topics:

v Linux UNIX “Setting up the high availabilitycontrol scripts (System Automation for Multiplatformsexample)” on page 309

v Windows “Setting up high availability control scripts(MSCS example)” on page 319

2d. Client tier installation task list


Note: If you are creating a topology with more than one client computer, repeatthese steps for each client computer.








Chapter 12, “Installing new software,” on page 167











v If the installation program did not configure HTTPSfor a tier computer during InfoSphere InformationServer installation, manually configure HTTPS for thattier computer.


Windows (Optional) Configure the cluster to run as aservice.

“Configuring a cluster to run as a service (Windows)” onpage 333

DB2 clustered and HADR installations: Configure theprimary and secondary servers.

v DB2 cluster installation: “Configuring automatic clientreroute” on page 342

v DB2 HADR installation:

– “Configuring the HADR primary server” on page348

– “Configuring the HADR standby server” on page350




Configure WebSphere Application Server to work withthe metadata repository tier cluster.

v DB2 clustered installation: “Specifying the alternatedatabase address and port for IBM WebSphereApplication Server” on page 342

v DB2 HADR installation: “Specifying the alternatedatabase address and port for IBM WebSphereApplication Server” on page 351

v Oracle RAC installation: “Connecting to an OracleRAC configuration” on page 358

(Optional) Add additional WebSphere Application Servernodes or other components to the cluster.

"Adding a new cluster member" in the IBM InfoSphereInformation Server Administration Guide

To communicate the WebSphere Application Servercluster configuration to the front-end Web server, run theWebSphere Application Server administrative console togenerate the plugin-cfg.xml file, and then manuallycopy it to each Web server. Then restart the Web server.

If you are using IBM HTTP Server, you can automaticallypropagate the file to your Web servers by using theWebSphere Application Server administrative console.

"Propagating the plugin-cfg.xml file to the front-end Webserver" in the Administration Guide

DB2 HADR installation: Start HADR. “Starting HADR” on page 353

Test the engine tier failover function. Go to the documentation for your high-availabilitycluster management software. For exampleconfigurations, see the following topics:

v Linux UNIX “Testing the configuration(System Automation for Multiplatforms example)” onpage 311

v Windows “Testing the configuration (MSCSexample)” on page 319







Optionally, also:

v ConfigureWebSphere Application Server for non-rootadministration.








1. If you installed globalization support (NLS), ensurethat InfoSphere DataStage users have the correctsettings specified for localization.

2. Configure access to ODBC data sources.

3. Windows For systems that have large numbers ofsimultaneously connected users or large numbers ofsimultaneously running jobs, tune the server engine.

Optionally, also:



v Configure the InfoSphere QualityStage MatchDesigner.






Configure InfoSphere Information Analyzer (if installed). “Configuring IBM InfoSphere Information Analyzer” onpage 256








Sample scenario D: Topology with clustered metadatarepository tier and services tier

Sample scenario D is a topology that includes IBM WebSphere Application Serverclustering and IBM DB2 clustering for high availability.

A large company uses both IBM WebSphere Application Server NetworkDeployment (ND) and DB2 for other applications. They recently purchased IBMInfoSphere Information Server. They plan to use the full suite of components forfuture data integration projects.

The company has existing WebSphere Application Server and IBM DB2installations. They are each managed within different support groups within thecompany IT department. Each group understands how to provide high availabilitysolutions for the component under their supervision.

The large number of concurrent users requires a clustered WebSphere ApplicationServer topology that permits almost no downtime. This topology also allows for


future expansion to accommodate additional capacity. The WebSphere ApplicationServer group plans to create a WebSphere Application Server cluster for InfoSphereInformation Server. The DB2 group will provide clustering of the metadatarepository database and IBM InfoSphere Information Analyzer database tominimize downtime.

The engine tier will be configured in an active-passive server cluster topology. Thecluster management software will be IBM Tivoli System Automation forMultiplatforms. To increase processing throughput, the passive node will be usedas a parallel engine node while the primary node is active.

For the servers, 64-bit Red Hat Enterprise Linux 5 Advanced Platform will be usedon an AMD CPU or processor. For the clients, existing Microsoft Windows XPworkstations will be used.

The following diagram illustrates the topology that they will build.


MetadataRepositorycomputer(active)

HA mgt sw

DB2 DBMS

Cluster

DB2DB

Services tier

SAN

HA mgt sw

Engine tier

Analysisdatabase


Clienttier

DB2DB

FIREWALL

Backup loadbalancer

Loadbalancer

Webserver 1

Webserver 2


ServerDeployment

Manager


ServerNode 2


Server Node 1

ActiveComputer

PassiveComputer


HA mgt sw

HA mgt sw

DB2 DBMS

Client workstations


Figure 47. Sample scenario D topology



To plan and build the installation topology, complete the following tasks.

Table 46. Scenario D: Planning and building the topology

Task User action


Determine your database installation strategy. The metadata repository database and InfoSphereInformation Analyzer analysis database will run in aclustered DB2 installation. The IBM InfoSphereQualityStage Match Designer database will run in aseparate, non-clustered DB2 installation.

Since the database cluster must be operational before theInfoSphere Information Server installation program runs,IBM DB2 will be preinstalled and preconfigured.


Since the application server cluster must be operationalbefore the InfoSphere Information Server installationprogram runs, WebSphere Application Server will bepreinstalled and preconfigured.

Review Secure Sockets Layer (SSL) configuration tasks. SSL will be enabled in this configuration.

Plan volume groups and file systems. Plan the volume groups and file systems on which youare installing InfoSphere Information Server. Verify thatyou have sufficient storage space in your file systems.

Obtain the installation software. Obtain the InfoSphere Information Server software andany applicable fix packs. Uncompress the software ontoeach tier computer.

Verify the network and open ports. On all tier computers, verify name resolution, and openTCP ports for InfoSphere Information Server across anyapplicable firewalls.

Modify kernel parameters and user limits. Update the kernel parameters and user limits on all tierservers.

Prepare to run the installation program. Prepare each tier computer to run the InfoSphereInformation Server installation program, and back upcritical data on the computers.

Installing and configuring the metadata repository tier

After reviewing the system requirements, take the following actions to prepare themetadata repository tier computers for the databases:


Table 47. Scenario D: Metadata repository tier preinstallation tasks

Planning task User action

Install the servers, network, and storage device. Set up two servers with identical internal storage,memory, and processing power. Designate one server as"primary" and the other as "standby". These servers willsupport the metadata repository database and analysisdatabase in a nonpartitioned topology.

Configure a high-speed network between the servers,and a separate, isolated network to carry a heartbeatsignal for the HA software.

Install a storage device and configure it so it is shared byboth nodes in the cluster.

Set up a separate server for the non-clustered DB2instance that will support the IBM InfoSphereQualityStage Match Designer database and IBMInfoSphere Information Analyzer analysis database.

Install high availability (HA) software on the DB2 clusterservers.

On the two DB2 cluster servers, configure Tivoli SystemAutomation for Multiplatforms to monitor the health ofthe servers and to manage failover:

1. Install Tivoli System Automation for Multiplatformson both servers.

2. Define the service (virtual) IP address and host name.Inform Tivoli System Automation for Multiplatformsthat the network adapters on the nodes areappropriate and equivalent for the service IP address.

3. Define the resource group. Create the automationpolicy by using relationship definitions. Create anetwork tiebreaker, and activate the resource group.

4. Create identical users and user groups on each server.

Install the database system on the cluster servers, createthe cluster, and preconfigure the metadata repositorydatabase in the cluster.

To configure the metadata repository database in thecluster, run the scripts that are supplied with theinstallation media.

Do not run the InfoSphere Information Server installationprogram because the database system is preinstalled, andthe database is created by using the scripts.

Install the database system for the IBM InfoSphereQualityStage Match Designer database.

On the dedicated server, install the DB2 database system.

Note: Do not run the InfoSphere Information Server installation program on themetadata repository tier computer.

Installing and configuring the services tier

After reviewing the system requirements, take the following actions to create aclustered topology of WebSphere Application Server for the InfoSphere InformationServer services tier:


Table 48. Scenario D: Services tier preinstallation tasks

Preinstallation task User action

Install the servers and network. Because InfoSphere Information Server must havededicated nodes within a WebSphere Application Servercluster, set up two additional servers to host the cluster.As a front end to the cluster, set up an IP sprayer withbackup servers.

Install WebSphere Application Server. Install WebSphere Application Server NetworkDeployment on all the computers that will host theservices tier. This installation includes the deploymentmanager system and all computers that will host amanaged node in the cluster. Also install any requiredWebSphere Application Server fix packs and patches.

Create a Deployment Manager profile. On the computer that hosts the deployment manager,create a deployment manager profile named Dmgr01 thatcontains the deployment manager process. Make surethat Administrative Security is disabled.

Create a custom profile. On the computer that hosts the managed node, use theProfile Management Tool to create a custom profilenamed Custom01. This profile will contain the nodeagent process and the managed server process that willbe part of the cluster.

Create a cluster and cluster members. Use the WebSphere Application Server administrativeconsole to create a cluster with one cluster memberdefinition.

For management of HTTP sessions in the clusterenvironment, HTTP session memory-to-memoryreplication will be used.

Install a front-end Web server. Install IBM HTTP Server on two separate computers.One computer serves as backup for the other. Forinformation about installing IBM HTTP Server, refer tothe IBM HTTP Server documentation.

Run the configurewebserver_name script to create a Webserver definition in WebSphere Application Server, anddo other Web server configuration.

Configure the front-end Web server for HTTPS. Enable IBM HTTP Server to accept secure HTTP (HTTPS)calls.

(Optional) Install a front-end load balancer. Install IBM Load Balancer on two separate computers.One computer serves as backup for the other. Forinformation about installing IBM Load Balancer, refer tothe IBM Load Balancer documentation.

Configure the load balancer to balance the loads on thedownstream Web servers. If you modify the Web serverconfiguration, for example, to add or remove a Webserver, reconfigure the load balancer to accommodate thechange and balance the loads on the Web servers.

Make sure that you can start and stop the Web server.Then start the Web server.







Table 48. Scenario D: Services tier preinstallation tasks (continued)


Verify the deployment manager. On the computer that hosts the deployment manager,verify that you can start and stop the deploymentmanager process. Then start the process and verify that itis running. See "Administering IBM InfoSphereInformation Server and IBM WebSphere ApplicationServer services" in the Administration Guide.

Verify the managed node and node agent. On the computer that hosts the managed node, verifythat you can start and stop the managed node and nodeagent that you created. Then start the process and verifythat it is running. Verify that it does not have globalsecurity on. See "Administering IBM InfoSphereInformation Server and IBM WebSphere ApplicationServer services" in the Administration Guide.


Use the WebSphere Application Server console to makesure that the WebSphere Application Server DeploymentManager is running, and the node agents are started onall nodes. The application server processes on the nodesmust be stopped.

Make sure that the IBM DB2 cluster is running.

On the computer that hosts the deployment manager,run the installation program as described in “Runningthe installation program for Scenario D” on page 207.

Installing and configuring the engine tier

The engine tier is to be configured in a two-server active-passive server clustertopology. To manage high availability across the cluster, Tivoli System Automationfor Multiplatforms will be used.

After reviewing the system requirements, take the following actions to configurethe engine tier:

Table 49. Scenario D: Engine tier preinstallation tasks


Configure the servers, networks, and storage device. Set up the servers with redundant connections to twoseparate high-speed networks. The heartbeat signal is totravel over a serial network.

Create an /opt/IBM directory on each server and mountthe storage device on both servers. Make sure that thedirectory is shared and has the correct permissions.


Table 49. Scenario D: Engine tier preinstallation tasks (continued)


Install high availability (HA) software. Configure Tivoli System Automation for Multiplatformsto monitor the health of the servers and to managefailover:

1. Install Tivoli System Automation for Multiplatformson both servers.

2. Define the service (virtual) IP address and host name.Inform Tivoli System Automation for Multiplatformsthat the network adapters on the nodes areappropriate and equivalent for the service IP address.

3. Define the resource group. Create the automationpolicy by using relationship definitions. Create anetwork tiebreaker, and activate the resource group.

4. Create identical users and user groups on each server.

Set the locale for the target computer. Globalization (NLS) support will be enabled. Ensure thatthe locale and encoding are set correctly on both enginetier servers.

Set up administrator and component owner accounts. Create an administrator account for the InfoSphereInformation Server engine. Log in to the account toactivate the password.



Run the installation program for the engine tier asdescribed in “Running the installation program forScenario D” on page 207.

Set up the resource agent scripts. Implement the scripts to start, stop, and monitor theservers. Create the application resource.


After reviewing the system requirements, complete the following tasks for eachclient workstation:

Table 50. Scenario D: Client tier preinstallation tasks



Run the installation program for the client tier asdescribed in “Running the installation program forScenario D” on page 207.

Manually configure InfoSphere Information Servercomponents to use HTTPS.

Manually configure secure HTTP (HTTPS) for the clienttier.

Postinstallation tasks

After installing all InfoSphere Information Server tiers, configure the system asdescribed in the following table.


Table 51. Scenario D: Postinstallation tasks

Task User action

Enable Secure Sockets Layer (SSL). v Enable SSL for inbound RMI/IIOP. When you installInfoSphere Information Server in an IBM WebSphereApplication Server Network Deployment 6.1 or laterenvironment, SSL for inbound RMI/IIOPcommunications is disabled by default.


Configure the primary and secondary servers. Configure automatic client reroute to switch between theprimary and secondary servers.

Set up WebSphere Application Server to communicatewith the DB2 cluster.

To cause WebSphere Application Server to communicatewith the DB2 cluster instead of a single node, run theWebSphere Application Server administrative console tospecify an alternate database address and port.

Add other WebSphere Application Server clustermembers.

Add additional WebSphere Application Server nodes orother components to the cluster. See "Adding a newcluster member" in the IBM InfoSphere Information ServerAdministration Guide.

Propagate the plugin.xml file if necessary. To communicate the cluster configuration to thefront-end Web server, run the WebSphere ApplicationServer administrative console to generate plugin-cfg.xmlthe file, and then manually copy it to each Web server.See "Administering WebSphere Application Serverclusters" in the IBM InfoSphere Information ServerAdministration Guide.

Test the engine tier failover function. Simulate active server failures and network failures andobserve the results.

Configure security. An external Lightweight Directory Access Protocol(LDAP) user registry will be used.

v Use the WebSphere Application Server AdministrativeConsole to configure the system to use the LDAP userregistry.

v Use LDAP administration tools to create InfoSphereDataStage users and groups within the registry.


v Install Pluggable Authentication Modules (PAM) onthe engine tier computers.

v Use the InfoSphere Information Server Web console toset up the engine tier to use the LDAP user registry.No credential mapping is required.

v Within new InfoSphere Information Serverinstallations, Secure Sockets Layer (SSL) is disabled bydefault. Reenable SSL to maximize system security.

Ensure that IBM InfoSphere DataStage users have thecorrect settings specified for localization.

The InfoSphere Information Server engine will use thedefault locale settings that are inherited by the operatingsystem users. No action is necessary.



Table 51. Scenario D: Postinstallation tasks (continued)

Task User action

Configure the parallel processing environment. v Copy the parallel engine components to the targetcomputer.







Configure IBM InfoSphere Information Analyzer. Complete the following tasks:






Configure the IBM InfoSphere QualityStage MatchDesigner.

Do the following tasks:






Configure IBM InfoSphere Business Glossary. Complete the following tasks:

v Assign security roles to glossary users.

v Configure general settings.

v Configure viewing permissions.

Configure IBM InfoSphere Metadata Workbench. Assign roles to users and administrators.

Configure IBM InfoSphere FastTrack. Create administrator and user IDs.



Adding product modules to an existing installationTo add product modules to an existing installation, use the installation program toinstall the product module components on one or more tiers.

When you first install IBM InfoSphere Information Server, you run the installationprogram on all tier computers. During the initial installation, the program installsthe product modules that you select, and also installs a framework of componentsthat all product modules use. The components reside on all the tiers.


Note: If you preinstall the database system for the metadata repository tier andconfigure the databases within the database system by using the scripts that aresupplied with the installation media, you do not run the installation program onthe metadata repository tier computers.

To install additional product modules, you run the installation program again.However, depending on the product modules that you select, you might not haveto run the installation program for all tiers. Not all product modules havecomponents on all tiers.

The following table lists product modules and indicates the tier computers onwhich you must run the installation program.

Table 52. Product modules and the tiers on which you must run the installation program

Product moduleTier computers on which to run theinstallation program

IBM InfoSphere FastTrack Services, Client

IBM InfoSphere Metadata Workbench Services, Engine

IBM InfoSphere Business Glossary Services, Client

IBM InfoSphere Business GlossaryAnywhere (requires InfoSphere BusinessGlossary). The client is installed separately.

Services

All others All tier computers

Before you add product modules to an existing installation, make sure that youhave an up-to-date backup of all computers in the installation. See the IBMInfoSphere Information Server Administration Guide.

If you acquire entitlements for additional IBM InfoSphere DataStage editions orfeature packs after initial installation, you do not use the InfoSphere InformationServer installation program to add them. Instead, enable them by using theLicensingServiceAdmin tool. Also use the tool if you are entitled to an additionaledition or trade up to a different edition. Refer to the IBM InfoSphere InformationServer Administration Guide.



Part 2. Preparing the tier computers

Before you run the IBM InfoSphere Information Server installation program,prepare each target computer for the installation.



Chapter 5. Computer preparation road maps

Follow these road maps to prepare each tier computer for IBM InfoSphereInformation Server installation.

Preparation road map for the metadata repository tier computerIf you are creating a metadata repository tier without a clustered database systeminstallation, follow these steps to configure the metadata repository tier.

Note: If you are using a clustered database system setup, instead follow theprocedures in Chapter 24, “Metadata repository tier clustering for highavailability,” on page 337.

Table 53. Metadata repository tier computer preparation checklist (non-clustered installation)

Metadata repository tier preparation step Procedure

Review the system requirements. Chapter 1, “Planning Step 1: Reviewingsystem requirements and release notes,” onpage 3

Determine the database system to install foryour metadata repository and how you areinstalling it (or whether to use an existinginstallation).

v “Determining your database topology” onpage 61

v “Determining the database installationmethod” on page 63

If installing IBM InfoSphere InformationAnalyzer, determine the database system orsystems to install for the analysis databasesand how to install them. Alternatively,decide whether to use existing installations,or the metadata repository database system.

v “Determining your database topology” onpage 61

v “Determining the database installationmethod” on page 63

v “Sizing the analysis databases” on page 65

Obtain the IBM InfoSphere InformationServer software and any applicable fixpacks. Uncompress the software onto eachtier computer.

Chapter 6, “Obtaining IBM InfoSphereInformation Server software,” on page 131

Verify the network and open ports. “Verifying the network and opening ports”on page 133

Linux UNIX Modify kernelparameters and user limits.

“Modifying kernel parameters and userlimits (Linux, UNIX)” on page 137

Set up administrator and component owneraccounts.

“Setting up administrator and owneraccounts” on page 142

If you decide to preinstall DB2 or anothersupported database system, install thedatabase system now.

Database system documentation. For theDB2 database system, see “Preinstalling theIBM DB2 database system” on page 147

If you preinstalled DB2, configure thedatabases within DB2 by using scripts.Alternatively, configure the databases whenyou run the InfoSphere Information Serverinstallation program.

If you preinstalled another database system,configure the databases by using scripts.

v “Preparing an existing DB2 databasesystem” on page 148

v “Using a database system other thanDB2” on page 152


Preparation road map for the services tier computerIf you are creating a services tier without a clustered IBM WebSphere ApplicationServer installation, follow these steps to configure the services tier.

If you are creating a WebSphere Application Server cluster, instead follow theprocedures in Chapter 23, “WebSphere Application Server clustering for highavailability and scalability,” on page 323.

Table 54. Services tier computer preparation checklist (non-clustered installation)

Services tier computer preparation step Procedure


Determine if you need to preinstallWebSphere Application Server, orpreconfigure an existing WebSphereApplication Server installation.

“Determining how to install WebSphereApplication Server” on page 66

Obtain the InfoSphere Information Serversoftware and any applicable fix packs.Uncompress the software onto each tiercomputer.






Preinstall WebSphere Application Server ifnecessary.

“Preinstalling WebSphere ApplicationServer” on page 153

Preconfigure an existing WebSphereApplication Server installation if necessary.

“Configuring an existing WebSphereApplication Server installation(non-clustered installation)” on page 154

(Optional) To increase security, configure theWebSphere Application Server front-endWeb server to accept secure HTTP (HTTPS)calls. Do this configuration if you arepreinstalling WebSphere Application Serveror configuring an existing installation, andyou are configuring a separate front-endHTTP server.Note: If you install WebSphere ApplicationServer by using the InfoSphere InformationServer installation program, both the HTTPand HTTPS protocols are enabled inWebSphere Application Server. Theseprotocols are also enabled if you preinstallWebSphere Application Server but use thebuilt-in HTTP server.

“Configuring the front-end HTTP server forHTTPS” on page 155

Preparation road map for the engine tier computersIf you are creating an engine tier without high-availability (HA) server clustering,follow these steps to configure the engine tier. If you are creating a configurationwith more than one server engine, repeat these steps for each server engine.


Not all product modules require an engine tier. IBM InfoSphere FastTrack, IBMInfoSphere Business Glossary, and IBM InfoSphere Business Glossary Anywhere donot require an engine tier.

For information about creating a highly available engine tier, see Chapter 22,“Creating a two-server active-passive high availability configuration,” on page 299.

Table 55. Engine tier computer preparation checklist (non-HA)

Engine tier computer preparation step Procedure




Verify the network and open ports. “Verifying the network and opening ports”on page 133



Linux UNIX If you are notinstalling in English, or if you are enablingglobalization (NLS) support, confirm thatthe current code page is supported. If it isnot supported, change to a supported codepage.

“Setting the locale for the target computer”on page 157



Install C++ compiler for job development. “Installing a C++ compiler for jobdevelopment” on page 159

Preparation road map for the client tier computersFollow these steps to prepare each client tier workstation computer.

Table 56. Client tier computer preparation checklist

Client tier computer preparation step Procedure




Chapter 5. Computer preparation road maps 129


Chapter 6. Obtaining IBM InfoSphere Information Serversoftware

Obtain InfoSphere Information Server software and applicable fix packs.

About this task

The installation media for installing InfoSphere Information Server is availableeither as physical CDs or as downloadable installation image files from PassportAdvantage®. Fix packs are available as downloadable installation image files fromFix Central.

Procedure1. If you obtained InfoSphere Information Server in the form of physical CDs,

check that you have all of the installation disks.2. If you do not have CDs, download the installation image files from Passport

Advantage. See http://www.ibm.com/support/docview.wss?uid=swg21443006to determine the image files that are appropriate for your operating systemsand configurations.

3. Download any applicable fix packs from Fix Central. Seepublib.boulder.ibm.com/infocenter/iisinfsv/v8r5/topic/com.ibm.swg.im.iis.trblsh.sup.doc/topics/ts_fixcentral.html.

4. If you downloaded installation image files, uncompress the installation imagefiles onto each tier computer.

Windows To avoid corrupting the files in the image, do not use the MicrosoftWindows uncompression utility to uncompress the files. Use another standarduncompression utility.



http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r5/topic/com.ibm.swg.im.iis.trblsh.sup.doc/topics/ts_fixcentral.html

http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r5/topic/com.ibm.swg.im.iis.trblsh.sup.doc/topics/ts_fixcentral.html


Chapter 7. Preparation steps for all tier computers

Complete the following preparation steps for each computer in your installation.

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

About this task

For performance reasons, do not install InfoSphere Information Server in a widearea 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 latencyincreases, 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 othercomputers 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 IPaddress.

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 hostnames 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 installedOn the computer where the engine tier is installedOn the computer where the client tier is installed

Engine

On the computer where the engine tier is installedOn the computer where the services tier is installedOn the computer where the client tier is installed

d. Ensure that the localhost host name and the computer host name are notboth 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 thelocal computer. This example shows how these entries are configured in the/etc/hosts file:127.0.0.1 localhost.localdomain localhostxx.xx.xx.xx longhostname shorthostname


localdomainThe domain name

xx.xx.xx.xxThe unique IP address for the computer

longhostname shorthostnameThe long and short names for the computer

3. Ensure that you install the metadata repository and engine tiers in the samenetwork segment.

4. Open and make TCP ports available through firewalls for InfoSphereInformation Server and the application server. The following tables identify theTCP ports that must be available for each tier:v Port numbers for the metadata repository tierv Port numbers for the services tierv 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 metadatarepository (default database)

50000 Services

IBM DB2 database for the analysisdatabase (default database)

50000 Services, engine, client

Oracle database for the metadatarepository (if used)

1521 Services

Oracle database for the analysisdatabase (if used)


Microsoft SQL Server database forthe metadata repository (if used)

1433 Services

Microsoft SQL Server database forthe analysis database (if used)


Table 58. Port numbers for the services tier

ComponentDefault port numbers forstand-alone configuration

Default port numbers forcluster configuration Tiers that use the port

DHTML reports server 16581 (DHTML reports serverfunctionality is notsupported in clusteredconfigurations.)

Client

InfoSphere InformationServer Web-based clients

WC_defaulthost (9080) Firewall between the clientand dispatcher (if any):usually 80. This value variesdepending on theconfiguration of thefront-end dispatcher.

Firewall between dispatcherand cluster members (ifany): WC_defaulthost of allcluster members (forexample, 9080, 9081, and soon).

Services, engine, client


Table 58. Port numbers for the services tier (continued)



InfoSphere InformationServer Web-based clients(HTTPS)

WC_defaulthost_secure(9443)

Firewall between the clientand dispatcher (if any):usually 443. This valuevaries depending on theconfiguration of thefront-end dispatcher.

Firewall between thedispatcher and clustermembers (if any):WC_defaulthost_secure ofall cluster members (forexample, 9443, 9444, and soon)

Client

If HTTPS is configured, theservices tier and engine tieralso use this port.

IBM WebSphereApplication Serveradministrative console(redirects to HTTPS)

WC_adminhost (9060) WC_adminhost (9060) Client

IBM WebSphereApplication Serveradministrative console(HTTPS)

WC_adminhost_secure(9043)

WC_adminhost_secure(9043)

Client

InfoSphere InformationServer services(RMI/IIOP)

BOOTSTRAP_ADDRESS(2809)

ORB_LISTENER_ADDRESS(9100)

SAS_SSL_SERVERAUTH_LISTENER_ADDRESS(9401)

CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS(9402)

CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS(9403)

BOOTSTRAP_ADDRESS ofall cluster members (9810,9811, and so on)

ORB_LISTENER_ADDRESSof all node agents (9100,9101, and so on)

SAS_SSL_SERVERAUTH_LISTENER_ADDRESS,CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS,CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESSof all cluster members:(9410, 9411, 9412),(9411, 9414, 9415),and so on

Services, engine, client

Chapter 7. Preparation steps for all tier computers 135

Table 58. Port numbers for the services tier (continued)



IBM InfoSphereInformation ServicesDirector services with JMSbindings

SIB_ENDPOINT_ADDRESS(7276)

SIB_ENDPOINT_SECURE_ADDRESS (7286)

SIB_MQ_ENDPOINT_ADDRESS (5558)

SIB_MQ_ENDPOINT_SECURE_ADDRESS (5578)

SIB_ENDPOINT_ADDRESSof all cluster members(7277, 7278, and so on)

SIB_ENDPOINT_SECURE_ADDRESS of all clustermembers(7287, 7288, and so on)

SIB_MQ_ENDPOINT_ADDRESS of all clustermembers(5559, 5560, and so on)

SIB_MQ_ENDPOINT_SECURE_ADDRESS of allcluster members(5579, 5580, and so on)

Client

Important: IBM WebSphere Application Server Network Deployment does notsupport deployment of firewalls between components within a cell (forexample, between the dmgr and nodes).

Table 59. Port numbers for the engine tier


InfoSphere Information Server ASB agent 31531, and a random portnumber greater than 1024

Instead of using a random portnumber, you can fix this to aspecific port by specifyingagent.objectport=# in theC:\IBM\InformationServer\ASBNode\conf\agent.propertiesfile after you complete theinstallation. After designating aspecific port, restart the loggingagent and the ASB agent so thatthe change takes effect.

Services

InfoSphere Information Server logging agent 31533 Engine

IBM InfoSphere DataStage and QualityStageAdministrator services

DSRPC (31538) Engine, client

Parallel job monitors 13400 (port 1) and 13401 (port 2)

Access to port 1 is required onlyfrom the conductor node. Accessto port 2 is required from theconductor node and the nodewhere the InfoSphere DataStageand QualityStage Administratorengine is installed, if that node isdifferent from the conductornode.

Engine


Table 59. Port numbers for the engine tier (continued)


Parallel engine APT_PM_STARTUP_PORT(multiple ports, uses a portnumber of 10240 or greater)

Engine

Parallel engine remote process startup(rsh/ssh, multiple nodes only)

22514 Engine

Parallel engine (multiple nodes only) APT_PLAYER_CONNECTION_PORT (multiple ports, uses aport number of 11000 orgreater)

Engine

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

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

The kernel parameter and user limit requirements are minimum requirements forIBM InfoSphere Information Server. The optimal value for each parameter might behigher depending on the topology of your installation and the operational dataload. Additional kernel parameter and user limit changes might be required. Whenmore than one value is provided for your configuration, use the largest minimumvalue.

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

Minimum kernel parameters

The following sections describe the minimum kernel parameter requirements foreach tier:

Metadata repository tier“Minimum kernel parameters for DB2 Database for Linux, UNIX, andWindows (metadata repository tier)” on page 138

Engine and services tiers

v AIX “Minimum AIX kernel parameters (engine and services tiers)”on page 139

v HP�UX “Minimum HP-UX kernel parameters (engine and servicestiers)” on page 139

v Linux “Minimum Linux kernel parameters (engine and servicestiers)” on page 140

v Solaris “Minimum Solaris kernel parameters (engine and servicestiers)” on page 140

You can find additional system tuning information in the IBM WebSphereApplication Server documentation:


v WebSphere Application Server, Version 6.1 Information Center: Preparingthe 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: Preparingthe 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 toIBM DB2 database installations. Before you install IBM DB2 as part of InfoSphereInformation Server, ensure that your computer meets the following minimumkernel parameter requirements for DB2:

v AIX For IBM AIX®, the default kernel parameter values are sufficient.

v HP�UX Solaris For HP-UX or Solaris, run the db2osconf utility to suggestappropriate kernel parameter values for your system. If you have not yetinstalled the DB2 server, you can obtain the db2osconf utility from theInfoSphere 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 describedin the following table:

Table 60. Minimum Linux kernel parameters and user limits for the metadata repository tieron 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 (whichevervalue is greater)

SHMMAX 32-bit: 26843545664-bit: 1073741824

Set this value to be equal to the amount of physicalmemory on your computer.

SHMMNI 4096

When the DB2 kernel requirements are different from the InfoSphere InformationServer kernel parameter requirements, use the largest minimum value. If you use adifferent database system for the metadata repository, consult the productdocumentation for that database system to find information about kernelparameter requirements.


http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.base.doc/info/aes/ae/tins_prepare.html



http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.installation.base.doc/info/aes/ae/tins_prepare.html



For more information about the kernel parameter requirements and user limits forIBM DB2, see the following topics in the IBM DB2 Database for Linux, UNIX, andWindows 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 HP�UX 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 forthe 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)


Table 62. Minimum HP-UX kernel parameters and user limits (engine and services tiers)


MAXFILES 8000

MSGMAP 32768

MSGMAX 65535

MSGMNB 65535 (single profile)131070 (more than one profile)

MSGMNI 50


http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.qb.server.doc/doc/r0052441.html

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.qb.server.doc/doc/r0052441.html

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.qb.server.doc/doc/t0006477.html









http://publib.boulder.ibm.com/infocenter/db2luw/v9/




Table 62. Minimum HP-UX kernel parameters and user limits (engine and servicestiers) (continued)


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)


Table 63. Minimum Linux kernel parameters and user limits (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 thefollowing example, the ⇒ character represents the continuation of the defaultparameter line.


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 forthe 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)


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


Table 65. Minimum Solaris 9 kernel parameters and user limits (engine tier) (continued)


rlim_fd_cur Greater than 8193

rlim_fd_max Greater than 8193

Setting up administrator and owner accountsBefore installing IBM InfoSphere Information Server, create the requiredadministrator and owner accounts. When you run the InfoSphere InformationServer installation program, specify the names and passwords of these accounts forthe program.

Before you begin

Make sure that you are familiar with the naming restrictions described in “Namingrestrictions for user IDs and passwords” on page 145.

About this task

Creating administrator and owner accounts before you install InfoSphereInformation Server ensures that operating system policies, such as requiring apassword change at the first login, do not interfere with the installation programuse of the accounts.

Create the accounts as local operating system accounts. The InfoSphere InformationServer installation program cannot use the accounts if they are lightweightdirectory access protocol (LDAP) or Active Directory accounts. After theinstallation is complete, you can change the InfoSphere Information Server setup touse LDAP.

When you create the accounts, record the name and password for each user. Thenspecify each name and password when the installation program prompts you forthat information.

Procedure1. On the operating systems where you install InfoSphere Information Server,

make sure that the user who installs InfoSphere Information Server can log inusing these accounts:

v Linux UNIX The root user account.

v Windows A user account in the local Administrators group. This accountmust be one of the following types:– A local account that is directly assigned to the Windows local

Administrators group.– A domain account that is directly assigned to the Windows local

Administrators group.The user must log in using one of these accounts to install InfoSphereInformation Server.

2. Linux UNIX On the operating systems where you install each enginetier, create the following additional accounts and record the passwords.


Note: If your installation does not include an engine tier, you can skip thisstep.

Table 66. Accounts that you create for an engine tier (Linux, UNIX only)

Account description Default user name Primary group Secondary group Notes

Linux UNIX

Administrator for theInfoSphere InformationServer engine

dsadm dstage You customize thisgroup to apply to yoursecurity model.

This user performsadministrative tasks,such as adding newprojects and definingtheir properties. To runjobs, create a separateuser with the developerrole.

This account must be anaccount on the localoperating system.During installation time,you cannot specify aLightweight DirectoryAccess Protocol (LDAP)account as the engineadministrator account.

3. On the operating system where you install the metadata repository, create thefollowing additional accounts and record the passwords.

Table 67. Accounts that you create on the metadata repository tier


DB2 administrationserver user v Linux

UNIX dasusr1

v Windows db2admin

v Linux

UNIX dasadm1

v Windows db2admnsand Administrators

None DB2 database only,operating systemaccount. This accountmust haveread/write/executepermission to thefollowing directories:

v The home directoryfor the DB2administration serveruser (by default, thepath is/home/dasusr1)

v /tmp

v /var/tmp

Linux UNIX

DB2 instance owner

db2inst1 db2iadm1 dasadm1 DB2 database only,operating systemaccount. This accountmust haveread/write/executepermission to thefollowing directories:

v The home directoryfor the DB2 instanceowner (by default, thepath is/home/db2inst1)

v /tmp

v /var/tmp

Linux UNIX

DB2 fenced user

db2fenc1 db2fadm1 None DB2 database only,operating systemaccount


Table 67. Accounts that you create on the metadata repository tier (continued)


Owner of the metadatarepository

xmetaImportant: Do notspecify db2admin ordb2inst1 as themetadata repository username.

xmeta None DB2 database only,operating systemaccount. When you usethe DB2 database for therepository, the DB2database uses theauthentication for theoperating system forconnection requests.

IBM InfoSphereInformation Analyzer:owner of the analysisdatabases

iauserImportant: Do notspecify db2admin ordb2inst1 as theInfoSphere InformationAnalyzer database username.

iauser None DB2 database only,operating systemaccount. DB2 databaseuses the authenticationfor the operating system.

Linux UNIX The InfoSphere Information Server installation programmust have root access. Root must have write permissions to the followingdirectories:v /tmp

v /var

v /var/tmp

v /usr/local/bin

4. Verify permissions for all users including root. If any directories are mountedfrom network file systems such as AFS, permissions might not be adequate toperform a successful installation.

5. Determine the names and passwords to use for the following administratoraccounts:

Table 68. 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 systemaccounts. Instead, specify the account names and passwords when theInfoSphere Information Server installation program prompts for thisinformation. The installation program stores this account information in theinternal InfoSphere Information Server user registry. The program does notcreate these accounts as local accounts. After installation, you can modify theInfoSphere Information Server setup so it uses a local operating system userregistry or lightweight directory access protocol (LDAP) user registry.

6. Log in to each account to confirm that it functions correctly. Some operatingsystems are set up to force a password change during the first login. Therefore,a manual login is required to activate the accounts appropriately.

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


/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.

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.

Naming restrictions for user IDs and passwordsSome restrictions apply to the names that you choose for user IDs and passwords.

All user IDs and passwordsThe 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, such as spaces, tabs, and line continuationcharacters, is removed by the installation program. Any existing user IDsand passwords cannot have leading or trailing white space characters aspart of their definitions.

Internal user registry user IDsOnly alphanumeric characters and the following characters are permitted:

_ (underscore)- (hyphen)\ (backslash)= (equal sign)


. (period)

IBM WebSphere Application Server administrator passwordThe following characters are not permitted:v Space charactersv ^ (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. Must not be the first character.)

Linux and UNIX user names and passwords cannot start with a numericdigit.

v On UNIX, the DB2 database requires these user accounts: DB2 instanceowner, DB2 fenced user, and DB2 administrator. These account namescannot begin with these characters:

SQL

SYS

IBM

v In addition, these account names cannot use these words:USERS

ADMINS

GUESTS

PUBLIC

LOCAL

Any SQL reserved word in the SQL reference for the database systemv Names cannot include accented characters.v UNIX and Linux users, groups, and instance names must be in

lowercase letters.

Character length limits

v AIX operating system user IDs: 8v WebSphere Application Server IDs: 60v DB2 user IDs and passwords:

– UNIX and Linux: 8– Microsoft Windows: 30


Chapter 8. Additional preparation steps for the metadatarepository tier computer

To prepare a computer for the metadata repository tier installation, complete thesetasks in addition to the tasks that are common to all tier computers.

Preinstalling the IBM DB2 database systemPreinstall the DB2 database system if necessary before you run the IBM InfoSphereInformation Server installation program.

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.7 with

InfoSphere Information Serverv To build a DB2 database cluster or high availability disaster recovery (HADR)

architecture for high availability

Procedure1. Obtain a DB2 database system installation package from IBM.

The IBM InfoSphere Information Server installation package includesinstallation packages for IBM DB2 Enterprise Server Edition, Version 9.7 forLinux, UNIX, and Windows. To preinstall Version 9.7 before you run theInfoSphere Information Server installation program, you can run the DB2database system installation program that is included in the InfoSphereInformation Server installation media.On the installation media, the DB2 database system installation packages are inthe following directories:

v Linux UNIX installable_image_directory/payloads/Shared/DB2/payload

v Windows installable_image_directory\payloads\Shared\DB2\payload

2. Install the DB2 database system as described in the DB2 database systemdocumentation:v IBM DB2 Database, Version 9.5 for Linux, UNIX, and Windows:

publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jspv IBM DB2 Database, Version 9.7 for Linux, UNIX, and Windows:

publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp3. Optional: If you are using DB2 diagnostics, 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 eventmonitors and snapshots. These monitoring tools do not work under the defaultsize setting. See publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.admin.config.doc/doc/r0000306.html.db2 update dbm cfg using MON_HEAP_SZ 192 immediate

Restart DB2 for changes to take effect.


http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp


http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.admin.config.doc/doc/r0000306.html


What to do next

Configure the databases within DB2. Use the InfoSphere Information Serverinstallation program, or use the database creation scripts.

Preparing an existing DB2 database systemInstead of installing the IBM DB2 database system, you can use an existinginstallation of DB2.

Preparing an existing DB2 database system by using theinstallation program

You can use the IBM InfoSphere Information Server to configure an existing IBMDB2 database system installation for InfoSphere Information Server.

Before you begin

To configure the DB2 database system by using the InfoSphere Information Server,the database system must satisfy the following requirements:v It must be a supported version. See the system requirements at

www.ibm.com/support/docview.wss?rs=14&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.v For the analysis database for IBM InfoSphere Information Analyzer, the

computer must also be accessible to computers that host the client tier.v You must run the installation program locally on the computer where the DB2

instance is installed.If you cannot run the program locally on the target computer, use theinstallation scripts instead. See “Preparing an existing DB2 database system byusing scripts” on page 149.

v If installing into a DB2 cluster, set up the cluster and configure the databaseswithin the cluster. Then use the installation scripts to install the databases. SeeChapter 24, “Metadata repository tier clustering for high availability,” on page337.

v Make sure that the database does not contain any user objects.v The existing installation cannot be set up as a partitioned database environment.

This type of environment and the fast communications manager (FCM) are notsupported for use with InfoSphere Information Server.

v DB2 Fault Monitoring components must be enabled. Make sure that the path tothe fault monitor (db2fmcd) is included in the /etc/inittab file. The db2fmcdcommand must point to the actual executable location. For example:fmc:234:respawn:/ul/IBM/db2/V9/bin/db2fmcd #DB2 Monitor Coordinator

Attention: The InfoSphere Information Server installation program runs thefollowing commands when it configures the DB2 database system. These changesaffect all the databases in the DB2 instance:db2set DB2_INLIST_TO_NLJN=YESdb2set DB2_USE_ALTERNATE_PAGE_CLEANING=ONdb2set DB2_REDUCED_OPTIMIZATION=YESdb2 update dbm cfg using MON_HEAP_SZ 192 immediate

Before you proceed, do all tasks that are listed in Chapter 7, “Preparation steps forall tier computers,” on page 133.



Procedure1. Make sure that the DB2 installation instance is defined in the services file

a. Open the services file. The services file is located in one of the followingdirectories:

v Linux UNIX /etc

v Windows %SystemRoot%\system32\drivers\etc\services

Note: %SystemRoot% is the installation directory of the Windowsoperating system. For example: c:\windows.

b. Verify that the following line appears in the file. If the line does not appearin the file, add the line, and save the file:db2c_instanceName port/tcp

instanceName is the DB2 instance name. port is the port number of the DB2instance.

2. Run the InfoSphere Information Server installation program on the targetcomputer. See “Starting the installation program in graphical mode” on page180.v In the Tier selection page, click Metadata repository.v In the Database Management System Selection page, click Use an existing

DB2 instance on this computer. Select the path to the database instance inthe menu. In the Instance port number menu, select the port number of theDB2 instance.

v Linux UNIX In the IBM DB2 Instance User page, specify the name ofthe DB2 instance owner account that you created. See “Setting upadministrator and owner accounts” on page 142.

v Linux UNIX In the DB2 Fenced User Information page, specify thename of the DB2 fenced user account that you created.

v In the DB2 Administrator User Information page, specify the name of theDB2 administrator server user account that you created.

v In the Metadata Repository Configuration page, specify the metadatarepository database information and database owner account information.

v If you are installing InfoSphere Information Analyzer, specify the analysisdatabase and owner information in the IBM InfoSphere Information AnalyzerRepository Configuration page.

3. If you use DB2 diagnostics, run the following command to set the DB2Database Monitor Heap size to 192 or greater:



Preparing an existing DB2 database system by using scriptsYou can scripts that are shipped with IBM InfoSphere Information Server toconfigure an existing IBM DB2 database system installation for InfoSphereInformation Server.

Chapter 8. Additional preparation steps for the metadata repository tier computer 149



Before you begin

The DB2 database system must satisfy the following requirements:v It must be a supported version. See the system requirements at



computer must also be accessible to computers that host the client tier.v Make sure that the database does not contain any user objects.v The existing installation cannot be set up as a partitioned database environment.



About this task

You can run a script to create a metadata repository or IBM InfoSphere InformationAnalyzer analysis database. For a DB2 installation, use the scripts in the followingsituations:v You are configuring a DB2 cluster for the databases. See Chapter 24, “Metadata

repository tier clustering for high availability,” on page 337.v You cannot run the installation program locally on the target computer.v You do not want to use the InfoSphere Information Server installation program

to configure the database.

Procedure1. If installing into a DB2 cluster, set up the cluster and configure the databases

within the cluster before running the scripts. See Chapter 24, “Metadatarepository tier clustering for high availability,” on page 337.

2. Create the databases by using the database creation scripts. Refer to theappropriate readme file in the DatabaseSupport directory of the InfoSphereInformation Server installation media for more details on how to create thedatabases by using the scripts.

3. If you use DB2 diagnostics, run the following command to set the DB2Database Monitor Heap size to 192 or greater:



Using an IBM DB2 for z/OS database system for the databasesYou can use a DB2 for z/OS database as the metadata repository. You run aprovided script to create the database before you install IBM InfoSphereInformation Server.





Before you begin

The DB2 database system must satisfy the following requirements:v It must be a supported version. See the system requirements at



computer must also be accessible to computers that host the client tier.v Make sure that the database does not contain any user objects.v The existing installation cannot be set up as a partitioned database environment.



Procedure1. Set the DB2 DSNZPARM parameter IDTHTOIN (in the DSN6FAC macro) to

600 seconds before installing the services tier. After installation is complete, youcan restore this parameter to its original value. This is a system-wide parameterand requires a database administrator to set it.

Note: IBM InfoSphere Information Services Director deployment requires thatthe DB2 IDTHTOIN parameter be set to a value longer than the time requiredto deploy an application.

2. Bind the DB2 Universal Driver JDBC packages before installing InfoSphereInformation Server. Do this bind action from the DB2 command promptinterface that is provided with the Linux operating system that is running onSystem z. For details on installing the z/OS Application Connectivity to DB2for z/OS, see IBM DB2 Version 9.x for z/OS Application Programming Guide andReference for Java.

3. If you choose to use the same DB2 for z/OS subsystem as the metadatarepository for more than one InfoSphere Information Server installation, youmust use a different DB2 user ID for each. In DB2 for z/OS, the tablenamespace is defined only by the DB2 user ID, which allows for namecollisions on multiple databases. Consequently, the DB2 user ID that is used forthe InfoSphere Information Server metadata repository must not be used forany other database. The installation program checks prerequisites to determineif the database is empty. If you ignore the check failure when the database isnot empty, tables under the user ID might be overwritten and data might bedestroyed.

Note: It is not necessary to use different user IDs for analysis databases. Tablenames are created with generated tags and are very unlikely to collide evenwhen multiple analysis databases are created under the same DB2 user ID. TheInfoSphere Information Server installation program does not validate that otheranalysis databases exist for the DB2 user ID.

4. Refer to the appropriate readme file in the DatabaseSupport directory of theInfoSphere Information Server installation media for more details on how tocreate a DB2 database for the metadata repository.

Chapter 8. Additional preparation steps for the metadata repository tier computer 151


Using a database system other than DB2To prepare a database system other than IBM DB2 for IBM InfoSphere InformationServer, use scripts to create the metadata repository and analysis databases.

Before you begin

The database system must satisfy the following requirements:v It must be a supported database system and version. See the system

requirements at www.ibm.com/support/docview.wss?rs=14&uid=swg27016382.v It must be located on a computer that is accessible by the computers where the


computer must also be accessible to computers that host the client tier.v (Oracle database system) The Advanced Security option is not supported. If this

option is turned on, turn it off before installing IBM InfoSphere InformationServer.


Procedure

Refer to the appropriate readme file in the DatabaseSupport directory of theInfoSphere Information Server installation media for more details on how to createthe databases by using the database creation scripts.



Chapter 9. Additional preparation steps for the services tiercomputer

To prepare a computer for the services tier installation, complete these tasks inaddition to the tasks that are common to all tier computers.

Preinstalling WebSphere Application ServerIBM InfoSphere Information Server supports IBM WebSphere Application ServerNetwork Deployment, Versions 6.1 and 7.0. You must install one of these versions.

About this task

This task describes the installation of IBM WebSphere Application Server NetworkDeployment in a non-cluster (stand-alone) installation.

For a cluster installation, see “Installing IBM WebSphere Application ServerNetwork Deployment for a cluster installation” on page 324.

Procedure1. Install IBM WebSphere Application Server Network Deployment on the

InfoSphere Information Server services tier.Run the IBM WebSphere Application Server installation program to install IBMWebSphere Application Server Network Deployment. See the WebSphereApplication Server documentation for more information:v For IBM WebSphere Application Server Network Deployment, Version 6.1:

publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/welc6topinstalling.html

v For IBM WebSphere Application Server Network Deployment, Version 7.0:publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.installation.nd.doc/info/ae/ae/welc6topinstalling.html

The IBM InfoSphere Information Server installation package includesinstallation packages for IBM WebSphere Application Server NetworkDeployment, Version 7.0. To preinstall WebSphere Application Server, Version7.0 before you run the InfoSphere Information Server installation program, youcan run the WebSphere Application Server installation program that is includedin the InfoSphere Information Server installation media.Within the installation media, the WebSphere Application Server installationpackages 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. Install any required fix pack and iFixes. To find the supported fix pack level,Java SDK fix number, and iFixes that are required for your installed version ofIBM WebSphere Application Server Network Deployment, refer to theInfoSphere Information Server system requirements page: www.ibm.com/support/docview.wss?rs=14&uid=swg27016382.


http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/welc6topinstalling.html



http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.installation.nd.doc/info/ae/ae/welc6topinstalling.html




Note: If you use the installation packages for IBM WebSphere ApplicationServer Network Deployment, Version 7.0 that is included in the installationpackage, you do not need to install additional fix packs or iFixes.

Configuring an existing WebSphere Application Server installation(non-clustered installation)

Instead of installing a new IBM WebSphere Application Server instance for IBMInfoSphere Information Server, you can configure an existing installation to usewith InfoSphere Information Server.

Before you begin

The WebSphere Application Server installation must satisfy the followingrequirements:v It must be on the same computer where you install the services tier.v It must be a supported version. See the system requirements at

www.ibm.com/support/docview.wss?rs=14&uid=swg27016382.

InfoSphere Information Server does not support WebSphere Application ServerExtended Deployment (XD) or the WebSphere Application Server base version.

About this task

The InfoSphere Information Server installation program enables security as part ofits configuration.

Procedure

Configure your WebSphere Application Server installation before you installInfoSphere Information Server.1. At a command prompt, enter one of the following commands to verify that you

have a supported version of WebSphere Application Server and the Java SDK.

v Linux UNIX

/opt/IBM/WebSphere/AppServer64/bin/versionInfo.sh/opt/IBM/WebSphere/AppServer64/java/bin/java -fullversion

v Windows

C:\IBM\WebSphere\AppServer\bin\versionInfo.batC:\IBM\WebSphere\AppServer\bin\java -fullversion

Compare the values that are returned by these commands to the versionnumbers in the system requirements to determine if you have a supportedversion. If you do not have a supported version, do not attempt to configure itfor use with InfoSphere Information Server.

2. Create a new application server profile with security disabled. For informationabout creating a profile, see the WebSphere Application Server documentation:v Version 6.1: publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/

com.ibm.websphere.nd.doc/info/ae/ae/tpro_profiles.htmlv Version 7.0: publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/

com.ibm.websphere.nd.doc/info/ae/ae/tpro_profiles.html



http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.nd.doc/info/ae/ae/tpro_profiles.html




Configuring the front-end HTTP server for HTTPSIf you preinstall IBM WebSphere Application Server and install a separatefront-end HTTP server before you run the IBM InfoSphere Information Serverinstallation program, to enable WebSphere Application Server to accept HTTPScalls you must manually configure the HTTP server.

About this task

Note: If you install WebSphere Application Server by using the InfoSphereInformation Server installation program, both the HTTP and HTTPS protocols areenabled in WebSphere Application Server. These protocols are also enabled if youpreinstall WebSphere Application Server but use the built-in HTTP server.

HTTPS configuration is optional. If you do not configure HTTPS, HTTP is usedinstead. HTTPS adds greater security to your system, but also requires moreadministrative work and can be error-prone. There is also a performance impact.Therefore, carefully consider the benefits and drawbacks before enabling HTTPS.You might not need HTTPS if you have a strong firewall in place.

Procedure

Follow the instructions in the WebSphere Application Server documentation:v Version 6.1: publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/

com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tsec_securecomm.htmlv Version 7.0: publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/

com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tsec_securecomm.html

What to do next

When you run the installation program, click the Use Secure Sockets Layer (SSL)for HTTP communication check box if it appears within the installation programwizard. After the installation, follow the steps in “Manually configuring InfoSphereInformation Server components to use HTTPS” on page 234 to configure HTTPS onany tier computers on which the installation program did not configure thisprotocol.

Chapter 9. Additional preparation steps for the services tier computer 155

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tsec_securecomm.html





Chapter 10. Additional preparation steps for the engine tiercomputers

To prepare a computer for an engine tier installation, complete these tasks inaddition to the tasks that are common to all tier computers.

Setting the locale for the target computerThe installation program uses the locale and encoding information of the targetcomputer to determine whether it can provide language support. For languagesother than English, you must ensure that the locale and encoding are set correctly.

About this task

When you install IBM InfoSphere Information Server with globalization (NLS)support enabled, the installation program chooses the globalization configurationthat is the most suitable for the locale and encoding of the target computer. Toensure that server jobs run and compile correctly, make sure that the targetcomputer uses a supported locale and encoding. For UNIX installations, you canset the encoding to UTF-8 to support a wide variety of languages.

If you do not set the target computer to use a supported locale and encoding, theinstallation program configures InfoSphere Information Server for the Englishlanguage, including globalization support.

Procedure

Windows For information about setting the locale in Windows, see the Microsoftdocumentation.

Linux UNIX To set the locale in Linux or UNIX:1. Log in to the computer.2. Enter the following command to determine the current locale:

locale

3. 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 localenames or alias locale names. A full locale name contains the encoding name inthe last component. For example, the full locale name ja_JP.utf8 contains theencoding name, utf8, in the last component. An alias locale name does notinclude the encoding name. To determine the encoding, you can run thefollowing command:LANG=alias_name locale charmap

where alias_name is the alias name. For example, the following commandreturns utf8 on a system where the locale ja_JP uses the utf8 encoding:LANG=ja_JP locale charmap

4. If the target computer does not use a supported locale and encoding, changethe LANG value to a combination that is available on your computer and that


is supported by IBM InfoSphere Information Server. To change the locale andencoding, run the export command with the following format:export LANG={locale.charmap}export LC_ALL={locale.charmap}

For example, the following commands change the locale to ja_JP and theencoding to UTF-8:export LANG=ja_JP.utf8export LC_ALL=ja_JP.utf8

Character encodings supported by IBM InfoSphereInformation Server

Verify that the operating system of the target computer uses a supported characterencoding.

The following table lists the languages and encodings that are supported byInfoSphere Information Server on various operating systems. To ensure that serverjobs run and compile correctly, the operating system of the target computer mustuse an encoding that is supported by the globalization configuration that is usedduring installation.

Table 69. Supported encodings for InfoSphere Information Server

Language

Globalizationconfigurationname

SupportedWindowsencodings

SupportedLinuxencodings

SupportedHP-UXencodings

SupportedAIX encodings

SupportedUNIXencodings

Chinese DS-CHINESE-SIMPLIFIED

MS936 EUC-CN,GB18030,GB2312, GBK,IBMEUCCN

GB2312,XEUCCN

EUC-CN,GB18030,GB2312, GBK,IBMEUCCN

EUC-CN,GB18030,GB2312, GBK,IBMEUCCN

Chinese DS-CHINESE-SIMPLIFIED-UTF8

UTF-8 UTF-8 UTF-8 UTF-8 UTF-8

Chinese,Traditional

DS-CHINESE-TRADITIONAL

MS950 BIG5 BIG5 BIG5 BIG5

Chinese,Traditional

DS-CHINESE-TRADITIONAL-UTF8


English DS-ENGLISH MS1252 ISO8859-1 ISO8859-1 ISO8859-1 ISO8859-1

English DS-ENGLISH-UTF8


French DS-FRENCH MS1252 ISO8859-1 ISO8859-1 ISO8859-1 ISO8859-1

French DS-FRENCH-UTF8


German DS-GERMAN MS1252 ISO8859-1 ISO8859-1 ISO8859-1 ISO8859-1

German DS-GERMAN-UTF8


Italian DS-ITALIAN MS1252 ISO8859-1 ISO8859-1 ISO8859-1 ISO8859-1

Italian DS-ITALIAN-UTF8


Japanese DS-JAPANESE MS932,MS31J


Table 69. Supported encodings for InfoSphere Information Server (continued)

Language

Globalizationconfigurationname

SupportedWindowsencodings

SupportedLinuxencodings

SupportedHP-UXencodings

SupportedAIX encodings

SupportedUNIXencodings

Japanese DS-JAPANESE-EUC

Notsupported

EUC-JP, EUC,IBM33722,IBM33722C,IBMEUCJP,UJIS,XEUCJPOPEN

Not supported Not supported Not supported

Japanese DS-JAPANESE-SJIS

IBM932,IBM943,IBM943C, PCK,SHIFT_JIS, SJIS




Japanese DS-JAPANESE-UTF8


Korean DS-KOREAN MS949 EUC, EUC-KR EUC-KR KSC5601 KSC5601

Korean DS-KOREAN-UTF8


Portuguese DS-PORTUGUESE-BRAZILIAN

MS1252 ISO8859-1 ISO8859-1 ISO8859-1 ISO8859-1

Portuguese DS-PORTUGUESE-BRAZILIAN-UTF8


Spanish DS-SPANISH MS1252 ISO8859-1 ISO8859-1 ISO8859-1 ISO8859-1

Spanish DS-SPANISH-UTF8


Thai DS-THAI PC874 TIS620 TIS620 TIS620 TIS620

Turkish DS-TURKISH MS1254 ISO8859-9 ISO8859-9 ISO8859-9 ISO8859-9

For more information, see the IBM InfoSphere DataStage and QualityStageGlobalization Guide.

Installing a C++ compiler for job developmentThe computer where you will install the IBM InfoSphere Information Server enginemust have a C++ compiler. The job compilation process uses it to compile paralleljobs with transformer stages, buildop components, and some lookup stages. Tofunction correctly, the transform feature of the parallel canvas requires thecompiler. The parallel canvas requires that the compiler and SDK be installed intheir default locations.

For some compilers, each developer must have a license at the time that thedeveloper compiles the job with the Designer client. The maximum number ofsimultaneous processes that compile jobs determines the number of licenses.

Install only one compiler on each engine for development environments. Forproduction environments, you do not need a C++ compiler, but some operatingsystems require additional C++ runtime libraries.

Chapter 10. Additional preparation steps for the engine tier computers 159

For the list of supported C++ compilers, see the system requirements for youroperating system: www.ibm.com/support/docview.wss?rs=14&uid=swg27016382.

When InfoSphere Information Server is installed, the compiler settings are preset.However, for some compilers you might need to alter the settings after installation.



Chapter 11. Preparing for the IBM InfoSphere QualityStageMatch Designer database

The IBM InfoSphere QualityStage Match Designer is a component of InfoSphereQualityStage that is used to design and test match specifications. Matchspecifications consist of match passes that identify duplicate entities in one or morefiles.

If you intend to develop match specifications, use a new or existing database thatis dedicated to storing the results of match test passes. Do not use the metadatarepository or the analysis database to store these results.

The Match Designer database can be hosted by the following database systems:v IBM DB2 database system, which you can install during the IBM InfoSphere

Information Server installationv Oracle database systemv Microsoft SQL Server database system

Database requirements

The InfoSphere Information Server installation program does not create the MatchDesigner results database. You create the database before or after the installation,as long as the database is configured and accessible when you use the MatchDesigner. You can create the database on a computer where the client or engine tieris installed or on any computer that is accessible to both of these tiers. You mustconfigure the database to receive the type of data that is processed in the MatchDesigner. For example, you must configure the database to receive double-bytedata if the Match Designer processes Asian data.

The following table lists the supported databases and describes the configurationrequirements:

Table 70. Configuration requirements by database

Database Configuration requirements

All databases Configure as an empty database. The MatchDesigner creates the table structure that itrequires when it stores the match passresults in the database.

IBM DB2 database system Configure the following settings:

v Set Default Buffer Pool and Table SpacePage Size to 32K.

v Set Code Set to UTF-8.


Table 70. Configuration requirements by database (continued)

Database Configuration requirements

Oracle database system Configure the following settings:

v Set Character Set for the data beingprocessed. For example, useWE8ISO8859P1 for English and forWestern European languages.

v Set National Character Set to AL32UTF8.

Note: If you use the IBM Wire Protocoldriver, select the Enable N-CHAR Supportoption.

Microsoft SQL Server database system No special settings are required.

Database space requirements

After you create the database, use automatic storage management to allocatedatabase space as needed.

To estimate initial space requirements and plan for the appropriate hardware, youneed to make some assumptions about the type and volume of matching that youwill do. Consider the following factors:v Estimated number of match specificationsv Average number of match passes per match specificationv Average number of input data records per match specificationv Average number of bytes per input data recordv Average number of input frequency records per match specification

When you calculate the number of bytes in a Match Designer input record, assumethat VarChar columns contain maximum width values. Also, keep in mind thatmost Match Designer input records will be preprocessed through an InfoSphereQualityStage Standardization Stage. This stage will add 500 bytes to a sourcerecord or 1000 bytes if the source record is double-byte.

When calculating frequency record volume, consider whether the data values forthe source columns that participate in your matches typically have high or lowrates of duplication. For data that is highly unique, your frequency record countwill be similar to your data record count. For data that has a high rate ofduplication, your frequency record count will be significantly less than your datarecord count.

Review the factors described in Table 2. Then use the factors in the followingformula to estimate how many megabytes of space the Match Designer resultsdatabase is likely to require.

(number of match specifications x (match size + (match size x 10%) + frequencysize) x replication factor) / 1,000,000


Table 71. Space requirement factors and calculations

Factor Description Calculation

Match specification count Match specifications defineand test criteria for matchingdata.

Approximate number ofmatch specifications youexpect to retain in yourdatabase

Match pass count Match passes define thecolumn-level matchingcriteria applied during asingle pass through matchspecification input.

Average number of matchpasses per matchspecification (used in theMatch Size calculation)

Data record count Data records define thecontent and format of matchspecification input.

Average number of inputdata records per matchspecification (used in theMatch Size calculation)

Data record length Data records define thecontent and format of matchspecification input.

When calculating data recordlength, assume sizingscenarios that require themost space.

Average number of bytes permatch specification inputdata record (used in theMatch Size calculation)

Match size (in bytes) Match size aggregates thematch pass and data recordcount and length factors intothe estimated spacerequirements for the datacomponent of a single matchspecification.

(Match pass count) x (datarecord count) x (data recordlength)

Frequency record count Frequency records indicatehow often a particular valueappears in a particularcolumn.

For frequency record count,consider high or low rates ofduplication for the datavalues in source columns.

Average number offrequency records per matchspecification

Frequency size (in bytes) Frequency size estimates thespace requirement for thefrequency component of asingle match specification.

(Frequency record count permatch) x 360

Chapter 11. Preparing for the IBM InfoSphere QualityStage Match Designer database 163

Table 71. Space requirement factors and calculations (continued)

Factor Description Calculation

Replication factor Replication factors accountfor significant differences inspace requirements ofdifferent match types:

v Unduplicate matches takeinput from one source,then group and match thedata.

v One-to-one referencematches compare a recordon the data source to arecord on the referencesource.

v Many-to-one referencematches can match anyreference source recordwith many data sourcerecords.

Select the replication factorfor the match type youexpect to run most often:

v For unduplicate matches,use a factor of 1

v For one-to-one referencematches, use a factor of 2

v For many-to-one referencematches, use a factor of 5


Part 3. Installing IBM InfoSphere Information Server software

You can create an installation of IBM InfoSphere Information Server or update anexisting installation with a patch or fix pack.



Chapter 12. Installing new software

Use the IBM InfoSphere Information Server installation program to create aninstallation. You can also use the installation program to add product modules orsoftware tiers to an existing installation.

After you have planned your installation and prepared your computers, run theInfoSphere Information Server installation program to install InfoSphereInformation Server product modules and components.

After you install the suite, you can use the installation program to add productmodules to the installation. For example, you can add IBM InfoSphere FastTrack toan existing Version 8.5 installation that includes IBM InfoSphere DataStage or otherproduct modules.

Do not use the InfoSphere Information Server installation program to addInfoSphere DataStage editions or feature packs after initial installation. Instead,enable them by using the LicensingServiceAdmin tool. Refer to the IBM InfoSphereInformation Server Administration Guide.

You can also use the installation program to add a software tier to a computer thatis already hosting a Version 8.5 tier. For example, if a target computer hosts aservices tier instance, you can use the program to add an engine tier instance tothat computer.

The program can also install IBM DB2 and IBM WebSphere Application ServerNetwork Deployment (ND) if your installation requires stand-alone configurationsof these components. Alternatively, the installation program can set up InfoSphereInformation Server to use preinstalled instances of these components, or othersupported database systems and application servers.

The installation program can run in either of two modes:

Graphical modeIn this mode, the installation program runs within a standard Webbrowser, either locally on the target computer or remotely. The installationprogram presents wizard pages for you to select options. When you haveselected your options, the program saves them to a response file on thetarget computer. Then the program performs a prerequisites check. If thecheck succeeds, the program installs the software.

Silent modeIn this mode, the installation program does not present a user interface.Instead, it reads settings from a response file. It performs a prerequisitescheck. If the check succeeds, the program installs the software. As itperforms the installation, it can save the report to a text file or displayresults on the console.

Creating an installationYou can create an installation of IBM InfoSphere Information Server productmodules and components by running the installation program.


Before you begin1. Plan your installation as described in Part 1, “Planning for the installation of

IBM InfoSphere Information Server,” on page 1.2. Prepare your computers as described in Part 2, “Preparing the tier computers,”

on page 125.3. Perform the additional preparation steps that are described in “Preparing to

run the installation program” on page 177.4. Make sure that your browser is configured correctly. See “Configuring your

browser” on page 179.

About this task

Run the installation program on each tier computer, in the following order:1. Metadata repository. Run the installation program for this tier unless you have

preinstalled a database system and configured the databases within it asdescribed in “Using a database system other than DB2” on page 152.

2. Services.3. Engine. Run the installation program for this tier unless you are only installing

product modules that do not require an engine tier. IBM InfoSphere FastTrack,IBM InfoSphere Business Glossary, and IBM InfoSphere Business GlossaryAnywhere do not require an engine tier.

The client tier installation can take place at any point in the sequence.

You only need to run the installation program one time on each computer even ifthe computer is to host more than one tier. The installation program installs thetier components in the correct order on the computer.

Note: If you create operating system user accounts from the installation program,the installation program immediately adds them on the computer. If you exit theinstallation program before you complete the installation, delete the user accountsmanually from the computer.

For client tier installations, if you want to include multiple versions of the clientson the same computer, install the Version 8.5 client tier before you install theearlier version clients on the computer.

Procedure

Run the installation program on the computer as described in “Graphical mode”on page 180. The installation program:v Prompts you to accept the license agreement.v Runs a short prerequisites check on the target computer.v Prompts you for the installation location. Use the directories that you

determined during the installation preparation phase. See “Planning volumegroups and file systems” on page 67.

v Prompts you for the installation type. Select New installation.v Prompts you for the tier or tiers to install on the target computer.v If you chose Engine in the Tier Selection page but did not choose Services,

prompts you for the IBM InfoSphere Information Server location. If your servicestier is set up in a clustered IBM WebSphere Application Server implementation,specify the host name and port number of the front-end HTTP dispatcher.


Otherwise, specify the host name of the services tier computer and the portnumber for WebSphere Application Server (typically 9080).Select Use Secure Sockets Layer (SSL) for HTTP communication if the HTTPserver is configured to allow HTTPS traffic only, or you want to configureInfoSphere Information Server to use an HTTPS-only connection. If you selectthis option, provide a port number that is configured for HTTPS.

Note: Select this option only if the HTTP port has been disabled in yourWebSphere Application Server installation. If you do not select this option, youcan still set up the client components to use HTTPS. Most installations do notuse this option.Also enter the InfoSphere Information Server administrator user name andpassword. Use the information that you determined during the installationpreparation phase. See “Setting up administrator and owner accounts” on page142.

v Prompts you for the list of product modules to install. Select the same set ofproduct modules for each computer.

v If you chose Services in the Tier Selection page, and if you are installing IBMInfoSphere DataStage, prompts you to choose InfoSphere DataStage editions andoptional features to install.The following table lists the InfoSphere DataStage editions and optional featuresthat the InfoSphere Information Server installation program can install. The tablealso lists the features that are included with each item.

Table 72. 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 BalancedOptimization

v InfoSphere DataStage balancedoptimization features

v Linux UNIX

If you chose Services, Metadata repository, or Engine in the Tier Selection page,asks you if this install is a two-server active-passive high availabilityconfiguration. If yes, it prompts you to enter the preconfigured floating hostname to share between the servers. See “Active-passive topology” on page 28.

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, or to configure anexisting application server instance. See “Determining how to installWebSphere Application Server” on page 66.

– If you choose to install WebSphere Application Server:- Prompts you for the application server installation location.

Chapter 12. Installing new software 169

- If Customize WebSphere Application Server profile ports is selected,allows you to define custom port assignments for WebSphere ApplicationServer within the profile.

- Prompts you for the application server administrator user name andpassword. Use the information that you determined during the installationpreparation phase. See “Setting up administrator and owner accounts” onpage 142.

– If you choose to configure an existing application server instance:- Prompts you to specify the application server instance to use.- Prompts you to specify an application server profile to use.

You must have at least one profile available for installation. The profile youselected for installation must not have security settings on.If the installation program detects that the type of the selected profile is“dmgr”, it installs InfoSphere Information Server on a WebSphereApplication Server cluster. In this case, your cluster must have beenproperly configured so that you can restart all node agents and nodesproperly. It is highly recommended that you start with a small cluster thathas only one WebSphere Application Server deployment manager node andone WebSphere Application Server node for installation

- If the application server profile is a WebSphere Application Serverdeployment manager, the installation program prompts the user to providean HTTP server host name and port number.

- If the selected profile is not a deployment manager profile, prompts you tospecify whether or not to use Secure Sockets Layer (SSL) for HTTPcommunications. Select this option if the HTTP server is configured toallow HTTPS traffic only, or you want to configure InfoSphere InformationServer to use an HTTPS-only connection. If you select this option, providea port number that is configured for HTTPS.

- Prompts you for the application server administrator user name andpassword.

v If you chose Services or Engine in the Tier Selection page, prompts you for theInfoSphere Information Server administrator user name and password (if theinformation was not collected earlier). Use the information that you determinedduring the installation preparation phase. See “Setting up administrator andowner accounts” on page 142.

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. See“Determining your database topology” on page 61.If you chose Services in the Tier Selection page, you can alternately connectto a DB2 installation on a remote computer, or another database system. Youmust have created the database within the database system before runningthe installation program. See “Preparing an existing DB2 database system” onpage 148 and “Using a database system other than DB2” on page 152.If you choose to install the DB2 database system:- Prompts you for the DB2 database system installation directory. If you are

installing the DB2 database system, the DB2 database system is installed inthis directory. If you are configuring an existing DB2 instance, specify thelocation of the existing DB2 database system installation and the portnumber for connecting to the instance.

- Linux UNIX


Prompts you for the DB2 instance owner. The instance owner controls allthe DB2 processes and owns all the file systems and devices that are usedby the databases within the DB2 instance. Click Existing user and specifythe DB2 instance owner name that you created before starting theinstallation program. (See “Setting up administrator and owner accounts”on page 142.) Also specify a port number for the new instance.If you did not create the DB2 instance owner account before starting theinstallation program, instead click Create a user as an instance owner andspecify the user information. The installation program creates the account.This option is not available if the user registry is Lightweight DirectoryAccess Protocol (LDAP) or NIS.

- Linux UNIX

Prompts you for the DB2 fenced user. Any fenced user-defined functions(UDFs) and stored procedures run under this user and group. ClickExisting user and specify the DB2 fenced user name that you createdbefore starting the installation program.If you did not create the fenced user account before starting the installationprogram, instead click Create a new user as a fenced user and specify theuser information. The installation program creates the account. This optionis not available if the user registry is LDAP or NIS.

- Prompts you for the DB2 administrator user. This user is the DB2Administration Server (DAS) user. Click Existing user and specify the username that you created before starting the installation program. See “Settingup administrator and owner accounts” on page 142.If you did not create the DB2 administrator user account before starting theinstallation program, instead click Create the user as administrator userand specify the user information. The installation program creates theaccount. This option is not available if the user registry is LDAP or NIS.

- Prompts you for the metadata repository owner information and databasename. Specify the user name that you created before starting theinstallation program. See “Setting up administrator and owner accounts”on page 142.The installation program creates the account. This option is not available ifthe user registry is LDAP or NIS.

If you choose to configure an existing database (local or remote, DB2 or otherdatabase system), you are prompted for the database type, host computername and port, and metadata repository owner information.

v If you chose Services in the Tier Selection page, prompts you for the metadatarepository database owner account and database information. Specify theaccount information that you created before starting the installation program.Also specify the database name, instance name, and location.

z/OS Also specify the database collection ID and tablespace name.If you did not create the metadata repository database owner account beforestarting the installation program, the installation program creates the account.

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. The ASB agent facilitatescommunication between tiers. The logging agent logs events to the metadatarepository database.Specify ports that are not used by other services. The default port settingswork in most configurations.


– If you are installing InfoSphere DataStage, IBM InfoSphere QualityStage, orIBM InfoSphere Information Analyzer:

- Linux UNIX

Prompts you for the InfoSphere DataStage administrator. Click Existinguser and specify the InfoSphere DataStage administrator account name thatyou created before starting the installation program.If you did not create the user account before starting the installationprogram, instead click Create a user as the IBM InfoSphere DataStageadministrator and specify the user information. The installation programcreates the account.

- Prompts you for the TCP/IP ports for the IBM InfoSphere DataStage andQualityStage job monitor to use. The job monitor provides snapshots of jobperformance. You access the job monitor through the IBM InfoSphereDataStage Director.Specify two ports. The job monitor uses one port to request job informationand the second port to report job information. Specify ports that are notused by other services. The default port settings work in mostconfigurations.

- Linux UNIX

Prompts you for InfoSphere Information Server engine instance taginformation. Specify a tag if an installed instance of the InfoSphereInformation Server engine exists on the target computer, and you want toinstall another engine instance on the same computer. See “Multipleinstances of IBM InfoSphere Information Server” on page 22.

- Prompts you to choose whether to install globalization support. If youwant this installation to handle data in a non-English language, installlocalization support.Some server jobs might run more slowly after you install globalization. Theperformance of parallel jobs is not affected.You cannot change this option after installation.The code page that is currently configured on the target computer must besupported by InfoSphere Information Server. If the code page is notsupported, change to a supported code page and restart the installationprogram. See “Setting the locale for the target computer” on page 157.

- Prompts you to choose whether to install the IBM WebSphere MQ Plug-in.Select this option if you have existing jobs that depend on the plug-in. Fornew jobs, you can use the IBM WebSphere MQ Connector, whichsupersedes the IBM WebSphere MQ Plug-in.

- Linux UNIX

Prompts you to choose whether to enable a legacy SAS configuration. Ifyou have existing jobs that use SAS, enable this configuration and select theversion of SAS that you want to configure. Otherwise, you can restructurethe jobs to use the Version 8.5 connector stages.

- Prompts you to specify InfoSphere DataStage projects to create. You mustcreate at least one project during installation. The installation wizarddefaults to creating a project called “dstage1”.

v If you chose Services in the Tier Selection page and are installing IBMInfoSphere Information Analyzer, prompts you for the analysis database owneraccount and database information. Specify the account information that youcreated before starting the installation program. Also specify the database name,instance name, and location.


The installation program creates the analysis database within DB2. If you didnot create the analysis database owner account before starting the installationprogram, the installation program creates the account.

v (All tier installations) Saves a response file that contains the information that youspecified in the installation wizard.

v (All tier installations) Runs a longer prerequisites check on the target computer.v (All tier installations) Prompts you whether to begin the installation process. If

you start the process, the installation program installs the product modulecomponents on the target computer.

What to do next

When the installation is successful for all computers, configure the software asdescribed in Part 4, “Configuring the software after installation,” on page 229.

You can run the IBM Support Assistant Lite for InfoSphere Information Server toolto verify the installation. Refer to “Installation verification and troubleshooting” onpage 197 for more information.

Adding product modules to an installationYou can add product modules to an existing IBM InfoSphere Information Server,Version 8.5 installation by running the installation program.


IBM InfoSphere Information Server,” on page 1.2. Prepare your target computers as described in Part 2, “Preparing the tier

computers,” on page 125.3. Do the preparation steps that are described in “Preparing to run the installation

program” on page 177.4. Make sure that your browser is configured correctly. See “Configuring your


Do not use the IBM InfoSphere Information Server installation program to addIBM InfoSphere DataStage editions or feature packs after initial installation.Instead, enable them by using the LicensingServiceAdmin tool. Refer to the IBMInfoSphere Information Server Administration Guide.

About this task

Depending on the product modules that you select, you might not have to run theinstallation program for all tiers. Not all product modules have components on alltiers. You only need to run the installation program on the tier computers thatcontain components for the product modules. You can skip tier computers that donot contain components for the product modules.

The following table lists product modules and indicates the tier computers onwhich you must run the installation program:





Table 73. Product modules and the tiers on which you must run the installationprogram (continued)





Services


The installation program only installs the appropriate software for the tiers on acomputer. You can run the installation program on all of the computers in yourconfiguration, and select the products to be installed each time. The installationprogram determines automatically which tiers exist on each computer and addsthe appropriate components.

Run the program on the computers in the following order:1. Metadata repository, if the product modules you are installing require changes

to this tier.If you preinstalled the database system for the metadata repository tier andconfigured the databases within the database system by using the scripts thatare supplied with the installation media, you do not run the installationprogram on the metadata repository tier computers.

2. Services. All product module additions require changes to the services tier.3. Engine, if needed. Refer to the table to determine whether you need to run the

installation program on the engine tier.If the product modules you are installing require an engine tier installation, andthe engine tier is not present, first install the engine tier as described in theprocedure.

4. Client, 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.

For example, to install IBM InfoSphere Information Analyzer, first run theinstallation program on the metadata repository tier computer. Then run it on theservices tier computer. Lastly, run the program on the engine tier. You can run theinstallation program on the client tier computers at any point in the sequence.

You only need to run the installation program one time on each computer even ifthe computer hosts more than one tier. The installation program installs the tiercomponents in the correct order on the computer.

Notes about specific product module addition tasks:v InfoSphere DataStage and IBM InfoSphere QualityStage share many components.

For this reason, if you add one of these product modules to a system on whichthe other product module is installed, the installation process runs faster.

v Many of these components are also shared by IBM InfoSphere InformationAnalyzer. The installation process for this product module is faster if InfoSphereDataStage or InfoSphere QualityStage is already installed.


Procedure1. Make sure you have an up-to-date backup of your entire InfoSphere

Information Server installation. See the IBM InfoSphere Information ServerAdministration Guide.

2. Consult the table above to determine what software tiers must be present inyour installation to install the product module. If a required tier is not present,install and configure the tier. See “Adding an additional software tier to acomputer.” For example, if you installed only IBM InfoSphere FastTrack, yourinstallation does not have an engine tier. To add InfoSphere DataStage, firstcreate an engine tier.

3. Run the installation program on the computers as described in “Graphicalmode” on page 180. The installation program:v Prompts you for the installation location. Select the InfoSphere Information

Server installation directory.v Detects the existing installation, and prompts you to choose whether to add

additional products or tiers.v Select Add products.v Prompts you for the product modules to install. Select the product modules

that you want to install. Select the same set of product modules for each tiercomputer.

v Prompts you for information that is specific to the product modules that youhave selected.

v Saves a response file that contains the information that you specified in theinstallation program.

v Runs a prerequisites check on the target computer.v Prompts you whether to begin the installation process. If you start the

process, the installation program installs the product module components onthe target computer. The components that the installation program installsare appropriate for the tiers that the computer hosts.

4. Repeat the process for each target computer.

What to do next

Configure the newly installed product modules as described in Part 4,“Configuring the software after installation,” on page 229.

If you disabled scheduled tasks or deployed applications before running theinstallation program, restart the tasks and reenable the applications.


Adding an additional software tier to a computerYou can add a software tier to a computer that already hosts one or more tiers, byrunning the installation program.


IBM InfoSphere Information Server,” on page 1.


2. Prepare your target computer as described in Part 2, “Preparing the tiercomputers,” on page 125.

3. Do the preparation steps that are described in “Preparing to run the installationprogram” on page 177.

4. Make sure that your browser is configured correctly. See “Configuring yourbrowser” on page 179.

About this task

To add an additional software tier to a computer that already hosts one or moretiers, run the installation program on the target computer.

You only need to run the installation program one time on each computer even ifyou are adding more than one tier. The installation program installs the tiers in thecorrect order on the computer.

For client tier installations, if you want to include multiple versions of the clientson the same computer, install the Version 8.5 client tier before you install theearlier version clients on the computer.

Procedure1. Make sure you have an up-to-date backup of your entire IBM InfoSphere

Information Server installation. See the IBM InfoSphere Information ServerAdministration Guide.

2. Run the installation program on the computer as described in “Graphicalmode” on page 180. The installation program:v Prompts you for the installation location. Select the InfoSphere Information

Server installation directory.If you are installing a client tier on a computer where an engine tier isinstalled, the client tier and engine tier must share the same base directory(for example, C:\IBM\InformationServer).

v Detects the existing installation, and prompts you to choose whether to addadditional products or tiers.

v Select Add tiers.v Prompts you for the tier or tiers to install on the target computer. Tiers that

are already installed are disabled in the window.v Prompts you for information that is specific to the tiers that you have

selected to install.v Saves a response file that contains the information that you specified in the

installation wizard.v Runs a prerequisites check on the target computer.v Prompts you whether to begin the installation process. If you start the

process, the software installs the tier on the target computer.

What to do next

Configure the software as described in Part 4, “Configuring the software afterinstallation,” on page 229.

If you disabled scheduled tasks or deployed applications before running theinstallation program, restart the tasks and reenable the applications.



Starting the installation programYou can start the IBM InfoSphere Information Server installation program ingraphical mode or silent mode.

Preparing to run the installation programBefore you run the installation program to create an installation or add productmodules or tiers, make sure that the computers are ready for installation. Also backup critical data.

Before you begin1. Review the system requirements and release notes as described in Chapter 1,

“Planning Step 1: Reviewing system requirements and release notes,” on page3.

2. Plan your installation as described in Part 1, “Planning for the installation ofIBM InfoSphere Information Server,” on page 1.

3. Prepare your target computers as described in Part 2, “Preparing the tiercomputers,” on page 125.

Procedure

Follow this procedure for each target computer:1. If you plan to run the installation program in graphical mode, make sure that

the browser is configured correctly. See “Configuring your browser” on page179.

2. Back up all critical data that is on the target computers. If you are addinganother IBM InfoSphere Information Server instance to a computer thatalready hosts an instance, back up the existing InfoSphere Information Servercomponents and critical data. See the IBM InfoSphere Information ServerAdministration Guide. Also, back up the following items:

Linux UNIX

Back up /etc/services, /etc/inittab, /etc/passwd, and /etc/group.

Windows

Back up the Microsoft Windows registry and the C:\Windows\System32\drivers\etc directory.

3. If you removed a previous installation of InfoSphere Information Server onthe computer, reboot the computer before continuing.

4. The installation program writes required temporary files to a location definedby the environment variable %temp% (Windows) or TMP (Linux, UNIX). Youcan redirect the temporary files to a different temporary directory. Ifredirection is required, do the following steps before you run the installationprogram:a. At the root of the installation package directory, copy the file

.jvm_args_debug to .jvm_args:

v Linux UNIX cp .jvm_args_debug .jvm_args

v Windows copy .jvm_args_debug .jvm_args

b. Edit .jvm_args:


1) Remove the contents of the file.2) Add the following line:

-Djava.io.tmpdir=installation_program_tempdir

3) Save the file.

After installation is finished, do not delete the installation log files that are inthe temporary directory. Preserve these files for troubleshooting andverification purposes.

5. Linux IBM WebSphere Application Server is not compatible with SecurityEnhanced Linux (SELinux). Disable SELinux or set it to permissive modebefore installing InfoSphere Information Server. For more information abouthow to disable SELinux, see the Linux documentation.

6. Linux UNIX The Linux Pluggable Authentication Modules (PAM)must be installed on the target computer. For details on supported versions,go to the system requirements at www.ibm.com/support/docview.wss?rs=14&uid=swg27016382.

7. (Oracle database system) The Advanced Security option is not supported. Ifthis option is turned on, turn it off before installing InfoSphere InformationServer.

8. Windows The installation program requires the Windows Script Engine tooperate. To test your Windows Script Engine installation, see “"There is noscript engine for file extension '.js'" message appears during installation” onpage 400.

9. Windows For a client tier or engine tier installation, if MKS Toolkit is installedon the computer, uninstall it and reboot the computer before you run theInfoSphere Information Server installation program.

10. Windows If you are installing Metabrokers and bridges, remove any existinginstallations of Metabrokers and bridges from the target computer before yourun the InfoSphere Information Server installation program. Also install thecorrect Microsoft XML Core Services (MSXML) Service Pack. For moreinformation about these and other software requirements for thesecomponents, see www.ibm.com/support/docview.wss?rs=14&uid=swg27018060

11. In a non-English environment, the installation program uses the system localesetting. To determine if your locale is supported, see “Character encodingssupported by IBM InfoSphere Information Server” on page 158. If the systemlocale setting is not supported, the product modules are configured to useEnglish and globalization support is enabled.If necessary, set the locale for the computer. For information about setting thelocale:

v Windows See your Microsoft documentation.

v Linux UNIX See “Setting the locale for the target computer” on page157.

12. If you plan to use an existing database on a different computer as yourmetadata repository, ensure that the computer where you install the servicestier has network connectivity.

13. To ensure uninterrupted connectivity to the installation media, copy thecontents of the installation media to a local file system or optical drive. Runthe installation program from this location.






14. Disable all scheduled jobs, scheduled tasks, scheduled reports, and enabledIBM InfoSphere Information Services Director applications before updating anexisting installation with a patch or fix pack.

15. Disable firewall software and antivirus software before starting theinstallation.

16. Windows When you run the installation program in graphical mode, amessage might be displayed in the browser that reads "The publisher cannotbe verified..." You can safely ignore the message and continue the installation.This message does not indicate a security risk when it is displayed duringInfoSphere Information Server installation.

17. Windows Make sure that the following directories are in your system path,and exist on the target computer:v %SystemRoot%\

v %SystemRoot%\system32

v %SystemRoot%\system32\wbem

18. For an installation that involves WebSphere Application Server clustering:v All management processes including the node agents must be started before

the installation. Also, sufficient file descriptor resources must be allocated tothe processes by using the ulimit command. See “Running the installationprogram (clustered installation)” on page 330.

v Verify that you can start and stop the cluster, and restart node agents. Seethe IBM InfoSphere Information Server Administration Guide.

v Verify that you can stop and start the Web server.v For optimal results, install into a cluster that has one Deployment Manager

and one WebSphere Application Server node. Add additional nodes asbusiness needs dictate post-installation.

19. If the WebSphere Application Server processes or node agents are currentlyrunning under a non-root user, log in as the non-root user and stop theprocesses. Then log in as root, change the ownership of the WebSphereApplication Server installation directory and profile directory to be root. Thenstart WebSphere Application Server as root.

20. Ensure that the system PATH does not include paths to Java executables.Remove any paths to Java executables.

Configuring your browserMake sure that the browser is configured so that the installation program runs ingraphical mode.

Locate your browser type in the following sections, and configure it so that theinstallation program runs correctly.

All browsersv Verify that you have a supported browser. For details, go to the system

requirements at www.ibm.com/support/docview.wss?rs=14&uid=swg27016382.v Make sure that JavaScript is enabled.

Microsoft Internet Explorer

Make sure that the security zone for the computer allows the installation programto run:1. From Microsoft Internet Explorer, in the Tools menu, select Internet Options.



2. Click the Security tab.3. Click the Trusted Sites icon.4. Click Sites.5. In the Add this Website to the zone field, type http://hostname where

hostname is the host name of the computer on which the install program willrun.

6. Click Add.7. Click OK.8. Click OK.

Mozilla Firefox

Make sure that images load automatically and that JavaScript is enabled:1. In the Tools menu, click Options. The Options window displays.2. Click Content.3. Enable Load images automatically.4. Enable Enable JavaScript.5. Click OK.

Graphical modeIn graphical mode, the installation program displays the user interface to astandard Web browser.

To run the installation program in graphical mode, you can use a Web browserlocally on the target computer. Alternatively, you can use a browser on any systemthat has network access to the computer where the program is running.

When you first start the installation program, it presents a non-graphical interface.The program starts a self-contained Web server on the computer. You can then starta Web browser on the computer or on a remote computer and access the graphicalinterface. On Microsoft Windows computers, the installation program automaticallylaunches the default Web browser on the local computer to display the graphicalinterface.

After you enter your settings in the wizard pages, the program stores your settingsin a response file. If you run the installation program again, you can load yoursettings from this file into the program instead of entering them again.

Starting the installation program in graphical modeThe installation program provides a graphical interface that leads you step-by-stepthrough the process of installing IBM InfoSphere Information Server.




program” on page 177.4. Make sure that your browser is configured correctly. See “Configuring your



About this task

The installation program displays a wizard that prompts you for parameters, usernames, passwords, and other data. While you are using the wizard:v If you create new user accounts from the wizard, the installation program

immediately creates them on the computer. If you exit the wizard before youcomplete the installation, delete the user accounts manually from the computer.

v If you close your browser while the wizard is running, you can continue thesame session by opening the browser again and reconnecting to the session.

v If your browser displays a "server busy" message, select the Continue option.You can also close the browser and then reconnect to same session.

v Windows You might see a security warning or notification when any of thefollowing programs are run during installation: setup.exe, db2setup.exe,install.exe, java.exe. When a security notification opens, click Run or Yes toallow the program to run and continue with the installation.

v The wizard times out if there is no activity within two hours.

Procedure1. Log in to the computer.

v Linux UNIX Log in as the root user.

v Windows Log in to the target computer as a local administrator or as alocal or domain user who is directly assigned to the local Administratorsgroup.

2. Open a command prompt window.

v Linux UNIX Open a command prompt or shell window.Open the window on the target computer, or use a graphical desktopsharing system. Keep the shell window open during the entire installationprocess. If you use telnet or ssh, make sure that the session does not shutdown or timeout for the duration of the installation.

v Windows Microsoft Windows 2008, Microsoft Windows 7, MicrosoftWindows Vista: Start an administrator session by using either of thefollowing methods:– Run the following command:

runas /user:Administrator cmd.exe

– Open an elevated command window. To do so, click the Start menu andtype cmd in the Start Search box. Press Ctrl-Shift-Enter. Click Continue toaccept the prompt asking for your permission to continue.

3. In the newly created session, run the following command to clear any Javaoptions that might be set:

v Linux UNIX bash, sh:export IBM_JAVA_OPTIONS=

csh, tcsh:unsetenv IBM_JAVA_OPTIONS

v Windows

set IBM_JAVA_OPTIONS=

4. Linux UNIX Make these additional settings to help ensure that theinstallation is successful:v Set the file creation mask to 022:


umask 022

v Ensure that you have enough file descriptor resources allocated for theinstallation. Set the file descriptor limit to 10240, a higher value, orunlimited. For example:ulimit -n 10240

v Check that the current setting for the NOFILES kernel parameter is set to avalue that is at least equal to the value that you specify for ulimit.

v Linux If the target installation directory for InfoSphere InformationServer, IBM WebSphere Application Server, or IBM DB2 is an NFS filesystem, ensure that the lock daemon is running.ps -ef | grep -i lockd

If the lock daemon is not running, refer to your operating systemdocumentation for the preferred method of starting daemon services.

5. Change to the is-suite directory within the directory that contains theinstallation media.

6. Run the installation program:

Linux UNIX

./setup [-verbose]

Windows

setup.exe [-verbose]

The -verbose option is optional. The option causes the installation program todisplay log messages to the console and also write them to the log file. If the-verbose option is not specified, log messages are written to the log file only.Several messages are displayed. Then the program describes how to access thegraphical interface:======> Enter one of the following URLs to your web browser to begin theinstallation process:http://localhost:8080/ISInstallhttps://localhost:8443/ISInstall

7. Open a Web browser on the computer or on a remote computer, and navigateto one of the addresses that are listed in the messages that are displayed inthe previous step.

Note: Windows The installation program automatically launches the defaultWeb browser on the local computer and navigates to the HTTP address.A Login Installation window is displayed in the Web browser window.A message might appear in the browser that reads "The publisher cannot beverified..." You can safely ignore the message and continue the installation.This message does not indicate a security risk when it appears duringInfoSphere Information Server installation.

8. To display messages in a language other than English, select the language inthe Select a language field.

Note: This language selection only applies to this installation session. Later inthe installation process, you select the language to apply to the InfoSphereInformation Server installation.

9. Click Login. The first wizard page is displayed.10. Follow the prompts in the wizard. After you accept the license agreement, the

program runs a short prerequisites check. The wizard page displays each


check. If the check fails, it is marked FAILED in the page. If the check foundissues that might cause problems with the installation, it is markedWARNING in the page.

11. If you receive FAILED or WARNING messages:a. Double-click each message to learn more about resolving it.b. Try to resolve each issue without exiting the installation program. Then

click Check Again in the Prerequisites Check page.c. If you have to exit the installation program, click Cancel, close the browser

window, and type Ctrl+c in the session window to end the installationsession. Resolve the issues and then restart the installation program.

12. When all prerequisites checks pass, continue to follow the prompts in thewizard. The installation program prompts you for the installation type. Youcan create an installation, add product modules to existing installation, or adda software tier to a computer that already hosts tiers. Then the wizardprompts you for information that is specific to the type of installation that youselected.After the installation program has collected your selections, it runs a detailedprerequisites check based on your selections. During this check, it analyzesyour computer resources and file system to determine whether the installationis likely to succeed. The wizard page displays each check. If the check fails, itis marked FAILED in the page. If the check found issues that might causeproblems with the installation, it is marked WARNING in the page.

13. If you receive FAILED or WARNING messages:a. Double-click each message to learn more about resolving it.b. Try to resolve each issue without exiting the installation program. Then

click Check Again in the Prerequisites Check page.c. If you have to exit the installation program, click Cancel, close the browser

window, and type Ctrl+c in the session window to end the installationsession. Resolve the issues and then restart the installation program withyour response file as described in “Restarting in graphical mode with aresponse file” on page 184.

After the prerequisite check is complete, the installation program displays aResponse File Review page.

14. In the Response file location field, specify a name and location for theresponse file.

Note: Passwords are not saved in the response file. To use the response file ina subsequent installation pass, you must first edit the response file and addpasswords. To edit the response file, use a text editor.

15. At this point, you can choose to cancel the installation and use the savedresponse file in a later session. To continue, click Next.v To continue with the installation, click Install IBM InfoSphere Information

Server and save my settings in a response file and then click Next.v To cancel the installation, click Do not install IBM InfoSphere Information

Server and save my settings in a response file and then click Next. ClickOK in the confirmation window that appears.

16. If you choose to continue with the installation, the program displays asummary of the choices that you made in the wizard. When you click Next,the program begins the installation. While the installation is running:v Leave the terminal window open until the installation is complete.


v The system might occasionally request a response from you if it encountersan error. Check periodically to make sure that the system is not waiting foryou to respond. If the installation pauses for a long time, it might fail.

v Pop-up windows might be displayed, that you must respond to for theinstallation to proceed. Occasionally a pop-up window might be displayedbehind the browser window. If the installation halts for a long interval,check for pop-up windows displayed behind the browser window.

v After you have started the installation process, keep the browser windowopen to monitor progress and to respond if there is an error. If you closethe Web browser, the installation continues to the end. You can reconnect tothe session by opening a new browser session to the same URL. You canalso monitor the installation process by reading log files.

v Windows Depending upon your security settings, warning windows mightdisplay during the installation of the IBM DB2 database system or othercomponents. Ignore the warnings and click OK to continue the installation.

If the installation program encounters a problem, an Installation Exceptionwindow appears.v If this is the first time that the installation program has encountered this

problem, click Retry failed action and click OK.v If the problem reoccurs:

a. Review the last statements in the log file. See Chapter 27, “Log files,” onpage 393.

b. If the issue can be resolved, fix the issue and then click Retry.v Do not continue an installation if there are errors.When the installation is complete, an Installation Summary window isdisplayed. The following message is written to the log file:Installation Engine completed all steps successfully.

17. Click Finish or close the browser window.

18. Windows Restart the computer.

Restarting in graphical mode with a response fileYou can load settings from a response file into the IBM InfoSphere InformationServer installation program graphical interface.

Before you begin

Use a response file that the installation program created, or create one by using atext editor. See “Response files” on page 191.

Note: No passwords (administrator passwords, database passwords, and so on)are saved in the response file that is created by the installation program. Beforeyou use the response file, edit the file by using a text editor to add any passwords.Remove the passwords from the file after the installation.

About this task

After you enter settings in the InfoSphere Information Server installation programgraphical interface, the program saves your settings in a response file before itbegins the installation. When you run the installation program, you can load thesettings into the graphical interface instead of entering them again.


Alternatively, you can run the installation program in silent mode. In this mode,the program installs the software by using the settings in the response file withoutdisplaying a graphical interface.



v Windows Log in to the target computer as a local administrator or as a localor domain user who is directly assigned to the local Administrators group.


v Linux UNIX Open a command prompt or shell window.Open the window on the target computer, or use a graphical desktop sharingsystem. Keep the shell window open during the entire installation process. Ifyou use telnet or ssh, make sure that the session does not shut down ortimeout for the duration of the installation.







v Windows



umask 022








Linux UNIX

./setup -rsp response_file_name -uiMode graphical [-verbose]

Windows

setup.exe -rsp response_file_name -uiMode graphical [-verbose]

where response_file is the path and name of your response file.The -verbose option is optional. The option causes the installation program todisplay log messages to the console and also write them to the log file. If the-verbose option is not specified, log messages are written to the log file only.

7. Open a Web browser on the computer or on a remote computer, and navigateto one of the addresses that are listed in the messages that the installationprogram displays.

8. Follow the steps in “Starting the installation program in graphical mode” onpage 180 to log in and use the wizard. Each wizard page displays the settingsthat you specified in the response file. If necessary, you can change the valuesin the wizard.

Silent modeIn silent mode, the installation program does not display a user interface. Instead,it reads settings from a response file that you create. It performs a prerequisitescheck. If the check succeeds, the program installs the software.

Silent mode allows you to run an unattended installation. Also it allows you to domultiple similar installations quickly. For example, if you want to install identicalclient tier software on multiple workstations, you can create a single response fileand install the software on each workstation in silent mode instead of using thegraphical user interface each time.

Starting the installation program in silent modeYou can install IBM InfoSphere Information Server without starting the graphicinterface. In this mode, the installation program reads your installation choicesfrom a response file.




program” on page 177.4. Create a response file. See “Response files” on page 191.

About this task

The following procedure describes how to start the installation program in silentmode with the most commonly used command-line options. For more information,see “setup command syntax” on page 189.






v Linux UNIX Open a command prompt or shell window.Open the window on the target computer, or use a graphical desktop sharingsystem. Keep the shell window open during the entire installation process. Ifyou use telnet or ssh, make sure that the session does not shut down ortimeout for the duration of the installation.







v Windows



umask 022






6. Run the following command to start the installation program:


Linux UNIX

./setup -rsp response_file -verbose

Windows

setup.exe -rsp response_file -verbose

where response_file is the path and name of your response file.The -verbose option is optional. The option causes the installation program todisplay log messages to the console and also write them to the log file. If the-verbose option is not specified, log messages are written to the log file only.When you start the installation program, the program begins to displaymessages in the window if the -verbose option is specified. The installationprogram runs through a prerequisites check phase. If all prerequisite checkspass, installation continues until the installation process finishes.If one or more prerequisite checks fail, the installation displays errors andstops. The prerequisites check report contains messages like the following line:FAIL - The DB2 installation directory C:\IBM\SQLLIB must be empty.

7. If a prerequisites check fails, correct the problem and restart the installation.

8. Windows While the installation is running:v Monitor the installation as described in “Monitoring installation progress” on

page 194.v Leave the terminal window open until the installation is complete.v The system might occasionally request you to grant permissions to execute a

process, such as Java.exe or db2setup.exe. When this prompt is displayed,click Yes. The system might also display a firewall warning if the firewall isnot shutdown or disabled. Click through the warning to allow theinstallation program to continue.

If the installation program encounters a problem, it displays an exceptionhandling message.v If this is the first time that the installation program has encountered this

problem, choose Retry.v If the problem reoccurs:

a. Review the last statements in the log file. See Chapter 27, “Log files,” onpage 393.

b. If the issue can be resolved, fix the issue and then choose Retry.v Do not continue an installation if there are errors.When the installation is complete, the following message appears in the log file:Installation Engine completed all steps successfully.


Error handling in silent modeYou can specify the action that the installation program takes if an error occurswhile it is running in silent mode.

About this task

By default, if an error occurs during an installation while the program is runningin silent mode, the installation program halts with an error message. For trueunattended operation, you can change this behavior by setting an environmentvariable.


Procedure1. On the target computer, set the EXCEPTION_POLICY environment variable to

one of the following values:

Table 74. EXCEPTION_POLICY values

Value Description

1 Prompt user to retry on error (defaultbehavior)

2 Continue on error.Important: Continuing an installation afteran error occurs might result in anonoperational installation, or might causeexisting installed software to stopfunctioning. Use this option only if directedby IBM Support.

3 Exit on error

For example:

v Linux UNIX

setenv EXCEPTION_POLICY=1

v Windows

set EXCEPTION_POLICY=1

2. Start the installation program.

setup command syntaxYou use the setup command to run the IBM InfoSphere Information Serverinstallation program.

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 programto start in graphical mode.

-helpDisplays this usage information, and terminates.

-uiMode modeSpecifies the mode to run in. mode can be graphical (default) or silent.

-rsp rspfileSpecifies the response file to use for this installation. For a silent modeinstallation, you must specify a response file by using this parameter. For agraphical mode installation, the settings in the response file that you specifyappear in the wizard and you do not have to enter them again.

If you specify the -rsp parameter, the installation program runs in silent modeby default. To run in graphical mode with a response file, you must alsospecify the -uiMode graphical parameter.


-reportOnlyFor a silent mode installation only. Performs the prerequisites check but doesnot perform the installation.

Use with the -reportFile parameter to store the results of the prerequisitescheck in a text file.

If this parameter is specified for a software removal, the parameter is ignored.

-forceUse -force to permit the installation program to continue even if prerequisitescheck tests fail.

In graphical mode, if -force is specified on the command line and aprerequisites check fails, an Ignore FAILED items and continue check box isshown in the window. To continue the installation, click this check box andthen click Next. If -force is not specified, the check box is not shown and theNext button is disabled.

In silent mode, if -force is specified on the command line and a prerequisitescheck fails, the installation process continues. If -force is not specified, theinstallation process halts if prerequisites check tests fail.

Important: Prerequisites check FAILED and WARNING messages indicateitems that might cause a failed installation, or cause malfunctions in theinstalled software. Use the -force option only if directed by IBM Support.

-reportFile rptfileFor a silent mode installation only. Specifies a text file for the prerequisitescheck report.

If a reportFile value is not specified, the report is displayed to the console.

-language languagecodeSpecifies the language that displays for the installation.

The following table lists valid language codes.

Table 75. 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

-verboseStarts the installation session in trace mode. In this mode, log messages aredisplayed to the console and are also written to the log file. You can use thisoption in silent mode or graphical mode.


If you do not specify this parameter, log messages are written to the log fileonly.

-secureFor a graphical mode installation only. Prompts you to create a password whenthe installation program starts. The password is used to authenticate access tothe installation program from the browser. The password can be any string ofalphanumeric characters. The password can include white-space characters.

Examples

The following command causes the installation program to start in graphical modeon a Linux or UNIX system:./setup

The following command causes the installation program to prompt for a passwordand then start in graphical mode. When the user accesses the installation programby using the browser, a login window is displayed. The user enters the passwordin the login window to access the installation program../setup -secure

The following command causes the installation program to prompt for a passwordand then start in graphical mode. The installation program uses the settings in thersp.txt response file. It stores log messages in a log file../setup -secure -rsp rsp.txt -uiMode graphical

The following command causes the installation program to start in silent mode.The installation program uses the settings in the rsp.txt response file. It stores logmessages in a log file. When the prerequisites checks run, results are stored inprq.txt. The installation program stops if a prerequisite check test fails../setup -rsp rsp.txt -reportFile prq.txt

The following command causes the installation program to start in silent mode.The installation program uses the settings in the rsp.txt response file. It stores logmessages in a log file. When the prerequisites checks run, results are stored inprq.txt. The installation program stops after the prerequisites check withoutinstalling the software../setup -rsp rsp.txt -reportFile prq.txt -reportOnly

The following command causes the installation program to start in silent mode.The installation program uses the settings in the rsp.txt response file. It stores logmessages in a log file and also displays them to the console. When theprerequisites check runs, results are stored in prq.txt../setup -rsp rsp.txt -reportFile prq.txt -verbose

Response filesA response file contains parameters and values that tell the IBM InfoSphereInformation Server installation program how to perform an installation. You canalso use a response file during software removal. Create a response file by usingthe InfoSphere Information Server installation or software removal program, or bymodifying the sample templates that are included on the installation media.

Different sets of parameters and values are used depending on the type of softwareinstallation or removal. For example, a certain set of parameters and values is used


for an installation that includes application server clustering. Another set is usedfor an installation where the application server is set up in a stand-aloneconfiguration.

For lists and descriptions of response file parameters and values, go to thefollowing topics:

v Linux UNIX Appendix A, “Response file parameters (Linux, UNIX),” onpage 429

v Windows Appendix B, “Response file parameters (Windows),” 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.To use the wizard to create the file:1. Run the installation program or software removal program in graphical

mode.2. Specify your parameters in the wizard.3. When the Response File Review page is displayed, select either Install

IBM InfoSphere Information Server and save my settings in aresponse file or Do not install IBM InfoSphere Information Serverand save my settings in a response file. Either selection causes aresponse file to be created.

4. Specify a file name and location and click Next. The program savesyour parameters in a response file in the specified location. Theprogram then either performs the operation or exits, depending uponyour selections in the window.

Modify one of the sample response file templates that are included with theinstallation media.

Several different templates are included for different installation types. Thetemplates 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 moreinformation about them.

Response file syntax

A response file is a text file. In the file, parameters and values are specified one perline. In each line, the parameter is separated from the value with an equals sign(=). A line that begins with a pound sign (#) indicates a comment. Parameters andvalues are case sensitive. Blank lines are ignored.

To specify a backslash in the response file, include two backslashes. For example:suite.installLocation=C:\\IBM\\InformationServer

To set a parameter to a null value, omit the parameter value or specify theparameter without a value. For example:xmeta.db.tablespace=


Passwords in a response file

To use a response file, you must specify passwords in the file. If the file is createdby the installation or software removal program, the program does not store thepasswords in the file. Instead, locations in the file where passwords must beincluded are indicated with markers. For example:app.server.password=<CHANGE_TO_YOUR_PASSWORD>

Replace the markers with your passwords. For example:app.server.password=mypassword

If you want to include passwords in encrypted format, see “Encryptinginformation in a response file.”

Encrypting information in a response fileYou can encrypt passwords and other information in response files.

About this task

By default, information is stored in plain text in response files. If you want toencrypt passwords or other information in your response files, follow thisprocedure to encrypt information and include it in the files.

You can encrypt any values in a response file. However, this procedure is typicallyused to encrypt passwords.

Procedure1. Create a response file. See “Response files” on page 191.2. Run the genkey command to generate encrypted information. The genkey

command is located in the tools directory on your installation media:

v Linux UNIX

install_media/tools/genkey.sh info_to_encrypt

v Windows

install_media\tools\genkey.cmd info_to_encrypt

For example:C:\is-suite\tools\genkey.cmd mypassword

Messages are displayed in the terminal window. Then the command displaysthe encrypted version of the specified information. For example:{xor}8Y3lImYJo0sxGOl4igw/pA==

3. In the response file, append the extension .encrypted to the parameter. Replacethe value with the encrypted version. For example:v Original parameter specification:

app.server.password=<CHANGE_TO_YOUR_PASSWORD>

v Encrypted parameter specification:app.server.password.encrypted={xor}8Y3lImYJo0sxGOl4igw/pA==


Monitoring installation progressYou can follow the progress of an installation by monitoring log files.

You can monitor log files to track the following installation processes:v The overall IBM InfoSphere Information Server suite installationv The IBM WebSphere Application Server application installationv The IBM WebSphere Application Server enterprise archive (EAR) deploymentv Individual IBM InfoSphere DataStage component installations

To monitor a log file, use the command tail -f logfilename where logfilename isthe path and name of the log file.

Windows The tail command is available on Microsoft Windows systems if youhave installed Microsoft Windows Resource Toolkit or a third-party tail utility. Thecommand is also available if you have installed the InfoSphere DataStage client orserver-side software. (The MKS Toolkit is installed with these product modules.)

If the tail command is not available, open the log file in a text editor that does notlock the file for editing while it is open. To view updates, close the file and thenreopen it.

The monitoring procedures assume that you have installed InfoSphere InformationServer in the default installation path. This path is:

v Windows C:\IBM\InformationServer

v Linux UNIX /opt/IBM/InformationServer

If your installation is located in a different path, substitute your path when youperform the procedures.

Monitoring the IBM InfoSphere Information Server installationYou can follow the progress of the IBM InfoSphere Information Server suiteinstallation by monitoring the installation log file.

Before you begin

To monitor log files as they are created, you can use the tail command.

Windows The tail command is available on Microsoft Windows systems if youhave installed Microsoft Windows Resource Toolkit or a third-party tail utility. Thecommand is also available if you have installed the IBM InfoSphere DataStageclient or server-side software. (The MKS Toolkit is installed with these productmodules.)

About this task

To follow the progress of the InfoSphere Information Server suite installation,monitor the installation log file.

Procedure1. On the computer on which the installation program is running, navigate to the

directory that contains the log file:

v AIX Linux UNIX


cd /tmpcd ibm_is_logs

v Windows

cd %temp%cd ibm_is_logs

Note: In Preparing to run the installation program, if you redirected theinstallation program's temporary files to a different directory, go to that locationinstead.

2. Enter the following command:tail -f ISInstall*.log

where ISInstall*.log is the log file with the most recent date-time stamp.If the tail command is not available, open the log file in a text editor that doesnot lock the file for editing while it is open. To view updates, close the file andthen reopen it.

Monitoring the IBM WebSphere Application Server installationYou can follow the progress of the WebSphere Application Server installation bymonitoring the installation log file.

Before you begin



About this task

To follow the progress of the WebSphere Application Server installation, monitorthe installation log file.



v Windows

cd c:\IBM\InformationServer\logs

v Linux UNIX

cd /opt/IBM/InformationServer/logs

2. Enter the following command:tail -f WebSphereInstall.log

If the tail command is not available, open the log file in a text editor that doesnot lock the file for editing while it is open. To view updates, close the file andthen reopen it.

Note: The installation process updates the WebSphere Application Server suiteinstallation log file sporadically. There might be gaps of up to 20 minutes whenno updates are displayed.


Monitoring the IBM WebSphere Application Server enterprisearchive deployment

You can follow the progress of the IBM WebSphere Application Server enterprisearchive (EAR) deployment by monitoring the installation log file.

Before you begin



About this task

To follow the progress of the IBM WebSphere Application Server EAR deployment,monitor the installation 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. Enter the following command:tail -f SystemOut.log

If the tail command is not available, open the log file in a text editor that doesnot lock the file for editing while it is open. To view updates, close the file andthen reopen it.

Note: Some EAR deployments can take up to 25 minutes, which can cause theinstallation program to seem as if it has stopped running.

Monitoring IBM InfoSphere DataStage component installationsYou can follow the progress of individual IBM InfoSphere DataStage componentinstallations by monitoring the component installation log file.

Before you begin


Windows The tail command is available on Microsoft Windows systems if youhave installed Microsoft Windows Resource Toolkit or a third-party tail utility. Thecommand is also available if you have installed the InfoSphere DataStage client orserver-side software. (The MKS Toolkit is installed with these product modules.)


About this task

You can monitor the installation of the following InfoSphere DataStagecomponents:v InfoSphere DataStage plug-insv PX operatorsv Connectors

Each component must be installed into each project on each host system. If youhave many projects, the plug-in installation can take considerable time.



v Windows

cd c:\IBM\InformationServer\Server\StagingArea\Log

v Linux UNIX

cd /opt/IBM/InformationServer/Server/StagingArea/Log

2. Enter the following command:tail -f ISInstall*.log

where ISInstall*.log is the log file with the most recent date-time stamp.If the tail command is not available, open the log file in a text editor that doesnot lock the file for editing while it is open. To view updates, close the file andthen reopen it.

Installation verification and troubleshootingThe IBM® Support Assistant Lite for InfoSphere Information Server tool providesfunctionality to collect data, files, and artifacts from the local installation of IBMInfoSphere Information Server. It focuses on performing non-destructive tests andpassive collection of data to report the system health and verify the correctconfiguration of the installation.

What the tool offers

The IBM® Support Assistant (ISA) Lite for InfoSphere Information Server tool helpsyou troubleshoot InfoSphere Information Server problems. The tool focuses onautomatic collection of problem data and provides diagnostic verifications of anInfoSphere Information Server installation. Information pertinent to a problem iscollected and analyzed to identify the origin of the problem. The IBM SupportAssistant Lite for InfoSphere Information Server tool reduces the effort and amountof time it takes you to send the appropriate diagnostic data to IBM CustomerSupport by automating the gathering and collection process. The tool FTPs theresults to IBM Support and attaches them to an existing PMR (problemmanagement record). Additionally, the tool performs symptom analysis to helpstreamline the problem determination process. To verify the installation, run theGeneral Diagnostic Health Checker and other product-specific health checkers. Thehealth checkers are available under the All Diagnostic Tools menu.


Where to find the tool

IBM Support Assistant Lite for InfoSphere Information Server tool is installed inthe ISALite folder under IS_HOME when you run the installation program. Forinformation about how to get the tool for previous releases and for any updatesthat are available, refer to www.ibm.com/support/docview.wss?rs=14&uid=swg24022700.

Documentation

Refer to the following documentation that is available under the \doc folder of theISALite installation.

IBM Support Assistant Lite for InfoSphere Information Server Quick StartGuide Provides an overview of the ISALite tool and what you must configure to

get started.

IBM Support Assistant Lite for InfoSphere Information Server User's GuideProvides a detailed description of the ISALite tool.

Updates to the documentation are available at www.ibm.com/support/docview.wss?rs=14&uid=swg24022700.

Installation program sample scenariosFor the sample scenarios that are described in the planning portion of thisdocumentation, run the installation program as described in these topics.

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

“Sample scenario A: Basic client-server topology” on page 84 describes a simpleIBM InfoSphere DataStage installation. In this configuration, the metadatarepository tier, services tier, and engine tier are installed on one server, and theclient tier is installed on five separate workstations.

Metadata repository tier, services tier, and engine tier installation

Set up the hardware and the network, and complete all other preinstallation tasks.Then run the installation program on the computer in graphical mode.

The program runs a basic requirements check. If all checks pass, the installationproceeds. The user response to each wizard page is described in the followingtable:

Table 76. Scenario A: Metadata repository tier and services tier installation

Wizard page title User action

Early Requirements Check After all tests pass, click Next.

IBM InfoSphere Information ServerInstallation Directory

Click Next to accept the default installationdirectory.

Installation Type Selection Choose New installation.

Tier Selection Choose Metadata repository, Services, andEngine.

Product Selection Choose IBM InfoSphere DataStage.






Table 76. Scenario A: Metadata repository tier and services tier installation (continued)


IBM InfoSphere DataStage InstallationOptions

Choose IBM InfoSphere DataStage. Clearall other check boxes.

High Availability Server ClusterConfiguration

This is not a high availability active-passiveconfiguration. Leave This is anactive-passive server cluster configurationcleared.

Application Server Options Choose Install WebSphere ApplicationServer.

IBM WebSphere Application ServerInstallation Directory

Leave the Customize the port values checkbox selected. Click Next to accept the defaultinstallation directory.

IBM WebSphere Application Server ProfilePorts Assignment

Click Next to accept the specified ports. Theport values are selected automatically basedon the current system configuration.

Application Server Administrator Accept the default user name (wasadmin)and provide a password.

IBM InfoSphere Information ServerAdministrator

Specify isadmin as the user name andprovide a password.

Database Management System Selection Choose Install IBM DB2 9.7 EnterpriseServer Edition.

DB2 Installation Directory Click Next to accept the default installationdirectory. The installation program installsDB2 in this directory.

IBM DB2 Instance User As the instance name, enter the user nameof the DB2 instance owner account that theuser created before running the installationprogram. Also enter the port number to usefor the DB2 instance.

DB2 Fenced User Information Click Existing user. Enter the user name ofthe DB2 fenced user that the user created onthe target computer before starting theinstallation program.

DB2 Administrator User Information Click Existing user. Enter the user name ofthe DB2 administrator user that the usercreated on the target computer beforestarting the installation program.

Metadata Repository Configuration Enter the account information of the DB2database owner that was created beforerunning the installation program. Alsospecify the database name, instance name,and location.

IBM InfoSphere Information Server AgentPorts Configuration

Click Next to accept the default values inthis page.

IBM InfoSphere DataStage Administrator Enter the user name of the IBM InfoSphereDataStage administrator that the usercreated on the target computer beforestarting the installation program.

Job Monitor Ports Configuration Click Next to accept the default values inthis page.


Table 76. Scenario A: Metadata repository tier and services tier installation (continued)


IBM InfoSphere DataStage Instance TagInformation

A single instance of the IBM InfoSphereInformation Server engine is to be installedon the computer. Leave the ConfigureEngine Instance tag instance check boxcleared.

IBM InfoSphere DataStage and IBMInfoSphere QualityStage Globalization

International code pages must be supported.Leave the Install globalization support forIBM InfoSphere DataStage and IBMInfoSphere QualityStage check boxselected.

IBM WebSphere MQ Plug-in Selection No existing jobs depend on the IBMWebSphere MQ plug-in. Leave the InstallWebSphere MQ Plug-in check box cleared.

SAS Configuration There are no existing jobs that require SAS.Leave the Enable a legacy SASconfiguration check box cleared.

IBM InfoSphere DataStage Projects No additional projects are required at thistime. Click Next.

System Requirements Check After all tests pass, click Next.

Response File Review Click Next to save the file in its defaultlocation.

Preinstallation Summary for the CurrentComputer

Review the summary, and click Next to startthe installation.

Client installation

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

Table 77. Scenario A: Client tier installation

Wizard page User action





Tier Selection Choose Client.






After all client installations are completed, do the postinstallation configurationsteps that are described in “Sample scenario A: Basic client-server topology” onpage 84.


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

Sample scenario B describes an IBM InfoSphere DataStage installation with adedicated server for the engine tier. In this configuration, the metadata repositorytier and services tier are installed on one computer, the engine tier is installed onanother computer, and the client tier is installed on other computers.

Metadata repository tier and services tier installation

Set up the hardware and the network, and complete all other preinstallation tasks.Run the installation program in graphical mode, and respond to wizard pages asdescribed in the following table:

Table 78. Scenario B: Metadata repository tier and services tier installation






Tier Selection Choose Metadata repository and Services.



Choose IBM InfoSphere DataStage (paralleland server canvas). Clear all other checkboxes.


This is not a high availability active passiveconfiguration. Leave This is anactive-passive server cluster configurationcleared.



Leave the Customize the port values checkbox selected. Click Next to accept the defaultinstallation directory.


Click Next to accept the specified ports. Theport values are selected automatically basedon the current system configuration.

Application Server Administrator Accept the default user name (wasadmin)and provide a password.


Specify isadmin as the user name andprovides a password.

Database Management System Selection Choose Install IBM DB2 9.7 EnterpriseServer Edition.

DB2 Installation Directory Click Next to accept the default installationdirectory.

IBM DB2 Instance User As the instance name, enter the user nameof the DB2 instance owner account that youcreated before running the installationprogram. Also enter the port number of theDB2 instance.


Table 78. Scenario B: Metadata repository tier and services tier installation (continued)


DB2 Fenced User Information Click Existing user and enter the user nameof the DB2 fenced user that was createdbefore running the installation program.

DB2 Administrator User Information Click Existing user and enter the user nameof the DB2 administrator user that wascreated before running the installationprogram.

Metadata Repository Configuration Enter the account information of the DB2database owner that was created beforerunning the installation program. Alsospecify the database name, instance name,and location.





Engine tier installation

Set up the hardware and the network, and complete all other preinstallation tasks.Run the installation program in graphical mode, and respond to wizard pages asdescribed in the following table:

Table 79. Scenario B: Engine tier installation






Tier Selection Choose Engine.

IBM InfoSphere Information Server Location Select Use Secure Sockets Layer (SSL) forHTTP communication. Specify the hostname of the services tier computer, and theport number of the front-end Web server onwhich secure HTTP (HTTPS) has previouslybeen configured. Enter the administrator IDand password of the IBM InfoSphereInformation Server administrator user thatyou created on the servers before runningthe installation program.





This is not a high availability active passiveconfiguration. Leave This is anactive-passive server cluster configurationcleared.




Table 79. Scenario B: Engine tier installation (continued)


IBM InfoSphere DataStage Administrator Enter the user name of the IBM InfoSphereDataStage administrator that you created onboth servers before starting the installationprogram.



A single instance of the InfoSphereInformation Server engine is to be created.Do not select the Configure Engine Instancetag instance check box.


International code pages need to besupported. Do not clear the Installglobalization support for IBM InfoSphereDataStage and IBM InfoSphereQualityStage check box.


SAS Configuration There are no jobs that require SAS. Leavethe Enable a legacy SAS configurationcheck box cleared.

IBM InfoSphere DataStage Projects No additional projects are needed at thisstage. Click Next.





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 80. Scenario B: Client tier installation













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

Running the installation program for Scenario CFor 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). Themetadata 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 (thepassive server) is started, but is not running any tier software. IBM Tivoli SystemAutomation for Multiplatforms is installed on both the active server and thepassive server. The HA software maintains a heartbeat: a periodic signal from theactive server to the passive server that indicates that the active server isoperational. If the active server fails, the heartbeat also fails. The HA softwarerestarts 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 andvirtual host name are specified for the system. This information is associated withthe active server. All client programs connect to the system by using this addressor host name. If the active server fails, the information is automaticallyreassociated with the passive server. Client programs do not need to connect to adifferent address.

Metadata repository tier, services tier, and engine tier installation

Set up the hardware and the network, install and configure the HA software, andcomplete 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




To install the software on the SAN, clickNext to accept the default installationdirectory. The default directory(/opt/IBM/InformationServer) is within thepreconfigured SAN shared directory.


Tier Selection Choose all tiers. The metadata repositorytier, services tier, and engine tier softwarewill all be located on the SAN. (The clienttier is not offered for a non-MicrosoftWindows installation.)

Product Selection Choose IBM InfoSphere DataStage, IBMInfoSphere QualityStage, and IBMInfoSphere Information Analyzer.


Choose IBM InfoSphere DataStage (paralleland server canvas). Clear all other checkboxes.


Table 81. Scenario C: Metadata repository tier, services tier, and engine tierinstallation (continued)



This panel applies specifically to the targetinstallation (an active-passive configuration).

Select This is an active-passive servercluster configuration. In the Virtual hostname field, type the preconfigured floatinghost name to share between the servers.



Leave the Customize the port values checkbox selected. Click Next to accept the defaultinstallation directory. The default directory(/opt/IBM/WebSphere/AppServer) is withinthe preconfigured SAN shared directory.


Click Next to accept the specified port. Theport values are selected automatically basedon the current system configuration.

Application Server Administrator Enter the user name and password of theIBM WebSphere Application Serveradministrator, which will be created in theinternal registry.


Enter the user name and password of theIBM InfoSphere Information Serveradministrator user, which will be created inthe internal registry.

Database Server Select Install IBM DB2 Enterprise Edition.

DB2 Installation Directory Click Next to accept the default installationdirectory. The default directory(/opt/IBM/db2/V9.7) is within thepreconfigured SAN shared directory.

IBM DB2 Instance User Click Existing user. Enter the instance nameand port number that you created on bothservers before starting the installationprogram.

DB2 Fenced User Information Click Existing user. Enter the user name ofthe DB2 fenced user that you created onboth servers before starting the installationprogram.

DB2 Administrator User Information Click Existing user. Enter the user name ofthe DB2 administrator user that you createdon both servers before starting theinstallation program.

Metadata Repository Configuration Enter the account information of the DB2database owner that the user created onboth servers before starting the installationprogram. Specify the database name,instance name, and location.




Table 81. Scenario C: Metadata repository tier, services tier, and engine tierinstallation (continued)


IBM InfoSphere DataStage Administrator Enter the user name of the IBM InfoSphereDataStage administrator that you created onboth servers before starting the installationprogram.





International code pages must be supported.Do not clear the Install globalizationsupport for IBM InfoSphere DataStage andIBM InfoSphere QualityStage check box.


SAS Configuration There are no existing jobs that require SAS.Leave the Enable a legacy SASconfiguration check box cleared.

IBM InfoSphere DataStage Projects No additional projects are required at thisstage. Click Next.

IBM InfoSphere Information AnalyzerRepository Configuration

Enter the user name and password of theIBM InfoSphere Information Analyzeranalysis database owner that you created onboth servers before starting the installationprogram.

Click Next to accept the default databaselocation. The default directory(/opt/IBM/InformationServer/Repos/iadb) iswithin the preconfigured SAN shareddirectory.


Response File Review Click Next to save the file in its defaultlocation. The default directory(/opt/IBM/InformationServer/response.txt)is within the preconfigured SAN shareddirectory. This location allows the user torun the installation program again fromeither server to make changes if necessary.



Client installation



Table 82. Scenario C: Client tier installation







Product Selection Choose IBM InfoSphere DataStage, IBMInfoSphere QualityStage, and IBMInfoSphere Information Analyzer.





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

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

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

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

Metadata repository tier installation

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

Set up a separate DB2 installation for the IBM InfoSphere Information Analyzeranalysis database. Run the installation script to create the analysis database withinthis 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 ServerNetwork Deployment for a clustered installation. Create a deployment managerprofile, a custom profile, a cluster, and cluster members. Install a front-end Webserver. Run the installation program in graphical mode, and respond to wizardpages as described in the following table:


Table 83. Scenario D: Services tier installation




Click Next to accept the default installationdirectory which is /opt/IBM/InformationServer.


Tier Selection Choose Services.

Product Selection Choose all product modules.




This tier is not set up in an active-passiveconfiguration. Leave This is anactive-passive server cluster configurationcleared and click Next.

Application Server Options Choose Use an existing WebSphereApplication Server installation.


Specify the WebSphere Application Serverinstallation directory.

WebSphere Application Server Profile Select the WebSphere Application ServerDeployment Manager (dmgr) profile.

WebSphere Application Server ClusterInformation

Select Use Secure Sockets Layer (SSL) forHTTP communication. Specify the hostname and port number of the front-end Webserver on which secure HTTP (HTTPS) haspreviously been configured.

Application Server Administrator Enter the name and password of theWebSphere Application Server administratoruser, which will be created in the internalregistry.


Enter the name and password of theInfoSphere Information Server administratoruser, which will be created in the internalregistry.

Database Management System Selection Click Use existing database managementsystem installation (do not create thedatabase).

Database Connection In the Database type menu, select IBM DB2V9. Enter the host name and port of the DB2database. Also enter the database name anddatabase owner name and password.


Enter the account information of the IBMInfoSphere Information Analyzer analysisdatabase owner that you created on theservers before running the installationprogram. Also specify the database name,instance name, and location of the DB2instance that was created for this database.


Response File Review Click Next to save the file in its defaultlocation (/opt/IBM/InformationServer/response.txt).


Table 83. Scenario D: Services tier installation (continued)




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

Engine tier installation

Set up the hardware and the network, install and configure the HA software, anddo all other preinstallation tasks. Configure the SAN mount point as /opt/IBM.Create identical sets of users and groups, including administrator users, on bothservers. Run the installation program in graphical mode. Run the installationprogram in graphical mode, and respond to wizard pages as described in thefollowing table:

Table 84. Scenario D: Engine tier installation




To install the software on the SAN, clickNext to accept the default installationdirectory which is /opt/IBM/InformationServer.


Tier Selection Choose Engine.

IBM InfoSphere Information Server Location Select Use Secure Sockets Layer (SSL) forHTTP communication. Specify the hostname of the services tier computer, and theport number of the front-end Web server onwhich secure HTTP (HTTPS) has previouslybeen configured. Enter the administrator IDand password of the IBM InfoSphereInformation Server administrator user thatyou created on the servers before runningthe installation program.





This panel applies specifically to this portionof the installation (an active-passiveconfiguration).

Select This is an active-passive servercluster configuration. In the Virtual hostname field, type the preconfigured floatinghost name to share between the servers.


Enter the name and password of the IBMInfoSphere Information Server administratoruser, which will be created in the internalregistry.


Table 84. Scenario D: Engine tier installation (continued)




IBM InfoSphere DataStage Administrator Enter the user name of the IBM InfoSphereDataStage administrator that you created onboth servers before running the installationprogram.





International code pages need to besupported. Do not clear the Installglobalization support for IBM InfoSphereDataStage and IBM InfoSphereQualityStage check box.


SAS Configuration No existing jobs use SAS. Leave the Enablea legacy SAS configuration check boxcleared.

IBM InfoSphere DataStage Projects No additional projects are needed at thisstage. Click Next.


Enter the name and password of the IBMInfoSphere Information Analyzer analysisdatabase owner that you created on bothservers before running the installationprogram.

Click Next to accept the default databaselocation. This location (/opt/IBM/InformationServer/Repos/iadb) is within thepreconfigured SAN shared directory.


Response File Review Click Next to save the file in its defaultlocation. This location (/opt/IBM/InformationServer/response.txt) is withinthe preconfigured SAN shared directory.This location allows you to run theinstallation program again from either serverto make changes if necessary.



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


Client installation


Table 85. Scenario D: Client tier installation












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



Chapter 13. Updating products and components

Use the Update Installer to update IBM InfoSphere Information Server andassociated product modules.

About this task

The Update Installer is installed as part of InfoSphere Information Server in thefollowing 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.





Chapter 14. Installing components that are not in the suiteinstallation program

Some components have their own installation programs. You install thesecomponents after you install IBM InfoSphere Information Server.

Installing the IBM InfoSphere Business Glossary Anywhere clientTo use IBM InfoSphere Business Glossary Anywhere, you must install andconfigure the client.

Preparing for enterprise-wide distributionTo take advantage of IBM InfoSphere Business Glossary Anywhere enterprise-wideinstallation and update features, administrators can copy the installation files forIBM InfoSphere Business Glossary Anywhere client to a shared directory and edit aconfiguration file.

Before you beginv The InfoSphere Business Glossary Anywhere server must already be installed in

the services tier.v You must know the name and port number of the system where IBM InfoSphere

Business Glossary is installed. For detailed information about the name and portnumber requirements, see “Server configuration parameters” on page 216.

v If you are installing an update to the client such as a patch or fix pack, and wantto take advantage of the automatic update feature, you must know the directorypath where the previous client installation files are located.

About this task

You must install and configure the InfoSphere Business Glossary Anywhere clientseparately from the installation of IBM InfoSphere Information Server. The clientruns on individual user computers running Microsoft Windows operating systems.(See the InfoSphere Information Server system requirements for specific systemrequirements.)

InfoSphere Business Glossary Anywhere provides the following enterprise-wideinstallation features:v Users can install the client from a central location.v User computers can be automatically updated when a software update to the

InfoSphere Business Glossary Anywhere client becomes available.

To install the client from a central location, administrators must create a directorythat is shared over the network that contains the installation files. From the shareddirectory, each user can install the client on his own computer. Optionally,administrators can edit a configuration file whose values are propagated to all theclients during this initial installation. The configuration file, config.ini, specifiesconnection information between the server and the InfoSphere Business GlossaryAnywhere clients.



To use the automatic update feature, you must copy the compressed file containingthe updated InfoSphere Business Glossary Anywhere client to the same shareddirectory that was used for the previous version. Then, the next time a user startsthe client, it is automatically updated.

Note: The automatic update feature works for updates, such as fix packs, to aparticular InfoSphere Business Glossary Anywhere version, but it cannot updatefrom one version to another. For example, this feature cannot be used to updatethe client from InfoSphere Business Glossary Anywhere, Version 8.1.2 to InfoSphereBusiness Glossary Anywhere, Version 8.5.

Procedure1. Copy the file file_name.zip to a shared directory that can be accessed by users,

where file_name.zip is the name of the file containing the InfoSphere BusinessGlossary Anywhere client. This file is a compressed file that contains all thefiles required for installing InfoSphere Business Glossary Anywhere. Forexample, for InfoSphere Business Glossary Anywhere, Version 8.5, this file isBGA_WIN_85.zip.

Note: If the client has already been installed at your site, copy the installationfiles to the same directory where the installation files of the current version arelocated to take advantage of the automatic update feature.

2. (First-time installation only.) In the root of the installation directory, openconfig.ini with a text editor. Change the configuration values for your site.

Note: The values configured in the config.ini file take effect the first time youinstall the InfoSphere Business Glossary Anywhere client on each usercomputer. For subsequent installations (updates), configuration changes mustbe made manually within each client, from the Settings screen.

What to do next

Next, install the InfoSphere Business Glossary Anywhere client in either of thefollowing 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 filesare now located, then users must manually install the client. See “Installing theclient” on page 219.

v If you are updating to a fix pack or other interim release and you install theinterim release files from the same directory from which the files of the priormajor version were installed, then the client is updated automatically the firsttime that the user runs the client. No user intervention is needed.

Server configuration parametersThe config.ini configuration file contains the parameters to configure theconnection between the server and all the clients for IBM InfoSphere BusinessGlossary Anywhere.

Purpose

The parameters in the config.ini file configure the settings in the ServerConfiguration tab in the client for InfoSphere Business Glossary Anywhere thefirst time that the client is installed. All clients that are installed from the server onwhich a particular config.ini file resides will be affected by the settings in thatfile.


Note: To change these parameters after the initial installation of the client, edit theparameters in the Server Configuration tab of each client.

Parameters

You can set the value for each parameter or accept the default value, if one exists.

CustomizedTextText you enter here is displayed on the Welcome screen beneath the producttitle.

Optional: Type in any alphanumeric text. The text does not extend beyond thewidth of the window and is truncated at the end of the last complete word. Donot include graphics such as company logos.

The default text is blank.

LogFileDirectoryWrites log messages to the log file in this directory.

Optional: Type the complete directory path on the local disk of the clientcomputer.

The default directory is C:\Documents and Settings\user account\ApplicationData\IBM\BusinessGlossaryAnywhere\Logs where user account is the name ofthe Microsoft Windows user account on the client computer. The clientinstallation program automatically determines the name of the user account oneach client computer.

LogToFileWrites messages to a log file.

Optional: Type true or false.

If LogToFile is false, the LogToEventViewer and LogFileDirectory parametersare ignored.

The default value is true.

PasswordSpecifies the password of the user account in the UserName parameter.

The password is not encrypted and can be seen by anyone who opens theconfig.ini file.

There is no default value.

PortSpecifies the port number of the Web console of the server or front-enddispatcher that is specified in the ServerName parameter.

The value of Port depends on whether IBM WebSphere Application Serverclustering is set up within your services tier configuration.

If clustering is set up Port is the port of the front-end dispatcher(either the Web server or the load balancer).

Do not use the port of a particular clustermember.

If clustering is not set up Port is the port that is assigned to the IBMInfoSphere Information Server Web console.

Chapter 14. Installing components that are not in the suite installation program 217

ServerNameThe value of ServerName depends on whether WebSphere Application Serverclustering is set up within your services tier configuration.

If clustering is set up ServerName is the name or IP address andthe port of the front-end dispatcher (eitherthe Web server or the load balancer).

Do not use the host name of a particularcluster member.

If clustering is not set up ServerName is the host name or IP addressof the computer where WebSphereApplication Server is installed.

UILanguageCodeDefines the language for the client to use. The default setting is English(United States).

Note: If the config.ini file is not found, the default is still English (UnitedStates).If the server is set to a different language than the client, then when the clientconnects to the server, the client language setting is changed to that of theserver. The user is prompted to restart the client for the new setting to takeeffect.

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

UserNameSpecifies the name of a user account that has access to IBM InfoSphereBusiness Glossary on the server in the ServerName parameter.

The user must have a Business Glossary Basic User role or higher.

There is no default value.

Sample config.ini file

This sample file configures InfoSphere Business Glossary Anywhere to writeinformational messages to a log file in C:\IBM\BGA\LOGS. Errors are also sent tothe Microsoft Windows Event Viewer. The company name, JK Enterprises, is


included in the Welcome and Getting Started windows. InfoSphere BusinessGlossary is installed on a server called sample_server.LogToFile=trueLogToConsole=falseLogFileDirectory=C:\IBM\BGA\LOGSServerName=sample_serverPort=9080UserName=sample_userPassword=sample_passwordCustomizedText=JK EnterprisesUILanguageCode=ja-JP

Installing the clientInstall and configure the IBM InfoSphere Business Glossary Anywhere client onyour computer, for either initial installation or an update.

Before you beginv You must know the location of the directory where the InfoSphere Business

Glossary Anywhere client installation files are located and you must be able toaccess them.

v You must have a user account on IBM InfoSphere Information Server with aBusiness Glossary Basic User role or higher.

About this task

You can install the InfoSphere Business Glossary Anywhere client and define userpreferences and configuration parameters. Some parameters might have beenpreconfigured by an administrator.

After the initial installation for a particular version, the client is automaticallyupdated if an interim release (such as a Fix Pack) of InfoSphere Business GlossaryAnywhere for this version of InfoSphere Business Glossary Anywhere is installedfrom the initial installation directory.

Note: If you want to install InfoSphere Business Glossary Anywhere from adifferent directory than was used for an earlier version, you must first uninstall theearlier version.

Procedure1. Copy the file file_name.zip to a directory, where file_name.zip is the name of

the file containing the InfoSphere Business Glossary Anywhere client, andextract the files. For example, for InfoSphere Business Glossary Anywhere,Version 8.5, this file is BGA_WIN_85.zip. If you are updating with an interimrelease, copy file_name.zip to the same directory from which the earlierversion was installed to take advantage of the automatic update feature.

2. Double-click BGAsetup.exe to start the installation. When the installation is

complete, an Open Book icon is displayed in your system tray.3. Right-click the Open Book icon and click Settings → Text Capture. Configure

the method that you want to use to capture text.4. Right-click the open book icon and click Settings → Server Configuration.

Configure, or update if necessary, the server name, server port, user name, andpassword. Contact your IBM InfoSphere Business Glossary administrator orIBM InfoSphere Information Server administrator for this information.


5. Click the User Preferences tab to define other user parameters. Click OK tosave the settings and close the configuration window.

6. Click the Search Items tab to define what business glossary content you wantto include in searches.

7. (Required if HTTPS is enabled.) If the IBM InfoSphere Information Server portbeing connected to uses HTTPS, the first time that you access InfoSphereBusiness Glossary Anywhere a message about HTTPS is displayed if thecertificate from the server is not trusted. If you receive such a message, thenyou must install a security certificate. One method of doing so is by followingthese steps with your Microsoft Windows Internet Explorer web browser:a. Open Windows Internet Explorer. In the address field, type the connection

information to connect to the IBM InfoSphere Business Glossary browser.Use the following format:https://host_server:port/bg.where host_server is the Server Name andport is the Server Port as configured in the Server Configuration tab of theInfoSphere Business Glossary Anywhere Settings screen.

Note: The following steps describe the procedure to follow with WindowsInternet Explorer 7.0. Other Internet Explorer versions might require slightlydifferent steps.

b. On the page that warns you about a problem with the security certificate,click Continue to this website (Not recommended.)

c. Click Certificate Error at the top of the window, then click on Viewcertificates.

d. Click the Certification Path tab.e. Click the root path that is displayed at the top of the Certification Path

window.f. Click View Certificate.g. Click Install Certificate to launch the Certificate Import Wizard.h. Follow the Certificate Import Wizard prompts, and click Finish. You can

store the certificate in any security store.i. On the Security Warning screen, click Yes to install the certificate.j. Double click on the open book icon to reopen InfoSphere Business Glossary

Anywhere and connect to the business glossary.

What to do next

To confirm that you can connect to the business glossary, double-click the OpenBook icon in your system tray.

If you have connection errors, check the log file. Each time that the client is started,a log file is created on the client computer. The name of the log file isBusinessGlossaryAnywhereyyyymmddhhmmss.log, where yyyymmddhhmmss is theyear, month, day, hour, minute, and second when the application was started. Thelog file is in the directory that has been defined in the LogFileDirectory parameterin the config.ini file. Verify with the InfoSphere Business Glossary administratorthat the server name, port number, user name, and password are correct.

You can change the text capture method, user preferences, and configurationvalues at any time by using the options available from the Settings tab.


Installing IBM InfoSphere Business Glossary Client for EclipseIBM InfoSphere Business Glossary Anywhere provides an Eclipse plug-incomponent that enables you to access business glossary content directly fromEclipse-based applications. You install this component, InfoSphere BusinessGlossary Client for Eclipse, separately from the rest of IBM InfoSphere BusinessGlossary and InfoSphere Business Glossary Anywhere.

Before you begin

Make sure that your system meets the prerequisites described for InfoSphereBusiness Glossary Client for Eclipse in the IBM InfoSphere Information Serversystem requirements.

If the InfoSphere Information Server host that you connect to uses HTTPS, yourcomputer must have a digital security certificate installed that corresponds to theInfoSphere Information Server host. The first time that you connect to the server, amessage about HTTPS is displayed if the certificate from the server is not trusted.If you receive such a message, contact your system administrator to put thecertificate in a known directory. You need access to that directory to install thecertificate on your computer.

About this task

You must copy the compressed file (.zip file) that contains the installation files forInfoSphere Business Glossary Client for Eclipse to a directory. This directorybecomes the archive site for the client.

The client consists of the Eclipse features that are described in the following table.Depending on your needs, you can install all of the features or a subset of them.

Feature name Description Feature dependencies

InfoSphere Business GlossaryCore

Users can view businessglossary from within theirEclipse-based application.The feature also includes theInfoSphere Business GlossaryClient for Eclipse Core API.

No other features required.

InfoSphere Business GlossaryUML Integration

Users can incorporate terminformation into UML modelelements, including assigningterms to model elements.

Requires InfoSphere BusinessGlossary Core feature andInfoSphere Business GlossaryUML Profile feature.

InfoSphere Business GlossaryUML Profile

Users can apply the BusinessGlossary profile to theirUML model and to viewpreexisting termassignments. Also includesthe InfoSphere BusinessGlossary Client for EclipseUML Profile API.

No other features required.

InfoSphere Business GlossaryData Model Integration

Users can incorporate terminformation into logical andphysical data modelelements, including assigningterms to model elements.

Requires InfoSphere BusinessGlossary Core feature andInfoSphere Business GlossaryUML Profile feature.



Procedure

To install a client feature:

Procedure1. Copy the file BGE_ALL_85.zip to a directory on your hard disk.

Note: If you are an administrator who is providing the client to multiple users,copy the file to a shared directory that can be accessed by all users.

2. Start the Eclipse application to which you are adding InfoSphere BusinessGlossary Client for Eclipse.

3. If you are working with Eclipse applications other than IBM InfoSphere DataArchitect or a supported Rational® Software Architect product, make sure thatyour Eclipse application is set up to install publicly available Eclipsecomponents. (These Eclipse components are provided with InfoSphere DataArchitect and supported Rational Software Architect products, so in these casesthis step is not necessary.) InfoSphere Business Glossary Client for Eclipsedepends on specific publicly available Eclipse components. If your installationof Eclipse does not include them, you might need to update the Eclipseplug-ins that correspond to your version of Eclipse. You must follow differentsteps depending on what version of Eclipse you have installed. For Eclipseversion 3.4.2, follow the instructions in step 4. For Eclipse version 3.5.1, followthe instructions in step 5. Later versions of Eclipse might have different steps tofollow.

4. Configure Eclipse to update publicly available components of Eclipse 3.4.2.a. Click Help > Software Updates....b. Click the Available Software tab.c. Click Manage Sites.d. Make sure that the Ganymede Update Site is in the list of Available

Software Sites, and checked. If the Ganymede Update Site is not in the list,click Add and enter http://download.eclipse.org/releases/ganymede inthe Location field.

e. Click OK.5. Configure Eclipse to update publicly available components of Eclipse 3.5.1.

a. Click Help > Install New Software.b. Click the Available Software Sites hyperlink. Make sure that the Galileo

Update Site is in the list of Available Software Sites, and enabled. If theGalileo Update Site is not in the list, click Add and enterhttp://download.eclipse.org/releases/galileo in the Location field.

c. Click OK.d. Make sure that Contact all update sites during install to find required

software is checked.6. Add the InfoSphere Business Glossary Client for Eclipse update site.

a. For Eclipse version 3.4.2, click Help > Software Updates... > Add Site. ForEclipse version 3.5.1, click Help > Install New Software > Add.

b. Click Archive.c. Navigate to the file BGA_ALL_85.zip. Click OK. The InfoSphere Business

Glossary Client for Eclipse features are added to the list of availablesoftware.

d. Navigate to the site you have added and expand the contents. The listexpands to include the available features.


e. Select the check boxes for each of the features you want to install. Makesure to select the check boxes for all of the dependent features. See the"Feature dependencies" column in the table in this document to ensure thatyou install all the features that you need. For example, if you want to usethe InfoSphere Business Glossary Data Model Integration feature, select thecheck boxes for the following features:v InfoSphere Business Glossary Core featurev InfoSphere Business Glossary UML Profile feature.v InfoSphere Business Glossary Data Model Integration

Note: If you are using Eclipse 3.5.1, make sure that Group items bycategory is not checked.

7. Click Install. Follow the remaining prompts to finish the installation.8. If the InfoSphere Information Server host that you connect to uses HTTPS, then

the first time that you connect to the server, a message about HTTPS isdisplayed if the certificate from the server is not trusted. If you receive such amessage, then you must install a security certificate by following these steps:a. Open Microsoft Windows Internet Explorer. In the address field, type the

connection information to connect to the IBM InfoSphere Business Glossarybrowser. Use the following format:https://host_server:port/bg

host_serverIf your installation has a separate front-end dispatcher, use the hostname of the front-end dispatcher.

If your installation does not have a separate front-end dispatcher,use the host name of the services tier computer.

port If your installation has a separate front-end dispatcher, use theHTTPS port of the front-end dispatcher if it is configured forHTTPS. Otherwise, use the HTTP port of the front-end dispatcher.

If your installation does not have a separate front-end dispatcher,use the WebSphere Application Server secure transport port ifHTTPS is configured, or use the HTTP transport port if HTTPS isnot configured.

Note: The following steps describe the procedure to follow with WindowsInternet Explorer 7.0. Other Internet Explorer versions might require slightlydifferent steps.

b. On the page that warns you about a problem with the security certificate,click Continue to this website (Not recommended).

c. Click Certificate Error at the top of the window, then click Viewcertificates.

d. Click the Details tab.e. Click Copy to File... and then click Next.f. Select Base-64 encoded X.509 (.CER) and then click Next.g. Store the certificate in any directory and then click Finish. The certificate

name with its full directory path are needed in a later step.h. In a command prompt window, go to the directory of the JRE binary that is

associated with the Eclipse application that you use (for example,InfoSphere Data Architect or IBM Rational Software Architect).


An example of the directory might be C:\Program Files\IBM\SDP\jdk\jre\bin.

i. Run the command:keytool -import -v -file "certificate_name" -keystore..\lib\security\cacerts

The file certificate_name is the certificate name with its full directory path.You must enclose the file in quotation marks (").An example of the command might bekeytool -import -v -file "C:\SSL\bge_certificate" -keystore

..\lib\security\cacerts

The keystore utility accesses the certificate and prepares to import it. Enterthe following information:1) At the Enter keystore password prompt, type changeit.2) At the Trust this certificate prompt, type Y.

The certificate is installed and added to the keystore.

Results

The features that you selected are installed.

What to do next

Validate that InfoSphere Business Glossary Client for Eclipse is installed andconfigure the client to connect to InfoSphere Business Glossary. Then review thedocumentation to learn how to use the client.

To validate that the InfoSphere Business Glossary Client for Eclipse is installed:1. Start your Eclipse application.2. From the menu bar, select Window > Preferences to see the list of available

Preference page titles.3. Check that Business Glossary is one of the Preference page titles listed in the

left pane. If it is visible, then InfoSphere Business Glossary Client for Eclipsehas been installed.

To connect to InfoSphere Business Glossary:1. Start your Eclipse application if it is not already started.2. From the menu bar, select Window > Preferences to see the list of available

Preference page titles.3. From the list of Preference page titles, click Business Glossary.4. Press F1 or click the Help icon ? to display the online help for the connection

settings page.5. Follow the instructions in the online help to fill out the connection settings.

To learn how to use the client, review the documentation by selecting Help > HelpContents > IBM InfoSphere Business Glossary Client for Eclipse.

Installing z/OS components for IBM InfoSphere DataStage MVS EditionTo compile and run IBM InfoSphere DataStage jobs on a server that runs IBMz/OS, you must first install COBOL copybook files and the Runtime Library (RTL).


Procedure

To install the components:1. Upload the COBOL copybook files to add them as members of a copybook

library (copylib). See “Installing COBOL copybook files.”2. Install the runtime library for z/OS jobs. The library contains routines that are

used when a job is run. See “Installing the runtime library for z/OS jobs” onpage 226.

3. Run the installation verification process (IVP). The IVP validates that a z/OSenvironment is configured for compiling and running z/OS jobs. See“Installation verification process for z/OS components” on page 227.

Installing COBOL copybook filesUpload the COBOL copybook files to add them as members of a copybook library(copylib).

Procedure1. Using FTP, upload the COBOL copybook files to copylib members. On the

installation media, the files are in the Mainframe Components directory.

Table 86. Copybook to copylib associations

Copy these files To these copylib members

ArdtIMSg.cob ARDTIMSG

ArdtMsg1.cob ARDTMSG1

ArdtMsg2.cob ARDTMSG2

ArdtUBgn.cob ARDTUBGN

ArdtUCod.cob ARDTUCOD

ArdtUDat.cob ARDTUDAT

ArdtUEnd.cob ARDTUEND

ArtdtUFct.cob ARDTUFCT

ArtdtuFdf.cob ARDTUFDF

RTLMsgs.cob RTLMSGS

2. In the JCL templates for compiling the COBOL program, specify the name ofthe copylib that contains the uploaded copybook files.a. Start the Designer client.b. Under the Tools menu option, edit the CompileLink, DB2CompileLinkBind,

and TDCompileLink JCL templates.c. In the SYSLIB DD statement of each COBCOMP step, specify the copylib.

Copylib membersThe copylib members for IBM InfoSphere DataStage contain message text or codetemplates that you can customize.


Message text

The following table describes copylib members that contain runtime message text.

Table 87. 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 librarygenerates

Templates

The following table describes copylib members that can control the initialization ortermination of the generated COBOL program for a job.

Table 88. Copylib members that can control the operation of generated COBOL programs

copylib member Adds

ARDTUBGN Program initialization code for the generated COBOL program.

ARDTUCOD Paragraphs to the end of the generated COBOL program.

ARDTUDAT Code before the PROCEDURE DIVISION statement of the generatedCOBOL program. For example, you can add WORKING-STORAGEvariables and a LINKAGE SECTION.

ARDTUEND Program termination code before each GOBACK statement.

ARDTUFCT Statements, such as SELECT, to the end of FILE-CONTROL paragraphin the ENVIRONMENT division.

ARDTUFDF FD statements at the end of the FILE SECTION in the DATADIVISION.

Installing the runtime library for z/OS jobsThe runtime library for z/OS jobs contains routines that are used when a job isrun.

Procedure1. Log in to the computer that runs z/OS.2. Allocate a runtime library data set.

a. In ISPF, access function 3.2 (Data Set Utility).b. In the Option line, type A.c. Tab to the Data Set Name prompt, type a data set name, and press Enter.d. In the Allocate New Data Set panel, in the Space units field, type TRKS.e. In the Allocate New Data Set panel, type the following values:

Field Value

Primary quantity 10

Secondary quantity 10

Directory blocks 0

Record format FB


Field Value

Record length 80

Block size 3120

3. Transfer the runtime library data file to the allocated runtime library data set.a. On your workstation, start FTP.b. Connect to the computer that runs z/OS and log in.c. Set the transfer mode to BIN.d. Use the PUT command to send the ArdtRTL.data file to the allocated

runtime library data set. This file contains the IBM InfoSphere DataStageruntime library in binary format.

4. On the computer that runs z/OS, receive the runtime library data set.a. Run the TSO RECEIVE command: RECEIVE INDA('input_dataset_name')

input_dataset_name is the data set that you specified in Step 2.b. At the prompt, type DA('output_dataset_name')

output_dataset_name is the name of the data set that the TSO RECEIVEcommand creates. This output data set is a sequential file that is used bythe job that you create and run in steps 5, 6, and 7.

5. Transfer the file ArdtRTL.jcl to z/OS. This file contains sample JCL to createthe runtime library.a. On your workstation, start FTP.b. Connect to the computer that runs z/OS and log in.c. Set the transfer mode to ASCII.d. Use the PUT command to send the ArdtRTL.jcl file to a member of a JCL

library.6. On the computer that runs z/OS, edit the JCL library member specified in step

5d.a. Modify the JOB statement to meet your site standards.b. In the SEQ1 statement, change the DSN value to the name of the output

data set that the TSO RECEIVE command creates in Step 4b. The outputdata set is the source data set for an IEBCOPY operation.

c. In the PDS2 statement, change the DSN value to the name of the linklibrary to contain the contents of the InfoSphere DataStage runtime library.The link library is the target for the IEBCOPY operation.

7. Submit the JCL file from the previous step to copy the data set to the linklibrary.

8. Start the Designer client.9. Edit the JCL templates for CompileLink and DB2CompileLinkBind. In the

LKED step, change the ARDTLIB DD statement to use the data set name thatyou specified in the PDS2 statement in Step 6c.

Installation verification process for z/OS componentsThe installation verification Process (IVP) validates that a z/OS environment isconfigured for compiling and running z/OS jobs.

The installation verification process uses IBM InfoSphere DataStage jobs to validatea z/OS environment.


Job Purpose

IVPFLAT Tests the runtime library.

IVPDB2 Tests connectivity to IBM DB2 for z/OS andthe runtime library.

IVPIMS Tests connectivity to the IMS database andthe runtime library.

For information about installing and running the installation verification process,see the \Utilities\Supported\IVP\IVP Installation Instructions.doc file on theinstallation media.

Installing IBM InfoSphere Blueprint DirectorIBM InfoSphere Blueprint Director is included with IBM InfoSphere InformationServer. InfoSphere Blueprint Director strengthens the alignment of business andinformation technology by enabling the business and IT teams to collaborate onactionable information blueprints that connect the business vision with thecorresponding technical metadata. InfoSphere Blueprint Director directs the team toapply best practices based on reference architectures and methodology.

Before you begin

InfoSphere Blueprint Director is supported in Microsoft Windows environments.For complete details about system requirements and compatible software, read therelease notes. The release notes are located in the same directory as the InfoSphereBlueprint Director setup program.

About this task

When you install IBM InfoSphere Information Server on a computer that isrunning Microsoft Windows, the installation program creates a directory thatcontains the InfoSphere Blueprint Director documentation and setup program. Thisdirectory is created on the client tiers and for all product modules andcomponents.

Procedure1. In the InfoSphere Information Server installation directory, locate the Blueprint

directory.2. In the Blueprint directory, locate the release notes. Follow the instructions in

the release notes to install InfoSphere Blueprint Director.

Results

InfoSphere Blueprint Director is installed.

What to do next

To learn how to configure and use InfoSphere Blueprint Director, see the help orthe IBM InfoSphere Blueprint Director User's Guide. The User's Guide is located in thesame directory as the InfoSphere Blueprint Director setup program.


Part 4. Configuring the software after installation

To finish setting up IBM InfoSphere Information Server, complete the tasks thatcorrespond to the product modules that you installed or the features that you wantto enable. For additional setup steps, see the documentation for your specificproduct modules.



Chapter 15. Firewall exceptions for client-side executable files(Windows)

In most cases, you can avoid specifying firewall exceptions by opening ports whenyou prepare a Microsoft Windows computer for installation. However, you mightprefer to set up explicit firewall exceptions for client-side executable files thatrequire network access.

For normal client use, set up firewall exceptions for the following executable files.Unless otherwise noted, the default location of these files is C:\IBM\InformationServer\Clients\Classic\.

Table 89. Firewall exceptions for normal client use

Executable file Description

admin.exe IBM InfoSphere DataStage and QualityStageAdministrator

director.exe IBM InfoSphere DataStage and QualityStageDirector

DSCompilerWizard.exe Multi-job compiler used by IBM InfoSphereDataStage and QualityStage Designer

DSDesign.exe IBM InfoSphere DataStage and QualityStageDesigner

dsviewer.exe Data set management for IBM InfoSphereDataStage and QualityStage Designer

C:\IBM\InformationServer\ASBNode\apps\jre\bin\java.exe

C:\IBM\InformationServer\ASBNode\apps\jre\bin\javaw.exe

Processes used to run Java programs. Theseprocesses are needed by all clients.

C:\IBM\InformationServer\Clients\Classic\ISC\isc.exe

Program that runs the IBM InfoSphereInformation Services Director console andIBM InfoSphere Information Analyzerconsole

C:\IBM\InformationServer\Clients\istools\manager\manager.exe

IBM InfoSphere Information Server Manager

C:\IBM\InformationServer\Clients\istools\cli\istool.bat

InfoSphere Information Server Managercommand-line interface

For stand-alone tools, set up firewall exceptions for the following executable files.The default location of these files is C:\IBM\InformationServer\Clients\Classic\.

Table 90. Firewall exceptions for stand-alone tools


diffapicmdline.exe

dsdiffexporter.exe

Compare command-line tool

dsadmin.exe Command-line administration tool

dscc.exe Command-line compiler tool

dscmdexport.exe Command-line export tool


Table 90. Firewall exceptions for stand-alone tools (continued)


dscmdimport.exe Command-line import tool

dsexport.exe Export tool

dsimport.exe Import tool

dsjob.exe Command-line job administration tool

NLVAdmin.exe Support tool for switching to English for anon-English installation

XMDICmd.exe Metadata importer utility

XMLImporter.exe

XMLMDImporter.exe

XML table definition importer


Chapter 16. Enablement of Secure Sockets Layer (SSL)

After running the installation program, you can optionally enable SSL forRMI/IIOP by using the IBM WebSphere Application Server administrative console.You can also configure your environment to use secure HTTP (HTTPS)communication with the services tier.

Enabling SSL for inbound RMI/IIOPIn IBM InfoSphere Information Server, Version 8.5, SSL for RMI/IIOP is disabledby default. After you install or upgrade to Version 8.5, you can enable SecureSockets Layer (SSL) for IBM WebSphere Application Server, Versions 6.1 and 7.0.

About this task

If you are upgrading from a previous version of InfoSphere Information Serverthat used SSL and you want to continue using SSL, you must enable SSL afterinstalling Version 8.5. If you prefer to use SSL or if your system requiresconfidentiality at the EJB level, you must enable SSL.

Remember: You must run the UpdateSignerCerts tool on all client systems whenany SSL changes occur in the cell. For example, when a certificate expires or, in acluster environment, when you add a managed node to the cell, you must run thetool on every client system.

Procedure1. Start the WebSphere Application Server processes. In a cluster environment,

ensure that all node agents are up and running.v For stand-alone installations:

– Linux UNIX Start WebSphere Application Server by running theMetadataServer.sh/bat script.

– Windows Start WebSphere Application Server by starting the MicrosoftWindows service.

For information about starting application server processes, see the IBMInfoSphere Information Server Administration Guide.

v For cluster installations, start the WebSphere Application Server deploymentmanager by running the startManager command. For information aboutstarting application server processes, see the IBM InfoSphere Information ServerAdministration Guide.

2. Log in to the WebSphere Application Server administrative console. To set upyour security settings:v For IBM WebSphere Application Server Network Deployment, Version 6.1:

a. Click Security → Secure administration, applications, and infrastructure.b. In the Authentication area, select the type of transport and the SSL

settings. Click RMI/IIOP security → CSIv2 inbound transport.c. Select the SSL settings that correspond to an SSL transport. In the General

Properties area, under Transport, select SSL-supported.v For IBM WebSphere Application Server Network Deployment, Version 7.0:

a. Click Security → Global Security.


b. In the Authentication area, select the type of transport and the SSLsettings. Click RMI/IIOP security → CSIv2 inbound communications.

c. Select the SSL settings that correspond to an SSL transport. In the CSIv2Transport Layer area, click Transport → SSL-supported.

3. Click OK and save all changes.4. Stop and restart all WebSphere Application Server processes.v For stand-alone installations, restart the WebSphere Application Server

process.v For cluster installations, restart all the WebSphere Application Server

processes in the cell by stopping all application servers, node agents, andthen the Deployment Manager. Then start the Deployment Manager, all nodeagents, and then all application servers. For more information about startingapplication server processes, see the IBM InfoSphere Information ServerAdministration Guide.

What to do next

Run the IBM InfoSphere Information Server UpdateSignerCerts tool on every clientsystem. See “Running UpdateSignerCerts after enabling SSL or changing SSL at thecell level” on page 236. You must run this tool whenever an SSL-related changeoccurs in the cell; for example, when SSL is first enabled, or a server certificateexpires, or a new managed node is added to the cluster.

Manually configuring InfoSphere Information Server components touse HTTPS

If the installation program did not configure HTTPS for a tier computer duringIBM InfoSphere Information Server installation, follow this procedure to manuallyconfigure HTTPS for that tier computer.

About this task

The services and engine tiers are properly configured for HTTPS if you selectHTTPS during the installation of these tiers. If you did not select HTTPS duringthe installation of these tiers, you can manually configure HTTPS communicationsas described in this procedure. Each client tier must be manually configured toenable HTTPS communications with the services tier.

Procedure1. (Client tier, engine tier, and services tier computers) Create an empty text file

called https.conf. Store the file in the following locations, where installdir is thelocation of your InfoSphere Information Server installation directory:

Linux UNIX

v installdir/ASBServer/conf

v installdir/ASBNode/conf

The typical installdir is /opt/IBM/InformationServer.

Windows

v installdir\ASBServer\conf

v installdir\ASBNode\conf

v

The typical installdir is C:\IBM\InformationServer.


Note: The ASBServer directory is present only if the computer hosts theservices tier.

2. (Client tier, engine tier, and services tier computers) Use the updateSignerCertscommand to install the HTTPS certificate on the computer. See “RunningUpdateSignerCerts after enabling SSL or changing SSL at the cell level” on page236.

3. (Engine tier and services tier computers) Update the port value in theVersion.xml files. These files contain the installation records that are used bythe installation program. Keeping these files current avoids problems withfuture installations. Update the following Version.xml files:v The file that is on the server that hosts the engine tierv The file that is on the server that hosts the services tierOn each server, the Version.xml file is located in the IBM InfoSphereInformation Server installation directory.Edit each file as follows:a. Use a text editor to open the Version.xml file.b. In the file, locate the following XML element:

<PersistedVariable encrypted="false" name="is.console.port"persistent="true" readonly="true" value="80"/>

c. Change the value attribute to the HTTPS port number.d. In the file, locate the following XML element:

<PersistedVariable encrypted="false" name="is.https"persistent="true" readonly="true" value="false"/>

e. Change the value attribute to true.f. In the file, locate the following XML element:

<PersistedVariable encrypted="false" name="isf.http.port"persistent="true" readonly="true" value="port" />

g. Change the value attribute to the HTTPS port number.4. (Services tier computer) Modify the registered-servers.xml file. 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. Open the file in a text editor.b. In the file, 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.xml file. Modify the port for all <asb-server> elements to reflect thesecure port for the services tier.

c. Update the port value.d. Save your changes.

5. (Engine tier computer) Modify the registered-servers.xml file. You can findthis file in the following location:

v Linux UNIX installdir/ASBNode/eclipse/plugins/com.ibm.isf.client_8.5.0.0

v Windows installdir\ASBNode\eclipse\plugins\com.ibm.isf.client_8.5.0.0

Chapter 16. Enablement of Secure Sockets Layer (SSL) 235


<asb-server name="host"host-name="host"port="9080"is-primary-server="true" />

There might be multiple <asb-server> elements in the registered-servers.xml file. Modify the port for all <asb-server> elements to reflect thesecure port for the services tier.


6. Optional: (Client tier computers) Modify the registered-servers.xml file. Thelist of servers in these files is used to populate the server lists in the loginpages for some client applications. You can update these files if you want tohave the updated port values shown on the next login attempt. Alternatively,you can enter the new value in the login page the next time you log in.However, the old host name and port continue to display in the lists in someclient application login pages unless you modify the registered-servers.xmlfile on the computer. Modify the file in either of the following ways:v Change the file in the same way that you modified the registered-

servers.xml files on the engine tier computers.

Note: On client-only computers, the is-primary-server="true" attributedoes not appear in the <asb-server> element.

v To remove old server entries, run the RegistrationCommand command asfollows:

– Linux UNIX

cd installdir/ASBNode/bin./RegistrationCommand.sh -remove -hostname host -port port

– Windows

cd installdir\ASBNode\binRegistrationCommand.bat -remove -hostname host -port port

7. (Client tier computers) Update the browser bookmarks and URL shortcuts.Change each item so it uses https:// instead of http://, and so it referencesthe HTTPS port instead of the HTTP port.

Running UpdateSignerCerts after enabling SSL or changing SSL at thecell level

To enable SSL on a computer, you must retrieve the certificate from the server. Toretrieve the certificate, run the UpdateSignerCerts tool. Also run theUpdateSignerCerts tool whenever an SSL change occurs in an IBM WebSphereApplication Server cell. Examples of changes include when server certificatesexpire or when a new managed node is added to a WebSphere Application Servercluster.


About this task

The following table describes when and where to run the UpdateSignerCerts tool.

Table 91. When and where to run the UpdateSignerCerts tool

When to run theUpdateSignerCerts tool

Where to run theUpdateSignerCerts tool

WebSphere ApplicationServer configurations

After reenabling SSL forRMI/IIOP or HTTPS for thefirst time (after a newinstallation or after anupgrade).

Client tiers, engine tiers, andservices tiers.

Stand-alone and clusterconfigurations of WebSphereApplication Server

After replacing or updating aserver certificate (forexample, when a certificateexpires).

Client tiers, engine tiers, andservices tiers


After installing a new IBMInfoSphere InformationServer client or engine tier.

New client tiers and newengine tiers (only if SSL isenabled)


After adding a new managednode to the cluster and anew custom profile is created(horizontal clustering).

Client tiers, engine tiers, andservices tiers (only if SSL isenabled)

WebSphere ApplicationServer cluster configurationonly

Procedure1. Change to the directory in which the UpdateSignerCerts tool is located. The

following table indicates the location from which to run the tool. The locationdepends upon which computer you are running it on and how WebSphereApplication Server is configured:

Computer and configuration Run UpdateSignerCerts from this location

Services tier computer, clustered WebSphereApplication Server environment

The following path on the computer thathosts the Deployment Manager:

v Linux UNIX

installdir/ASBServer/bin

v Windows installdir\ASBServer\bin

Services tier computer, non-clustered(stand-alone) WebSphere Application Serverenvironment

The following path on the services tiercomputer:

v Linux UNIX

installdir/ASBServer/bin

v Windows installdir\ASBServer\bin

Engine tier computers The following path on each engine tiercomputer:

v Linux UNIX

installdir/ASBNode/bin

v Windows installdir\ASBNode\bin


Computer and configuration Run UpdateSignerCerts from this location

Client tier computers The following path on each client tiercomputer:

v Linux UNIX

installdir/ASBNode/bin

v Windows installdir\ASBNode\bin

Metadata repository tier computer You do not need to run the tool on thiscomputer.

If the computer that hosts the services tier also has the engine tier or client tierinstalled on it, run the UpdateSignerCerts tool in both the ASBServer/bin andASBNode/bin directories on the computer.

2. Use the following command to run the UpdateSignerCerts tool.

v Linux UNIX

./UpdateSignerCerts.sh –host host_name –port port_number

v Windows

UpdateSignerCerts.bat –host host_name –port port_number

-host host_nameIf your installation has a separate front-end dispatcher, use the host nameof the front-end dispatcher.

If your installation does not have a separate front-end dispatcher, use thehost name of the services tier computer.

-port port_numberIf your installation has a separate front-end dispatcher, use the HTTPS portof the front-end dispatcher if it is configured for HTTPS. Otherwise, use theHTTP port of the front-end dispatcher.

If your installation does not have a separate front-end dispatcher, use theWebSphere Application Server secure transport port if HTTPS is configured,or the HTTP transport port if HTTPS is not configured.

Note: If HTTPS is used, the tool might prompt you to accept an HTTPScertificate. Accept the certificate to let the tool finish its tasks.If you do not specify a -host or -port value, the tool uses the following set ofdefault values. These values might or might not work, depending on yourconfiguration:

When the tool is run on a computer that hosts the services tier (other tiersmight or might not be installed on the same computer):

If the tool is run from the ASBServer/bin directory, the tool connects tothe host and port that are designated as the primary-server in theregistered-servers.xml file. This is the host and port that werespecified during the services tier or engine tier installation unless theregistered-servers.xml file was manually updated because of achange in the front-end dispatcher or a change in the HTTP or HTTPSport for the services tier.

When the tool is run on a computer that hosts an engine tier (other tiersmight or might not be installed on the same computer):

If the tool is run from the ASBNode/bin directory, the tool connects tothe host and port that are designated as the primary-server in theregistered-servers.xml file. This is the host and port that were


specified during the services tier or engine tier installation unless theregistered-servers.xml file was manually updated because of achange in the front-end dispatcher or a change in the HTTP or HTTPSport for the services tier.

When the tool is run on a client tier computer without an engine tierinstalled on the same computer:

The -host and -port values are mandatory.

Replacing WebSphere Application Server certificatesTo replace a certificate before it expires, or to use your own certificate, you canreplace an IBM WebSphere Application Server certificate by specifying a differentcertificate for each and any endpoint.

About this task

In clustered IBM InfoSphere Information Server installations, all signer certificatesmust be stored in the CellDefaultTrustStore truststore. In stand-alone InfoSphereInformation Server installations, all signer certificates must be stored in theNodeDefaultTrustStore truststore. This configuration is the default for WebSphereApplication Server.

In WebSphere Application Server, Version 6.1, when certificates expire or if thenodes are out of synchronization, you can replace a certificate by completing thesteps in the following technote: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21305596.

In WebSphere Application Server, Version 7.0, you can renew certificates.WebSphere Application Server generates a new certificate that replaces the oldcertificate. You can renew self-signed certificates and chained certificates bycompleting the steps in the following WebSphere Application Serverdocumentation: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.base.iseries.doc/info/iseries/ae/tsec_7renewcecacert.html.

Note: In these steps, you replace an expired certificate with another certificate thatis generated by WebSphere Application Server. Alternatively, you can replace acertificate with your own certificate, or you can use a certificate signed by acertificate authority. Refer to the WebSphere Application Server documentation fordetails.

Procedure1. Log in to the WebSphere Application Server administrative console.

a. In a stand-alone environment, use the MetadataServer.sh/bat script to startthe application server.

b. In a clustered environment, use the startManager command to start thedeployment manager.

2. In the WebSphere Application Server administrative console, click Security →SSL certificate and key management → Manage endpoint securityconfigurations.

3. Expand Inbound and click the node that uses the default certificate that youwant to replace.




http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.base.iseries.doc/info/iseries/ae/tsec_7renewcecacert.html



4. Click Manage certificates. You can create a self-signed certificate generated byWebSphere Application Server, receive a certificate from a certificate authority,or import an existing certificate.

5. Click Create a self-signed certificate.6. Complete the form. Specify an alias, common name, and organization for the

new certificate. Click OK and Save.7. On the Manage endpoint security configuration page, click the node again,

and then click Manage certificates to view the old and new certificates.8. Select the old certificate and click Replace.9. Select the new certificate and select the Delete old certificate and Delete old

signers check boxes. Click OK and Save.10. Stop and restart all IBM WebSphere Application Server Network Deployment

processes. For more information about restarting application server processes,see the IBM InfoSphere Information Server Administration Guide

What to do next

Run the UpdateSignerCerts tool on the client tiers, engine tiers, and services tiers.For more information, refer to “Running UpdateSignerCerts after enabling SSL orchanging SSL at the cell level” on page 236.

Switching from HTTPS back to HTTPIf your IBM InfoSphere Information Server installation is configured for secureHTTP (HTTPS), you can configure it to use HTTP instead.

Procedure1. (Client tier, engine tier, and services tier computers) Delete the https.conf files.

The files are found in the following locations, where installdir is the location ofyour InfoSphere Information Server installation directory:

Linux UNIX

v installdir/ASBServer/conf

v installdir/ASBNode/conf

The typical installdir is /opt/IBM/InformationServer.

Windows

v installdir\ASBServer\conf

v installdir\ASBNode\conf

The typical installdir is C:\IBM\InformationServer.

Note: The ASBServer directory is present only if the computer hosts theservices tier.

2. (Engine tier and services tier computers) Change the port value in theVersion.xml files. These files contain the installation records that are used bythe installation program. Keeping these files current avoids problems withfuture installations. Update these Version.xml files:v The file that is on the server that hosts the engine tierv The file that is on the server that hosts the services tierOn each server, the Version.xml file is located in the IBM InfoSphereInformation Server installation directory.Edit each file as follows:a. Use a text editor to open the Version.xml file.


b. In the file, locate the following XML element:<PersistedVariable encrypted="false" name="is.console.port"

persistent="true" readonly="true" value="port" />

c. Change the value attribute to the HTTP port to use.d. In the file, locate the following XML element:

<PersistedVariable encrypted="false" name="is.https"persistent="true" readonly="true" value="true"/>

e. Change the value attribute to false.f. In the file, locate the following XML element:


g. Change the value attribute to the HTTP port to use.3. (Services tier computer) Modify the registered-servers.xml file. You can find

this file in the following location:




<asb-server name="host"host-name="host"port="port"is-primary-server="true" />

There might be multiple <asb-server> elements in the registered-servers.xml file. Modify the port for all <asb-server> elements to reflect theHTTP port for the services tier.


4. (Engine tier computer) Modify the registered-servers.xml file. You can findthis file in the following location:





There might be multiple <asb-server> elements in the registered-servers.xml file. Modify the port for all <asb-server> elements to reflect theHTTP port for the services tier.


5. Optional: (Optional, for client tier computers) Modify the registered-servers.xml file. The list of servers in these files is used to populate the serverlists in the login windows for some client applications. You can update these


files if you want to have the updated port values shown on the next loginattempt. Alternatively, you can enter the new value in the login window thenext time you log in. However, the old host name and port are still listed insome client application login windows unless you modify theregistered-servers.xml file on the computer. Modify the file in either of thefollowing ways:v Change the file in the same way that you modified the registered-


Note: On client-only computers, the is-primary-server="true" attribute isnot included in the <asb-server> element.

v To remove old server entries, run the RegistrationCommand command asfollows:

– Linux UNIX

cd installdir/ASBNode/bin./RegistrationCommand.sh -remove -hostname host -port port

– Windows

cd installdir\ASBNode\binRegistrationCommand.bat -remove -hostname host -port port

6. (Client tier computers) Update the browser bookmarks and URL shortcuts.Change each item so it uses http:// instead of https://, and so it includes theHTTP port instead of the HTTPS port.


Chapter 17. Configuring security for IBM InfoSphereInformation Server

To configure security, choose a user registry configuration, set up the registry,create users, and assign security roles to those users. If the user registryconfiguration that you choose cannot be shared between the services tier andengine tier, also map credentials between the user registry that is used byInfoSphere Information Server and the user registry that is used by the engine.Some suite components also require that you assign project-specific roles to users.Optionally, also enable Secure Sockets Layer (SSL) communication, configure IBMWebSphere Application Server or InfoSphere Information Server agents fornon-root administration, and configure the Auditing service.

About this task

The following list outlines the tasks that you do to set up security for IBMInfoSphere Information Server. For details on doing each task, refer to the IBMInfoSphere Information Server Administration Guide.

Procedure1. Choose a user registry and configure it for InfoSphere Information Server. A

user registry contains valid user names and passwords. To log in to InfoSphereInformation Server, a user must have a user name and password in the userregistry. The installation program configures InfoSphere Information Server touse its internal user registry. As part of security setup, you can configureInfoSphere Information Server to use an external user registry such as the localoperating system user registry or a Lightweight Directory Access Protocol(LDAP) user registry.

2. Create users and groups in the user registry. If InfoSphere Information Server isconfigured to use the internal user registry, create users and groups by usingthe InfoSphere Information Server console or the InfoSphere Information ServerWeb console. If InfoSphere Information Server is configured to use an externaluser registry, use standard operating system utilities or user registry utilities.

3. Assign security roles to users and groups. Security roles determine which suitecomponents each user or group has access to and what level of access that useror group has in the suite component.

4. Configure InfoSphere Information Server engine security. The InfoSphereInformation Server engine performs user authentication separately from otherInfoSphere Information Server components. Depending upon your user registryconfiguration, you might have to map credentials between the InfoSphereInformation Server user registry and the local operating system user registry onthe computer where the engine is installed.

5. Assign project roles to users. Assign project roles if required by the installedsuite components.

6. Optional: Enable Secure Sockets Layer (SSL) communication. After running theinstallation program, you can optionally enable SSL for RMI/IIOP by using theWebSphere Application Server administrative console. If the installationprogram did not configure a tier for HTTPS, you can also configure the tier byusing a manual procedure.

7. Optional: Configure IBM WebSphere Application Server for non-rootadministration. By default, WebSphere Application Server runs as root.


However, it can also be run by using a non-root user ID. You can configure andset appropriate file system permissions for WebSphere Application Server to"run-as" a non-root user ID.

8. Optional: Configure InfoSphere Information Server agents for non-rootadministration. By default, the InfoSphere Information Server agents (such asthe ASB and logging agents) run as root. However, they can also be run byusing a non-root user ID. You can configure and set appropriate file systempermissions for the agents to "run-as" a non-root user ID.

9. Optional: Configure the Auditing service. The Auditing service creates an audittrail of security-related events. These events include all security-related settingschanges and user login and logout operations. You can configure which auditevents to log and how much information to include based on your auditingrequirements.


Chapter 18. Configuring product modules in the suite

Depending on which products you installed or the tasks that you want tocomplete, you must complete some configuration tasks.

Configuring IBM InfoSphere DataStage and IBM InfoSphereQualityStage

Before you use IBM InfoSphere DataStage and IBM InfoSphere QualityStage, youmust perform several configuration tasks.

Procedure

Do the following tasks to configure and administer IBM InfoSphere DataStage andIBM InfoSphere QualityStage.1. Configure security. Choose a user registry configuration, set up the registry,

create users, and assign security roles to those users. If the user registryconfiguration that you choose cannot be shared between the services tier andengine tier, also map credentials between the user registry that is used byInfoSphere Information Server and the user registry that is used by the engine.Also assign project-specific roles to users. See Chapter 17, “Configuring securityfor IBM InfoSphere Information Server,” on page 243.

2. Linux UNIX Ensure that InfoSphere DataStage users have the correctlocalization settings. If you installed globalization support (NLS), ensure thatIBM InfoSphere DataStage users have the correct settings specified forlocalization.

3. Configure access to ODBC data sources. Configure the ODBC drivers to accessODBC data sources. The drivers are installed with the client tier or the enginetier.

4. Windows Optional: Tune the server engine. For systems that have largenumbers of simultaneously connected users or large numbers of simultaneouslyrunning jobs, configure the server engine to support the required number ofopen files, lock table entries, and locks that are necessary for correct engineoperation. To tune the engine, modify settings in the uvconfig file. See “Tuningthe InfoSphere Information Server engine for large numbers of users or jobs(Windows Server)” on page 252.

5. Optional: Configure the parallel processing environment. Add computers toshare engine processing. Set environment variables for the parallel engine, andconfigure the parallel engine. Configure database connectivity. See Chapter 19,“Configuring a parallel processing environment,” on page 261.

6. Optional: Migrate jobs. Migrate jobs that you created in an earlier version ofInfoSphere DataStage to the current version.

7. Optional: Configure the IBM InfoSphere QualityStage Match Designer. If youintend to develop InfoSphere QualityStage matches, ensure that a new orexisting supported database is available to receive test pass results for theMatch Designer. The IBM InfoSphere QualityStage Match Designer requires anODBC data source name (DSN) to connect to the database where the MatchDesigner stores match pass results. See “Configuring IBM InfoSphereQualityStage Match Designer” on page 253.


8. Optional: Set up the application server to run SQA or investigation reports. Theinvestigation reports and Standardization Quality Assessment (SQA) reportscan read data from a sequential file or a database table. You must set up theapplication server to find the applicable data source. See “Setting upapplication servers to run SQA or investigation reports” on page 253.

9. Test the installation. After you install and configure InfoSphere DataStage andInfoSphere QualityStage, test the installation by logging in to the Administratorand Designer clients. See “Testing the installation of IBM InfoSphereQualityStage and IBM InfoSphere DataStage” on page 254.

Ensuring that InfoSphere DataStage users have the correctlocalization settings (Linux, UNIX)

In Linux or UNIX, if you installed globalization support (NLS), ensure that IBMInfoSphere DataStage users have the correct settings specified for localization.

About this task

On most systems, the locale for individual users is set by using a system-widedefault. For example, on Linux systems, this default is defined in/etc/sysconfig/i18n. If the user who performed the installation used this defaultand all InfoSphere DataStage users are expected to inherit the same default, thenyou do not need to perform the steps that are described in this task.

However, in some cases, the locale that is set for an InfoSphere DataStage usermight be different from the locale that was set during installation. For example,this problem might occur if the user who performed the installation used a localethat was not the default, or if a user set a private locale (for example, in their$HOME/.profile).

To ensure that InfoSphere DataStage users have the correct locale and environmentsettings, you can edit the environment variables in the dsenv file. The environmentvariables in the dsenv file affect the entire InfoSphere DataStage environment. Todefine the environment variables on a per-project or per-job basis, use the IBMInfoSphere DataStage and QualityStage Administrator client or the IBM InfoSphereDataStage and QualityStage Designer client.

Perform this task as soon as possible after installation, before any jobs are stored orcompiled.

Procedure1. Log in to the operating system as the user who ran the installation program.2. Determine the locale and encoding name to use. The encoding must correspond

to one of the encodings that InfoSphere DataStage supports. See “Characterencodings supported by IBM InfoSphere Information Server” on page 158.The table gives the names of encodings as they appear to the InfoSphereInformation Server engine. The encoding names for the operating system mightbe slightly different. You must use the operating system-specific name for theencoding. For example, for ISO8859-1, use iso8859_1. See your operatingsystem documentation for more information.To determine the current locale that is set for the server operating system, usethe locale command:locale


3. Locate the following section in the dsenv file. By default, this file is located in/opt/IBM/InformationServer/Server/DSEngine.#LANG="langdef";export LANG#LC_ALL="langdef";export LC_ALL#LC_CTYPE="langdef";export LC_CTYPE#LC_COLLATE="langdef";export LC_COLLATE#LC_MONETARY="langdef";export LC_MONETARY#LC_NUMERIC="langdef";export LC_NUMERIC#LC_TIME="langdef";export LC_TIME#LC_MESSAGES="langdef"; export LC_MESSAGES

4. Replace the occurrences of langdef with the locale and encoding name that werespecified during installation. For example, the following settings specify thatthe locale is ja_JP and the encoding is UTF-8:LANG="ja_JP.utf8";export LANGLC_ALL="ja_JP.utf8";export LC_ALLLC_CTYPE="ja_JP.utf8";export LC_CTYPELC_COLLATE="ja_JP.utf8";export LC_COLLATELC_MONETARY="ja_JP.utf8";export LC_MONETARYLC_NUMERIC="ja_JP.utf8";export LC_NUMERICLC_TIME="ja_JP.utf8";export LC_TIMELC_MESSAGES="ja_JP.utf8"; export LC_MESSAGES

5. Remove the comment marker (#) that is at the beginning of each line. Save thefile.

6. Restart the InfoSphere Information Server engine.

What to do next

Before performing any work from the InfoSphere DataStage command line,InfoSphere DataStage users must issue the following command:. $DSHOME/dsenv

Configuring access to ODBC data sourcesYou can configure ODBC access on Windows, Linux, and UNIX operating systems.

Configuring ODBC access (Linux, UNIX)If you installed Linux or UNIX ODBC drivers, you must configure the drivers toaccess ODBC data sources.

The DataDirect Technologies Connect ODBC drivers are installed ininstall_home/Server/branded_odbc. Documentation for configuring the ODBCdrivers is provided within this directory tree.

Edit the dsenv, odbc.ini, and uvodbc.config files to set up access to ODBC datasources.

Non-wire protocol drivers require different setup information from wire drivers.Non-wire drivers require information about the location of the database clientsoftware. Wire protocol drivers require information about the database itself.

For information about configuring the ODBC environment for a specific database,see the DataDirect Connect and Connect XE for ODBC Reference manual (a PDF file)in the $DSHOME/Server/branded_odbc/books/odbc directory. Also review theodbcread.me file in the branded_odbc directory and an HTML file in thebranded_odbc/odbchelp directory.

Configuring the dsenv file: Linux UNIX

Chapter 18. Configuring product modules in the suite 247

The dsenv file contains a series of shell arguments that are used when the enginestarts. Interactive users, other programs, and scripts can use the dsenv file. Forsome ODBC connections, plug-ins, and connectors, and for interactions withexternal applications such as IBM WebSphere MQ, you must add environmentvariables to enable interactive use of ODBC drivers to make a connection to anODBC data source. This lets IBM InfoSphere DataStage inherit the correctenvironment for ODBC connections.

Before you begin

You must be logged in as an InfoSphere DataStage administrator with theoperating system credentials on the server for the InfoSphere DataStageadministrator.

Back up the dsenv file before you edit it.

For a connection that uses a wire protocol driver, you do not have to modify thedsenv file.

Procedure

1. Edit the dsenv file. The file is located in $DSHOME/DSEngine. $DSHOME identifiesthe InfoSphere DataStage installation directory. The default directory is/opt/IBM/InformationServer/Server/DSEngine.

2. Specify the following information in the dsenv file:v Environment variables for the database client softwarev Database home locationv Database library directory

Table 92. Names of the library path environment variable, 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. Theentries vary slightly depending on your operating system. See the data sourcedocumentation for more information.

Sybase 11LANG=export LANGSYBASE=/export/home/sybase/sybaseexport SYBASELD_LIBRARY_PATH=$LD_LIBRARY_PATH:$SYBASE/lib:/usr/lib:/libexport LD_LIBRARY_PATH

Informix® XPS 9.3INFORMIXDIR=/space/informixexport INFORMIXDIRINFORMIXSERVER=solnew2.1export INFORMIXSERVERONCONFIG=onconfig.solnew2export ONCONFIGLD_LIBRARY_PATH=$LD_LIBRARY_PATH:$INFORMIXDIR/lib:$INFORMIXDIR/lib/


esql:$INFORMIXDIR/lib/cliexport LD_LIBRARY_PATHLANG=Cexport LANG

DB2 Version 9.5DB2DIR=/opt/IBM/db2/V9.5export DB2DIRDB2INSTANCE=db2inst1export DB2INSTANCEINSTHOME=/export/home/db2inst1export INSTHOMEPATH=$PATH:$INSTHOME/sqllib/bin:$INSTHOME/sqllib/adm:

$INSTHOME/sqllib/miscexport PATHLD_LIBRARY_PATH=$LD_LIBRARY_PATH:$INSTHOME/sqllib/libexport LD_LIBRARY_PATHTHREADS_FLAG=nativeexport THREADS_FLAG

3. Save your changes.4. Stop and restart the IBM InfoSphere Information Server engine. See Chapter 20,

“Stopping and starting the server engine,” on page 287.

Configuring the odbc.ini file: Linux UNIX

The odbc.ini file must provide information about connecting to all the databasesand database client applications that you use.

The /opt/IBM/InformationServer/Server/branded_odbc/IBM_Tools directorycontains example odbc.ini files for each supported Linux and UNIX platform. Usethe contents of these files to create the odbc.ini file for the $DSHOME directory.

Create a soft link for the .odbc.ini file to point to the odbc.ini file. In the<installation-directory>/Server/DSEngine folder, use the command: ln -sodbc.ini .odbc.ini

Specifying data source names in the uvodbc.config file: Linux UNIX

The uvodbc.config file must specify the ODBC data source name (DSN) for eachdatabase.

About this task

There are several copies of the uvodbc.config file:v A copy is in the $DSHOME directory.v A copy of the uvodbc.config file is also in each project directory. For example,

the default path for projects on Linux is /opt/IBM/WDIS/Server/Projects.

By default, IBM InfoSphere DataStage searches the current project directory for auvodbc.config file and, if it finds one, uses this file instead of $DSHOME. This filearrangement allows you to configure data sources that are known to some projectsbut not others.

Procedure

1. Use this syntax to add entries to the uvodbc.config file:<DSN_name>DBMSTYPE = ODBC


where DSN_name is the ODBC DSN. This name must be the same name that isspecified in the .odbc.ini file. The space on each side of the equal sign isrequired.In the uvodbc.config file, comment lines begin with a number sign (#).Comments that are not in the comment block at the top of the file causeprocessing errors. Add comments only to the comment block that is at the topof the uvodbc.config file.The following example shows a typical uvodbc.config file:[ODBC DATA SOURCES]<localuv>DBMSTYPE = UNIVERSEnetwork = TCP/IPservice = uvserverhost = 127.0.0.1<Sybase1>DBMSTYPE = ODBC<Sybase2>DBMSTYPE = ODBC<Oracle8>DBMSTYPE = ODBC<Informix>DBMSTYPE = ODBC<DB2>DBMSTYPE = ODBC

2. If you alter uvodbc.config after creating projects, copy the edited file to theproject directories.

Creating and binding a DB2 package to a data source name: Linux UNIX

To use a DB2 package, you must bind it to each DB2 data source name (DSN).

Procedure

1. Open a terminal window, and change to the $DSHOME/../branded_odbc/bindirectory.

2. Type this command:bind22 dsn

where dsn is the ODBC data source name.3. Specify your user ID and password, if you are prompted to provide them.

Configuring other ODBC drivers: Linux UNIX

You can use ODBC drivers from other vendors to connect to data sources. Youmight be required to connect to a database not supported by the DataDirect driverpack, for example, Red Brick®. You can use only one ODBC Manager at a time. Asa result, you cannot use drivers from other vendors at the same time that you usethe IBM InfoSphere DataStage drivers, and you must perform some reconfigurationto switch between the two types.

Procedure

1. Install the ODBC manager and drivers. Use the documentation that the drivervendor provides.

2. Configure the computer to connect to the driver.a. In the dsenv file, add the required environment variables.


b. In the odbc.ini file, set up the connection to the database or to the databaseclient application. You must specify the Data Source Name (DSN), drivername, and login information.

c. In the uvodbc.config file, specify the DSN to use to connect to the database.3. Include the shared library libodbc.sl for the ODBC Manager in the InfoSphere

DataStage load library path. (On HP-UX, the suffix is so.) Edit the dsenv fileand ensure that the path to the ODBC Manager precedes the path to$DSHOME/../branded_odbc/lib in the shared library path environment variable.

4. After you install and configure the driver, test the connectivity.

Results

To use the DataDirect drivers again, reverse the procedure in Step 3 and ensurethat the InfoSphere DataStage ODBC driver library precedes any other ODBCdriver libraries.

Testing ODBC driver connectivity: Linux UNIX

After you configure ODBC connectivity, test the configuration to verify yourconnection to the data source.

Procedure

To test the connectivity of the ODBC connections that you defined for IBMInfoSphere DataStage:1. Change directories to $DSHOME and set up the environment by running the

following command:. ./dsenv

2. Enter this command to start the IBM InfoSphere Information Server engineshell:./bin/dssh

3. Enter this command to log in to the project:LOGTO project_name

where project_name is case-sensitive.4. Enter this command to obtain a list of available data source names:

DS_CONNECT

5. Enter this command to test the connection:DS_CONNECT dsn

where dsn is the data source name of the connection to test.6. Enter your user name and password to connect to the specified database.7. Enter .Q to quit the connection.

Configuring ODBC access (Microsoft Windows)If you installed ODBC drivers, you must configure the drivers to access ODBCdata sources. See your ODBC driver vendor documentation for information abouthow to configure the driver.

The DataDirect Technologies Connect ODBC drivers are installed ininstall_home\ODBCDrivers. Documentation for configuring the ODBC drivers isprovided within this directory tree.


Tuning the InfoSphere Information Server engine for largenumbers of users or jobs (Windows Server)

For Microsoft Windows Server systems that have large numbers of simultaneouslyconnected users or large numbers of simultaneously running jobs, you canconfigure the tIBM InfoSphere Information Server engine to support the number ofopen files, lock table entries, and locks that are necessary for correct engineoperation. To tune the engine, modify settings in the uvconfig file.

Before you beginv Back up the uvconfig file. By default, this file is located in the following

directory: C:\IBM\InformationServer\Server\DSEngine.v Stop all IBM InfoSphere DataStage jobs and ask all users to log out of

InfoSphere DataStage.

About this task

For new installations of IBM InfoSphere Information Server, change the settingsdescribed in this task if you are configuring production systems that have 80 ormore simultaneously connected users or 50 or more simultaneously running jobs.

For existing installations, change these settings if you encounter resource problemswhile running InfoSphere DataStage jobs.

Procedure1. Perform the following steps to verify that no InfoSphere DataStage jobs or

osh.exe processes are running on the server and that no connections are active:a. From the Microsoft Windows Task Manager, click the Processes tab, and

then click the Image Name column to sort the process list by name.b. Verify that the Show processes from all users check box is selected.c. In the list of processes, verify that the following processes are not running:

uvsh.exe and osh.exe. If these processes are not running, there are noInfoSphere DataStage jobs running on the server.

d. In the list of processes, verify that the following processes are not running:dsapi_server.exe and dsapi_slave.exe. If these processes are not running,there are no active InfoSphere DataStage connections.

2. Stop the InfoSphere Information Server engine. See Chapter 20, “Stopping andstarting the server engine,” on page 287.

3. Use a text editor to edit the uvconfig file. By default, this file is located in thefollowing directory: C:\IBM\InformationServer\Server\DSEngine. Specify thefollowing settingsMFILES 200T30FILES 300RLTABSZ 300MAXRLOCK 299

4. Save the uvconfig file. Make sure that you do not save the file with a .txtextension. The uvconfig file cannot have a file extension.

5. From the Windows command prompt, change to the directory that contains theuvconfig file. For example, change to the following directory:C:\IBM\InformationServer\Server\DSEngine

6. Issue the following command to regenerate the binary uvconfig file:bin\uvregen.exe

7. Restart the InfoSphere Information Server engine.


Configuring IBM InfoSphere QualityStage Match DesignerThe IBM InfoSphere QualityStage Match Designer requires an ODBC data sourcename (DSN) to connect to the database where the Match Designer stores matchpass results.

Before you begin

Designate a new or existing IBM DB2 database, Oracle database, or Microsoft SQLServer database dedicated to the storage of Match Designer output. See Chapter 11,“Preparing for the IBM InfoSphere QualityStage Match Designer database,” onpage 161.

Procedure1. On each client tier and engine tier computer, define a System DSN that points

to the Match Designer database. The ODBC DSN must have the same name oneach computer. You might want to select from the set of IBM Wire ProtocolODBC drivers installed as part of the IBM InfoSphere Information Serverenvironment. These drivers are convenient because their functionality does notdepend on the presence of any additional database-specific client software.

2. On each client tier computer, open the Match Designer and run a TestEnvironment Update for your match specification. When you run this function,the connection to the Match Designer database is established and yourencrypted credentials are retained.

Setting up application servers to run SQA or investigationreports

The investigation reports and Standardization Quality Assessment (SQA) reportscan read data from a sequential file or a database table. You must set up theapplication server to find the applicable data source.

Procedure1. If the stage writes the report data to a sequential file, perform the action that

corresponds to the topology of your installation.

Topology Action

v IBM InfoSphere Information Server engineand the services tier are on the samecomputer.

No additional steps are necessary.

v InfoSphere Information Server engine andthe services tier are on differentcomputers.

The sequential file exists only on the engine.Because the reports run on the applicationserver, perform one of the following steps:

v Create a network shared directory thatboth the engine and application server canaccess.

v Copy the sequential file from the enginetier computer to the local file system ofthe services tier. Ensure that the file pathsare identical on both the engine tiercomputer and the services tier computer.

2. If the stage writes the report data to a database table, perform the action thatcorresponds to the topology and operating system of your installation.


Topology and operating system Action

v Microsoft Windows

v InfoSphere Information Server engine andthe services tier are on the same computer

No additional steps are necessary.

The reports run on the application server.They can find the database table by usingthe Open Database Connectivity (ODBC)data source name (DSN) that was set up onthe engine.

v UNIX or Linux

v InfoSphere Information Server engine andthe services tier are on the same computer

Because the ODBC DSN is not visible to theengine as the system DSN, perform thefollowing steps:

1. Set up the Java Database Connectivity(JDBC) data source on the applicationserver.

2. Ensure that the Java Naming andDirectory Interface (JNDI) name is thesame as the ODBC DSN on the engine.

v Microsoft Windows, UNIX, or Linux

v InfoSphere Information Server engine andthe services tier are on differentcomputers

Because the necessary ODBC drivers are notinstalled on the application server, performthe following steps:

1. Set up the JDBC data source on theapplication server.

2. Ensure that the JNDI name is the sameas the ODBC DSN on the engine.

For more information about configuring JDBC data sources, see the IBMWebSphere Application Server documentation:v "Configuring a JDBC provider and data source" in the WebSphere

Application Server , Version 6.1 Information Center: publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.base.doc/info/aes/ae/tdat_tccrtprovds.html

v "Configuring a JDBC provider and data source" in the WebSphereApplication Server , Version 7.0 Information Center: publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.base.doc/info/aes/ae/tdat_tccrtprovds.html

Testing the installation of IBM InfoSphere QualityStage andIBM InfoSphere DataStage

After you install and configure InfoSphere DataStage and InfoSphere QualityStage,test the installation by logging in to the Administrator and Designer clients.

Before you begin

To run these tests, especially to connect to the IBM InfoSphere DataStage andQualityStage Designer client, you must be either an InfoSphere DataStageadministrator or a lower-level user with specific project access granted by anadministrator (in the Administrator client).

If the services and engine tier do not share a user registry, then you must set upcredential mapping. For more information, refer to the IBM InfoSphere InformationServer Administration Guide.

Procedure1. Start the IBM InfoSphere DataStage and QualityStage Administrator client:


http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.base.doc/info/aes/ae/tdat_tccrtprovds.html






a. On the computer where you installed the Administrator client, click Start →All Programs → IBM InfoSphere Information Server → IBM InfoSphereDataStage and QualityStage Administrator.

b. Use your suite credentials to log in to the Administrator client.c. When you are prompted for the server where the services tier is installed,

select a URL in the Host name of the services tier list. If the URL is not inthe list, type the URL into the field. The URL is in the formserver_name:port_number. The server name and port values depend onwhether IBM WebSphere Application Server clustering is set up within yourservices tier configuration and whether the services tier and engine tier areconfigured to use secure HTTP (HTTPS).

Table 93. Host and port values for different configurations

WebSphereApplication Serverconfiguration Host value

Port value (HTTPprotocol)

Port value (HTTPSprotocol)

WebSphereApplication Serverclustering is set up

The host name orIP address of thefront-enddispatcher (eitherthe Web server orthe load balancer).Do not use the hostname of aparticular clustermember.

HTTP port of thefront-end dispatcher(for example, 80).Do not use the portnumber of aparticular clustermember.

HTTPS secure port of thefront-end dispatcher (forexample, 443). Do not usethe port number of aparticular cluster member.

Clustering is not setup

The host name orIP address of thecomputer whereWebSphereApplication Serveris installed.

HTTP transportport (configured asWC_defaulthost inWebSphereApplication Server).Default: 9080

HTTPS transport secureport (configured asWC_defaulthost_secure inWebSphere ApplicationServer). Default: 9443

d. Select the engine server name in the Host name of the Information Serverengine list, or type it into the field if it is not in the list.

2. Start the IBM InfoSphere DataStage and QualityStage Designer client:a. On the computer where you installed the Designer client, click Start → All

Programs → IBM InfoSphere Information Server → IBM InfoSphereDataStage and QualityStage Designer.

b. Use your suite credentials to log in to the Designer client.c. When you are prompted for the server where the services tier is installed,

select a URL in the Hostname of the services tier list. If the URL is not inthe list, type the URL into the field. The URL is in the formserver_name:port_number. Use the same server name and port number thatyou used in the previous step.

d. When you are prompted for the server and project, select the server andproject in the Project list. If the values are not in the list, type them into thefield. Specify the server and project as follows: server_name/project_name.For example, if the engine is installed on the xyz server (in a non-clusteredapplication server configuration) and the project is named my-project, typexyz/my-project.


Testing the IBM InfoSphere Information Services Director installationAfter you install and configure IBM InfoSphere Information Services Director, testthe installation.

Before you begin

You must have suite administrator credentials or have already set up credentialsthat have user authority.

Procedure1. Start the IBM InfoSphere DataStage and QualityStage Administrator client:

a. On the computer where you installed the InfoSphere Information ServicesDirector client, click Start → All Programs → IBM InfoSphere InformationServer → IBM InfoSphere Information Server console.

b. Log in to the console with credentials that have the Information ServicesDirector Administrator role or suite administrator credentials.

c. When you are prompted for the server where the services tier is installed,select a URL in the Host name of the services tier list. If the URL is not inthe list, type the URL into the field. The URL is in the formserver_name:port_number. The server name and port values depend onwhether IBM WebSphere Application Server clustering is set up within yourservices tier configuration and whether the services tier and engine tier areconfigured to use secure HTTP (HTTPS).

Table 94. Host and port values for different configurations

WebSphereApplication Serverconfiguration Host value

Port value (HTTPprotocol)

Port value (HTTPSprotocol)

WebSphereApplication Serverclustering is set up

The host name orIP address of thefront-enddispatcher (eitherthe Web server orthe load balancer).Do not use the hostname of aparticular clustermember.

HTTP port of thefront-end dispatcher(for example, 80).Do not use the portnumber of aparticular clustermember.

HTTPS secure port of thefront-end dispatcher (forexample, 443). Do not usethe port number of aparticular cluster member.

Clustering is not setup

The host name orIP address of thecomputer whereWebSphereApplication Serveris installed.

HTTP transportport (configured asWC_defaulthost inWebSphereApplication Server).Default: 9080

HTTPS transport secureport (configured asWC_defaulthost_secure inWebSphere ApplicationServer). Default: 9443

2. Expand the Enabling Information Services section in the Getting Started paneto begin deploying integration logic as services, cataloging and registeringservices, and setting up credentials.

Configuring IBM InfoSphere Information AnalyzerBefore you use IBM InfoSphere Information Analyzer, you must perform severalconfiguration tasks.


Before you begin

You must have Information Analyzer Data Administrator authority.

About this task

Do the following high-level tasks to initially configure and administer this productmodule.

For detailed information about analysis configuration, see the IBM InfoSphereInformation Analyzer User's Guide.

Procedure1. On the computer that hosts the engine, define the Data Source Name (DSN) to

the analysis database and source databases. On Windows, the DSN must be asystem DSN. To avoid additional changes to the DSN information, validatethe DSNs before you do the next step.

2. Verify the credentials that are used to connect to the IBM InfoSphereInformation Server engine. You can validate the settings in the IBM InfoSphereInformation Server console, in the Home → Configuration → Analysis Settings→ Analysis Engine tab.

3. Verify the credentials that are used to connect to the analysis database. Youcan validate the settings in the IBM InfoSphere Information Server console, inthe Home → Configuration → Analysis Settings → Analysis Database tab. Forthe analysis database, match this DSN to the name that you defined in step 1.

4. In the IBM InfoSphere Information Server console, change values as needed inthe Home → Configuration → Analysis Settings → Analysis Settings tab.This step completes the global settings for InfoSphere Information Analyzer.When you create new InfoSphere Information Analyzer projects, they inheritthese global settings.

5. Verify the credentials that are used to connect to the source databases byusing the source DSNs that are defined in step 1.a. Open Home → Configuration → Sources.b. Select the host, and click Add data source.c. Provide the data source name, the data connection name, and the

connector to use.d. Match the source DSN with one of the available DSNs that are listed in the

Connection String field.e. Click Connect, and save the connection information.

6. Import metadata into the metadata repository.7. Create an InfoSphere Information Analyzer project and provide basic project

details.8. On the Overview menu in the console, select Project Properties.9. In the Analysis Engine, Analysis Database, and Analysis Settings tabs, you

can set project-specific settings by performing the tasks that are described insteps 2 through 4.

10. In the Project Properties tab, associate the imported metadata with theproject.

11. Modify the project and data source analysis settings.12. Set up security for the project.13. Customize the project dashboard.


Configuring IBM InfoSphere Business GlossaryYou must configure some settings before you start using InfoSphere BusinessGlossary.

Before you begin

The IBM InfoSphere Information Server suite administrator must assign securityroles to glossary users.

About this task

You can configure InfoSphere Business Glossary to suit the needs of yourorganization. Most configuration tasks are optional. Most of them are performedby the Business Glossary Administrator.

Procedure

The configuration tasks are as follows:1. Required: Assign security roles to glossary users. This must be done by the

InfoSphere Information Server suite administrator.2. Configure general settings. From the Edit Settings page in the InfoSphere

Business Glossary administrative interface, you can configure items such as thefollowing:v The content of the display page when users log in to InfoSphere Business

Glossaryv An e-mail address to which users can send feedbackv Whether a property name is displayed if its value is undefinedv Restrict which terms are displayed based on their status, such as "accepted"

or "deprecated "v The order in which parts of user names are listed in relevant displaysv Whether a history of changes to terms is displayedv Whether integration with Cognos® 8 Go! is enabled

3. Configure viewing permissions. This allows you to restrict the access ofselected glossary users to some glossary content.

4. Configure support for right-to-left reading languages (bidirectional languagesupport).

Configuring IBM InfoSphere Metadata WorkbenchTo use IBM InfoSphere Metadata Workbench, the suite administrator must assignroles to IBM InfoSphere Metadata Workbench users and administrators.

Procedure

To assign roles to users and administrators, refer to the IBM InfoSphere InformationServer Administration Guide.

Configuring IBM InfoSphere FastTrackTo use InfoSphere FastTrack, the suite administrator must create InfoSphereFastTrack administrator and InfoSphere FastTrack user IDs.


Procedure

For more information, see the IBM InfoSphere FastTrack documentation.



Chapter 19. Configuring a parallel processing environment

Some tasks are required to configure the parallel engine, and some tasks ensure theparallel engine is running smoothly. A well-performing parallel engine requiresmonitoring and adjustment to various settings, such as network, processor, andkernel parameter settings.

Adding computers to share engine processingTo configure an MPP system that runs the parallel engine on multiple computers,copy the parallel engine components to each computer. Then configure the parallelengine on each computer.

Before you begin

Each user who runs parallel jobs must have rsh or ssh access to each computerwhere the parallel engine components are copied.

Configuring a computer to be a processing node for MPP(Linux, UNIX)

After you have copied the parallel engine to each computer that is a member ofthe MPP environment, you must configure the computer to act as a processingnode.

Procedure

Repeat this procedure for each Linux or UNIX computer that is to be a parallelprocessing node in your environment.1. 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. See“Configuring remote and secure shells (Linux, UNIX).”

2. Set user privileges to run parallel jobs. See “Setting user privileges to runparallel jobs (Linux, UNIX)” on page 264.

Configuring remote and secure shells (Linux, UNIX)You must configure the parallel engine to run the remote shell (rsh) or the secureshell (ssh) without a password on all processing nodes that run parallel jobs.

Configuring the parallel engine to use the secure shell (ssh) program (Linux,UNIX):

The secure shell (ssh) program provides strong authentication and securecommunications between computers on a network.

Before you begin

Ensure that ssh servers are installed on all of the computers where the parallelengine runs.


About this task

When you configure ssh to work with the parallel engine, the engine connectsfrom the primary computer to all of the other computers, using RSA public keyencryption for authentication. This task must be completed for each user that runsparallel jobs. It is also necessary to log in to each computer before it can runparallel jobs. In the following steps, the primary computer is the computer thatcontains the IBM InfoSphere Information Server engine. The secondary computersare the other computers that contain parallel engines.

Procedure

1. On the primary computer, run the following command to create public andprivate encryption keys. Press the Enter key twice when you run the command.ssh-keygen –b 1024 -t rsa -f ~/.ssh/id_rsa

The keys are saved in the ~/.ssh/id_rsa directory.2. If the user home directories are not automatically mounted, run the following

commands to send the public key to the other computers. Run scp for eachuser on each secondary computer.cd ~/.sshscp id_rsa.pub user@secondary_computer:~/.ssh

3. Log in to each of the secondary computers and add the public key to the list ofauthorized keys. This process must be repeated for each user that runs paralleljobs.cd .sshcat id_rsa.pub > authorized_keys2chmod 640 authorized_keys2rm -f id_rsa.pub

The file that contains the authorized keys might be called authorized_keys orauthorized_keys2, depending on the version of ssh.

4. On the primary computer, run the following command for each user andsecondary computer to test the ssh configuration:primary_computer% ssh secondary_computer ls

If successful, you should be able to log in to the remote shell without providinga password.

5. On the primary computer, create the remsh file in the /Server/PXEngine/etc/directory with the following content:#!/bin/shexec /usr/bin/ssh "$@"

The /Server/PXEngine/etc/ directory is located in the directory where youinstalled the engine. The default directory is /opt/IBM/InformationServer/Server/PXEngine/.

6. Give the file execute permissionchmod 755 remsh

Allowing users to run the remote shell program (rsh) without a password (Linux,UNIX):

If you do not want to use a secure shell connection, you can choose instead to usersh for each parallel engine connection. As with ssh, the connections must be ableto be established without a password prompt.


About this task

You achieve password-less rsh connections differently according to your type ofsystem. For example, you can edit the /etc/hosts.equiv file or create a .rhostsfile for each user. In both cases, add the host name of each parallel processing nodeto the /etc/hosts.equiv file or the .rhosts file, one host name per line.

The host name that is included in this file must correspond to the setting of thenode fastname parameter in the parallel configuration file.

Procedure

1. Use one of these methods to allow users to run rsh without a password:v Edit the /etc/hosts.equiv file. The file must be owned by the root user,

must grant read and write access to the root user, and grant no access to anyother user (file mode of 600).

v Create a .rhosts file for each user. The file must be located in the homedirectory of each parallel user, be owned by the user, and grant read/writeaccess to the user and no access to any other user (file mode of 600).

2. On each node, use this command to verify that users can use rsh without apassword:rsh host_name uptime

where host_name is the name of a processing node that you use with theparallel engine. If hostname is accessible, this command prints a messagedisplaying the time it has been up.

Specifying the location of the remote shell (rsh) program (Linux, UNIX):

The parallel engine has a set of paths it uses when trying to establish a remoteshell. You must explicitly specify the path location in the remsh file if the rshprogram is not in the engine list of paths.

About this task

The parallel engine searches the paths in the following order:v install_dir/etc/remsh, where install_dir is the top-level directory where the

engine tier is installed.

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,explicitly specify the path to rsh in the first place the engine searches:install_dir/etc/remsh.

Procedure

1. Copy or rename the file install_dir/etc/remsh.example to install_dir/etc/remsh.This file contains the following shell script, which invokes /usr/bin/rsh:#!/bin/shexec /usr/bin/rsh "$@"

Chapter 19. Configuring a parallel processing environment 263

2. Edit the last line of the shell script to invoke the specific remote shell commandthat you are using. For example:#!/bin/shexec /usr/local/remsh "$@"

3. To ensure that all users can run the command, use the chmod command:chmod 755 install_dir/etc/remsh

4. Test the shell script by runningrsh on each processing node:rsh node_name uptime

Setting user privileges to run parallel jobs (Linux, UNIX)A user who runs a parallel job must have the necessary privileges on all processingnodes that the application uses.

Procedure

For each user who runs a parallel job, ensure that they have the followingprivileges:v Log in accessv Read, write, and modify access to these directories:

– /ishome/Server/Scratch

– /ishome/Server/Datasets

– /tmp

v Run permission on local copies of programs and scripts.v Read access to the disk location is referred to by the $APT_ORCHHOME environment

variable set in the project, or overridden in the parameters for the job. Theinstallation default is /ishome/Server/PXEngine.

Copying the parallel engine components to system nodes(Linux, UNIX)

When you configure an MPP system, you must copy the parallel enginecomponents to all computers in your MPP system.

About this task

There are two ways to make the parallel engine available to all the nodes in theMPP system:v You can globally cross-mount, typically via NFS, a single directory on a single

system containing the parallel engine software. This configuration makessoftware upgrades more convenient than if the parallel engine components areinstalled on all processing systems. If you are using NFS to globally mount thedirectory, mount it using the soft link option.

v You can use a script to copy the parallel engine components to a directory withthe same path name on all processing systems that you designate for processingparallel jobs.

Procedure

To copy the parallel engine components to several nodes in a single operation,complete the following steps:1. On the computer where you installed the IBM InfoSphere Information Server

engine, change the directory to the parallel engine directory (by default/opt/IBM/InformationServer/Server/PXEngine).


2. Enter the following command:install_dir/install/copy-orchdist node1 node2 ... nodeN

Where node1 to nodeN is a space-separated list of the new node names.3. Add the nodes to the configuration files for jobs that will use the nodes. For

information about the parallel engine configuration files, see the IBM InfoSphereDataStage and QualityStage Parallel Job Developer's Guide.

Copying parallel engine components to processing nodes(Windows)

When you configure an MPP system with Microsoft Windows nodes, you must runthe IBM InfoSphere Information Server installation program to install the parallelengine components on all Windows computers in your MPP system.

About this task

Instead of manually copying files, run the InfoSphere Information Serverinstallation program on each target computer. The installation program installs theparallel engine components, and also installs the MKS Toolkit on each node.

Procedure

Repeat this procedure for each Windows computer that is to be a parallelprocessing node in your environment.1. On each computer that is a node, run the InfoSphere Information Server

installation program.2. Select the engine tier only.3. After you have installed the engine tier on each computer, add an entry in the

parallel engine configuration file for each additional node. For moreinformation about the parallel engine configuration file, see the IBM InfoSphereDataStage and QualityStage Parallel Job Developer's Guide.

Configuring a computer to be a processing node for MPP(Windows)

If your parallel environment is a massively parallel processing environment (MPP),complete these steps to configure a computer to be a member of your MPPenvironment.

About this task

Repeat this procedure for each Windows computer that is to be a parallelprocessing node in your environment.

Procedure1. Create a generic user account.

a. Log in as a user with Administrator privileges.b. At a command prompt, create a generic user named dstage:

NET USER dstage password /ADD /COMMENT:"DataStage user account"/FULLNAME:"DataStage User" /ACTIVE:YES /EXPIRES:NEVER /PASSWORDCHG:NO


where password is the password for the dstage user. All computers thatparticipate in the MPP configuration must use the generic user name andpassword.

c. Log off and log in as the dstage user.d. Edit the User environment variable named HOME. If the entry contains

other environment variables, for example %HOMEPATH%, replace theentire contents with the literal value of HOMEPATH. The default location istypically C:\Documents and Settings\dstage. MKS does not have the abilityto resolve the environment variable when connecting remotely.

e. You can set APT_ORCHHOME as an environment variable. This variablepoints to the parallel engine install directory. The default value isC:\IBM\InformationServer\Server\PXEngine. You must restart the rshdservice after setting up this variable.

f. Set APT_PM_NOWAITPID=1 at the project level. This environment variablemust be set for all jobs.

g. Log off as the dstage user and log back in as an Administrator user.2. Set user permissions for the dstage account. The new user must have sufficient

access rights to run jobs. The following table lists the minimum directories thatyou must set and the appropriate permissions.

Directory Permissions

X:\tmp Write, Read, Modify

X:\IBM\InformationServer\Server\Scratch Write, Read, Modify

X:\IBM\InformationServer\Server\Datasets Write, Read, Modify

3. Set the remote shell permissions:a. At a command prompt, type ksh.b. From the ksh shell, run the ssh command to connect to the remote engine:

ssh -l dstage hostname. If prompted for an RSA certificate, accept it. Youmust enter the password for the dstage user.

c. After you are connected, run the rsetup command to add the dstage userand password to the Windows XP or Windows 2003 Server LSA databasefor use by the rshd service. Enter the same password when prompted.

d. Edit the .rhosts file in the dstage user's home directory. You might need tocreate the .rhosts file if it does not already exist.

e. Add the following line:+ dstage

f. Exit from the ssh session.g. Edit the hosts.equiv file located in the $ROOTDIR/etc folder. The path name

is shown in UNIX format, which is required by MKS. That location isequivalent to C:\Program Files\MKS Toolkit\etc on the Windows filesystem, if you installed MKS in the default location.

h. For testing purposes, add the following line:+ +

You might need to create this file if it does not already exist.i. Test the configuration by attempting a remote directory listing:

rsh -l dstage hostname ls


4. Configure the parallel engine for remote shell (rsh) or secure shell (ssh). To runparallel jobs on remote hosts, you must use a remote shell script. A samplescript named remsh.example is provided for this purpose. The script is locatedin the PXEngine\etc folder.a. Copy the sample script file, and rename it remsh.b. Edit the script file to include the name of the dstage user:

#!/bin/sh# Example $APT_ORCHHOME/etc/remshrsh -l dstage "$@"

5. Configure the distribute-component script, which is located in thePXEngine\etc directory. This script installs and removes the PXEnginecomponent binaries on remote compute nodes. This script enables jobs thatcontain compiled PX transforms to copy their transformer binaries to theremote nodes.a. Make a backup copy of the distribute-component script file.b. Edit the script file to include the name of the dstage user:

# The user (optional)# theUser=dstage

c. Save the changes.

Setting environment variables for the parallel engineYou set environment variables to ensure smooth operation of the parallel engine.Environment variables are set on a per-project basis from the Administrator client.

About this task

You set the same environment variables for both Windows and UNIX or Linuxoperating systems. You can set the environment variables by using the IBMInfoSphere DataStage and QualityStage Administrator.

Procedure1. Click Start → All Programs → IBM Information Server → IBM InfoSphere

DataStage and QualityStage Administrator, and log in to the Administratorclient.

2. Click the Project tab, and select a project.3. Click Properties.4. On the General tab, click Environment.5. Set the values for the environment variables as necessary.

Environment variables for the parallel engineSet the listed environment variables depending on whether your environmentmeets the conditions stated in each variable.

See the IBM InfoSphere DataStage and QualityStage Parallel Job Advanced Developer'sGuide for a complete listing of environment variables you can set.

Network settings

APT_IO_MAXIMUM_OUTSTANDINGIf the system connects to multiple processing nodes through a network, setthe APT_IO_MAXIMUM_OUTSTANDING environment variable to specify


the amount of memory, in bytes, to reserve for the parallel engine on everynode for TCP/IP communications. The default value is 2 MB.

If TCP/IP throughput at that setting is so low that there is idle processortime, increment it by doubling the setting until performance improves. Ifthe system is paging, however, or if your job fails with messages aboutbroken pipes or broken TCP connections, the setting is probably too high.

APT_RECVBUFSIZEIf any of the stages within a job has a large number of communicationlinks between nodes, specify this environment variable with the TCP/IPbuffer space that is allocated for each connection. Specify the value inbytes.

The APT_SENDBUFSIZE and APT_RECVBUFSIZE values are the same. Ifyou set one of these environment variables, the other is automatically setto the same value. These environment variables override theAPT_IO_MAXIMUM_OUTSTANDING environment variable that sets thetotal amount of TCP/IP buffer space that is used by one partition of astage.

APT_SENDBUFSIZEIf any of the stages within a job has a large number of communicationlinks between nodes, specify this environment variable with the TCP/IPbuffer space that is allocated for each connection. Specify the value inbytes.

The APT_SENDBUFSIZE and APT_RECVBUFSIZE values are the same. Ifyou set one of these environment variables, the other is automatically setto the same value. These environment variables override theAPT_IO_MAXIMUM_OUTSTANDING environment variable that sets thetotal amount of TCP/IP buffer space that is used by one partition of astage.

Transform library

If you are working on a non-NFS MPP system, set theAPT_COPY_TRANSFORM_OPERATOR environment variable to true to enableTransformer stages to work in this environment. IBM InfoSphere DataStage andQualityStage Administrator users must have the appropriate privileges to createproject directory paths on all the remote nodes at runtime. This environmentvariable is set to false by default.

Job monitoring

By default, the job monitor uses time-based monitoring in the InfoSphereDataStage and QualityStage Administrator Director. The job monitor window isupdated every five seconds. You can also specify that the monitoring is based onsize. For example, the job monitor window is updated based on the number ofnew entries. To base monitoring on the number of new entries, set a value for theAPT_MONITOR_SIZE environment variable. If you override the default setting forthe APT_MONITOR_TIME, the setting of the APT_MONITOR_SIZE environmentvariable is also overridden.


Detailed information about jobs

To produce detailed information about jobs as they run, set theAPT_DUMP_SCORE value to True. By default, this environment variable is set toFalse.

C++ compiler

The environment variables APT_COMPILER and APT_LINKER are set atinstallation time to point to the default locations of the supported compilers. Ifyour compiler is installed on a different computer from the parallel engine, youmust change the default environment variables for every project by using theAdministrator client.

Temporary directory

By default, the parallel engine uses the C:\tmp directory for some temporary filestorage. If you do not want to use this directory, assign the path name to adifferent directory by using the environment variable TMPDIR.

Specifying C++ compiler settingsIf you are using one of the compilers listed, then you must make the specifiedchanges before you create and run parallel jobs. Complete this task for everydevelopment engine computer or any production engine computer where jobs willbe recompiled. The compiler settings must be specified for each project thatrequires them.

Procedure

v Linux For GCC:

Use the IBM InfoSphere DataStage and QualityStage Administrator to configurecompiler settings for each project.– APT_COMPILEOPT: -O -fPIC -Wno-deprecated -c -m32– APT_COMPILER: g++– APT_LINKER: g++– APT_LINKOPT: -shared -m32 -Wl,-Bsymbolic,--allow-shlib-undefined

v UNIX For Solaris 9 and 10:

Use the IBM InfoSphere DataStage and QualityStage Administrator to configurecompiler settings for each project.– 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 .NET 2003:

1. Select Start → IBM InfoSphere Information Server → IBM InfoSphereDataStage and QualityStage Administrator, and then log in to theAdministrator client.

2. Select Projects → Properties → Environment.3. Select Parallel → Compiler → APT_COMPILEOPT and delete the string

-W/Zc:wchar_t- from the end of the existing setting in the Value field.


4. Select Parallel → Compiler → APT_LINKOPT and delete the string-W/Zc:wchar_t- from the end of the existing setting in the Value field.

v Windows For Microsoft Visual Studio 2005 Professional Edition C++:

No additional changes are required to run the parallel engine transforms whenthis compiler is installed before you install IBM InfoSphere Information Server.

v Windows For Microsoft Visual Studio .NET 2005 Express® Edition C++ andMicrosoft Visual Studio .NET 2008 Express Edition C++:

The compiler settings for this version are correctly set by default; however,ensure that you also installed the SDK and that its resources are available to thesystem environment.1. From the Windows Control Panel, select System Advanced → Environment

Variables → System Variables.2. Set the LIB environment variable to the location of the library directory for

the SDK. For example, for Microsoft Visual Studio .NET 2008 Express EditionC++, a typical location is C:\Program Files\Microsoft SDKs\Windows\v6.0A\Lib.

3. Set the INCLUDE environment variable to the location of the includedirectory for the SDK. For example, for Microsoft Visual Studio .NET 2008Express Edition C++, a typical location is C:\Program Files\MicrosoftSDKs\Windows\v6.0A\Include.

Note: The LIB and INCLUDE environment variable names must be specifiedin uppercase characters.

4. Save the settings and restart the computer.

Note: You must restart the computer for the environment variable settings totake effect.

Configuring the parallel engine (Linux, UNIX)The following tasks must be performed to configure the parallel engine for Linuxand UNIX.

Setting the maximum number of processes for parallel jobs(AIX)

The setting of the maxuproc kernel parameter on each parallel engine nodecontrols the maximum number of processes per user for that node. Use the chdevcommand to set an appropriate value.

About this task

A user who runs parallel jobs must be able to run at least 1000 processes on eachprocessing node. Large systems and symmetric multiprocessing (SMP) serversrequire more than 1000 processes. Complete the following steps on each computerthat acts as a processing node in your parallel environment.

Procedure1. Issue this command to determine the current setting for the number of

processes:/usr/sbin/lsattr -E -l sys0 | grep maxuproc

2. If the value of the maxuproc parameter is less than 1000, enter this commandto increase it to 1000:


/usr/sbin/chdev -l sys0 -a maxuproc=1000

This command must be issued on the node by a user with root privileges.3. In an AIX cluster, you can use the dsh command to set the maximum number

of processes per user to 1000 on all cluster nodes.dsh -a chdev -l sys0 -a maxuproc=1000

This command must be run from the control workstation with root privileges.You can also use the smit or smitty commands to perform this action.

Setting per-user kernel parameters for parallel jobs (AIX)Per-user kernel parameters ensure that users who run parallel jobs have sufficientresources. Use the chuser command to set appropriate values.

About this task

The following table describes the parameters that control memory resources andrecommends a value for each parameter. Complete the following steps for eachuser on each processing node in your parallel environment.

Table 95. Per-user kernel parameter values

Parameter Description Value

fsize The largest file that a usercan create.

2 GB minus 512 bytes(4,194,303 512-byte blocks).

data The largest data segment, orheap, that a program canhave.

128 MB (262,144 512-byteblocks) or more. For no limit,specify -1.

stack The largest stack that aprogram can have.

32 MB (65,536 512-byteblocks) or more.

rss The maximum amount ofphysical memory that a userprocess can use.

64 MB (131,072 512-byteblocks) or more.

Procedure1. 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, including fsize, data, stack, andrss. For example:fsize=2097151 data=262144 stack=65536 rss=131072

These numbers represent the number of 512-byte blocks.2. Log in as the root user.3. Set the parameters for each user as defined by the values in Table 95. 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


4. In an AIX cluster, you can use the dsh command to set the kernel parameterson all cluster nodes. This command must be issued from the controlworkstation.dsh -a chuser param=value user_name

What to do next

Users whose per-user kernel parameters have changed must log out and log inagain for the changes to take effect.

Setting the paging space for the parallel engineTo process parallel jobs that have large amounts of data, specify the minimumpaging space settings.

About this task

Attention: You must be a system administrator logged in as the root user to resetthe system paging space.

Setting the paging space for the parallel engine (AIX)To process parallel jobs that have large amounts of data, specify the minimumpaging space settings.

Before you begin


About this task

The minimum amount of paging space to run parallel jobs is 500 MB per processorfor computers that have fewer than 20 processors and 1 GB per processor forcomputers that have 20 or more processors. The design of the parallel jobs and thenumber of jobs that you plan to run at one time affect the paging spacerequirement. Jobs that have many individual stages require more paging spacethan jobs that have fewer individual stages. Running more than one job at a timerequires more paging space.

Complete this procedure on each computer in your parallel processingenvironment.

Procedure1. 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.

Table 96. Results of lsps command

Page spacePhysicalvolume 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


The Group Size column lists the paging size for each disk drive. In this case,the total for the node is 2000 MB + 192 MB + 64 MB = 2256 MB (approximately2.2 GB).

2. See the AIX documentation for additional information about setting the pagingspace.

Setting the paging space for the parallel engine (Solaris)To process parallel jobs that have large amounts of data, specify the minimumpaging space settings.

Before you begin


About this task



Procedure1. 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 followingexample output:swapfile dev swaplo blocks free/dev/dsk/c0t3d0s1 32,25 8 132040 103440/dev/dsk/c0t2d0s1 32,17 8 580600 553760/dev/dsk/c0t1d0s6 32,14 8 1348192 1316864

A single block is 512 bytes. In this example, the total paging space is 2,060,832blocks, or approximately 1 GB.

2. Increase the paging space as necessary for each node, using the followingcommand:swap -a

Setting the paging space for the parallel engine (HP-UX)To process parallel jobs that have large amounts of data, specify the minimumpaging space settings.

Before you begin



About this task



Procedure1. Log in as the root user, 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. Sample results of the swapinfo command

TypeKBAvailable KB Used KB Free % Used

Start/Limit

KBReserve Priority Name

dev 524288 0 524288 0% 0 1 /dev/vg00/l vol2

dev 524288 60808 463480 12% 0 0 /dev/vg01/1vol1

reserve 240012 240012

memory 697588 602088 95500 86%

In this example, the total paging space for the two disks is approximately 1 GB.2. To change the paging space as necessary for each node, use the System

Administration Manager (SAM) or use the command /etc/swapon -a.

Setting the paging space for the parallel engine (Linux)To process parallel jobs that have large amounts of data, specify the minimumpaging space settings.

Before you begin


About this task



Procedure

See the documentation for your Linux distribution for information about settingthe paging space for your system. Configure the paging space on each computer inyour parallel processing environment.

Updating the /etc/magic fileEdit the /etc/magic file to include data set descriptor files for the parallel engine.

About this task

The UNIX file command examines a file to classify it by type. The command readsthe /etc/magic file to identify files that have a magic number. The magic number isa constant that specifies the file type.

The install_dir/etc/magic file contains additions to the /etc/magic file that arespecific to the parallel engine. The install_dir directory is the top-level directory ofthe parallel engine installation. The default path is /opt/IBM/InformationServer/Server/PXEngine/.

Procedure1. Log in as the root user.2. Back up the /etc/magic file.

cp /etc/magic /etc/magic.bak

3. Edit the /etc/magic file and add the contents of the install_dir/etc/magic tothe /etc/magic file. For example: 0 string Torrent IBM Information Serverparallel engine dataset descriptor

4. Save the /etc/magic file.5. Test that the /etc/magic file has been updated correctly by running the file

command on a data set descriptor file.file file_name

where file_name is the name of a data set descriptor file. For example, if youenter file t1.ds, the following command returns:t1.ds: IBM Information Server parallel engine dataset descriptor

Configuring the parallel engine (Windows Server)You can configure the parallel engine for Microsoft Windows Server, 32-biteditions, by editing the Windows Registry and by changing system settings thatcontrol available memory. The Windows Registry includes keys that controldesktop heap size, swap area size, the number of available TCP connections, andmemory management.

Procedure

If the parallel engine is installed on a computer that runs Microsoft WindowsServer, Standard or Enterprise edition:1. Enable auto-tuning for the paged pool size. Enabling auto-tuning ensures that

sufficient memory is available for paged pools. See “Configuring the WindowsRegistry: Enabling auto-tuning for paged pool size” on page 276.


2. Enable auto-tuning for the system page size. Enabling auto-tuning ensures thatsufficient memory is available for page tables and page table entries. See“Configuring the Windows Registry: Enabling auto-tuning for system pagesize” on page 277.

3. Set the threshold for de-committing memory. On computers that have 1 GB ormore of RAM, setting the threshold to the suggested value improves memorymanagement. See “Configuring the Windows registry: Setting the threshold forde-committing memory” on page 278.

4. Increase the noninteractive desktop heap size to ensure that a sufficient numberof processes can be created and run concurrently. See “Configuring theWindows registry: Increasing the noninteractive desktop heap size” on page278.

5. Specify settings for TCP/IP in the Windows Registry to ensure that therequired number of parallel processes can run concurrently. See “Configuringthe Windows registry: Specifying TCP/IP settings” on page 279.

6. Change the size of the swap area to improve performance. See “ConfiguringWindows: Changing swap area size” on page 280.

7. Edit the boot.ini file to remove the /3GB switch and, if necessary, add the /PAEswitch. See “Configuring Windows: Editing the boot.ini file” on page 281.

Configuring the Windows Registry: Enabling auto-tuning forpaged pool size

If the parallel engine is installed on a computer that runs Microsoft WindowsServer, Standard or Enterprise edition, enable auto-tuning for the paged pool size.Enabling auto-tuning ensures that sufficient memory is available for paged pools.

Before you beginv Log in to Windows Server as the Administrator.v Start the Registry Editor, and back up the Windows Registry. If you plan to

make several changes (for example, to configure the parallel engine), create asingle backup before you make all the changes.

About this task

The Windows Server kernel allocates memory in pools. These pools are known asthe paged pool and the non-paged pool. Performance degradation and serverinstability might result if the memory for these pools is exhausted. To avoid thissituation, you can enable auto-tuning at server startup by editing thePagedPoolSize registry value in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management registry subkey.

Procedure1. In the Registry Editor, select the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

2. In the right pane of the Registry Editor, right-click PagedPoolSize, and clickModify.

3. In the Base area, select Hexadecimal.4. In the Value data field, specify 0 (zero). If 0 is already specified, auto-tuning is

enabled, and you do not need to change this value. If you must specify a valueother than 0, the value data for SystemPages must be 0.

5. Click OK.


What to do next

After you make changes to the Windows Registry, restart Windows to apply yourchanges. If you plan to make several changes (for example, to configure theparallel engine), make all changes before you restart Windows.

Configuring the Windows Registry: Enabling auto-tuning forsystem page size

If the parallel engine is installed on a computer that runs Microsoft WindowsServer, Standard or Enterprise edition, enable auto-tuning for the system page size.Enabling auto-tuning ensures that sufficient memory is available for page tablesand page table entries.



About this task

To support virtual to physical address translation, the Windows operating systemuses page tables and page table entries (PTEs). These tables reside in kernelmemory. If not enough memory is allocated for the page tables, Windows mightfail to create processes, threads, and I/O buffers. Because the parallel enginecreates many processes to run a job, jobs will fail at startup or during run time ifWindows does not have enough resources to create processes.

You can enable auto-tuning at server startup by editing the SystemPages registryvalue in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\Memory Management registry subkey.


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

2. In the right pane of the Registry Editor, right-click SystemPages, and clickModify.

3. In the Base area, select Hexadecimal.4. In the Value data field, specify 0 (zero). Typically, specifying 0 for this value

provides sufficient memory. If the available PTEs are exhausted, however, youcan specify the maximum value, 0XFFFFFFFF. If you must specify a value otherthan 0, the value data for PagedPoolSize must be 0.

5. Click OK.

What to do next



Configuring the Windows registry: Setting the threshold forde-committing memory

If the parallel engine is installed on a computer that runs Microsoft WindowsServer, Standard or Enterprise edition, set the threshold for de-committingmemory. On computers that have 1 GB or more of RAM, setting the threshold tothe suggested value improves memory management.



About this task

When Windows frees memory at a specific address, the memory can remaincommitted, or it can be de-committed and marked as reserved. You can improvememory management on computers that have 1 GB or more of RAM by editingthe HeapDeCommitFreeBlockThreshold registry value in theHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager registrysubkey. This registry value specifies the number of contiguous bytes of memory(around the address of the freed memory) above which the block of memory isde-committed.


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager

2. Specify the value data for HeapDeCommitFreeBlockThreshold registry value:a. If the registry value does not exist, click Edit → New → DWORD Value, and

type the name of the registry value.b. In the right pane of the Registry Editor, right-click the registry value, and

click Modify.c. In the Base area, select Hexadecimal.d. In the Value data field, specify 0x00040000.e. Click OK.

What to do next


Configuring the Windows registry: Increasing thenoninteractive desktop heap size

If the parallel engine is installed on a computer that runs Microsoft WindowsServer, Standard or Enterprise edition, increase the noninteractive desktop heapsize to ensure that a sufficient number of processes can be created and runconcurrently.

Before you beginv Log in to Windows Server as the Administrator.


v Start the Registry Editor, and back up the Windows Registry. If you plan tomake several changes (for example, to configure the parallel engine), create asingle backup before you make all the changes.

v After you finish this procedure, make sure to restart Windows as described inthe procedure.

About this task

IBM InfoSphere DataStage processes are created in a specific desktop heap. Eachprocess consumes a small amount of memory from the desktop heap. If you expectto run many InfoSphere DataStage jobs concurrently, increase the size of thenoninteractive desktop heap to allow more processes to be created and runconcurrently.

You increase the size of the noninteractive desktop heap by editing theSharedSection parameter string in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems registry subkey. TheSharedSection parameter string is located in the Windows registry value and usesthe following format to specify heap size:SharedSection=xxxx,yyyy,zzzz

Where:v xxxx specifies the maximum size of the system-wide heap (in kilobytes)v yyyy specifies the size of each desktop heapv zzzz specifies the size of the desktop heap that is associated with a

noninteractive Windows instance


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems

2. In the right pane of the Registry Editor, right-click the Windows registry value,and click Modify.

3. In the Value data field, locate the SharedSection parameter string, and changethe last SharedSection parameter from 512 to 2048. For example, specify thefollowing values for this parameter:SharedSection=1024,3072,2048

If you cannot change the size of the desktop heap to 2048, try setting the valueto 1024. For example, specify the following values for this parameter:SharedSection=1024,3072,1024

4. Click OK.

What to do next


Configuring the Windows registry: Specifying TCP/IP settingsIf the parallel engine is installed on a computer that runs Microsoft WindowsServer, Standard or Enterprise edition, specify settings for TCP/IP in the WindowsRegistry to ensure that the required number of parallel processes can runconcurrently.




About this task

You specify TCP/IP settings by editing the following registry values in theHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parametersregistry subkey:

MaxUserPortSpecifies the maximum port number for ephemeral TCP ports.

TcpNumConnectionsSpecifies the maximum number of concurrent connections that TCP canopen. This value significantly affects the number of concurrent osh.exeprocesses that are allowed. If the value for TcpNumConnections is too low,Windows cannot assign TCP ports to stages in parallel jobs, and theparallel jobs cannot run.

These keys are not added to the registry by default.


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

2. Specify the following registry values: MaxUserPort and TcpNumConnections.a. If the registry value does not exist, click Edit → New → DWORD Value, and

type the name of the registry value.b. In the right pane of the Registry Editor, right-click the registry value, and

click Modify.c. In the Base area, select Hexadecimal.d. In the Value data field, specify the following values:

Registry value name Value data Valid range

MaxUserPort 65534 5000 - 65534 (decimal)

TcpNumConnections 65534 0 - 0xfffffe (65534 decimal)

e. Click OK.

What to do next


Configuring Windows: Changing swap area sizeIf the parallel engine is installed on a computer that runs Microsoft WindowsServer, Standard or Enterprise edition, change the size of the swap area to improveperformance.


Before you begin

Log in to Windows Server as the Administrator.

Procedure1. Click Start → Control Panel → System.2. In the System Properties window, click the Advanced tab.3. In the Performance area, click Settings.4. In the Performance Options window, select the Advanced tab.5. In the Virtual memory area, click Change.6. In the Virtual Memory window, specify a value for Maximum size. Set this

value to be one to one-and-a-half times larger than the value for physicalmemory.

7. Click Set.8. Click OK three times, and then close the Control Panel window.

What to do next

After you change the size of the swap area, restart Windows to apply your changes

Configuring Windows: Editing the boot.ini fileIf the parallel engine is installed on a computer that runs Microsoft WindowsServer, Standard or Enterprise edition, edit the boot.ini file to remove the /3GBswitch and, if necessary, add the /PAE switch.

Before you begin

You might want to save a backup of the boot.ini file before you change the file.

About this task

By default, Windows reserves 2 GB of memory for the kernel and 2 GB of memoryfor user mode programs. When the /3GB switch is specified in the boot.ini file, 3GB of memory is reserved for user mode programs, and the amount of kernelmemory is reduced by 1 GB. This setting results in an insufficient amount ofmemory for the kernel. To resolve this problem, remove the /3GB switch, ifpresent, from boot.ini file.

In addition, on servers that have more than 4 GB of physical memory installed,specify the /PAE switch in the boot.ini file. The /PAE switch specifies physicaladdress extensions that allow a 32-bit processor to access memory that is above the4 GB limit.

Procedure1. Click Start → Control Panel → System.2. In the System Properties window, click the Advanced tab.3. In the Startup and Recovery area, click Settings.4. Click Edit to edit the boot.ini file.5. Remove the /3GB switch, if present.6. On servers that have more than 4 GB of physical memory installed, add the

/PAE switch to the boot.ini file.7. Save and close the boot.ini file.


8. Click OK twice, and then close the Control Panel window.

Results

These changes are applied when you restart Windows.

Configuring database connectivity in a parallel environmentLinux UNIX

The following topics describe the steps to take to connect to various databasesfrom a parallel job.

Configuring access to DB2 databasesConfigure IBM InfoSphere DataStage to run on all processing nodes that functionas IBM DB2 servers.

Procedure

To configure InfoSphere DataStage to access IBM DB2 servers, include a nodedefinition for each IBM DB2 server node in the configuration file. Also, completethe following steps.

Running the IBM DB2 configuration scriptUse the IBM DB2 configuration script to configure access to IBM DB2 databases.

Procedure

From the Linux or UNIX command line, run the $APT_ORCHHOME/bin/db2setup.sh script once for each IBM DB2 database that users will access. Pass thedatabase name as an argument.For example, the following command calls db2setup.sh to configure access to thedatabase db2db:db2setup.sh db2db

Granting user privileges to run IBM DB2 Enterprise stage jobsYou must grant privileges to each user who runs jobs that contain the IBM DB2Enterprise stage.

Before you begin

You must have DBADM privileges to complete this task.

Procedure

Run the $APT_ORCHHOME/bin/db2grant.sh script once for each user. Use thefollowing syntax:db2grant.sh database_name user_name

Accessing a remote IBM DB2 server from IBM DB2 EnterprisestagesYou use an IBM DB2 client to connect from an IBM DB2 Enterprise stage to aremote IBM DB2 server.


About this task

For more information, read about remote connections in the IBM InfoSphereDataStage and QualityStage Connectivity Guide for IBM DB2 Databases.

Configuring the DB2 systemThe DB2 server can be configured in many ways. The DB2 administrator typicallyfollows this procedure to configure IBM DB2 and IBM InfoSphere DataStage tocommunicate.

Procedure1. Install IBM DB2 and make sure it is working correctly.

Note: Ensure that the touch utility exists in the /usr/bin directory or create asymbolic link to the touch command.

2. Grant the InfoSphere DataStage users SELECT privileges on the DB2 systemtables syscat.nodegroupdef, syscat.tablespaces, and syscat.tables.

3. Make the file db2nodes.cfg readable by the InfoSphere DataStage administrativeuser.

4. InfoSphere DataStage runs many processes for each job. This can require thesystem administrator to modify DB2 resources, configuration parameters, andmanager configuration parameters. See the DB2 information center for moreinformation.

5. The DB2 Enterprise stage requires that users invoking it in load mode haveDBADM privilege on the DB2 database written to by the stage. Among theways to grant this privilege is to start the DB2 system, connect to a database,and grant privileges from the DB2 command prompt:CONNECT TO database_nameGRANT DBADM ON DATABASE TO USER user_name

Configuring DB2 usersTo access IBM InfoSphere DataStage, parallel jobs use an operating system user IDto connect to the IBM DB2 server. Therefore, user IDs that invoke DB2 readoperators must have the SELECT privilege on the tables that they access, and userIDs that invoke DB2 write operators must have INSERT privileges on the tablesthat they access.

About this task

The following procedure configures an InfoSphere DataStage user to access theDB2 database. Either a system administrator or an InfoSphere DataStage user canperform this task.

Procedure1. Set the DB2INSTANCE environment variable to the user name of the owner of

the DB2 instance. DB2INSTANCE determines the location of the db2nodes.cfgfile, as follows:~owner_user_name/sqllib/db2nodes.cfg

The db2nodes.cfg file contains information that is used to translate DB2 nodenumbers to host names. The information in this file must agree with the hostnames that are specified in the InfoSphere DataStage parallel configuration file.For example, if you set DB2INSTANCE to Janet, the db2nodes.cfg file is in thefollowing location:~Janet/sqllib/db2nodes.cfg.


2. Set the DB2DBDFT environment variable to the name of the DB2 database thatyou want to connect to.

3. Source the db2profile file and update the LIBPATH environment variable toinclude the location of the DB2 library that contains your instance of DB2. Inthe following example, the owner of the DB2 instance is the user Mary, thelocation of db2profile is ~Mary/sqllib/db2profile, and the location of the DB2library is ~Mary/sqllib/lib.For a Korn or Bourne shell, include these statements in the .profile or .kshrcfiles:. ~Mary/sqllib/db2profileexport LIBPATH=~Mary/sqllib/lib:${LIBPATH:-/usr/lib}

For a C shell, include these lines in the .cshrc file:source ~Mary/sqllib/db2profileif (! $?LIBPATH) setenv LIBPATH /usr/libsetenv LIBPATH ~Mary/sqllib/lib:$LIBPATH

Configuring access to Oracle databasesConfiguring access to Oracle databases includes granting the appropriate accesslevel to users.

Granting access to the Oracle parallel serverTo access the Oracle parallel server (OPS), users must have SELECT access to thesys.gv_$instance and sys.v_$cache tables.

Procedure1. Run the following SQL statements:

GRANT select ON sys.gv_$instance TO public;GRANT select ON sys.v_$cache TO public;

2. If the Oracle parallel server is not installed, set the APT_ORACLE_NO_OPSenvironment variable to disable OPS checking on the Oracle Enterprise stage.

Granting user privileges to run Oracle Enterprise stage jobsYou must grant privileges to each user who runs jobs that contain the OracleEnterprise stage.

Procedure1. Create the user-defined environment variable ORACLE_HOME and set it to the

$ORACLE_HOME path, such as /disk3/oracle10.2. Create the user-defined environment variable ORACLE_SID and set it to the

correct service name, such as ODBCSOL.3. Add ORACLE_HOME/bin to your PATH and ORACLE_HOME/lib to your operating

system's library path (LIBPATH, LD_LIBRARY_PATH, or SHLIB_PATH).4. Obtain login privileges to Oracle by using a valid Oracle user name and

password. The user name and password must be recognized by Oracle beforeyou attempt to access it.

5. Obtain the SELECT privilege on the following tables:

DBA_EXTENTSDBA_DATA_FILESDBA_TAB_PARTITONSDBA_TAB_SUBPARTITIONSDBA_OBJECTSALL_PART_INDEXES


ALL_PART_TABLESALL_INDEXESSYS.GV_$INSTANCE (required only if you use the Oracle parallel server)

6. Verify that the APT_ORCHHOME/bin directory is before the ORACLE_HOME/bindirectory in the PATH statement.

7. Create a role that has SELECT privileges on the tables. The following codecreates a role named DSXE, which grants SELECT privileges on the requiredtables:CREATE ROLE DSXE;GRANT SELECT on sys.dba_extents to DSXE;GRANT SELECT on sys.dba_data_files to DSXE;GRANT SELECT on sys.dba_tab_partitions to DSXE;GRANT SELECT on sys.dba_tab_subpartitions to DSXE;GRANT SELECT on sys.dba_objects to DSXE;GRANT SELECT on sys.all_part_indexes to DSXE;GRANT SELECT on sys.all_part_tables to DSXE;GRANT SELECT on sys.all_indexes to DSXE;

8. Enter this command to grant the role to users who run jobs:GRANT role_name to oracle_user;

Configuring access to Teradata databasesConfiguring access to Teradata databases includes granting the appropriate accesslevel to users.

Installing the Teradata tools and utilitiesYou must install Teradata Tools and Utilities on all nodes that run parallel jobs. Seethe installation instructions supplied by Teradata for complete information.

Procedure1. Ensure that the Teradata Parallel Transporter is installed and that the following

environment variables are set in the /etc/profile file:

v AIX

TWB_ROOT=/usr/tbuild/08.01.00.02PATH=$TWB_ROOT/bin:$PATHLIBPATH=$TWB_ROOT/lib:$LIBPATHNLSPATH=$TWB_ROOT/msg/%Nexport TWB_ROOT PATH LIBPATH NLSPATH

v HP�UX

TWB_ROOT=/usr/tbuild/08.01.00.02PATH=$TWB_ROOT/bin:$PATHSHLIB_PATH=$TWB_ROOT/lib:$SHLIB_PATHNLSPATH=$TWB_ROOT/msg/%Nexport TWB_ROOT PATH SHLIB_PATH NLSPATH

v Solaris

TWB_ROOT=/usr/tbuild/08.01.00.02PATH=$TWB_ROOT/bin:$PATHLD_LIBRARY_PATH=$TWB_ROOT/lib:$LD_LIBRARY_PATHNLSPATH=$TWB_ROOT/msg/%Nexport TWB_ROOT PATH LD_LIBRARY_PATH NLSPATH

2. To run Teradata Connector jobs, add these same environment variables to thedsenv file.

Creating a Teradata userYou must create a Teradata user before you can connect from the parallel server tothe Teradata database.


About this task

The Teradata database owner is the user that is referred to by a DB optionsproperty in the Teradata stage. The user must be able to create tables and insertand delete data. If you want to use a pre-existing Teradata user, install a databaseserver and configure it to use a new database. Install the new database server with100 MB of PERM space and 10 MB of SPOOL space.

Procedure

After installing the Teradata Tools and Utilities:1. Run these Basic Teradata Query (BTEQ) commands to create a user account

that is stored in the terasync table.CREATE USER user_name FROM database_name ASPASSWORD = user_passwordPERM = 100000000SPOOL = 10000000

2. After the account is set up, run the following command:GRANT SELECT on dbc TO user_name;

Configuring access to Informix XPS databasesYou must set the INFORMIXSERVER, INFORMIXDIR, ANDINFORMIXSQLHOSTS environment variables. On AIX, you must also set theLIBPATH.

About this task

You must have the correct privileges and settings to use the Informix EnterpriseStage. You must have a valid account and appropriate privileges on the databasesto which you connect. You must have read and write privileges on any table towhich you connect, and you must have Resource privileges for using the PartitionTable property on an output link or for using create and replace modes on aninput link.

Procedure1. Make sure that Informix XPS is running.2. Make sure that the INFORMIXSERVER environment variable is set in your

environment. This value corresponds to a server name in the sqlhosts file andis set to the coserver name of coserver 1. The coserver must be accessible fromthe node on which you invoke the job.

3. Make sure that the INFORMIXDIR environment variable is set to theinstallation directory of the Informix server.

4. Make sure that the INFORMIXSQLHOSTS environment variable is set to thepath to the sqlhosts file, for example, /disk6/informix/informix_runtime/etc/sqlhosts.

5. AIX Set the LIBPATH environment variable as follows:LIBPATH=$APT_ORCHHOME/lib:$INFORMIXDIR/lib:’dirname $DSHOME’/branded_odbc/lib:$DSHOME/lib:$DSHOME/uvdlls:$DSHOME/java/jre/bin/classic:$DSHOME/java/jre/bin:$INFORMIXDIR/lib:$INFORMIXDIR/lib/cli:$INFORMIXDIR/lib/esql


Chapter 20. Stopping and starting the server engine

Restart the IBM InfoSphere Information Server engine after you complete certaintasks such as editing the dsenv file on Linux or UNIX or modifying the uvconfigfile.

Procedure

v Linux UNIX

1. Log in to the engine tier computer as the IBM InfoSphere DataStageadministrator (typically dsadm).

2. Change to the engine directory and set the environment.cd $DSHOME. ./dsenv

$DSHOME is the name of the engine directory. The default directory is/opt/IBM/InformationServer/Server/DSEngine.

3. Stop the engine../bin/uv –admin -stop

The command displays a message when the engine stops.4. Restart the engine.

./bin/uv –admin -start

v Windows

1. In the Windows control panel, open the DataStage Control Panel.2. Click Stop all services. Wait until the services have stopped.3. Click Start all services.



Chapter 21. Changing host names and ports

You can change your IBM DB2 and IBM WebSphere Application Server host namesand ports after installation.

Changing the WebSphere Application Server HTTP portTo change the IBM WebSphere Application Server HTTP server port, HTTPtransport port, or HTTPS port, use the WebSphere Application Serveradministrative console, restart WebSphere Application Server, and then edit otherconfiguration files.

About this task

This task applies to stand-alone (non-cluster) environments only.

Procedure1. Change the port value in the WebSphere Application Server administrative

console.To change the port value in the console:a. Start the WebSphere Application Server administrative console.b. For WebSphere Application Server, Version 7.0, click Servers → Server Types

→ WebSphere application servers.For WebSphere Application Server, Version 6.1, click Servers → Applicationservers.

c. Select the server for which you want to change the port.d. Click Ports.e. Change the value of the port.v To change the value of the HTTP server port or HTTP transport port,

change the WC_defaulthost value.v To change the value of the HTTPS port, change the

WC_defaulthost_secure value.2. Stop and restart WebSphere Application Server.3. Update the port value in the Version.xml files. These files contain the

installation records that are used by the installation program. Keeping thesefiles current avoids problems with future installations. Update the followingVersion.xml files:v The file that is on the server that hosts the engine tierv The file that is on the server that hosts the services tierOn each server, the Version.xml file is located in the IBM InfoSphereInformation Server installation directory.Edit each file as follows:a. Use a text editor to open the Version.xml file.b. In the file, locate the following XML element:

<PersistedVariable encrypted="false" name="is.console.port"persistent="true" readonly="true" value="port" />

c. Change the value attribute to the new HTTPS port if HTTPS is configured.If HTTPS is not configured, specify the new HTTP port.

d. In the file, locate the following XML element:



e. Change the value attribute to the new HTTPS port if HTTPS is configured.If HTTPS is not configured, specify the new HTTP port.

f. If you changed the WC_defaulthost value in step 1 on page 289, specify thesame value in the following XML element:<PersistedVariable encrypted="false" name="was.default.host.port"


g. If you changed the WC_defaulthost_secure value in step 1 on page 289,specify the same value in the following XML element:<PersistedVariable encrypted="false" name="was.secure.default.host.port"


4. Modify the registered-servers.xml file on each computer that hosts theservices tier. You can find this file in the following location, where installdir isthe location of your InfoSphere Information Server installation directory:


Note: The typical installation location is /opt/IBM/InformationServer.


Note: The typical installation location is C:\IBM\InformationServer.



There might be multiple <asb-server> elements in the registered-servers.xml file. Modify the <asb-server> elements for the servers whoseport numbers are changing.


5. Modify the registered-servers.xml file on each computer that hosts the enginetier. You can find this file in the following location:





There might be multiple <asb-server> elements in the registered-servers.xml file. Modify the <asb-server> elements for the servers whoseport numbers are changing.

c. Update the port value.


d. Save your changes.6. Optional: Modify the registered-servers.xml file on each computer that hosts

the client tier. The list of servers in these files is used to populate the serverlists in the login pages for some client applications. You can update these filesif you want to have the updated port values shown on the next login attempt.Alternatively, you can enter the new value in the login page the next time youlog in. However, the old host name and port continue to display in the lists insome client application login pages unless you modify theregistered-servers.xml file on the computer. Modify the file in either of thefollowing ways:v Change the file in the same way that you modified the registered-


Note: On client-only computers, the is-primary-server="true" attributedoes not appear in the <asb-server> element.

v Run the RegistrationCommand command as follows:

– Linux UNIX

cd /opt/IBM/InformationServer/ASBNode/bin./RegistrationCommand -remove -hostname host -port port

– Windows

cd C:\IBM\InformationServer\ASBNode\binRegistrationCommand.bat -remove -hostname host -port port

Note: These commands use example installation directories, which might bedifferent from your own setup.

Tip: To use the RegistrationCommand command to add the new host nameand port number for a new server entry, run the command:

– Linux UNIX

./RegistrationCommand.sh -add -name host -hostname host -port port

– Windows

RegistrationCommand.bat -add -name host -hostname host -port port

Changing other WebSphere Application Server portsAfter you change IBM WebSphere Application Server ports in the WebSphereApplication Server administrative console, you must restart WebSphere ApplicationServer, and then edit other configuration files.

Procedure1. Change a port value in the WebSphere Application Server administrative

console.To change a port value in the console:a. Start the WebSphere Application Server administrative console.b. For WebSphere Application Server, Version 7.0, click Servers → Server Types

→ WebSphere application servers.For WebSphere Application Server, Version 6.1, click Servers → Applicationservers.

c. Select the server for the port that you want to change.d. Click Ports.e. Change the value of the port that you want to change.

Chapter 21. Changing host names and ports 291

2. In a stand-alone environment, stop and restart WebSphere Application Server.In a cluster environment, stop and restart the WebSphere Application Servercluster member for which the port has changed.

3. If you changed the SOAP_CONNECTOR_ADDRESS port value in the WebSphere portsettings, you must update the wsadmin.properties file.

Note: For a cluster environment, change wsadmin.properties only if theSOAP_CONNECTOR_ADDRESS of the deployment manager is changed. Make sure toupdate the wsadmin.properties files of all the nodes and profiles of the clusterso that they point to the deployment manager. You do not need to update anyfile if you changed the SOAP_CONNECTOR_ADDRESS of a cluster member only.To update the file:a. Use a text editor to open the wsadmin.properties file. This file is on the

services tier in the following directory, where <profile> is the name of theprofile where IBM InfoSphere Information Server is installed. In a clusterenvironment, this is the name of the Custom profile where the clustermember, for which the port has been changed, is deployed.

v Linux UNIX opt/IBM/WebSphere/AppServer/profiles/<profile>/properties/

v Windows C:\IBM\WebSphere\AppServer\profiles\<profile>\properties\

Note: These file paths use example installation directories, which might bedifferent from your own setup.

b. Open the file by using a text editor, and locate thecom.ibm.ws.scripting.port parameter.

c. Change the parameter value so it matches SOAP_CONNECTOR_ADDRESS.d. Save any changes. Restart WebSphere after all other changes are complete.

In a stand-alone environment, the default value of SOAP_CONNECTOR_ADDRESS is8880.In a cluster environment, the default value of SOAP_CONNECTOR_ADDRESS of thedeployment manager is 8879. The default value for SOAP_CONNECTOR_ADDRESS fora cluster member is 8880.

Remember: For a cluster environment, make sure to repeat all of step 3 for allthe nodes and profiles of the cluster.

Changing the metadata repository database host name and portYou can change the metadata repository database host name or port by modifyingconfiguration files and then changing values in the IBM WebSphere ApplicationServer administrative console.

Procedure1. Stop IBM WebSphere Application Server.2. Create a temporary empty directory and make it your default working

directory:mkdir tmpcd tmp

3. Locate the ojb-conf.jar file on one of the following servers, depending uponyour configuration:


v If your installation includes a clustered implementation of WebSphereApplication Server, locate the file on the server that hosts the WebSphereApplication Server Deployment Manager.

v Otherwise, locate the file on the server that hosts the services tier.The file is located in the following directory:

v Linux UNIX /opt/IBM/InformationServer/ASBServer/apps/lib

v Windows C:\IBM\InformationServer\ASBServer\apps\lib

4. Unjar the ojb-conf.jar file in the temporary location by using the jar utilityof a Java developer kit such as the one in WebSphere Application Server.

v Linux UNIX (The following lines are part of a single command)/opt/IBM/WebSphere/AppServer/java/bin/jar xf

/opt/IBM/InformationServer/ASBServer/apps/lib/ojb-conf.jar

v Windows (The following lines are part of a single command)C:\IBM\WebSphere\AppServer\java\bin\jar xf

C:\IBM\InformationServer\ASBServer\apps\lib\ojb-conf.jar

5. Open the repository_database.xml file in a text editor.6. Locate the dbalias attribute. The following table describes the attribute

format.

Table 98. Attributes for different database system systems

Databasesystem dbalias attribute

IBM DB2databasesystem

dbalias="//host:port/dbname"

Oracledatabasesystem

dbalias="//host:port;SID=SID"

Oracle RAC Dbalias="//host:port;ServiceName=SID;AlternateServers= (host:port,host:port, host:port, ...)

For more information about the format of this attribute for Oracle RAC, see“Connecting to an Oracle RAC configuration” on page 358.

MicrosoftSQL Serverdatabasesystem

dbalias="//host:port;DatabaseName=dbname"

7. Modify the host and port values as necessary.8. Save your changes and exit the text editor.9. Re-jar the ojb-conf.jar file with the updated information.

v Linux UNIX (The following lines are part of a single command. Theperiod at the end is part of the command)/opt/IBM/WebSphere/AppServer/java/bin/jar

cf /opt/IBM/InformationServer/ASBServer/apps/lib/ojb-conf.jar .

v Windows (The following lines are part of a single command. The period atthe end is part of the command)C:\IBM\WebSphere\AppServer\java\bin\jar cf

C:\IBM\InformationServer\ASBServer\apps\lib\ojb-conf.jar .


10. Locate the database.properties file. This file is located in theASBServer/bin/sql/ subdirectory of the IBM InfoSphere Information Serverinstallation directory.

11. Edit the file as follows:a. Use a text editor to open the file.b. In the file, locate the url keyword and value:

Table 99. URL keyword and value format for different database systems

Databasesystem url keyword and value

IBM DB2databasesystem

url=jdbc\:db2\://host\:port/dbname

Oracledatabasesystem andOracle RAC

url=jdbc\:ibm\:oracle\://host\:port;SID=SID

MicrosoftSQL Serverdatabasesystem

url=jdbc\:ibm\:sqlserver\://host\:port;DatabaseName=dbname

c. Change host and port to the same values that you specified in step 7 onpage 293.

d. Save the file.12. Restart WebSphere Application Server.13. For DB2 clustered or HADR configurations, update automatic client reroute

with the new host name and port information. See “Configuring automaticclient reroute” on page 342.

14. Log in to the WebSphere Application Server administrative console. Use theWebSphere Application Server administrator username and password.

15. Click Resources → JDBC → Data sources.16. Do the following steps for the ASB JDBC DataSource, ASB JDBC XA

DataSource, and Jreport JDBC DataSource data sources:a. Click the data source name in the window.b. Under Additional Properties, click Custom Properties.c. Modify the connection properties.d. In the Messages area at the top of the page, click Apply and then click

Save to apply changes to the master configuration.e. Click the Save button again in the next page.f. Return to the Data sources page, click the data source that you modified,

and click Test Connection.17. For clustered metadata repository configurations (DB2 clustering or HADR,

Oracle RAC), also update the alternate database host name and portinformation in WebSphere Application Server. See “Specifying the alternatedatabase address and port for IBM WebSphere Application Server” on page342.

18. Log out of the console.19. Restart WebSphere Application Server.


20. Update the values in the Version.xml file. This file contains the installationrecords that are used by the installation program. Keeping the file currentavoids problems with future installations.The Version.xml file is located in the IBM InfoSphere Information Serverinstallation directory on the same server as the ojb-conf.jar file.Edit the fileas follows:a. Use a text editor to open the Version.xml file.b. In the file, locate the following XML element:

<PersistedVariable encrypted="false" name="xmeta.db.hostname"persistent="true" readonly="true" value="myserver\isdev"/>

c. Modify the value attribute.d. In the file, locate the following XML element:

<PersistedVariable encrypted="false" name="xmeta.db.port"persistent="true" readonly="true" value="1433"/>

e. Modify the value attribute.f. If your IBM InfoSphere Information Analyzer analysis database is located

in the same database system as the metadata repository, locate thefollowing XML element:<PersistedVariable encrypted="false" name="ia.db.url"

persistent="true" readonly="true" value="jdbc:ibm:sqlserver://myserver\isdev:1433;DatabaseName=iadb"/>

g. Modify the value attribute.h. Save your changes.



Part 5. Creating highly available, scalable configurations

To reduce system downtime and increase the flexibility of your IBM InfoSphereInformation Server installation, you can design for high availability and scalability.

A highly available system maximizes the percentage of time that the systemservices are operational from the user point of view. To heighten availability, youimplement topologies and technologies that introduce redundancy. The aim is toreduce or eliminate the number of single points of failure (SPOF): elements that, ifthey fail, cause critical aspects of the system to stop operating.

IBM provides different high-availability solutions for each InfoSphere InformationServer tier. Each solution allows you to design a variety of different highlyavailable configurations, from relatively simple setups to complex installations.Most solutions involve the clustering of hardware and software components toprovide redundancy.



Chapter 22. Creating a two-server active-passive highavailability configuration

You can provide a basic level of high availability by configuring the IBMInfoSphere Information Server software tiers in an active-passive high availabilityconfiguration.

In a two-server active-passive high availability configuration, two computers sharea storage device. The metadata repository tier, engine tier, and services tier are allinstalled on the shared storage device. One of the computers (the active server)hosts the tiers. The other computer (the passive server) is started, but is notrunning any tier software. A high availability software product is installed on bothservers, such as IBM Tivoli System Automation for Multiplatforms on Linux orUNIX systems or Microsoft Cluster Service (MSCS) on Microsoft Windows systems.The high availability software maintains a heartbeat, which is a periodic signal fromthe active server to the passive server that indicates that the active server isoperational. If the active server fails, the heartbeat also fails. The high availabilitysoftware restarts all the services on the passive server. This process is called afailover.

With this configuration, a floating IP address and virtual host name are defined forthe server pair. This information is associated with the active server. All clientprograms connect to the server by using this address or host name. If the activeserver fails, the floating IP address and virtual host name are automaticallyreassociated with the passive server.

If you provide high availability for the services tier or metadata repository tier (orboth) by using other methods, you can choose to include only the remaining tiersin the active-passive configuration. For example, you might choose to implementan IBM WebSphere Application Server cluster for your services tier and an IBMDB2 Database for Linux, UNIX, and Windows cluster for your metadata repositorytier. In this case, the servers in your active-passive configuration host only theengine tier.

To set up a high availability configuration, you must have a solid understanding ofnetwork technologies such as protocols, layers, devices, and so on. Highlyavailable configurations, especially those that involve clustering, are technicallycomplex and require expertise to implement them successfully.

Creating an active-passive configuration (Linux, UNIX)For a Linux or UNIX installation, regardless of the high availability software thatyou use, you must complete the same basic steps to configure a two-serveractive-passive configuration.

Procedure1. Set up the hardware and cable the network.

The servers must be physically separate. Use identical hardware with identicalinternal storage, memory, and processing power.


The servers must be able to communicate with each other over high-speednetworks. To minimize single points of failure, each server must haveredundant connections to at least two physically separate high-speednetworks.To support failover when a problem occurs, the high availability softwarecreates a heartbeat signal between the servers. Set up at least two morephysically separate networks for this signal. These networks can be serial orother networks. The networks that carry the heartbeat signal must bephysically separate and isolated from the high-speed networks.

2. Install the high availability software on both the active server and the passiveserver.

3. Allocate an IP address and associate it with the virtual host name that theclient tier will use to connect to the IBM InfoSphere Information Serverserver-side components.

4. Mount the shared storage device in an identical mount point on each node.5. Use the appropriate high availability software administration tools to complete

the following steps:a. Create a resource group for the InfoSphere Information Server resources.b. Add a resource to manage the virtual IP address.c. Start the resource group.d. Ensure that the resource group is running on the primary server on which

InfoSphere Information Server is to run. Ensure that you can connect tothe primary server by using the virtual host name. Test failover andresolve any issues before continuing.

6. Create users and user groups on the shared storage device.7. On both servers, make sure that the directories that are listed in the following

table are shared, with identical mount points and local user permissions. Thedirectories might differ depending on your configuration.

Table 100. Directories for active-passive configuration

Configuration of tiers Directory

All Project directory. Default:/opt/IBM/InformationServer/Server/Projects

Engine tier on both servers InfoSphere Information Server installationdirectory. Default: /opt/IBM/InformationServer

Services tier on both servers IBM WebSphere Application Serverinstallation directory. Default:/opt/IBM/WebSphere

Metadata repository tier on both servers,IBM DB2 database system

v DB2 database system installationdirectory. Default: /opt/IBM/db2

v DB2 instance owner home directory.

v DB2 administrator home directory.

v DB2 fenced user home directory.

8. If the active-passive configuration will include only the engine tier (themetadata repository or services tiers are to be located outside of theactive-passive configuration), install and configure the metadata repositoryand services tiers first, before you continue with the engine tier installationand configuration. The engine tier installation requires that the metadata


repository tier and services tier are installed first, unless you install them all atthe same time in a single pass of the installation program.

9. Run the InfoSphere Information Server installation program on the primaryserver.When prompted by the installation program, specify the virtual host name.Whenever prompted for an installation directory, specify a path within themount point.

10. Replicate the /etc/services entries on both servers.11. Create scripts to start, stop, and monitor the servers. Store the scripts on the

shared storage device.Several sample high availability control scripts are included with InfoSphereInformation Server. You can use these scripts or modify them to fit yourconfiguration. See “High availability control scripts included with IBMInfoSphere Information Server” on page 320.

12. Use the appropriate high availability software administration tools to completethe following steps:a. If the engine tier is included in the high availability configuration, add the

InfoSvrEngine script or its equivalent resource agent script to the resourcegroup.

b. If the services tier or metadata repository tier is included in the highavailability configuration, add the InfoSvrServices script or its equivalentresource agent script to the resource group.

13. Test the setup by simulating different failures.

Example: Setting up an active-passive configuration by usingIBM Tivoli System Automation for Multiplatforms

This example describes how to set up a two-server active-passive high availabilityconfiguration by using Tivoli System Automation for Multiplatforms.

This example configuration is built on two Red Hat Enterprise Linux Serverservers. The servers are connected to each other over a single public network. Eachserver is also connected to a storage area network (SAN). All IBM InfoSphereInformation Server components are installed on the SAN. At any given time, onlyone of the servers is active; that is, it hosts the InfoSphere Information Servercomponents on the SAN. The other server is passive and does not access the SAN.

AIX Although this example is for Linux, most steps are identical in an AIXenvironment. Steps that differ are indicated.

The following diagram illustrates the example configuration:

Chapter 22. Creating a two-server active-passive high availability configuration 301

In this example, the following software is used for each server:v Red Hat Enterprise Linux Server 64-bitv IBM InfoSphere Information Server, Version 8.5v IBM WebSphere Application Server Network Deployment, Version 7.0 (installed

with the InfoSphere Information Server installation program)v IBM DB2 Database for Linux, UNIX, and Windows, Version 9.7 (installed with

the InfoSphere Information Server installation program)v IBM Tivoli System Automation for Multiplatforms (the version that is included

in the IBM DB2 9.7 installation package)

For storage, there is a storage area network (SAN) that is accessible to both servers.

To create the configuration in this example, follow these steps:1. Set up the hardware. Then configure the network, and configure mount points

to the storage area network (SAN). Finally, mount the SAN. See “Setting up theservers, network, and storage (System Automation for Multiplatformsexample)” on page 303.

2. Install System Automation for Multiplatforms on each server in the cluster, andthen create the first level automation domain. System Automation for

Computer B(Active)



Computer C(Passive)

Enginetier

Servicestier

Databaseinstance

Client tier

Computer A

Enginetier

(installed)

Servicestier

(installed)

Database

SAN

Public Network

Separate networkcarrying heartbeat

Figure 48. Example of a two-server active-passive high availability configuration


Multiplatforms is bundled with the IBM DB2 database system installationpackage. See “Installing the high availability software (System Automation forMultiplatforms example)” on page 304.

3. Define the virtual IP address. Then, configure System Automation forMultiplatforms so that the network adapters on the servers are appropriate andequivalent for the virtual IP address. See “Setting up the virtual IP address(System Automation for Multiplatforms example)” on page 305.

4. Define the resource group, and then create the automation policy by usingrelationship definitions. Create a network tiebreaker. Finally, activate theresource group. See “Defining and starting the resource group (SystemAutomation for Multiplatforms example)” on page 306.

5. Create users and user groups on the SAN. Then, run the InfoSphereInformation Server installation program. Finally, replicate the /etc/servicesentries on both servers. See “Installing IBM InfoSphere Information Server inthe cluster (System Automation for Multiplatforms example)” on page 309.

6. Set up scripts to start, stop, and monitor the servers. Then, create theapplication resources. See “Setting up the high availability control scripts(System Automation for Multiplatforms example)” on page 309.

7. To test the configuration, simulate active server failures and network failuresand observe the results. See “Testing the configuration (System Automation forMultiplatforms example)” on page 311.

Setting up the servers, network, and storage (SystemAutomation for Multiplatforms example)Set up the hardware. Then configure the network, and configure mount points tothe storage area network (SAN). Finally, mount the SAN.

About this task

The two servers in this example contain one network interface each (en0). The en0network interfaces are connected to each other through the external network cloudthat forms the public network. The following static IP addresses are assigned to theen0 adapters on the active and passive servers:v Active server (hostname myprimary): 192.0.2.0v Passive server (hostname mysecondary): 192.0.2.1

Procedure1. Set up the servers, network, and storage hardware.2. Adjust kernel parameters and user limits identically on both servers. For

information about these adjustments, see “Modifying kernel parameters anduser limits (Linux, UNIX)” on page 137.

3. Open the /etc/hosts file on each server. In each file, verify that the active andpassive server names are mapped to their corresponding public IP addresses.For example:192.0.2.0 myprimary.example.com myprimary192.0.2.1 mysecondary.example.com mysecondary

Defining the host names in the /etc/hosts file allows the servers to identifyeach other if a DNS server failure occurs. All servers in the cluster must havethe same entries in this file. In addition, all servers must have static IPaddresses.

4. Validate that the active and passive servers can ping each other successfullyover the public network: For example:


ping myprimaryping mysecondary

5. Create an identical directory on each server to be used as the mount point forthe shared SAN. Give the directory permissions of 775:mkdir /opt/IBMchmod 775 /opt/IBM

6. Open the /etc/fstab file on each server.

AIX The file to open is named /etc/filesystems.7. In each file, define the mount point for the shared SAN. For each mount point,

specify the noauto option to prevent the mount point from being automaticallymounted on more than one server in the cluster. For example:192.0.2.2:/newfs /opt/IBM nfs defaults 0 0

8. Mount the SAN on each server.9. On both servers, make sure that the following directories are shared, with

identical mount points and local user permissions:v /opt/IBM/InformationServer/Server/Projects

v /opt/IBM/InformationServer

v /opt/IBM/WebSphere

v /opt/IBM/db2

v DB2 instance owner home directory.v DB2 administrator home directory.v DB2 fenced user home directory.

Installing the high availability software (System Automation forMultiplatforms example)Install IBM Tivoli System Automation for Multiplatforms on each server in thecluster, and then create the first level automation domain. System Automation forMultiplatforms is bundled with the IBM DB2 database system installation package.

Procedure1. Install the System Automation for Multiplatforms base component on each

server. The installation directory must be on the local storage on each server,not on the storage area network (SAN).

2. Edit the /etc/profile file and ensure that the CT_MANAGEMENT_SCOPEenvironment variable is set to 2 for all users.

3. On each server that is to be part of the automation domain, run the preprpnodeto prepare security on the server so it can be defined in a peer domain./usr/sbin/rsct/bin/preprpnode myprimary mysecondary

4. Create the automation domain. In the example, a single automation domainnamed ha_domain is created that contains the myprimary and mysecondaryservers. To create the domain, run the mkrpdomain command on one of theservers (you can choose either server):mkrpdomain ha_domain myprimary mysecondary

After this command is run once on a server, any System Automation forMultiplatforms or Reliable Scalable Cluster Technology (RSCT) command canbe issued from any server in the automation domain.

5. The newly created automation domain has an operational state (OpState) ofoffline. Run the startrpdomain command to bring the domain online:startrpdomain ha_domain


Setting up the virtual IP address (System Automation forMultiplatforms example)Define the virtual IP address. Then, configure IBM Tivoli System Automation forMultiplatforms so that the network adapters on the servers are appropriate andequivalent for the virtual IP address.

Procedure1. Create a configuration file in the /opt/IBM/hascripts directory that defines the

virtual IP address and specifies the names of the servers to associate with theaddress. In this configuration example, a file named myserviceip.cfg is createdthat defines a virtual IP address named haip. The IPAddress value is thenetwork alias IP address. The NetMask value is the network mask of this IPaddress:PersistentResourceAttributes::

NodeNameList={"myprimary", "mysecondary"}Name="haip"NetMask=255.255.255.128IPAddress=192.0.2.10ResourceType=1

2. Run the mkrsrc command to create the virtual IP resource:mkrsrc -f /opt/IBM/hascripts/myserviceip.cfg IBM.ServiceIP

3. Run the lsrsrc command to verify that the resource was created correctly:lsrsrc -l IBM.ServiceIP

The command displays the virtual IP resource configuration. For example:Resource Persistent Attributes for IBM.ServiceIPresource 1:

Name = "haip"ResourceType = 0AggregateResource = "0x2029 0xffff 0x8657b47c 0x9cbcbccb 0x918205be 0xc296f798"IPAddress = "192.0.2.10"NetMask = "255.255.255.128"ProtectionMode = 1NetPrefix = 0ActivePeerDomain = "ha_domain"NodeNameList = {"mysecondary"}

resource 2:Name = "haip"ResourceType = 0AggregateResource = "0x2029 0xffff 0x8657b47c 0x9cbcbccb 0x918205be 0xc296f798"IPAddress = "192.0.2.10"NetMask = "255.255.255.128"ProtectionMode = 1NetPrefix = 0ActivePeerDomain = "ha_domain"NodeNameList = {"myprimary.example.com"}

resource 3:Name = "haip"ResourceType = 1AggregateResource = "0x3fff 0xffff 0x00000000 0x00000000 0x00000000 0x00000000"IPAddress = "192.0.2.10"NetMask = "255.255.255.128"ProtectionMode = 1NetPrefix = 0ActivePeerDomain = "ha_domain"NodeNameList = {"myprimary.example.com","mysecondary"}

4. Run the mkequ command to create an equivalency definition that specifies thenetwork adapters that are to carry the virtual IP address. For example, thefollowing command creates a static equivalency that is named ha_nieq:mkequ ha_nieq IBM.NetworkInterface:eth0:myprimary,eth0:mysecondary

5. Run the lsequ command to verify the equivalency definition:lsequ -e ha_nieq


The command displays the equivalency definition configuration. For example:Displaying Equivalency information:For Equivalency "ha_nieq".

Equivalency 1:Name = ha_nieqMemberClass = IBM.NetworkInterfaceResource:Node[Membership] = {eth0:myprimary.example.com,eth0:mysecondary}SelectString = ""SelectFromPolicy = ANYMinimumNecessary = 1Subscription = {}Color = 0ActivePeerDomain = ha_domainConfigValidity =

6. On both servers, in the /etc/hosts file, add the mapping for the virtual hostname to the virtual IP address. For example:192.0.2.10 ha_rg ha_rg.example.com

Defining and starting the resource group (System Automation forMultiplatforms example)Define the resource group, and then create the automation policy by usingrelationship definitions. Create a network tiebreaker. Finally, activate the resourcegroup.

Procedure1. Run the mkrg command to create a resource group. In this configuration

example, the resource group that is created is named ha_rg:mkrg ha_rg

2. Run the addrgmbr command to add the virtual IP address and applicationresources to the resource group.addrgmbr -g ha_rg IBM.ServiceIP:haip

3. Run the lsrg command to verify the resource group:lsrg -m

The command displays the resource group definition.Displaying Member Resource information:Class:Resource:Node[ManagedResource] Mandatory MemberOf OpState WinSource LocationIBM.ServiceIP:haip True ha_rg offline Nominal myprimary

4. Run the mkrel command to define the relationship between the virtual IPresource (haip) and the network interface equivalency (ha_nieq). The virtualIP depends on the network interface equivalency to be active.mkrel -p DependsOn -S IBM.ServiceIP:haip -G IBM.Equivalency:ha_nieq

haip_dependson_ha_nieq

5. Run the lsrel command to verify the relationships:lsrel -l

The command displays managed relations.Displaying Managed Relations :

Managed Relationship 1:Name = haip_dependson_ha_nieqClass:Resource:Node[Source] = IBM.ServiceIP:haipResourceGroup[Source] = ha_rg

6. Create a network quorum (tiebreaker). The tiebreaker ensures that SystemAutomation for Multiplatforms can decide which node still owns the cluster ifcommunication between the nodes is lost. This safeguard prevents processesfrom being started on both nodes simultaneously.


a. Edit the /usr/sbin/cluster/netmon.cf file on both servers. In each file,add the IP address of each server.cat /usr/sbin/cluster/netmon.cf192.0.2.0192.0.2.1

b. Run the mkrsrc command to create the network tie breaker:mkrsrc IBM.TieBreaker Type="EXEC" Name="ha_nettiebkr" DeviceInfo=’PATHNAME=

/usr/sbin/rsct/bin/samtb_net Address=192.0.2.24 Log=1 Count=2’PostReserveWaitTime=30;

The network address used in the command (192.0.2.24 in the example) canbe any valid IP address that responds to the ping command from bothnodes.

c. Run the chrsrc command to set the persistent attributes for the tie breaker:chrsrc -c IBM.PeerNode OpQuorumTieBreaker="ha_nettiebkr"

d. Run the lsrsrc command to verify that the tie breaker is created:lsrsrc -Ab IBM.TieBreaker

The command displays the attributes for the tie breaker.Resource Persistent and Dynamic Attributes for IBM.TieBreakerresource 1:

Name = "ha_nettiebkr"Type = "EXEC"DeviceInfo = "PATHNAME=/usr/sbin/rsct/bin/samtb_net

Address=192.0.2.24 Log=1 Count=2"ReprobeData = ""ReleaseRetryPeriod = 0HeartbeatPeriod = 0PreReserveWaitTime = 0PostReserveWaitTime = 30NodeInfo = {}ActivePeerDomain = "ha_domain"ConfigChanged = 0

resource 2:Name = "Fail"Type = "Fail"DeviceInfo = ""ReprobeData = ""ReleaseRetryPeriod = 0HeartbeatPeriod = 0PreReserveWaitTime = 0PostReserveWaitTime = 0NodeInfo = {}ActivePeerDomain = "ha_domain"ConfigChanged = 0

resource 3:Name = "Operator"Type = "Operator"DeviceInfo = ""ReprobeData = ""ReleaseRetryPeriod = 0HeartbeatPeriod = 0PreReserveWaitTime = 0PostReserveWaitTime = 0NodeInfo = {}ActivePeerDomain = "ha_domain"ConfigChanged = 0

7. Run the chrg command to activate the resource group and all of the resourcesthat are defined as its members:chrg -o online ha_rg

8. Run the lsrg command to verify the status of the resource group:


lsrg -g ha_rg

The command displays information for the specified resource group.Displaying Resource Group information:For Resource Group "ha_rg".Resource Group 1:

Name = ha_rgMemberLocation = CollocatedPriority = 0AllowedNode = ALLNominalState = OnlineExcludedList = {}Subscription = {}Owner =Description =InfoLink =Requests = {}ActivePeerDomain = ha_domainOpState = OnlineTopGroup = ha_rgConfigValidity =TopGroupNominalState = Online

9. Run the lssam command to check the status of the cluster:lssam

The command displays the status of each component of the cluster.Online IBM.ResourceGroup:ha_rg Nominal=Online

’- Online IBM.ServiceIP:haip|- Online IBM.ServiceIP:haip:myprimary’- Offline IBM.ServiceIP:haip:mysecondary

10. Test the cluster to verify that it is working correctly.a. Verify that the virtual IP address connects to the primary node.b. Run the rgreq command to force a failover to the secondary node. In the

command, specify the name of the secondary node and the resource groupname.rgreq –o move –n mysecondary ha_rg

c. Run the lssam command again to check the status of the cluster:lssam

If the failover was successful, the command output indicates that theprimary node is now offline and the secondary node is online.Online IBM.ResourceGroup:ha_rg Nominal=Online

’- Online IBM.ServiceIP:haip|- Offline IBM.ServiceIP:haip:myprimary’- Online IBM.ServiceIP:haip:mysecondary

d. Verify that the virtual IP address now connects to the secondary node.e. Run the rgreq command to force a failover back to the primary node.

rgreq –o move –n myprimary ha_rg

f. Run the lssam command again to check the status of the cluster:lssam

If the failover was successful, the command output indicates that thesecondary node is now offline and the primary node is online.Online IBM.ResourceGroup:ha_rg Nominal=Online



Installing IBM InfoSphere Information Server in the cluster(System Automation for Multiplatforms example)Create users and user groups on the storage area network (SAN). Then, run theInfoSphere Information Server installation program. Finally, replicate the/etc/services entries on both servers.

Procedure1. On the storage area network (SAN), create all users and user groups. The

following sample Linux commands create some of the administrator useraccounts and groups. In the example, the SAN is mounted at opt/IBM:/usr/sbin/groupadd db2iadm1/usr/sbin/groupadd db2fadm1/usr/sbin/groupadd dasadm1/usr/sbin/groupadd xmeta/usr/sbin/groupadd isuser/usr/sbin/groupadd dstage


AIX The following sample AIX commands create some of theadministrator 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


For details about creating administrator users and groups, see “Setting upadministrator and owner accounts” on page 142.

2. Run the InfoSphere Information Server installation program in Graphical Modeas described in “Running the installation program for Scenario C” on page 204.Whenever you are prompted for a directory, choose a directory from the mountpoint (/opt/IBM).In the High Availability Server Cluster Configuration page, click This is anactive-passive server cluster configuration. In the Virtual host name field,enter the virtual host name (ha_rg.example.com in this example).

3. Allow the installation program to complete.4. Replicate the /etc/services entries on both servers.

Setting up the high availability control scripts (SystemAutomation for Multiplatforms example)Set up scripts to start, stop, and monitor the servers. Then, create the applicationresources.


About this task

Several sample high availability control scripts are supplied with IBM InfoSphereInformation Server. These scripts are used in this example. See “High availabilitycontrol scripts included with IBM InfoSphere Information Server” on page 320.

Procedure1. Copy the script files to a directory on the storage area network (SAN). For

example: /opt/IBM/hascripts2. Create an application resource configuration file for the services tier. Put the

file in the same directory as the script files. For example: /opt/IBM/hascripts.The following sample file defines an application resource for the services tier.The file is named /opt/IBM/hascripts/InfoSvrServices.IBM.Application:PersistentResourceAttributes::

Name="ServicesApp"StartCommand="/opt/IBM/hascripts/InfoSvrServices start"StopCommand="/opt/IBM/hascripts/InfoSvrServices stop"MonitorCommand="/opt/IBM/hascripts/InfoSvrServices status"MonitorCommandPeriod=60MonitorCommandTimeout=60NodeNameList={"myprimary","mysecondary"}StartCommandTimeout=240StopCommandTimeout=240UserName="root"ResourceType=1

3. Run the mkrsrc command to create the application resource for the servicestier:mkrsrc -f /opt/IBM/hascripts/InfoSvrServices.IBM.Application IBM.Application

4. Create an application resource configuration file for the engine tier. Thefollowing sample file defines an application resource for the engine tier. Thefile is named /opt/IBM/hascripts/InfoSvrEngine.IBM.Application:PersistentResourceAttributes::

Name="EngineApp"StartCommand="/opt/IBM/hascripts/InfoSvrEngine start"StopCommand="/opr/hascripts/InfoSvrEngine stop"MonitorCommand="/opt/IBM/hascripts/InfoSvrEngine status"MonitorCommandPeriod=60MonitorCommandTimeout=60NodeNameList={"myprimary","mysecondary"}StartCommandTimeout=240StopCommandTimeout=240UserName="root"ResourceType=1

5. Run the mkrsrc command to create the application resource for the enginetier:mkrsrc -f /opt/IBM/hascripts/InfoSvrEngine.IBM.Application IBM.Application

6. Run the rgreq command to lock the ha_rg resource group:rgreq -o lock ha_rg

7. Run the addrgmbr command to add the services tier application resource tothe resource group ha_rg that was created:addrgmbr -g ha_rg IBM.Application:ServicesApp

8. Run the addrgmbr command to add the engine tier application resource to theresource group ha_rg that was created:addrgmbr -g ha_rg IBM.Application:EngineApp


9. Run the mkrel command to define the relationship between the InfoSphereInformation Server services tier application resource (ServicesApp) and thevirtual IP resource (haip):mkrel -p StartAfter -S IBM.Application:ServicesApp -G IBM.ServiceIP:haip

ServicesApp_startafter_haip

10. Run the mkrel command to define the relationship between the InfoSphereInformation Server engine tier application resource (EngineApp) and thevirtual IP resource (haip):mkrel -p StartAfter -S IBM.Application:EngineApp -G IBM.ServiceIP:haip

EngineApp_startafter_haip

11. Run the lsrel command to verify the relationships:lsrel -l

The command displays all the managed relations:Displaying Managed Relations :

Managed Relationship 1:Name = haip_dependson_ha_nieqClass:Resource:Node[Source] = IBM.ServiceIP:haipResourceGroup[Source] = ha_rg

Managed Relationship 2:Name = ServicesApp_startafter_haipClass:Resource:Node[Source] = IBM.Application:ServicesAppResourceGroup[Source] = ha_rg

Managed Relationship 3:Name = EngineApp_startafter_haipClass:Resource:Node[Source] = IBM.Application:EngineAppResourceGroup[Source] = ha_rg

12. Run the rgreq command again to unlock the resource group:rgreq -o unlock ha_rg

Testing the configuration (System Automation for Multiplatformsexample)To test the configuration, simulate active server failures and network failures andobserve the results.

About this task

During the test, run the lssam command periodically to view the status of theservers in the cluster. When the active server in the cluster is operational and thepassive server is on standby, the lssam command displays output like thisexample:Online IBM.ResourceGroup:ha_rg Nominal=Online

|- Online IBM.Application:EngineApp|- Online IBM.Application:EngineApp:myprimary’- Offline IBM.Application:EngineApp:mysecondary

|- Online IBM.Application:ServicesApp|- Online IBM.Application:ServicesApp:myprimary’- Offline IBM.Application:ServicesApp:mysecondary


The first line indicates the resource group. In the above example, the resourcegroup name is ha_rg.


The following lines indicate the status of the member resources: EngineApp (theIBM InfoSphere Information Server engine tier control application), ServicesApp(the InfoSphere Information Server services tier and metadata repository tiercontrol application), and haip (the virtual IP resource). Resources and constituentservers can be in any of the following states:v Online: The resource was started and is functioning normally:v Offline: The resource was stopped successfully.v Failed Offline: The resource malfunctioned.

Procedure1. Run the lssam command to verify that the active server in the cluster is

operational and functioning normally.2. Simulate a power failure on the active server. For example, turn off the power

or unplug the power cable. Verify that all resources fail over to the otherserver and remain online there.

3. Run the lssam command to verify that the failover was successful. Thecommand output is similar to the following text:Online IBM.ResourceGroup:ha_rg Nominal=Online

|- Online IBM.Application:EngineApp|- Failed offline IBM.Application:EngineApp:myprimary Node=Offline’- Online IBM.Application:EngineApp:mysecondary

|- Online IBM.Application:ServicesApp|- Failed offline IBM.Application:ServicesApp:myprimary Node=Offline’- Online IBM.Application:ServicesApp:mysecondary

’- Online IBM.ServiceIP:haip|- Failed offline IBM.ServiceIP:haip:myprimary Node=Offline’- Online IBM.ServiceIP:haip:mysecondary

These lines indicate that the application resource failed over successfully tothe passive server (mysecondary). Also, the virtual IP resource failed oversuccessfully. Verify that the formerly active server (myprimary) is now in thefailed offline state.

4. Use an InfoSphere Information Server client to access the system and verifythat it is functioning normally.

5. Restore power to the formerly active server (myprimary).6. Run the lssam command. The command output is similar to the following

text:Online IBM.ResourceGroup:ha_rg Nominal=Online

|- Online IBM.Application:EngineApp|- Offline IBM.Application:EngineApp:myprimary’- Online IBM.Application:EngineApp:mysecondary

|- Online IBM.Application:ServicesApp|- Offline IBM.Application:ServicesApp:myprimary’- Online IBM.Application:ServicesApp:mysecondary

’- Online IBM.ServiceIP:haip|- Offline IBM.ServiceIP:haip:myprimary’- Online IBM.ServiceIP:haip:mysecondary

Verify that the formerly active server (myprimary) is now in the offline state.You might need to run the command several times before the status isdisplayed as shown in the preceding text.

7. Simulate a power failure on the formerly passive (mysecondary) server. Verifythat all resources fail over to the myprimary server and remain online there.

8. Run the lssam command to verify that the failover was successful. Thecommand output is similar to the following text:Online IBM.ResourceGroup:ha_rg Nominal=Online

|- Online IBM.Application:EngineApp|- Online IBM.Application:EngineApp:myprimary


’- Failed offline IBM.Application:EngineApp:mysecondary Node=Offline|- Online IBM.Application:ServicesApp

|- Online IBM.Application:EngineApp:myprimary’- Failed offline IBM.Application:EngineApp:mysecondary Node=Offline

’- Online IBM.ServiceIP:haip|- Online IBM.ServiceIP:haip:myprimary’- Failed offline IBM.ServiceIP:haip:mysecondary Node=Offline

These lines indicate that the application resource failed over successfully tothe myprimary server. Also, the virtual IP resource failed over successfully.Verify that the mysecondary server is now in the failed offline state. Youmight need to run the command several times before the status is displayedas shown in the preceding text.

9. Use an InfoSphere Information Server client to access the system and verifythat it is functioning normally.

10. Restore power to the mysecondary server.11. Run the lssam command. The command output is similar to the following

text:Online IBM.ResourceGroup:ha_rg Nominal=Online

|- Online IBM.Application:EngineApp|- Online IBM.Application:EngineApp:myprimary’- Offline IBM.Application:EngineApp:mysecondary

|- Online IBM.Application:ServicesApp|- Online IBM.Application:EngineApp:myprimary’- Offline IBM.Application:EngineApp:mysecondary


Verify that the mysecondary server is now in the offline state. You might needto run the command several times before the status is displayed as shown inthe preceding text.

12. Repeat steps 1 through 11. During this test cycle, restart each server in turninstead of disabling power. For example, to restart a server, you can log in tothe server as root and run the reboot command.

13. Repeat steps 1 through 11. During this test cycle, simulate a network failureby disconnecting the public network cable from each server in turn.

Creating an active-passive configuration (Microsoft Windows)Regardless of the Microsoft Windows operating system version that you use, youmust complete the same basic steps to configure a two-server active-passiveconfiguration.

Procedure1. Set up the servers and storage, and cable the network.

The servers must be able to communicate with each other over high-speednetworks. To minimize single points of failure, each server must haveredundant connections to at least two physically separate high-speednetworks.To support failover when a problem occurs, the high availability softwarecreates a heartbeat signal between the servers. Set up at least two morephysically separate networks for this signal. The networks that carry theheartbeat signal must be physically separate and isolated from the high-speednetworks.Each server must connect to issued storage device. The storage device can beconnected to each server by using a Fibre Channel Switch or SCSI interface.


The storage device is listed as a local disk on both servers. At any given time,only one node has exclusive access to the storage device.Configure a separate server as the Windows domain controller.

2. Install the operating system on both servers. The operating system includeshigh availability functions.

3. Set up the cluster. Verify that all cluster resources are running correctly, andthat all resources failover properly from server to server.

4. Set up the virtual IP address.5. Create users and user groups on the shared storage device.6. On both servers, make sure that the directories that are listed in the following

table are shared. The directories might differ depending on yourconfiguration.

Table 101. Directories for active-passive configuration

Configuration of tiers Directory

All Project directory. Default:C:\IBM\InformationServer\Server\Projects

Engine tier on both servers IBM InfoSphere Information Serverinstallation directory. Default:C:\IBM\InformationServer

Services tier on both servers IBM WebSphere Application Serverinstallation directory. Default:C:\IBM\WebSphere

Metadata repository tier on both servers,IBM DB2 database system

v DB2 database system installationdirectory. Default: C:\IBM\db2

v DB2 administrator home directory.

7. If the active-passive configuration will include only the engine tier (themetadata repository or services tiers are to be located outside of theactive-passive configuration), install and configure the metadata repositoryand services tiers first, before you continue with the engine tier installationand configuration. The engine tier installation requires that the metadatarepository tier and services tier are installed first, unless you install them all atthe same time in a single pass of the installation program.

8. Run the InfoSphere Information Server installation program on the primaryserver.When prompted by the installation program, specify the virtual host name.Whenever prompted for an installation directory, specify a path within theshared storage device.

9. Cause a failover to the backup server.10. Delete the InfoSphere Information Server installation directory on the shared

storage device, and repeat the installation on the backup server.11. Create scripts to start and stop the servers. Store the scripts on the shared

storage device.Several sample high availability control scripts are included with InfoSphereInformation Server. You can use these scripts or modify them to fit yourconfiguration. See “High availability control scripts included with IBMInfoSphere Information Server” on page 320.

12. Use the appropriate high availability software administration tools to do thefollowing steps:


a. If the engine tier is included in the high availability configuration, create aGeneric Application resource for the InfoSvrEngine script or an equivalentscript.

b. If the services tier or metadata repository tier is included in the highavailability configuration, create a Generic Application resource for theInfoSvrServices script or an equivalent script.

13. Test the setup by simulating different failures.

Example: Setting up an active-passive configuration by usingthe Microsoft Cluster service (MSCS)

This example describes how to set up a two-server active-passive high availabilityconfiguration by using the Microsoft Cluster service in Microsoft Windows Server2003

This example configuration is built on two Microsoft Windows Server 2003 servers.The servers are connected to each other over a single public network. Each serveris also connected to a storage area network (SAN). All IBM InfoSphere InformationServer components are installed on the SAN. At any given time, only one of theservers is active; that is, it hosts the InfoSphere Information Server components onthe SAN. The other server is passive and does not access the SAN.

The following diagram illustrates the example configuration:


In this example, the following software is used for each server:v Microsoft Windows Server 2003 64-bitv IBM InfoSphere Information Server, Version 8.5v IBM WebSphere Application Server Network Deployment, Version 7.0 (installed

with the InfoSphere Information Server installation program)v IBM DB2 Database for Linux, UNIX, and Windows, Version 9.7 (installed with

the InfoSphere Information Server installation program)

For storage, there is a shared storage area network (SAN) that is accessible to bothservers. The SAN is connected to the servers through a Fibre Channel switch.

To create the configuration in this example, follow these steps:1. Set up the hardware. Then configure the network, and configure the connection

to the storage area network (SAN). See “Setting up the servers, network, andstorage (MSCS example)” on page 317.

2. Use the Cluster Configuration Wizard to set up the cluster. See “Setting up thecluster (MSCS example)” on page 317.

3. Create resources for the virtual IP address and virtual host name. Then, mapthe virtual host name to the virtual IP address in the etc\hosts file on each

Computer B(Active)



Computer C(Passive)

Enginetier

Servicestier

Databaseinstance

Client tier

Computer A

Enginetier

(installed)

Servicestier

(installed)

Database

SAN

Public Network

Private networkcarrying heartbeat

Fibre Channel Switch

Figure 49. Example of a two-server active-passive high availability configuration


server. Finally, add environment variables that specify the virtual host name.See “Setting up the virtual IP address (MSCS example)” on page 318.

4. Create users and user groups on the SAN. Then, run the InfoSphereInformation Server installation program on the primary server. Finally, cause afailover to the backup server, and run the installation program on the backupserver. See “Installing IBM InfoSphere Information Server in the cluster (MSCSexample)” on page 318.

5. Set up scripts to start and stop the servers. Then, create the applicationresources. See “Setting up high availability control scripts (MSCS example)” onpage 319.

6. Use the Cluster Administrator tool to test the configuration, simulate activeserver failures and network failures, and observe the results. See “Testing theconfiguration (MSCS example)” on page 319.

Setting up the servers, network, and storage (MSCS example)Set up the hardware. Then configure the network, and configure the connection tothe storage area network (SAN).

About this task

See the Microsoft Cluster Service (MSCS) documentation for details on each of thefollowing steps.

Procedure1. Set up the servers, network, and storage hardware.2. Install the Windows Server 2003 operating system on both servers.3. Within Windows on each server, rename the local area network icons so that

they reflect the purpose of each network. For example, name the publicnetwork icon "Public". Name the private network icon "Private".

4. Configure the binding order for the networks on each server. Set up thefollowing order: Public, then Private, then Remote Access Connections.

5. Configure the private network adapter on each server. Set the protocol toTCP/IP, and specify a static IP address. Specify a network speed, and duplexmode.

6. Configure the public network adapter on each server. Specify a static IPaddress. Verify connectivity by pinging all IP addresses from each server.

7. Add the servers to the same domain in the domain controller. Verify that eachserver can access the domain controller

8. Set up a domain user account that is dedicated to the Cluster service.9. Set up a quorum disk. The quorum disk is a separate disk that stores

checkpoint data and other information that is required for cluster operation.10. Verify that the SAN can be accessed from both servers, and that it is

functioning properly.

Setting up the cluster (MSCS example)Use the Cluster Configuration wizard to set up the cluster.

About this task

For detailed information about each step in the procedure, see the MicrosoftCluster Service (MSCS) documentation.


Procedure1. Turn off the backup server. Turn on the storage area network (SAN).2. Log in to the primary server. Use a domain account that has local

administrator privileges.3. Using the Cluster Administrator (CluAdmin.exe) tool, do the following

configuration tasks to configure the primary server.a. Specify a unique NetBIOS cluster name.b. Make the server the first node in the cluster.c. Analyze the node to make sure that there are no hardware or software

problems that might interfere with the cluster configuration.d. Associate the IP address of the cluster with the public network.e. Specify the name of the domain account that you created that is dedicated

to the Cluster service.f. Create the cluster.

4. Use the Cluster Administrator tool to verify that all cluster resources arerunning correctly.

5. Leave the primary server and SAN on. Turn on the backup server.6. Use the Cluster Administrator tool to add the backup server to the cluster.7. Use the Cluster Administrator tool to configure the heartbeat and prioritize

the network adapters for the private network.8. Use the Cluster Administrator tool to configure the quorum disk.9. Set up a boot delay so that simultaneous restoration of power to all nodes

does not cause the Cluster service to fail to start.10. Test that all resources failover properly from server to server.

Setting up the virtual IP address (MSCS example)Create resources for the virtual IP address and virtual host name. Then, map thevirtual host name to the virtual IP address in the etc\hosts file on each server.Finally, add environment variables that specify the virtual host name.

About this task


Procedure1. Use the Cluster Administrator tool to create a resource for the virtual IP

address. Use the IP address resource type.2. Use the Cluster Administrator tool to create a resource for the virtual host

name. Use the Network Name resource type.3. On each server, open the C:\Windows\System32\drivers\etc\hosts file. In each

file, map the virtual host name to the virtual IP address.

Installing IBM InfoSphere Information Server in the cluster(MSCS example)Create users and user groups on the storage area network (SAN). Then, run theInfoSphere Information Server installation program on the primary server. Finally,cause a failover to the backup server, and run the installation program on thebackup server.


Procedure1. On the SAN, create all users and user groups. For details about creating

administrator users and groups, see Setting up administrator and owneraccounts.

2. Run the InfoSphere Information Server installation program on the primaryserver in Graphical Mode. See “Starting the installation program” on page 177.Whenever you are prompted for a directory, specify a directory that is locatedon the SAN.In the High Availability Server Cluster Configuration page, click This is anactive-passive server cluster configuration. In the Virtual host name field,enter the virtual host name.

3. Allow the installation program to finish.4. Cause a failover to the backup server. See the Microsoft Cluster Service (MSCS)

documentation for more information.5. Delete the InfoSphere Information Server installation folder on the SAN.6. Run the InfoSphere Information Server installation program on the backup

server in Graphical Mode. Be sure to specify the same user names, passwords,and path names as you did when you ran the installation program on theprimary server.

Setting up high availability control scripts (MSCS example)Set up scripts to start and stop the servers. Then, create the application resources.

About this task

Several sample high availability control scripts are supplied with InfoSphereInformation Server. These scripts are used in this example. See “High availabilitycontrol scripts included with IBM InfoSphere Information Server” on page 320.

Procedure1. Copy the script files to a directory on the storage area network (SAN).2. Use the Cluster Administrator to create a Generic Application resource for each

of the scripts. Make sure that the application resources start only when thevirtual IP address is available.For detailed information about the Cluster Administrator, see the MicrosoftCluster Service (MSCS) documentation.

Testing the configuration (MSCS example)Use the Cluster Administrator tool to test the configuration, simulate active serverfailures and network failures, and observe the results.

About this task


Procedure1. Using the Cluster Administrator tool, verify that all cluster resources are

running correctly.2. Simulate a power failure on the active server. For example, turn off the power

or unplug the power cable.3. Verify that all resources fail over to the other server and remain online there.


4. Use an IBM InfoSphere Information Server client to access the system andverify that it is functioning normally.

5. Restore power to the formerly active server.6. Verify that the formerly active server is now in the offline state.7. Simulate a power failure on the formerly passive server.8. Verify that all resources fail over to the active server and remain online there.

Verify that the passive server is now in the failed offline state.9. Use an InfoSphere Information Server client to access the system and verify

that it is functioning normally.10. Restore power to the passive server.11. Verify that the backup server is now in the offline state12. Repeat the previous steps. During this test cycle, restart each server in turn

instead of disabling power. For example, to restart a server, you can log in tothe server and run the reboot command.

13. Repeat the previous steps. During this test cycle, simulate a network failure bydisconnecting the public network cable from each server in turn.

High availability control scripts included with IBM InfoSphereInformation Server

Several sample high availability control scripts are included with InfoSphereInformation Server. To enable your high availability software to start or stop tiersand components, set up these files as application resources within the highavailability software.

These scripts are installed by the InfoSphere Information Server installationprogram in the following directory:

1. Linux UNIX installdir/InformationServer/HAScripts

2. Windows installdir\InformationServer\HAScripts

Within your high availability configuration, you can use these scripts as they are,or modify them so that they work in your environment. The following table listsand describes the scripts that are available:

Table 102. Sample scripts that are supplied with InfoSphere Information Server

Script Description

InfoSvrEngine Starts or stops the InfoSphere InformationServer engine tier. Calls ISFAgents as part ofits operation.

InfoSvrServices Starts or stops the InfoSphere InformationServer services tier. Calls ISFRepos andISFServer scripts as part of its operation.

ISFAgents Calls the NodeAgents.sh script to start orstop InfoSphere Information Server ASBnode agents.

ISFServer Calls the MetadataServer.sh script to start orstop IBM WebSphere Application Server.


Table 102. Sample scripts that are supplied with InfoSphere Information Server (continued)

Script Description

ISFRepos Called by the InfoSvrServices script in anactive-passive configuration where an IBMDB2 database system hosts the metadatarepository tier. Starts or stops a local DB2database system instance. The DB2 databasesystem must run on the same server as otherInfoSphere Information Server components.Assumes that the DB2 database system isinstalled on shared storage that is mountedidentically on both servers.

The set of scripts you use depends on which tiers you configure in theactive-passive high-availability configuration. The following table lists the scripts touse based on the tiers that you include in your configuration:

Table 103. Tiers and resource agent scripts

Tier Sample resource agent scripts

Engine v InfoSvrEngine

v ISFAgents

Services v InfoSvrServices

v ISFServer

Metadata repository v InfoSvrServices

v ISFRepos



Chapter 23. WebSphere Application Server clustering for highavailability and scalability

You can set up a clustered environment for high availability, failover, andscalability. First, you determine an appropriate cluster topology, and then youinstall and configure the appropriate version of IBM WebSphere Application ServerNetwork Deployment, set up clusters, and install a front-end Web server.

To deploy a highly available topology, you must have a solid understanding ofnetwork technologies such as protocols, layers, devices, and so on. Highlyavailable topologies, especially topologies that involve clustering, are technicallycomplex, and require expertise to implement successfully.

You choose an appropriate cluster topology based on your system requirements(level of high availability needed, level of security needed, hardware equipmentavailable, and so on). The cluster topology can include one or more clusteredapplication servers, each running cloned copies of IBM InfoSphere InformationServer, one or more front-end Web servers (or hardware or software loadbalancers), one or more firewalls, and so on.

Refer to theWebSphere Application Server information center for information aboutcluster configurations and manual tuning:v Version 6.1: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jspv Version 7.0: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp

General considerations for clustering on WebSphere ApplicationServer

IBM WebSphere Application Server Network Deployment provides control over thedesign of the cluster environment through the deployment manager, managednodes, and unmanaged nodes (stand-alone InfoSphere Information Serverinstances):v You can define multiple Network Deployment cells with their own deployment

manager.v You can install multiple deployment managers on the same computer.v You can install a deployment manager separately on a dedicated computer, or a

deployment manager can share the same computer with another InfoSphereInformation Server managed node or stand-alone InfoSphere Information Serverinstance.

When you create a cluster, be aware of these InfoSphere Information Server-specificrestrictions:v All managed nodes that are participating in a cluster must run on the same

operating system. For example, in a cluster, there cannot be one managed noderunning on a Windows system and another managed node on a UNIX system.

v Each InfoSphere Information Server cluster must have its own dedicatedNetwork Deployment domain (or "cell").

That is, within a cell in which an InfoSphere Information Server cluster isdeployed, do not deploy any other type of server (which includes: InfoSphereInformation Server cluster, IBM InfoSphere Master Data Management Server server,


http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp

InfoSphere Information Server stand-alone server, or any standard applicationserver instance that runs J2EE applications).

Implementing a WebSphere Application Server cluster for InfoSphereInformation Server

After you choose a cluster topology for IBM InfoSphere Information Server, youmust install and configure the appropriate version of IBM WebSphere ApplicationServer Network Deployment. Then, you set up a cluster, install a front-end Webserver, and optionally install a front-end load balancer and additional components.

Installing IBM WebSphere Application Server NetworkDeployment for a cluster installation

IBM InfoSphere Information Server supports IBM WebSphere Application ServerNetwork Deployment, Versions 6.1 and 7.0. You must install a supported version.

Before you beginv Determine the cluster topology that you want to use, based on your system

requirements.v On the computer where you will install the deployment manager and on all

computers that will host a managed node, configure the system to support alarge number of file descriptors.Refer to your system administrator if you are not familiar with file descriptorallocations.For example, if your login shell is /bin/bash, do the following tasks:

– Linux Add the following line to the /etc/profile file:ulimit -n 10240

– Linux Add the following lines to the /etc/security/limits.conf file:* soft nofile 10240* hard nofile 10240

– AIX Configure the following environment variable in /etc/profile forsystem-wide change.unset LDR_CNTRL

Procedure1. Install IBM WebSphere Application Server Network Deployment on all the

computers that will host the InfoSphere Information Server services tier. Thisinstallation includes the deployment manager system and all computers thatwill host a managed node.Run the IBM WebSphere Application Server installation program to install IBMWebSphere Application Server Network Deployment. See the WebSphereApplication Server documentation for more information:v Version 6.1: publib.boulder.ibm.com/infocenter/wasinfo/v6r1/

index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/welc6topinstalling.html

v Version 7.0: publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.installation.nd.doc/info/ae/ae/welc6topinstalling.html

The InfoSphere Information Server installation package includes installationpackages for IBM WebSphere Application Server Network Deployment, Version








7.0. To preinstall WebSphere Application Server, Version 7.0 before you run theInfoSphere Information Server installation program, you can run theWebSphere Application Server installation program that is included in theInfoSphere Information Server installation media.Within the installation media, the WebSphere Application Server installationpackages are in the following directories:

v Linux UNIX payloads/Shared/WAS/payload/WAS

v Windows payloads\Shared\WAS/payload/WAS

2. Install the required fix pack and iFixes. To find the supported fix pack level,Java SDK fix number, and iFixes that are required for your installed version ofIBM WebSphere Application Server Network Deployment, refer to theInfoSphere Information Server system requirements page: www.ibm.com/support/docview.wss?rs=14&uid=swg27016382

Creating a deployment manager profileYou create a deployment manager profile (for example, Dmgr01) that contains thedeployment manager process. The deployment manager process is the mainadministration process that manages all other IBM WebSphere Application Serverprocesses running in the cell, including node agents and application serverprocesses.

Procedure

Create a deployment manager profile by using the Profile Management tool. Thetool is located in the bin/ProfileManagement directory of a WebSphere ApplicationServer installation. Refer to the complete instructions in the IBM WebSphereApplication Server Network Deployment documentation:

Important: On the Administrative Security panel, do not enable securityadministrative security. Make sure that the Enable administrative security checkbox is not selected. Security is enabled during the IBM InfoSphere InformationServer installation.v To create a deployment manager profile in Version 6.1:

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tpro_instancesdmgr.html

v To create a deployment manager profile in Version 7.0:http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tpro_instancesdmgr.html

Note: In the Profile Management tool, on the Environment Selection panel, selectDeployment Manager.

Note: For most cases, choose the Typical profile creation option. If you want tochange some attributes of the deployment manager profile (such as the portnumbers or whether to run the deployment manager process as a Windowsservice), you can select the Advanced profile creation option.

What to do next

Create a custom profile.

Chapter 23. WebSphere Application Server clustering for high availability and scalability 325







Creating a custom profileUse the Profile Management tool to create a custom profile (for example,Custom01). This profile contains the node agent process and the managed serverprocess that is part of the cluster.

About this task

It is a good practice to install IBM InfoSphere Information Server on a single-nodecluster and then, after the installation, to expand your cluster by adding newmanaged nodes and cluster members. Refer to the post-installation tasks for detailsabout adding new managed nodes and cluster members.

Procedure

Use the instructions to create a custom profile.v For Version 6.1:

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tpro_instancesmngdnode.html

v For Version 7.0:http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tpro_instancesmngdnode.html

Note: In most cases, select the Typical profile creation option. Select theAdvanced profile creation option if you need to modify attributes of the customprofile (such as port numbers or node name).

Important: On the Federation panel, ensure that the host name and portinformation match your deployment manager (the default information is localhostand 8879). Make sure that the Federate this node later check box is not selected.Federate the node later, when you can verify the availability of the deploymentmanager. Because administrative security is not enabled yet, do not enter the username and password for the deployment manager.

What to do next

Create a cluster and cluster members.

Creating a cluster and cluster members for the applicationserver

Use the IBM WebSphere administrative console to create a cluster with one clustermember definition.

Before you begin1. If you use HTTP session persistence with database-based persistence, you must

configure the application server separately before you can create a cluster.2. Create a managed server (which is not yet part of a cluster) and configure it to

use HTTP session database persistence.3. After you configure the HTTP session with database-based persistence enabled,

you can create a cluster and use the newly configured managed server as theinitial cluster member.








4. You must choose one of the following two methods available to manage HTTPsessions in a cluster environment: HTTP session memory-to-memory replicationor HTTP session database-based persistence. Both methods ensure that HTTPsession data survive in the event of a cluster member failure.

Note: HTTP session memory-to-memory replication is easier to set up. If you wantto use HTTP session memory-to-memory replication, when creating the cluster inIBM WebSphere Application Server Network Deployment administrative console,in the Step1: Enter basic cluster information window, select the Configure HTTPsession memory-to-memory replication check box. By default, the IBM InfoSphereInformation Server installation process detects whether HTTP sessions werealready configured with database-based session persistence. If it is not yetconfigured, HTTP session memory-to-memory replication is configuredautomatically, even if you do not select this check box.

For more information about HTTP session memory-to-memory replication or HTTPsession database persistence, refer to WebSphere Application Server V6 Scalability andPerformance Handbook, Section 6.8.5, at http://www.redbooks.ibm.com/abstracts/sg246392.html.

About this task

Create one cluster member to start with. After IBM InfoSphere Information Serveris installed, you can create additional cluster members. Refer to thepost-installation information for more details on how to add new cluster members.

Remember: There can be only one cluster defined in the cell. (You must deployeach InfoSphere Information Server cluster in its own dedicated cell.) The cellcannot contain any other type of server, which includes: InfoSphere InformationServer cluster, IBM InfoSphere Master Data Management (MDM) server, InfoSphereInformation Server stand-alone servers, or any standard application server instancethat runs J2EE applications. For more information, refer to “Implementing IBMWebSphere Application Server clustering” on page 33 and Chapter 23, “WebSphereApplication Server clustering for high availability and scalability,” on page 323.

Procedure

Create clusters and cluster members by using the IBM WebSphere ApplicationServer Network Deployment administrative console.v 6.1: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/

com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/trun_wlm_cluster_v61.html

v 7.0: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/trun_wlm_cluster_v61.html

Replication domainsWhen you create clusters and cluster members, it is useful to understand thevarious replications domains that are used to create clusters.

Several replication domains are used within an IBM InfoSphere Information Servercluster:v If you chose a memory-to-memory replication approach for HTTP session

management, the replication domain replicates HTTP session information andthe stateful EJB state across the cluster.


http://www.redbooks.ibm.com/abstracts/sg246392.html

http://www.redbooks.ibm.com/abstracts/sg246392.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/trun_wlm_cluster_v61.html






v Another type of replication domain is used to replicate cached data (data-cachedapplications that are part of the InfoSphere Information Server suite).

Both types of replication domains replicate cached data to all cluster members (afull-domain strategy). Replication domains are created automatically during theInfoSphere Information Server installation. You use the default IBM WebSphereApplication Server settings during installation. You can change these settings fromthe WebSphere Application Server administrative console after the InfoSphereInformation Server installation.

Installing a front-end Web serverYou might want to install and configure a front-end Web server before you run theIBM InfoSphere Information Server installation program so that the variousInfoSphere Information Server applications can be mapped to the front-end Webserver automatically. The alternative to installing a front-end Web server is toinstall a front-end load balancer.

Before you begin

Determine which Web server and Web server version to install, depending on yourversion of IBM WebSphere Application Server Network Deployment.

Review the documentation:v 6.1: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/

com.ibm.websphere.nd.doc/info/ae/ae/twsv_plugin.htmlv 7.0: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/

com.ibm.websphere.nd.doc/info/ae/ae/twsv_plugin.html

About this task

The following steps describe how to install the IBM HTTP Server, Versions 6.1 and7.0. Refer to the Apache HTTP Server documentation for information about how toinstall the Apache HTTP Server.

Procedure1. Determine a Web server topology diagram and road map:v 6.1: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/

index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tins_road_plugins.html.

v 7.0: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tins_road_plugins.html.

2. Choose whether to install the Web server locally or remotely:v For development and testing environments, you might prefer to install the

Web server locally on a computer that hosts an IBM WebSphere ApplicationServer Network Deployment managed node. When you do so, the Webserver plug-in file, plugin-cfg.xml, is automatically propagated to the Webserver by IBM WebSphere Application Server.

v For production environments, install the Web server remotely on a dedicatedserver. Because the front-end Web server is typically outside the firewall inthe DMZ, the front-end Web server must be installed remotely on a separatededicated computer. You manually copy the plugin-cfg.xml file to thecomputer where the Web server is installed. (For more information, see theIBM InfoSphere Information Server Administration Guide.)


http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/twsv_plugin.html




http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tins_road_plugins.html






3. Install IBM HTTP Server:v For 6.1, follow the steps in Installing IBM HTTP Server: http://

publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.ihs.doc/info/ihs/ihs/tihs_installihs.html

v For 7.0, follow the steps in Installing IBM HTTP Server: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.ihs.doc/info/ihs/ihs/tihs_installihs.html

4. Install the Web server plug-in module:v 6.1: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/

index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tins_webplugins.html

v 7.0: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tins_webplugins.html.

After you install the Workload Manager plug-in binary files, run theconfigure<webserver_name> script to create a Web server definition inWebSphere Application Server.

v UNIX On UNIX, the script is configure<webserver_name>.sh

v Windows On Microsoft Windows, the script isconfigure<webserver_name>.bat

Note: For remote installations, running the script also creates an unmanagednode.

5. Configure the Web server to accept encoded slashes. See “Cannot view reportresult from InfoSphere Information Server console or InfoSphere InformationServer Web console” on page 415.

6. Optional: To increase security, configure the front-end Web server tocommunicate by using secure HTTP (HTTPS). See “Configuring the front-endHTTP server for HTTPS” on page 155.

What to do next

You can now install additional components such as: backup load balancers, backupWeb servers, firewalls, and cache proxies. Refer to the external vendors'documentation.

Installing a front-end load balancer (Optional)You can install a load balancer in front of the Web servers in an IBM WebSphereApplication Server cluster installation. This configuration is called an IP sprayertopology.

About this task

Steps for installing a front-end load balancer are specific to external vendors andare not provided in this documentation.

Do not install a load balancer directly in front of a WebSphere Application Servercluster without a Web server between the load balancer and the cluster. Webservers with the WebSphere Application Server workload management plug-inadjust to changes in the cluster topology such as adding or removing nodes. Loadbalancers do not have this functionality, and must be manually reconfigured.


http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.ihs.doc/info/ihs/ihs/tihs_installihs.html






http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tins_webplugins.html






Make sure to configure session affinity in the load balancer. There are severalmethods to achieve session affinity. The method you choose depends on theproduct that you use and the forwarding mechanism that you configure.Mechanisms include media access control (MAC) address forwarding, NetworkAccess Translation/Network Address Port Translation (NAT/NAPT) forwarding,and content-based forwarding. Layer 2 load balancers (load balancers that operateat the MAC layer) generally achieve session affinity by using a "stickiness to sourceIP address" approach. Layer 3 and higher load balancers (load balancers thatoperate at the IP layer and above) typically achieve session affinity by usingpassive cookies or a content-based technique. This is how session affinity istypically implemented with HTTP servers.

What to do next

After you install a load balancer, you can install any additional components thatyou need, such as backup load balancers, firewalls, and so on.

Running the installation program (clustered installation)After you configure your system, you can run the IBM InfoSphere InformationServer installation program.

Before you begin

v Linux Make sure that all WebSphere Application Server processes will startwith the correct ulimit setting on the computer where you will install thedeployment manager and on all computers that will host a managed node:Add the following to the /etc/profile file:ulimit -n 10240

v Ensure that no firewall is deployed within the IBM WebSphere ApplicationServer Network Deployment cell.

v Ensure that the deployment manager process is running.

Tip: You can check whether the deployment manager is running by launchingthe WebSphere Application Server administrative console. If the login screen isdisplayed correctly, the deployment manager process is running. If you see anerror or a blank screen, you can start the deployment manager by using thestartManager command located under the <dmgrProfileName>/bin directory.

v Ensure that the managed node and node agent that you created are bothrunning.

Tip: You can check whether the node agent is running by logging in to theWebSphere Application Server administrative console and clicking Systemadministration → Node agents. You can start the node agent by using thestartNode WebSphere Application Server command under the<customProfileName>/bin directory.

v Verify that you have created one cluster with at least one member.

Note: It is a best practice to install IBM InfoSphere Information Server on asingle-node cluster and then, after the installation, to expand your cluster byadding new managed nodes and cluster members. Refer to the post-installationadministration tasks for details on how to add new custom profiles.

v The front-end Web server and plug-in module must be installed.


Procedure1. Disable any firewall that might be running on your computer and ensure that

the firewall is disabled during the entire installation. You can reenable thefirewall after the installation is finished.

2. Run the InfoSphere Information Server installation program on the computerthat hosts the deployment manager process.a. Use the steps in the following documentation: Installing IBM InfoSphere

Information Server software.b. On the WebSphere Application Server Selection panel, select Configure an

existing instance.3. Select the WebSphere Application Server deployment manager profile. The

installation program detects that this is a cluster installation, not a standaloneinstallation.

4. During the interview process, specify the host name and port number of thefront-end HTTP dispatcher for any requests for the services tier host name andport. Do not specify a port to a specific application server cluster member, suchas 9080. A specific port number to cluster member does not allow for highavailability and efficient dispatching of requests, because requests are directedto a specific cluster member. This configuration is especially important whenspecifying the services tier host name and port number during an engine tierinstallation.

What to do next

After you configure WebSphere Application Server for your cluster installation ofInfoSphere Information Server, you can administer your WebSphere ApplicationServer clusters. For more information, refer to the IBM InfoSphere Information ServerAdministration Guide.

Note: When the MetadataServer script is run in a stand-alone (non-cluster)environment, it sets the following system settings:

v Linux uname setting: ulimit -n 10240

v AIX uname setting: unset LDR_CNTRL

These settings are not set when you start a cluster. You can manually producethese settings in a cluster environment, if needed. The MetadataServer script existsin the ASBServer/bin directory of the computer hosting the deployment manager.

Changing the front-end dispatcher locationIf you change the front-end dispatcher location or configuration, you mustcomplete a few additional steps. This post-configuration task involves updatingtwo files that exist on all tiers.

About this task

During the installation process, you must enter the host name and port number ofthe front-end dispatcher for a high availability installation. This information isused by the installation program to configure IBM InfoSphere Information Server.When you modify the front-end dispatcher (for example, if you relocate thedispatcher to another machine, or replace the Web server with a load balancer, andso on), you must update the following files with the new host name and portnumber: registered-servers.xml and Version.xml.


You must update these files on every engine tier computer that is registered to thatservices tier. Also update the Version.xml file on the services tier system that hoststhe Deployment Manager.

Procedure1. On every engine tier computer, update the registered-servers.xml file with

the correct front-end dispatcher host name and port number:In the file, /opt/IBM/InformationServer/ASBNode/eclipse/plugins/com.ibm.isf.client_8.5.0.0/registered-servers.xml or C:\IBM\InformationServer\ASBNode\eclipse\plugin\com.ibm.isf.client_8.5.0.0\registered-servers.xml, update the following <asb-server> element, wheredispatcher_hostname is the new host name of the front-end dispatcher, anddispatcher_port is the new HTTP port of the front-end dispatcher.<asb-server name="domain_name"host-name="dispatcher_hostname"port="dispatcher_port"is-primary-server="true"/>

Important: On engine tier systems that have clients installed, you might seemultiple <asb-server> elements in the registered-servers.xml file. Theseinstances represent the host name and port number of each services tier thathas been successfully logged into from this client system. This is the source ofthe list of services tiers shown on client login pages. Update the host namesand port numbers of only the services tiers that are affected by the front-enddispatcher changes.

Note: In the file you are examining, if there is no <asb-server> element withis-primary-server="true" in the registered-servers.xml file, then you are noton the engine tier. Refer to the last step in this topic for information aboutconfiguring files on the client tier.

2. Update the Version.xml file with the correct front-end dispatcher host nameand port number:In the file, /opt/IBM/InformationServer/Version.xml or C:\IBM\InformationServer\Version.xml, update the following <asb-server> elements,where dispatcher_hostname is the new host name of the front-end dispatcher,and dispatcher_port is the new HTTP port of the front-end dispatcher:

Modify Version.xml on the Services and Engine Tier computers<PersistedVariable encrypted="false" name="was.default.host.port"

persistent="true" readonly="true" value="dispatcher_port"/><PersistedVariable encrypted="false" name="is.console.port"

persistent="true" readonly="true" value="dispatcher_port"/><PersistedVariable encrypted="false" name="isf.server.host"

persistent="true" readonly="false" value="dispatcher_hostname"/>...<PersistedVariable encrypted="false" name="isf.http.host"

persistent="true" readonly="true" value="dispatcher_hostname"/><PersistedVariable encrypted="false" name="isf.http.port"

persistent="true" readonly="true" value="dispatcher_port"/>

3. On the engine tier, recycle the agents and engine processes. Refer to the IBMInfoSphere Information Server Administration Guide.

4. Restart the cluster and cluster members. Refer to the IBM InfoSphere InformationServer Administration Guide.

5. Go to http://dispatcher_hostname:dispatcher_port to verify whether you canlog in to the InfoSphere Information Server Web console.


6. Optional: You can update the list of services tier host names and port numbersthat appears on the client login page by using one of the following methods:v If you are comfortable with editing the XML file across the client tier, you

can update the registered-servers.xml file, /opt/IBM/InformationServer/ASBNode/eclipse/plugins/com.ibm.isf.client_8.5.0.0/registered-servers.xml or C:\IBM\InformationServer\ASBNode\eclipse\plugin\com.ibm.isf.client_8.5.0.0\registered-servers.xml, on each client tiercomputer. Then restart all clients on the client tier.

v Alternatively, if you do not want to edit the XML file, or if you prefer to usea command, you can use the RegistrationCommand tool. To remove the hostname and port numbers that are no longer in use, run the followingcommands:

Note: The RegistrationCommand tool is in the following directory:<InformationServer_installation_directory>\ASBNode\bin

Linux UNIX

./RegistrationCommand.sh -remove -hostname old_host_name -portold_port_number

./RegistrationCommand.sh -add -name new_host_name -hostname new_host_name-port new_port_number

./RegistrationCommand.sh -list

Windows

RegistrationCommand.bat -remove -hostname old_host_name -portold_port_number

RegistrationCommand.bat -add -name new_host_name -hostname new_host_name-port new_port_number

RegistrationCommand.bat -list

-removeThe remove command removes the old host name and old port numberso that they no longer appear in the list of services tiers shown duringclient login.

-addThe add command adds the new host name and port number inadvance. Alternatively, you can enter the new host name and portnumber at the next login.

-listThe list command lists the servers that you currently have in yourregistered-servers.xml file, which reflects the list of servers that appearon the client login page.

Configuring a cluster to run as a service (Windows)You can configure an IBM WebSphere Application Server cluster to run as aservice. When you run a WebSphere Application Server cluster as a service, thecluster to automatically restarts after a failure and keeps processes active after youlog out of Microsoft Windows.

About this task

When you run a WebSphere Application Server cluster as a service, you have thesebenefits:v Enables automatic restarts in the event of a failure


v Enables cluster member processes to remain active after you log out from yourMicrosoft Windows system account

Procedure

To configure a cluster to run as a service:1. Configure your node agent or node agents, to run as a service by using the

WASService command line tool.v Version 6.1: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/

index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rins_wasservice.html

v Version 7.0: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rins_wasservice.html

The following example code uses the Local System account, SYSTEM, as thedefault user ID. If you want to use a different account, you can specify yourown user ID by using the -userid option.C:\IBM\WebSphereND61\AppServer\bin>WASService-add "myNode01" -servername nodeagent-profilePath C:\IBM\WebSphereND61\AppServer\profiles\Custom01-wasHome C:\IBM\WebsphereND61\Appserver-logFile C:\IBM\WebSphereND61\AppServer\profiles\Custom01\logs\nodeagent\startNode.log-logRoot C:\IBM\WebSphereND61\AppServer\profiles\Custom01\logs\nodeagent-restart true -startType automatic

Adding Service: ImyNode01Config Root: C:\IBM\WebSphereND61\AppServer\profiles\Custom01\configServer Name: nodeagentProfile Path: C:\IBM\WebSphereND61\AppServer\profiles\Custom01Was Home: C:\IBM\WebsphereND61\Appserver\Start Args:Restart: 1

IBM WebSphere Application Server V6.1 - myNode01 service successfully added.

2. Configure your cluster members to restart automatically:a. Log in to the WebSphere administrative console.b. Click Servers → Application Servers → server_name.c. Expand Java and Process Management and select Monitoring Policy.d. Change the node restart state to RUNNING.e. Click OK and Save.

Repeat this step for each server in the cluster.3. Shut down your node agents by using the stopNode command:v Version 6.1: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/

index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/rxml_stopnode.html

v Version 7.0: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/rxml_stopnode.html

4. Shut down your cluster by using the WebSphere administrative console.v Version 6.1: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/

index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/trun_wlm_cluster_stop.html


http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rins_wasservice.html






http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/rxml_stopnode.html






http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/trun_wlm_cluster_stop.html



v Version 7.0: http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/trun_wlm_cluster_stop.html

5. Start your node agents by using the Windows Services Console. Your clusterwill automatically restart.

Note: Your node agents and cluster members must now run in the context ofthe Local System account instead of your own user account, unless youspecified a different account when you ran the WASService command in step 1.You can now safely log out of your Windows user account and your clusterwill continue to run.






Chapter 24. Metadata repository tier clustering for highavailability

To provide high availability for your metadata repository database, you can set upthe database within a database cluster.

IBM InfoSphere Information Server does not support clustered configurations ofthe IBM InfoSphere Information Analyzer database or the IBM InfoSphereQualityStage Match Designer database.

Configuring the metadata repository database in an IBM DB2 clusterUse this road map to create an IBM InfoSphere Information Server configuration inwhich the metadata repository database is set up within an IBM DB2 cluster.

If you want to create a new DB2 database cluster installation, complete the tasks inthe following table. If you want to integrate InfoSphere Information Server into anexisting DB2 database cluster, read through the task topics to make sure that yourcluster configuration is compatible with InfoSphere Information Server.

Table 104. Setting up an IBM DB2 database cluster

Task Link for more information

To set up a DB2 database cluster, firstconfigure the servers, storage, and network.

“Preparing the servers, file system, andstorage” on page 338

(Optional) Install high availability (HA)software to monitor the health of the serversand to manage failover.

“Installing high availability software on DB2database system servers” on page 339

Before you install InfoSphere InformationServer, install the DB2 database system,create a cluster, and create the metadatarepository database on the primary node inthe cluster.

“Installing the DB2 database system andcreating the cluster and metadata repositorydatabase” on page 340

Create users and groups. Run the InfoSphereInformation Server installation program.

“Running the installation program for asetup that includes DB2 clustering” on page341

To allow IBM WebSphere Application Serverto reconnect to the standby server smoothly,configure Automatic Client Reroute.

“Configuring automatic client reroute” onpage 342

To enable WebSphere Application Server tocommunicate with more than one server, usethe WebSphere Application Serveradministrative console to specify analternate database address and port.

“Specifying the alternate database addressand port for IBM WebSphere ApplicationServer” on page 351

Verify the state of the cluster. “Verifying the IBM DB2 database cluster” onpage 345

InfoSphere Information Server does not support cluster configurations of the IBMInfoSphere Information Analyzer analysis database or IBM InfoSphere QualityStageMatch Designer database.


To deploy a clustered topology, you must have a solid understanding of networktechnologies such as protocols, layers, devices, and so on. Clustered topologies aretechnically complex, and require expertise to implement successfully.

Preparing the servers, file system, and storageTo set up an IBM DB2 database cluster, first configure the servers, storage, andnetwork.

For high availability, the cluster must include at least two physically separatecomputers. If possible, use identical hardware with identical internal storage,memory, and processing power.

The metadata repository database cannot be partitioned. They must exist in anon-partitioned environment. For this reason, you cannot set up the cluster in a"mutual takeover" configuration. You must set up an "idle standby" configuration.In an idle standby configuration, a primary server processes all the workload. Asecondary server is idle, or in standby mode, ready to take over the workload ifthere is a failure on the primary system.

The servers must be able to communicate with each other over high-speednetworks. To minimize single points of failure, each server must have redundantconnections to at least two physically separate high-speed networks.

To support failover when a problem occurs, the HA software creates a heartbeatsignal between the servers. Set up at least two more physically separate networksfor this signal. These networks can be serial or other networks. The networks thatcarry the heartbeat signal must be physically separate and isolated from thehigh-speed networks.

The following diagram shows a two-server active-passive architecture withminimum network redundancy. The diagram shows two servers (Node 1 andNode 2). Each server has four network interfaces (en0, en1, en2, and en3). Thereare two redundant high-speed networks (Network A and Network B). On eachserver, two network interfaces are connected to Network A, and two networkinterfaces are connected to Network B. This arrangement creates redundancy at thenetwork interfaces and within the overall high-speed network architecture.

Each server also has two serial interfaces (tty1 and tty2). Each serial interface onone server is connected to a serial interface on the other. This arrangement createsa redundant serial "ring" network for the heartbeat signal.

Create the DB2 database system file system on disk partitions that are shared byall cluster nodes. The disk partitions must be on highly available media such as astorage area network (SAN).


For more specific information about DB2 database cluster servers, storage, ornetwork considerations, see the IBM DB2 database system documentation:v "Database fundamentals" in the IBM DB2 Database, Version 9.5 for Linux, UNIX,

and Windows Information Center: publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.container.doc/doc/c0052964.html

v "Database fundamentals" in the IBM DB2 Database, Version 9.7 for Linux, UNIX,and Windows Information Center: publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.container.doc/doc/c0052964.html

Installing high availability software on DB2 database systemservers

You can optionally install and configure IBM Tivoli System Automation forMultiplatforms (SA MP) to monitor the health of the IBM DB2 database systemservers and to manage failover.

Tivoli System Automation for Multiplatforms software is shipped as part of theDB2 database system installation package. This high availability (HA) softwaremonitors the health of the servers, the network, the operating system, and selectedsoftware components. If a critical item fails, the software triggers a failover to thestandby server. Then the automatic client reroute feature causes IBM WebSphereApplication Server to connect to another server in the cluster.

If you plan to implement SA MP, install it before you install and configure IBMInfoSphere Information Server. When you install SA MP, you configure a floatingIP address that is shared between the servers. When you configure automatic clientreroute, you provide this IP address as the "alternate server host name".

You can also choose not to install SA MP. If you do not install the software, if afailure occurs on the primary server the database administrator must manuallydetect the failure and perform a failover. Then automatic client reroute redirectsWebSphere Application Server to the new server.

To install and configure the software, see the DB2 database system documentation:

Node 1

tty2 en0

en1

en2

en3

Node 2

tty1

tty2en0

en1

en2

en3 tty1

Serial

Netw

ork

A

Netw

ork

B

Figure 50. Two servers with redundant connections to networks

Chapter 24. Metadata repository tier clustering for high availability 339

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.container.doc/doc/c0052964.html




v "Installing and upgrading the SA MP Base Component with the DB2 installer" inthe IBM DB2 Database Version 9.5 for Linux, UNIX, and Windows InformationCenter: publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.admin.ha.doc/doc/t0051289.html

v "Installing and upgrading the SA MP Base Component with the DB2 installer" inthe IBM DB2 Database Version 9.7 for Linux, UNIX, and Windows InformationCenter: publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.qb.server.doc/doc/t0051374.html

For an example of how to set up SA MP for a simple active-passive serverconfiguration, see “Example: Setting up an active-passive configuration by usingIBM Tivoli System Automation for Multiplatforms” on page 301.

Installing the DB2 database system and creating the clusterand metadata repository database

Before you install IBM InfoSphere Information Server, install the IBM DB2 databasesystem, create a cluster, and create the metadata repository database on theprimary node.

Before you begin

A separate copy of the DB2 database system must be installed on each server.

Procedure1. Install the DB2 database system on the computers that are to make up the

cluster.v Each DB2 database system instance must be the same version of the DB2

database system.v The installations must have the same container file system and installation

path, for example: /home/db2inst1/sqllib.v Create identical user names and passwords for each DB2 database system

instance.For information about installing the DB2 database system, see the DB2 databasesystem documentation:v DB2 Database, Version 9.5 for Linux, UNIX, and Windows:

publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jspv DB2 Database, Version 9.7 for Linux, UNIX, and Windows:

publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jspThe InfoSphere Information Server installation package includes installationpackages for IBM DB2 Enterprise Server Edition, Version 9.7 for Linux, UNIX,and Windows. To preinstall DB2 9.7 before you run the InfoSphere InformationServer installation program, you can run the DB2 database system installationprogram that is included in the InfoSphere Information Server installationmedia.Within the installation media, the DB2 database system installation packagesare in the following directories:

v Linux UNIX payloads/Shared/DB2/payload

v Windows payloads\Shared\DB2\payload

2. Set up the cluster.The metadata repository database cannot be partitioned. The database mustexist in a non-partitioned environment. For this reason, you cannot set up the


http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.admin.ha.doc/doc/t0051289.html






system in a "mutual takeover" configuration. You must set up an "idle standby"configuration. In this configuration, a primary system processes all theworkload. A secondary system is idle, or in standby mode, ready to take overthe workload if there is a failure on the primary system.For information about creating a DB2 database cluster, see the DB2 databasesystem documentation:v "Configuring a clustered environment for high availability" in the IBM DB2

Database, Version 9.5 Information Center: publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.admin.ha.doc/doc/t0051353.html

v "Configuring a clustered environment for high availability" in the IBM DB2Database, Version 9.7 Information Center: publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.admin.ha.doc/doc/t0051353.html

3. On the primary node, create the metadata repository database within the DB2database system.To create the database, use the scripts that are supplied with the InfoSphereInformation Server installation media. See “Preparing an existing DB2 databasesystem by using scripts” on page 149.Locate the database file system on a disk partition that is shared by all nodes inthe cluster. The disk partition must be on highly available media such as astorage area network (SAN).

Running the installation program for a setup that includesDB2 clustering

Create administrator and component owner accounts and groups. Run the IBMInfoSphere Information Server installation program.

Procedure1. Create identical administrator and component owner accounts and user groups

on all servers in the cluster. Make sure that the group IDs and user IDs areidentical on both servers. The following sample commands create some of theaccounts and groups:

v Linux UNIX

/usr/sbin/groupadd db2iadm1/usr/sbin/groupadd db2fadm1/usr/sbin/groupadd dasadm1/usr/sbin/groupadd xmeta/usr/sbin/groupadd isuser/usr/sbin/groupadd dstage


v AIX

/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









For details on creating administrator users and groups, see “Setting upadministrator and owner accounts” on page 142.

2. Run the InfoSphere Information Server installation program in graphical mode.Complete the entire InfoSphere Information Server installation as described in“Sample scenario D: Topology with clustered metadata repository tier andservices tier” on page 114.

Configuring automatic client rerouteTo allow IBM WebSphere Application Server to reconnect to the standby serversmoothly, configure automatic client reroute.

About this task

In an IBM InfoSphere Information Server installation with a clustered DB2database system setup, automatic client reroute can redirect WebSphere ApplicationServer to connect to an alternate server when the primary server fails. Thealternate server is preregistered within automatic client reroute. When the failureoccurs, automatic client reroute first tries to reconnect to the primary database. Ifthe connection fails, automatic client reroute establishes a connection with thestandby server.

If an update, deletion, or insertion transaction was taking place and the failureoccurred before the transaction was committed, the user receives an error message.When the user retries the transaction, the standby server handles the transaction. Ifa read transaction was taking place, the read transaction is automatically executedon the standby server, and no error message is displayed.

Procedure1. Log in to the primary node.2. Run the following command to configure automatic client reroute for the

database:db2 update alternate server for database database using hostname standby_IP

port port

For example:db2 update alternate server for database xmeta using hostname 192.0.2.7 port

60000

Specifying the alternate database address and port for IBMWebSphere Application Server

To enable IBM WebSphere Application Server to communicate with more than oneserver, specify an alternate database address and port.

Procedure1. Start the WebSphere Application Server administrative console.2. Log in as the WebSphere Application Server administrator (default:

wasadmin), or as another user with administrative privileges.


3. In the navigation pane, expand Resources, expand JDBC, and click JDBCProviders. The JDBC providers page appears.

4. Click ASB JDBC Provider.5. Under Additional Properties, click Data sources.6. For each of the data sources listed in the window, perform these steps:

a. Click the data source.b. Under Additional Properties, click Custom Properties.c. Click clientRerouteAlternateServerName. If this property is not present,

click New and add the property and value.d. In the Value field, type the alternate server address:v If IBM Tivoli System Automation for Multiplatforms (SA MP) is running

in the cluster, type the service IP address that the cluster nodes share.v If SA MP is this not running in the cluster, type the IP address of the

standby server.e. Click OK.f. Click clientRerouteAlternatePortNumber. If this property is not present,

click New and add the property and value.g. In the Value field, type the alternate server port number:v If SA MP is running in the cluster, type the service port number that the

cluster nodes share.v If SA MP is not running in the cluster, type the port number of the

standby server.h. Click enableSeamlessFailover. If this property is not present, you can click

New and add the property and value.i. In the Value field, type 1.

This property controls whether the server returns an error that indicatesthat failover occurred. For more information, see the DB2 database systemdocumentation.

j. Click OK.k. Click New.l. In the Name field, type maxRetriesForClientReroute

m. In the Value field, type 2. This parameter sets the number of connectionretry attempts.

n. Click Apply.o. In the Name field, type retryIntervalForClientReroute This parameter

sets the sleep interval between retry attempts.p. In the Value file, type 15.

Note: You might want to set these values differently. The values youchoose depend upon the hardware and the topology of your configuration.

q. Click OK.r. Click Apply.s. In the Messages box at the top of the page, click Save to apply the

changes to the master configuration.t. Click the data source name in the line at the top of the page to return to

the data source page.u. Click Test Connection to test the connection.v. Continue with step (a) for the next data source.


7. In the navigation pane, under Resources → JDBC, click ASB XA JDBCProvider. The JDBC providers page appears.

8. Under Additional Properties, click Data sources.9. Repeat step 6 for each data source that is listed in the window.

10. Log out of the console.11. Add the alternate server name and port number to the

repository_database.xml file. This file is located in the following .jar file:

v Windows opt/IBM/InformationServer/ASBServer/apps/lib/obj-conf.jar

v Linux UNIX C:\IBM\InformationServer\ASBServer\apps\lib\obj-conf.jar

In a configuration that includes WebSphere Application Server clustering, thefile is on the server that hosts the Deployment Manager. In a configurationwithout WebSphere Application Server clustering, the file is on the servicestier computer.To modify the repository_database.xml file:a. Make a backup copy of the obj-conf.jar file.b. Use an unzip utility to extract the repository_database.xml file from the

obj-conf.jar file.c. Open the repository_database.xml file by using a text editor.d. Locate the <jdbc-connection-descriptor> element in the file that has a

dbalias attribute. This element is typically the second<jdbc-connection-descriptor> element in the file. For example:<jdbc-connection-descriptor batch-mode="true" dbalias="//192.0.2.15/xmeta" default-connection="false" driver="com.ibm.db2.jcc.DB2Driver" eager-release="false" ignoreAutoCommitExceptions="false" jcd-alias="pojo" jdbc-level="2.0" password="{xor}tIakDPBAIX2Ao1nHR8j/+A==" platform="Db2" protocol="jdbc" subprotocol="db2" useAutoCommit="2" username="{xor}tIakDPBAIX2Ao1nHR8j/+A==">

<connection-pool maxActive="21" validationQuery=""/><object-cache class="org.apache.ojb.broker.cache.ObjectCach

ePerBrokerImpl"/></jdbc-connection-descriptor>

e. Modify the element to include the client reroute information. Use the sameserver address and port number that you specified in the previous steps.For example:<jdbc-connection-descriptor batch-mode="true" dbalias="//192.0.2.15:50001/xmetanls:;clientRerouteAlternateServerName=192.0.2.16;clientRerouteAlternatePortNumber=50001;queryCloseImplicit=2;"default-connection="false" driver="com.ibm.db2.jcc.DB2Driver" eager-release="false" ignoreAutoCommitExceptions="false" jcd-alias="pojo" jdbc-level="2.0" password="{xor}tIakDPBAIX2Ao1nHR8j/+A==" platform="Db2" protocol="jdbc" subprotocol="db2" useAutoCommit="2" username="{xor}tIakDPBAIX2Ao1nHR8j/+A==">



f. Save your changes.g. Use a zip utility to replace the repository_database.xml file in the

obj-conf.jar file with your modified version.12. Restart WebSphere Application Server.


Verifying the IBM DB2 database clusterAfter you complete the cluster configuration and IBM InfoSphere InformationServer installation, verify the state of the cluster.

Procedure1. Log in to the primary node in the DB2 database cluster.2. Run the lssam command to validate the state of the cluster. For example:

lssam

The command displays a report. For example:Online IBM.ResourceGroup:db2_db2inst1_0-rg Nominal=Online

|- Online IBM.Application:db2_db2inst1_0-rs|- Online IBM.Application:db2_db2inst1_0-rs:myprimary’- Offline IBM.Application:db2_db2inst1_0-rs:mystandby

’- Online IBM.ServiceIP:db2ip_192_0_2_16-rs|- Online IBM.ServiceIP:db2ip_192_0_2_16-rs:myprimary’- Offline IBM.ServiceIP:db2ip_192_0_2_16-rs:mystandby

This report shows a two-node cluster. One node (myprimary) is active (online).The other node (mystandby) is offline.

Setting up the metadata repository database in an IBM DB2 databaseHADR configuration

Use this road map to create an IBM InfoSphere Information Server implementationin which the metadata repository database is set up within a DB2 database highavailability disaster recovery (HADR) configuration.

If you want to create a DB2 database HADR installation, complete the tasks in thefollowing table. If you want to integrate InfoSphere Information Server into anexisting HADR configuration, read through the task topics to make sure that yourHADR configuration is compatible.

Table 105. Configuring the metadata repository database in a DB2 database HADRconfiguration.


Configure the servers, the network, and thestorage.

“Preparing the servers, storage, andnetwork” on page 346

Install DB2 database system on both serversin the configuration. Use the scripts in theinstallation media to configure the databaseon the primary server.

“Installing the DB2 database system andcreating the metadata repository database”on page 347

Create administrator and component owneraccounts and groups, and complete theInfoSphere Information Server installationand configuration.

“Running the installation program for anHADR configuration” on page 348

On the HADR primary server, configure theHADR variables and verify your settings.

“Configuring the HADR primary server” onpage 348

Back up the database from the primaryserver and restore it on the standby server.Then set HADR variables on the standbyserver.

“Configuring the HADR standby server” onpage 350


Table 105. Configuring the metadata repository database in a DB2 database HADRconfiguration. (continued)


To enable IBM WebSphere ApplicationServer to communicate with either server inthe HADR setup, use the WebSphereApplication Server administrative console tospecify an alternate database address andport.

“Specifying the alternate database addressand port for IBM WebSphere ApplicationServer” on page 351

Start the HADR software on the standbyserver and then on the primary server.

“Starting HADR” on page 353

Validate the HADR configuration and testthe takeover function.

“Validating the HADR configuration” onpage 355

InfoSphere Information Server does not support HADR configurations of the IBMInfoSphere Information Analyzer analysis database or the IBM InfoSphereQualityStage Match Designer database.

To deploy a clustered or HADR topology, you must have a solid understanding ofnetwork technologies such as protocols, layers, devices, and so on. Clusteredtopologies are technically complex, and require expertise to implement successfully.

Preparing the servers, storage, and networkTo set up an IBM DB2 database HADR configuration, first configure the servers,storage, and network.

The high availability disaster recovery (HADR) configuration must include at leasttwo physically separate computers. Use identical hardware with identical storage,memory, and processing power. The configuration must satisfy the followingrequirements:v The computers must have identical operating system versions.v The computers must run identical versions of DB2 database system.v The computers must each have separate storage that is not shared between

them.v They must have the same container file system and installation path for DB2

database system.v The servers must be able to communicate with each other using TCP/IP over a

high-speed network.v The IBM WebSphere Application Server installation must be able to

communicate with both servers over the network.v On each server, the services file must specify the ports for HADR. The port

name is user-defined. The port number can be any number, provided there is noconflict. The ports on the primary and standby servers do not need to beidentical. However, if the ports are identical, configuration is easier.The services file can be found in the following locations:

– Linux UNIX /etc/services

– Windows c:\windows\system32\drivers\etc\services

The following example shows HADR ports specified within the services file:# HADR ports assigned by userha_myhadr 51012/tcpha_myhadr_int 51013/tcp


For more specific information about DB2 database HADR servers, storage, ornetwork considerations, search for these terms in the IBM DB2 database systemdocumentation:v IBM DB2 Database, Version 9.5 for Linux, UNIX, and Windows:


publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp

Installing the DB2 database system and creating the metadatarepository database

Before you install IBM InfoSphere Information Server, install the IBM DB2 databasesystem on both servers and create the InfoSphere Information Server metadatarepository database on the primary node.

Before you begin

A separate copy of the DB2 database system must be installed on each server.

Procedure1. Install the DB2 database system on both computers.v Each DB2 database system instance must be the same version of the DB2

database system.v Each instance must use a separate file system for storage.v The installations must have the same container file system and installation

path. For example: /home/db2inst1/sqllib.v Create identical user names and passwords for each DB2 database system

instance.For information about installing the DB2 database system, see the DB2 databasesystem documentation:v IBM DB2 Database, Version 9.5 for Linux, UNIX, and Windows:


publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jspThe InfoSphere Information Server installation package includes installationpackages for IBM DB2 Enterprise Server Edition, Version 9.7 for Linux, UNIX,and Windows. To preinstall Version 9.7 before you run the InfoSphereInformation Server installation program, you can run the DB2 database systeminstallation program that is included in the InfoSphere Information Serverinstallation media.Within the installation media, the DB2 database system installation packagesare in the following directories:

v Linux UNIX payloads/Shared/DB2/payload

v Windows payloads\Shared\DB2\payload

2. On the primary node, create the metadata repository database within the DB2database system.To create the databases, use the scripts that are supplied with the InfoSphereInformation Server installation media. See “Preparing an existing DB2 databasesystem by using scripts” on page 149.






Running the installation program for an HADR configurationCreate administrator and component owner accounts and groups. Run the IBMInfoSphere Information Server installation program.

Procedure1. Create identical administrator and component owner accounts and groups on

both high availability disaster recovery (HADR) servers. Make sure that thegroup IDs and user IDs are identical on both servers. The following samplecommands create some of the accounts and groups:

v Linux UNIX

/usr/sbin/groupadd db2iadm1/usr/sbin/groupadd db2fadm1/usr/sbin/groupadd dasadm1/usr/sbin/groupadd xmeta/usr/sbin/groupadd isuser/usr/sbin/groupadd dstage


v AIX

/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


For details on creating administrator users and groups, see “Setting upadministrator and owner accounts” on page 142.

2. Run the InfoSphere Information Server installation program in graphical mode.Complete the entire InfoSphere Information Server installation as described in“Sample scenario D: Topology with clustered metadata repository tier andservices tier” on page 114.

Configuring the HADR primary serverOn the primary server, configure the high availability disaster recovery (HADR)variables and verify your settings.

Before you begin

Complete the installation of IBM InfoSphere Information Server. The installationmust be operational before you complete the HADR configuration.

Complete HADR configuration as soon as the InfoSphere Information Serverinstallation is operational.


Procedure1. Log in to the primary server as an administrator.2. Run the following commands to specify the HADR primary server and

standby server:db2 update db cfg for database using hadr_local_host primary_IPdb2 update db cfg for database using hadr_remote_host standby_IP

For example:db2 update db cfg for xmeta using hadr_local_host 192.0.2.6db2 update db cfg for xmeta using hadr_remote_host 192.0.2.7

3. Run the following commands to specify the HADR primary and standbyservice names:db2 update db cfg for database using hadr_local_svc primary_svc_namedb2 update db cfg for database using hadr_remote_svc standby_svc_name

In the commands, the service names must match the HADR port names thatappear in the services file. For example:db2 update db cfg for xmeta using hadr_local_svc ha_myhadrdb2 update db cfg for xmeta using hadr_remote_svc ha_myhadr_int

4. Run the following command to specify the DB2 instance name on the standbyserver:db2 update db cfg for database using hadr_remote_inst DB2_standby_instance

For example:db2 update db cfg for xmeta using hadr_remote_inst db2inst1

5. Run the following command to specify the time (in seconds) that the HADRprocess waits before considering a communication attempt to have failed:db2 update db cfg for database using hadr_timeout timeout

For example:db2 update db cfg for xmeta using hadr_timeout 120

6. Run the following command to specify the HADR synchronization mode:db2 update db cfg for database using syncmode mode

For example:db2 update db cfg for xmeta using syncmode SYNC

When configuring the synchronization mode, choose synchronous mode(SYNC) or near synchronous mode (NEARSYNC). Either mode typicallyprovides adequate response time for InfoSphere Information Server. Avoidchoosing asynchronous mode (ASYNC) because ASYNC mode has the highestchance of transaction loss if the primary server fails.

7. Run the following command to specify the time (in seconds) that the HADRprocess waits before considering a communication attempt to have failed:db2 update db cfg for database using hadr_timeout timeout

For example:db2 update db cfg for xmeta using hadr_timeout 120

8. Run the following command to activate the "log index pages created" feature.When logindexbuild is on, index creation, recreation, and reorganizationoperations are logged. This logging allows indexes to be reconstructed duringDB2 roll-forward operations or HADR log replay procedures.db2 update db cfg for xmeta using logindexbuild on

9. Run the following command to set up automatic client reroute:


db2 update alternate server for database database using hostname standby_IPport port

For example:db2 update alternate server for database xmeta using hostname 192.0.2.7

port 60000

10. Run the following command to verify your configuration values:db2 get db cfg for database | grep HADR

For example:db2 get db cfg for xmeta | grep HADR

The command displays a report:HADR database role = STANDARDHADR local host name (HADR_LOCAL_HOST) = myprimary.example.comHADR local service name (HADR_LOCAL_SVC) = ha_myhadrHADR remote host name (HADR_REMOTE_HOST) = mystandby.example.comHADR remote service name (HADR_REMOTE_SVC) = ha_myhadr_intHADR instance name of remote server (HADR_REMOTE_INST) = db2inst1HADR timeout value (HADR_TIMEOUT) = 120HADR log write synchronization mode (HADR_SYNCMODE) = SYNC

Configuring the HADR standby serverBack up the database from the primary server and restore it on the standby server.Then set HADR variables on the standby server.

Before you begin

Make sure that neither database has an existing connection with client application.You cannot perform a backup on a database that has an existing connection withits client application.

Procedure1. Log in to the primary server as an administrator.2. Run these commands to back up the database on the primary server:

mkdir temp_backup_directorycd temp_backup_directorydb2 backup db database

For example:mkdir mytempbackupcd mytempbackupdb2 backup db xmeta

Note: You can store more than one database backup in the same temporarydirectory.After the backup completes, a confirmation message is displayed:Backup successful. The timestamp for this backup image is :20101101161943

3. Transfer the backup files from the primary server to the standby server.4. Log in to the standby server. Use your DB2 user ID.5. Run this command to restore the database on the standby server:

db2 restore db database from database_backup_directory replace history file

For example:db2 restore db xmeta from mytemprestore replace history file


6. On the standby server, run the following commands to specify the HADRprimary server and standby server. In the command, specify the standby serverfor hadr_local_host. Specify the primary server for hadr_remote_host (theopposite of the settings on the primary server).db2 update db cfg for database using hadr_local_host standby_IPdb2 update db cfg for database using hadr_remote_host primary_IP

For example:db2 update db cfg for xmeta using hadr_local_host 192.0.2.7db2 update db cfg for xmeta using hadr_remote_host 192.0.2.6

7. On the standby server, run the following commands to specify the HADRprimary and standby service names. In the command, specify the standbyserver port name for hadr_local_svc. Specify the primary server port name forhadr_remote_svc (the opposite of the settings on the primary server).db2 update db cfg for database using hadr_local_svc standby_svc_namedb2 update db cfg for database using hadr_remote_svc primary_svc_name

For example:db2 update db cfg for xmeta using hadr_local_svc ha_myhadr_intdb2 update db cfg for xmeta using hadr_remote_svc ha_myhadr

8. On the standby server, run the following command to set up automatic clientreroute. Specify the primary server IP address and port number in thecommand:db2 update alternate server for database database using hostname primary_IP

port port

For example:db2 update alternate server for database xmeta using hostname 192.0.2.6

port 60000

9. On the standby server, run the following command to verify your configurationvalues:db2 get db cfg for database | grep HADR

For example:db2 get db cfg for xmeta | grep HADR

The command displays a report:HADR database role = STANDARDHADR local host name (HADR_LOCAL_HOST) = mystandby.example.comHADR local service name (HADR_LOCAL_SVC) = ha_myhadr_intHADR remote host name (HADR_REMOTE_HOST) = myprimary.example.comHADR remote service name (HADR_REMOTE_SVC) = ha_myhadrHADR instance name of remote server (HADR_REMOTE_INST) = db2inst1HADR timeout value (HADR_TIMEOUT) = 120HADR log write synchronization mode (HADR_SYNCMODE) = SYNC

Specifying the alternate database address and port for IBMWebSphere Application Server

To enable WebSphere Application Server to communicate with more than oneserver, specify an alternate database address and port.

Procedure1. Start the WebSphere Application Server administrative console.2. Log in as the WebSphere Application Server administrator (default:

wasadmin), or as another user with administrative privileges.


3. In the navigation pane, expand Resources, expand JDBC, and click JDBCProviders. The JDBC providers page appears.

4. Click ASB JDBC Provider.5. Under Additional Properties, click Data sources.6. For each of the data sources listed in the window, perform these steps:

a. Click the data source.b. Under Additional Properties, click Custom Properties.c. Click clientRerouteAlternateServerName. If this property is not present,

click New and add the property and value.d. In the Value field, type the alternate server address. This address is the

physical IP address of the standby server.e. Click OK.f. Click clientRerouteAlternatePortNumber. If this property is not present,

click New and add the property and value.g. In the Value field, type the port number of the standby server.h. Click enableSeamlessFailover. If this property is not present, you can click

New and add the property and value.i. In the Value field, type 1.

This property controls whether the server returns an error that indicatesthat failover occurred. For more information, see the DB2 database systemdocumentation.

j. Click OK.k. Click New.l. In the Name field, type maxRetriesForClientReroute

m. In the Value field, type 2. This parameter sets the number of connectionretry attempts.

n. Click Apply.o. In the Name field, type retryIntervalForClientReroute This parameter

sets the sleep interval between retry attempts.p. In the Value file, type 15.

Note: You might want to set these values differently. The values youchoose depend upon the hardware and the topology of your configuration.

q. Click OK.r. Click Apply.s. In the Messages box at the top of the page, click Save to apply the

changes to the master configuration.t. Click the data source name in the line at the top of the page to return to

the data source page.u. Click Test Connection to test the connection.v. Continue with step (a) for the next data source.

7. In the navigation pane, under Resources → JDBC, click ASB XA JDBCProvider. The JDBC providers page appears.

8. Under Additional Properties, click Data sources.9. Repeat step 6 for each data source that is listed in the window.

10. Log out of the console.11. Add the alternate server name and port number to the

repository_database.xml file. This file is located in the following .jar file:


v Windows opt/IBM/InformationServer/ASBServer/apps/lib/obj-conf.jar

v Linux UNIX C:\IBM\InformationServer\ASBServer\apps\lib\obj-conf.jar

In a configuration that includes WebSphere Application Server clustering, thefile is on the server that hosts the Deployment Manager. In a configurationwithout WebSphere Application Server clustering, the file is on the servicestier computer.To modify the repository_database.xml file:a. Make a backup copy of the obj-conf.jar file.b. Use an unzip utility to extract the repository_database.xml file from the

obj-conf.jar file.c. Open the repository_database.xml file by using a text editor.d. Locate the <jdbc-connection-descriptor> element in the file that has a

dbalias attribute. This element is typically the second<jdbc-connection-descriptor> element in the file. For example:<jdbc-connection-descriptor batch-mode="true" dbalias="//192.0.2.15/xmeta" default-connection="false" driver="com.ibm.db2.jcc.DB2Driver" eager-release="false" ignoreAutoCommitExceptions="false" jcd-alias="pojo" jdbc-level="2.0" password="{xor}tIakDPBAIX2Ao1nHR8j/+A==" platform="Db2" protocol="jdbc" subprotocol="db2" useAutoCommit="2" username="{xor}tIakDPBAIX2Ao1nHR8j/+A==">



e. Modify the element to include the client reroute information. Use the sameserver address and port number that you specified in the previous steps.For example:<jdbc-connection-descriptor batch-mode="true" dbalias="//192.0.2.15:50001/xmetanls:;clientRerouteAlternateServerName=192.0.2.16;clientRerouteAlternatePortNumber=50001;queryCloseImplicit=2;"default-connection="false" driver="com.ibm.db2.jcc.DB2Driver" eager-release="false" ignoreAutoCommitExceptions="false" jcd-alias="pojo" jdbc-level="2.0" password="{xor}tIakDPBAIX2Ao1nHR8j/+A==" platform="Db2" protocol="jdbc" subprotocol="db2" useAutoCommit="2" username="{xor}tIakDPBAIX2Ao1nHR8j/+A==">



f. Save your changes.g. Use a zip utility to replace the repository_database.xml file in the

obj-conf.jar file with your modified version.12. Restart WebSphere Application Server.

Starting HADRStart high availability disaster recovery (HADR) on the standby server, and thenon the primary server.

Before you begin

Make sure to configure the HADR variables as described in the previousinformation. If the parameters are not configured correctly, the HADR servers donot start.


Procedure1. On the standby server, run the following command to deactivate the database:

db2 deactivate db database

For example:db2 deactivate db xmeta

2. On the standby server, run the following command to start HADR on thestandby server:db2 start hadr on db database as standby

For example:db2 start hadr db xmeta as standby

The following message is displayed:DB2000I The START HADR ON DATABASE command completed successfully

3. On the standby server, run the following command to verify the HADR role ofthe server:db2 get snapshot for db on database | grep Role

For example:db2 get snapshot for db on xmeta | grep Role

The following line is displayed:Role = Standby

4. On the primary server, run the following command to activate the database:db2 activate db database

For example:db2 activate db xmeta

5. On the primary server, run the following command to start HADR on theprimary server:db2 start hadr on db database as primary

For example:db2 start hadr db xmeta as primary

The following message is displayed:DB2000I The START HADR ON DATABASE command completed successfully

6. On the primary server, run the following command to verify the HADR role ofthe server:db2 get snapshot for db on database | grep Role


The following line is displayed:Role = Primary

7. On each server, run the following command to verify that the databases aresynchronized:db2 get snapshot for database on database | grep State


For example:db2 get snapshot for database on xmeta | grep State

After the standby database makes the connection to the primary database, thestate is reported as Peer:

State = Peer

Validating the HADR configurationAfter you configure high availability disaster recovery (HADR), validate yourconfiguration and test the takeover function.

Before you begin

Configure HADR on your primary and standby servers, and start HADR on theservers.

About this task

Use the IBM DB2 Control Center to verify the connection status. Then initiate atakeover and a failback to test the takeover function.

Procedure1. On the primary server, start the IBM DB2 Control Center.2. In the left pane, locate the database.3. Right-click the database name and select High Availability Disaster Recovery

→ Manage. The Manage High Availability Disaster Recovery (HADR) windowis displayed.

4. Verify that the Connection status field reads Connected.5. Log in to the primary server as an administrator.6. On the primary server, run the following command to initiate a DB2 HADR

takeover:db2 takeover hadr on db database

For example:db2 takeover hadr on db xmeta

When the takeover is complete, the following result is displayed:DB2000I The TAKEOVER HADR ON DATABASE command completed successfully.

7. Log in to the standby server as an administrator.8. On the standby server, run the following command to determine the status of

the database:db2 get snapshot for db on database | grep Role


When the takeover is successful, the following result is displayed for thestandby server:

Role = Primary


9. Check the IBM WebSphere Application Server log file SystemOut.log todetermine whether the application server successfully connected to thestandby database. To locate this file, see “IBM WebSphere Application Serversystem log files” on page 394.If automatic client reroute worked correctly, the log file indicates thatWebSphere Application Server first tried to connect to the primary server.When that connection failed, automatic client reroute connected successfully tothe standby server. The following log file excerpt shows these events:[11/1/10 17:15:39:298 CST] 00000039 ServletWrappe E SRVE0068E: Uncaughtexception thrown in one of the service methods of the servlet: /dbview.jsp.Exceptionthrown : javax.servlet.ServletException: A connection failed buthas been re-established. The hostname or IP address is "myprimary.example.com"and the service name or port number is 60000 . Special registers may or maynot be re-attempted (Reason code = 1 DB2ConnectionCorrelator:G9056D89.O37F.061101231714

10. Log in to the standby server as an administrator.11. On the standby server, run the following command to initiate a DB2 HADR

failback:db2 takeover hadr on db database

For example:db2 takeover hadr on db xmeta

When the failback is complete, the following result is displayed:DB2000I The TAKEOVER HADR ON DATABASE command completed successfully.

12. On the primary server, run the following command to determine the status ofthe database:db2 get snapshot for db on database | grep Role


When the takeover is successful, the following result is displayed for theprimary server:

Role = Primary

13. On each server, run the following command to verify that the databases aresynchronized:db2 get snapshot for database on database | grep State

For example:db2 get snapshot for database on xmeta | grep State

After the standby database makes the connection to the primary database, thestate is displayed as Peer:

State = Peer

Configuring the metadata repository database in an Oracle RACcluster

Use this road map to create a metadata repository tier setup that includes ametadata repository database that is set up in an Oracle Real Application Clusters(RAC) configuration.


IBM InfoSphere Information Server does not support Oracle RAC configurations ofthe IBM InfoSphere Information Analyzer analysis database or the IBM InfoSphereQualityStage Match Designer database.

Complete the tasks in the following table.

Table 106. Configuring the metadata repository database in an Oracle RAC cluster


Prepare the Oracle RAC cluster. “Oracle RAC requirements”

Use the scripts that are provided with theIBM InfoSphere Information Serverinstallation media to configure the metadatarepository database within the cluster. Thenrun the InfoSphere Information Serverinstallation program to install InfoSphereInformation Server software.

Within the installation program, specify asingle node in the Oracle RAC configuration.

“Creating the metadata repository databaseand running the installation program withinan Oracle RAC configuration”

After you complete the installation, modifythe JDBC driver configuration to causeInfoSphere Information Server to operatewith the complete Oracle RACconfiguration.

“Connecting to an Oracle RACconfiguration” on page 358

To deploy a clustered topology, you must have a solid understanding of networktechnologies such as protocols, layers, devices, and so on. Clustered topologies aretechnically complex, and require expertise to implement successfully.

Oracle RAC requirementsFollow these guidelines when configuring your Oracle Real Application Clusters(RAC) environment for IBM InfoSphere Information Server. If you are installinginto an existing Oracle RAC implementation, make sure that your installationfollows these guidelines.

Follow Oracle database documentation to set up and configure your cluster.

JDBC drivers are shipped with InfoSphere Information Server. They are installedwhen you run the installation program and install services tier components.

Use the services Transparent Failover configuration (TAF policy) to orchestrate howfailover occurs during run time.

When you set up Oracle RAC, modify the tnsnames.ora configuration file for useby the sqlplus user so that connection and failover operate correctly.

Creating the metadata repository database and running theinstallation program within an Oracle RAC configuration

Use the scripts that are provided with the IBM InfoSphere Information Serverinstallation media to configure the metadata repository database within the OracleRAC configuration. Then run the InfoSphere Information Server installationprogram.


Procedure1. To create the metadata repository database, use the scripts that are supplied

with the InfoSphere Information Server installation media. See “Using adatabase system other than DB2” on page 152.

2. Run the InfoSphere Information Server installation program in graphical modeas described in “Creating an installation” on page 167. Complete the entireInfoSphere Information Server installation as described in “Sample scenario D:Topology with clustered metadata repository tier and services tier” on page 114.From the installation program, specify a single node in the Oracle RACconfiguration.

Connecting to an Oracle RAC configurationAfter you complete your services tier installation, modify the JDBC driverconfiguration to cause IBM InfoSphere Information Server to operate with thecomplete Oracle RAC configuration.

About this task

When you installed the services tier as described in “Creating the metadatarepository database and running the installation program within an Oracle RACconfiguration” on page 357, you provided the connection information for a singlenode of the Oracle RAC configuration, by using the normal host and system ID(SID) information. After the installation, redirect IBM WebSphere ApplicationServer to use an Oracle RAC connection string.

In an Oracle RAC configuration, a service name is shared among the differentnodes in the cluster. This service name is in the connection string. Also, each of thenodes in the cluster is listed in the string as alternate server. If the primary nodegoes offline, the database connection is immediately reestablished to one of thealternate servers.

The connection string has the following format:

primaryhost:port;serviceName=SID;alternateServers=(altserver1:port,altserver2:port,...)

For example, in a three-node cluster, the nodes might be named as follows:

Table 107. Example node names

Host SID

rac1 orce1

rac2 orce2

rac3 orce3

If they share the SID orce, a valid connection string for the connection is:rac1:1521;serviceName=orce;alternateServers=(rac1:1521,rac2:1521,rac3:1521)

Procedure1. Update the metadata repository configuration for the new connection string.

See “Changing the metadata repository database host name and port” on page292.

2. Change the string in the WebSphere Application Server configuration. See“Specifying the alternate database address and port for IBM WebSphereApplication Server” on page 342.


Part 6. Removing IBM InfoSphere Information Server software

To remove InfoSphere Information Server from your computers, use the softwareremoval utilities or remove the software manually.



Chapter 25. Software removal by using the software removalprogram

To remove IBM InfoSphere Information Server software from your computers, youcan run the InfoSphere Information Server software removal program.

You can remove the entire software suite, individual product modules, orindividual software tiers.

Attention: Removing the entire software suite, individual product modules, orindividual software tiers will result in data loss. Make sure all file systems anddatabases are backed up before beginning a software removal. See the IBMInfoSphere Information Server Administration Guide.

The first time that you run the software removal program, use graphical mode.The program displays a graphical wizard that prompts you for options. After youcomplete the wizard, you save your settings in a response file. Then you cancontinue in the wizard to complete the software removal. Alternatively, you canexit the program after saving the response file. The next time you run the programin graphical mode, you can load in the settings in your response file instead ofspecifying them again.

Alternatively, you can run the program in silent mode. In silent mode, the programuses the settings in a response file and does not display the graphical interface.

Shutting down tasks and applications before removing softwareBefore running the software removal program, shut down scheduled tasks anddisable IBM InfoSphere Information Services Director applications.

Procedure1. (Installations with Pack for SAP BW or Pack for SAP R/3, engine tier) Shut

down the SAP BW and SAP R/3 listeners. For details on shutting down thelisteners, see www.ibm.com/support/docview.wss?uid=swg21409098.

2. (Services and engine tiers) Shut down all scheduled tasks, such as reports andlog purge activities. To shut down these tasks, create an unfiltered scheduleview within the IBM InfoSphere Information Server Web console, and then stopall scheduled tasks that are displayed in the view.a. Log in to the IBM InfoSphere Information Server Web console with an

account that has the suite administrator role.b. In the Web console, click the Administration tab.c. In the Navigation pane, select Scheduling Management → Scheduling

Views.d. In the Scheduling Views pane, click New.e. Enter a name and description in the Name and Description fields.f. Click Save and Close.g. Select the schedule view that you created in the previous steps.h. Click View Schedules.i. Select a schedule in the list, and click View Task.



j. Look at the Status value in the Schedule section:v If the Status value is STARTED, click Close, and then click Stop to stop

the task. If you are removing a product module or a tier, write down thename of the schedule so that you can restart it after the software removalis completed.

v If the Status value is not STARTED, click Close.k. Repeat steps (i) through (j) for each schedule in the list. For a product

module or tier removal, do not restart the scheduled tasks until both theservices and engine tiers are updated.

3. (Services and engine tiers) Disable any InfoSphere Information Services Directorapplications that are currently running.a. Log in to the IBM InfoSphere Information Server console with an account

that has the suite administrator role.b. Select OPERATE → Deployed Information Services Applications.c. From the View pane, select a deployed application.d. Click Edit.e. In the bottom of the View pane, click Disable and select Disable from the

menu.f. Repeat these steps for each deployed application. For a product module or

tier removal, do not reenable the deployed applications until both theservices and engine tiers are updated.

Removing an IBM InfoSphere Information Server installationTo remove an entire InfoSphere Information Server installation, run the InfoSphereInformation Server software removal program on each computer.

Before you beginv Do the preparation steps that are described in “Preparing to run the software

removal program” on page 368.v Make sure that your browser is configured correctly. See “Configuring your


Attention: Removing an InfoSphere Information Server installation also deletesany projects, jobs, models, and other user-created items that are associated withthat installation. Before you remove the software, make sure that you have backedup all computers in the installation. See the IBM InfoSphere Information ServerAdministration Guide.

About this task

Run the software removal program on all target computers, in the following order:1. Client.

You can run the removal program on any point in the sequence.2. Engine, if your installation includes an engine tier.3. Services.

If you installed IBM WebSphere Application Server by using the installationprogram, WebSphere Application Server is removed when the services tier isremoved.


If you preinstalled the application server, components that are specific toInfoSphere Information Server are removed. However, the application server isnot removed.

4. Metadata repository.If you installed IBM DB2 by using the installation program, the metadatarepository database (and analysis database, if present) are dropped and DB2 isremoved.If you used the installation program to create the metadata repository databaseor analysis database in a preinstalled DB2 instance, the databases are dropped.However, DB2 is not removed.If you did not create the metadata repository tier by using the installationprogram, do not use the installation program to remove the metadatarepository tier.

You run the software removal program only once on each computer, even if thecomputer hosts more than one tier. The installation program removes the tiercomponents in the correct order.

Attention: All projects, jobs, and other items that exist within InfoSphereInformation Server are deleted when you remove the products that created theprojects.


Information Server installation, so you can roll back the removal process ifnecessary. See the IBM InfoSphere Information Server Administration Guide.

2. Shut down scheduled tasks and IBM InfoSphere Information Services Directorapplications. See “Shutting down tasks and applications before removingsoftware” on page 361.

3. Run the software removal program as described in “Graphical mode” on page369.

4. Complete the wizard pages and start the software removal process.

What to do next

Do the following tasks when the software removal process completes:

v Windows “Completing software removal (Windows)” on page 378

v Linux UNIX “Completing software removal (Linux, UNIX)” on page 380

If a failure occurs, remove the software manually:

v Windows “Manually removing IBM InfoSphere Information Server (Windows)”on page 383

v Linux UNIX “Manually removing IBM InfoSphere Information Server(Linux, UNIX)” on page 386

Removing individual product modulesTo remove an IBM InfoSphere Information Server product module from yourinstallation, run the InfoSphere Information Server software removal program oneach computer that contains components of the product module.

Chapter 25. Software removal by using the software removal program 363

Before you beginv Do the preparation steps that are described in “Preparing to run the installation

program” on page 177.v Make sure that your browser is configured correctly. See “Configuring your


Attention: Removing a product module also deletes any user-created items thatare associated with that product module. Before you remove software, make surethat you have backed up all computers in the installation. See the IBM InfoSphereInformation Server Administration Guide.

To deactivate an IBM InfoSphere DataStage edition or feature pack (for example, ifyou are no longer entitled to an item), you do not use the IBM InfoSphereInformation Server software removal program. Instead, deactivate them by usingthe LicensingServiceAdmin tool. Refer to the IBM InfoSphere Information ServerAdministration Guide.

About this task

Depending upon the product modules that you select, you might not have to runthe software removal program for all tiers. Not all product modules havecomponents on all tiers. You only need to run the program on the tier computersthat contain components for the product modules. You can skip tier computers thatdo not contain components for the product modules. If you run the program on acomputer that does not contain components for the product modules, nocomponents are removed.

The following table lists product modules and indicates the tier computers onwhich you must run the software removal program:







Services


The installation program only removes the appropriate software for the tiers on acomputer. You can run the software removal program on all of the computers inyour configuration, and select all tiers each time. The removal program determinesautomatically which tiers exist on each computer and removes the appropriatecomponents.

Run the program on the computers in the following order:1. Client, if the product modules you are removing require changes to this tier.

The client tier software removal can take place at any point in the sequence.2. Engine, if needed. Refer to the table to determine whether you need to run the

software removal program on the engine tier.


3. Services. All product module removals require changes to the services tier.4. Metadata repository, if the product modules you are removing require changes

to this tier.If you preinstalled the database system for the metadata repository tier andconfigured the databases within the database system by using the scripts thatare supplied with the installation media, the software removal program doesnot remove the database system.

For example, to remove InfoSphere Information Analyzer, first run the softwareremoval program on the engine tier computer. Then run it on the services tiercomputer. Lastly, run the program on the metadata repository tier. You can run thesoftware removal program on the client tier computers at any point in thesequence.

You only need to run the software removal program one time on each computereven if the computer hosts more than one tier. The installation program removesthe tier components in the correct order on the computer.

If you remove all product modules that require a particular tier, the tier is alsoremoved. For example, in a system that includes InfoSphere DataStage andInfoSphere Business Glossary, if you remove InfoSphere DataStage, the entireengine tier is removed because InfoSphere Business Glossary does not require it.

Attention: All projects, jobs, and other items are deleted when a tier is removed.

Notes about specific product module removal tasks:v InfoSphere DataStage and InfoSphere QualityStage share many components

between them. For this reason, if you remove one of these product modulesfrom the system on which the other product module is installed, the removalprocess is extremely rapid.

v Many of these components are also shared by InfoSphere Information Analyzer.The removal process for this product module is faster if InfoSphere DataStage orInfoSphere QualityStage remains installed.

v If both InfoSphere Business Glossary and InfoSphere Metadata Workbench areinstalled, you must remove both. If only one of these product modules isinstalled, you can remove it.

v If multiple versions of InfoSphere DataStage client programs are installed on acomputer and you remove the Version 8.5 InfoSphere DataStage client programs,older versions of the client programs might not function. If you want to retainthe older InfoSphere DataStage client programs do the following tasks:1. Remove the InfoSphere DataStage, Version 8.5 client programs.2. Remove all older InfoSphere DataStage client programs.3. Reinstall the older versions, starting from the oldest version to the most

recent version that you want to retain.





3. Run the software removal program as described in “Graphical mode” on page369. The software removal program prompts you to select the product modulesto remove. All product modules that have components on this computer aredisplayed in the page.

4. Select the product modules that you want to remove.5. Complete the wizard pages and start the software removal process.

What to do next

When the software removal process completes successfully, perform the followingtask:v “Completing software removal (Windows)” on page 378v “Completing software removal (Linux, UNIX)” on page 380

If a failure occurs, restore your installation from your backup.

Removing a software tierTo remove an IBM InfoSphere Information Server software tier from a computerwhere other tiers are installed, run the InfoSphere Information Server softwareremoval program on the computer.


program” on page 177.v Make sure your browser is configured correctly. See “Configuring your browser”

on page 179.

Attention: Removing an engine tier, services tier, or metadata repository tiermight delete any projects, jobs, models, and other user-created items that areassociated with the installation, or render the items unusable. Removing a clienttier installation deletes any user settings that are stored locally on the clientworkstation. Before you remove software, make sure that you have backed up allcomputers in the installation. See the IBM InfoSphere Information ServerAdministration Guide.

For client tier removals: On a computer on which more than one version of theclient tier is installed, removing any client tier version renders the other versionsunusable. To remove a particular client tier version from a computer, remove allversions. Then reinstall the versions that you want to have on the computer.

About this task

To remove one or more software tiers, run the removal program on the targetcomputer. The program removes all InfoSphere Information Server product modulecomponents that belong to the selected tiers. Also, the program removes allInfoSphere Information Server common components that belong to the selectedtiers.

You run the software removal program only once on each computer even if youare removing more than one tier. The removal program removes the tiers in thecorrect order. The engine tier is dependent on the services tier, and the services tier


is dependent on the metadata repository tier. If more than one tier is installed on acomputer, you cannot uninstall a tier without uninstalling the tiers that aredependent on it.

If you remove the services tier:v If you installed IBM WebSphere Application Server by using the installation

program, WebSphere Application Server is removed.v If you preinstalled the application server, components that are specific to

InfoSphere Information Server are removed. However, the application server isnot removed.

If you remove the metadata repository tier:v If you installed IBM DB2 by using the installation program, the metadata

repository database (and analysis database, if present) are dropped and DB2 isremoved.

v If you used the installation program to create the metadata repository databaseor analysis database in a preinstalled DB2 instance, the databases are dropped.However, DB2 is not removed.

v If you did not create the metadata repository tier by using the installationprogram, do not use the installation program to remove the metadata repositorytier.

Attention: All InfoSphere Information Server projects, jobs, and other items aredeleted when you remove any tier except the client tier.




3. Run the software removal program on the computer as described in “Graphicalmode” on page 369. The software removal program prompts you to select thetiers to remove. All tiers that are installed on the computer are enabled in thepage.

4. Select the tiers to remove.5. Complete the wizard pages and start the software removal process.

What to do next

If the software removal process succeeds, perform these additional softwareremoval steps for your operating system:v “Completing software removal (Windows)” on page 378v “Completing software removal (Linux, UNIX)” on page 380

If a failure occurs, restore your installation from your backup.

Starting the software removal programYou can run the IBM InfoSphere Information Server software removal program ingraphical mode or silent mode.


Preparing to run the software removal programBefore you run the software removal program to remove an installation or toremove product modules or tiers, back up critical data on your computers andmake sure that the computers are ready for the removal process.

Procedure

Follow this procedure for each target computer:1. If you run the software removal program in graphical mode, make sure that the

browser is configured so that the program runs correctly. See “Configuringyour browser” on page 179.

2. Back up your current IBM InfoSphere Information Server components andcritical data. See the IBM InfoSphere Information Server Administration Guide.Also, back up the following items:

Linux UNIX

Back up /etc/services, /etc/inittab, /etc/passwd, and /etc/group.

Windows

Back up the Microsoft Windows registry and the C:\Windows\System32\drivers\etc directory.

3. Windows The software removal program requires the Windows Script Engineto operate. To test your Windows Script Engine installation, see “"There is noscript engine for file extension '.js'" message appears during installation” onpage 400.

4. Disable all scheduled jobs, scheduled tasks, scheduled reports, and enabledIBM InfoSphere Information Services Director applications before running thesoftware removal program.

5. Disable firewall software and antivirus software during the software removalsession.

6. Windows When you run the software removal program in graphical mode, themessage, "The publisher cannot be verified..." might be displayed in thebrowser. You can safely ignore the message and continue the software removal.This message does not indicate a security risk when it appears duringInfoSphere Information Server installation.

7. Windows Make sure that the following directories are in your system path:v %SystemRoot%

v %SystemRoot%\system32

v %SystemRoot%\system32\wbem

8. For an installation that involves WebSphere Application Server clustering,perform the following tasks:v Start management processes, including the node agents, before you begin the

software removal. To ensure that sufficient file descriptor resources areallocated to the processes use the ulimit command. See “Running theinstallation program (clustered installation)” on page 330.

v Verify that you can start and stop the cluster and that you can restart thenode agents. See the IBM InfoSphere Information Server AdministrationGuide.

v Verify that you can stop and start the Web server.9. If the WebSphere Application Server processes or node agents are currently

running under a non-root user, log in as the non-root user and stop the


processes. Then log in as root, change the ownership of the WebSphereApplication Server installation directory and profile directory to be root. Thenstart WebSphere Application Server as root.

Configuring your browserMake sure that the browser is configured so that the installation program runs ingraphical mode.

Locate your browser type in the following sections, and configure it so that theinstallation program runs correctly.

All browsersv Verify that you have a supported browser. For details, go to the system

requirements at www.ibm.com/support/docview.wss?rs=14&uid=swg27016382.v Make sure that JavaScript is enabled.

Microsoft Internet Explorer

Make sure that the security zone for the computer allows the installation programto run:1. From Microsoft Internet Explorer, in the Tools menu, select Internet Options.2. Click the Security tab.3. Click the Trusted Sites icon.4. Click Sites.5. In the Add this Website to the zone field, type http://hostname where

hostname is the host name of the computer on which the install program willrun.

6. Click Add.7. Click OK.8. Click OK.

Mozilla Firefox

Make sure that images load automatically and that JavaScript is enabled:1. In the Tools menu, click Options. The Options window displays.2. Click Content.3. Enable Load images automatically.4. Enable Enable JavaScript.5. Click OK.

Graphical modeIn graphical mode, the software removal program displays the user interface in astandard Web browser.

To run the software removal program in graphical mode, you can use a Webbrowser locally on the target computer. Alternatively, you can use a browser onany system that has network access to the computer where the program isrunning.

To provide security during the software removal process, access to the softwareremoval application is password protected. When you first start the softwareremoval program, a non-graphical interface is displayed. You are prompted to



create a password to use for the software removal session. You can start a Webbrowser on the computer or on a remote computer and access the graphicalinterface. On Microsoft Windows computers, the program automatically opens thedefault Web browser on the local computer to display the graphical interface.

The first wizard page prompts you to log in by using the password you created.

After you choose your settings in the graphical interface, the program stores yoursettings in a response file. If you run the software removal program again, you canuse the response file to perform the same software removal process again.

Starting the software removal program in graphical modeThe software removal program leads you through the process of removing IBMInfoSphere Information Server.


program” on page 177.v Make sure that your browser is configured correctly. See “Configuring your

browser” on page 179.v Shut down scheduled tasks and IBM InfoSphere Information Services Director

applications. See “Shutting down tasks and applications before removingsoftware” on page 361.

About this task

The software removal program displays a wizard that prompts you for parametersand other data. While you are using the wizard:

v Windows You might see a security warning or notification when uninstall.exeor java.exe are run. When a security notification opens, you can safely clickRun or Yes to allow the program to run and continue with the uninstallation.

v If you close your browser while the wizard is running, you can continue thesame session by opening the browser again and reconnecting to the session.

v If your browser displays a "server busy" message, select the Continue option.You can also close the browser and then reconnect to same session.

v The wizard times out if there is no activity within two hours.



v Windows Log in to the target computer as a local administrator or as alocal or domain user who is directly assigned to the local Administratorsgroup.

2. Linux UNIX Open a command prompt or shell window.a. Open the window on the target computer, or use a graphical desktop

sharing system. Keep the shell window open during the entire softwareremoval process. If you use telnet or ssh, make sure that the session doesnot shut down or timeout for the duration of the software removal.

b. Run the following command to clear any Java options that might be set:




c. Set the file creation mask to 022:umask 022

d. Ensure that you have enough file descriptor resources allocated for thesoftware removal. Set the file descriptor limit to 10240, a higher value, orunlimited. For example:ulimit -n 10240

e. Check that the current setting for the NOFILES kernel parameter is set to avalue that is at least equal to the value that you specify for ulimit.

f. Linux If the installation directory for InfoSphere Information Server,IBM WebSphere Application Server, or IBM DB2 is an NFS file system,ensure that the lock daemon is running.ps -ef | grep -i lockd


3. Run the software removal program:

Linux UNIX

a. Change to the _uninstall directory within the InfoSphereInformation Server installation directory. By default, this directoryis /opt/IBM/InformationServer.

b. Enter the following command:./uninstall

Windows

a. In the Control Panel, double-click Add or Remove Programs.b. Click IBM InfoSphere Information Server.c. Click Change/Remove.

A welcome message is displayed. Then the program describes how to accessthe graphical interface:======> Installer available at: http://localhost:8080/ISInstall,and https://localhost:8443/ISInstall

4. Open a Web browser on the computer or on a remote computer, and navigateto one of the addresses that are listed in the messages that are displayed inthe previous step.

Note: Windows The software removal program automatically opens thedefault Web browser on the local computer and navigates to the HTTPaddress.A Login Uninstallation window is displayed in the Web browser window.A message might appear in the browser that reads "The publisher cannot beverified..." You can ignore the message and continue the software removal.This message does not indicate a security risk when it appears duringInfoSphere Information Server installation or software removal.

5. To display messages in a language other than English, select the language inthe Select a language field.

6. Click Login.7. Follow the prompts in the wizard. After you accept the license agreement, the

program runs a short prerequisites check. The wizard page displays each


check. If the check fails, it is marked FAILED in the page. If the check foundissues that might cause problems with the installation, it is markedWARNING in the page.

8. If you receive a FAILED or WARNING message:a. Double-click the message to learn more about resolving it.b. Try to resolve the issue without exiting the software removal program.

Then click Check Again in the Prerequisites Check page.c. If you must exit the program, click Cancel, close the browser window, and

type Ctrl+c in the session window to end the session. Resolve the issues,and then restart the program.

9. When all prerequisites checks pass, continue to follow the prompts in thewizard. The software removal program prompts you for the software removaltype. You can remove an entire installation, remove specific product modules,or remove a software tier from a computer. Then the wizard prompts you forinformation that is specific to the type of software removal that you selected.After the program collects your selections, it displays a Response File Reviewpage.

10. In the Response file location field, specify a name and location for theresponse file.

Note: The passwords that you create for the session are not saved in theresponse file. To use the response file in a subsequent software removal pass,you must first edit the response file and add passwords. To edit the responsefile, use a text editor.

11. At this point, you can choose to cancel the software removal and use thesaved response file in a later session. To continue, click Next.v To continue with the software removal, click Remove IBM InfoSphere

Information Server and save my settings in a response file and then clickNext.

v To cancel the software removal, click Do not remove IBM InfoSphereInformation Server and save my settings in a response file and then clickNext. Click OK in the confirmation window that appears.

12. If you choose to continue with the software removal, the program displays asummary of the choices that you made in the wizard. When you click Next,the program begins the software removal. While the program is running keepthe following tips in mind:v Leave the terminal window open until the software removal is complete.v The system might occasionally request a response from you. Check

periodically to make sure that the system is not waiting for you to respond.If the software removal process pauses for a long time, it might fail.

v Pop-up windows might be displayed, which you must respond to for thesoftware removal to proceed. Occasionally a pop-up window might bedisplayed behind the browser window. If the program halts for a longinterval, check for pop-up windows displayed behind the browser window.

v After you have started the software removal process, keep the browserwindow open to monitor progress and to respond if there is an error. If youclose the Web browser, the software removal process continues to the end.You can reconnect to the session by opening a new browser session to thesame URL. You can also monitor the process by reading log files.

If the software removal program encounters a problem, an InstallationException window opens.


v If this is the first time that the software removal program has encounteredthis problem, click Retry failed action and click OK.

v If the problem recurs, perform these tasks:a. Review the last statements in the log file. See Chapter 27, “Log files,” on

page 393.b. If the issue can be resolved, fix the issue and then click Retry.c. If you cannot resolve the issue, click Exit uninstallation and click OK.

Then use the following task to manually remove the entire suite:– “Manually removing IBM InfoSphere Information Server (Windows)”

on page 383– “Manually removing IBM InfoSphere Information Server (Linux,

UNIX)” on page 386v Do not continue a software removal by using the program if there are

errors.When the installation is complete, an Installation Summary window opens.The following message is written to the log file:Installation Engine completed all steps successfully.

13. Click Finish or close the browser window.


What to do next

If the software removal process succeeds, perform the following task:v “Completing software removal (Windows)” on page 378v “Completing software removal (Linux, UNIX)” on page 380

Restarting in graphical mode with a response fileYou can load settings from a response file into the software removal program.

Before you begin

Use a response file that the software removal program created, or use a text editorto create a response file. See “Response files” on page 191.

Note: No passwords (administrator passwords, database passwords, and so on)are saved in the response file that the software removal program creates. Beforeyou use the response file, use a text editor to add any required passwords to thefile. Then after the software removal, remove the passwords from the file.

About this task

After you choose settings in the graphical interface, the program saves yoursettings in a response file. If you run the software removal program again, you canuse the response file to perform the same software removal process again.

Alternatively, you can run the software removal program in silent mode. In thismode, the program uses the settings in the response file but does not display thegraphical interface.






v Linux UNIX Open a command prompt or shell window.Open the window on the target computer, or use a graphical desktop sharingsystem. Keep the shell window open during the entire software removalprocess. If you use telnet or ssh, make sure that the session does not shutdown or timeout for the duration of the software removal.







v Windows


4. Linux UNIX Make these additional settings to help ensure that thesoftware removal is successful:v Set the file creation mask to 022:

umask 022

v Ensure that you have enough file descriptor resources allocated for thesoftware removal. Set the file descriptor limit to 10240, a higher value, orunlimited. For example:ulimit -n 10240


v Linux If the installation directory for IBM InfoSphere Information Server,IBM WebSphere Application Server, or IBM DB2 is an NFS file system,ensure that the lock daemon is running.ps -ef | grep -i lockd



Linux UNIX

a. Change to the _uninstall directory within the InfoSphere InformationServer installation directory. By default, this directory is/opt/IBM/InformationServer.

b. Enter the following command:./uninstall -uimode graphical -rsp response_file_name


where response_file is the path and name of your response file.

Windows

a. Change to the _uninstall directory within the InfoSphere InformationServer installation directory. By default, this directory isC:\IBM\InformationServer.

b. Enter the following command:uninstall -uimode graphical -rsp response_file_name

The software removal program begins to display messages in the window.6. Follow the steps in “Starting the software removal program in graphical mode”

on page 370 to log in and use the wizard. Each wizard page displays thesettings that you specified in the response file. If necessary, you can change thevalues in the wizard.

Silent modeIn silent mode, the software removal program does not present a user interface.Instead, the program reads settings from a response file and performs aprerequisites check. If the check succeeds, the program removes the software.

Using silent mode, you can run an unattended software removal and performmultiple similar software removals quickly. For example, if you want to removeidentical client tier software from multiple workstations, you can create a singleresponse file and use silent mode to remove the software from each workstation,rather than repeatedly using the graphical user interface.

To run the software removal program in silent mode, perform the following tasks:v Create a response file. See “Response files” on page 191.v Start the software removal program in silent mode. See “Starting the software

removal program in silent mode.”

Starting the software removal program in silent modeTo remove IBM InfoSphere Information Server without starting the graphicinterface, you use silent mode, which reads your previously defined softwareremoval settings from a response file.

Before you begin1. Perform the preparation steps that are described in “Preparing to run the

software removal program” on page 368.2. Create a response file. See “Response files” on page 191.3. Shut down scheduled tasks and IBM InfoSphere Information Services Director

applications. See “Shutting down tasks and applications before removingsoftware” on page 361.





v Linux UNIX Open a command prompt or shell window.


Open the window on the target computer, or use a graphical desktop sharingsystem. Keep the shell window open during the entire software removalprocess. If you use telnet or ssh, make sure that the session does not shutdown or timeout for the duration of the software removal.







v Windows


4. Linux UNIX Make these additional settings to help ensure that thesoftware removal is successful:v Set the file creation mask to 022:

umask 022

v Ensure that you have enough file descriptor resources allocated for thesoftware removal. Set the file descriptor limit to 10240, a higher value, orunlimited. For example:ulimit -n 10240


v Linux If the installation directory for IBM InfoSphere Information Server,IBM WebSphere Application Server, or IBM DB2 is an NFS file system,ensure that the lock daemon is running.ps -ef | grep -i lockd



Linux UNIX

a. Change to the _uninstall directory within the InfoSphere InformationServer installation directory. By default, this directory is/opt/IBM/InformationServer.

b. Enter the following command:./uninstall -rsp response_file_name -verbose

where response_file is the path and name of your response file.

Windows


a. Change to the _uninstall directory within the InfoSphere InformationServer installation directory. By default, this directory isC:\IBM\InformationServer.

b. Enter the following command:uninstall -rsp response_file_name -verbose

where response_file is the path and name of your response file.The -verbose option, which is optional, instructs the program to display logmessages to the console and to write them to the log file. If the -verbose optionis not specified, log messages are written to the log file only.When you start the program, the program begins to display messages in thewindow if the -verbose option is specified. The program runs through aprerequisites check phase. As each prerequisites check runs, the programdisplays a report.If all prerequisites checks pass, the software removal continues. As it runs, itstores log messages in a log file. It also displays the log messages to stdout ifthe -verbose option is specified. For more information, see “Monitoring the IBMInfoSphere Information Server installation” on page 194.If a prerequisite check fails, the software removal program displays errors andstops. The prerequisites check report contains messages that are similar to thefollowing message:FAIL - The current user must have administrative rights.

6. If a prerequisites check fails, correct the problem and restart the program.

7. Windows While the software removal is running, keep these tips in mind:v Leave the terminal window open until the installation is complete.v The system might occasionally request a response from you. Check

periodically to make sure that the system is not waiting for you to respond.If the program pauses for a long time, it might fail.

If the program encounters an error, it halts with a message. You can change thisbehavior by setting the EXCEPTION_POLICY environment variable. See “Errorhandling in silent mode” on page 188.When the installation is complete, the following message appears in the log file:Installation Engine completed all steps successfully.


What to do next

If the software removal process fails, perform the following task to remove thesoftware manually:v “Manually removing IBM InfoSphere Information Server (Windows)” on page

383v “Manually removing IBM InfoSphere Information Server (Linux, UNIX)” on

page 386

If the software removal process succeeds, perform the following task:v “Completing software removal (Windows)” on page 378v “Completing software removal (Linux, UNIX)” on page 380


Completing software removal (Windows)After you remove software from Microsoft Windows computers, perform thesesteps to complete the software removal.

Before you begin

Run the software removal program and make sure that it completed successfully.

Procedure

After you remove IBM InfoSphere Information Server software, perform thefollowing procedure on all affected computers:1. If you created the metadata repository database before you installed InfoSphere

Information Server, manually drop the metadata repository database. Thedefault database name is xmeta.If the IBM InfoSphere Information Analyzer analysis database was createdbefore you installed InfoSphere Information Server, manually drop thedatabase. The default database name is iadb.

2. When you remove suite software, the software removal program removes onlythe files that were created as part of the installation of InfoSphere InformationServer. You must manually remove other files if you plan to reinstall the suite.For each tier that you removed, remove the following files from the targetcomputer, if they still exist:a. (All tier computers) Delete the directory where InfoSphere Information

Server was installed. The default directory is C:\IBM\InformationServer.b. (Services tier computer) If you installed the application server by using the

InfoSphere Information Server installation program, delete the applicationserver directory. The default directory is C:\IBM\WebSphere.

c. (Metadata repository computer) If you used the InfoSphere InformationServer installation program to install the IBM DB2 database system, removethe following directories:v \DB2Home. DB2Home is the directory where the DB2 database system is

installed. The default directory is C:\IBM\sqllib.v x:\DB2, where x is the drive where you installed the DB2 database

system.v %ALLUSERSPROFILE%\Application Data\IBM\DB2

v %ALLUSERSPROFILE%\Application Data\IBM\DB2History

3. On the computer where the services tier is installed, if you installed IBMWebSphere Application Server by using the InfoSphere Information Serverinstallation program, do the additional WebSphere Application Server removalsteps that are listed in the IBM WebSphere Application Server NetworkDeployment, Version 7.0 information center. See http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.websphere.wps.doc/doc/tins_uninstman.html. If the WebSphereApplication Server installation folder is empty, delete the folder. The defaultfolder is C:\IBM\WebSphere\AppServer.

4. If you previously installed older versions of IBM InfoSphere DataStage orInfoSphere Information Server clients, Windows registry keys might remain onthe system after you uninstall the clients. If you have uninstalled all InfoSphereDataStage or InfoSphere Information Server software, delete the followingregistry keys:


http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.websphere.wps.doc/doc/tins_uninstman.html



HKLM\SOFTWARE\Ascential Software\ASBNodeHKLM\SOFTWARE\Ascential Software\DataStage ClientHKLM\SOFTWARE\Ascential Software\DataStage Multi-Client ManagerHKLM\SOFTWARE\Ascential Software\Documentation ToolHKLM\SOFTWARE\IBM\InformationServer

5. Remove users if you no longer need them after you uninstall InfoSphereInformation Server. Use the following command to delete the unused users:net user username /delete

Remove the following users if they are not needed:a. (Metadata repository computer)v If you used the DB2 database system as the metadata repository, you can

remove the following accounts:– The DB2 administration server user (db2admin by default). Delete this

user only if you are also removing DB2.– The owner of the metadata repository (xmeta by default).– If IBM InfoSphere Information Analyzer is installed, the owner of the

analysis database (iauser by default).v If you used an Oracle database system or a Microsoft SQL Server

database system for the metadata repository, use an Oracle databasesystem command or a Microsoft SQL Server database system commandto drop the metadata repository user and schema.

b. (Services tier computer)v If you used the internal user registry, there is no user to remove.v If you used the local operating system user registry, delete the users that

you created for InfoSphere Information Server.6. Delete the groups that contained the deleted users, if you no longer need the

groups.7. (Services tier computer) If you used an existing installation of IBM WebSphere

Application Server, remove the profile that you created for the suite.

Note: If the suite installation program installed the application server, theprofile is removed when you remove the suite from your computer.a. Click Start → All Programs → IBM WebSphere → Application Server →

Profiles → profileName → Stop the server. profileName is the name of theprofile to delete.

b. Open a Windows command prompt.c. Change to the WASHome\bin directory. WASHome is the directory where the

application server is installed. The default directory is C:\IBM\WebSphere\AppServer.

d. Run the following command:manageprofiles.bat -delete -profileName profile

profile is the name of the profile to be deleted.e. Delete the directory for the profile. The directory is in the

WASHome\profiles\profileName directory.8. Remove any remaining InfoSphere Information Server users and groups if you

are not using them for other purposes.9. Restart the computer.


Completing software removal (Linux, UNIX)After you remove software from Linux or UNIX computers, perform these steps tocomplete the software removal.

Before you begin

Run the software removal program and make sure that it completed successfully.

Procedure

After you remove IBM InfoSphere Information Server software, perform thefollowing procedure on all affected computers:1. If you created the metadata repository database before you installed InfoSphere

Information Server, manually drop the metadata repository database. Thedefault database name is xmeta.If you created the IBM InfoSphere Information Analyzer analysis databasebefore you installed InfoSphere Information Server, manually drop thisdatabase. The default database name is iadb.

2. When you uninstall, the installation program removes only the files that werecreated as part of the installation of InfoSphere Information Server. You mustmanually remove other files if you plan to reinstall the suite. For each tier thatyou removed, remove the following files from your computer, if they still exist.a. (All tier computers) If you removed all tiers, delete the directory where

InfoSphere Information Server was installed. The default directories are asfollows:

AIX

/usr/IBM/InformationServer

Linux UNIX

/opt/IBM/InformationServer

b. (Services tier computer) If you installed the application server by using theInfoSphere Information Server installation program, delete the applicationserver directory. The default directory is /opt/IBM/WebSphere/AppServer.

c. (Metadata repository computer) If you installed the DB2 database system byusing the InfoSphere Information Server installation program, remove thefollowing directories:

DB2 installation directoryThe default directory is /opt/IBM/db2/V9.

DB2 instance owner directoryRemove the / ~db2inst1/sqllib directory, where ~db2inst1 is homedirectory of the instance owner. For example, the default homedirectory of the instance owner is typically /home/db2inst1.

DB2 administrator directoryRemove the /~dasusr1 /das directory, where ~dasusr1 is the homedirectory of the DB2 administrator. For example, the default homedirectory of the DB2 administrator is typically /home/dasusr1.

3. On the computer where the services tier is installed, if you installed IBMWebSphere Application Server by using the InfoSphere Information Serverinstallation program, do the additional WebSphere Application Server removalsteps that are listed in the IBM WebSphere Application Server NetworkDeployment, Version 7.0 information center. See http://



publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.websphere.wps.doc/doc/tins_uninstman.html.

4. Remove the following users and groups if you no longer need them after youuninstall InfoSphere Information Server:a. (Metadata repository computer)v If you used the DB2 database system as the metadata repository and it no

longer needs a DB2 user account, you can remove the DB2 user accounts.1) Identify the related groups for the following DB2 user accounts:

dasusr1, db2inst1, and db2fenc1. To find the related groups, run the idcommand for each user. For example:bash-3.00$ id dasusr1uid=210(dasusr1) gid=206(dasadm1) groups=1(staff)

2) After you identify the related group for each user, use the userdelcommand to delete unused user accounts and then use the groupdelcommand to delete the unused related groups.

v If you used an Oracle database system or a Microsoft SQL Serverdatabase system as the metadata repository, use an Oracle databasesystem command or a Microsoft SQL Server database system commandto drop the metadata repository user and schema.

b. (Services tier computer)v If you used the internal user registry, there is no user to be removed.v If you used the local operating system user registry, delete the users that

you created for InfoSphere Information Server.c. (Engine tier computer) If you no longer need the dsadm account, delete this

user and the related group.5. (Services tier computer) If you used an existing installation of IBM WebSphere

Application Server, remove the profile that you created for the suite.

Note: If the suite installation program installed the application server, theprofile is removed when you remove the suite from your computer.a. From a Linux or UNIX shell prompt, change to the WASHome/bin. WASHome

is the directory where the application server is installed. The defaultdirectory is /opt/IBM/WebSphere/AppServer.

b. Run the following command to delete the profile:./manageprofiles.sh -delete -profileName profile

profile is the name of the profile to be deleted.c. Delete the directory for the profile. The directory is in the WASHome/profiles

directory.6. Remove any remaining InfoSphere Information Server users and groups if you

are not using them for other purposes.




Chapter 26. Manual software removal

If a previous installation or removal failed, you might have to manually removethe suite. You remove the software manually only after trying to use the softwareremoval program.

Manually removing IBM InfoSphere Information Server (Windows)If the software removal program fails to uninstall the suite, manually uninstall thesuite.

Before you begin

Before you manually remove software, on each computer in your installation, tryto remove the suite by using the software removal program. If the softwareremoval program fails to operate properly, follow this procedure to remove theentire InfoSphere Information Server instance. You can also use this procedure toclean up any files that the software removal program does not automaticallyremove.


All scheduled tasks must be shut down, and IBM InfoSphere Information ServicesDirector applications must be disabled. See “Shutting down tasks and applicationsbefore removing software” on page 361.

About this task

You cannot manually remove only a single tier or product module. A manualuninstallation must remove the entire instance.

If multiple client versions are installed, you cannot remove only the latest version.You must remove all client versions.

Procedure1. Back up the computer.

2. Windows Open an elevated command window. To install update packages,you must use a command window that is elevated to full administrativeprivileges.a. Click the Microsoft Windows Start menu.b. Enter cmd.exe in the Start Search field.c. Press Ctrl+Shift+Enter.d. Click Continue to accept the prompt asking for your permission to

continue.3. On the computer where the engine tier is installed, remove InfoSphere

Information Server services. From a command prompt, run the followingcommands:


sc stop ASBAgentsc stop LoggingAgentsc stop DSEnginesc stop dsrpcsc stop dstelnet

sc delete ASBAgentsc delete LoggingAgentsc delete DSEnginesc delete dsrpcsc delete dstelnet

4. On the computer where the services tier is installed, if you installed IBMWebSphere Application Server by using the InfoSphere Information Serverinstallation program, remove WebSphere Application Server.Refer to the IBM WebSphere Application Server Network Deployment, Version7.0 information center for more information about completely removingWebSphere Application Server: http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.websphere.wps.doc/doc/tins_uninstman.html

5. If you used an existing installation of IBM WebSphere Application Server (thesuite installation program did not install the application server), remove theprofile that you created for the suite.a. Click Start → All Programs → IBM WebSphere → Application Server →

Profiles → profileName → Stop the server. profileName is the name of theprofile to be deleted.

b. Open a Windows command prompt.c. Change to the WASHome\bin directory. WASHome is the directory where the

application server is installed. The default directory isC:\IBM\WebSphere\AppServer.

d. Run the following command.manageprofiles.bat -delete -profileName profile

profile is the name of the profile to be deleted.e. Delete the directory for the profile. The directory is in the

WASHome\profiles\profileName directory.6. If you installed IBM DB2 database system as part of the InfoSphere

Information Server installation, do the following steps:a. Remove the DB2 database system by using the Add or Remove Programs

utility in the Windows Control Panel. If DB2 cannot be removed by usingthe Add or Remove Programs utility, remove the DB2 database system byrunning the command db2unins.bat /f in the bin directory of your DB2database system installation location.

b. Remove the DB2 database system administrator user from your operatingsystem user accounts. The default user name is db2admin.

c. Delete the following directories:v Delete the home directory for the DB2 database system administrator

account. The default directory is C:\Documents and Settings\db2adminor C:\Users\db2admin

v Delete the installation directory. The default directory is C:\IBM\SQLLIB\

v Delete the DB2 data directory. The default directory is C:\DB2\.v Delete the %ALLUSERSPROFILE%\Application Data\IBM\DB2 and

%ALLUSERSPROFILE%\Application Data\IBM\DB2History directories.





d. Remove the metadata repository database user and the analysis databaseuser. The default user names are xmeta and iauser.

e. Remove the GSK7 entries from the PATH environment variable.7. If you used an existing installation of DB2 database system, use the DB2

command prompt to drop the metadata repository database and the analysisdatabase. The default database names are xmeta and iadb.

8. If you used an Oracle database system or a Microsoft SQL Server databasesystem for the metadata repository database and the analysis database,manually drop the users, table spaces (Oracle database system) or databases(Microsoft SQL Server database system). The default table space or databasenames are xmeta and iadb.

9. The installation program uses a particular version of the MKS Toolkit on theclient and engine tiers. If you did not first install your own supported versionof MKS Toolkit, use Add or Remove Programs to remove the MKS Toolkit thatwas installed by the InfoSphere Information Server installation program.

10. On the computers where the client tier is installed, remove the followingdesktop shortcuts: Administrator Client.lnk, Designer Client.lnk, Consolefor IBM Information Server.lnk, and Web Console for IBM InformationServer.lnk

11. On the client machine, if the Multi-Client Manager was installed, type thefollowing command to remove the Multi-Client Manager service entry:"C:\IBM\InformationServer\MCM\ClientSwitcherService.exe" /uninstall

Note: If multiple client versions are installed on the computer, all clients areremoved. To use a previous client version, you must reinstall the client.

12. On each computer in your installation, remove the following files anddirectories:a. Delete the InfoSphere Information Server installation directory. The default

directory is C:\IBM\InformationServer\.b. If only the Version 8.5 clients are installed on this computer, back up your

registry and then delete the \HKEY_LOCAL_MACHINE\SOFTWARE\Ascential Software and \HKEY_LOCAL_MACHINE\SOFTWARE\IBM\InformationServer registry keys.

Note: If other client versions are installed on this computer, do not deletethe registry keys.

c. Delete the temporary log files for the installation program. Remove the%TEMP%\ibm_is_logs and %TEMP%\ISInstall* directory. To go to thatdirectory, enter cd %TEMP% at a command prompt or type %TEMP% in theaddress bar of Windows Explorer to go to that directory.

Note: If you redirected the installation program's temporary files to adifferent directory in “Preparing to run the installation program” on page177, the installation log files are in that location, instead of in the defaulttemporary directory that is specified here.

d. Delete the Windows Start menu shortcuts. The default directory isC:\Documents and Settings\All Users\Start Menu\Programs\IBMInfoSphere Information Server\. On Windows Server 2008 and Windows7, the default directory is C:\ProgramData\Microsoft\Windows\Start Menuor %ALLUSERSPROFILE%\Start Menu\Programs\IBM InfoSphere InformationServer\.

13. If you previously installed older versions of IBM InfoSphere DataStage orInfoSphere Information Server clients, Windows registry keys might remain on

Chapter 26. Manual software removal 385

the system after you uninstall the clients. If you uninstalled all InfoSphereDataStage or InfoSphere Information Server software, delete the followingregistry keys:HKLM\SOFTWARE\Ascential Software\ASBNodeHKLM\SOFTWARE\Ascential Software\DataStage ClientHKLM\SOFTWARE\Ascential Software\DataStage Multi-Client ManagerHKLM\SOFTWARE\Ascential Software\Documentation ToolHKLM\SOFTWARE\IBM\InformationServer

14. Remove any remaining InfoSphere Information Server users and groups if youare not using them for other purposes.

15. Restart your computer. Microsoft Windows might not be able to remove somefiles and services until the computer is restarted.Attention: Do not perform a new installation before restarting. If youreinstall before restarting, the new installation might fail.

Manually removing IBM InfoSphere Information Server (Linux, UNIX)If a previous installation or removal failed, you might have to manually removethe suite. You remove the software manually only after trying to use the softwareremoval program.

Before you begin

Before you manually remove software, on each computer in your installation, tryto remove the suite by using the software removal program. If the softwareremoval program fails to function, follow this procedure to remove the entireInfoSphere Information Server instance.


All scheduled tasks must be shut down, and IBM InfoSphere Information ServicesDirector applications must be disabled. See “Shutting down tasks and applicationsbefore removing software” on page 361.

About this task

You cannot manually remove only a single tier or product module. A manualremoval must remove the entire instance.

Procedure1. Back up the computers in your installation.2. On the computer where the engine tier is installed, log in as the root user and

do the following steps to stop and remove services:a. Change directories to the installation directory for the InfoSphere

Information Server engine. The default location is /opt/IBM/InformationServer/Server/DSEngine.

b. Source the dsenv file to set up the required environment variables. Enter thefollowing command:. ./dsenv

c. Run the following command to stop the engine services:


./bin/uv -admin -stop

d. Change to the InfoSphere Information Server installation directory (defaultis /opt/IBM/InformationServer).

e. Run the following command to stop the agents:./ASBNode/bin/NodeAgents.sh stop

f. Remove the startup entries. The NodeAgents.sh file is started automaticallyby symbolic links in the rc directory. (On AIX and Linux, the directory is/etc/rc.d). To determine which entries to remove, run the followingcommand:find /etc -name "*" -print | xargs grep -i installation_dir

where installation_dir is the InfoSphere Information Server installationdirectory. For example:find /etc -name "*" -print | xargs grep -i /opt/IBM/InformationServer

Remove all entries that contain DSEngine or ISFAgent.g. Edit the /etc/services file, and search for and remove the dsrpc entry,

which is similar to this entry:dsrpc 31538/tcp # RPCdaemon DSEngine@/opt/IBM/InformationServer/Server/

DSEngine

3. If you installed IBM DB2 database system as part of the InfoSphere InformationServer installation, remove DB2 database system from the computer on whichyou installed the metadata repository tier. Removing the DB2 database systemautomatically removes the metadata repository database and the analysisdatabase.a. On the computer where the metadata repository is installed, log in as the

DB2 instance owner. This account is db2inst1 by default.b. Drop the databases by running the following commands:

db2 drop database xmetadb2 drop database iadb

This example uses the default database names: xmeta and iadb. If you useddifferent names, use your database names instead of xmeta and iadb.

c. If you installed the DB2 database system as part of the installation ofInfoSphere Information Server and it is the only DB2 installation, removethe DB2 database system. For more information, see the following topicabout removing DB2 9.7: http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.qb.server.doc/doc/t0007439.html.

d. Use the following commands to remove the remaining files:rm -rf /tmp/db2*rm -rf /tmp/dascrt*rm -rf /var/db2rm –rf /var/opt/db2rm -rf ~dasusr1/dasrm -rf ~db2inst1/db2inst1rm -rf ~db2inst1/sqllibrm -rf /opt/IBM/db2

This example uses the default paths and user accounts. If you used differentpaths and user accounts, use your paths and user accounts instead of thoseshown here.


http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.qb.server.doc/doc/t0007439.html



e. Remove any entries in the /etc/services file that start with DB2_db2inst1or db2c_db2inst1 where db2inst1 is the name of the instance owner thatyou used during the suite installation.

f. If the /etc/inittab file exists and this is the only DB2 database systeminstallation, edit the file, and search for and remove the fmc entry, whichlooks similar to this entry:fmc:number:respawn:/opt/IBM/db2/V9/bin/db2fmcd #DB2 Fault Monitor Coordinator

4. If you used an existing installation of DB2 database system, use the DB2command prompt to drop the metadata repository database and the analysisdatabase. The default database names are xmeta and iadb.

5. If you used Oracle database system or Microsoft SQL Server database system tocreate the metadata repository database and the analysis database, manuallydrop the databases. The default database names are xmeta and iadb.

6. On the computer where the services tier is installed, log in as the root user anddo the following steps to stop and remove services:a. Change to the InfoSphere Information Server installation directory (default

is /opt/IBM/InformationServer).b. Stop IBM WebSphere Application Server. See the IBM InfoSphere Information

Server Administration Guide.c. Remove the startup entries. The MetadataServer.sh files are started

automatically by symbolic links in the rc directory. (On AIX and Linux, thedirectory is /etc/rc.d). To determine which entries to remove, run thefollowing command:find /etc -name "*" -print | xargs grep -i installation_dir

where installation_dir is the InfoSphere Information Server installationdirectory. For example:find /etc -name "*" -print | xargs grep -i /opt/IBM/InformationServer

Remove all entries that contain 99ISF.7. On the computer where the services tier is installed, if you installed IBM

WebSphere Application Server by using the InfoSphere Information Serverinstallation program, remove WebSphere Application Server. If the WebSphereApplication Server installation folder is empty, delete the folder.

Note: If you pre-installed WebSphere Application Server manually, instead ofreinstalling, delete the profile and then re-create it.Refer to the IBM WebSphere Application Server Network Deployment, Version7.0 information center for more information about completely removingWebSphere Application Server: http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/topic/com.ibm.websphere.wps.doc/doc/tins_uninstman.html

8. On each computer in your installation, complete the following steps to removeremaining files and directories:a. Delete the InfoSphere Information Server installation directory. The default

directory is /opt/IBM/InformationServer.b. Delete the temporary log files for the installation program by running the

following commands:rm -rf /tmp/ibm_is_logs

Note: If you redirected the installation program's temporary files to adifferent directory in “Preparing to run the installation program” on page177





177, the installation log files are in that location, instead of in the defaulttemporary directory that is specified here.

c. Delete the IBM InfoSphere DataStage installation location file by runningthe command:rm -rf /.dshome

d. Delete the InfoSphere DataStage log files by running the command:

AIX

rm -rf /ds_logs

UNIX

rm -rf /root/ds_logs

9. Remove any InfoSphere Information Server users and groups if you are notusing them for other purposes.

What to do next

To ensure that all processes have been terminated, restart each computer after youremove the suite.



Part 7. Troubleshooting installations

Resolve installation problems with this installation troubleshooting information.You can find more troubleshooting information in the information centers andcustomer support technotes for various product modules and components.



Chapter 27. Log files

To troubleshoot issues with IBM InfoSphere Information Server, you can consultlog files and temporary files.

Installation log filesLog files are created during the installation and uninstallation process. You can usethe log files to troubleshoot installation errors.

During the installation and uninstallation process, the log files are saved to thefollowing directory:

AIX Linux UNIX

/tmp/ibm_is_logs

Windows

%TEMP%\ibm_is_logs

Note: If you redirected the installation program's temporary files to a differentdirectory in “Preparing to run the installation program” on page 177, theinstallation log files are in that location, instead of in the default temporarydirectory that is specified here.

After a successful installation, a .zip file of the log files that are created during theinstallation process is saved to the IBM InfoSphere Information Server installationdirectory. This .zip file is named isdump-os-timestamp.zip. After a failedinstallation, the ISInstall-date-timestamp.log log file is retained in the temporarydirectory.

After a successful uninstallation, the ISInstall-date-timestamp.log log file isretained in the logs directory under the installation directory. After a faileduninstallation, the ISinstall-date-timestamp.log log file is retained in theibm-is-logs directory within the temporary directory.

Note: Do not delete the installation log files in the InfoSphere Information Serverinstallation directory after installation is completed. Save these files fortroubleshooting and verification purposes.

Temporary files generated by installation programTemporary files are created during the installation process. The temporary files arenot used after the installation is completed.

During the installation process, temporary files are saved to the followinginstallation directories:

Windows Location specified with the %TEMP% environment variable that is setfor the user that is logged on during installation:%TEMP%

AIX Linux UNIX


/tmp

Note: If you redirected the installation program's temporary files to a differentdirectory in Preparing to run the installation program, the temporary files are inthat location, instead of in the default temporary directory that is specified here.

The following example shows the temporary files that are generated duringinstallation on a Linux computer:/tmp (Thu Aug 20 09:18:15)<1:649> % ls -ltotal 1576-rw-r--r-- 1 nfsnobody nfsnobody 742 Aug 20 00:19 1.txtdrwxr-xr-x 2 nfsnobody nfsnobody 4096 Aug 20 01:12 ibm_is_logs/-rw-r--r-- 1 nfsnobody nfsnobody 16975 Aug 20 01:08 script34973.log-rw-r--r-- 1 nfsnobody nfsnobody 678 Aug 20 01:08 script34973.sh

script34973.shA script that is generated during installation on engine tier computers thatspecify globalization (NLS) support. This script defines environmentvariables and then runs the globalization (NLS) configuration for theInfoSphere Information Server server. The file name is variable and isbased on the process ID number. In this script34973.sh example, 34973 isthe process ID number.

script34973.logThe output log that is generated when the script34973.sh is run by theinstallation program. The contents of this file are copied to the installationlog file. The file name is variable and is based on the process ID number.In this script34973.log example, 34973 is the process ID number.

Note: The temporary files that are created during installation are not used afterinstallation is completed. You can delete the installation temporary files afterinstallation is completed.

IBM WebSphere Application Server system log filesThe WebSphere Application Server log files contain information that you can use tomonitor WebSphere Application Server startup and diagnose errors.

The following log files are useful for diagnosing problems with IBM InfoSphereInformation Server:

SystemOut.logWebSphere Application Server messages to STDOUT are redirected to thisfile.

SystemErr.logWebSphere Application Server messages to STDERR are redirected to thisfile.

These files are located in the following directories on each node in your WebSphereApplication Server installation:

v Linux UNIX

path/profiles/profile/logs/server1

v Windows

path\profiles\profile\logs\server1

In the directory path:


v path is the WebSphere Application Server installation path. By default, path isone of the following paths:

– Linux UNIX

opt/IBM/WebSphere/AppServer

– Windows

C:\IBM\WebSphere\AppServer

v profile is the profile name where IBM InfoSphere Information Server is installed.For a stand-alone installation, the default value is InfoSphere. For a clusteredinstallation, the default value for a custom profile is Customxx, where xx is thenumber of the profile.

v server1 is the name of the application server. For a stand-alone installation, thedefault value is server1. For cluster installations, there might be multipleapplication server directories under the custom profile. The typical value isserverx, where x is the number of the application server instance. For aDeployment Manager profile, the default value is dmgr. For a node agent underthe custom profile, the default value is nodeagent.

For more information about WebSphere Application Server log files, see theWebSphere Application Server documentation:v IBM WebSphere Application Server Network Deployment 6.1:

publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.nd.doc/info/ae/ae/ttrb_mglogs.html

v IBM WebSphere Application Server Network Deployment 7.0:publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/ttrb_mglogs.html

Chapter 27. Log files 395

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.nd.doc/info/ae/ae/ttrb_mglogs.html





Chapter 28. General installation problems

These problems and resolutions are related to general issues that might occuracross the product suite.

"User credentials are not valid" error appears unexpectedly duringinstallation

If you receive a "user credentials are not valid" error when you create a newoperating system user account from the installation program, specify the correctpassword or remove the user account.

Symptoms

When you specify a new operating system user account from the IBM InfoSphereInformation Server installation program, you receive a "user credentials are notvalid" error and you cannot continue the installation. See “Setting up administratorand owner accounts” on page 142 for more information about operating systemuser accounts.

Causes

When you specify a new operating system user account from the installationprogram, the program checks whether the user account already exists. If theaccount exists, the program checks whether the password is correct. If the accountdoes not exist, the program immediately creates the user account on the computer.If you exit the program before you complete the installation, the user accountremains on the computer. If you subsequently restart the installation and specifythe same user name but a different password, you receive a "user credentials arenot valid" error.

Environment

All supported operating systems.

Resolving the problem

Use operating system utilities to determine whether the user account exists on thecomputer. If necessary, change the password. Then continue the installation.

IWAV0003E warning in installation log fileIWAV0003E warnings in the installation log file can be ignored.

Symptoms

A warning similar to the following text is written to the installation log file duringthe IBM WebSphere Application Server enterprise archive (EAR) deploymentphase:


[exec] +++ Warning +++: Mon Sep 18 19:36:18 BST 2010 IWAV0003ECould not reflect methods for com.ascential.xmeta.shared.ILocalTransactionalBusiness because one of the methods referencesa type that could not be loaded. Exception: java.lang.NoClassDefFoundError: com.ascential.xmeta.exception.ServiceException

Environment

All environments.


This error can be ignored. The EAR installs correctly.

This warning is issued because the classes inside the EAR are not on the classpathfor the EAR installation process. After the EAR is installed, the classes are resolvedcorrectly.

Warnings occur during installation of DB2While installing IBM InfoSphere Information Server, you might see a messageindicating that warnings occurred during the installation of IBM DB2 Database forLinux, UNIX, and Windows, or "Open File - Security Warning" messages might bedisplayed.

Symptoms

During the DB2 installation, warnings or other messages are displayed.


If the warnings are "Open File - Security Warning" messages, ignore the messages.Otherwise, do these steps:1. Look in the installation log file for a message that is similar to the following

line:WARNING: com.ascential.acs.installer.asb.InstallDB2ActionWRepositoryInstaller65507: Warnings occurred installing DB2.For details see the log file:C:\IBM\InformationServer\logs\db2_install.log

2. View the log file that is specified in the warning message. You can ignorewarnings such as SQL1362W or SQL20189W, which warn that the updates donot take effect until the next database startup. These warnings are notimportant because the installation program stops and restarts DB2 during theinstallation process.

For more information about specific warning messages in the DB2 log file, refer tothe DB2 documentation:v DB2 9.5: publib.boulder.ibm.com/infocenter/db2luw/v9r5/v DB2 9.7: publib.boulder.ibm.com/infocenter/db2luw/v9r7/


http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/

Installation problems with VMware ESXIf you experience problems when installing IBM InfoSphere Information Server ona VMware ESX virtual computer, make sure that your system is not overloaded.

Symptoms

When you attempt the installation, one or more of the following problems occurs:v The system performs slowly, and the installation takes a much longer time than

expected.v IBM DB2 installation fails because not all ports are available.v IBM WebSphere Application Server installation fails because not all ports are

available.

Causes

The target system is overloaded.

Environment

Microsoft Windows, Linux (SUSE, Red Hat)


Reduce the load on the system, and try the installation again.

User creation errors appear in log files (Linux, UNIX)If several errors about user creation are included in the log files, check that theusers exist before you run the installation.

Symptoms

Errors that are similar to the following lines are in the log files:WARNING: com.ibm.is.install.core.CommonProcess Exit Code: 1, Error /bin/chown:cannot access `/home/xmeta’: No such file or directory typeSEVERE: com.ibm.is.install.core.util.User CDIIN3185E: Changing ownership failedWARNING: com.ibm.is.install.core.CommonProcess Exit Code: 9, Error groupadd:Group `iauser’ already exists.SEVERE: com.ibm.is.install.core.util.User CDIIN3183E: groupadd command failedwith return code: 9

Causes

The users do not yet exist. On a system that runs the Lightweight Directory AccessProtocol (LDAP) or the Network Information Service (NIS), you must create allusers in the user registry before you run the IBM InfoSphere Information Serverinstallation program. The installation program attempts to create the metadatarepository database owner and IBM InfoSphere Information Analyzer user if theaccounts do not exist. The installation program cannot create users on an LDAP orNIS-enabled system.

Any user that you create before you run the installation program must have avalid home directory defined.


Chapter 28. General installation problems 399

Create all users and then run the installation program again. See “Setting upadministrator and owner accounts” on page 142.

"The publisher could not be verified" messageYou can ignore messages such as "The publisher could not be verified. Are yousure you want to run this software?" during IBM InfoSphere Information Serverinstallation.

Symptoms

A window is displayed in the browser window. The message in the window reads"The publisher could not be verified. Are you sure you want to run this software?"

Causes

The installation program and related utilities are not signed.

Environment

Microsoft Windows 7 and Microsoft Windows Vista


Ignore the message and continue the installation. This message does not indicate asecurity risk when it is displayed during InfoSphere Information Serverinstallation.

"There is no script engine for file extension '.js'" message appearsduring installation

During a Microsoft Windows installation, if you receive a message that reads"There is no script engine for file extension '.js'", repair or reinstall the WindowsScript Engine.

Symptoms

During installation, you receive a message that reads "There is no script engine forfile extension '.js'."

Causes

The Microsoft Windows Script Engine is not installed or is not operational.

Environment

Microsoft Windows

Diagnosing the problem

Open a command prompt window and enter the following command:cscript myfile1.js

where myfile1 is the name of a new file.


If you receive the following message, there is a problem with the Windows ScriptEngine installation:Input Error: There is no script engine for file extension ".js".


Repair or reinstall the Windows Script Engine. Refer to Microsoft documentationfor more information. There are known problems with the Windows Script Enginethat cause this error.

Installation process hangs when a web browser session is closedIf an exception occurs after a web browser or browser tab has been closed, or if thebrowser session has timed out, the installation process will be stuck waiting foruser response.

Symptoms

The installation process is stuck waiting for a response.

Causes

When the web browser window or tab that is running an installation process isclosed during the installation session, if the installation runs into exception, theinstallation process gets stuck waiting for a user response.

Note: To avoid this problem, keep the browser or browser tab availablethroughout the installation session.

Environment

Graphical mode installation

Resolving the problem1. Uninstall your current IBM InfoSphere Information Server installation by

running the following commands:cd /opt/IBM/InformationServer/_uninstall./uninstall -verbose

2. Do the manual cleanup tasks as described in “Completing software removal(Linux, UNIX)” on page 380 or “Completing software removal (Windows)” onpage 378.

3. Start a new InfoSphere Information Server installation by running the followingcommands:cd <image>/is-suite./setup -rsp response.txt -force –verbose

Chapter 28. General installation problems 401


Chapter 29. Authentication problems

These problems and resolutions are related to authentication.

Directory and user permissionsIf installation fails, confirm that the users who install IBM InfoSphere InformationServer have read and write permissions for the InfoSphere Information Serverinstallation directories.

The following table shows the default InfoSphere Information Server installationdirectories that require read and write permissions by the specified users.

Table 109. Required directory permissions

Installationcomponents Directories Permissions Users

InfoSphereInformationServer

Installation parentdirectories:

Linux UNIX

v /opt

v /opt/IBM

Windows

v C:\

v C:\IBM

v %WinDir%: the Windowsdirectory. TypicallyC:\WINDOWS

Read or readand write

Linux UNIX

v Root user

Windows

v Local administrator ordomain administratorwith local administratorprivileges


Installation directory:

Linux UNIX


Windows

v C:\IBM\InformationServer

Read andwrite

Linux UNIX

v Root user

Windows


Engine tierand IBMInfoSphereDataStage

Installation parentdirectories:

Linux UNIX

v /opt

v /opt/IBM

Windows

v C:\

v C:\IBM



InfoSphere DataStageadministrator (default username is dsadm)


Table 109. Required directory permissions (continued)


Engine tierandInfoSphereDataStage


Linux UNIX


Windows

v C:\IBM\InformationServer

Read andwrite

InfoSphere DataStageadministrator (default username is dsadm)


Temporary directory:

Linux UNIX

v /tmp

Windows

v This directory is typicallythe “x:\Documents andSettings\user_name\LocalSettings\temp” directory,where user_name is theMicrosoft Windows loginname for the user whoinstalls the product. OnWindows Server 2008 andWindows 7, this directoryis typically the“x:\Users\user_name\AppData\Local\Temp”directory.

Read andwrite

Linux UNIX

v Root user

v Database instance owner(default user name isdb2inst1)

Windows


v Database owner (defaultuser name is db2admin)


Table 109. Required directory permissions (continued)


Metadatarepository

Database server directories:

If you are using IBM DB2:

Linux UNIX

v /opt

v /opt/IBM

v /opt/IBM/db2/V9.5/ (DB2Version 9.5)

v /opt/IBM/db2/V9.7/ (DB2Version 9.7)

Windows

v C:\

v C:\IBM

v C:\IBM\SQLLIB


If you are using anotherdatabase system, refer to thedocumentation for thedatabase system fordirectory permissionsinformation.


Linux UNIX


Windows


Metadatarepository

Database storage directories:

Linux UNIX

v /opt/IBM/InformationServer/Repository

Windows

v C:\DB2

Read andwrite

Linux UNIX


Windows


IBMWebSphereApplicationServer


Linux UNIX

v /opt/IBM/WebSphere/AppServer

Windows

v C:\IBM\WebSphere\AppServer

AIX

v /usr/IBM/WebSphere/AppServer

Read andwrite

Linux UNIX

v Root user

Windows


Chapter 29. Authentication problems 405

User privilegesIf installation fails, confirm that the users who install IBM InfoSphere InformationServer have the necessary privileges.

To install InfoSphere Information Server:

v Windows You must log in to the target computer as a local administrator or as alocal or domain user who is directly assigned to the local Administrators group.

v Linux UNIX You must log in as the root user.


Chapter 30. Application server problems

These problems and resolutions are related to the services tier and the applicationserver.

Resolving IBM WebSphere Application Server installation problemsUse this troubleshooting information when you install IBM WebSphere ApplicationServer with IBM InfoSphere Information Server.

Symptoms

When you install WebSphere Application Server with IBM InfoSphere InformationServer, the WebSphere Application Server installation fails.

Environment

All supported environments.


If the WebSphere Application Server installation fails, review the following logfiles:v WebSphere Application Server log files. For more information, refer to the

following topics in the WebSphere Application Server documentation:– WebSphere Application Server Network Deployment 6.1: WebSphere

Application Server Network Deployment 6.1: Troubleshooting installation– WebSphere Application Server Network Deployment 7.0: WebSphere

Application Server Network Deployment 7.0: Troubleshooting installationv InfoSphere Information Server installation log file:

– Linux UNIX /opt/IBM/InformationServer/logs/WebSphereInstall.log

– Windows C:\IBM\InformationServer\logs\WebSphereInstall.log

Search for following error:INSTCONFFAILED: Cannot create profile:The profile does not exist


Any of the following issues can cause problems with the WebSphere ApplicationServer installation process:

Windows The DEBUG variable is set in your environment variables.Verify that the DEBUG variable is not set in your environment variables. Ifthe DEBUG variable is set:1. Remove the DEBUG variable from your environment variables.2. Restart the computer.3. Reinstall InfoSphere Information Server.4. After the installation is complete, reset the DEBUG variable.


http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.nd.doc/info/ae/ae/tins_trouble.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.installation.nd.doc/info/ae/ae/tins_trouble.html

Windows The installation user cannot write to the Microsoft Windows directory.The installation user must have write permissions to the Windowsdirectory. This directory is the directory specified by the %WinDir%environment variable. By default, the directory is C:\WINDOWS.

In Microsoft Windows 2008, this problem might occur if you run as thetrue administrator or if User Account Control (UAC) is enabled.

AIX The /etc/filesystems file contains a duplicate entry.If the /etc/filesystems file contains a duplicate entry, the WebSphereApplication Server installation reports 0 MB of available disk space. Editthe /etc/filesystems file, and comment out the duplicate entry.

Installation fails when the IBM WebSphere Application Server port ischanged after installation

After you install IBM InfoSphere Information Server, if you change the WebSphereApplication Server HTTP port (WC_defaulthost) by using the IBM WebSphereApplication Server administrative console, future installations, product additions,and updates fail.

Symptoms

A "Connection refused" error message is displayed on the user interface or in thelog file.

Causes

The original installation settings are stored in several configuration files are usedfor subsequent installation activities. If the WebSphere Application Server portnumber changes after installation, the installation settings in these files areincorrect.


Follow the procedure in “Changing the WebSphere Application Server HTTP port”on page 289 to change the HTTP port in the WebSphere Application Serveradministrative console and in the configuration files.

Resolving connection problemsAn installation might fail because the Domain Name System (DNS) server isunable to resolve system names or because the application server is not running.

Symptoms

IBM InfoSphere Information Server installation fails when the Domain NameSystem (DNS) is unable to resolve system names. The installation program returnsan error message that is similar to the following message:CDIIN2107E: Unable to validate the IBM InfoSphere Information Server user name nameand password for host hostname at port port_number. Thereturned message is:java.net.UnknownHostException: hostname.

Confirm that 1) WebSphere Application Server is running; 2) you entered the correctuser name and password; 3) the port number is correct.


Causes

The communication between the installation computer and the application serveron the services tier is not established. The following issues might cause thisproblem:v The connection to the application server uses the short host name.v The connection to the application server uses a host name that does not match

the name that the computer had when the application server was installed.v The short host name does not map to the same IP address as the long host

name.v The application server is not running.


When the services tier is installed on hostname.domain, use the following pingcommands to test the connection to the short host name and to the long hostname:ping hostnameping hostname.domain

Resolving the problem1. Ensure that the application server is running.2. Ensure that the etc/hosts file is correctly configured with the short host name

and long host name of the services tier computer.3. Ensure that all necessary ports are open among the client tier, engine tier, and

services tier computers.4. Ensure that the host name that is used to access the services tier computer is

the same name that the computer had when the application server wasinstalled.

5. Ensure that "localhost" and the computer host name are not both mapped to IPaddress 127.0.0.1. Map only "localhost" to IP address 127.0.0.1. The followingexample shows an etc/hosts file where these entries are specified correctly:127.0.0.1 localhost.localdomain localhostxx.xx.xx.xx machinelonghostnamemachineshorthostname

xx.xx.xx.xx is the unique IP address of the computer.6. If the engine tier or services tier was installed on a computer that has

incorrectly configured host names, reinstall IBM InfoSphere Information Server.

Unable to start IBM WebSphere Application Server after the user namechanges or expires

If the user name or password that you created for WebSphere Application Serveror for the metadata repository changes or expires, the application server does notstart.

Symptom

The application server does not start.

Chapter 30. Application server problems 409

Cause

The WebSphere Application Server user name or password changed or expired, orthe metadata repository user name or password changed or expired. Starting andstopping WebSphere Application Server requires user authentication. These startand stop commands fail when user authentication is unsuccessful because the usernames or passwords changed or expired.


The IBM InfoSphere Information Server installation directory is shown asinstall_home in the following commands.

Note: The AppServerAdmin commands do not validate user names or passwords.

Linux UNIX

For a Linux or UNIX installation, follow these steps to resolve the problem:1. Log in to the services tier computer as root.2. To change the password for the WebSphere Application Server

administrator user, enter the following command:install_home/ASBServer/bin/AppServerAdmin.sh -was -user user_name

-password new_password

3. To change the password for the metadata repository user, do thefollowing steps:a. Confirm that you can use the new password to connect to the

database.b. Enter the following command to register the new password

information:install_home/ASBServer/bin/AppServerAdmin.sh -db -user user_name


c. Restart all WebSphere Application Server processes. See the IBMInfoSphere Information Server Administration Guide.

Windows

For a Microsoft Windows installation, follow these steps to resolve theproblem:1. Log in to the services tier computer as a user with administrator

privileges.2. To change the password for the WebSphere Application Server

administrator user, enter the following command:install_home\ASBServer\bin\AppServerAdmin.bat -was -user user_name


3. To change the password for the metadata repository user, do thefollowing steps:a. Confirm that you can use the new password to connect to the

database.b. Enter the following command to register the new password

information:install_home\ASBServer\bin\AppServerAdmin.bat -db -user user_name


c. Restart all WebSphere Application Server processes. See the IBMInfoSphere Information Server Administration Guide.


For details on adding a new WebSphere Application Server user when using theinternal registry, see “Adding an IBM WebSphere Application Server administratoruser to an internal user registry.”

Adding an IBM WebSphere Application Server administrator user to aninternal user registry

If you do not know the WebSphere Application Server administrator user andpassword, you can create a user in the internal user registry.

Symptom

You are using the internal user registry and you do not know the WebSphereApplication Server administrator user and password.

Cause

The password changed, or the user was deleted.


The IBM InfoSphere Information Server installation directory is shown asinstall_home in the following commands.

Linux UNIX

For a Linux or UNIX installation, follow these steps to resolve the problem:1. Log in to the services tier computer as root.2. Enter the following command to add a user with administrator

privileges to the InfoSphere Information Server internal user registry:install_home/ASBServer/bin/DirectoryAdmin.sh -user -admin

-userid new_user_name -password new_password

3. Enter the following AppServerAdmin command to update the username or password within the WebSphere Application Serverconfiguration:/opt/IBM/InformationServer/ASBServer/bin/AppServerAdmin.sh-was -user name -password password

Windows

For a Microsoft Windows installation, follow these steps to resolve theproblem:1. Log in to the services tier computer as a user with administrator

privileges.2. Enter the following command to add a user with administration

privileges to the InfoSphere Information Server internal user registry:install_home\ASBServer\bin\DirectoryAdmin.bat -user -admin

-userid new_user_name -password new_password

3. Enter the following AppServerAdmin command to update the username or password within the WebSphere Application Serverconfiguration:C:\IBM\InformationServer\ASBServer\bin\AppServerAdmin.bat-was -user name -password password


Repairing the WebSphere Application Server registry after switching toLDAP

If you have switched from an internal registry to a Lightweight Directory AccessProtocol (LDAP) user registry without using the documented procedure,"Switching to an LDAP user registry," you might be unable to stop IBM WebSphereApplication Server processes.

Symptoms

You can not stop WebSphere Application Server when using either theMetadataServer.sh stop command or the stopServer.sh command.

Environment

Optional. Describe any environmental details that are not already in the title orshort description.


Repair the WebSphere Application Server registry:1. Kill the WebSphere Application Server processes.2. Use sudo vi to edit the following settings in the file, /opt/IBM/WebSphere/

AppServer/profiles/InfoSphere/config/cells/hostNameNode01Cell/security.xml:a. Change the first instance of enabled="true" to "false"b. Change the first instance of appEnabled="true" to "false"

3. Start WebSphere Application Server.4. Log into the WebSphere Application Server administrative console by using

wasadmin.

Note: Because of your modifications to security.xml in step 2, the consoledoes not prompt you for a password.

5. In Security → Global Security, click Configure and enter the followinginformation:a. Set Primary administrator user name to wasadmin.b. Select Server identity that is stored in the repository and set the user ID

to wasadmin and type the password.6. Click Apply and then OK. This returns you to the Global Security page.7. Select the check boxes: Enable administrative security and Enable

application security

8. Clear the Java 2 security check box.9. Click Apply. A message appears on the top of the form. Click the Save link

inside the message.10. Log out of the WebSphere Application Server administrative console.11. Test that you can now stop WebSphere Application Server smoothly:

a. Stop WebSphere Application Server.

Note: WebSphere Application Server should be able to stop without errors,but you must still do the following steps to ensure the that the problem isfixed.


b. Start WebSphere Application Server.c. Stop WebSphere Application Server. It should be able to stop without

errors.

Services tier performanceIf the services tier is slow, ensure that you have not turned on IBM WebSphereApplication Server tracing.

Symptoms

The services tier is running slowly. The default setting for IBM WebSphereApplication Server tracing is off.


To avoid the problem, ensure that any changes made to IBM WebSphereApplication Server are restored to the default settings before installing and usingIBM InfoSphere Information Server.

To resolve the problem, ensure that you have not turned on the IBM WebSphereApplication Server tracing.



Chapter 31. IBM InfoSphere Information Server reportingproblems

These problems and resolutions are related to reporting.

Cannot view report result from InfoSphere Information Server consoleor InfoSphere Information Server Web console

In a cluster environment, if a "Page Not Found" error message is displayed whileyou are trying to view a report result, a security process might be running. Youcan edit the httpd.conf configuration file to allow encoded slash characters, andthen restart the Web server.

Symptoms

After you run a process in a cluster environment, a "Page Not Found" errormessage is displayed, and you cannot view the report results.

Causes

As a security measure, the Web server encodes some URLs. Each slash in a URL isencoded as special character that the httpd.conf configuration file reads and thenrejects by default.

Environment

This advice applies to cluster environments that run on IBM HTTP Server orApache Web Server.

Resolving the problem1. Open the httpd.conf configuration file. The file is in the configuration

directory: install-home\IBM\HTTPServer\conf\httpd.conf.2. Set the AllowEncodedSlashes value to ON.3. Save this file, and restart the Web server. If the Web server is installed as a

managed server, use theIBM WebSphere Application Server administrativeconsole to restart it. Otherwise, log into the computer where the Web server isinstalled, and restart the Web server.

Enabling and disabling trace logging of the reporting engineWhen you encounter a problem or an error that requires attention by IBM SoftwareSupport, you can set up trace logging to report detailed internal processes. You canenable trace logging in the reporting engine to generate logs that help IBMSoftware Support diagnose errors.

Symptoms

Not applicable.

Resolving the problem1. Open a command prompt or a terminal window on the computer.


2. Enter the following command to enable logging in the reporting engine:Windows

installdir\ASBServer\bin\ReportingAdmin.bat -user username -password password-el

Linux UNIX

installdir/ASBServer/bin/ReportingAdmin.sh -user username -password password-el

3. Rerun the process that resulted in the error that you received earlier.4. After the error occurs, create a .zip file that contains the log files. The log files

are located in the following directories:v If IBM WebSphere Application Server clustering is enabled, the log files are

created in the reporting workspace on each server in the cluster. On eachserver, the reporting workspace is located in the temp folder that is definedby the operating system. The path has the following format:\tempfolder\informationServer\servername\engine\JREPORTFor example: C:\WINDOWS\Temp\informationServer\myservernode1\engine\JREPORT

v If clustering is not enabled, the log files are located in the followingdirectory:

Windows

installdir\bin\InformationServer\ASBServer\apps\Reporting\engine\JReport\logs

Linux UNIX

installdir/bin/InformationServer/ASBServer/apps/Reporting/engine/JReport/logs

5. Send this .zip file to IBM Software Support.6. When you finish collecting detailed logs, roll back the trace level settings to the

original state. At the command prompt, enter the following command todisable logging: Windows

installdir\ASBServer\bin\ReportingAdmin.bat -user username -password password-dl

Linux UNIX

installdir/ASBServer/bin/ReportingAdmin.sh -user username -password password -dl


Chapter 32. Client and console problems

These problems and resolutions are related to client errors and login problems.

Java Virtual Machine fails to loadDuring startup, client applications might fail to load the Java Virtual Machine(JVM) if the operating system is unable to allocate a sufficient amount of heapmemory.

Symptoms

The client application fails with an error message that is similar to the followingmessage:Internal error - Failed to load the Java Virtual Machine

Causes

The JVM is unable to allocate the memory that it has been configured to use. Thiserror typically occurs when too many client processes are running concurrently.


Decrease the value that is specified for MaximumHeapSize in theapplication-specific sections of the following file: \ASBNode\conf\proxy.xml. Thisfile is located in the IBM InfoSphere Information Server installation directory.

Continue to decrease this value until clients start normally. If multiple clientapplications are running, you might need to decrease this value for all clients.Comments in the proxy.xml file identify the configuration section for each clientapplication. Common values for MaximumHeapSize include 64, 128, 256, 348, 512,and so on.

After making changes, you must restart the clients to reallocate the memory.

Rich client login failureIf the rich client login fails because the services tier cannot be reached, you cantroubleshoot several possible causes.

Symptoms

The client login failure can be identified with the following information:v The stack trace from the client does not include the message Trace from server.v The stack trace shows that the root cause of the exception is a socket connection

error.v The host name and port number are included in the error message.v A RegistrationHelper exception is included in the error message.

Stack traces and error messages vary depending on the situation. A connectionfailure might be identified with an error message about network connection, such


as "Could not connect to server" or "port out of range." A connection failure mightalso be revealed in a stack trace that is similar to the following example:Exception type: javax/security/auth/login/LoginExceptionException message: Could not connect to server [green3] on port [9081].Exception stack trace:javax.security.auth.login.LoginException:Could not connect to server [green3] on port [9081].at com.ascential.acs.security.auth.client.AuthenticationService.getLoginException(AuthenticationService.java:978)at com.ascential.acs.security.auth.client.AuthenticationService.doLogin(AuthenticationService.java:355)

Caused by: com.ascential.acs.registration.client.RegistrationContextManagerException:Caught an unexpected exception.at com.ascential.acs.registration.client.RegistrationContextManager.setContext(RegistrationContextManager.java:76)at com.ascential.acs.security.auth.client.AuthenticationService.doLogin(AuthenticationService.java:349)

Caused by: com.ascential.acs.registration.client.RegistrationHelperException:Caught an unexpected exception.at com.ascential.acs.registration.client.RegistrationHelper.getBindingProperties(RegistrationHelper.java:694)at com.ascential.acs.registration.client.RegistrationHelper.getBindingProperties(RegistrationHelper.java:587)at com.ascential.acs.registration.client.RegistrationHelper.getBindingConfigProperties(RegistrationHelper.java:566)at com.ascential.acs.registration.client.RegistrationContextManager.setContext(RegistrationContextManager.java:173)at com.ascential.acs.registration.client.RegistrationContextManager.setContext(RegistrationContextManager.java:73)... 1 moreCaused by: java.net.ConnectException: Connection refused: connectat java.net.PlainSocketImpl.socketConnect(Native Method)at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:352)at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:214)at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:201)at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:368)at java.net.Socket.connect(Socket.java:526)at java.net.Socket.connect(Socket.java:476)at sun.net.NetworkClient.doConnect(NetworkClient.java:175)at sun.net.www.http.HttpClient.openServer(HttpClient.java:407)at sun.net.www.http.HttpClient.openServer(HttpClient.java:542)at sun.net.www.http.HttpClient.<init>(HttpClient.java:246)at sun.net.www.http.HttpClient.New(HttpClient.java:319)at sun.net.www.http.HttpClient.New(HttpClient.java:336)at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:858)at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:799)at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:724)at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1047)at com.ascential.acs.registration.client.RegistrationHelper.getBindingProperties(RegistrationHelper.java:677)... 5 more


To resolve the problem, apply one of the following solutions, depending on thecause of the failure:

Cause Solution

The client computer host file has an invalidhost name or IP address entry.

Update the client computer hosts file so thatthe server host name can be resolved fromclient.


Cause Solution

The server listening port might be blockedby a firewall.

Ensure that the application server TCP/IPports are not blocked by the firewall.

The application server is not running. Ensure that the application server isrunning.

In a cluster environment, you did notspecify the host name and port of thefront-end HTTP dispatcher.

If IBM WebSphere Application Serverclustering is implemented within yourinstallation, direct the client to the hostname and port of the front-end HTTPdispatcher. (The default port is 80.) Theclient login will fail if you specify theDeployment Manager host name and port orif you specify the host name and port of asingle cluster member.

You changed a WebSphere ApplicationServer port or modified the host file on thesystem, but you did not restart WebSphereprocesses after making the change.

In a stand-alone (non-cluster) environment,restart IBM WebSphere Application Server.

In a cluster environment, restart the cluster.

Resolving problems logging in to the IBM WebSphere ApplicationServer administrative console

Use this troubleshooting information when you are running WebSphereApplication Server with IBM InfoSphere Information Server and you cannot log into the WebSphere Application Server administrative console.

Symptoms

You cannot log in to the WebSphere Application Server administrative console ofan WebSphere Application Server installation that is running InfoSphereInformation Server.

Causes

There are multiple reasons why the login fails.

Environment

This advice applies to all environments that are supported by InfoSphereInformation Server.


Ensure that you are using the default IBM WebSphere Application Serveradministrator user name and password. If you are not sure of the WebSphereApplication Server administrator user name, you can view the WebSphereApplication Server security.xml file.

Attention: Do not modify this file.

The security.xml file is in the following directory:

v Windows

\IBM\WebSphere\AppServer\profiles\profile_name\config\cells\cell\security.xml

Chapter 32. Client and console problems 419

v Linux UNIX

/opt/IBM/WebSphere/AppServer/profiles/profile_name/config/cells/cell/security.xml

profile_name is the name of the WebSphere Application Server profile being used(the default name is InfoSphere). cell is the name of the WebSphere ApplicationServer cell.

The user name is specified by the serverId attribute in the userRegistries elementof the active user registry. Ensure that you are looking at the serverId of the activeuser registry. To find the active user registry in the security.xml file, look for theactiveUserRegistry string in the file. The file contains an entry that is similar toactiveUserRegistry=UserRegistry, where the UserRegistry value depends on yourconfiguration. Search the remainder of the security.xml file for this value, whichdetermines the current active user registry. Ensure that you can access the registry.For example, if you are using an LDAP user registry, ensure that the LDAP serveris running and that you can connect to it. If you are using the InfoSphereInformation Server internal registry, ensure that the database server that is used byInfoSphere Information Server is running and that you can access it.


If the user name or password is invalid or unknown:1. Change the password.v If your installation is configured to use the InfoSphere Information Server

internal user registry, enter the following DirectoryAdmin command tochange the password:

Windows

install_home\ASBServer\bin\DirectoryAdmin -user -userid wasadmin_username-password wasadmin_password

Linux UNIX

install_home/ASBServer/bin/DirectoryAdmin.sh -user -userid wasadmin_username-password wasadmin_password

v If your installation is configured to use an external user registry (such as alocal operating system user registry or an LDAP user registry), use operatingsystem or LDAP utilities to change the password.

2. Enter the following the AppServerAdmin command to update the WebSphereApplication Server and InfoSphere Information Server configurations:

Windows

install_home\ASBServer\bin\AppServerAdmin -was -user username-password password

Linux UNIX

install_home/ASBServer/bin/AppServerAdmin.sh -was -user username-password password

Connection problems after IBM WebSphere Application Server clustermembers are removed

You might experience connection problems with the WebSphere Application Serveradministrative console or IBM InfoSphere DataStage clients if you remove allmembers of a WebSphere Application Server cluster.

Symptoms


You cannot access the WebSphere Application Server administrative console, or login to InfoSphere DataStage clients. You recently removed all members of theWebSphere Application Server cluster and then added members again.

Causes

When all cluster members are removed from the cluster, the cluster template isremoved. New cluster members are set up with the default cluster template. Thedefault template is not compatible with IBM InfoSphere Information Server.

Environment

All environments.

Resolving the problem1. Rebuild the cluster as described in "Adding a new cluster member" in the IBM

InfoSphere Information Server Administration Guide. Do not start the cluster yet.2. On the computer that hosts the Deployment Manager, run the following

command:

v UNIX Linux installdir/ASBServer/bin/reconfigure_was_cluster.sh-user wasadmin_user -password wasadmin_password

v Windows installdir\ASBServer\bin\reconfigure_was_cluster.bat -userwasadmin_user -password wasadmin_password

wasadmin_user and wasadmin_password are the user name and password of theWebSphere Application Server administrator.

3. Start the cluster as described in "Restarting application server processes" in theIBM InfoSphere Information Server Administration Guide.

Chapter 32. Client and console problems 421


Chapter 33. Removal problems

These problems and resolutions are related to removing IBM InfoSphereInformation Server products.

IBM InfoSphere Information Server installation fails repeatedlyIf an installation fails repeatedly on a computer that has been used for a previousIBM InfoSphere Information Server installation, verify that the previous installationwas completely removed.

Symptoms

Installation fails on a computer that has been used for a previous IBM InfoSphereInformation Server installation.

Causes

Previous installations are not completely removed, or the computer was notrestarted after the software removal process completed.

Environment

This advice applies to all operating systems.


Before you install InfoSphere Information Server, you must completely removeprevious installations, including failed installations, of InfoSphere InformationServer. You must remove previous versions of InfoSphere Information Server fromthe installation location where you intend to install the new instance.

You must also remove DB2 and WebSphere from the target installation locationsbefore the InfoSphere Information Server installation program can reinstall DB2and WebSphere.

To ensure that the previous installation is completely removed, follow the manualsoftware removal steps for the previous installation.

Note: Windows On Microsoft Windows, you can have more than one version ofInfoSphere Information Server only if the previously installed versions wereclient-only installations. You must completely remove any non-client InfoSphereInformation Server installations before you install InfoSphere Information Server.

Ignoring runtime error during uninstallationA known problem causes an unimportant error message to be displayed during theuninstallation process.

Symptoms


During the uninstallation process, the following error message is displayed whenthe ASBAgent is being removed:This application has requested the Runtime to terminate it in an unusual way

Causes

This is a known problem with the Visual C++ Runtime .dll file (msvcrt.dll), whichis documented in the Microsoft Knowledge Base.

Environment

This advice applies to the Microsoft Windows XP operating system.


Ignore this error message. The uninstallation process completes successfully withno errors encountered in the process.

MKS Toolkit errors occur when uninstalling clientsOnly one version of the MKS Toolkit can exist on a Microsoft Windows computerat a time. The MKS Toolkit is installed with the IBM InfoSphere Information Serverclients. If you install a newer version of the clients, the version of the MKS Toolkitthat is packaged with the clients overwrites any older version of the MKS Toolkiton the system, resulting in version incompatibility issues between the MKS Toolkitand older versions of IBM InfoSphere Information Server clients. Versionincompatibility might also cause problems when you remove older InfoSphereInformation Server clients.

Symptoms

When you try to remove InfoSphere Information Server clients, you might seeseveral possible symptoms that point to version incompatibility issues:v When you attempt to remove an older InfoSphere Information Server client,

error messages are displayed when the software removal program tries toremove the MKS Toolkit. The messages are displayed because the older versionof the InfoSphere Information Server client is not compatible with the newversion of the MKS Toolkit.The following error message is displayed:ERROR: The product bean "installMksClientAction" could not be loaded...

v At the end of the software removal of the older InfoSphere Information Serverclient, the following error message is displayed:Could not uninstall assembly: uid=mksinstaller : version = 8.0.0.0: instance = 1

v After you remove IBM InfoSphere Information Server, Version 8.0.1 clients, theproduct shortcuts are not removed from the Windows Start menu.

Causes

A newer version of the MKS Toolkit was installed and overwrote the previouslyexisting version that was installed by the InfoSphere Information Server client thatyou are trying to remove. If you install multiple versions of the InfoSphereInformation Server client, the only version of the MKS Toolkit that remains onyour computer is the version that is packaged with the newest version of theInfoSphere Information Server client that you install.


If you remove the version of the InfoSphere Information Server client that installedthe current version of the MKS Toolkit without removing the MKS Toolkit, theremaining clients continue to run. However, if you later try to remove theremaining clients, you might receive error messages when you try to remove theMKS Toolkit because the versions are incompatible.

Environment

This advice applies to all Microsoft Windows operating systems.


If you removed all IBM InfoSphere DataStage and InfoSphere Information Serverclients but the MKS Toolkit remains, you can remove it by using the add orremove program function that is available with your version of Windows. Rebootthe computer after removing the MKS Toolkit.

Chapter 33. Removal problems 425


Part 8. Appendixes



Appendix A. Response file parameters (Linux, UNIX)

You can use the IBM InfoSphere Information Server installation program togenerate a response file that you can then modify and use to do silent installations.Alternatively, you can modify a provided response file template to run a silentinstallation on a Linux or UNIX system.

The response file templates are in the Image/samples/responses directory. Use thetemplates for the following purposes:v Creating a new installation of all productsv Installing selected tiers and products

Response files vary depending on the conditions of your particular installation.You can use this reference to view details about the file response parameters thatapply to your installation. Response parameters and their values are case sensitive.

allow.customize.was.profile.ports=[true|false]Set to true if you are specifying the settings for all IBM WebSphere ApplicationServer ports instead of installing with the default ports.

app.server.password=change_to_application_server_admin_passwordSet the password for the application server administrator.

app.server.type=[was]Set this property to the type of application server that is being configured.

An example value is was.

app.server.user=admin user IDSet to the user ID for the application server administrator. This ID will becreated in the local repository for authentication.

An example value is wasadmin.

DataStage=[true|false]Set to true if installing IBM InfoSphere DataStage.

DataStage.BalOp=[true|false]Set to true if installing IBM InfoSphere DataStage Balanced Optimization. Thisoption can be true only if DataStage is true.

DataStage.MVS=[true|false]Set to true if installing IBM InfoSphere DataStage MVS Edition.

DataStage.SAS=[true|false]Set to true if installing IBM InfoSphere DataStage Pack for SAS. This optioncan be true only if DataStage is true.

DataStage.Server=[true|false]Set to true if installing IBM InfoSphere DataStage.

db.driver=[com.ibm.db2.jcc.DB2Driver|com.ibm.isf.jdbc.sqlserver.SQLServerDriver|com.ibm.isf.jdbc.oracle.OracleDriver]

Set the driver to be used by the metadata repository for connection. Thisoption controls which database to use, and is available if you are using apreinstalled database.

An example value is com.ibm.db2.jcc.DB2Driver.


db.url=database_urlSet the database URL for the metadata repository or given database. Thesesample values apply only if you created the database using theDatabaseSupport scripts or if the database is on a remote system. Thefollowing database URLs are allowed:

db.url=jdbc:db2://hostname:port/database

jdbc:ibm:oracle://hostname:port;SID=database

jdbc:ibm:sqlserver://hostname:port;DatabaseName=database

An example value is jdbc:db2://hostname:port/database.

db2.admin.group.name=DB2_admin_group_nameSet to the IBM DB2 administrator group name.

An example value is dasadm.

db2.admin.home.directory=DB2_admin_home_directorySet to the DB2 administrator home directory.

An example value is /home/dasusr.

db2.admin.user.name=DB2_admin_usernameSet to the operating system ID to be used as the DB2 administrator ID. Thisvalue applies only if you are installing the repository tier.

An example value is dasuser.

db2.fenced.group.name=DB2_fenced_group_nameSet to the DB2 fenced group name.

An example value is db2fadm.

db2.fenced.home.directory=DB2_fenced_home_directorySet to the DB2 fenced home directory.

An example path is /home/db2fenc1.

db2.fenced.user.name=DB2_fenced_user_nameSet to the DB2 fenced user name.

An example value is db2fenc1.

db2.fenced.user.password=change_to_DB2_fenced_passwordSet to the DB2 fenced user password

db2.install.location=DB2_absolute_installation_pathSet to the absolute path where DB2 is to be installed.

An example value is /opt/IBM/db2.

db2.instance.group=DB2_instance_group_nameSet to the group name of the installed DB2 instance.

An example value is db2iadm.

db2.instance.home.directory=DB2_instance_home_directorySet to the directory of the installed instance of DB2.

An example value is /home/db2inst1.

db2.instance.name=DB2_instance_nameSet to a string that will identify the DB2 instance. The DB2INSTANCEenvironment variable will be set to this DB2 instance name by default.


An example value is db2inst1.

db2.instance.user.name=DB2_instance_user_nameSet to the user name of the instance of DB2.

An example value is db2inst1.

db2.instance.user.password=change_to_DB2_instance_user_passwordSet to the password of the DB2 instance user.

db2.port.number=DB2_instance_port_numberSet to the TCPIP port for this DB2 instance. This value applies only if you areinstalling the repository tier.

An example value is 50000.

ds.admin.gid=DataStage_admin_group_nameSet to the InfoSphere DataStage administrator group name.

An example value is dstage.

ds.admin.uid=DataStage_admin_usernameSet to the InfoSphere DataStage administrator user name.

An example value is dsadm.

ds.client.language.acronym=[ENU|FRA|DEU|ITA|ESP|PTB|CHS|CHT|JPN|KOR]

Set to the language code for InfoSphere DataStage clients.

Table 110. Supported language codes for InfoSphere DataStage

Language Code

English ENU

French FRA

German DEU

Italian ITA

Spanish ESP

Portuguese-Brazil PTB

Chinese-Simplified CHS

Chinese-Traditional CHT

Japanese JPN

Korean KOR

An example value is ENU.

ds.project.1.name=DataStage_project_nameSet the value to the InfoSphere DataStage project name that you want. Replacethe number, 1, with the project number that increments, starting with 1.

An example value is dstage1.

ds.project.1.path=path_to_DataStage_project_filesSet the value for the path to the InfoSphere DataStage project files. Replace thenumber, 1, with the project number that increments, starting with 1.

An example value is /opt/IBM/InformationServer/Server/Projects/dstage1.

ds.project.1.version=NewReplace the number with the incrementing number, starting with 1, of theproject to be created for InfoSphere DataStage.

Appendix A. Response file parameters (Linux, UNIX) 431

Set the value to New for this release.

Note: To make a project protected, add (Protected) in English, asdemonstrated in the last line in the following example.For example:ds.project.1.name=dstage1ds.project.1.path=/opt/IBM/InformationServer/Server/Projects/dstage1ds.project.1.version=Newds.project.2.name=addedprojds.project.2.path=/opt/IBM/InformationServer/Server/Projects/addedprojds.project.2.version=Newds.project.3.name=protectds.project.3.path=/opt/IBM/InformationServer/Server/Projects/protectds.project.3.version=New (Protected)

ds.rpc.instance.tag=ITAG_valueSet to the InfoSphere DataStage rpc instance tag (ITAG). The ITAG value is athree-digit hexadecimal. ACE, ADE, and DCD are reserved values. The ITAGvalue must be unique on the system.

ADE is the default value if you do not make this an ITAG installation. If youspecify a value for an ITAG installation, use a value other than ACE, ADE, orDCD.

dsrpc.port=DataStage_dsrpc_port_numberSet to the InfoSphere DataStage dsrpc port.


https.truststore.path=pathIn a secure HTTP (HTTPS) installation, set to the path to the truststore file thatcontains the certificate to accept.

An example location is tmp/MyFile.jks.

ia.db.hostname=Information_Analyzer_db_host_nameSet to the IBM InfoSphere Information Analyzer database server name.

The host name is the output of the hostname command on the system were theresponse file was generated.

ia.db.location=Information_Analyzer_db_locationSet to the path where the InfoSphere Information Analyzer database will bestored.

An example location is /opt/IBM/InformationServer/Repos/iadb.

ia.db.name=Information_Analyzer_db_locationSet to the name of the InfoSphere Information Analyzer database to be created.

An example database name is iadb.

ia.db.password=Information_Analyzer_db_owner_passwordSet to the password for the InfoSphere Information Analyzer database owner.

ia.db.port=port_number_for_DB2_instanceSet to the port for the DB2 instance where the database is to be created. If thisis a repository installation and the InfoSphere Information Analyzer database isto be created in the local DB2 instance, ia.db.port must use the same port asthe port used for db2.port.number.


ia.db.type=[db2|db2zos|oracle|sqlserver]Set to database type for the InfoSphere Information Analyzer database.


An example value is db2.

ia.db.username=Information_Analyzer_db_owner_IDSet to the operating system ID to be used as the InfoSphere InformationAnalyzer database owner ID.

An example value is iauser.

install.path=[1|2|3|4|5|6]Set to the type of installation:

1 = New Installation2 = Add Product3 = Add Tier4 = Remove Product5 = Remove Tier6 = Uninstall


is.admin.password=Information_Server_Admin_passwordSet to the password for the InfoSphere Information Server Administrator ID.

is.admin.user=Information_Server_Admin_IDSet to the user name that you want for the InfoSphere Information ServerAdministrator ID. This ID will be created in the local repository.

An example value is admin.

is.console.port=portSet to the HTTP or HTTPS port where InfoSphere Information Server isinstalled.

In HTTP installation, the value is typically 9080. In an HTTPS installation, thevalue is typically 9443 or 443.

is.ha.selected=[true|false]Set to true if this is an active-passive server cluster configuration installation.

is.https=[true|false]Set to true if this is an HTTPS installation.

is.sas.selected=[true|false]Set to true if you want to enable legacy IBM InfoSphere DataStage SAS jobs.This option can be true only if sas.install.choice is set to a valid value, andDataStage.SAS is true.

is.was.cluster=[true|false]Set to true if you are installing into a WebSphere Application Server clusterconfiguration.

isf.agent.port=[true|false]Set to the port number for the InfoSphere Information Server Agent.


isf.http.host=host_nameSet the host name of the front-end dispatcher for a cluster installation.

This value is the short form of hostname, excluding the domain. (For example,only the HTTP_host_name portion of HTTP_host_name.domain.com is used.)


isf.http.port=port_numberSet the HTTP or HTTPS port number of the front-end dispatcher for a clusterinstallation.


isf.server.host=ISF_server_host_nameSet the server host name for a cluster environment.

This value is the complete form of hostname, including the complete domain.

jobmon.port.1=port_number_for_first_job_monitor_portSet to the port number for the first job monitor port.


jobmon.port.2=port_number_for_second_job_monitor_portSet to the port number for the second job monitor port.


LIC_AGREEMENT=ACCEPTSet to ACCEPT to accept the license agreement.

logging.agent.port=Logging_Agent_port_numberSet to the port number for the Logging Agent.


mq.install.choice=[NONE|SERVER|CLIENT]Set to SERVER if you want to install the MQ Series Server plug-in.

Set to CLIENT if you want to install the MQ Series Client plug-in.

nls.enabled=[true|false]Set to true if you want globalization support for InfoSphere DataStage andIBM InfoSphere QualityStage.

The value, false, is supported only for systems that have the nls.languageparameter set to English and a supported system code page.

nls.language=[English-UTF8|English|Chinese-Simplified-UTF8|Chinese-Simplified|Chinese-Traditional-UTF8|Chinese-Traditional|French-UTF8|French|German-UTF8|German|Italian-UTF8|Italian|Japanese-EUC|Japanese-SJIS|Japanese-UTF8|Japanese|Korean-UTF8|Portuguese-Brazilian-UTF8|Portuguese-Brazilian|Spanish-UTF8|Spanish|Thai|Turkish]

Set to the language to configure for InfoSphere DataStage and InfoSphereQualityStage. The installation computer code page must be compatible andsupported by InfoSphere DataStage.

An example value is English.

nls.language.code=[ENU|FRA|PTB|JPN|ITA|KOR|DEU|CHT|CHS|ESP]Set to the three-letter language code for InfoSphere DataStage and InfoSphereQualityStage support.

Table 111. Supported language codes

Language Code

English ENU

French FRA

German DEU

Italian ITA


Table 111. Supported language codes (continued)

Language Code

Spanish ESP




Japanese JPN

Korean KOR


product[AVI].selected=[true|false]Set to true if installing IBM InfoSphere QualityStage Address VerificationInterface.

product[BusinessGlossary].selected=[true|false]Set to true if installing IBM InfoSphere Business Glossary.

product[BusinessGlossaryAnywhere].selected=[true|false]Set to true if installing IBM InfoSphere Business Glossary Anywhere.

product[DataStage].selected=[true|false]Set to true if installing InfoSphere DataStage.

product[DPID].selected=[true|false]Set to true if installing IBM InfoSphere QualityStage Module for DPID.

product[FastTrack].selected=[true|false]Set to true if installing IBM InfoSphere FastTrack.

product[InformationAnalyzer].selected=[true|false]Set to true if installing InfoSphere Information Analyzer.

product[ISTools].selected=[true|false]Set to true if installing InfoSphere Information Server Manager.

product[metadata.server].selected=[true]Set to true for installing IBM InfoSphere Metadata Server.

product[MetadataWorkbench].selected=[true|false]Set to true if installing IBM InfoSphere Metadata Workbench.

product[QualityStage].selected=[true|false]Set to true if installing InfoSphere QualityStage.

product[SERP].selected=[true|false]Set to true if installing IBM InfoSphere QualityStage Module for SERP.

product[WISD].selected=[true|false]Set to true if installing IBM InfoSphere Information Services Director.

sas.install.choice=[SASVersion6|SASVersion8|SASVersion9]Select the version of InfoSphere DataStage SAS that you are installing. If youare setting is.sas.selected to true to enable legacy InfoSphere DataStage SASjobs, you must provide a value for sas.install.choice.

An example value is SASVersion6.

suite.installLocation=IS_installation_pathSet to the absolute directory path where InfoSphere Information Server is to beinstalled.


An example value is /opt/IBM/InformationServer.

suite.tier[app.server.tier].selected=[true|false]Set to true if installing the Services tier.

suite.tier[client.tier].selected=[true|false]Set to true if installing the Client tier.

suite.tier[database.tier].selected=[true|false]Set to true if installing the Repository tier.

suite.tier[engine.tier].selected=[true|false]Set to true if installing the Engine tier.

target.country.code=[US|FR|BR|JP|IT|KR|DE|TW|CN|ES]Set the two-letter country or region code for the InfoSphere Information Serverinstallation.

Table 112. Supported country or region codes

Language Code

Brazil BR

China CN

France FR

Germany DE

Italy IT

Japan JP

Korea KR

Spain ES

Taiwan TW

United States US

An example value is US.

target.language.code=[en|fr|de|it|es|pt_BR|zh|zh_TW|ja|ko]Set the language code for the InfoSphere Information Server installation.


Language Code

English en

French fr

German de

Italian it

Spanish es

Portuguese-Brazil pt_BR

Chinese-Simplified zh

Chinese-Traditional zh_TW

Japanese ja

Korean ko

An example value is en.


use.bundled.db2=[true|false]Set to true if installing the DB2 database that is bundled with InfoSphereInformation Server.

use.bundled.was=[true|false]Set to true if installing the IBM WebSphere Application Server NetworkDeployment that is bundled with InfoSphere Information Server.

was.admin.host.port=was_console_port_numberSet to the port for the WebSphere Application Server administrative console.


was.bootstrap.port=websphere_bootstrap_port_numberSet to the WebSphere bootstrap port.


was.dcs.unicast.port=was_ha_manager_port_numberSet to WebSphere high availability manager communication port.


was.default.host.port=was_http_transport_port_numberSet to the port number for the HTTP transport port.


was.install.location=empty_was_installation_locationThe directory must be empty.

An example value is /opt/IBM/WebSphere/AppServer.

was.mutual.auth.listener.port=was_mutual_bootstrap_port_numberSet to the port number for the WebSphere mutual bootstrap port.


was.orb.listener.port=was_orb_listener_port_numberSet to the port number for the WebSphere ORB listening port.


was.profile.dir=was_profile_directorySet the WebSphere profile directory.

An example value is /opt/IBM/WebSphere/AppServer/profiles/InfoSphere.

was.profile.name=was_profile_nameSet the WebSphere profile name.

An example value is InfoSphere.

was.sas.ssl.port=SAS_SSL_portSet to the port number for the SAS SSL Server Authentication listener.


was.secure.admin.host.port=secure_was_portSet to the port number for the secure WebSphere Application Serveradministrative console.


was.secure.default.host.port=default_secure_HTTP_transport_portSet to the port number for the default secure HTTP transport port.



was.secure.sib.mq.port=secure_service_integration_MQ_port_numberSet to the port number for the secure service integration MQ interoperabilityport.


was.secure.sib.port=secure_service_integration_port_numberSet to the port number for the secure service integration port.


was.server.auth.listener.port=CSIV2_server_auth_port_numberSet to the port number for the CSIV2 server authentication port.


was.server.name=was_server_nameSet the WebSphere Application Server server name.

An example value is server1.

was.sib.mq.port=service_integration_MQ_port_numberSet to the port number for the service integration MQ interoperability port.


was.sib.port=service_integration_portSet to the port number for the service integration port.


was.sip.port=SIP_port_numberSet to the port number for the SIP port.


was.sip.secured.port=SIP_secured_port_numberSet to the port number for the secured SIP port.


was.soap.connector.port=SOAP_connector_port_numberSet to the port number for the SOAP connector port.


xmeta.db.collection=DB2_JDBC_collection_nameSet to the collection name for DB2 JDBC collection. Used for IBM DB2 forz/OS.

xmeta.db.config.type=[db2_9_nls|db2_9_zOS_nls|oracle10g_nls|sqlserver_nls]To set the database configuration type for metadata repository.

An example value is db2_9_nls.

xmeta.db.hostname=metadata_repository_server_host_nameSet to the host name for the metadata repository database server.

An example value is myhostname.mydomain.com.

xmeta.db.location=metadata_repository_db_locationSet to the path for Linux or UNIX where you want the metadata repositorydatabase to be created.

An example value is /opt/IBM/InformationServer/Repos/xmeta.

xmeta.db.name=metadata_repository_db_nameSet to the database name for the metadata repository.


An example value is xmeta.

xmeta.db.password=metadata_repository_db_owner_passwordSet to the password for the metadata repository database owner.

xmeta.db.port=metadata_repository_db_portSet to the port for the DB2 instance where the database is to be created. Theport for xmeta.db.port must be the same as db2.port.number if this is arepository installation and the InfoSphere Information Analyzer database is tobe created in the local DB2 instance.


xmeta.db.tablespace=z/OS_metdata_repository_table_space_nameSet to the table space name to be created on the DB2 for z/OS database. Thisparameter is ignored for other databases.

xmeta.db.type=[db2|db2zos|oracle|sqlserver]Set the database type for the metadata repository.


xmeta.db.username=metadata_respository_db_owner_IDSet to the operating system ID to be used as the metadata repository databaseowner ID.


xmeta.driver.type=[DB2_9|DB2_ZOS|ORACLE|SQL_SERVER]Set the driver type for the metadata repository.

An example value is DB2_9.



Appendix B. Response file parameters (Windows)

You can use the IBM InfoSphere Information Server installation program togenerate a response file that you can then modify and use to do silent installations.Alternatively, you can modify a provided response file template to run a silentinstallation on your Microsoft Windows system.

The response file templates are in the Image/samples/responses directory. Use thetemplates for the following purposes:v Creating a new installation of all productsv Installing selected tiers and products

Response files vary depending on the conditions of your particular installation.You can use this reference to view details about the file response parameters thatapply to your installation. Response parameters and their values are case sensitive.

allow.customize.was.profile.ports=[true|false]Set to true if you are specifying the settings for all IBM WebSphere ApplicationServer ports instead of installing with the default ports.

app.server.password=change_to_application_server_admin_passwordSet the password for the application server administrator.

app.server.type=[was]Set this property to the type of application server that is being configured.

An example value is was.

app.server.user=admin user IDSet to the user ID for the application server administrator. This ID will becreated in the local repository for authentication.

An example value is wasadmin.

DataStage=[true|false]Set to true if installing IBM InfoSphere DataStage.

DataStage.BalOp=[true|false]Set to true if installing IBM InfoSphere DataStage Balanced Optimization. Thisoption can be true only if DataStage is true.

DataStage.MVS=[true|false]Set to true if installing IBM InfoSphere DataStage MVS Edition.

DataStage.SAS=[true|false]Set to true if installing IBM InfoSphere DataStage Pack for SAS. This optioncan be true only if DataStage is true.

DataStage.Server=[true|false]Set to true if installing IBM InfoSphere DataStage.

db.driver=[com.ibm.db2.jcc.DB2Driver|com.ibm.isf.jdbc.sqlserver.SQLServerDriver|com.ibm.isf.jdbc.oracle.OracleDriver]

Set the driver to be used by the metadata repository for connection. Thisoption controls which database to use, and is available if you are using apreinstalled database.

An example value is com.ibm.db2.jcc.DB2Driver.


db.url=database_urlSet the database URL for the metadata repository or given database. Thesesample values apply only if you created the database using theDatabaseSupport scripts or if the database is on a remote system. Thefollowing database URLs are allowed:

db.url=jdbc:db2://hostname:port/database

jdbc:ibm:oracle://hostname:port;SID=database

jdbc:ibm:sqlserver://hostname:port;DatabaseName=database

An example value is jdbc:db2://hostname:port/database.

db2.admin.user.name=DB2_admin_usernameSet to the operating system ID to be used as the IBM DB2 administrator ID.This value applies only if you are installing the repository tier.

An example value is db2admin.

db2.admin.user.password=change_to_DB2_admin_passwordSet to the password for the DB2 administrator ID. This value applies only ifyou are installing the repository tier.

db2.install.location=DB2_absolute_installation_pathSet to the absolute path where DB2 is to be installed.

An example path is: C:\IBM\SQLLIB.

db2.port.number=DB2_instance_port_numberSet to the TCPIP port for this DB2 instance. This value applies only if you areinstalling the repository tier.


ds.client.language.acronym=[ENU|FRA|DEU|ITA|ESP|PTB|CHS|CHT|JPN|KOR]

Set to the language code for InfoSphere DataStage clients.

Table 114. Supported language codes for InfoSphere DataStage

Language Code

English ENU

French FRA

German DEU

Italian ITA

Spanish ESP




Japanese JPN

Korean KOR


ds.project.1.name=DataStage_project_nameSet the value to the InfoSphere DataStage project name that you want. Replacethe number, 1, with the project number that increments, starting with 1.


An example value is dstage1.

ds.project.1.path=path_to_DataStage_project_filesSet the value for the path to the InfoSphere DataStage project files. Replace thenumber, 1, with the project number that increments, starting with 1.

An example value is C:\\IBM\\InformationServer\\Server\\Projects\\dstage1.

ds.project.1.version=NewReplace the number with the incrementing number, starting with 1, of theproject to be created for InfoSphere DataStage.

Set the value to New for this release.

Note: To make a project protected, add (Protected) in English, asdemonstrated in the last line in the example.For example:ds.project.1.name=dstage1ds.project.1.path=C:\\IBM\\InformationServer\\Server\\Projects\\dstage1ds.project.1.version=Newds.project.2.name=addedprojds.project.2.path=C:\\IBM\\InformationServer\\Server\\Projects\\addedprojds.project.2.version=Newds.project.3.name=protectds.project.3.path=C:\\IBM\\InformationServer\\Server\\Projects\\protectds.project.3.version=New (Protected)

https.truststore.path=pathIn a secure HTTP (HTTPS) installation, set to the path to the truststore file thatcontains the certificate to accept.

An example location is C:\\tempMyFile.jks.

ia.db.hostname=Information_Analyzer_db_host_nameSet to the IBM InfoSphere Information Analyzer database server name.

The host name is the output of the hostname command on the system were theresponse file was generated.

ia.db.location=Information_Analyzer_db_locationSet to the path where the InfoSphere Information Analyzer database will bestored.

An example location is C:\\.

ia.db.name=Information_Analyzer_db_nameSet to the name of the InfoSphere Information Analyzer database to be created.

An example database name is iadb.

ia.db.password=Information_Analyzer_db_owner_passwordSet to the password for the InfoSphere Information Analyzer database owner.

ia.db.port=port_number_for_DB2_instanceSet to the port for the DB2 instance where the database is to be created. If thisis a repository installation and the InfoSphere Information Analyzer database isto be created in the local DB2 instance, ia.db.port must use the same port asthe port used for db2.port.number.

An example port is 50000.

ia.db.type=[db2|db2zos|oracle|sqlserver]Set to database type for the InfoSphere Information Analyzer database.


Appendix B. Response file parameters (Windows) 443

ia.db.username=Information_Analyzer_db_owner_IDSet to the operating system ID to be used as the InfoSphere InformationAnalyzer database owner ID.

An example value is iauser.

install.path=[1|2|3|4|5|6]Set to the type of installation:

1 = New Installation2 = Add Product3 = Add Tier4 = Remove Product5 = Remove Tier6 = Uninstall


is.admin.password=Information_Server_Admin_passwordSet to the password for the InfoSphere Information Server Administrator ID.

is.admin.user=Information_Server_Admin_IDSet to the user name that you want for the InfoSphere Information ServerAdministrator ID. This ID will be created in the local repository.

An example value is admin.

is.console.port=portSet to the HTTP or HTTPS port where InfoSphere Information Server isinstalled.

In HTTP installation, the value is typically 9080. In an HTTPS installation, thevalue is typically 9443 or 443.

is.ha.selected=[true|false]Set to true if this is an active-passive server cluster configuration installation.

is.https=[true|false]Set to true if this is an HTTPS installation.

is.was.cluster=[true|false]Set to true if you are installing into a WebSphere Application Server clusterconfiguration.

isf.agent.port=[true|false]Set to the port number for the InfoSphere Information Server Agent.


isf.http.host=host_nameSet the host name of the front-end dispatcher for a cluster installation.

This value is the short form of hostname, excluding the domain. (For example,only the HTTP_host_name portion of HTTP_host_name.domain.com is used.)

isf.http.port=port_numberSet the HTTP or HTTPS port number of the front-end dispatcher for a clusterinstallation.


isf.server.host=ISF_server_host_nameSet the server host name for a cluster environment.

This value is the complete form of hostname, including the complete domain.


jobmon.port.1=port_number_for_first_job_monitor_portSet to the port number for the first job monitor port.


jobmon.port.2=port_number_for_second_job_monitor_portSet to the port number for the second job monitor port.


LIC_AGREEMENT=ACCEPTSet to ACCEPT to accept the license agreement.

logging.agent.port=Logging_Agent_port_numberSet to the port number for the Logging Agent.


mq.install.choice=[NONE|SERVER|CLIENT]Set to SERVER if you want to install the MQ Series Server plug-in.

Set to CLIENT if you want to install the MQ Series Client plug-in.

nls.enabled=[true|false]Set to true if you want globalization support for InfoSphere DataStage andIBM InfoSphere QualityStage.

The value, false, is supported only for systems that have the nls.languageparameter set to English and a supported system code page.

nls.language=[English-UTF8|English|Chinese-Simplified-UTF8|Chinese-Simplified|Chinese-Traditional-UTF8|Chinese-Traditional|French-UTF8|French|German-UTF8|German|Italian-UTF8|Italian|Japanese-EUC|Japanese-SJIS|Japanese-UTF8|Japanese|Korean-UTF8|Portuguese-Brazilian-UTF8|Portuguese-Brazilian|Spanish-UTF8|Spanish|Thai|Turkish]

Set to the language to configure for InfoSphere DataStage and InfoSphereQualityStage. The installation computer code page must be compatible andsupported by InfoSphere DataStage.

An example value is English.

nls.language.code=[ENU|FRA|PTB|JPN|ITA|KOR|DEU|CHT|CHS|ESP]Set to the three-letter language code for InfoSphere DataStage and InfoSphereQualityStage support.


Language Code

English ENU

French FRA

German DEU

Italian ITA

Spanish ESP




Japanese JPN

Korean KOR



product[AVI].selected=[true|false]Set to true if installing IBM InfoSphere QualityStage Address VerificationInterface.

product[BusinessGlossary].selected=[true|false]Set to true if installing IBM InfoSphere Business Glossary.

product[BusinessGlossaryAnywhere].selected=[true|false]Set to true if installing IBM InfoSphere Business Glossary Anywhere.

product[DataStage].selected=[true|false]Set to true if installing InfoSphere DataStage.

product[DPID].selected=[true|false]Set to true if installing IBM InfoSphere QualityStage Module for DPID.

product[FastTrack].selected=[true|false]Set to true if installing IBM InfoSphere FastTrack.

product[InformationAnalyzer].selected=[true|false]Set to true if installing InfoSphere Information Analyzer.

product[ISTools].selected=[true|false]Set to true if installing InfoSphere Information Server Manager.

product[metadata.server].selected=[true]Set to true for installing IBM InfoSphere Metadata Server.

product[MetadataWorkbench].selected=[true|false]Set to true if installing IBM InfoSphere Metadata Workbench.

product[QualityStage].selected=[true|false]Set to true if installing InfoSphere QualityStage.

product[SERP].selected=[true|false]Set to true if installing IBM InfoSphere QualityStage Module for SERP.

product[WISD].selected=[true|false]Set to true if installing IBM InfoSphere Information Services Director.

suite.installLocation=IS_installation_pathSet to the absolute directory path where InfoSphere Information Server is to beinstalled.

An example value is C:\\IBM\\InformationServer.

suite.tier[app.server.tier].selected=[true|false]Set to true if installing the Services tier.

suite.tier[client.tier].selected=[true|false]Set to true if installing the Client tier.

suite.tier[database.tier].selected=[true|false]Set to true if installing the Repository tier.

suite.tier[engine.tier].selected=[true|false]Set to true if installing the Engine tier.

target.country.code=[US|FR|BR|JP|IT|KR|DE|TW|CN|ES]Set the two-letter country or region code for the InfoSphere Information Serverinstallation.

Table 116. Supported country or region codes

Language Code

Brazil BR


Table 116. Supported country or region codes (continued)

Language Code

China CN

France FR

Germany DE

Italy IT

Japan JP

Korea KR

Spain ES

Taiwan TW

United States US

An example value is US.

target.language.code=[en|fr|de|it|es|pt_BR|zh|zh_TW|ja|ko]Set the language code for the InfoSphere Information Server installation.


Language Code

English en

French fr

German de

Italian it

Spanish es

Portuguese-Brazil pt_BR

Chinese-Simplified zh

Chinese-Traditional zh_TW

Japanese ja

Korean ko

An example value is en.

use.bundled.db2=[true|false]Set to true if installing the DB2 database that is bundled with InfoSphereInformation Server.

use.bundled.was=[true|false]Install the IBM WebSphere Application Server Network Deployment that isbundled with InfoSphere Information Server.

was.admin.host.port=was_console_port_numberSet to the port for the WebSphere Application Server administrative console.


was.bootstrap.port=websphere_bootstrap_port_numberSet to the WebSphere bootstrap port.


was.dcs.unicast.port=was_ha_manager_port_numberSet to WebSphere high availability manager communication port.



was.default.host.port=was_http_transport_port_numberSet to the port number for the HTTP transport port.


was.install.location=was_installation_locationSet to the directory where installing WebSphere Application Server. Thedirectory must be empty.

An example value is C:\\IBM\\WebSphere\\AppServer.

was.mutual.auth.listener.port=was_mutual_bootstrap_port_numberSet to the port number for the WebSphere mutual bootstrap port.


was.orb.listener.port=was_orb_listener_port_numberSet to the port number for the WebSphere ORB listening port.


was.profile.dir=was_profile_directorySet the WebSphere profile directory.

An example value is C:\\IBM\\WebSphere\\AppServer\\profiles\\InfoSphere.

was.profile.name=was_profile_nameSet the WebSphere profile name.

An example value is InfoSphere.

was.sas.ssl.port=SAS_SSL_portSet to the port number for the SAS SSL Server Authentication listener.


was.secure.admin.host.port=secure_was_portSet to the port number for the secure WebSphere Application Serveradministrative console.


was.secure.default.host.port=default_secure_HTTP_transport_port_numberSet to the port number for the default secure HTTP transport port.


was.secure.sib.mq.port=secure_service_integration_MQ_port_numberSet to the port number for the secure service integration MQ interoperabilityport.


was.secure.sib.port=secure_service_integration_port_numberSet to the port number for the secure service integration port.


was.server.auth.listener.port=CSIV2_server_auth_port_numberSet to the port number for the CSIV2 server authentication port.


was.server.name=was_server_nameSet the WebSphere Application Server server name.

An example value is server1.


was.sib.mq.port=service_integration_MQ_port_numberSet to the port number for the service integration MQ interoperability port.


was.sib.port=service_integration_port_numberSet to the port number for the service integration port.


was.sip.port=SIP_port_numberSet to the port number for the SIP port.


was.sip.secured.port=SIP_secured_port_numberSet to the port number for the secured SIP port.


was.soap.connector.port=SOAP_connector_port_numberSet to the port number for the SOAP connector port.


xmeta.db.collection=DB2_JDBC_collection_nameSet to the collection name for DB2 JDBC collection. Used for IBM DB2 forz/OS.

xmeta.db.config.type=[db2_9_nls|db2_9_zOS_nls|oracle10g_nls|sqlserver_nls]To set the database configuration type for metadata repository.

An example value is db2_9_nls.

xmeta.db.hostname=metadata_repository_server_host_nameSet to the host name for the metadata repository database server.

An example value is myhostname.mydomain.com.

xmeta.db.location=metadata_repository_db_locationSet to the drive on Windows where you want the metadata repository databaseto be created.

An example value is C:\\.

xmeta.db.name=metadata_repository_db_nameSet to the database name for the metadata repository.


xmeta.db.password=metadata_repository_db_owner_passwordSet to the password for the metadata repository database owner.

xmeta.db.port=metadata_repository_db_portSet to the port for the DB2 instance where the database is to be created. Theport for xmeta.db.port must be the same as db2.port.number if this is arepository installation and the InfoSphere Information Analyzer database is tobe created in the local DB2 instance.


xmeta.db.tablespace=z/OS_metdata_repository_table_space_nameSet to the table space name to be created on the DB2 for z/OS database. Thisparameter is ignored for other databases.

xmeta.db.type=[db2|db2zos|oracle|sqlserver]Set the database type for the metadata repository.



xmeta.db.username=metadata_respository_db_owner_IDSet to the operating system ID to be used as the metadata repository databaseowner ID.


xmeta.driver.type=[DB2_9|DB2_ZOS|ORACLE|SQL_SERVER]Set the driver type for the metadata repository.

An example value is DB2_9.


Appendix C. Naming restrictions for user IDs and passwords

Some restrictions apply to the names that you choose for user IDs and passwords.

All user IDs and passwordsThe 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, such as spaces, tabs, and line continuationcharacters, is removed by the installation program. Any existing user IDsand passwords cannot have leading or trailing white space characters aspart of their definitions.

Internal user registry user IDsOnly alphanumeric characters and the following characters are permitted:

_ (underscore)- (hyphen)\ (backslash)= (equal sign). (period)

IBM WebSphere Application Server administrator passwordThe following characters are not permitted:v Space charactersv ^ (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. Must not be the first character.)

Linux and UNIX user names and passwords cannot start with a numericdigit.


v On UNIX, the DB2 database requires these user accounts: DB2 instanceowner, DB2 fenced user, and DB2 administrator. These account namescannot begin with these characters:

SQL

SYS

IBM

v In addition, these account names cannot use these words:USERS

ADMINS

GUESTS

PUBLIC

LOCAL

Any SQL reserved word in the SQL reference for the database systemv Names cannot include accented characters.v UNIX and Linux users, groups, and instance names must be in

lowercase letters.

Character length limits

v AIX operating system user IDs: 8v WebSphere Application Server IDs: 60v DB2 user IDs and passwords:

– UNIX and Linux: 8– Microsoft Windows: 30


Appendix D. Installation checklists

These quick start checklists list step-by-step procedures for installing andconfiguring IBM InfoSphere Information Server in various scenarios.

For more generic road maps for different configurations, see Chapter 4, “PlanningStep 4: Determining your installation strategy,” on page 59. Each road mapincludes example scenarios for various installations.

Installation checklist with separate engine tierIn this configuration, you install the IBM InfoSphere Information Server engine onone computer and the application server, the common and product-specificcomponents, and the metadata repository database on another computer. Bothcomputers run a supported Linux or UNIX operating system.

Additionally, you install InfoSphere Information Server clients on a supportedMicrosoft Windows operating system.

The following diagram illustrates this configuration.

Note: Although the diagram shows only one client tier computer, you can installthe client tier on multiple computers.

Client tier

Engine tier


Services tier


Computer A

Network

Figure 51. Configuration with separate server dedicated to the engine tier


When you run the InfoSphere Information Server installation program to installInfoSphere Information Server, you also install IBM WebSphere Application ServerNetwork Deployment, Version 7.0 and the IBM DB2 9.7 database system. Youconfigure the metadata repository database within this database system. If IBMInfoSphere Information Analyzer is installed, you also configure the analysisdatabase within this database system.

The following procedures suggest various user and group names. You can usethese names, or use different names in accordance with your company policies.

1. Setting up the environment

Before you install the product, plan your installation and set up network and filesystems.

Table 118. Environment setup tasks for all tiers

Task Record your information here

1. Verify that you are installing the correct packages for your operatingsystem.

See the system requirements at www.ibm.com/support/docview.wss?rs=14&uid=swg27016382.

2. Plan the volume groups and file systems on which you are installingInfoSphere Information Server. Verify that you have sufficient storage spacein your file systems.

See the system requirements, and “Planning volume groups and filesystems” on page 67.

3. Review and verify the planning and system requirements information.

See Part 1, “Planning for the installation of IBM InfoSphere InformationServer,” on page 1.

4. Verify name resolution:

v Verify that the computers in the installation can resolve all the othercomputers by both the short name (host name only) and long name (fullyqualified host and domain name). Verify that both the short and long hostnames resolve to the same IP address.

v Verify that the computers in the installation can resolve their own namesto IP addresses by both short name and long name.

v Ensure that the localhost host name resolves to IP address 127.0.0.1.Ensure that the computer host name is not mapped to the 127.0.0.1.

v Add the short and long names of all the computers in the installation tothe /etc/hosts file of each computer in the installation.

See “Verifying the network and opening ports” on page 133.

5. Open the TCP ports for InfoSphere Information Server and the applicationserver across any applicable firewalls.


6. Create the temporary directories /tmp and /var/tmp, if they do not alreadyexist. The root user must have read, write, and execute permissions to thesedirectories. The installation program must be run as root.

See “Planning volume groups and file systems” on page 67.




Table 118. Environment setup tasks for all tiers (continued)


7. Prepare each computer to run the InfoSphere Information Serverinstallation program, and back up any critical data on the computers.

See “Preparing to run the installation program” on page 177.

2. Installing and configuring the metadata repository andservices tiers

Prepare for the metadata repository tier and services tier, and then run theInfoSphere Information Server installation program.

Table 119. Metadata repository tier and services tier tasks


1. Update the DB2 and WebSphere Application Server kernel parameters anduser limits on each computer for the metadata repository tier, services tier,and engine tier.

See “Modifying kernel parameters and user limits (Linux, UNIX)” on page137.

2. Create the following administration accounts on the computer. Log in toeach account to confirm that it functions properly:

v DB2 database administrator user: dasusr1 in the dasadm1 group

v DB2 database instance owner: db2inst1 in the db2iadm1 group

v DB2 fenced user: db2fenc1 in the db2fadm1 group

v Owner of the metadata repository: xmeta in the xmeta group

v (If installing InfoSphere Information Analyzer) The owner of the analysisdatabase: iauser in the iauser group

See “Setting up administrator and owner accounts” on page 142.


1. From the is-suite directory on the installation media, run followingcommand to start the installation program:

./setup -verbose

2. Using a supported web browser on a Windows computer, open the URLthat the ./setup command displays.

3. In the installation program, accept all defaults, except:

a. In the Tier Selection page, choose Metadata repository and Services.

b. In the Application Server page, choose Install WebSphereApplication Server.

c. In the Database Server page, choose Install IBM DB2 9.7 EnterpriseServer Edition.


See “Starting the installation program in graphical mode” on page 180.

Appendix D. Installation checklists 455

3. Installing and configuring the engine tier

Set up directories and accounts. Then install and configure the engine tier.

Table 120. Engine tier tasks


1. Create an administrator account for the InfoSphere Information Serverengine. Log in to the account to activate the password.


2. For non-English locales, make sure that the locale and encoding are setcorrectly. The installation program uses the locale and encoding informationof the computer to determine whether it can provide language support.

See “Setting the locale for the target computer” on page 157.


1. From the is-suite directory on the installation media, run followingcommand to start the installation program:

./setup -verbose


3. In the installation program, accept all defaults, except in the Tier Selectionpage, choose Engine.



4. Configure the ODBC Data Source Name by using drivers ininstall_home/Server/branded_odbc as described in the documentation inthat directory.

Also see “Configuring ODBC access (Linux, UNIX)” on page 247.

5. For mixed locale clients, ensure that IBM InfoSphere DataStage, IBMInfoSphere QualityStage, and IBM InfoSphere Information Analyzer usershave the correct settings specified for globalization.

See “Ensuring that InfoSphere DataStage users have the correct localizationsettings (Linux, UNIX)” on page 246.

6. Review the system requirements to choose a supported C++ compiler forjob development, and install it in its default location.

See “Installing a C++ compiler for job development” on page 159.

4. Installing and configuring the client tier

On each computer where you need the client programs, run the InfoSphereInformation Server installation program, and then configure ODBC drivers.


Table 121. Client tier tasks

Task Document your information here


1. Double-click the setup icon to start the installation program. The programwindows display in your default Web browser.

2. In the installation program, accept all defaults, except in the Tier Selectionpage, choose Client only.Note: If you are using the client-only installation media, the TierSelection page does not display. The program installs the client tier only.



2. Configure the ODBC Data Source Name by using drivers ininstall_home\ODBCDrivers as described in the documentation in thatdirectory.

5. Completing the installation

After you install the tiers, configure users, security, connectivity, and productmodules.

Table 122. Postinstallation tasks for all tiers


1. Set up firewall exceptions for client-side executable files.

See Chapter 15, “Firewall exceptions for client-side executable files(Windows),” on page 231.

2. Optional: Configure Secure Sockets Layer (SSL):

v Enable SSL for inbound RMI/IIOP. When you install InfoSphereInformation Server, SSL for inbound RMI/IIOP communications isdisabled by default.

v If the installation program did not configure HTTPS for a tier computerduring InfoSphere Information Server installation, manually configureHTTPS for that tier computer.

To allow clients to communicate with the server by using HTTPS, youmust manually configure HTTPS on each client tier computer.

See Chapter 16, “Enablement of Secure Sockets Layer (SSL),” on page 233.

3. Optional: Change InfoSphere Information Server to use an external userregistry such as the local operating system user registry or a LightweightDirectory Access Protocol (LDAP) user registry.

See the IBM InfoSphere Information Server Administration Guide.

4. If InfoSphere Information Server is configured to use the internal userregistry, create users and groups by using the InfoSphere Information Serverconsole or the InfoSphere Information Server Web console. If InfoSphereInformation Server is configured to use an external user registry, usestandard operating system utilities or user registry utilities.



Table 122. Postinstallation tasks for all tiers (continued)


5. If necessary, map credentials between the InfoSphere Information Serveruser registry that you chose in Step 4 and the local operating system userregistry on the computer where the InfoSphere Information Server engine isinstalled.




7. Assign project roles to users.


8. Configure IBM InfoSphere Information Analyzer, IBM InfoSphere BusinessGlossary, IBM InfoSphere Metadata Workbench, and IBM InfoSphereFastTrack (if you installed any of these product modules).

See Chapter 18, “Configuring product modules in the suite,” on page 245.

9. Optional: Run the IBM Support Assistant Lite for InfoSphere InformationServer tool to verify the installation.

See “Installation verification and troubleshooting” on page 197.


Installation checklist with IBM WebSphere Application Server clusterand IBM DB2 cluster

In this configuration, you install the IBM InfoSphere Information Server servicestier in a WebSphere Application Server cluster for high availability and scalability.The metadata repository tier is installed in a DB2 cluster. All server computers runa supported Linux or UNIX operating system.

Additionally, you install InfoSphere Information Server clients on a supportedMicrosoft Windows operating system.

The following diagram illustrates a sample configuration. You might choose tocreate a different front-end configuration than the diagram illustrates, or includemore WebSphere Application Server nodes. For more information about InfoSphereInformation Server clustered configurations, see “High availability configurations”on page 27.

The following procedures suggest various user and group names. You can usethese names, or use different names in accordance with your company policies.

Heartbeat

Cluster

DB2DB

Engine tier

Services tier


FIREWALL

Backup loadbalancer

Loadbalancer

Webserver 1

Webserver 2


Serverdeployment

manager


Servernode 2


Server node 1

Engine tiercomputer

Clienttier

Clientworkstations

InfoSpereInformation

Server engine

Metadata repositorycomputer (standby)

High availabilitymanagement software

DB2 DBMS

Metadata repositorycomputer (active)

High availabilitymanagement software

DB2 DBMS

Figure 52. Sample configuration with WebSphere Application Server cluster and DB2 cluster


1. Setting up the environment

Before you install the product, plan your installation and set up network and filesystems on all tiers.

Table 123. Environment setup tasks for all tiers


1. Verify that you are installing the correct packages for your operatingsystem.

See the system requirements at www.ibm.com/support/docview.wss?rs=14&uid=swg27016382.

2. Plan the volume groups and file systems on which you are installingInfoSphere Information Server. Verify that you have sufficient storage spacein your file systems.

See the system requirements, and “Planning volume groups and filesystems” on page 67.

3. Review and verify the planning and system requirements information.

See Part 1, “Planning for the installation of IBM InfoSphere InformationServer,” on page 1.

4. Verify name resolution:

v Verify that the computers in the installation can resolve the othercomputers by both the short name (host name only) and long name (fullyqualified host and domain name). Verify that both the short and long hostnames resolve to the same IP address.

v Verify that the computers in the installation can resolve their own namesto IP addresses by both short name and long name.

v Ensure that the localhost host name resolves to IP address 127.0.0.1.Ensure that the computer host name is not mapped to the 127.0.0.1.

v Add the short and long names of all the computers in the installation tothe /etc/hosts file of each computer in the installation.


5. Open the TCP ports for InfoSphere Information Server and the applicationserver across any applicable firewalls.


6. Update the DB2 and WebSphere Application Server kernel parameters anduser limits on each computer for the metadata repository tier, services tier,and engine tier.

See “Modifying kernel parameters and user limits (Linux, UNIX)” on page137.

7. Create the temporary directories /tmp and /var/tmp, if they do not alreadyexist. The root user must have read, write, and execute permissions to thesedirectories. The installation program must be run as root.

See “Planning volume groups and file systems” on page 67.

8. Prepare each computer to run the InfoSphere Information Serverinstallation program, and back up any critical data on the computers.

See “Preparing to run the installation program” on page 177.




2. Preparing the metadata repository tier

Install the DB2 database system and create the cluster and the database for themetadata repository.

Table 124. Metadata repository tier tasks


1. Prepare the DB2 cluster computers, file system, network, and storage.

See “Preparing the servers, file system, and storage” on page 338.

2. (Optional) Install and configure IBM Tivoli System Automation forMultiplatforms (SA MP). This software monitors the state of the DB2database system servers and manages failover.

See “Installing high availability software on DB2 database system servers” onpage 339.

3. Create the following administration accounts on each DB2 clustercomputer. The accounts on each computer must be identical. Log in to eachaccount to confirm that it functions properly:

v DB2 database administrator user: dasusr1 in the dasadm1 group

v DB2 database instance owner: db2inst1 in the db2iadm1 group

v DB2 fenced user: db2fenc1 in the db2fadm1 group

v Owner of the metadata repository: xmeta in the xmeta group

v (If installing InfoSphere Information Analyzer) The owner of the analysisdatabase: iauser in the iauser group


4. Install the DB2 database system, create a cluster, and create the metadatarepository database on the primary node.

See “Installing the DB2 database system and creating the cluster andmetadata repository database” on page 340.

3. Installing and configuring the services tier

Install the application server, create a cluster, and then run the InfoSphereInformation Server installation program.

Start with only one managed node in the cluster. Add additional nodes only afterInfoSphere Information Server installation is complete. This strategy minimizescomplexity and installation time.

Table 125. Services tier tasks


1. (Linux) Make sure that all WebSphere Application Server processes willstart with the correct ulimit setting on the computer where you will installthe deployment manager and on all computers that will host a managednode. Add the following to the /etc/profile file:

ulimit -n 10240



Table 125. Services tier tasks (continued)


2. Install IBM WebSphere Application Server Network Deployment on all thecomputers that will host the services tier. This installation includes thedeployment manager system and all computers that will host a managednode in the cluster. Also install any required WebSphere Application Serverfix packs and iFixes.

See “Installing IBM WebSphere Application Server Network Deployment fora cluster installation” on page 324.

3. On the computer that hosts the deployment manager, create a deploymentmanager profile that contains the deployment manager process. Make surethat Administrative Security is disabled.

See “Creating a deployment manager profile” on page 325.

4. On the computer that hosts the managed node, use the ProfileManagement Tool to create a custom profile. This profile will contain thenode agent process and the managed server process that will be part of thecluster.

See “Creating a custom profile” on page 326.

5. Use the WebSphere Application Server administrative console to create acluster with one cluster member definition.

See “Creating a cluster and cluster members for the application server” onpage 326.

6. Install a front-end Web server and the Web server plug-in module. Run theconfigurewebserver_name script to create a Web server definition inWebSphere Application Server, and do other Web server configuration.

See “Installing a front-end Web server” on page 328.

7 Optional: Install backup Web servers, load balancers, firewalls, and otherarchitectural components.

See “Installing a front-end load balancer (Optional)” on page 329.

8. Optional: To increase security, configure the WebSphere Application Serverfront-end Web server to accept secure HTTP (HTTPS) calls.

See “Configuring the front-end HTTP server for HTTPS” on page 155.

9. Ensure that no firewall is deployed within the IBM WebSphere ApplicationServer Network Deployment cell.

10. Make sure that you can start and stop the Web server. Then start the Webserver.


11. On the computer that hosts the deployment manager, verify that you canstart and stop the deployment manager process. Then start the process andverify that it is running.


12. On the computer that hosts the managed node, verify that you can startand stop the managed node and node agent that you created. Then start theprocess and verify that it is running. Verify that it does not have globalsecurity on.





Table 125. Services tier tasks (continued)


13. Run the installation program on the computer where the WebSphereApplication Server deployment manager is installed:

1. From the is-suite directory on the installation media, run the followingcommand to start the installation program:

./setup -verbose


3. In the installation program, accept all defaults, except these items:

a. In the Tier Selection page, choose Services only.

b. In the Application Server page, choose Use an existing WebSphereApplication Server installation.

c. In the WebSphere Application Server Profile page, choose theDeployment Manager profile.

d. In the WebSphere Application Server Cluster Information page,specify the URL of the front-end HTTP dispatcher for the WebSphereApplication Server cluster. In the HTTP Port field, type the portnumber of the front-end HTTP dispatcher.

(Optional) Click Use Secure Sockets Layer (SSL) for HTTPcommunication. In the HTTP Port field, type the HTTP dispatcherport number on which secure HTTP (HTTPS) has previously beenconfigured.

e. In the Database Management System Selection page, choose Useexisting database management system installation.

f. In the Database Connection page, specify the metadata repository tierconnection and database information.



14. After installation, configure automatic client reroute to enable WebSphereApplication Server to reconnect to the DB2 standby server.

See “Configuring automatic client reroute” on page 342.

15. To cause WebSphere Application Server to communicate with the DB2cluster instead of a single node, run the WebSphere Application Serveradministrative console to specify an alternate database address and port.Then restart the cluster.

See “Specifying the alternate database address and port for IBM WebSphereApplication Server” on page 342.

16. To communicate the cluster configuration to the front-end Web server,run the WebSphere Application Server administrative console to generate theplugin-cfg.xml file, and then manually copy it to each Web server. Thenrestart the Web server.

If you are using IBM HTTP Server, you can automatically propagate the fileto your Web servers by using the WebSphere Application Serveradministrative console.



4. Installing and configuring the engine tier

Set up directories and accounts. Then install and configure the engine tier.

Table 126. Engine tier tasks


1. Create an administrator account for the InfoSphere Information Serverengine. Log in to the account to activate the password.


2. For non-English locales, make sure that the locale and encoding are setcorrectly. The installation program uses the locale and encoding informationof the computer to determine whether it can provide language support.

See “Setting the locale for the target computer” on page 157.


1. From the is-suite directory on the installation media, run the followingcommand to start the installation program:

./setup -verbose


3. In the installation program, accept all defaults, except:

v In the Tier Selection page, choose Engine only.

v In the IBM InfoSphere Information Server Location page, specify theURL of the front-end HTTP dispatcher for the WebSphere ApplicationServer cluster. In the Port field, type the port number of the front-endHTTP dispatcher. Enter the InfoSphere Information Serveradministrator account name and password.

(Optional) Click Use Secure Sockets Layer (SSL) for HTTPcommunication. In the Port field, type the HTTP dispatcher portnumber on which secure HTTP (HTTPS) has previously beenconfigured.



4. Configure the ODBC Data Source Name by using drivers ininstall_home/Server/branded_odbc as described in the documentation inthat directory.

Also see “Configuring ODBC access (Linux, UNIX)” on page 247.

5. For mixed locale clients, ensure that IBM InfoSphere DataStage, IBMInfoSphere QualityStage, and IBM InfoSphere Information Analyzer usershave the correct settings specified for globalization.

See “Ensuring that InfoSphere DataStage users have the correct localizationsettings (Linux, UNIX)” on page 246.

6. Review the system requirements to choose a supported C++ compiler forjob development, and install it in its default location.

See “Installing a C++ compiler for job development” on page 159.

5. Installing and configuring the client tier

On each computer where you need the client programs, run the InfoSphereInformation Server installation program, and then configure ODBC drivers.


Table 127. Client tier tasks

Task Document your information here


1. Double-click the setup icon to start the installation program. The programwindows display in your default Web browser.

2. In the installation program, accept all defaults, except in the Tier Selectionpage, choose Client only.Note: If you are using the client-only installation media, the TierSelection page does not display. The program installs the client tier only.



2. Configure the ODBC Data Source Name by using drivers ininstall_home\ODBCDrivers as described in the documentation in thatdirectory.

6. Completing the installation

After you install the tiers, configure users, security, connectivity, and productmodules.

Table 128. Postinstallation tasks for all tiers


1. Set up firewall exceptions for client-side executable files.

See Chapter 15, “Firewall exceptions for client-side executable files(Windows),” on page 231.

2. Optional: Configure Secure Sockets Layer (SSL):

v Enable SSL for inbound RMI/IIOP. When you install InfoSphereInformation Server, SSL for inbound RMI/IIOP communications isdisabled by default.

v If the installation program did not configure HTTPS for a tier computerduring InfoSphere Information Server installation, manually configureHTTPS for that tier computer.

To allow clients to communicate with the server by using HTTPS, youmust manually configure HTTPS on each client tier computer.

See Chapter 16, “Enablement of Secure Sockets Layer (SSL),” on page 233.

3. Change InfoSphere Information Server to use a Lightweight DirectoryAccess Protocol (LDAP) user registry.


4. Create users and groups by using the LDAP user registry utilities.


5. Map credentials between the LDAP user registry and the local operatingsystem user registry on the computer where the InfoSphere InformationServer engine is installed.





Table 128. Postinstallation tasks for all tiers (continued)


7. Assign project roles to users.


8. Configure IBM InfoSphere Information Analyzer, IBM InfoSphere BusinessGlossary, IBM InfoSphere Metadata Workbench, and IBM InfoSphereFastTrack (if you installed any of these product modules).

See Chapter 18, “Configuring product modules in the suite,” on page 245.

9. Add additional WebSphere Application Server cluster members andmanaged nodes.


10. Optional: Run the IBM Support Assistant Lite for InfoSphere InformationServer tool to verify the installation.

See “Installation verification and troubleshooting” on page 197.


Product accessibility

You can get information about the accessibility status of IBM products.

The IBM InfoSphere Information Server product modules and user interfaces arenot fully accessible. The installation program installs the following productmodules and components:v IBM InfoSphere Business Glossaryv IBM InfoSphere Business Glossary Anywherev IBM InfoSphere DataStagev IBM InfoSphere FastTrackv IBM InfoSphere Information Analyzerv IBM InfoSphere Information Services Directorv IBM InfoSphere Metadata Workbenchv IBM InfoSphere QualityStage

For information about the accessibility status of IBM products, see the IBM productaccessibility information at http://www.ibm.com/able/product_accessibility/index.html.

Accessible documentation

Accessible documentation for InfoSphere Information Server products is providedin an information center. The information center presents the documentation inXHTML 1.0 format, which is viewable in most Web browsers. XHTML allows youto set display preferences in your browser. It also allows you to use screen readersand other assistive technologies to access the documentation.

IBM and accessibility

See the IBM Human Ability and Accessibility Center for more information aboutthe commitment that IBM has to accessibility.


http://www.ibm.com/able/product_accessibility/index.html

http://www.ibm.com/able/product_accessibility/index.html

http://www.ibm.com/able


Accessing product documentation

Documentation is provided in a variety of locations and formats, including in helpthat is opened directly from the product client interfaces, in a suite-wideinformation center, and in PDF file books.

The information center is installed as a common service with IBM InfoSphereInformation Server. The information center contains help for most of the productinterfaces, as well as complete documentation for all the product modules in thesuite. You can open the information center from the installed product or from aWeb browser.

Accessing the information center

You can use the following methods to open the installed information center.v Click the Help link in the upper right of the client interface.

Note: From IBM InfoSphere FastTrack and IBM InfoSphere Information ServerManager, the main Help item opens a local help system. Choose Help > OpenInfo Center to open the full suite information center.

v Press the F1 key. The F1 key typically opens the topic that describes the currentcontext of the client interface.

Note: The F1 key does not work in Web clients.v Use a Web browser to access the installed information center even when you are

not logged in to the product. Enter the following address in a Web browser:http://host_name:port_number/infocenter/topic/com.ibm.swg.im.iis.productization.iisinfsv.home.doc/ic-homepage.html. Thehost_name is the name of the services tier computer where the informationcenter is installed, and port_number is the port number for InfoSphereInformation Server. The default port number is 9080. For example, on aMicrosoft® Windows® Server computer named iisdocs2, the Web address is inthe following format: http://iisdocs2:9080/infocenter/topic/com.ibm.swg.im.iis.productization.iisinfsv.nav.doc/dochome/iisinfsrv_home.html.

A subset of the information center is also available on the IBM Web site andperiodically refreshed at http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r5/index.jsp.

Obtaining PDF and hardcopy documentationv PDF file books are available through the InfoSphere Information Server software

installer and the distribution media. A subset of the PDF file books is alsoavailable online and periodically refreshed at www.ibm.com/support/docview.wss?rs=14&uid=swg27016910.

v You can also order IBM publications in hardcopy format online or through yourlocal IBM representative. To order publications online, go to the IBMPublications Center at http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss.


http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r5/index.jsp

http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r5/index.jsp



http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss

http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss

Providing feedback about the documentation

You can send your comments about documentation in the following ways:v Online reader comment form: www.ibm.com/software/data/rcf/v E-mail: [email protected]


http://www.ibm.com/software/data/rcf/

Reading command-line syntax

This documentation uses special characters to define the command-line syntax.

The following special characters define the command-line syntax:

[ ] Identifies an optional argument. Arguments that are not enclosed inbrackets are required.

... Indicates that you can specify multiple values for the previous argument.

| Indicates mutually exclusive information. You can use the argument to theleft of the separator or the argument to the right of the separator. Youcannot use both arguments in a single use of the command.

{ } Delimits a set of mutually exclusive arguments when one of the argumentsis required. If the arguments are optional, they are enclosed in brackets ([]).

Note:

v The maximum number of characters in an argument is 256.v Enclose argument values that have embedded spaces with either single or

double quotation marks.

For example:

wsetsrc[-S server] [-l label] [-n name] source

The source argument is the only required argument for the wsetsrc command. Thebrackets around the other arguments indicate that these arguments are optional.

wlsac [-l | -f format] [key... ] profile

In this example, the -l and -f format arguments are mutually exclusive andoptional. The profile argument is required. The key argument is optional. Theellipsis (...) that follows the key argument indicates that you can specify multiplekey names.

wrb -import {rule_pack | rule_set}...

In this example, the rule_pack and rule_set arguments are mutually exclusive, butone of the arguments must be specified. Also, the ellipsis marks (...) indicate thatyou can specify multiple rule packs or rule sets.



Links to non-IBM Web sites

This information center may provide links or references to non-IBM Web sites andresources.

IBM makes no representations, warranties, or other commitments whatsoeverabout any non-IBM Web sites or third-party resources (including any Lenovo Website) that may be referenced, accessible from, or linked to any IBM site. A link to anon-IBM Web site does not mean that IBM endorses the content or use of suchWeb site or its owner. In addition, IBM is not a party to or responsible for anytransactions you may enter into with third parties, even if you learn of such parties(or use a link to such parties) from an IBM site. Accordingly, you acknowledge andagree that IBM is not responsible for the availability of such external sites orresources, and is not responsible or liable for any content, services, products orother materials on or available from those sites or resources.

When you access a non-IBM Web site, even one that may contain the IBM-logo,please understand that it is independent from IBM, and that IBM does not controlthe content on that Web site. It is up to you to take precautions to protect yourselffrom viruses, worms, trojan horses, and other potentially destructive programs,and to protect your information as you deem appropriate.



Notices and trademarks

This information was developed for products and services offered in the U.S.A.

Notices

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Web


sites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM CorporationJ46A/G4555 Bailey AvenueSan Jose, CA 95141-1003 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment to


IBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. The sampleprograms are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

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

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

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

Trademarks

IBM, the IBM logo, and ibm.com are trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product andservice names might be trademarks of IBM or other companies. A current list ofIBM trademarks is available on the Web at www.ibm.com/legal/copytrade.shtml.

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

Adobe is a registered trademark of Adobe Systems Incorporated in the UnitedStates, and/or other countries.

IT Infrastructure Library is a registered trademark of the Central Computer andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of the Officeof Government Commerce, and is registered in the U.S. Patent and TrademarkOffice

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in theUnited States, other countries, or both and is used under license therefrom.

Notices and trademarks 477

http://www.ibm.com/legal/copytrade.shtml

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in theUnited States, other countries, or both.

The United States Postal Service owns the following trademarks: CASS, CASSCertified, DPV, LACSLink, ZIP, ZIP + 4, ZIP Code, Post Office, Postal Service, USPSand United States Postal Service. IBM Corporation is a non-exclusive DPV andLACSLink licensee of the United States Postal Service.

Other company, product or service names may be trademarks or service marks ofothers.


Contacting IBM

You can contact IBM for customer support, software services, product information,and general information. You also can provide feedback to IBM about productsand documentation.

The following table lists resources for customer support, software services, training,and product and solutions information.

Table 129. IBM resources

Resource Description and location

IBM Support Portal You can customize support information bychoosing the products and the topics thatinterest you at www.ibm.com/support/entry/portal/Software/Information_Management/InfoSphere_Information_Server

Software services You can find information about software, IT,and business consulting services, on thesolutions site at www.ibm.com/businesssolutions/

My IBM You can manage links to IBM Web sites andinformation that meet your specific technicalsupport needs by creating an account on theMy IBM site at www.ibm.com/account/

Training and certification You can learn about technical training andeducation services designed for individuals,companies, and public organizations toacquire, maintain, and optimize their ITskills at http://www.ibm.com/software/sw-training/

IBM representatives You can contact an IBM representative tolearn about solutions atwww.ibm.com/connect/ibm/us/en/

Providing feedback

The following table describes how to provide feedback to IBM about products andproduct documentation.

Table 130. Providing feedback to IBM

Type of feedback Action

Product feedback You can provide general product feedbackthrough the Consumability Survey atwww.ibm.com/software/data/info/consumability-survey


http://www.ibm.com/support/entry/portal/Software/Information_Management/InfoSphere_Information_Server




http://www.ibm.com/businesssolutions/

http://www.ibm.com/businesssolutions/

http://www.ibm.com/account/

http://www.ibm.com/software/sw-training/

http://www.ibm.com/software/sw-training/

http://www.ibm.com/connect/ibm/us/en/

http://www.ibm.com/software/data/info/consumability-survey/

http://www.ibm.com/software/data/info/consumability-survey/

Table 130. Providing feedback to IBM (continued)

Type of feedback Action

Documentation feedback To comment on the information center, clickthe Feedback link on the top right side ofany topic in the information center. You canalso send comments about PDF file books,the information center, or any otherdocumentation in the following ways:

v Online reader comment form:www.ibm.com/software/data/rcf/

v E-mail: [email protected]


http://www.ibm.com/software/data/rcf/

Index

Special characters/3GB switch

removing from boot.ini file 281/etc/magic file

editing 275/PAE switch

adding to boot.ini file 281.ds files

data set descriptor files 275.zip files

installation log files 393

Numerics32-bit systems 6664-bit systems 66

Aaccounts, user 142active-passive configuration

configuration example (MSCS) 301,315

configuration overview (Linux,UNIX) 299

configuration overview(Windows) 313

creating users and user groups (MSCSexample) 319

creating users and user groups(System Automation forMultiPlatforms example) 309

defining and starting resource group(System Automation forMultiplatforms example) 306

high availability control scripts 320installing high availability software

(System Automation forMultiplatforms example) 304

installing InfoSphere InformationServer in cluster (MSCSexample) 319

installing InfoSphere InformationServer in cluster (SystemAutomation for Multiplatformsexample) 309

preparing server hardware (MSCSexample) 303, 317

road map for installation 93scenarios 51setting up high availability control

scripts (MSCS example) 319setting up network (MSCS

example) 303, 317setting up resource agent scripts


setting up the cluster (MSCSexample) 317

active-passive configuration (continued)setting up virtual IP address (MSCS

example) 318setting up virtual IP address (System

Automation for Multiplatformsexample) 305

testing (MSCS example) 319testing (System Automation for

Multiplatforms example) 311analysis database

creating in DB2 for z/OSinstallation 151

creating in existing DB2 instance byusing installation program 148

creating in existing DB2 instance byusing scripts 150

creating in Microsoft SQL Serverdatabase system 152

creating in Oracle databasesystem 152

analysis databasesdetermining how to create 63sizing 65topologies 19, 62

application serverplanning 66removing profiles 378, 380troubleshooting 408, 409, 411

APT_COMPILEOPTenvironment variable 269

APT_LINKOPTenvironment variable 269

architectureengine 7installation 15services 10

ASB agents 7automatic client reroute

configuring for a DB2 databasecluster 342

configuring for HADR setup 348

Bbacking up

planning 57primary to standby in HADR

setup 350bind

DB2 package 250boot.ini file

adding /PAE switch 281removing /3GB switch 281

buildop componentscompilers 159

CC++ compilers

environment variables 269

C++ compilers (continued)installing 159

caching proxies 41capacity planning 57character encodings

supported 158checklists

separate engine tier 453WebSphere Application Server cluster

and IBM DB2 cluster 459client

firewall exceptions 231client for Eclipse 221client tier

described 6target computer preparation

overview 129cluster members

resolving connection problems afterremoving 420

clustersplanning 15WebSphere Application Server 33

COBOL copybook filesinstalling 225

code pages 158command prompt

installing from 186running software removal program

from 375command-line syntax

conventions 471commands

syntax 471component installer

described 7components

described 5compute nodes 53conductor nodes 53config.ini 216configuring

InfoSphere Information Server 231connections

maximum number 280connectivity

DB2 282planning 133testing ODBC drivers 251

Connector access services agent 7customer support

contacting 479

Ddata collection and analysis 197data source names

creating 253specifying 249

databaseMatch Designer database 161


database systemdetermining how to install 63supported 62

DB2 database clusteringconfiguration overview 337configuring automatic client

reroute 342creating a cluster 340creating the metadata repository

database 340creating users and groups 341heartbeat 338installing DB2 database system 340installing HA software 339overview 43preparing servers, file system, and

storage 338running installation program 341specifying alternate database address

and port 342verifying 345

DB2 database systemconfiguring 283configuring InfoSphere

DataStage 282DB2 for z/OS database system

analysis database 151metadata repository 151

DB2 installationwarnings 398

DB2 setup programrunning 282

DB2DBDFT environment variableconfiguring 283

DB2INSTANCE environment variableconfiguring 283

db2nodes.cfg fileconfiguring 283

deploymentsinstallation topologies 15

diagnostic tools 197directories, planning 67domain connections

troubleshooting 408DS_CONNECT 251dsenv file

sample entries 248DSNs

creating 253

EEAR deployment

warnings during 397Eclipse client 221encoded slashes

allowing 415encodings

supported 158engine tier

example scenario with isolatedengine 88

overview 7target computer preparation

overview 129topology example 17

Enterprise stage jobsgranting user privileges 282

environment variablesMicrosoft Visual Studio

compilers 269parallel engine 267setting 267setting for InfoSphere DataStage 248

EXCEPTION_POLICY 188

Ffailover 299file systems, planning 67firewall

clustering 42exceptions for client programs 231

Fix Central 131fix packs 131, 213front-end dispatcher

modifying 331front-end HTTP server

configuring HTTPS 155front-end load balancer

installing 329front-end Web server

alternative, front-end loadbalancer 328

clustering 37installing 328

GGCC 269genkey 193globalization (NLS)

configuring 246supported character encodings 158

GLTABSZ parameter 252graphical mode

configuring the browser 179, 369installation program overview 180restarting with a response file 184,

373software removal program

overview 369starting installation program in 180starting software removal program

in 370grids

configuring 53, 55planning 15

HHA software

installing 339hardware requirements 3health checkers 197heap size

increasing 278high availability

active-passive configurationexample 301, 315

high availability (continued)active-passive configuration scripts


active-passive configuration testing(MSCS example) 319

active-passive configuration testing(System Automation forMultiplatforms example) 311

configuration overview 27DB2 options 42design considerations 49, 297failover 299installing management software


redundancy 49required configuration 331setting up network (MSCS

example) 303, 317using control scripts (MSCS

example) 319high availability clustered configuration

road map for installation 105high availability control scripts

overview 320using (MSCS example) 319using (System Automation for

Multiplatforms example) 310high availability disaster recovery

(HADR)configuring automatic client

reroute 348configuring primary server 348configuring standby server 350creating the database 347creating users and groups 348installing DB2 database system 45,

347preparing servers and storage 346running installation program 348setting up metadata repository

in 345specifying alternate database address

and port 351starting 353validation 355

HTTP port 289HTTPS

example scenario 88https.conf 234, 240

IIBM DB2 database system

creating databases in existing instanceby using scripts 150

determining how to install 63preinstallation 147supported 62using existing instance for metadata

repository and analysisdatabase 148

IBM MetaBrokers and bridgesplanning 6

individual modulesremoving 364


information analysisplanning 65

Informix XPSconfiguring access 286

InfoSphere Blueprint Directorinstalling 228

InfoSphere Business Glossaryconfiguring 258

InfoSphere Business Glossary Anywhereinstalling and configuring a

client 219preparing for installation 215

InfoSphere Business Glossary Client forEclipse 221

InfoSphere DataStageconfiguring 245configuring globalization (NLS) 246configuring on DB2 database

servers 282installing z/OS components 225testing the installation 254

InfoSphere DataStage plug-insmonitoring installation 196

InfoSphere FastTrackconfiguring 259

InfoSphere Information Analyzeragent 7configuring 257database, analysis 65

InfoSphere Information Serverinstalling 168, 173, 175preparing to install 177removing 362, 364, 366, 368, 378, 380,

383, 386shutting down tasks and applications

before removing 361SSL for inbound RMI/IIOP,

disable 233SSL for inbound RMI/IIOP,

enable 233uninstalling 362, 364, 366, 378, 380upgrading 233

InfoSphere Information Server enginetuning 252

InfoSphere Information Server installationprogram

running 330InfoSphere Information Server Web

consoledescribed 10

InfoSphere Information Services Directoragent 7testing installation 256

InfoSphere Metadata Servertroubleshooting startup 409, 411

InfoSphere Metadata Workbenchconfiguring 258

InfoSphere QualityStageconfiguring 245configuring globalization (NLS) 246testing the installation 254

installationadditional product modules 122CDs 131InfoSphere Blueprint Director 228kernel parameter configuration 137log files 393

installation (continued)monitoring overview 194planning 1process overview 1sample road map: high availability

active-passive configuration 93sample road map: high availability

clustered configuration 105sample road map: installation with no

high availability 79scenario with basic client-server

topology 84scenario with clustered metadata

repository tier and services tier 114scenario with isolated engine tier 88scenario with parallel engine

configuration 88scenario with two-server

active-passive high availabilitytopology 99

strategy overview 59temporary files 393topologies 15troubleshooting permissions 403user privileges 406verification 197

installation checklistsseparate engine tier 453WebSphere Application Server cluster

and IBM DB2 cluster 459installation logs

monitoring 194installation program 167

graphical mode 180Microsoft Windows security

notifications 180running for DB2 database clustered

configuration 341running for HADR configuration 348sample scenarios 198, 201, 204, 207silent mode 186, 375starting in graphical mode 180

installation softwareobtaining 131

installingC++ compilers 159command prompt (silent) 186fix packs 213InfoSphere Information Server 168,

173, 175preparation steps 177

investigation reportsWebSphere Application Server 253

IP sprayer topology 40, 329ISALite 197ISInstall*.log 194, 196ITAG installations 7, 22IWAV0003E 397

JJava Virtual Machine (JVM)

troubleshooting 417

Kkernel parameters

modifying 137setting 270

Llanguage 157legal notices 475LIBPATH environment variable

configuring 283library path environment variables

InfoSphere DataStage libraries 248load balancers

introduction 39locale 157log files

installation 393WebSphere Application Server 394

log.txt 195logical tiers 5login

troubleshooting 417LOGTO 251lssam 345

Mmainframe components

installing 225Mainframe jobs

installing runtime libraries 226mainframes

running jobs 227maintenance

planning 57massively parallel processing

configurations 53configuring a node (Linux and

UNIX) 261configuring a node (Windows) 265copying components 265

Match Designer databaseconfiguring 253database requirements 161determining how to create 63locations 21planning 161supported topologies 62

MAXRLOCK parameter 252maxuproc parameter

setting 270memory

increasing swap area 281setting de-commit threshold 278setting for parallel jobs 271

metadata repositorychanging host name and port 292overview 12

metadata repository databasecreating for HADR configuration 347creating in DB2 for z/OS

installation 151creating in existing DB2 instance by

using installation program 148

Index 483

metadata repository database (continued)creating in existing DB2 instance by

using scripts 150creating in Microsoft SQL Server

database system 152creating in Oracle database

system 152creating within DB2 database

cluster 340determining how to create 63supported topologies 62

metadata repository tiertarget computer preparation

overview 127metadata server

troubleshooting startup 409, 411MFILES parameter 252Microsoft Cluster service (MSCS)

configuration example 315creating users and user groups 319installing InfoSphere Information

Server in cluster 319setting up network 317setting up the cluster 317setting up virtual IP address 318testing the configuration 319

Microsoft SQL Server database systemcreating analysis database in 152creating metadata repository database

in 152determining how to install 63supported 62

Microsoft Visual Studio compilersenvironment variables 269

Microsoft Windows Cluster service(MSCS)

setting up network 303Microsoft Windows Server 2003

setting up high availability controlscripts (MSCS example) 319

MKS Toolkit 194installation errors 424

monitoringInfoSphere DataStage plug-in

installation 196installation logs 194PX operators installation 196WebSphere Application Server ear

deployment 196WebSphere Application Server

installation 195monitoring installation

overview 194MPP 264multi-client manager 6

Nnaming conventions

projects 78NAS (network attached storage) 55national language support

supported character encodings 158network attached storage (NAS) 55networks

planning 133

non-IBM Web siteslinks to 473

OODBC

data source bind 250vendor drivers 250

ODBC data sourcesconfiguring access 247configuring access (Linux,

UNIX) 247configuring access (Windows) 251

ODBC driverstesting connectivity 251

odbc.ini 249Oracle database system

configuring 284creating analysis database in 152creating metadata repository database

in 152determining how to install 63high availability options 47supported 62

Oracle Enterprise stagejob privileges 284

Oracle parallel servergranting access 284

Oracle RACcreating database by using

scripts 358establishing communication with

WebSphere Application Server 358high availability 47node names 358requirements 357running installation program 358setting up metadata repository

in 357orchserver accounts

creating 286

PPage Not Found errors

troubleshooting 415page tables

auto-tuning 277paged pools

auto-tuning 276paging space

on HP-UX 273on IBM AIX 272on Linux 274on Solaris 273setting 272

parallel engineC++ compilers 159changing swap area size 281configuring for Windows 275configuring heap size 278configuring maximum

connections 280configuring maximum port

number 280connecting to Teradata databases 285

parallel engine (continued)copying components 264data set descriptor files 275editing boot.ini file 281enabling auto-tuning for paged pool

size 276enabling auto-tuning for system page

size 277environment variables 267example scenario 88monitoring system resources 7remote shell command 261running on multiple computers 261running rsh without a password 263setting paging space 272setting paging space (HP-UX) 273setting paging space (IBM AIX) 272setting paging space (Linux) 274setting paging space (Solaris) 273setting threshold for de-committing

memory 278using ssh 261

parallel jobsconfiguring 270setting the maximum memory 271user privileges 264

parallel processingconfiguring a node (Linux and

UNIX) 261configuring a node (Windows) 265installing components

(Windows) 265massively parallel processing (MPP)

systems 53overview 53symmetric multiprocessing (SMP)

systems 53Passport Advantage 131passwords

in response files 191, 193installation 142naming restrictions 145, 451

permissionsdirectory and user 403

planningcapacity 57client tier 6clusters 15connectivity 133directories 67engine tier 7file systems 67grids 15IDs 142installation 1Match Designer database 161metadata repository tier 12naming, projects 78networks 133ports 133services tier 10tier computers 127topologies 15users 142WebSphere Application Server 66

portschanging 291


ports (continued)configuring for HADR 348maximum number 280planning 133

processing nodeLinux, UNIX 261Windows 265

productupdates 213

product accessibilityaccessibility 467

product documentationaccessing 469

profilesremoving (Linux, UNIX) 380removing (Windows) 378

project naming 78PX operators

monitoring installation 196

RRAID 57redundancy 297registered-servers.xml

modifying to configure HTTPS 234modifying to switch back to

HTTP 240remote shell command

configuring 263removing

command prompt (silent) 375InfoSphere Information Server 368

requirementssystem 3

Resource Trackermonitoring system resources 7

response files 186creating 191encrypting information in 193graphical mode 184, 373Linux and UNIX parameters 429passwords 191samples 191silent mode (removing software) 375syntax 191Windows parameters 441

RLTABSZ parameter 252rsh command

configuring 263parallel engine 261program location 263

runtime errorstroubleshooting 423

runtime librariesinstalling for z/OS jobs 225, 226

SSAN (storage area networks) 55, 57scripts

database creation 150, 152secure HTTP (HTTPS)

configuring for InfoSphereInformation Server 76

secure HTTP (HTTPS) (continued)configuring for WebSphere

Application Server 233configuring the front-end HTTP

server 155manually configuring components

for 234switching back to HTTP 240

secure shell programconfiguring 261

Secure Sockets Layer (SSL)configuring for InfoSphere

Information Server 76security

configuring 243encrypting information in response

files 193server engine

starting and stopping 287server parameters

configuring all clients 216global configuration 216

services tiertarget computer preparation

overview 128troubleshooting 413

setup command syntax 189silent installation 186

Linux and UNIX parameters 429Windows parameters 441

silent modedescribed 186specifying error handling 188starting installation program in 186starting software removal program

in 375uninstalling in 375

single points of failure 297software removal

graphical mode overview 369Microsoft Windows security

notifications 370overview 361silent mode 375starting in graphical mode 370troubleshooting 423verifying 423

software requirements 3software services

contacting 479Solaris zones

file system requirements 67special characters

in command-line syntax 471SQA reports

WebSphere Application Server 253ssh command

parallel engine 261ssh program

configuring 261stage, Oracle Enterprise 284starting and stopping

InfoSphere Information Serverengine 287

storage area networks (SAN) 55, 57suite installation

monitoring 194

suite removalin Linux, UNIX 380in Windows 378manually in Linux, UNIX 386manually in Windows 383overview 362removing remaining files 378shutting down tasks and

applications 361support

customer 479swap area

increasing 281symmetric multiprocessing (SMP)

systems 53syntax

command-line 471sys.gv_$instance table

granting access 284sys.v_$cache table

granting access 284System Automation for Multiplatforms

configuration example 301system health checker 197system pages

auto-tuning 277system requirements 3SystemErr.log 394SystemOut.log 196, 394

TT30FILES parameter 252Teradata database program

installing the Teradata Tools andUtilities 285

Teradata database systemcreating users 286

Teradata databasessetting up connectivity 285

Teradata Tools and Utilitiesinstalling 285

tiersclient 6described 5engine 7product components contained in 5relationships among 12removing 366services 10

Tivoli System Automation forMultiplatforms

creating users and user groups 309defining and starting resource

group 306installing 304installing InfoSphere Information

Server in cluster 309setting up high availability control

scripts 310setting up virtual IP address 305testing the configuration 311

Tivoli System Automation forMultiplatforms (SA MP)

installing in DB2 databasecluster 339

Index 485

topologiesactive-passive 28analysis databases and 19client/server 16computer for each tier 18dedicated engine tier 17installation 15instance with multiple server

engines 26ITAG installations 22Match Designer database and 21multiple InfoSphere Information

Server instances 22scenarios 51, 52single computer 16

trace logsdisabling 415enabling 415

trademarkslist of 475

troubleshootingapplication server 408DB2 installation warnings 398domain connections 408enabling trace logs 415failed installations 401, 423ISALite tools 197JVM failure 417log files 393, 399login failure 417messages during installation 400Page Not Found errors 415report results, viewing 415runtime errors, uninstallation 423services tier 413software removal 423temporary files 393user accounts 397user privileges for installation 406VMware ESX 399WebSphere Application Server

administrative console 419WebSphere Application Server

installation with InfoSphereInformation Server 407

WebSphere Application Serverregistry 412

Uupdates 213updateSignerCerts 234UpdateSignerCerts tool

SSL, reenabling 237upgrading

monitoring overall suiteinstallation 194

user IDsnaming restrictions 145, 451

user limitsmodifying 137

user privilegesEnterprise stage jobs 282overview 406parallel jobs 264

usersplanning 142

uvconfig fileGLTABSZ parameter 252MAXRLOCK parameter 252MFILES parameter 252RLTABSZ parameter 252T30FILES parameter 252

uvodbc.config fileconfiguring 249

VVersion.xml

modifying to configure HTTPS 234modifying to switch back to

HTTP 240virtual IP address

setting up for active-passiveconfiguration (MSCS example) 318

setting up for active-passiveconfiguration (System Automationfor Multiplatforms example) 305

VMware ESX 399

WWeb sites

non-IBM 473WebSphere Application Server

changing HTTP port 289changing ports 291cluster members, creating 326cluster, creating 326cluster, implementing 33configuring HTTPS 233front-end load balancer, for

clustering 328front-end Web server, for

clustering 37, 328HTTP session persistence 326installation troubleshooting 407non-clustered installation 154planning 66planning for clusters 323removing profiles 378, 380reports 253SSL 233troubleshooting startup

(Windows) 409, 411WebSphere Application Server clustering

configurations, required 153, 324WebSphere Application Server clusters

load balancing 39running as a service 333

WebSphere Application Serverdeployment manager

administrative security 325custom profile, creating 326deployment manager profile,

creating 325node, federating 326Profile Management tool 325, 326

WebSphere Application Server eardeployment

monitoring 196WebSphere Application Server installation

monitoring 195

WebSphere Application Server NetworkDeployment

cluster environments, installing 153,324

clustering overview 31installation 153, 324replication domains 327

WebSphere Application Server, Version6.1

profile certificates, changedefault 239

SSL, enabling 233WebSphere Application Server, Version

7.0profile certificates, change

default 239SSL, enabling 233

Windows Registryediting for parallel engine 275increasing heap size 278MaxUserPort 280PagedPoolSize 276SystemPages 277TcpNumConnections 280

Zz/OS components

installing 225verifying the installation 227

z/OS jobsinstalling runtime libraries 226


��

Printed in USA

GC19-1048-08

Spineinformation:

IBM

Info

Sphe

reIn

form

atio

nSe

rver

Vers

ion

8Re

leas

e5

Plan

ning

,Ins

talla

tion,

and

Conf

igur

atio

nGu

ide

��

�