AIX Server

Version 8 Release 7
Plan, Install, and Configure IBM InfoSphere Information Server

on AIX Operating Systems
GC19-3612-00
Version 8 Release 7
Plan, Install, and Configure IBM InfoSphere Information Server

on AIX Operating Systems
GC19-3612-00
Note Before using this information and the product that it supports, read the information in Notices and trademarks on page 325.
Edition notice This document includes information for a customized configuration of the architectures, operating systems, and product components that are supported by IBM InfoSphere Information Server. For information about all supported configurations, see the IBM InfoSphere Information Server Planning, Installation, And Configuration Guide (GC19-3471-00). Copyright IBM Corporation 2005, 2011. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Part 1. Planning to install IBM InfoSphere Information Server . . . . 1
Chapter 1. Tiers and components. . . . 3
Engine tier . . . Services tier . . Metadata repository Tier relationships . . . . . tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 5 7 8 High availability control scripts included with IBM InfoSphere Information Server . . . . . Installing the metadata repository database . . . Installing DB2 database software . . . . . . Setting up an existing installation of Oracle database software . . . . . . . . . . . Creating the IBM InfoSphere QualityStage Match Designer database . . . . . . . . Installing WebSphere Application Server software Installing WebSphere Application Server by using the installation program . . . . . . . Implementing a WebSphere Application Server cluster for InfoSphere Information Server . . . Setting up an existing non-clustered installation of WebSphere Application Server . . . . . . Setting the locale and character encoding for the engine tier target computer . . . . . . . . . Character encodings supported by IBM InfoSphere Information Server. . . . . . . 120 121 121 151 154 156 156 158 168 169 170
Chapter 2. Selecting your installation topologies . . . . . . . . . . . . . 11

Designing an installation topology . . . . . . Basic installation topologies . . . . . . . High availability topologies . . . . . . . Parallel processing and grid topologies . . . Capacity planning . . . . . . . . . . . Installation scenarios . . . . . . . . . . Scenario A: Basic client-server configuration . Scenario B: Isolated engine tier and parallel engine configuration . . . . . . . . . Scenario C: Two-server active-passive high availability configuration . . . . . . . . Scenario D: Clustered metadata repository tier and services tier configuration . . . . . . . . . . . . . 11 11 23 44 47 48 49
. 49 . 50 . 51
Part 2. Installing IBM InfoSphere Information Server software . . . . 173

Chapter 5. Preparing to install IBM InfoSphere Information Server . . . . 175
Obtaining IBM InfoSphere Information Server software . . . . . . . . . . . . . Configuring your browser . . . . . . . Installing InfoSphere Metadata Asset Manager bridges to import and export metadata . . . Preparing to run the installation program . . . . . . and . . . . 175 175 176 177
Chapter 3. Reviewing installation checklists . . . . . . . . . . . . . 55

Options for installing the database software . . Options for installing the application server software . . . . . . . . . . . . . . Directories that must be present on all tier computers before installation . . . . . . . Installation checklists . . . . . . . . . . Basic installation checklist . . . . . . . Basic isolated engine tier and parallel engine installation checklist . . . . . . . . . High availability (active-passive configuration) installation checklist . . . . . . . . . High availability (clustered configuration) installation checklist . . . . . . . . . . 55 . 57 . 58 . 59 . 59 . 65 . 72 . 78
Chapter 6. Installing IBM InfoSphere Information Server software . . . . . 179

Installing IBM InfoSphere Information Server by using the wizard (graphical mode) . . . . . Installation prerequisites check failed . . . Specifying tiers and product modules to install Installing the product. . . . . . . . . Installation program encounters an error . . Completing the installation process . . . . Installing IBM InfoSphere Information Server by using the response file (silent mode). . . . . Creating a response file . . . . . . . . Starting the installation program with a response file . . . . . . . . . . . . Installation program encounters an error . . Response files . . . . . . . . . . . Monitoring log files to monitor installation progress . . . . . . . . . . . . . . Monitoring the IBM InfoSphere Information Server installation . . . . . . . . . . Monitoring the IBM WebSphere Application Server installation . . . . . . . . . . . 179 . 181 182 . 187 . 189 . 190 . 190 . 191 . 194 . 196 . 197 . 208 . 208 . 209
Chapter 4. Preparing the tier computers 91

Reviewing system requirements and release notes 91 Checking prerequisites. . . . . . . . . . 91 Setting up the tier computers . . . . . . . . 92 Removing libicu libraries (AIX) . . . . . . . 92 Configuring your network . . . . . . . . 92 Processes used by InfoSphere Information Server 97 Modifying kernel parameters and user limits (AIX ) . . . . . . . . . . . . . . . 99 Setting up administrator and owner accounts 100 Creating a two-server active-passive high availability configuration . . . . . . . . . 105 Creating an active-passive configuration (AIX ) 105
Copyright IBM Corp. 2005, 2011
iii
Monitoring the IBM WebSphere Application Server enterprise archive file deployment . . . Monitoring IBM InfoSphere DataStage component installations . . . . . . . . . Verifying and testing the installation. . . . . . Installation verification and troubleshooting . . Testing the installation of IBM InfoSphere DataStage and IBM InfoSphere QualityStage . . Testing the IBM InfoSphere Information Services Director installation . . . . . . . . . .
210 210 211 211 212 214
Replacing WebSphere Application Server certificates . . . . . . . . . . . Switching from HTTPS back to HTTP . . Configuring security for IBM InfoSphere Information Server . . . . . . . . .
. . .
. 256 . 257 . 259
Chapter 10. Configuring a parallel processing environment. . . . . . . 261

Adding computers to share engine processing . . Configuring computers to be compute nodes for in an MPP system (AIX ) . . . . . . . . Distributing transform libraries to compute nodes . . . . . . . . . . . . . . . Setting up a C++ compiler . . . . . . . . . Setting up a compiler on IBM AIX . . . . . Setting environment variables for the parallel engine . . . . . . . . . . . . . . . . Environment variables for the parallel engine Configuring the parallel engine (AIX ) . . . . . Setting the maximum number of processes for parallel jobs (AIX) . . . . . . . . . . . Setting per-user kernel parameters for parallel jobs (AIX) . . . . . . . . . . . . . Setting the paging space for the parallel engine Updating the /etc/magic file . . . . . . . Configuring database connectivity in a parallel environment. . . . . . . . . . . . . . Configuring access to DB2 databases . . . . Configuring access to Oracle databases . . . . Configuring access to Teradata databases . . . Configuring access to Informix XPS databases 261 261 265 266 266 267 267 269 269 269 270 271 272 272 274 275 276
Chapter 7. Adding additional tiers or products to an installation . . . . . . 215

Adding product modules to an installation Adding additional tiers to an installation . . . . . . 215 . 217
Chapter 8. Removing IBM InfoSphere Information Server software . . . . . 219

Preparing to remove software . . . . . . . . Shutting down tasks and applications before removing software (service tier and engine tier) . Configuring your browser for software removal Removing IBM InfoSphere Information Server software by using the software removal program . Removing individual product modules . . . . Removing IBM InfoSphere Information Server by using the software removal program (graphical mode) . . . . . . . . . . . Removing IBM InfoSphere Information Server by using a response file (silent mode) . . . . . . Software removal program encounters an error . . Completing software removal . . . . . . . . Completing software removal (AIX ) . . . . Removing IBM InfoSphere Information Server software manually. . . . . . . . . . . . Manually removing IBM InfoSphere Information Server (AIX ) . . . . . . . . . . . . 219 220 221 221 222
224 227 229 229 229 232 232
Chapter 11. Configuring product modules in the suite . . . . . . . . 277

Configuring IBM InfoSphere DataStage and IBM InfoSphere QualityStage . . . . . . . . . . Ensuring that InfoSphere DataStage users have the correct localization settings (AIX ) . . . . Configuring ODBC access (AIX ) . . . . . . Configuring IBM InfoSphere QualityStage Match Designer . . . . . . . . . . . Setting up application servers to run investigation, SQA, or Match Statistics reports . Configuring IBM InfoSphere Information Analyzer Configuring IBM InfoSphere Business Glossary . . Stopping and starting the IBM InfoSphere Information Server server engine . . . . . . . 277 278 279 283 283 284 285 286
Part 3. Configuring the software after installation . . . . . . . . . 237

Chapter 9. Configuring IBM InfoSphere Information Server . . . . 239
Changing host names and ports . . . . . . . Changing the WebSphere Application Server HTTP port . . . . . . . . . . . . . Changing other WebSphere Application Server ports . . . . . . . . . . . . . . . Changing the metadata repository database host name and port . . . . . . . . . . . . Enabling Secure Sockets Layer (SSL). . . . . . Enabling SSL for inbound RMI/IIOP transport (stand-alone installation) . . . . . . . . Enabling SSL for inbound RMI/IIOP transport (cluster installation) . . . . . . . . . . Running UpdateSignerCerts after enabling SSL or changing SSL settings. . . . . . . . . Manually configuring InfoSphere Information Server components to use HTTPS . . . . . 239 239 241 242 248 250 251 252 254
Part 4. Troubleshooting installations . . . . . . . . . . . 287

Chapter 12. Log files . . . . . . . . 289
Installation log files . . . . . . . . . . . 289 Temporary files generated by installation program 289 IBM WebSphere Application Server system log files 290
Chapter 13. General installation problems . . . . . . . . . . . . . 293
iv
Plan, Install, and Configure IBM InfoSphere Information Server on AIX Operating Systems
"User credentials are not valid" error appears unexpectedly during installation . . . . . IWAV0003E warning in installation log file . Warnings occur during installation of DB2. . User creation errors appear in log files (AIX ) Installation process hangs when a web browser session is closed . . . . . . . . . . Fix pack version errors during IBM InfoSphere Information Server installation . . . . .
. . . . . .
. . . .
293 293 294 295
Enabling and disabling trace logging of the reporting engine . . . . . . . . . .
. 307
Chapter 17. Client and console problems . . . . . . . . . . . . . 309

Java Virtual Machine fails to load . . . . . . 309 Rich client login failure . . . . . . . . . . 309 Resolving problems logging in to the IBM WebSphere Application Server administrative console . . . . . . . . . . . . . . . 311 Connection problems after IBM WebSphere Application Server cluster members are removed . 312
. 295 . 296
Chapter 14. Authentication problems

Directory and user permissions . Confirming user privileges . . . . . . . . . . . . .
299
. 299 . 300
Chapter 15. Application server problems . . . . . . . . . . . . . 301

Resolving IBM WebSphere Application Server installation problems . . . . . . . . . . . Installation fails when the IBM WebSphere Application Server port is changed after installation . . . . . . . . . . . . . . Resolving connection problems . . . . . . . Unable to start IBM WebSphere Application Server after the user name changes or expires . . . . . Adding an IBM WebSphere Application Server administrator user to an internal user registry . . Repairing the WebSphere Application Server registry after switching to LDAP . . . . . . . Services tier performance . . . . . . . . . 301
Chapter 18. Removal problems . . . . 315

IBM InfoSphere Information Server installation fails repeatedly . . . . . . . . . . . . . 315
Part 5. Appendixes . . . . . . . . 317

Contacting IBM . . . . . . . . . . 319 321
302 302 303 304 305 306
Accessing product documentation
Product accessibility . . . . . . . . 323 Notices and trademarks . . . . . . . 325 Index . . . . . . . . . . . . . . . 329
Chapter 16. IBM InfoSphere Information Server reporting problems 307

Cannot view report result from InfoSphere Information Server console or InfoSphere Information Server Web console . . . . . . . 307
Contents
vi
Part 1. Planning to install IBM InfoSphere Information Server

Before you install IBM InfoSphere Information Server, review the system requirements, learn about tiers and components, design your topology, and determine your installation steps.
Chapter 1. Tiers and components

You install IBM InfoSphere Information Server product modules in logical tiers. A tier is a logical group of components within InfoSphere Information Server and the computers on which those components are installed. Each tier includes a subgroup of the components that make up the InfoSphere Information Server suite and product modules. The tiers provide services, job execution, and storage of metadata and other data for your product modules. InfoSphere Information Server has these tiers: Engine tier The logical group of components (the InfoSphere Information Server engine components, service agents, and so on) and the computer where those components are installed. The InfoSphere Information Server engine runs jobs and other tasks for product modules. Services tier The application server, common services, and product services for the suite and product modules and the computer where those components are installed. The services tier provides common services (such as metadata and logging) and services that are specific to certain product modules. On the services tier, IBM WebSphere Application Server hosts the services. The services tier also hosts InfoSphere Information Server applications that are Web-based. Metadata repository tier The metadata repository and, if installed, the IBM InfoSphere Information Analyzer analysis database and the computer where these components are installed. The metadata repository contains the shared metadata, data, and configuration information for InfoSphere Information Server product modules. The analysis database stores extended analysis data for InfoSphere Information Analyzer.
Engine tier
The engine tier consists of the logical group of engine components (the IBM InfoSphere Information Server engine components, service agents, and so on) and the computer where those components are installed. Several product modules require the engine tier for certain operations. You install the engine tier components as part of the installation process for these product modules. The following product modules require the engine tier: v v v v v v IBM InfoSphere DataStage IBM InfoSphere Information Analyzer IBM InfoSphere Information Services Director IBM InfoSphere Metadata Workbench IBM InfoSphere QualityStage IBM InfoSphere Information Server istool command line. The istool framework is installed on the engine tier and client tier. Commands for InfoSphere Information Analyzer and InfoSphere Metadata Workbench are installed on the engine tier only when those products are installed.
IBM InfoSphere FastTrack, IBM InfoSphere Business Glossary, and IBM InfoSphere Business Glossary Anywhere do not require an engine tier. AIX : 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 ITAG installation. The installation program installs the following engine components as part of each engine tier: InfoSphere Information Server engine Runs tasks or jobs such as discovery, analysis, cleansing, or transformation. The engine includes the server engine and parallel engine and other components that make up the runtime environment for InfoSphere Information Server and its product components. ASB agents Java processes that run in the background on each computer that hosts an InfoSphere Information Server engine tier. When a service that runs on the services tier receives a service request that requires processing by an engine tier component, the agents receive and convey the request. AIX : The agents run as daemons that are named ASBAgent. ASB agents include: Connector access services agent Conveys service requests between the ODBC driver components on the engine tier and the connector access services component on the services tier. InfoSphere Information Analyzer agent Conveys service requests between the engine components on the engine tier and the InfoSphere Information Analyzer services component on the services tier. InfoSphere Information Services Director agent Conveys service requests between the engine components on the engine tier and the InfoSphere Information Services Director services component on the services tier. Logging agent Logs events to the metadata repository. AIX : The agent runs as a daemon that is named LoggingAgent. ODBC drivers The installation program installs a set of ODBC drivers on the engine tier that works with InfoSphere Information Server components. These drivers provide connectivity to source and target data. Resource Tracker The installation program installs the Resource Tracker for parallel jobs with the engine components for InfoSphere DataStage and InfoSphere QualityStage. The Resource Tracker logs the processor, memory, and I/O usage on each computer that runs parallel jobs.
dsrpcd (DSRPC Service) Allows InfoSphere DataStage clients to connect to the server engine. AIX : This process runs as a daemon (dsrpcd). Job monitor A Java application (JobMonApp) that collects processing information from parallel engine jobs. The information is routed to the server controller process for the parallel engine job. The server controller process updates various files in the metadata repository with statistics such as the number of inputs and outputs, the external resources that are accessed, operator start time, and the number of rows processed. The following diagram shows the components that make up the engine tier. Items marked with asterisks (*) are only present in Microsoft Windows installations.
Engine tier
Server engine
Connectivity (ODBC drivers)
ASB agents Connector access services agent InfoSphere Information Analyzer agent InfoSphere Information Services Director agent
Parallel engine
*MKS Toolkit
DataStage Telnet Service
DataStage Engine Resource service
istool command line
Job monitor
DSRPC service
Resource Tracker
Logging agent
*IBM Metabrokers and bridges
Source and target data
Figure 1. Engine tier components
Note: InfoSphere Metadata Integration Bridges are installed only on the client tier, not on the engine tier.
Services tier
The services tier consists of the application server, common services for the suite, and product module-specific services and the computer where those components are installed. Some services are common to all product modules. Other services are specific to the product modules that you install. The services tier must have access to the metadata repository tier and the engine tier. An instance of IBM WebSphere Application Server hosts these services. The application server is included with the suite for supported operating systems.
Alternatively, you can use an existing instance of WebSphere Application Server, if the version is supported by InfoSphere Information Server. The following diagram shows the services that run on the application server on the services tier.
Services tier
Application server
Product module-specific services Connector access services IBM InfoSphere Information Analyzer services IBM InfoSphere Information Services Director services IBM InfoSphere FastTrack services IBM InfoSphere QualityStage services IBM InfoSphere DataStage services IBM InfoSphere Business Glossary services IBM InfoSphere Metadata Workbench services Common services Scheduling Logging Directory Security Reporting Core services Metadata services
Figure 2. Services tier services
Product module-specific services for IBM InfoSphere Information Analyzer, IBM InfoSphere Information Services Director, IBM InfoSphere FastTrack, IBM InfoSphere DataStage, IBM InfoSphere QualityStage, IBM InfoSphere Business Glossary, and IBM InfoSphere Metadata Workbench are included on the services tier. They also include connector access services that provide access to external data sources through the ODBC driver components and the connector access services agent on the engine tier. The common services include: Scheduling services These services plan and track activities such as logging, reporting, and suite component tasks such as data monitoring and trending. You can use the InfoSphere Information Server console and Web console to maintain the schedules. Within the consoles, you can define schedules, view their status, history, and forecast, and purge them from the system. For example, a report run and the analysis job within InfoSphere Information Analyzer are scheduled tasks. Logging services These services enable you to manage logs across all the InfoSphere Information Server suite components. You can view the logs and resolve problems by using the InfoSphere Information Server console and Web console. Logs are stored in the metadata repository. Each InfoSphere Information Server suite component defines relevant logging categories.
Directory services These services act as a central authority that can authenticate resources and manage identities and relationships among identities. You can base directories on the InfoSphere Information Server internal user registry. Alternatively, you can use external user registries such as the local operating system user registry, or Lightweight Directory Access Protocol (LDAP). Security services These services manage role-based authorization of users, access-control services, and encryption that complies with many privacy and security regulations. If the user registry internal to InfoSphere Information Server is used, administrators can use the InfoSphere Information Server console and Web console to add users, groups, and roles within InfoSphere Information Server. Reporting services These services manage runtime and administrative aspects of reporting for InfoSphere Information Server. You can create product module-specific reports for InfoSphere DataStage, InfoSphere QualityStage, and InfoSphere Information Analyzer. You can also create cross-product reports for logging, monitoring, scheduling, and security services. You can access, delete, and purge report results from an associated scheduled report execution. You can set up and run all reporting tasks from the InfoSphere Information Server Web console. Core services These services are low-level services such as service registration, life cycle management, binding services, and agent services. Metadata services These services implement the integrated metadata management within InfoSphere Information Server. Functions include repository management, persistence management, and model management. The following InfoSphere Information Server Web-based applications are installed as part of the services tier. v IBM InfoSphere Metadata Workbench v The IBM InfoSphere Information Server Web console. A browser shortcut to the IBM InfoSphere Information Server Web console is created during the InfoSphere Information Server installation. The Web console consists of administration and reporting tools, and the Information Services Catalog for InfoSphere Information Services Director, if installed. v IBM InfoSphere Information Server Manager client
Metadata repository tier

The metadata repository tier consists of the metadata repository database and, if installed, the IBM InfoSphere Information Analyzer database and the computer where these components are installed. The metadata repository tier includes the metadata repository for IBM InfoSphere Information Server. This database is a shared component that stores design-time, runtime, glossary, and other metadata for product modules in the InfoSphere Information Server suite.
If InfoSphere Information Analyzer is installed, the metadata repository also includes one or more analysis databases. The analysis databases are used by InfoSphere Information Analyzer when it runs analysis jobs. The services tier must have access to the metadata repository tier. When product modules store or retrieve metadata, services on the services tier connect to the metadata repository tier and manage the interaction between the databases and the product modules. For InfoSphere Information Analyzer, the engine tier and the client tier must also have direct access to the analysis databases. The following diagram shows the components that make up the metadata repository tier.
Metadata repository database
Information Analyzer analysis databases
Figure 3. Metadata repository tier components
Tier relationships
The tiers provide services, job execution, and storage of metadata and other data for the product modules that you install. The following diagram illustrates the tier relationships.
Client tier
Console
Engine tier ODBC drivers Engine

Product modulespecific services
Services tier
Common services
Data
Figure 4. Tier relationships
The tiers relate to one another in the following ways: v Relationships differ depending on which product modules you install. v Client programs on the client tier communicate primarily with the services tier. The IBM InfoSphere DataStage and QualityStage clients also communicate with the engine tier. v Various services within the services tier communicate with agents on the engine tier. v Metadata services on the services tier communicate with the metadata repository tier. v ODBC drivers on the engine tier communicate with external databases. v InfoSphere Metadata Integration Bridges on the client tier can import data from external sources. Some bridges can also export data. v With the IBM InfoSphere Information Analyzer product module, the engine tier communicates directly with the analysis databases on the metadata repository tier. The InfoSphere Information Analyzer client also communicates directly with the analysis databases.
10
Chapter 2. Selecting your installation topologies

A successful deployment of IBM InfoSphere Information Server must include a topology that meets the needs of your organization, such as performance, ease of maintenance, security, high availability, and scalability. Determining the optimal deployment is a complex task that requires a firm understanding of your requirements and the topology that you plan to implement. This information provides explanations, illustrations, scenarios, and checklists to help you design an ideal topology based on a set of available resources and a set of functional requirements (such as high availability and scalability). Each of these variables represents different dimensions of a topology, and a change in any of these dimensions can greatly affect the resulting topology. Therefore, identifying and quantifying these dimensions is important to remain within your constraints while still meeting requirements.
Designing an installation topology

The overall topology of an installation can range widely in complexity. Optimize the design of the topology to accommodate the product modules that you install and any requirements for high availability, performance and throughput, and user concurrency. IBM InfoSphere Information Server supports a variety of topolgies. In these topology descriptions, the term computers refers to separate physical servers, logical partitions (LPARs), or virtual machines.
Basic installation topologies

If you do not need a high availability solution and do not anticipate scaling the installation for higher capacity in the future, choose a basic topology.
Dedicated engine tier topology

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

You can host each tier on a separate computer. This topology provides each tier with dedicated computing resources. If you choose this topology, minimize network latency between all tiers. In particular, you must have a high-bandwidth connection between the services tier and the metadata repository tier. The services tier and the metadata repository tier must be on the same subnet. The following diagram illustrates this topology. Although the diagram shows only one client tier computer, you can include multiple client tier computers.
12
Computer A
Client tier
Network
Computer B
Computer C
Computer D
Services tier
Engine tier
Figure 6. Topology with a dedicated computer for each tier
Topology with separate instances of IBM InfoSphere Information Server

AIX : You can install more than one instance of InfoSphere Information Server on the same set of computers. The instances are isolated from one another, with separate engine tiers, services tiers, and metadata repository tiers. These tiers cannot be shared between instances. The instances can exist on the same computer in different installation directories or on different computers. The instances can be the same software version or different versions. If the instances are the same InfoSphere Information Server version, you can configure a single client tier instance to communicate with multiple InfoSphere Information Server instances. The following diagram shows a topology with two separate InfoSphere Information Server, Version 8.5 instances that are installed on two separate computers. A single client tier installation communicates with both instances.
13
Computer A
Client tier
Clients for Version 8.5
Network
InfoSphere Information Server instance
Computer B
Engine tier Services tier
Computer C
InfoSphere Information Server instance
Figure 7. Topology with separate instances on separate computers
If the instances are different versions, the client tier must contain clients for each version. The following diagram shows a topology with two separate InfoSphere Information Server instances that are installed on two separate computers. The instances are different versions. The client tier contains clients for both versions. The Multi-Client Manager is used to switch between one version of IBM InfoSphere DataStage to another version that is also installed on the client tier.
14
Computer A
Client tier
Multi-client manager
Clients for Version n Clients for Version 8.5
Network
InfoSphere Information Server, Version n
Computer B
Computer C
InfoSphere Information Server, Version 8.5
Figure 8. Topology with separate different version instances on separate computers
If the services tiers for more than one instance exist on the same computer, specify different ports for each services tier. The following diagram shows a topology where the services tiers and metadata repository tiers for two different InfoSphere Information Server version instances are installed on the same computer. Each services tier communicates with a separate engine tier installed on a separate computer.
15
Computer A
Client tier
Network
Computer B
Computer C
Engine tier
Metadata repository
Services tier
Computer D
Metadata repository
Services tier
Engine tier
Figure 9. Topology where services tiers share a common computer
To install more than one instance of the InfoSphere Information Server engine on the same computer, create an installation tag (ITAG). An ITAG must be exactly three hexidecimal digits. The ITAG value is used when assigning shared memory segments so that each installation creates its shared memory in different locations. To perform this installation, run the installation program multiple times to create multiple engine tier instances. During the installation, assign each instance a unique identification tag and port number. All projects and jobs associated with a server engine instance are assigned the tag for the server engine instance. Each engine tier instance must be registered to a different InfoSphere Information Server service instance. The following diagram shows a topology where the engine tiers for two InfoSphere Information Server instances are installed on the same computer. Each engine tier has an associated ITAG.
16
Computer A
Client tier
Network
Computer B
Computer C
Engine tier ITAG "X"
Metadata repository
Services tier
Metadata repository
Services tier
Engine tier ITAG "Y"
Figure 10. ITAG installation
Topology with multiple engine tiers

You can create an installation topology that includes more than one engine tier. In this topology, each engine tier includes the IBM InfoSphere Information Server engine, which includes the server engine, the parallel engine, and other components that make up the runtime environment for InfoSphere Information Server and its product components. You might choose this topology for project and resource management reasons. For example, you might dedicate one engine tier to IBM InfoSphere DataStage jobs and another engine tier to IBM InfoSphere Information Analyzer jobs. Or you might dedicate multiple engine tiers to separate sets of InfoSphere Information Analyzer jobs, each with its own analysis database. Each engine tier instance must exist on a separate computer. You cannot configure the services tier to communicate with multiple engine tiers that are installed on the same computer. The following diagram shows a topology with two engine tiers that are installed on separate computers. A single services tier instance communicates with both engine tiers.
17
Computer A
Client tier
Network
Computer B
Computer C
Computer D
Engine tier
Services tier
Engine tier
Figure 11. Topology with two engine tiers
Database topologies
You use the metadata repository to store imported metadata, project configurations, reports, and results for all components of IBM InfoSphere Information Server. The metadata repository is included as part of the metadata repository tier, which can include additional databases such as one or more analysis databases, the Match Designer database, or the operations database that supports the IBM InfoSphere DataStage Operations Console. Analysis databases Analysis databases store high-volume, detailed analysis results, such as column analysis, primary key analysis, and domain analysis. Each InfoSphere Information Analyzer project is associated with a specific analysis database. If you install InfoSphere Information Analyzer, you must provide the location for one or more analysis databases. After the installation, you can add additional databases by using the InfoSphere Information Server console. The analysis database might be used by a single InfoSphere Information Analyzer project, or it might be shared by multiple projects. For example, two InfoSphere Information Analyzer projects might use two different analysis databases, or they might share the same analysis database. Match Designer database The InfoSphere QualityStage Match Designer is a component of InfoSphere
18
QualityStage that is used to design and test match specifications. Match specifications consist of match passes that identify duplicate entities within one or more files. The InfoSphere Information Server installation program does not create the Match Designer results database. You can create the database before or after the installation, as long as the database is configured and accessible when you use the Match Designer. You can create the database on a computer where the client or engine tier is installed or on any computer that is accessible to both of these tiers. You must configure the database to receive the type of data that is processed in the Match Designer. For example, you must configure the database to receive double-byte data if the Match Designer processes Asian data. Operations database You use the IBM InfoSphere DataStage Operations Console to monitor jobs. You create the operations database when you are ready to use the console. You can locate an analysis database, the Match Designer database, and the metadata repository in the same database system installation as distinct databases. Alternatively, you can locate these databases and the metadata repository on different computers. The database system that you choose can be different from the database system for your other databases. For example, you can use an IBM DB2 database for the metadata repository and an Oracle database for the Match Designer database. If you are creating a database system installation for a database, determine which database system to use and where to locate the instance and the database. If you are configuring a database in an existing database system instance, the database must be accessible by the computers where the services tier and engine tiers are installed. The following diagram illustrates a three-computer topology where an analysis database and the metadata repository database are located in the same database server installation.
19
Computer A
Client tier
Network
Computer B
Services tier Metadata repository tier
Metadata repository database Information Analyzer analysis database
Computer C
Engine tier
Figure 12. Topology with analysis database and metadata repository database in the same database server installation
The following diagram illustrates a four-computer topology where an analysis database and the metadata repository database are located on different computers.
20
Computer A
Client tier
Network
Computer B
Services tier
Computer C
Computer D

Metadata repository database Information Analyzer analysis database
Engine tier
Figure 13. Topology with analysis database and metadata repository database on different computers
Analysis database sizing: An analysis database is a component that IBM InfoSphere Information Analyzer uses when it runs analysis jobs. The extended analysis information is stored in the analysis databases. The extended analysis information includes the high-volume, detailed analysis results, such as column analysis, primary key analysis, and domain analysis. Additionally, the metadata repository contains the information analysis projects that contain the analysis results. Before you create the analysis databases, review the quantity of data to be analyzed. This review helps you to determine an appropriate storage size, location, and configuration of the analysis databases. When you plan for the size of your databases, consider these factors that affect the size of each database: v v v v v Number of tables to be analyzed Number of columns in tables to be analyzed Number of unique records within these tables Number of char and varchar columns Types of analysis to be done
Unless you use sampled analysis, an analysis database might be larger than the combined size of all the analyzed data sources.
21
Match Designer database sizing: After you create the Match Designer database, use automatic storage management to allocate database space as needed. To estimate initial space requirements and plan for the appropriate hardware, you must make some assumptions about the type and volume of matching that plan to accomplish. Consider the following factors: v Estimated number of match specifications v Average number of match passes per match specification v Average number of input data records per match specification v Average number of bytes per input data record v Average number of input frequency records per match specification When you calculate the number of bytes in a Match Designer input record, assume that varchar columns contain maximum width values. Also, keep in mind that most Match Designer input records are preprocessed through an InfoSphere QualityStage Standardization Stage. This stage adds 500 bytes to a source record or 1000 bytes if the source record is double-byte. When calculating frequency record volume, consider whether the data values for the source columns that participate in your matches typically have high or low rates of duplication. For data that is highly unique, your frequency record count might be similar to your data record count. For data that has a high rate of duplication, your frequency record count might be significantly less than your data record count. Review the factors described in Table 2. Then use the factors in the following formula to estimate how many megabytes of space the Match Designer results database is likely to require. (number of match specifications x (match size + (match size x 10%) + frequency size) x replication factor) / 1,000,000
Table 1. Space requirement factors and calculations Factor Match specification count Description Match specifications define and test criteria for matching data. Match passes define the column-level matching criteria applied during a single pass through match specification input. Data records define the content and format of match specification input. Calculation Approximate number of match specifications you expect to retain in your database Average number of match passes per match specification (used in the Match Size calculation) Average number of input data records per match specification (used in the Match Size calculation)
Match pass count
Data record count
22
Table 1. Space requirement factors and calculations (continued) Factor Data record length Description Data records define the content and format of match specification input. When calculating data record length, assume sizing scenarios that require the most space. Match size (in bytes) Match size aggregates the match pass and data record count and length factors into the estimated space requirements for the data component of a single match specification. Calculation Average number of bytes per match specification input data record (used in the Match Size calculation)
(Match pass count) x (data record count) x (data record length)
Frequency record count
Average number of frequency Frequency records indicate how often a particular value records per match occurs in a particular column. specification For frequency record count, consider high or low rates of duplication for the data values in source columns.
Frequency size (in bytes)
Frequency size estimates the space requirement for the frequency component of a single match specification. Replication factors account for significant differences in space requirements of different match types: v Unduplicate matches take input from one source, then group and match the data. v One-to-one reference matches compare a record on the data source to a record on the reference source. v Many-to-one reference matches can match any reference source record with many data source records.
(Frequency record count per match) x 360
Replication factor
Select the replication factor for the match type you expect to run most often: v For unduplicate matches, use a factor of 1 v For one-to-one reference matches, use a factor of 2 v For many-to-one reference matches, use a factor of 5
High availability topologies

IBM provides different high availability solutions for each IBM InfoSphere Information Server tier. Increasing availability (implementing a high availability solution) refers to maximizing the percentage of time that the system services are operational. To increase availability, you implement topologies and technologies that introduce
23
redundancy. The aim is to reduce or eliminate the number of single points of failure. Single points of failure are elements whose failure causes critical aspects of the system to stop operating. IBM provides different high availability solutions for each InfoSphere Information Server tier. With each solution, you can design many different highly available configurations, from relatively simple setups to complex installations. The following table lists high availability solutions for each tier:
Table 2. Tiers and high availability solutions Tier Engine tier Solutions Active-passive topology managed by high availability cluster-management software, such as IBM Tivoli System Automation for Multiplatforms Either of the following solutions: v Active-passive topology managed by high availability cluster-management software such as Tivoli System Automation for Multiplatforms v IBM WebSphere Application Server clustering Metadata repository tier Any of the following solutions: v Active-passive topology managed by high availability cluster-management software such as Tivoli System Automation for Multiplatforms v IBM DB2 clustering v DB2 high-availability data recovery (HADR) v Oracle Real Application Clusters (RAC)
Services tier
In general, the higher the level of overall availability that you want to achieve, the more complex the system that you must design and maintain. High availability systems typically require more hardware. For these reasons, give careful consideration to the level of availability that you require within each software tier in the system. You might want a different level of availability within your development system than you have within your production system. To install a highly available topology, you must have a solid understanding of network technologies such as protocols, tiers, and devices. Successfully deploying highly available topologies, especially ones that include clustering, is a technically complex process that requires a high degree of technical expertise. The server and software topology that you choose is only part of a high availability solution. You must also introduce redundancy at a number of different levels to reduce or eliminate single points of failure. When determining which topology and implementation to choose, consider the following design factors.
Level of high availability

When considering your topology, evaluate the level of high availability that you require:
24
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 to intervene? v Consider how your needs might differ depending upon how the system is used, such as whether it is a development system, testing system, or production system. For example, how important is it that the development system or testing system is highly available? v Consider the level of high availability that you require for different software tiers. The tiers are used differently depending upon whether the system is used primarily for development or in production. The tiers are also used differently depending upon the product modules that you have installed. Important: A failure on one tier typically renders the entire system nonoperational until the problem is fixed or failover occurs.
Performance and throughput requirements

The amount of scalability that each high availability solution offers differs from solution to solution. When you are choosing a topology and architecture, consider how the system might need to scale to support greater performance and throughput requirements in the future. Other considerations include the configuration of your network, your electrical infrastructure, and your backup, restore, and disaster recovery contingencies. For examples of how the solutions differ, see the scenario comparisons. See Capacity planning on page 47 to analyze your performance, throughput, and storage needs.
Security requirements
Different topologies lend themselves to different security possibilities. Consider how you want to implement firewalls and other security precautions between the different tiers, between the computers in each tier, and between the system and external data sources and targets. These considerations are important for the services tier and the engine tier that must have fast communications paths with external systems. For more information about security, see the IBM WebSphere Application Server documentation: v For Version 7.0, go to the WebSphere Application Server information center and read Securing applications and their environment v For Version 8.0, go to the WebSphere Application Server information center and read Securing applications and their environment
Complexity factors
High availability and scalability add layers of complexity to the installation. Eliminating single points of failure requires implementation of complex redundant hardware and software components. When you design your system, consider the amount of complexity that your IT staff must support. Is there sufficient in-house expertise to support the system that
25
you design? If your high availability features fail, the amount of time you need to bring the system online again might negate any uptime gains that your features provide. 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 the high availability features on a staggered schedule until your entire system is in place. This approach also gives the group experience with changing the system and provides them with knowledge for future system scaling.
Maintainability factors
Consider the maintenance costs of the system that you design. Determine what aspects of maintenance to automate, and which aspects to leave in the hands of support personnel. High availability features can simplify system maintenance. For example, in a clustered system, you can take servers offline for certain updates without rendering the entire system nonoperational. In an organization where specific departments are responsible for different systems, consider isolating the tiers on separate computers so each department can "own" a tier. For example, in an organization where a group of database administrators is responsible for corporate databases, consider isolating the metadata repository tier on computers that are within their control.
Cost
Implementing high availability typically adds to the initial cost of the system. Extra hardware, software, training, and other costs make the initial outlay larger. However, the productivity gains that the highly available system provides might make up for these costs.
Active-passive topology
To create a basic level of availability for IBM InfoSphere Information Server, install it on a file system that is shared by two or more computers. The computers are clustered by using high availability (HA) software. In this topology, two computers share a storage area network (SAN). The metadata repository tier, engine tier, and services tier are all installed on the SAN. One of the computers (the active server) hosts the InfoSphere Information Server instance. The other computer (the passive server) is started, but does not run any tier software. A high availability software product such as IBM Tivoli System Automation for Multiplatforms is installed on both the active server and the passive server. The HA software maintains a heartbeat: a periodic signal that is sent from the active server to the passive server and that indicates that the active server is operational. The following diagram illustrates this topology. Although the diagram shows only one client tier computer, you can include multiple client tier computers.
26
Computer A
Client tier
Computer B
(Active)
Computer C
(Passive)
Engine tier
Services tier
Database instance HA management software HA management software
SAN
Engine tier (installed) Services tier (installed)
Database
Figure 14. Active-passive topology
If the active server fails, the heartbeat also fails. The HA software restarts all InfoSphere Information Server services on the passive server. This process is called a failover. The following diagram illustrates this process.
27
Computer A
Client tier
Computer B
(Inoperative)
Computer C
(Newly active)
Engine tier Heartbeat Signal (broken) HA management software
Services tier
Database instance HA management software
SAN
Database
Figure 15. Active-passive server cluster configuration with a failed computer
At installation time, you create a host name alias for the system. This information is associated with the active server. All client programs connect to the system by using this address or host name. If the active server fails, the information is automatically reassociated with the passive server, so client programs do not need to connect to a different address. However, a failover is not apparent to client users. If the active server fails, all InfoSphere Information Server services are unavailable until the failover is complete and the passive server is operational. The failover process can take several minutes. Also, any jobs that were running fail and must be restarted after the passive server has taken over. In this configuration, the HA software monitors the health only of the server hardware and operating-system-level processes. The software initiates a failover only if one of these elements fails. Other software monitors the health of individual InfoSphere Information Server processes, but does not trigger a failover if a process fails. Instead, the system administrator is notified. By using this design, a system administrator can correct the problem, instead of allowing the problem to be reproduced on the passive server. Some other variations of this topology are possible, for example:
28
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, if Computer B fails, Computer C also takes over the services tier and the metadata repository 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 C hosts the engine tier. Another computer (Computer D) serves as backup server for 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 your implementation, and have your IT department to trigger a failover manually when necessary.
Topology dimensions and analysis

The active-passive topology is appropriate for small- to medium-sized companies with few concurrent system users. The topology provides a basic level of high availability without incurring significant additional server hardware costs. This configuration is suitable mainly for systems that run scheduled production jobs. The types of activities involved in a development environment make it more likely that a failover would cause dynamic file corruption or synchronization problems. This topology is not scalable. You can add other passive servers if necessary. However, performance, throughput, and concurrency are not affected because at any specific time, only one instance of each tier component is running in the configuration. Among the small scale InfoSphere Information Server deployments, this topology is popular and rates high on the performance and high availability dimensions while considering the hardware, skills, and complexity dimensions.
Table 3. Analysis: Two-server, active-passive topology Consideration Level of high availability Advantages and disadvantages v A host failure causes all tiers to be restarted. v When a node fails, there might be up to a 10-minute outage. v If any component fails, there is the potential for job design loss (client disconnected). v Software failure might not cause a failover. Scalability v The topology is difficult to scale because adding nodes does not increase performance or throughput. v To increase engine performance, add parallel engine computer nodes. Security v Complexity is fairly low. v A security breach on the server might jeopardize the entire system. Complexity v Complexity is fairly low. v No IBM WebSphere Application Server or database clustering experience is required. v HA software might be difficult to implement. Maintainability Cost By using failover, you can take one server offline for maintenance, while the rest of the system remains operational. This topology requires minimal hardware and software.
29
Clustered topologies
To maximize the high availability capabilities of IBM InfoSphere Information Server, install it on a file system that is shared by eight or more computers in which all tiers are implemented within clusters. In this topology, all tiers are configured with the most advanced high availability solutions, and both application server clustering and metadata repository tier clustering are implemented. The cost in hardware is high because a minimum of eight computers are required: v Two computers for the engine tier, configured with the active-passive failover solution v Three or more computers for the services tier, configured as an IBM WebSphere Application Server Network Deployment cluster (the WebSphere Application Server Deployment Manager and managed nodes are deployed on dedicated computers) v One computer for the front-end dispatcher (typically a web server) that sends requests to the IBM WebSphere Application Server Network Deployment cluster v Two computers for the metadata repository tier that runs on IBM DB2 high availability disaster recovery (HADR) with the Automatic Client Reroute The following diagram illustrates this topology.
30
Client tier
Client workstations
HTTP clients
EJB clients
Backup load balancer
Load balancer
Web server 1
Web server 2
FIREWALL
Services tier
Analysis database
DB2 DB WebSphere Application Server Deployment Manager
Cluster
WebSphere Application Server Node 2
Engine tier
Active Computer
HA mgt sw

Passive Computer
HA mgt sw
Metadata Repository computer (standby)

HA mgt sw
Metadata Repository computer (active)

HA mgt sw DB2 DBMS
SAN
DB2 DBMS
DB2 DB
Figure 16. Fully clustered topology
Topology dimensions and analysis

You can adapt this topology as needed to meet available resources and specific requirements. For example, to reduce hardware cost, you can consolidate some of the tiers and components on fewer computers. You can also collocate some of the services tier cluster nodes with the DB2 HADR instances of the metadata repository tier or collocate the front-end web server with one of the Services tier nodes. Similarly, if performance and scalability at the services tier is more important than high availability, then you might consider configuring the metadata repository tier with the active-passive failover solution rather than with the DB2 HADR technology. Additionally, the engine tier and metadata repository tier can be consolidated on the same computers to mitigate the cost of two additional computers.
31
Table 4. Scenario analysis: Fully clustered topology Consideration Level of high availability Advantages and disadvantages v The failure of a node in the WebSphere Application Server cluster does not cause service interruption. However, a slight degradation of performance might occur. v The failure of a node in the metadata repository tier cluster causes minimal or no service interruption. v The failure of a node in the engine tier causes up to a 10-minute interruption in engine operation, while failover occurs and the other node takes over. However, activities that do not require the engine tier continue without interruption. Scalability v The topology is highly scalable. v The topology supports many concurrent users. v You can add nodes to the WebSphere Application Server cluster to improve the performance and throughput of the application server. v For metadata repository configurations within an Oracle Real Application Clusters (RAC) cluster, add nodes to improve the performance and throughput of the metadata repository. v To increase engine performance, add additional parallel engines. Security v The topology requires a complex security setup that includes multiple firewalls and other security considerations. v If the security of one node or tier is compromised, the entire system is not necessarily compromised. Complexity v The topology is highly complex. v You must know WebSphere Application Server clustering and either IBM DB2 clusters or Oracle RAC clusters. v The topology might require the implementation of high-availability cluster-management software, which might be difficult to implement. Maintainability v The maintenance of this topology is complex. v The topology is highly flexible because you can take a server offline for maintenance, and the rest of the system remains operational. v The isolation of each tier on one or more separate computers enables groups of users within the organization to be responsible for or use particular tiers. Cost The cost is high.
Application server clustering

An application server runs your J2EE applications and can be stand-alone or managed. You can cluster your application servers to run the same set of J2EE applications and participate in workload management. Clusters enable enterprise applications to scale beyond the amount of throughput capable of being achieved with a single application server. Clusters also enable enterprise applications to be highly available because requests are automatically routed to the running servers in the event of a failure. The servers that are members of a cluster can be on different host computers. In contrast, servers that are part of the same node must be located on the same host computer. A cell can include no clusters, one cluster, or multiple clusters. WebSphere Application Server clustered topology:
32
To provide high availability of the services tier, create a cluster of application servers across two or more computers. Deploy an instance of the services tier in each application server. When a member of the cluster fails, other cluster members continue to provide services. Components in other tiers communicate with the cluster, not directly with a specific application server in the cluster. As long as at least one member of the cluster is operational, there is no interruption 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 the system simultaneously with a reasonable level of system responsiveness. You can scale a clustered configuration in order to meet increased concurrency requirements. The following diagram shows a topology with a services tier where application server clustering is implemented across two computers. A third computer hosts the WebSphere Application Server Deployment Manager. In the diagram, the engine tier is still set up in an active-passive configuration. The metadata repository tier is located on a separate computer. This topology also includes a sophisticated front-end configuration that includes dual web servers and a load balancer. These systems are set up outside the firewall. HTTP clients such as the WebSphere Application Server web console access 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 IBM InfoSphere DataStage and QualityStage Designer client communicate directly with the WebSphere Application Server nodes. Important: IBM WebSphere Application Server Network Deployment does not support deployment of firewalls between components within a cell (for example, between the deployment manager and the nodes). Note: High availability configurations that include WebSphere Application Server clustering typically also include metadata repository clustering. The database cluster ensures that the metadata repository is not a single point of failure.
33
Client tier
Client workstations
HTTP clients
EJB clients
Load balancer
Web server 1
Web server 2
Firewall
Services tier
WebSphere Application Server Deployment Manager
Cluster WebSphere Application Server Node 2 WebSphere Application Server Node 1
Engine tier
Active Computer
HA mgt sw

Passive Computer
HA mgt sw
Metadata Repository computer

DBMS
SAN
Database
Figure 17. Topology with application server cluster
A highly available and scalable front-end configuration to an IBM WebSphere Application Server cluster: If you deploy a WebSphere Application Server cluster within your IBM InfoSphere Information Server implementation, you must provide a front-end configuration for the cluster. The front-end configuration can consist of any of the following components located upstream of the cluster: v A front-end web server v A load balancer v A load balancer upstream of the web servers (IP sprayer topology) To maximize security, deploy firewalls at various key points within the topology that you select. To improve delivery response, you can also deploy caching proxy servers upstream of the web servers and load balancers. Front-end web servers:
34
If you deploy an IBM WebSphere Application Server cluster within your IBM InfoSphere Information Server implementation, you can provide a front-end web server upstream of the cluster. InfoSphere Information Server supports IBM HTTP Server and Apache HTTP Server. These software products are not shipped with InfoSphere Information Server. A front-end web server manages servlet and JSP requests. The web server typically uses an internal workload management (WLM) plug-in to dispatch web requests to the appropriate cluster members and their containers. It performs the dispatches according to policies that are preconfigured in the WLM plug-in. The front-end web server increases performance and security because the web server provides a unique HTTP entry point to the cluster. To prevent single points of failure at the web server level, deploy a backup dedicated web server to take over in case the active one fails. The following diagram shows an InfoSphere Information Server cluster with a front-end web server. A backup web server is also deployed.
InfoSphere Information Server cell

Cluster
Node
Web container
Web server
WLM plug-in
Application server running InfoSphere Information Server services
Node
Web container
Backup Web server
Figure 18. Cluster with front-end web server
If you choose IBM HTTP Server, you can set up the Deployment Manager to manage configuration and administration of the web server. The web server can be defined either as a managed node or an unmanaged node. v If you want to use the Deployment Manager to manage web servers in the same manner as any other managed nodes in the cell, define the web servers as managed nodes. For example, you can use the Deployment Manager to start or stop IBM HTTP Server or to install the IBM HTTP Server plug-in configuration file that contains the workload management policies that are defined for the cluster. v If you deploy the web servers upstream of a firewall that protects the cluster members, define the web servers as unmanaged nodes. In this case, you can manage the web servers with the Deployment Manager by enabling the IBM HTTP Server Admin Process on the computer. The following diagram shows an IBM HTTP Server instance that is defined as a managed node. The Deployment Manager manages IBM HTTP Server through the
35
local node agent.

Node
Deployment manager Web container Application server running InfoSphere Information Server services
Node agent
Cluster
Node
Node agent
Node
IBM HTTP Server
plug-in Web container Application server running InfoSphere Information Server services
Node agent
Figure 19. IBM HTTP Server instance that is defined as a managed node
The following diagram shows an IBM HTTP Server instance that is defined as an unmanaged node on a stand-alone server. A firewall separates the server from the cell. The Deployment Manager manages the IBM HTTP Server instance by using the IBM HTTP Server Admin Process.
Stand-alone server

Node
Cluster
IBM HTTP Server Admin Process
Deployment manager
Node agent
Web container
Firewall
IBM HTTP Server

plug-in
Node agent
Web container
Node
Figure 20. IBM HTTP Server instance that is defined as an unmanaged node on a stand-alone server
If you use the Apache HTTP Server, you must define the instances as unmanaged nodes. You cannot manage them by using the Deployment Manager. For example, you must copy the web server plug-in configuration file to each web server manually.
36
Stand-alone server

Node
Cluster
Deployment manager
Node agent
Web container
Apache Web Server plug-in
Node agent
Web container
Node
Figure 21. Apache HTTP Server
Load balancing: If you deploy an IBM WebSphere Application Server cluster within your IBM InfoSphere Information Server implementation, you can provide a load balancer upstream of the cluster. InfoSphere Information Server supports many load balancer solutions manufactured by IBM and by other vendors. The following list highlights the advantages and disadvantages of a load balancer approach. Advantages of deploying a load balancer v Easier deployment because you do not have to set up a network of web servers and then configure the web server plug-ins. v More load balancing algorithm alternatives are available. Load balancers often offer more algorithms than the ones provided by web server plug-ins, including advanced load-based balancing strategies that monitor usage levels on individual computers. Disadvantages of deploying a load balancer v Additional configuration is required. You must perform additional configuration to maintain persistent connections between clients and servers (web server plug-ins handle persistent connection maintenance automatically). Also, you must re-configure the load balancer whenever the downstream cluster topology changes (for example, when a node is added or removed). v Load balancers do not serve static HTML. v Hardware-based load balancers typically cost more. To prevent single points of failure at the load balancer level, consider deploying a backup load balancer to take over in case the active one fails. The following diagram shows an InfoSphere Information Server cluster with a front-end load balancer. A backup load balancer is also deployed.
37

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

Cluster
Node
Server
Load balancer
Server
Web server
Node
Web server
Server
Server
Figure 23. IP sprayer topology
Caching proxies: To improve delivery response and reduce downstream traffic, you can also deploy caching proxies. If caching proxy functions are not embedded within your load balancer hardware, you can deploy caching proxy servers upstream of the web servers and load balancers. IBM InfoSphere Information Server supports any caching proxy that 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 sprayer configuration. A backup caching proxy server is also deployed.

Cluster
Node
Server
Caching proxy
Server
Load balancer
Server
Web server
Node
Server
Backup caching proxy
Server
Server
Web server
Figure 24. Caching proxy configuration
Firewalls: To secure access to your IBM InfoSphere Information Server cluster, deploy firewalls at various key points in the topology that you select.
39
For example, add a firewall in front of the caching proxies, load balancers, and web servers. Isolate them within a DMZ to deny direct access to internal components from clients that you do not trust. Alternatively, you can place a firewall between the DMZ and the cluster. You can also add a firewall between the services tier and the metadata repository database. Important: IBM WebSphere Application Server does not support the deployment of firewalls between components within a cell. For example, the application server does not support firewalls between nodes in a cell, or between nodes and the Deployment Manager in a cell. The following diagram shows an InfoSphere Information Server cluster behind a DMZ. A firewall is located between the DMZ and the outside world. A firewall is also located between the cluster and the DMZ. For maximum security, a firewall is also located between the cluster and the metadata repository database.
InfoSphere Information Server cell Node
DMZ
Firewall
Server
Load balancer
Server
Firewall Firewall Web server
Metadata repository
Node
Server
Server
Web server
Figure 25. Cluster with firewalls
If you deploy firewalls, make sure to open any ports through the firewalls that are used by InfoSphere Information Server.
Database clustering
To provide a high availability topology, you can create database clusters across computers. By clustering your databases, you combine the computing power of the servers that are involved to provide higher scalability, more combined computing power, or built-in redundancy that provides higher availability of your information. DB2 database clustering: IBM offers several high availability DB2 configurations. IBM InfoSphere Information Server supports these configurations: v DB2 clustering by using high availability clustering software v DB2 with high availability disaster recovery (HADR) In either configuration, you can use DB2 automatic client reroute to enable IBM InfoSphere Information Server processes to reconnect to a standby node when a failover occurs.
40
Database clustering To provide a high availability DB2 configuration, you can create a DB2 cluster across computers. In this configuration, the metadata repository database is shared between nodes in the cluster. If a failover occurs, another node in the cluster provides DB2 functionality. To provide high availability, set up your cluster in an active-passive configuration with a single active DB2 instance on one computer and one or more passive instances on the other computers. If the DB2 instance encounters a problem or fails, a passive instance can take over. To manage this configuration, you can choose between several high availability clustering 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 several minutes as the new instance acquires resources, repeats certain transactions, and undoes other transactions. To minimize interruption and manual intervention, configure DB2 automatic client reroute. This function causes other components in the IBM InfoSphere Information Server instance, such as IBM WebSphere Application Server, to automatically reconnect to the new DB2 instance. This configuration does not provide redundancy for the database itself. Instead, it provides high availability for database client processes and smooths the reconnection 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 metadata repository tier. In this case, HA cluster management software on the metadata repository computers monitors DB2 processes specific to DB2. The software also monitors the health of the computer hardware and the network.
41
Client tier
Client workstations
HTTP clients
EJB clients
Load balancer
Web server 1
Web server 2
Firewall
Services tier
Cluster
Engine tier
Active computer
HA mgt sw

Passive computer
HA mgt sw

HA mgt sw

HA mgt sw DB2 DBMS
SAN
DB2 DBMS
DB2 DB
Figure 26. Topology with a clustered metadata repository tier
High availability disaster recovery (HADR) To provide high availability at the DB2 database level, you can create a DB2 high availability disaster recovery (HADR) configuration. In this configuration, a complete, separate copy of the database is maintained on a standby node at a local or remote location. The primary DB2 database processes transactions. It uses internal HADR processes to replicate transaction logs to the standby node, where the logs are stored. A process at the standby node then replays the logged transactions directly to the standby database. The two copies are maintained in synchronization or near-synchronization with each other. DB2 processes normally access only the primary copy of the database. However, if the primary copy fails, an administrator triggers the standby copy to take over the transactional workload. You can set up automatic client reroute to make the failover behavior nearly transparent. If the primary copy becomes unavailable, automatic client reroute tries the connection again to the failed primary copy. If the reconnection fails, automatic client reroute determines whether the standby copy is available. If the server is available, automatic client reroute reroutes the application server connection to the standby copy. Pending transactions are rolled back and then reissued on the standby copy. Automatic client reroute can also be configured to reconnect to an alternate standby copy if the first standby copy is unavailable. Failover is quick (normally 10 seconds to 15 seconds if the servers are on the same LAN segment). If the unavailable database becomes available again, it is automatically reintegrated as the new standby database and is resynchronized. The following diagram shows an IBM InfoSphere Information Server implementation in which the metadata repository tier is set up in an HADR
42
configuration.
Client tier
Client workstations
HTTP clients
EJB clients
Backup load balancer Web server 1 Firewall
Load balancer Web server 2
Services tier
Engine tier
Active computer
HA mgt sw

Passive computer
HA mgt sw
Metadata Repository computer (HADR standby)

DB2 DBMS
Metadata Repository computer (HADR primary)

DB2 DBMS
Primary database
SAN
Secondary database
Transaction log records are copied to the standby server and replayed on standby database
Figure 27. HADR configuration
Oracle database clustering: If you use an Oracle database system to host the metadata repository database or the IBM InfoSphere Information Analyzer analysis database, you can increase the availability of the metadata repository tier by implementing Oracle Real Application Clusters (RAC). An Oracle RAC configuration consists of multiple computers, each of which runs an Oracle instance, which is made up of processes that provide access to stored data. Each Oracle instance has access to a common database file system across a high-speed network. If a computer or Oracle instance process fails, other Oracle instances continue to provide service. Oracle database cluster management software (Oracle Clusterware) monitors and manages the Oracle RAC configuration and tries to restart failed Oracle instances. Client processes access the Oracle RAC configuration in the same way that they access a single Oracle database instance. With Oracle RAC 11g, a virtual IP address is assigned to each server in the cluster. If a node in the cluster fails, the virtual IP address fails over to another node and client processes can automatically reconnect.
43
Nodes in an Oracle RAC cluster require a separate, private high-speed network for messaging between nodes. This network is called the interconnect. The following figure shows an IBM InfoSphere Information Server topology that includes Oracle RAC. The two Oracle RAC node computers share access to a database farm.
Client tier
Client workstations
HTTP clients
EJB clients
Backup load balancer Web server 1 Firewall
Load balancer Web server 2
Services tier
Engine tier
Active computer
HA mgt sw

Passive computer
HA mgt sw Oracle Real Application Clusters (RAC) cluster
SAN
Database farm
Figure 28. Topology with Oracle RAC configuration
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 Extended Distance Clusters configuration. In this configuration, nodes in the cluster are located in physically separated sites. To install InfoSphere Information Server in an Oracle RAC configuration, install to a single node in the configuration. Then perform additional steps to cause InfoSphere Information Server to operate with the complete Oracle RAC configuration.
Parallel processing and grid topologies

To maximize the IBM InfoSphere Information Server engine efficiency and throughput, create a parallel processing or grid topology.
44
In these topologies, the workload for each job is distributed across several processors. The processors can be located on the same computer or on different computers that are connected over a network. The parallel engine uses the processors and computers concurrently to complete each job. The parallel engine and the InfoSphere Information Server engine make up the engine tier. You can configure the InfoSphere Information Server parallel framework for grid computing processing. Install a supported resource manager to enable the dynamic assignment of available computer nodes (physical computers) at run time yo.
Parallel processing topologies

In a parallel processing topology, the workload for each job is distributed across several processors. In IBM InfoSphere DataStage, you design and run jobs to process data. Normally, a job extracts data from one or more data sources, transforms the data, and loads it into one or more new locations. In a parallel processing topology, the workload for each job is distributed across several processors on one or more computers, called compute nodes. Within InfoSphere DataStage, the user modifies a configuration file to define multiple processing nodes. These nodes work concurrently to complete each job quickly and efficiently. A conductor node computer orchestrates the work. Parallel processing environments are categorized as symmetric multiprocessing (SMP) or massively parallel processing (MPP) systems.
Symmetric multiprocessing (SMP) systems

In a symmetric multiprocessing (SMP) environment, multiple processors share other hardware resources. In the following diagram, multiple processors share the same memory and disk space, but use a single operating system.
Disk
CPU
CPU
CPU
CPU
Shared Memory
Figure 29. Symmetric multiprocessing (SMP) 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 shared resources in the system. To scale the system, you can increase the number of processors, add memory, or increase storage. The scalability strategy that you implement depends on how your job is limited within your current system.
45
Massively parallel processing (MPP) systems

In a massively parallel processing (MPP) system, many computers are physically housed in the same chassis, as shown in the following diagram:
Figure 30. Massively parallel processing (MPP) system
An MPP system is physically dispersed, as shown in the following diagram:
46
Network
Processing node
Figure 31. MPP system
In an MPP environment, performance is improved because no resources must be shared among physical computers. To scale the system, you can add computers and associated memory and disk resources. In an MPP system, a file system is commonly shared across the network. In this configuration, program files can be shared instead of installed on individual nodes in the system.
Capacity planning
You plan the use of disk, volume group, and file system resources to create an optimal operating environment for IBM InfoSphere Information Server. As part of capacity planning for your installation, size your file systems and databases to accommodate your anticipated needs. After the installation, continue monitoring the file systems to ensure that sufficient space is available. Before you change your computers, back up those computers where you plan to install InfoSphere Information Server. Attention: If the file system runs out of space, InfoSphere Information Server stops functioning correctly.
File systems
Plan for the following separate file systems: Temporary storage Directories for scratch data that is used during processing and later discarded.
47
Program code Program code directories for the InfoSphere Information Server installation directory, database server installation directory, and the IBM WebSphere Application Server installation directory. Storage directories Database storage directories for the metadata repository database, and for the IBM InfoSphere Information Analyzer databases and IBM InfoSphere QualityStage Match Designer database (if you are installing these product modules). Isolate each functional subgroup or components in its own separate file system to accommodate different performance and capacity characteristics and backup requirements. File systems need to be expandable without requiring destruction or recreation, if the operating system that you are installing on permits it.
RAID and SAN configurations

Performance of a job (for IBM InfoSphere DataStage, IBM InfoSphere QualityStage, and IBM InfoSphere Information Analyzer) depends on all components being optimized. For RAID (Redundant Array of Independent Disks) and SAN (system area network) configurations, maximum performance is a combination of maximum bandwidth (controllers and disk) and minimized contention. The following guidelines can assist in the configuration of RAID or SAN technologies: v Ensure that your database is optimally tuned. v Ensure that computers where you install the metadata repository tier and the services tier are on a high-speed network. v Minimize contention between temporary systems (scratch, buffer, and sort) and data file systems. For temporary storage, do not use a network file system (NFS). Consider using the local disk for temporary storage. v Minimize contention between the disks and controllers that are associated with InfoSphere Information Server file systems and other applications or servers. v Consider isolating multiple mount points to separate high-speed disk interconnects and controllers. v Consider the trade-off between the granularity of file systems and the underlying configuration in comparison to the available, unused storage. v Do not create overly complex device configurations. These configurations can be difficult to administer and might not offer noticeable performance improvement. v If possible, check your configuration with experts in hardware, storage, operating systems, and InfoSphere Information Server. v Systems with parallelism require different expertise than systems with engines that do not feature parallelism. The optimal disk configuration balances cost, complexity, ease of administration, and ultimate performance.
Installation scenarios
The following installation scenarios describe and illustrate how companies might implement different configurations of IBM InfoSphere Information Server based on the needs of their organization. Use these scenarios to better understand how you plan to use InfoSphere Information Server.
48
Scenario A: Basic client-server configuration

Scenario A is an installation on a single computer, plus client workstations. There are no provisions for high availability. This configuration can be used quite successfully for deployment systems. A small retail chain wants to integrate its forecasting, distribution, replenishment, and inventory management processes. As part of the integration, they want to migrate financial reporting data from several systems to a single system of record. They decide to create two separate IBM InfoSphere Information Server installations: a small development system where they build and test projects and jobs, and a larger production system (see Scenario B: Isolated engine tier and parallel engine configuration). For the development system, a simple topology can be used where a single server with a storage mechanism (Host1 in the following diagram) services five client workstations.
Client workstations
Client tier
Network
Host1
Figure 32. Scenario A configuration
Scenario B: Isolated engine tier and parallel engine configuration

Scenario B is an installation with a computer that is dedicated to the IBM InfoSphere Information Server engine. The retail chain that built the Scenario A development system also wants to build a larger production system. They are expecting a relatively high volume of job throughput. They decide to create a configuration in which the engine tier is built on a dedicated server (Host2 in the following diagram). To provide additional
49
capacity, they set up a separate computer (Host3) to serve as a parallel processing compute node. The metadata repository tier and services tier share a server (Host1). For higher security, HTTPS communication needs to be enabled between the servers and the client workstations.
Client workstations
Client tier
Network
Host1
Host2
Host3
Services tier
Engine tier
Parallel processing
Figure 33. Scenario B configuration
Scenario C: Two-server active-passive high availability configuration

Scenario C is a configuration that includes two computers that can fail over to one another in case of failure. A small industrial company has purchased IBM InfoSphere Information Server and plans to use IBM InfoSphere DataStage, IBM InfoSphere QualityStage, and IBM InfoSphere Information Analyzer for data integration. They expect to have three or four 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 to implement a two-server active-passive topology for this system. All components are 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 for maintenance purposes. While the failover is occurring, the system is nonoperational.
50
They decide to create two separate IBM InfoSphere Information Server installations: v A small development system where projects and jobs are built and tested. The configuration is identical to Scenario A: Basic client-server configuration on page 49. v A more highly available production system, using the two-server active-passive configuration with a storage mechanism. Several client workstations will access both systems. To increase processing throughput, the passive node will be used as a parallel engine compute node while the primary node is active. The following diagram illustrates this topology.
Client workstations
Client tier
Host1
(Active)
Host2
(Passive)
Engine tier
Services tier
Parallel processing
Database instance HA management software HA management software
SAN
Database
Figure 34. Scenario C configuration
Scenario D: Clustered metadata repository tier and services tier configuration

Scenario D is a configuration that includes IBM WebSphere Application Server clustering and IBM DB2 clustering for high availability.
51
A large company uses both IBM WebSphere Application Server Network Deployment (ND) and DB2 for other applications. They recently purchased IBM InfoSphere Information Server. They plan to use the full suite of components for future data integration projects. The company has existing WebSphere Application Server and IBM DB2 installations. They are each managed within different support groups within the company IT department. Each group understands how to provide high availability solutions for the component under their supervision. The large number of concurrent users requires a clustered WebSphere Application Server topology that permits almost no downtime. This topology also allows for future expansion to accommodate additional capacity. The WebSphere Application Server group plans to create a WebSphere Application Server cluster for InfoSphere Information Server. The DB2 group will provide clustering of the metadata repository database and IBM InfoSphere Information Analyzer database to minimize downtime. The engine tier will be configured in an active-passive server cluster topology. The cluster management software will be IBM Tivoli System Automation for Multiplatforms. To increase processing throughput, the passive node will be used as a parallel engine node while the primary node is active. For the servers, 64-bit Red Hat Enterprise Linux 5 Advanced Platform will be used on an AMD CPU or processor. For the clients, existing Microsoft Windows XP workstations will be used. The following diagram illustrates the configuration that they will build.
52
Client tier
Client workstations
HTTP clients
EJB clients
Load balancer
Web server 1
Web server 2
FIREWALL
Services tier
Analysis database
DB2 DB WebSphere Application Server Deployment Manager
Cluster
Engine tier
Active Computer
HA mgt sw

Passive Computer
HA mgt sw

HA mgt sw

HA mgt sw DB2 DBMS
SAN
DB2 DBMS
DB2 DB
Figure 35. Scenario D configuration
53
54
Chapter 3. Reviewing installation checklists

Determine the specific set of steps to take to install IBM InfoSphere Information Server within your topology.
Options for installing the database software

You must determine how you will install the database system for each database, and how you will create the databases within the database system. The procedure for setting up IBM InfoSphere Information Server databases differs depending upon the database system that you use and the location of the database system. To use a clustered database configuration for high availability, such as a DB2 cluster, DB2 high-availability disaster recovery (HADR) configuration, or Oracle Real Application Clusters (RAC), you must first install the database system and configure the cluster. Then, use the scripts on the InfoSphere Information Server installation media to create the databases within the instance. When you run the InfoSphere Information Server installation program, specify the database system for the installation. See Installing the metadata repository database on page 121 for more information about installing databases.
IBM DB2 databases

Configure the databases: Installing the DB2 database system by using the InfoSphere Information Server installation program Use the InfoSphere Information Server installation program to install DB2 9.7 on the target computer and create the database within it. DB2 9.7 is bundled with InfoSphere Information Server. Within the installation program, select the Metadata Repository tier installation option to install DB2 and create the databases. Preinstalling the DB2 database system Before you run the installation program, preinstall the DB2 database system (any supported version) on the target computer or another computer. Then, create the databases by using one of the following methods: v If the DB2 instance is located on the target computer, use the InfoSphere Information Server installation program to create the databases within the instance. Within the installation program, select the Metadata Repository tier installation option to create the databases. v If the DB2 instance is not located on the target computer, create the databases within the instance before running the InfoSphere Information Server installation program. To create the databases, use the scripts that are provided with the InfoSphere Information Server software. The following table summarizes the different installation options for IBM DB2 databases:
55
Table 5. Summary of database system installation and database creation options for IBM DB2 databases Configuration DB2, non-clustered configuration Database system installation options Database creation options Preinstall before you run the InfoSphere Information Server installation program. Use either of the following methods:
v Use the InfoSphere Information Server For DB2 9.7 only, you can use installation program. the InfoSphere Information Server installation program to v Use the scripts on the InfoSphere Information install. Server installation media. DB2, clustered configuration Preinstall, and then create the Use the scripts on the cluster. InfoSphere Information Server installation media.
DB2, high availability disaster Preinstall, and then create the Use either of the following recovery (HADR) HADR configuration. methods to create the configuration database on the primary node: v Use the InfoSphere Information Server installation program. v Use the scripts on the InfoSphere Information Server installation media. DB2 9.7, high availability disaster recovery (HADR) configuration Use either of the following methods: v Use InfoSphere Information Server installation program to install Use either of the following methods to create the database on the primary node: v Use the InfoSphere Information Server installation program.
v Preinstall before you run the InfoSphere Information v Use the scripts on the InfoSphere Information Server installation program Server installation media.
Other databases
Set up the databases by using one of the following methods: Preinstall the database system Create the databases within the database system before running the InfoSphere Information Server installation program. To create the databases, use scripts that are provided with the InfoSphere Information Server software. Use an existing database system Before you run the InfoSphere Information Server installation program, create the databases within the database system by using scripts that are provided with the InfoSphere Information Server installation media. In either case, you do not use the Metadata Repository tier option when you run the installation program.
56
The following table summarizes the different installation options for other supported databases:
Table 6. Summary of database system installation and database creation options for Oracle and Microsoft databases Configuration Oracle database system (any supported version), non-clustered configuration Oracle Real Application Clusters (RAC) cluster (any supported version) Microsoft SQL Server database system (any supported version), non-clustered configuration Database system installation options Database creation options Preinstall before you run the InfoSphere Information Server installation program. Use scripts on InfoSphere Information Server installation media.
Preinstall, and then create the Use the scripts on the RAC setup. InfoSphere Information Server installation media. Preinstall before you run the InfoSphere Information Server installation program. Use the scripts on the InfoSphere Information Server installation media.
Options for installing the application server software

As part of the services tier configuration, determine which version of IBM WebSphere Application Server to install and how to install it. The central component within the services tier is WebSphere Application Server. This application server hosts the common and product-specific services for IBM InfoSphere Information Server. For 64-bit platforms, WebSphere Application Server ND Version 7.0 and Version 8.0 are available in both 32-bit and 64-bit versions. Either version might be more appropriate as you plan for longer-term performance and number of users. WebSphere Application Server ND version Version 7.0 is bundled with InfoSphere Information Server. For 64-bit platforms, the bundled version is 64-bit. For 32-bit platforms, the bundled version is 32-bit. To set up WebSphere Application Server: v Use the InfoSphere Information Server installation program to install WebSphere Application Server ND Version 7.0 as part of the services tier installation. The installation program creates a server profile that is named InfoSphere and an application server instance that is named server1. This application server is licensed for use only with InfoSphere Information Server. v Preinstall WebSphere Application Server ND, Version 7.0 or Version 8.0. You can use an existing installation of Version 7.0, but Version 8.0 is supported as a preinstalled component only. If you use an existing installation, you must create the profiles manually. To set up a clustered WebSphere Application Server ND configuration for high availability and scalability, preinstall WebSphere Application Server ND. Configure the cluster, profiles, and front-end dispatcher before you install InfoSphere Information Server. See Implementing a WebSphere Application Server cluster for InfoSphere Information Server on page 158.
57
Directories that must be present on all tier computers before installation

The IBM InfoSphere Information Server installation program requires certain directories be present on all tier computers before you run it. The temporary directories will contain temporary files that are required by the installation program. The files are not needed after installation and can be removed safely. Temporary directories You do not have to back up temporary directories. The root user, the user who runs the installation program, and all other InfoSphere Information Server users must have read, write, and execute permissions to the temporary directories. Put the temporary directories on a file system that has high-speed read-write performance. The following table provides operating system-specific information about the temporary directories.
Table 7. Temporary directories: operating system-specific information Operating system AIX Default directory path /tmp /var/tmp Additional requirements None
Home directory for user IDs The home directory contains existing user IDs and (by default) the IDs that the installation program creates. The Administrator ID or the root user ID that performs the installation must be able to write to the home directory and all subdirectories. Regularly back up this directory. The following table provides operating system-specific information about the home directory.
Table 8. Home directory: operating system-specific information Operating system AIX Default directory path /home/user_name Additional requirements Owners must have at least 755 permissions for their directories and parent directories, and have read/write/execute access to all subdirectories. If the home directory is on a network file system (NFS), export the file system with the no_root_squash option enabled and the nosetuid option off.
58
Installation checklists
The following checklists include procedures for installing and configuring different implementations of IBM InfoSphere Information Server. Use these checklists to guide you through the installation process and to ensure that your environment is configured correctly.
Basic installation checklist

Use this checklist to complete a new installation of a configuration where there is no redundancy for high availability. Complete the following steps: 1. Plan and build your topology 2. Install and configure each tier 3. Perform postinstallation configuration tasks To complete these steps, use the task lists in the following sections.
Plan and build your topology

To plan and build your topology, follow the steps in the following task list.
Table 9. Topology planning and building tasks Description Review the system requirements. Learn about tiers and components. Design the topology of your installation. Determine whether to preinstall your database system. Determine whether to preinstall IBM WebSphere Application Server or preconfigure an existing installation of WebSphere Application Server. Build and test the hardware infrastructure. For more information Reviewing system requirements and release notes on page 91 Tiers and computers Designing an installation topology on page 11 Options for installing the database software on page 55 Options for installing the application server software on page 57 Record your information
Refer to the hardware documentation.
Prepare to install the software

To prepare your computers to install the product software, complete the steps in the following task list.
Table 10. Software planning tasks Description Obtain the InfoSphere Information Server software and any applicable fix packs. On all tier computers, verify name resolution, and open TCP ports for InfoSphere Information Server across any applicable firewalls. For more information Obtaining IBM InfoSphere Information Server software on page 175 Configuring your network on page 92 Record your information
59
Table 10. Software planning tasks (continued) Description AIX Update the kernel parameters and user limits on each computer. For more information Modifying kernel parameters and user limits Record your information
Install and configure each tier

For each tier, complete the computer preparation tasks. Then install IBM InfoSphere Information Server components, and perform postinstallation tasks. Install and configure the tiers in this order: v Metadata repository tier v Services tier v Engine tier v Client tier You can install more than one software tier on the same computer. In this case, you complete the planning and preparation tasks for the tiers on the computer. Then run the installation program only once for that computer, installing the software for the tiers. Then complete the postinstallation tasks for the tiers on the computer. For example, if the metadata repository tier and services tier components are installed on computer Host1, and the engine tier and client tier are each installed on 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, IBM InfoSphere Business Glossary, and IBM InfoSphere Business Glossary Anywhere do not require an engine tier. Metadata repository tier installation task list To configure the metadata repository tier, follow the steps in the following task list.
60
Table 11. Planning tasks: metadata repository tier Description For more information Record your information install
Setting up administrator and owner Create the following administration accounts on the metadata repository accounts on page 100 tier computer. Log in to each account to confirm that it functions properly: v Owner of the metadata repository v (If installing InfoSphere Information Analyzer) The owner of the analysis database v If installing the DB2 database system: All operating systems DB2 database administrator user AIX DB2 fenced user Installing the metadata repository database on page 121
If you decide to preinstall DB2 or another supported database system, install the database system now.
install
If you preinstalled DB2, configure the Configuring an existing installation install of DB2 database software by using databases within DB2 by using the installation program on page 122 scripts. Alternatively, configure the databases when you run the InfoSphere Information Server installation program. If you preinstalled another database system, configure the databases by using scripts.
61
Table 11. Planning tasks: metadata repository tier (continued) Description Run the InfoSphere Information Server installation program if necessary. For more information Run the InfoSphere Information Server installation program for this tier in either of the following situations: v To install the DB2 database system on the target computer and create the metadata repository and analysis databases within it. See Part 2, Installing IBM InfoSphere Information Server software, on page 173. v To create the metadata repository and analysis database within a local preinstalled supported DB2 database system instance. See Configuring an existing installation of DB2 database software by using the installation program on page 122. If you preinstall the DB2 database system or another database system and create the databases within it by using scripts that are provided with the InfoSphere Information Server software, do not run the installation program for this tier. Record your information install
Services tier installation task list To configure the services tier, follow the steps in the following task list.
Table 12. Installation tasks: services tier Description Preinstall WebSphere Application Server, if you decide not to use the InfoSphere Information Server installation program to install it. When creating a profile during the installation, make sure to disable administrative security. Preconfigure an existing WebSphere Application Server installation if necessary. Run the InfoSphere Information Server installation program. Setting up an existing non-clustered install installation of WebSphere Application Server on page 168 install Part 2, Installing IBM InfoSphere Information Server software, on page 173 For more information Installing WebSphere Application Server by using the installation program on page 156 Record your information install
Engine tier installation task list If your installation requires an engine tier, follow the steps in the following task list to plan and configure the tier.
62
Note: If you are creating a configuration with more than one server engine, repeat these steps for each server engine.
Table 13. Installation tasks: engine tier Description AIX For non-English locales, make sure that the locale and encoding are set correctly. The installation program uses the locale and encoding information of the computer to determine whether it can provide language support. Create an administrator account for the InfoSphere Information Server engine. Log in to the account to activate the password. Run the InfoSphere Information Server installation program. For more information Setting the locale and character encoding for the engine tier target computer on page 169 Record your information install
Setting up administrator and owner accounts on page 100
install
Part 2, Installing IBM InfoSphere install Information Server software, on page 173
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 14. Installation tasks: client tier Description Run the installation program. In the Tier Selection page, choose Client only. (Optional) Manually configure secure HTTP (HTTPS) for the client tier. For more information Record your information
Part 2, Installing IBM InfoSphere install Information Server software, on page 173 Manually configuring InfoSphere configure Information Server components to use HTTPS on page 254
Test the installation

After you install the software, complete the following tasks to test and validate your installation.
Table 15. Testing the installation tasks Description Test the IBM InfoSphere Information Services Director installation (if installed). For more information Testing the IBM InfoSphere Information Services Director installation on page 214 Record your information
Run the IBM Support Assistant Lite Installation verification and for InfoSphere Information Server tool troubleshooting on page 211 to verify the installation.
63
Perform postinstallation configuration tasks

After you run the InfoSphere Information Server installation program for each tier, perform these tasks:
Table 16. Postinstallation configuration tasks (all tiers) Description (Optional) Configure Secure Sockets Layer (SSL): v Enable SSL for inbound RMI/IIOP. When you install InfoSphere Information Server in an IBM WebSphere Application Server Network Deployment 7.0 or later environment, SSL for inbound RMI/IIOP communications is disabled by default. v If the installation program did not configure HTTPS for a tier computer during IBM InfoSphere Information Server installation, manually configure HTTPS for that tier computer. Configure security within InfoSphere Information Server: 1. Choose a user registry and configure it for InfoSphere Information Server. 2. Create users and groups in the user registry. 3. Assign security roles to users and groups. 4. Configure InfoSphere Information Server engine security. Map credentials if necessary. 5. Assign project roles if required by the installed suite components. Optionally, also: v Configure IBM WebSphere Application Server for non-root administration. v Configure InfoSphere Information Server agents for non-root administration. v Configure the Auditing service. Configuring security for IBM InfoSphere Information Server on page 259 For more information Enabling SSL for inbound RMI/IIOP transport (stand-alone installation) on page 250 Record your information
64
Table 16. Postinstallation configuration tasks (all tiers) (continued) Description Configure IBM InfoSphere DataStage and IBM InfoSphere QualityStage (if installed): 1. If you installed globalization support (NLS), ensure that IBM InfoSphere DataStage users have the correct settings specified for localization. 2. Configure access to ODBC data sources. 3. For systems that have large numbers of simultaneously connected users or large numbers of simultaneously running jobs, tune the server engine. Optionally, also: v Migrate jobs that you created in an earlier version of InfoSphere DataStage to the current version. v Configure the IBM InfoSphere QualityStage Match Designer. v Set up the application server to run SQA or investigation reports. v Test the installation. Configure IBM InfoSphere Information Analyzer (if installed). Configure IBM InfoSphere Business Glossary (if installed). Configuring IBM InfoSphere Information Analyzer on page 284 Configuring IBM InfoSphere Business Glossary on page 285 For more information Configuring IBM InfoSphere DataStage and IBM InfoSphere QualityStage on page 277 Record your information
Basic isolated engine tier and parallel engine installation checklist

Use this checklist to complete a new installation of a configuration in which the engine tier is built on a dedicated server with a separate computer to serve as a parallel processing compute node. Complete the following steps: 1. Plan and build your topology 2. Prepare to install the software 3. Install and configure the metadata repository tier and the services tier on one computer 4. Install and configure the engine tier on a separate computer 5. 6. 7. 8. Install and configure the client tier on each client workstation Test the installation Configure the parallel processing engine Perform postinstallation configuration tasks
To complete these steps, use the task lists in the following sections.
65

Table 17. Topology planning and building tasks Description Review the system requirements. Learn about tiers and components. Design the topology of your installation. Determine whether to preinstall your database system. Determine whether to preinstall IBM WebSphere Application Server or preconfigure an existing installation of WebSphere Application Server. Build and test the hardware infrastructure. For more information Reviewing system requirements and release notes on page 91 Tiers and computers Designing an installation topology on page 11 Options for installing the database software on page 55 Options for installing the application server software on page 57 Record your information
Refer to the hardware documentation.

Table 18. Software planning tasks Description Obtain the InfoSphere Information Server software and any applicable fix packs. On all tier computers, verify name resolution, and open TCP ports for InfoSphere Information Server across any applicable firewalls. AIX Update the kernel parameters and user limits on each computer. For more information Obtaining IBM InfoSphere Information Server software on page 175 Configuring your network on page 92 Record your information
Modifying kernel parameters and user limits
Install and configure the metadata repository tier, the services tier, and the client tier
For each tier, complete the computer preparation tasks. Then install IBM InfoSphere Information Server components, and perform postinstallation tasks. Install and configure the tiers in this order: v v v v v Metadata repository tier Services tier Engine tier Client tier Parallel processing engine
66
Complete the planning and preparation tasks for the metadata repository tier and services tier on a single computer. Then, run the installation program on that computer to install both of these tiers. You can then perform the planning, preparation, and installation tasks for the engine tier on a separate computer. Then complete the postinstallation tasks for the tiers on the computer. For example, if the metadata repository tier and services tier components are installed on computer Host1, the engine tier is installed on computer Host2, the client tier is installed on separate client computers, and the parallel processing engine is installed on Host3, complete the tasks in the following 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 each client computer. 6. Installation of client tier components on each client computer by using the installation program. 7. Parallel processing engine preparation tasks on computer Host 3. 8. Installation of parallel processing engine on Host 3 by using the installation program. Not all product modules require an engine tier. IBM InfoSphere FastTrack, IBM InfoSphere Business Glossary, and IBM InfoSphere Business Glossary Anywhere do not require an engine tier. Metadata repository tier installation task list Complete the steps in the following task list to prepare and install the metadata repository tier.
Table 19. Planning tasks: metadata repository tier Description For more information Record your information
Setting up administrator and owner Create the following administration accounts on the metadata repository accounts on page 100 tier computer. Log in to each account to confirm that it functions properly: v Owner of the metadata repository v (If installing InfoSphere Information Analyzer) The owner of the analysis database v If installing the DB2 database system: All operating systems DB2 database administrator user AIX DB2 fenced user Installing the metadata repository database on page 121
If you decide to preinstall DB2 or another supported database system, install the database system now.
67
Table 19. Planning tasks: metadata repository tier (continued) Description For more information Record your information
If you preinstalled DB2, configure the Configuring an existing installation databases within DB2 by using of DB2 database software by using scripts. Alternatively, configure the the installation program on page 122 databases when you run the InfoSphere Information Server installation program. If you preinstalled another database system, configure the databases by using scripts. Run the InfoSphere Information Server installation program if necessary. Run the InfoSphere Information Server installation program for this tier in either of the following situations: v To install the DB2 database system on the target computer and create the metadata repository and analysis databases within it. See Part 2, Installing IBM InfoSphere Information Server software, on page 173. v To create the metadata repository and analysis database within a local preinstalled supported DB2 database system instance. See Configuring an existing installation of DB2 database software by using the installation program on page 122. If you preinstall the DB2 database system or another database system and create the databases within it by using scripts that are provided with the InfoSphere Information Server software, do not run the installation program for this tier.
Services tier installation task list To configure the services tier, complete the steps in the following task list.
Table 20. Installation tasks: services tier Description Preinstall WebSphere Application Server, if you decide not to use the InfoSphere Information Server installation program to install it. When creating a profile during the installation, make sure to disable administrative security. Preconfigure an existing WebSphere Application Server installation if necessary. Setting up an existing non-clustered installation of WebSphere Application Server on page 168 For more information Installing WebSphere Application Server by using the installation program on page 156 Record your information
68
Table 20. Installation tasks: services tier (continued) Description Run the InfoSphere Information Server installation program. For more information Part 2, Installing IBM InfoSphere Information Server software, on page 173 Record your information
Install the engine tier on a separate computer

Complete the following task list to plan, configure, and install the engine tier. Do not create a parallel engine configuration yet. Parallel engine configuration is completed at the end of the installation procedure. Note: If you are creating a configuration with more than one server engine, repeat these steps for each server engine.
Table 21. Installation tasks: engine tier Description AIX For non-English locales, make sure that the locale and encoding are set correctly. The installation program uses the locale and encoding information of the computer to determine whether it can provide language support. Create an administrator account for the InfoSphere Information Server engine. Log in to the account to activate the password. Run the InfoSphere Information Server installation program. For more information Setting the locale and character encoding for the engine tier target computer on page 169 Record your information
Part 2, Installing IBM InfoSphere Information Server software, on page 173
Install the client tier on each client workstation

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 Description Run the installation program. In the Tier Selection page, choose Client only. (Optional) Manually configure secure HTTP (HTTPS) for the client tier. For more information Part 2, Installing IBM InfoSphere Information Server software, on page 173 Manually configuring InfoSphere Information Server components to use HTTPS on page 254 Record your information
69

Run the IBM Support Assistant Lite Installation verification and for InfoSphere Information Server tool troubleshooting on page 211 to verify the installation.
Configure the parallel processing engine

Configure the parallel processing engine for IBM InfoSphere DataStage and IBM InfoSphere QualityStage.
Table 24. Postinstallation configuration tasks (all tiers) Description v Add computers to share engine processing v Set up a C++ compiler v Set up environment variables for the parallel engine v Configure the parallel engine v Configure database connectivity for the parallel engine For more information Chapter 10, Configuring a parallel processing environment, on page 261 Record your information

Table 25. Postinstallation configuration tasks (all tiers) Description (Optional) Configure Secure Sockets Layer (SSL): v Enable SSL for inbound RMI/IIOP. When you install InfoSphere Information Server in an IBM WebSphere Application Server Network Deployment 7.0 or later environment, SSL for inbound RMI/IIOP communications is disabled by default. v If the installation program did not configure HTTPS for a tier computer during IBM InfoSphere Information Server installation, manually configure HTTPS for that tier computer. For more information Enabling SSL for inbound RMI/IIOP transport (stand-alone installation) on page 250 Record your information
70
Table 25. Postinstallation configuration tasks (all tiers) (continued) Description Configure security within InfoSphere Information Server: 1. Choose a user registry and configure it for InfoSphere Information Server. 2. Create users and groups in the user registry. 3. Assign security roles to users and groups. 4. Configure InfoSphere Information Server engine security. Map credentials if necessary. 5. Assign project roles if required by the installed suite components. Optionally, also: v Configure IBM WebSphere Application Server for non-root administration. v Configure InfoSphere Information Server agents for non-root administration. v Configure the Auditing service. Configure IBM InfoSphere DataStage and IBM InfoSphere QualityStage (if installed): 1. If you installed globalization support (NLS), ensure that IBM InfoSphere DataStage users have the correct settings specified for localization. 2. Configure access to ODBC data sources. 3. For systems that have large numbers of simultaneously connected users or large numbers of simultaneously running jobs, tune the server engine. Optionally, also: v Migrate jobs that you created in an earlier version of InfoSphere DataStage to the current version. v Configure the IBM InfoSphere QualityStage Match Designer. v Set up the application server to run SQA or investigation reports. v Test the installation. Configure IBM InfoSphere Information Analyzer (if installed). Configure IBM InfoSphere Business Glossary (if installed). Configuring IBM InfoSphere Information Analyzer on page 284 Configuring IBM InfoSphere Business Glossary on page 285 Configuring IBM InfoSphere DataStage and IBM InfoSphere QualityStage on page 277 For more information Configuring security for IBM InfoSphere Information Server on page 259 Record your information
71
High availability (active-passive configuration) installation checklist

Use this checklist to complete a new installation of a two-server active-passive configuration where all components can fail over from one server to the other. Complete the following steps: 1. Plan and build your topology 2. Prepare to install the software 3. Install and configure high availability cluster management software 4. Install and configure the metadata repository tier, services tier, and engine tier within the two-server configuration 5. Install the client tier 6. Test the installation 7. Perform postinstallation configuration tasks To complete these steps, use the task lists in the following sections.

Table 26. Topology planning and building tasks Description Review the system requirements. Learn about tiers and components. Learn about the topology of the active-passive high availability configuration. Determine whether to preinstall your database system. Determine whether to preinstall IBM WebSphere Application Server or preconfigure an existing installation of WebSphere Application Server. For more information Reviewing system requirements and release notes on page 91 Tiers and computers Active-passive topology on page 26 Record your information
Options for installing the database software on page 55 Options for installing the application server software on page 57

Table 27. Software planning tasks Description Configure the servers, the network, and the storage device. For more information AIX Setting up the servers, network, and storage (Tivoli System Automation for Multiplatforms example) on page 109 Record your information
Obtain the InfoSphere Information Server software and any applicable fix packs.
Obtaining IBM InfoSphere Information Server software on page 175
72
Table 27. Software planning tasks (continued) Description On both computers, verify name resolution, and open TCP ports for InfoSphere Information Server across any applicable firewalls. AIX Update the kernel parameters and user limits on both computers. For more information Configuring your network on page 92 Record your information
Modifying kernel parameters and user limits (AIX)
Preparing and installing the tiers

The servers will accommodate the metadata repository tier, services tier, and engine tier. For this reason, run the IBM InfoSphere Information Server installation program only once to install the software on the mass storage device. Then run the installation program on each client tier computer to install the client tier software. To manage the cluster and enable failover, install high availability software such as IBM Tivoli System Automation for Multiplatforms. InfoSphere Information Server metadata repository, services, and engine tier software installation task list To prepare your tier software for installing the product, follow the steps in the following task list.
Table 28. Preparation tasks: metadata repository, services, and engine tiers Description Acquire and install high availability cluster management software on both engine tier servers, and set up the cluster. For more information Refer to the documentation for your high availability cluster management software. For example configurations, see the following topics: AIX Installing the high availability software (Tivoli System Automation for Multiplatforms example) on page 110 Record your information
Set the service IP address.
Refer to the documentation for your high availability cluster management software. For example configurations, see the following topics: AIX Setting up the virtual IP address (Tivoli System Automation for Multiplatforms example) on page 111
AIX Define and start a resource group.
Refer to the documentation for your high availability cluster management software. See Defining and starting the resource group (Tivoli System Automation for Multiplatforms example) on page 112.
73
Table 28. Preparation tasks: metadata repository, services, and engine tiers (continued) Description AIX For non-English locales, make sure that the locale and encoding are set correctly. The installation program uses the locale and encoding information of the computer to determine whether it can provide language support. For more information Setting the locale and character encoding for the engine tier target computer (AIX) Record your information
Set up administrator and component Setting up administrator and owner owner accounts on the shared storage accounts on page 100 device. If you decide to preinstall DB2 or another supported database system, install the database system now. Installing the metadata repository database on page 121
If you preinstalled DB2, configure the Configuring an existing installation of DB2 database software by using databases within DB2 by using the installation program on page 122 scripts. Alternatively, configure the databases when you run the InfoSphere Information Server installation program. If you preinstalled another database system, configure the databases by using scripts. Installing WebSphere Application Preinstall WebSphere Application Server by using the installation Server Network Deployment on the program on page 156 shared storage device, if you decide not to use the InfoSphere Information Server installation program to install it. When creating a profile during the installation, make sure to disable administrative security. Preconfigure the IBM InfoSphere QualityStage Match Designer database. Creating the IBM InfoSphere QualityStage Match Designer database on page 154
74
Table 28. Preparation tasks: metadata repository, services, and engine tiers (continued) Description Run the installation program: For more information Record your information
For example configurations, see the following topics: v In the High Availability Server Cluster Configuration page, click AIX Installing IBM InfoSphere Server cluster configuration. In the Information Server in the Virtual host name field, enter the cluster (Tivoli System virtual host name that was created Automation for when the HA software was Multiplatforms example) on configured. page 115 v Whenever prompted for an installation directory, specify a path on the shared storage device. v (Optional) To configure HTTPS, when the installation program prompts you, click Use Secure Sockets Layer (SSL) for HTTP communication. In the Port field, type the HTTP dispatcher port number on which secure HTTP (HTTPS) has previously been configured. Set up the resource agent scripts. Go to the documentation for your high availability cluster management software. For example configurations, see the following topics: AIX Setting up the high availability control scripts (Tivoli System Automation for Multiplatforms example) on page 116
Test the high availability configuration.
Simulate active cluster node failures and network failures and observe the results. For an example based on Tivoli System Automation for Multiplatforms, see Testing the configuration (Tivoli System Automation for Multiplatforms example) on page 117.
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 29. Installation tasks: client tier Description Run the installation program. In the Tier Selection page, choose Client only. For more information Chapter 6, Installing IBM InfoSphere Information Server software, on page 179 Record your information
75
Table 29. Installation tasks: client tier (continued) Description (Optional) Manually configure secure HTTP (HTTPS) for the client tier. For more information Manually configuring InfoSphere Information Server components to use HTTPS on page 254 Record your information

Run the IBM Support Assistant Lite See Installation verification and for InfoSphere Information Server tool troubleshooting on page 211 to verify the installation. Test the engine tier failover function. Go to the documentation for your high availability cluster management software. For example configurations, see the following topics: AIX Testing the configuration (Tivoli System Automation for Multiplatforms example) on page 117

Table 31. Postinstallation configuration tasks (all tiers) Description (Optional) Configure Secure Sockets Layer (SSL): v Enable SSL for inbound RMI/IIOP. When you install InfoSphere Information Server in an IBM WebSphere Application Server Network Deployment 7.0 or later environment, SSL for inbound RMI/IIOP communications is disabled by default. v If the installation program did not configure HTTPS during IBM InfoSphere Information Server installation, manually configure HTTPS. For more information Enabling SSL for inbound RMI/IIOP transport (cluster installation) on page 251 Record your information
76
Table 31. Postinstallation configuration tasks (all tiers) (continued) Description Configure security within InfoSphere Information Server: 1. Choose a user registry and configure it for InfoSphere Information Server. 2. Create users and groups in the user registry. 3. Assign security roles to users and groups. 4. Configure InfoSphere Information Server engine security. Map credentials if necessary. 5. Assign project roles if required by the installed suite components. Optionally, also: v Configure IBM WebSphere Application Server for non-root administration. v Configure InfoSphere Information Server agents for non-root administration. v Configure the Auditing service. Configure IBM InfoSphere DataStage and IBM InfoSphere QualityStage (if installed): 1. If you installed globalization support (NLS), ensure that IBM InfoSphere DataStage users have the correct settings specified for localization. 2. Configure access to ODBC data resources. Optional: v Configure the parallel processing environment. v Migrate jobs that you created in an earlier version of InfoSphere DataStage to the current version. v Configure the IBM InfoSphere QualityStage Match Designer. v Set up the application server to run SQA or investigation reports. v Test the installation. Configure IBM InfoSphere Information Analyzer (if installed). Configure IBM InfoSphere Business Glossary (if installed). Configuring IBM InfoSphere Information Analyzer on page 284 Configuring IBM InfoSphere Business Glossary on page 285 Configuring IBM InfoSphere DataStage and IBM InfoSphere QualityStage on page 277 For more information Configuring security for IBM InfoSphere Information Server on page 259 Record your information
77
High availability (clustered configuration) installation checklist

Use this checklist to complete a new installation where the metadata repository database system and services tier (IBM WebSphere Application Server) are set up in a clustered topology. The engine tier is set up in an active-passive high availability 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 to communicate with the database cluster 6. Configure WebSphere Application Server to communicate with the database cluster 7. Install and engine tier 8. Install and 9. Install and configure high-availability cluster management software on the servers configure the engine tier configure the client tier
10. Test the installation 11. Configure the cluster 12. 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 HADR configuration on page 136. To complete these steps, use the task lists in the following sections.

Table 32. Topology planning and building tasks Description Review the system requirements. Learn about tiers and components. Design the topology of your installation. Determine whether to preinstall your database system. For more information Reviewing system requirements and release notes on page 91 Tiers and computers High availability topologies on page 23 Options for installing the database software on page 55 Record your information

78
Table 33. Software planning tasks Description Determine your cluster architecture. Build and test the hardware infrastructure. For more information WebSphere Application Server clustered topology on page 32 Metadata repository tier: v DB2 clustered installation: Preparing the servers, file system, and storage on page 127 v DB2 HADR installation: Preparing the servers, storage, and network on page 137 v Oracle Real Application Clusters (RAC) installation: Oracle RAC requirements on page 149 Services tier: v WebSphere Application Server clustered topology on page 32 Engine tier: AIX Setting up the servers, network, and storage (Tivoli System Automation for Multiplatforms example) on page 109 Setting up the servers, network, and storage (Tivoli System Automation for Multiplatforms example) on page 109 Record your information
Configure the servers, the network, and the storage device.
AIX
Obtain the InfoSphere Information Server software and any applicable fix packs. On both computers, verify name resolution, and open TCP ports for InfoSphere Information Server across any applicable firewalls. AIX Update the kernel parameters and user limits on both computers.
Obtaining IBM InfoSphere Information Server software on page 175 Configuring your network on page 92
Modifying kernel parameters and user limits (AIX)
Install and configure the tiers

For each tier, complete planning tasks and preinstallation tasks. Then install IBM InfoSphere Information Server components, and perform postinstallation tasks. Install and configure the tiers in this order: v v v v Metadata repository tier Services tier Engine tier Client tier
79
Metadata repository tier installation task list To configure your metadata repository tier, follow the steps in the following task list.
Table 34. Installation tasks: metadata repository tier Description For more information Record your information
Configure two servers with identical Preparing the servers, file system, and storage on page 127 internal storage, memory, and processing power. Designate one server as primary and the other as standby. These servers will support the metadata repository database and analysis database in a nonpartitioned topology. Configure a high-speed network between the servers, and a separate, isolated network to carry a heartbeat signal for the high availability software. Installing high availability software (Optional, for an IBM DB2 clustered on DB2 database system servers on topology.) Install high-availability page 128 (HA) software to monitor the health of the servers and to manage failover. Create the following administration accounts on each computer that will host the database system. The accounts on each computer must be identical. Log in to each account to confirm that it functions properly: v Owner of the metadata repository v (If installing IBM InfoSphere Information Analyzer) The owner of the analysis database v If installing the DB2 database system: All operating systems DB2 database administrator user AIX DB2 fenced user Setting up administrator and owner accounts on page 100
Install the database system, create the v DB2 clustered installation: database cluster, and preconfigure the Installing the DB2 database database by using scripts that are system and creating the cluster and supplied with the installation media. metadata repository database on page 129 v DB2 HADR installation: Installing the DB2 database system and creating the metadata repository database on page 138 v Oracle RAC installation: Creating the metadata repository database and running the installation program within an Oracle RAC configuration on page 150
80
Note: Do not run the InfoSphere Information Server installation program at this time. Run the installation program when you configure the services tier. Services tier installation task list
Table 35. Installation tasks: services tier Description Install WebSphere Application Server Network Deployment on all the computers that will host the services tier. This installation includes the deployment manager system and all computers that will host a managed node in the cluster. Also install any required WebSphere Application Server fix packs and patches. When creating a profile during the installation, make sure to disable administrative security. On the computer that hosts the deployment manager, create a deployment manager profile that contains the deployment manager process. Make sure that Administrative Security is disabled. On the computer that hosts the managed node, create a custom profile. This profile will contain the node agent process and the managed server process that will be part of the cluster. Use the WebSphere Application Server administrative console to create a cluster with one cluster member definition. Note: Start with a minimal cluster topology that contains a single node. After the installation procedure is complete, expand the cluster. Creating a deployment manager profile on page 160 For more information Installing IBM WebSphere Application Server Network Deployment for a cluster installation on page 159 Record your information
Creating a custom profile on page 161
Creating a cluster and cluster members for the application server on page 162
Install a front-end web server and the Installing a front-end web server on web server plug-in module. Run the page 164 configurewebserver_name script to create a web server definition in WebSphere Application Server, and do other web server configuration. (Optional) Install backup web servers, Installing a front-end load balancer (optional) on page 165 load balancers, firewalls, and other architectural components. Make sure that you can start and stop For IBM HTTP Server, see Starting the web server. Then start the web and stopping IBM HTTP Server server.
81
Table 35. Installation tasks: services tier (continued) Description On the computer that hosts the deployment manager, verify that you can start and stop the deployment manager process. Then start the process and verify that it is running. On the computer that hosts the managed node, verify that you can start and stop the managed node and node agent that you created. Then start the process and verify that it is running. Verify that it does not have global security on. For more information "Administering IBM InfoSphere Information Server IBM WebSphere Application Server services" in the Administration Guide Administering IBM InfoSphere Information Server IBM WebSphere Application Server services in the Administration Guide Record your information
82
Table 35. Installation tasks: services tier (continued) Description Run the installation program on the computer where the WebSphere Application Server deployment manager is installed: 1. From the is-suite directory on the installation media, run the following command to start the installation program: ./setup -verbose 2. Using a supported web browser, open the URL that the ./setup command displays. 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 WebSphere Application Server installation. c. In the WebSphere Application Server Profile page, choose the Deployment Manager profile. d. In the WebSphere Application Server Cluster Information page, specify the URL of the front-end HTTP dispatcher for the WebSphere Application Server cluster. In the HTTP Port field, type the port number of the front-end HTTP dispatcher. (Optional) Click Use Secure Sockets Layer (SSL) for HTTP communication. In the HTTP Port field, type the HTTP dispatcher port number on which secure HTTP (HTTPS) has previously been configured. e. In the Database Management System Selection page, choose Use existing database management system installation. f. In the Database Connection page, specify the metadata repository tier connection and database information. 4. Complete the rest of the installation steps. For more information Running the installation program (clustered installation) on page 166 Record your information
Engine tier installation task list

83
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, repeat these steps for each server engine.
Table 36. Installation tasks: engine tier Description Acquire and install high-availability cluster management software on both engine tier servers, and set up the cluster. For more information Go to the documentation for your high-availability cluster management software. For example configurations, see the following topics: AIX Installing the high availability software (Tivoli System Automation for Multiplatforms example) on page 110 Record your information
Set the service IP address.
Refer to the documentation for your high availability cluster management software. For example configurations, see the following topics: AIX Setting up the virtual IP address (Tivoli System Automation for Multiplatforms example) on page 111
AIX Define and start a resource group.
Refer to the documentation for your high availability cluster management software. See Defining and starting the resource group (Tivoli System Automation for Multiplatforms example) on page 112. Setting the locale and character encoding for the engine tier target computer on page 169
AIX For non-English locales, make sure that the locale and encoding are set correctly. The installation program uses the locale and encoding information of the computer to determine whether it can provide language support. Create an administrator account for the InfoSphere Information Server engine. Log in to the account to activate the password.
84
Table 36. Installation tasks: engine tier (continued) Description Run the installation program: v In the Tier Selection page, choose Engine only. v In the High Availability Server Cluster Configuration page, click Server cluster configuration. In the Virtual host name field, enter the virtual host name that was created when the HA software was configured. v Whenever prompted for an installation directory, specify a path on the shared storage device. v In the IBM InfoSphere Information Server Location page, specify the URL of the front-end HTTP dispatcher for the WebSphere Application Server cluster. In the Port field, type the port number of the front-end HTTP dispatcher. Enter the InfoSphere Information Server administrator account name and password. (Optional) Click Use Secure Sockets Layer (SSL) for HTTP communication. In the Port field, type the HTTP dispatcher port number on which secure HTTP (HTTPS) has previously been configured. Set up the resource agent scripts. Go to the documentation for your high availability cluster management software. For example configurations, see the following topics: AIX Setting up the high availability control scripts (Tivoli System Automation for Multiplatforms example) on page 116 For more information For example configurations, see the following topics: AIX Installing IBM InfoSphere Information Server in the cluster (Tivoli System Automation for Multiplatforms example) on page 115 Record your information
Client tier installation task list To configure your client tier, follow the steps in the following task list. Note: If you are creating a topology with more than one client computer, repeat these steps for each client computer.
Table 37. Installation tasks: client tier Description Run the installation program. In the Tier Selection page, choose Client only. For more information Chapter 6, Installing IBM InfoSphere Information Server software, on page 179 Record your information
85
(Optional) Manually configure secure HTTP (HTTPS) for the client tier.
Manually configuring InfoSphere Information Server components to use HTTPS on page 254

Run the IBM Support Assistant Lite See Installation verification and for InfoSphere Information Server tool troubleshooting on page 211 to verify the installation. Test the engine tier failover function. Go to the documentation for your high availability cluster management software. For example configurations, see the following topics: AIX Testing the configuration (Tivoli System Automation for Multiplatforms example) on page 117
Configure the cluster

After you install the software and test the installation, complete the following tasks to configure the cluster.
Table 39. Configuring the cluster tasks Description DB2 clustered and HADR installations: Configure the primary and secondary servers. For more information v DB2 cluster installation: Configuring automatic client reroute on page 131 v DB2 HADR installation: Configuring the HADR primary server on page 139 Configuring the HADR standby server on page 140 Record your information
86
Table 39. Configuring the cluster tasks (continued) Description Configure WebSphere Application Server to work with the metadata repository tier cluster. For more information v DB2 clustered installation: Specifying the alternate address and port for a DB2 database to connect to IBM WebSphere Application Server on page 132 v DB2 HADR installation: Specifying the alternate database address and port for IBM WebSphere Application Server on page 142 v Oracle RAC installation: Connecting to an Oracle RAC configuration on page 150 DB2 HADR installation: Start HADR. Starting HADR on page 146 Record your information

Table 40. Postinstallation configuration tasks (all tiers) Description (Optional) Configure Secure Sockets Layer (SSL): v Enable SSL for inbound RMI/IIOP. When you install InfoSphere Information Server in an IBM WebSphere Application Server Network Deployment 7.0 or later environment, SSL for inbound RMI/IIOP communications is disabled by default. v If the installation program did not configure HTTPS for a tier computer during InfoSphere Information Server installation, manually configure HTTPS for that tier computer. (Optional) Add additional WebSphere Adding a new cluster member in Application Server nodes or other the IBM InfoSphere Information Server components to the cluster. Administration Guide For more information Configuring security for IBM InfoSphere Information Server on page 259 Record your information
87
Table 40. Postinstallation configuration tasks (all tiers) (continued) Description To communicate the WebSphere Application Server cluster configuration to the front-end Web server, run the WebSphere Application Server administrative console to generate the plugin-cfg.xml file, and then manually copy it to each Web server. Then restart the Web server. If you are using IBM HTTP Server, you can automatically propagate the file to your Web servers by using the WebSphere Application Server administrative console. Configure security within InfoSphere Information Server: 1. Choose a user registry and configure it for InfoSphere Information Server. 2. Create users and groups in the user registry. 3. Assign security roles to users and groups. 4. Configure InfoSphere Information Server engine security. Map credentials if necessary. 5. Assign project roles if required by the installed suite components. Optionally, also: v ConfigureWebSphere Application Server for non-root administration. v Configure InfoSphere Information Server agents for non-root administration. v Configure the Auditing service. Configuring security for IBM InfoSphere Information Server on page 259 For more information Propagating the plugin-cfg.xml file to the front-end Web server in the IBM InfoSphere Information Server Administration Guide Record your information
88
Table 40. Postinstallation configuration tasks (all tiers) (continued) Description Configure IBM InfoSphere DataStage and IBM InfoSphere QualityStage (if installed): 1. If you installed globalization support (NLS), ensure that InfoSphere DataStage users have the correct settings specified for localization. 2. Configure access to ODBC data sources. Optionally, also: v Configure the parallel processing environment. v Migrate jobs that you created in an earlier version of InfoSphere DataStage to the current version. v Configure the InfoSphere QualityStage Match Designer. v Set up the application server to run SQA or investigation reports. v Test the installation. Configure InfoSphere Information Analyzer (if installed). Configure IBM InfoSphere Business Glossary (if installed). Configuring IBM InfoSphere Information Analyzer on page 284 Configuring IBM InfoSphere Business Glossary on page 285 For more information Configuring IBM InfoSphere DataStage and IBM InfoSphere QualityStage on page 277 Record your information
89
90
Chapter 4. Preparing the tier computers

Before you run the IBM InfoSphere Information Server installation program, prepare each target computer for the installation. You install InfoSphere Information Server tier by tier. When you run the installation program, it prompts you to select the product modules to install, to specify which tier or tiers to install on the computer, and it installs the appropriate product module components in the tiers that you specify.
Reviewing system requirements and release notes

Ensure that all computers meet the hardware and software requirements for the product modules that you want to install. To obtain the most up-to-date information about the installation requirements, see these resources: v The system requirements at www.ibm.com/support/ docview.wss?uid=swg27021833. v The release notes at publib.boulder.ibm.com/infocenter/iisinfsv/v8r7/topic/ com.ibm.swg.im.iis.productization.iisinfsv.relinfo.doc/topics/ iisihrinfo_infsv_rnote_v87.html.
Checking prerequisites
To determine if your system is ready to install IBM InfoSphere Information Server, run the IBM Support Assistant Lite for InfoSphere Information Server (ISA Lite) tool. The Prerequisite Checker that is included with ISA Lite evaluates your system to determine whether required packages are installed, if kernel parameters are too low for a successful installation, or if potential problems exist with environment variables.
Before you begin

Download and install the ISA Lite tool from the support site (www.ibm.com/ support/docview.wss?uid=swg24022700).
About this task

For a full explanation of how to complete the following steps, refer to the documentation that is available under the \doc folder of the ISA Lite installation.
Procedure
1. Run the tool in console mode to create a response file. You can use this response file to run the same script in the future without reentering all of your information. 2. Run the Prerequisites Checker to evaluate your system. You can run the Prerequisites Checker before starting a new installation of InfoSphere Information Server or before you start an upgrade to a new version. 3. View the generated reports to see the prerequisites that passed and failed. Correct any failed prerequisites and then run the tool again.
91
Setting up the tier computers

Complete the following preparation steps for each computer in your installation. Although the installation program completes a prerequisite check before installing software, you must check some additional prerequisites identified by IBM Software Support. See the following technote for more information regarding prerequisites: www.ibm.com/support/docview.wss?uid=swg27019888.
Removing libicu libraries (AIX)

Several libicu libraries might cause the IBM InfoSphere Information Server installation program to fail. Remove these entries before you start installing InfoSphere Information Server.
Symptoms
The installation program fails with the following error:
Ensure the following libraries do not exist: /usr/lib/libicuio.a /usr/lib/libicuuc.a /usr/lib/libicui18n.a. These libraries may cause uvsh to not work properly.
Causes
Some AIX systems have libicu libraries in the /usr/lib directory. The InfoSphere Information Server installation program installs a copy of libicu that it needs in the /opt/IBM/InformationServer/Server/DSComponents/lib directory. If the libicu libraries in the /usr/lib directory are 32-bit, uvsh reports an invalid magic value because of a load issue. If the libicu libraries in the /usr/lib directory are 64-bit, usvh works as designed.
Resolving the problem

Remove all of the following libraries from the /usr/lib directory if they exist before proceeding with your installation: libicuio.a libicuuc.a libicui18n.a
Configuring your network

IBM InfoSphere Information Server exchanges high volumes of data across several network ports, which requires that you carefully configure the host names and ports for your network.
Before you begin

Ensure that a TCP/IP network is used for all communications in the installation.
About this task

For performance reasons, do not install InfoSphere Information Server in a wide area network (WAN) configuration because of the data exchanges that are required.
92
Although clients can work over a WAN if the latency is low, when the network latency increases, it has a detrimental effect on the clients. Note: The port numbers in the following tables might vary from those that are used in your system because the installation program automatically computes the port value based on port availability. For example, for the BOOTSTRAP_ADDRESS port, the installation program starts with port 2809 and increments by 1 until it locates an open port. Ensure that you select the correct ports in your system to open and make available. The port values that are used in your system are stored in the response file that the installation program generates. Before you install the product, check the Response File Review panel in the installation program for the location, name, and contents of your response file.
Procedure
1. Set up the name resolution. a. Verify that the computers in the installation can resolve all the other computers by both the short name and long name (fully qualified domain name), for example mycomputer and mycomputer.mydomain.com. b. Ensure that each of the following tier computers can resolve the IP addresses of the computers that are listed for that tier.
Table 41. Tier computers and the computers that they connect to Tier computer Metadata repository tier Services tier Engine tier Tier computers to connect to Metadata repository tier Services tier, engine tier, client tier Services tier, engine tier, client tier
c. Ensure that only localhost is mapped to the loopback IP address. The IPv4 version of this address is 127.0.0.1 and the IPv6 version is ::1/128. No other entries can map localhost to the IP address of the local computer. The following example shows how these entries are configured in the following files:
Operating system AIX File /etc/hosts 127.0.0.1 | ::1/128 localhost.localdomain localhost xx.xx.xx.xx | xx:xx::xx:xx longhostname shorthostname
localdomain The domain name. xx.xx.xx.xx | xx:xx::xx:xx The unique IP address for the computer. IPv4 and IPv6 addresses are supported. longhostname shorthostname The long and short names for the computer. 2. For the metadata repository tier, open and make TCP ports available through firewalls for InfoSphere Information Server and the application server.
Table 42. Port numbers for the metadata repository tier Component IBM DB2 database for the metadata repository (default database) Default port numbers 50000 Tiers that use the port Services
93
Table 42. Port numbers for the metadata repository tier (continued) Component IBM DB2 database for the analysis database (default database) Oracle database for the metadata repository (if used) Oracle database for the analysis database (if used) Default port numbers 50000 1521 1521 Tiers that use the port Services, engine, client Services Services, engine, client Services Services, engine, client
Microsoft SQL Server database for the metadata repository 1433 (if used) Microsoft SQL Server database for the analysis database (if used) 1433
3. For the services tier, open and make TCP ports available through firewalls for InfoSphere Information Server and the application server.
Table 43. Port numbers for the services tier (basic configuration) Component Reports server InfoSphere Information Server web-based clients (HTTP) InfoSphere Information Server web-based clients (HTTPS) Default port numbers for basic configuration 16581 WC_defaulthost (9080) WC_defaulthost_secure (9443) Tiers that use the port Client Services, engine, client Client If HTTPS is configured, the services tier and engine tier also use this port. WC_adminhost (9060) WC_adminhost_secure (9043) Client Client Services, engine, client
IBM WebSphere Application Server administrative console (redirects to HTTPS) IBM WebSphere Application Server administrative console (HTTPS)
InfoSphere Information Server communication BOOTSTRAP_ADDRESS (2809) services (Java Remote Method Invocation ORB_LISTENER_ADDRESS (9100) [RMI] or Inter-ORB Protocol [IIOP]) SAS_SSL_SERVERAUTH_ LISTENER_ADDRESS (9401) CSIV2_SSL_ MUTUALAUTH_ LISTENER_ADDRESS (9402) CSIV2_SSL_SERVERAUTH_ LISTENER_ADDRESS (9403)
94
Table 43. Port numbers for the services tier (basic configuration) (continued) Component IBM InfoSphere Information Services Director services with JMS bindings Default port numbers for basic configuration SIB_ENDPOINT_ADDRESS (7276) SIB_ENDPOINT_SECURE_ ADDRESS (7286) SIB_MQ_ENDPOINT_ ADDRESS (5558) SIB_MQ_ENDPOINT_ SECURE_ADDRESS (5578) Table 44. Port numbers for the services tier (clustered configuration) Component Reports server InfoSphere Information Server web-based clients (HTTP) Default port numbers for clustered configuration (DHTML reports server functionality is not supported in clustered configurations.) Tiers that use the port Client Tiers that use the port Client
Services, engine, Firewall between the client and dispatcher (if any): usually 80. This value varies depending on client the configuration of the front-end dispatcher. Firewall between dispatcher and cluster members (if any): WC_defaulthost of all cluster members (for example, 9yep080, 9081, and so on).
InfoSphere Information Server web-based clients (HTTPS)
Firewall between the client and dispatcher (if any): usually 443. This value varies depending on the configuration of the front-end dispatcher.
Client
If HTTPS is configured, the Firewall between the dispatcher and cluster services tier and members (if any): WC_defaulthost_secure of all engine tier also use cluster members (for example, 9443, 9444, and so this port. on) WC_adminhost (9060) WC_adminhost_secure (9043) Client Client
IBM WebSphere Application Server administrative console (redirects to HTTPS) IBM WebSphere Application Server administrative console (HTTPS)
95
Table 44. Port numbers for the services tier (clustered configuration) (continued) Component Default port numbers for clustered configuration Tiers that use the port Services, engine, client
InfoSphere Information Server communication BOOTSTRAP_ADDRESS of all cluster members services (Java Remote Method Invocation (9809, 9810, 9811, and so on) [RMI] or Inter-ORB Protocol [IIOP]) ORB_LISTENER_ADDRESS of all node agents (9100, 9101, and so on) DCS_UNICAST_ADDRESS (9353) SAS_SSL_SERVERAUTH_ LISTENER_ADDRESS, CSIV2_SSL_SERVERAUTH_ LISTENER_ADDRESS, CSIV2_SSL_ MUTUALAUTH_ LISTENER_ADDRESS of all cluster members: (9410, 9411, 9412), (9411, 9414, 9415), and so on IBM InfoSphere Information Services Director services with JMS bindings SIB_ENDPOINT_ADDRESS of all cluster members (7277, 7278, and so on) SIB_ENDPOINT_SECURE_ ADDRESS of all cluster members (7287, 7288, and so on) SIB_MQ_ENDPOINT_ ADDRESS of all cluster members (5559, 5560, and so on) SIB_MQ_ENDPOINT_ SECURE_ADDRESS of all cluster members (5579, 5580, and so on)
Client
4. For the engine tier, open and make TCP ports available through firewalls for InfoSphere Information Server and the application server.
Table 45. Port numbers for the engine tier Component InfoSphere Information Server ASB agent Default port numbers 31531, and a random port number greater than 1024 Instead of using a random port number, you can fix this to a specific port by specifying agent.objectport=# in the C:\IBM\ InformationServer\ASBNode\conf\agent.properties file after you complete the installation. After designating a specific port, restart the logging agent and the ASB agent so that the change takes effect. 31533 Engine Tiers that use the port Services
InfoSphere Information Server logging agent
96
Table 45. Port numbers for the engine tier (continued) Component Default port numbers Tiers that use the port Engine, client Engine
IBM InfoSphere DataStage and DSRPC (31538) QualityStage Administrator services Parallel job monitors 13400 (port 1) and 13401 (port 2) Access to port 1 is required only from the conductor node. Access to port 2 is required from the conductor node and the node where the InfoSphere Information Server engine is installed, if that node is different from the conductor node. Parallel engine Parallel engine remote process startup (Remote Shell and Secure Shell, multiple nodes only) Parallel engine (multiple nodes only) APT_PM_STARTUP_PORT (multiple ports, uses a port number of 10240 or greater) 22514
Engine Engine
APT_PLAYER_CONNECTION_ PORT (multiple ports, uses a port number of 11000 or greater)
Engine
5. For connecting to external data sources, see the vendor-supplied documentation for additional port assignments.
Processes used by InfoSphere Information Server

The following processes are ones that you might see running in InfoSphere Information Server. This list also includes processes for DB2 Database and WebSphere Application Server, among other processes. Note: This list is not exhaustive. Other processes or services might run within your environment.
AIX
DB2 processes
dasusr1 17245 root 19072 1 0 Jun07 ? 1 0 Jun07 ? 00:00:00 /u1/home/dasusr1/das/adm/db2dasrrm 00:01:01 /opt/IBM/db2/V9/bin/db2fmcd
dasusr1 19108 1 0 Jun07 ? 00:00:00 /opt/IBM/db2/V9/das/bin/db2fmd -i dasusr1 -m /opt/IBM/db2/V9/das/lib/libdb2dasgcf.so.1 root 16647 1 0 Jun07 pts/2 00:00:00 db2wdog 0 00:17:56 db2sysc 0 00:00:21 db2ckpwd 0 00:00:21 db2ckpwd 0 00:00:21 db2ckpwd 0 00:00:00 db2vend (PD Vendor Process - 1)
db2inst1 16649 16647 0 Jun07 pts/2 root root root 16650 16649 0 Jun07 pts/2 16651 16649 0 Jun07 pts/2 16652 16649 0 Jun07 pts/2
db2inst1 16656 16649 0 Jun07 pts/2
db2inst1 16665 16647 0 Jun07 pts/2 00:01:23 db2acd 0 ,0,0,0,1,0,0,0000,1,0,8a6740,14,200014,2,0,1,1ffc0,0x210000000,0x210000000, 1600000,128005,2,4d0012 db2fenc1 19086 16647 0 Jun07 pts/2 00:00:03 db2fmp ( ,0,0,0,0,0,0,0000,1,0,8a6740,14,200014,2,0,1,64ffc0,0x210000000,0x210000000,
97
1600000,128005,2,b3f004a db2fenc1 19132 16647 0 Jun07 pts/2 00:00:02 db2fmp ( ,1,0,0,0,0,0,0000,1,0,8a6740,14,200014,2,0,1,85ffc0,0x210000000,0x210000000, 1600000,128005,2,b598040
InfoSphere Information Server processes

root root 3713 1 0 Jun07 pts/2 00:00:00 /opt/IBM/InformationServer/Server/DSEngine/bin/dsrpcd 3786 1 0 Jun07 pts/2 00:00:01 /opt/IBM/InformationServer/ASBNode/apps/jre/bin/java -classpath /opt/IBM/InformationServer/Server/PXEngine/java/JobMonApp.jar: /opt/IBM/InformationServer/Server/PXEngine/java/xerces/xercesImpl.jar: /opt/IBM/InformationServer/Server/PXEngine/java/xerces/xmlParserAPIs.jar JobMonApp 13400 13401 3801 1 0 Jun07 ? 00:09:07 /opt/IBM/InformationServer/Server/PXEngine/bin/resource_tracker 31294 1 0 Jun07 pts/2 00:01:44 /opt/IBM/InformationServer/ASBNode/apps/jre/bin/java -Duser.language=en -Duser.country=US -Djava.security.auth.login.config= /opt/IBM/InformationServer/ASBNode/eclipse/plugins/com.ibm.isf.client/auth.conf -Dcom.ibm.CORBA.ConfigURL=file: /opt/IBM/InformationServer/ASBNode/eclipse/plugins/com.ibm.isf.client/sas.client.props -Dcom.ibm.SSL.ConfigURL=file: /opt/IBM/InformationServer/ASBNode/eclipse/plugins/com.ibm.isf.client/ssl.client.props -Dcom.ibm.CORBA.enableClientCallbacks=true -Dcom.ibm.CORBA.FragmentSize=128000 -classpath /opt/IBM/InformationServer/ASBNode/conf: /opt/IBM/InformationServer/ASBNode/eclipse/plugins/com.ibm.isf.client: /opt/IBM/InformationServer/ASBNode/eclipse/plugins/com.ibm.isf.client/ iis_util.jar: /opt/IBM/InformationServer/ASBNode/eclipse/plugins/com.ibm.isf.client/ ACS_client.jar: /opt/IBM/InformationServer/ASBNode/eclipse/plugins/com.ibm.isf.client/ ACS_common.jar: /opt/IBM/InformationServer/ASBNode/eclipse/plugins/com.ibm.isf.client/ ISF_util.jar: /opt/IBM/InformationServer/ASBNode/eclipse/plugins/com.ibm.isf.client/ ISF_j2ee.jar: /opt/IBM/InformationServer/ASBNode/eclipse/plugins/com.ibm.isf.client/ ASB_utils.jar: /opt/IBM/InformationServer/ASBNode/eclipse/plugins/com.ibm.isf.client/ ASB_util_client.jar: /opt/IBM/InformationServer/ASBNode/eclipse/plugins/com.ibm.isf.client/ com.ibm.ws.ejb.thinclient_7.0.0.jar: /opt/IBM/InformationServer/ASBNode/eclipse/plugins/com.ibm.isf.client/ com.ibm.ws.security.crypto.jar com.ascential.acs.logging.agent.LoggingAgentSocketImpl 31324 31319 0 Jun07 pts/2 00:01:36 /opt/IBM/InformationServer/ASBNode/apps/jre/bin/java -Xbootclasspath/a:conf:eclipse/plugins/com.ibm.isf.client -Xss2M -Xoss2M -Duser.language=en -Duser.country=US -Djava.ext.dirs=apps/jre/lib/ext:lib/java:eclipse/plugins:eclipse/plugins/ com.ibm.isf.client -classpath conf:eclipse/plugins/com.ibm.isf.client -Djava.security.auth.login.config= /opt/IBM/InformationServer/ASBNode/eclipse/plugins/com.ibm.isf.client/auth.conf -Dcom.ibm.CORBA.ConfigURL=file: /opt/IBM/InformationServer/ASBNode/eclipse/plugins/com.ibm.isf.client/sas.client.props -Dcom.ibm.SSL.ConfigURL=file: /opt/IBM/InformationServer/ASBNode/eclipse/plugins/com.ibm.isf.client/ssl.client.props -Dcom.ibm.CORBA.enableClientCallbacks=true -Dcom.ibm.CORBA.FragmentSize=128000 com.ascential.asb.agent.impl.AgentImpl run
dsadm root
root
WebSphere Application Server processes

root 30600 1 0 Jun07 pts/2 01:06:02 /opt/IBM/WebSphere/AppServer/java/bin/java -Declipse.security -Dwas.status.socket=44248 -Dosgi.install.area=/opt/IBM/WebSphere/AppServer -Dosgi.configuration.area=/opt/IBM/WebSphere/AppServer/profiles/InfoSphere/configuration -Dosgi.framework.extensions=com.ibm.cds,com.ibm.ws.eclipse.adaptors -Xshareclasses:name=webspherev70_%g,groupAccess,nonFatal -Xscmx50M -Xbootclasspath/p:/opt/IBM/WebSphere/AppServer/java/jre/lib/ext/ibmorb.jar: /opt/IBM/WebSphere/AppServer/java/jre/lib/ext/ibmext.jar -classpath /opt/IBM/WebSphere/AppServer/profiles/InfoSphere/properties: /opt/IBM/WebSphere/AppServer/properties: /opt/IBM/WebSphere/AppServer/lib/startup.jar: /opt/IBM/WebSphere/AppServer/lib/bootstrap.jar:
98
/opt/IBM/WebSphere/AppServer/lib/jsf-nls.jar: /opt/IBM/WebSphere/AppServer/lib/lmproxy.jar: /opt/IBM/WebSphere/AppServer/lib/urlprotocols.jar: /opt/IBM/WebSphere/AppServer/deploytool/itp/batchboot.jar: /opt/IBM/WebSphere/AppServer/deploytool/itp/batch2.jar: /opt/IBM/WebSphere/AppServer/java/lib/tools.jar -Dibm.websphere.internalClassAccessMode=allow -verbose:gc -Xms1280m -Xmx2048m -Xcompressedrefs -Dws.ext.dirs=/opt/IBM/WebSphere/AppServer/java/lib: /opt/IBM/WebSphere/AppServer/profiles/InfoSphere/classes: /opt/IBM/WebSphere/AppServer/classes:/opt/IBM/WebSphere/AppServer/lib: /opt/IBM/WebSphere/AppServer/installedChannels:/opt/IBM/WebSphere/AppServer/lib/ext: /opt/IBM/WebSphere/AppServer/web/help: /opt/IBM/WebSphere/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime -Dderby.system.home=/opt/IBM/WebSphere/AppServer/derby -Dcom.ibm.itp.location=/opt/IBM/WebSphere/AppServer/bin -Djava.util.logging.configureByServer=true -Duser.install.root=/opt/IBM/WebSphere/AppServer/profiles/InfoSphere -Djavax.management.builder.initial=com.ibm.ws.management.PlatformMBeanServerBuilder -Dwas.install.root=/opt/IBM/WebSphere/AppServer -Dpython.cachedir=/opt/IBM/WebSphere/AppServer/profiles/InfoSphere/temp/cachedir -Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager -Dserver.root=/opt/IBM/WebSphere/AppServer/profiles/InfoSphere -Dcom.ibm.security.jgss.debug=off -Dcom.ibm.security.krb5.Krb5Debug=off -Duser.language=en -Duser.country=US -Xdisableexplicitgc -Djava.awt.headless=true -Djava.security.policy=/opt/IBM/WebSphere/AppServer/profiles/InfoSphere/properties /server.policy -Djava.security.auth.login.config= /opt/IBM/WebSphere/AppServer/profiles/InfoSphere/properties/wsjaas.conf com.ibm.wsspi.bootstrap.WSPreLauncher -nosplash -application com.ibm.ws.bootstrap.WSLauncher com.ibm.ws.runtime.WsServer /opt/IBM/WebSphere/AppServer/profiles/InfoSphere/config issusex1Node01Cell issusex1Node01 server1
Modifying kernel parameters and user limits (AIX )

IBM InfoSphere Information Server requires specific resources for each tier. Modify the kernel parameters and user limits, and restart the computer before you start the installation program. The kernel parameter and user limit requirements are minimum requirements for InfoSphere Information Server. The optimal value for each parameter might be higher depending on your topology and the operational data load. Additional kernel parameter and user limit changes might be required. When more than one value is provided for your configuration, use the largest minimum value. All changes must be made by a trained system administrator. Make a backup copy of the kernel parameters and user limits before you modify them. After you modify the kernel parameters and user limits with the suggested values, restart the computer, and then install InfoSphere Information Server.
Minimum kernel parameters

You might need to configure the kernel parameters and user limits for your application server. For more information, refer to the IBM WebSphere Application Server documentation.
Minimum kernel parameter values for IBM DB2 databases

The minimum metadata repository kernel parameter requirements apply only to DB2 database installations. Before you install DB2 as part of InfoSphere Information Server, ensure that your computer meets the following minimum requirements for kernel parameter for DB2: v AIX: The default kernel parameter values are sufficient.
99
When the DB2 kernel requirements are different from the InfoSphere Information Server kernel parameter requirements, use the largest minimum value. If you use a different database system for the metadata repository, consult the product documentation for that database system to find information about kernel parameter requirements.
Minimum AIX kernel parameters

Run the smit or smitty command to modify kernel parameters on AIX. The following table contains the minimum kernel parameters and user limits for the engine and services tiers.
Table 46. Minimum AIX kernel parameters and user limits (engine and services tiers) Parameter SHMMAX SHMMNI SHMSEG MAXUPROC NOFILES Engine and services tiers 536870912 2000 200 1000 or unlimited 10240
Setting up administrator and owner accounts

When you run the IBM InfoSphere Information Server installation program, you must specify the user names and passwords for administrator and owner accounts for the program.
Before you begin

Make sure that you are familiar with the naming restrictions described in Naming restrictions for user IDs and passwords on page 103.
About this task

Creating administrator and owner accounts before you install InfoSphere Information Server ensures that operating system policies, such as requiring a password change at the first login, do not interfere with the installation program use of the accounts. Create the accounts as local operating system accounts, lightweight directory access protocol (LDAP), accounts, or NIS accounts. Important: If you use LDAP accounts or NIS accounts, you must create these accounts before you run the InfoSphere Information Server installation program. The installation program cannot create these accounts. When you create the accounts, record the user ID and password for each user.
Procedure
1. On the operating systems where you install InfoSphere Information Server, make sure that the user who installs InfoSphere Information Server can log in using the following accounts. The user must log in using one of these accounts to install InfoSphere Information Server.
100
Table 47. User accounts that are required to install the product Operating system AIX Accounts The root user account.
2. AIX : On the operating systems where you install each engine tier, create the following additional accounts and record the passwords. Note: If your installation does not include an engine tier, you can skip this step.
Table 48. Accounts that you create for an engine tier (AIX )
Account description Administrator for the InfoSphere Information Server engine Default user name dsadm Primary group dstage Secondary group You customize this group to apply to your security model. Notes This user performs administrative tasks, such as adding new projects and defining their properties. To run jobs, create a separate user with the developer role. This account must be an account on the local operating system. During installation time, you cannot specify a Lightweight Directory Access Protocol (LDAP) account as the engine administrator account.
3. On the operating system where you install the metadata repository tier, create the following additional accounts and record the passwords.
Table 49. Accounts that you create on the metadata repository tier
Account description DB2 administration server user Default user name AIX dasusr1 Primary group AIX dasadm1 Secondary group None Notes Create the operating system account for DB2 database only. This account must have read, write, and execute permission to the following directories: v The home directory for the DB2 administration server user (by default, the path is /home/dasusr1) v /tmp v /var/tmp
101
Table 49. Accounts that you create on the metadata repository tier (continued)
Account description AIX DB2 instance owner Default user name db2inst1 Primary group db2iadm1 Secondary group dasadm1 Notes Create the operating system account for DB2 database only. This account must have read, write, and execute permission to the following directories: v The home directory for the DB2 instance owner (by default, the path is /home/db2inst1) v /tmp v /var/tmp AIX DB2 fenced user Owner of the metadata repository xmeta xmeta Important: Do not specify db2admin or db2inst1 as the metadata repository user name. None db2fenc1 db2fadm1 None Create the operating system account for DB2 database only. Create the operating system account for DB2 database only. When you use the DB2 database for the repository, the DB2 database uses the authentication for the operating system for connection requests. Create the operating system account for DB2 database only. When you use the DB2 database for the repository, the DB2 database uses the authentication for the operating system for connection requests. Create the operating system account for DB2 database only. DB2 database uses the authentication for the operating system.
User of the metadata repository
xmetasr Important: This user name must be different from the user name that you specify for the owner of the metadata repository (xmeta).
xmetasr
None
IBM InfoSphere Information Analyzer: owner of the analysis databases
iauser Important: Do not specify db2admin or db2inst1 as the InfoSphere Information Analyzer database user name.
iauser
None
AIX : The InfoSphere Information Server installation program must have root access. Root must have write permissions to the following directories: v /tmp v /var v /var/tmp v /usr/local/bin 4. Verify permissions for all users including root. If any directories are mounted from network file systems such as AFS, permissions might not be adequate to perform a successful installation. 5. Determine the names and passwords to use for the following administrator accounts:
102
Table 50. Administrator accounts set up by the installation program Account description Administrator for IBM WebSphere Application Server Administrator for InfoSphere Information Server Default user name wasadmin isadmin
6. Log in to each account to confirm that it functions correctly. Some operating systems are set up to force a password change during the first login. Therefore, a manual login is required to activate the accounts appropriately.
Naming restrictions for user IDs and passwords

Some restrictions apply to the names that you choose for user IDs and passwords. These restrictions are imposed by the underlying components that IBM InfoSphere Information Server uses. All user IDs and passwords The following characters are not permitted: (white space) ! (exclamation point) " (double quotation mark) # (number sign) $ (dollar sign) % (percent sign) ' (single quotation mark) : (colon) \ (backslash) { (left brace) } (right brace) Leading or trailing white space, such as spaces, tabs, and line continuation characters, is removed by the installation program. Any existing user IDs and passwords cannot have leading or trailing white space characters as part of their definitions. Internal user registry user IDs Only alphanumeric characters and the following characters are permitted: _ (underscore) - (hyphen) \ (backslash) = (equal sign) . (period) IBM WebSphere Application Server administrator password The following characters are not permitted: v Space characters v ^ (caret) IBM DB2 database user names v You can use these characters in IDs if permitted by the operating system: A through Z 0 through 9 # (number sign) ! (exclamation point)
103
% (percent sign) ( (opening parenthesis) ) (closing parenthesis) $ (dollar sign. Must not be the first character.) AIX : User names and passwords cannot start with a numeric digit. v AIX : The DB2 database requires these user accounts: DB2 instance owner, DB2 fenced user, and DB2 administrator. These account names cannot 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 system v Names cannot include accented characters. v AIX : Users, groups, and instance names must be in lowercase letters. Character length limits v AIX: Operating system user IDs: 8 v WebSphere Application Server IDs: 60 v DB2 user IDs and passwords: AIX : 8
Project naming conventions

Use these conventions when you name your projects. IBM InfoSphere DataStage, IBM InfoSphere QualityStage, and IBM InfoSphere Information Analyzer store jobs, analysis, and logs in these projects. You need to choose the name of one InfoSphere DataStage project during the initial installation. The name of a project is limited to a maximum of 40 characters. The project 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 the source code control. As projects are promoted through the source control, the name of the phase and the project reflect the version in this form:
Phase_ProjectName_version
where Phase corresponds to the phase in the application development life cycle:
104
dev it uat prod
Development Integration test User acceptance test Production
Creating a two-server active-passive high availability configuration

You can provide a basic level of high availability by configuring the IBM InfoSphere Information Server software tiers in an active-passive high availability configuration. In a two-server active-passive high availability configuration, two computers share a storage device. The metadata repository tier, engine tier, and services tier are all installed 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 not running any tier software. A high availability software product is installed on both servers, such as IBM Tivoli System Automation for Multiplatforms on Linux or UNIX systems or Microsoft Cluster Service (MSCS) on Microsoft Windows systems. The high availability software maintains a heartbeat, which is a periodic signal from the active server to the passive server that indicates that the active server is operational. If the active server fails, the heartbeat also fails. The high availability software restarts all the services on the passive server. This process is called a failover. With this configuration, a floating IP address and virtual host name are defined for the server pair. This information is associated with the active server. All client programs connect to the server by using this address or host name. If the active server fails, the floating IP address and virtual host name are automatically reassociated with the passive server. If you provide high availability for the services tier or metadata repository tier (or both) by using other methods, you can choose to include only the remaining tiers in the active-passive configuration. For example, you might choose to implement an IBM WebSphere Application Server cluster for your services tier and an IBM DB2 Database for Linux, UNIX, and Windows cluster for your metadata repository tier. In this case, the servers in your active-passive configuration host only the engine tier. To set up a high availability configuration, you must have a solid understanding of network technologies such as protocols, layers, devices, and so on. Highly available configurations, especially configurations that involve clustering, are technically complex and require expertise to implement them successfully.
Creating an active-passive configuration (AIX )

Regardless of the high availability software that you use, you must complete the same basic steps to configure a two-server active-passive configuration.
Procedure
1. Set up the hardware and cable the network. The servers must be physically separate. Use identical hardware with identical internal storage, memory, and processing power.
105
2. 3.
4.
5.
The servers must be able to communicate with each other over high-speed networks. To minimize single points of failure, each server must have redundant connections to at least two physically separate high-speed networks. To support failover when a problem occurs, the high availability software creates a heartbeat signal between the servers. Set up at least two more physically separate networks for this signal. These networks can be serial or other networks. The networks that carry the heartbeat signal must be physically separate and isolated from the high-speed networks. Install the high availability software on both the active server and the passive server. Allocate an IP address and associate it with the virtual host name that the client tier will use to connect to the IBM InfoSphere Information Server server-side components. Mount the shared storage device in identical mount points on each node. Create the following mount points: v Base installation directory. Typically /opt/IBM v Base user home directory. Typically /home 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 to the primary server by using the virtual host name. Test failover and resolve any issues before continuing. 6. On both servers, create the following directories within the mount points of these directories. Ensure that the directories have identical local user permissions. The directories might differ depending on your configuration.
Table 51. Directories for active-passive configuration Configuration of tiers All Directory Project directory. Default: /opt/IBM/InformationServer/Server/ Projects v InfoSphere Information Server installation directory. Default: /opt/IBM/ InformationServer v Home directory for the InfoSphere Information Server engine administrator. Typically /home/dsadm Services tier on both servers IBM WebSphere Application Server installation directory. Default: /opt/IBM/WebSphere
Engine tier on both servers
106
Table 51. Directories for active-passive configuration (continued) Configuration of tiers Directory
Metadata repository tier on both servers, IBM v DB2 database system installation directory. DB2 database system Default: /opt/IBM/db2 v DB2 instance owner home directory. Typically /home/db2inst1 v DB2 administration server user home directory. Typically /home/dasusr1 v DB2 fenced user home directory. Typically /home/db2fenc1 v Metadata repository owner home directory. Typically /home/xmeta v If IBM InfoSphere Information Analyzer is installed, the home directory of the owner of the analysis databases. Typically /home/iauser
7. If the active-passive configuration will include only the engine tier (that is, the metadata repository or services tiers are to be located outside of the active-passive configuration), install and configure the metadata repository and services tiers first, before you continue with the engine tier installation and configuration. The engine tier installation requires that the metadata repository tier and services tier are installed first, unless you install them all at the same time in a single pass of the installation program. 8. Run the InfoSphere Information Server installation program on the primary server. When prompted by the installation program, specify the virtual host name. Whenever prompted for an installation directory, specify a path within the mount point. 9. Replicate the /etc/services entries on both servers. 10. 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 InfoSphere Information Server. You can use these scripts or modify them to fit your configuration. See High availability control scripts included with IBM InfoSphere Information Server on page 120. 11. Use the appropriate high availability software administration tools to complete the 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 resource group. b. If the services tier or metadata repository tier is included in the high availability configuration, add the InfoSvrServices script or its equivalent resource agent script to the resource group. 12. Test the setup by simulating different failures.
Example: Setting up an active-passive configuration by using IBM Tivoli System Automation for Multiplatforms
This example describes how to set up a two-server active-passive high availability configuration by using Tivoli System Automation for Multiplatforms.
107
This example configuration is built on two Red Hat Enterprise Linux Server servers. The servers are connected to each other over a single public network. Each server is also connected to a storage area network (SAN). All IBM InfoSphere Information Server components are installed on the SAN. At any given time, only one of the servers is active; that is, it hosts the InfoSphere Information Server components on the SAN. The other server is passive and does not access the SAN. Although this example is for Linux, most steps are identical in an AIX environment. Steps that differ are indicated. The following diagram illustrates the example configuration:
Computer A
Client tier
Public Network
Computer B
(Active)
Computer C
(Passive)
Engine tier
Services tier
Database instance HA management software
Separate network carrying heartbeat

HA management software
SAN
Database
Figure 36. Example of a two-server active-passive high availability configuration
In this example, the following software is used for each server: v Red Hat Enterprise Linux Server 64-bit v IBM InfoSphere Information Server, Version 8.5 v 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)
108
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 the servers, network, and storage (Tivoli System Automation for Multiplatforms example). 2. Install System Automation for Multiplatforms on each server in the cluster, and then create the first level automation domain. System Automation for Multiplatforms is bundled with the IBM DB2 database system installation package. See Installing the high availability software (Tivoli System Automation for Multiplatforms example) on page 110. 3. Define the virtual IP address. Then, configure System Automation for Multiplatforms so that the network adapters on the servers are appropriate and equivalent for the virtual IP address. See Setting up the virtual IP address (Tivoli System Automation for Multiplatforms example) on page 111. 4. Define the resource group, and then create the automation policy by using relationship definitions. Create a network tiebreaker. Finally, activate the resource group. See Defining and starting the resource group (Tivoli System Automation for Multiplatforms example) on page 112. 5. Create users and user groups on the SAN. Then, run the InfoSphere Information Server installation program. Finally, replicate the /etc/services entries on both servers. See Installing IBM InfoSphere Information Server in the cluster (Tivoli System Automation for Multiplatforms example) on page 115. 6. Set up scripts to start, stop, and monitor the servers. Then, create the application resources. See Setting up the high availability control scripts (Tivoli System Automation for Multiplatforms example) on page 116. 7. To test the configuration, simulate active server failures and network failures and observe the results. See Testing the configuration (Tivoli System Automation for Multiplatforms example) on page 117. Setting up the servers, network, and storage (Tivoli System Automation for Multiplatforms example): Set up the hardware. Then configure the network, and configure mount points to the storage area network (SAN). Finally, mount the SAN. About this task The two servers in this example contain one network interface each (en0). The en0 network interfaces are connected to each other through the external network cloud that forms the public network. The following static IP addresses are assigned to the en0 adapters on the active and passive servers: v Active server (host name myprimary): 192.0.2.0 v Passive server (host name mysecondary): 192.0.2.1 In the following examples, you can express either of the IPv4 addresses as IPv6 addresses. For example, you can express 192.0.2.0 as ::ffff:192.0.2.0. Procedure 1. Set up the servers, network, and storage hardware.
109
2. Adjust kernel parameters and user limits identically on both servers. For information about these adjustments, see Modifying kernel parameters and user limits (AIX ) on page 99. 3. Open the /etc/hosts file on each server. In each file, verify that the active and passive server names are mapped to their corresponding public IP addresses. For example:
192.0.2.0 192.0.2.1 myprimary.example.com mysecondary.example.com myprimary mysecondary
If the host names are defined in the /etc/hosts file, the servers can identify each other if a DNS server failure occurs. All servers in the cluster must have the same entries in this file. In addition, all servers must have static IP addresses. 4. Validate that the active and passive servers can ping each other successfully over the public network: For example:
ping myprimary ping mysecondary
5. Create identical directories on each server to be used as the mount points for the shared SAN. Give the directories permissions of 775:
mkdir chmod mkdir chmod /opt/IBM 775 /opt/IBM /home 775 /home
6. Open the /etc/fstab file on each server. AIX: The file name is /etc/filesystems. 7. In each file, define the mount points for the shared SAN. For each mount point, specify the noauto option to prevent the mount point from being automatically mounted on more than one server in the cluster. For example:
192.0.2.2:/newfs 192.0.2.2:/newfs /opt/IBM /home nfs nfs defaults defaults 0 0 0 0
8. Mount the SAN on each server. 9. Create the following directories, with identical local user permissions: v v v v /opt/IBM/InformationServer/Server/Projects /opt/IBM/InformationServer /opt/IBM/WebSphere /opt/IBM/db2
Installing the high availability software (Tivoli System Automation for Multiplatforms example): Install IBM Tivoli System Automation for Multiplatforms on each server in the cluster, and then create the first level automation domain. System Automation for Multiplatforms is bundled with the IBM DB2 database system installation package. Procedure 1. 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_SCOPE environment variable is set to 2 for all users. 3. On each server that is to be part of the automation domain, run the preprpnode command to prepare security on the server so that it can be defined in a peer domain.
110
/usr/sbin/rsct/bin/preprpnode myprimary mysecondary
4. Create the automation domain. In the example, a single automation domain named ha_domain is created that contains the myprimary and mysecondary servers. To create the domain, run the mkrpdomain command on one of the servers (you can choose either server):
mkrpdomain ha_domain myprimary mysecondary
After this command is run once on a server, any Tivoli System Automation for Multiplatforms or Reliable Scalable Cluster Technology (RSCT) command can be issued from any server in the automation domain. 5. The newly created automation domain has an operational state (OpState) of offline. Run the startrpdomain command to bring the domain online:
startrpdomain ha_domain
Setting up the virtual IP address (Tivoli System Automation for Multiplatforms example): Define the virtual IP address. Then, configure IBM Tivoli System Automation for Multiplatforms so that the network adapters on the servers are appropriate and equivalent for the virtual IP address. About this task In the following examples, a file named myserviceip.cfg is created that defines a virtual IP address named haip. The IPAddress value is the network alias IP address, which can be an IPv4 address or an IPv6 address. In the following examples, you can express the IPv4 address 192.0.2.10 as the IPv6 address ::ffff:192.0.2.10. Procedure 1. 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 the address. The NetMask value is the network mask of this IP address:
PersistentResourceAttributes:: NodeNameList={"myprimary", "mysecondary"} Name="haip" NetMask=255.255.255.128 IPAddress=192.0.2.10 ResourceType=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.ServiceIP resource 1: Name = "haip" ResourceType = 0 AggregateResource = "0x2029 0xffff 0x8657b47c 0x9cbcbccb 0x918205be 0xc296f798" IPAddress = "192.0.2.10" NetMask = "255.255.255.128" ProtectionMode = 1 NetPrefix = 0 ActivePeerDomain = "ha_domain" NodeNameList = {"mysecondary"} resource 2: Name = "haip"
111
ResourceType AggregateResource IPAddress NetMask ProtectionMode NetPrefix ActivePeerDomain NodeNameList resource 3: Name ResourceType AggregateResource IPAddress NetMask ProtectionMode NetPrefix ActivePeerDomain NodeNameList
= = = = = = = = = = = = = = = = =
0 "0x2029 0xffff 0x8657b47c 0x9cbcbccb 0x918205be 0xc296f798" "192.0.2.10" "255.255.255.128" 1 0 "ha_domain" {"myprimary.example.com"} "haip" 1 "0x3fff 0xffff 0x00000000 0x00000000 0x00000000 0x00000000" "192.0.2.10" "255.255.255.128" 1 0 "ha_domain" {"myprimary.example.com","mysecondary"}
4. Run the mkequ command to create an equivalency definition that specifies the network adapters that are to carry the virtual IP address. For example, the following 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 MemberClass Resource:Node[Membership] SelectString SelectFromPolicy MinimumNecessary Subscription Color ActivePeerDomain ConfigValidity = = = = = = = = = = ha_nieq IBM.NetworkInterface {eth0:myprimary.example.com,eth0:mysecondary} "" ANY 1 {} 0 ha_domain
6. On both servers, in the /etc/hosts file, add the mapping for the virtual host name to the virtual IP address. For example:
192.0.2.10 harg harg.example.com
Defining and starting the resource group (Tivoli System Automation for Multiplatforms example): Define the resource group, and then create the automation policy by using relationship definitions. Create a network tiebreaker. Finally, activate the resource group. Procedure 1. Run the mkrg command to create a resource group. In this configuration example, the resource group that is created is named harg:
mkrg harg
2. Run the addrgmbr command to add the virtual IP address and application resources to the resource group.
addrgmbr -g harg IBM.ServiceIP:haip
3. Run the lsrg command to verify the resource group:

lsrg -m
112
The command displays the resource group definition.

Displaying Member Resource information: Class:Resource:Node[ManagedResource] Mandatory MemberOf OpState WinSource Location IBM.ServiceIP:haip True harg offline Nominal myprimary
4. Run the mkrel command to define the relationship between the virtual IP resource (haip) and the network interface equivalency (ha_nieq). The virtual IP 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_nieq Class:Resource:Node[Source] = IBM.ServiceIP:haip ResourceGroup[Source] = harg
6. Create a network quorum (tiebreaker). The tiebreaker ensures that Tivoli System Automation for Multiplatforms can decide which node still owns the cluster if communication between the nodes is lost. This safeguard prevents processes from 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 in either IPv4 format or IPv6 format. For example, you can use the address 192.0.2.0 or its equivalent IPv6 address ::ffff:192.0.2.0.
cat /usr/sbin/cluster/netmon.cf 192.0.2.0 | ::ffff:192.0.2.0 192.0.2.1 | ::ffff:192.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) can be any valid IP address that responds to the ping command from both nodes. 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.TieBreaker resource 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 = 0 HeartbeatPeriod = 0 PreReserveWaitTime = 0 PostReserveWaitTime = 30 NodeInfo = {} ActivePeerDomain = "ha_domain"
113
ConfigChanged resource 2: Name Type DeviceInfo ReprobeData ReleaseRetryPeriod HeartbeatPeriod PreReserveWaitTime PostReserveWaitTime NodeInfo ActivePeerDomain ConfigChanged resource 3: Name Type DeviceInfo ReprobeData ReleaseRetryPeriod HeartbeatPeriod PreReserveWaitTime PostReserveWaitTime NodeInfo ActivePeerDomain ConfigChanged
= 0 = = = = = = = = = = = = = = = = = = = = = = "Fail" "Fail" "" "" 0 0 0 0 {} "ha_domain" 0 "Operator" "Operator" "" "" 0 0 0 0 {} "ha_domain" 0
7. Run the chrg command to activate the resource group and all of the resources that are defined as its members:
chrg -o online harg
8. Run the lsrg command to verify the status of the resource group:
lsrg -g harg
The command displays information for the specified resource group.

Displaying Resource Group information: For Resource Group "harg". Resource Group 1: Name = harg MemberLocation = Collocated Priority = 0 AllowedNode = ALL NominalState = Online ExcludedList = {} Subscription = {} Owner = Description = InfoLink = Requests = {} ActivePeerDomain = ha_domain OpState = Online TopGroup = harg ConfigValidity = 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:harg 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.
114
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 group name.
rgreq -o move -n mysecondary harg
c. Run the lssam command again to check the status of the cluster:
lssam
If the failover was successful, the command output indicates that the primary node is now offline and the secondary node is online.
Online IBM.ResourceGroup:harg 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 harg
f. Run the lssam command again to check the status of the cluster:
lssam
If the failover was successful, the command output indicates that the secondary node is now offline and the primary node is online.
Online IBM.ResourceGroup:harg Nominal=Online - Online IBM.ServiceIP:haip |- Online IBM.ServiceIP:haip:myprimary - Offline IBM.ServiceIP:haip:mysecondary
Installing IBM InfoSphere Information Server in the cluster (Tivoli System Automation for Multiplatforms example): Create users and user groups on the storage area network (SAN). Then, run the InfoSphere Information Server installation program. Finally, replicate the /etc/services entries on both servers. About this task The configuration for this task matches Scenario C, which depicts a two-server active-passive high availability configuration. Procedure 1. On the storage area network (SAN), create all users and user groups. The following sample AIX commands create some of the administrator user accounts and groups:
/usr/bin/mkgroup /usr/bin/mkgroup /usr/bin/mkgroup /usr/bin/mkgroup /usr/bin/mkgroup /usr/bin/mkgroup /usr/bin/mkuser /usr/bin/mkuser /usr/bin/mkuser /usr/bin/mkuser /usr/bin/mkuser /usr/bin/mkuser id=202 id=203 id=204 id=205 id=206 id=207 db2iadm1 db2fadm1 dasadm1 xmeta iauser dstage groups=db2iadm1 groups=db2fadm1 groups=dasadm1 groups=xmeta groups=iauser groups=dstage home=/home/db2inst1 home=/home/db2fenc1 home=/home/dasusr1 home=/home/xmeta home=/home/iauser home=/home/dsadm db2inst1 db2fenc1 dasusr1 xmeta iauser dsadm
pgrp=db2iadm1 pgrp=db2fadm1 pgrp=dasadm1 pgrp=xmeta prgp=iauser pgrp=dstage
115
For details about creating administrator users and groups, see Setting up administrator and owner accounts on page 100. 2. Run the InfoSphere Information Server installation program in graphical mode. See Installing InfoSphere Information Server by using the wizard. Whenever you are prompted for a directory, choose a directory from the base directory mount point (/opt/IBM). On the High Availability Server Cluster Configuration page, click This is an active-passive server cluster configuration. In the Virtual host name field, enter the virtual host name (harg.example.com in this example). 3. Let the installation program complete. 4. Replicate the /etc/services entries on both servers. Setting up the high availability control scripts (Tivoli System Automation for Multiplatforms example): Set up scripts to start, stop, and monitor the servers. Then, create the application resources. About this task Several sample high availability control scripts are supplied with IBM InfoSphere Information Server. These scripts are used in this example. See High availability control scripts included with IBM InfoSphere Information Server on page 120. Procedure 1. Copy the script files to a directory on the storage area network (SAN). For example: /opt/IBM/hascripts 2. 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=60 MonitorCommandTimeout=60 NodeNameList={"myprimary","mysecondary"} StartCommandTimeout=240 StopCommandTimeout=240 UserName="root" ResourceType=1
3. Run the mkrsrc command to create the application resource for the services tier:
mkrsrc -f /opt/IBM/hascripts/InfoSvrServices.IBM.Application IBM.Application
4. Create an application resource configuration file for the engine tier. The following sample file defines an application resource for the engine tier. The file 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=60 MonitorCommandTimeout=60
116
NodeNameList={"myprimary","mysecondary"} StartCommandTimeout=240 StopCommandTimeout=240 UserName="root" ResourceType=1
5. Run the mkrsrc command to create the application resource for the engine tier:
mkrsrc -f /opt/IBM/hascripts/InfoSvrEngine.IBM.Application IBM.Application
6. Run the rgreq command to lock the harg resource group:

rgreq -o lock harg
7. Run the addrgmbr command to add the services tier application resource to the resource group harg that was created:
addrgmbr -g harg IBM.Application:ServicesApp
8. Run the addrgmbr command to add the engine tier application resource to the resource group harg that was created:
addrgmbr -g harg IBM.Application:EngineApp
9. Run the mkrel command to define the relationship between the InfoSphere Information Server services tier application resource (ServicesApp) and the virtual 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 InfoSphere Information Server engine tier application resource (EngineApp) and the virtual 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_nieq Class:Resource:Node[Source] = IBM.ServiceIP:haip ResourceGroup[Source] = harg Managed Relationship 2: Name Class:Resource:Node[Source] ResourceGroup[Source] Managed Relationship 3: Name Class:Resource:Node[Source] ResourceGroup[Source] rgreq -o unlock harg = ServicesApp_startafter_haip = IBM.Application:ServicesApp = harg = EngineApp_startafter_haip = IBM.Application:EngineApp = harg
12. Run the rgreq command again to unlock the resource group:
Testing the configuration (Tivoli System Automation for Multiplatforms example): To test the configuration, simulate active server failures and network failures and observe the results.
117
About this task During the test, run the lssam command periodically to view the status of the servers in the cluster. When the active server in the cluster is operational and the passive server is on standby, the lssam command displays output like this example:
Online IBM.ResourceGroup:harg 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 - Online IBM.ServiceIP:haip |- Online IBM.ServiceIP:haip:myprimary - Offline IBM.ServiceIP:haip:mysecondary
The first line indicates the resource group. In the preceding example, the resource group name is harg. The following lines indicate the status of the member resources: EngineApp (the IBM InfoSphere Information Server engine tier control application), ServicesApp (the InfoSphere Information Server services tier and metadata repository tier control application), and haip (the virtual IP resource). Resources and constituent servers 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. Procedure 1. 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 other server and remain online there. 3. Run the lssam command to verify that the failover was successful. The command output is similar to the following text:
Online IBM.ResourceGroup:harg 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 to the passive server (mysecondary). Also, the virtual IP resource failed over successfully. Verify that the formerly active server (myprimary) is now in the failed offline state. 4. Use an InfoSphere Information Server client to access the system and verify that 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:
118
Online IBM.ResourceGroup:harg 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 is displayed as shown in the preceding text. 7. Simulate a power failure on the formerly passive (mysecondary) server. Verify that all resources fail over to the myprimary server and remain online there. 8. Run the lssam command to verify that the failover was successful. The command output is similar to the following text:
Online IBM.ResourceGroup:harg 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 to the myprimary server. Also, the virtual IP resource failed over successfully. Verify that the mysecondary server is now in the failed offline state. You might need to run the command several times before the status is displayed as shown in the preceding text. 9. Use an InfoSphere Information Server client to access the system and verify that 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:harg 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 - Online IBM.ServiceIP:haip |- Online IBM.ServiceIP:haip:myprimary - Offline IBM.ServiceIP:haip:mysecondary
Verify that the mysecondary server is now in the offline state. You might need to run the command several times before the status is displayed as shown in the preceding text. 12. Repeat steps 1 through 11. During this test cycle, restart each server in turn instead of disabling power. For example, to restart a server, you can log in to the server as root and run the reboot command. 13. Repeat steps 1 through 11. During this test cycle, simulate a network failure by disconnecting the public network cable from each server in turn.
119
High availability control scripts included with IBM InfoSphere Information Server
Several sample high availability control scripts are included with InfoSphere Information Server. To enable your high availability software to start or stop tiers and components, set up these files as application resources within the high availability software. These scripts are installed by the InfoSphere Information Server installation program in the following directory:
Operating system AIX Directory 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 lists and describes the scripts that are available:
Table 52. Sample scripts that are supplied with InfoSphere Information Server Script InfoSvrEngine Description Starts or stops the InfoSphere Information Server engine tier. Calls ISFAgents as part of its operation. Starts or stops the InfoSphere Information Server services tier. Calls ISFRepos and ISFServer scripts as part of its operation. Calls the NodeAgents.sh script to start or stop InfoSphere Information Server ASB node agents. Calls the MetadataServer.sh script to start or stop IBM WebSphere Application Server. Called by the InfoSvrServices script in an active-passive configuration where an IBM DB2 database system hosts the metadata repository tier. Starts or stops a local DB2 database system instance. The DB2 database system must run on the same server as other InfoSphere Information Server components. Assumes that the DB2 database system is installed on shared storage that is mounted identically on both servers.
InfoSvrServices
ISFAgents
ISFServer ISFRepos
The set of scripts you use depends on which tiers you configure in the active-passive high-availability configuration. The following table lists the scripts to use based on the tiers that you include in your configuration:
Table 53. Tiers and resource agent scripts Tier Engine Sample resource agent scripts v InfoSvrEngine v ISFAgents Services v InfoSvrServices v ISFServer
120
Table 53. Tiers and resource agent scripts (continued) Tier Metadata repository Sample resource agent scripts v InfoSvrServices v ISFRepos
Installing the metadata repository database

You can install the metadata repository database when you install IBM InfoSphere Information Server. Alternatively, you can use scripts to manually create the metadata repository database in an existing database instance. The metadata repository database is a shared component that stores design-time, runtime, glossary, and other metadata for product modules in the InfoSphere Information Server suite.
Installing DB2 database software

Preinstall the DB2 database system if necessary before you run the IBM InfoSphere Information Server installation program.
About this task

To preinstall DB2 before you run the InfoSphere Information Server installation program, run the DB2 database system installation program that is included in the InfoSphere Information Server installation media. To learn what DB2 installation packages are included with your InfoSphere Information Server installation package, see the system requirements on the product support site at www.ibm.com/support/docview.wss?uid=swg27021833. 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 Server v To build a DB2 database cluster or high availability disaster recovery (HADR) architecture for high availability
Procedure
1. Obtain a DB2 database system installation package from IBM. On the installation media, the DB2 database system installation packages are in the following directories:
Operating system AIX Directory installable_image_directory/payloads/ Shared/DB2/payload
2. Install the DB2 database system as described in the DB2 database system documentation:
Database version IBM DB2 Database, Version 9.5 IBM DB2 Database, Version 9.7 Link publib.boulder.ibm.com/infocenter/db2luw/ v9r5/index.jsp publib.boulder.ibm.com/infocenter/db2luw/ v9r7/index.jsp
121
3. Optional: If you are using DB2 diagnostics, run the following command to set the DB2 Database Monitor Heap size to 192 or greater:
db2 update dbm cfg using MON_HEAP_SZ 192 immediate
Restart DB2 for changes to take effect. Note: The DB2 Database Monitor Heap is used for various database event monitors and snapshots. These monitoring tools do not work under the default size setting.
Setting up an existing installation of DB2 database software

To prepare an existing DB2 database system for IBM InfoSphere Information Server, use InfoSphere Information Server installation program or scripts to create the metadata repository database.
Before you begin

To configure the DB2 database system, 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?uid=swg27021833. v It must be located on a computer that is accessible by the computers where the services tier and engine tiers are installed. v You must run the installation program locally on the computer where the DB2 instance is installed. 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 not supported for use with InfoSphere Information Server. v DB2 Fault Monitoring components must be enabled. Make sure that the path to the fault monitor (db2fmcd) is included in the /etc/inittab file. The db2fmcd command must point to the actual executable location. For example:
fmc:234:respawn:/ul/IBM/db2/V9/bin/db2fmcd #DB2 Monitor Coordinator
Before you proceed, complete all tasks that are listed in Setting up the tier computers on page 92. Configuring an existing installation of DB2 database software by using the installation program: You can use the IBM InfoSphere Information Server installation program to configure an existing IBM DB2 database system installation for InfoSphere Information Server. Before you begin Complete all tasks that are listed in Setting up the tier computers on page 92.
122
About this task Attention: The InfoSphere Information Server installation program runs the following commands when it configures the DB2 database system. These changes affect all databases in the DB2 instance:
db2set DB2_INLIST_TO_NLJN=YES db2set DB2_USE_ALTERNATE_PAGE_CLEANING=ON db2set DB2_REDUCED_OPTIMIZATION=YES db2 update dbm cfg using MON_HEAP_SZ 192 immediate
Procedure 1. Open the services file and ensure that the following line appears in the file. This line ensures that the DB2 installation instance is defined. If the line does not appear in the file, add the line and save the file:
db2c_instanceName port/tcp
Where instanceName is the DB2 instance name. port is the port number of the DB2 instance.The services file is located in the following directory:
Operating system AIX Directory /etc
2. Run the installation program:

Operating system AIX Command ./setup [-verbose]
The -verbose option is optional. The option causes the installation program to display 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 the graphical interface:
======> Enter one of the following URLs to your web browser to begin the installation process: http://localhost:8080/ISInstall https://localhost:8443/ISInstall
3. Open a Web browser on the computer or on a remote computer, and navigate to one of the addresses that are listed in the messages that are displayed in the previous step. The installation program automatically launches the default Web browser on the local computer and navigates to the HTTP address. A Login Installation window is displayed in the Web browser window. 4. To display messages in a language other than English, select the language in the Select a language menu, and click Login. This language selection only applies to this installation session. Later in the installation process, you select the language to apply to the InfoSphere Information Server installation. 5. 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 found issues that might cause problems with the installation, it is marked WARNING in the page. 6. Specify the required information for the DB2 database system: v In the Tier selection page, click Metadata repository.
123
v In the Database Management System Selection page, click Use an existing DB2 instance on this computer. Select the path to the database instance in the menu. In the Instance port number menu, select the port number of the DB2 instance. v In the IBM DB2 Instance User page, specify the name of the DB2 instance owner account that you created. See Setting up administrator and owner accounts on page 100. v In the DB2 Fenced User Information page, specify the name of the DB2 fenced user account that you created. v In the DB2 Administrator User Information page, specify the name of the DB2 administrator server user account that you created. v In the Metadata Repository Configuration page, specify the metadata repository database information and database owner account information. v In the Staging Area Configuration page, enter the username and password to use for the staging area tablespace user. v If you are installing InfoSphere Information Analyzer, specify the analysis database and owner information in the IBM InfoSphere Information Analyzer Repository Configuration page. 7. If you use 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 event monitors and snapshots. These monitoring tools do not work under the default size 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
8. Restart DB2 for changes to take effect. Configuring an existing installation of DB2 database software by using scripts (AIX ): You can use an existing installation of a DB2 database to create a metadata repository for InfoSphere Information Server. About this task For a DB2 9.5 or DB2 9.7 installation, use the scripts in the following situations: v You are configuring a DB2 cluster for the databases. See Metadata repository tier clustering for high availability on page 126. 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. Attention: Do not change the name of the tablespace named XMETA. This name is used internally by InfoSphere Information Server.
124
Attention: The scripts run the following commands when configuring the DB2 database system. These changes affect all databases in the DB2 instance:
db2set DB2_INLIST_TO_NLJN=YES db2set DB2_USE_ALTERNATE_PAGE_CLEANING=ON db2set DB2_REDUCED_OPTIMIZATION=YES
Procedure 1. Navigate to the install_dir\DatabaseSupport directory of the InfoSphere Information Server installation media, where install_dir is the directory where you extracted the InfoSphere Information Server media.
Database version DB2 9.5 DB2 9.7 Directory install_dir\DatabaseSupport\UNIX_Linux\ MetadataRepository\DB2_LUW_9_5 install_dir\DatabaseSupport\UNIX_Linux\ MetadataRepository\DB2_LUW_9_7
2. Open the script file in a text editor and make the following changes. On 64-bit platforms, you must edit both of the following scripts:
DB2 instance version 32-bit 64-bit Script files create_xmeta_db.sql create_xmeta_db.sql configure_xmeta_db_64bit.sql
a. Replace all occurrences of @DATABASE_NAME@ (including the @ symbols) with the name of the database that you want to create. For example, replace @DATABASE_NAME@ with your database name:
xmeta
b. Replace all occurrences of @INSTALL_ROOT@ (including the @ symbols) with the path to the root directory where your DB2 database is installed. The default root directory is /var/lib. For example, replace @INSTALL_ROOT@ with the path to the root directory for your DB2 database:
/var/lib
When you run the script, DB2 creates a directory under the root directory where your database is installed. This directory contains the data files for your database. The default directory is /var/lib/db2inst1/NODE0000. c. Replace all occurrences of @DATABASE_ALIAS@ (including the @ symbols) with the name of the database that you want to create. For example, replace @DATABASE_ALIAS@ with your database name:
xmeta
d. Replace all occurrences of @DATABASE_USERNAME@ (including the @ symbols) with the name of the operating system user that you want to have access to the database. For example, replace @DATABASE_USERNAME@ with the operating system user name:
xmeta
3. Run the operating system script to invoke the SQL script: a. Log on as the DB2 instance owner. b. Run the following command:
create_xmeta_db.sh [logfile]
125
logfile is the name of the file where you want to save the results of running the command. This argument is optional. 4. Open the db2_grant_Permissions.sql file in a text editor and make the following changes: a. Replace all occurrences of @DATABASE_NAME@ (including the @ symbols) with the name of the database that you created. For example, replace @DATABASE_NAME@ with your database name:
xmeta
b. Replace all occurrences of @DATABASE_USERNAME@ (including the @ symbols) with the name of the user that you want to grant access to the staging area schema. This user must be different from the operating system user that you specified in step 2d. For example, replace @DATABASE_USERNAME@ with the user name for the staging area schema:
xmetasr
5. Run the operating system script to invoke the SQL script: a. Log on as the DB2 instance owner. b. Run the following command:
configure_staging_area.sh [logfile]
logfile is the name of the file where you want to save the results of running the command. This argument is optional. 6. Restart DB2.
Metadata repository tier clustering for high availability

To provide high availability for your metadata repository database, you can set up the database within a database cluster. IBM InfoSphere Information Server does not support clustered configurations of the IBM InfoSphere Information Analyzer database or the IBM InfoSphere QualityStage Match Designer database. Configuring the metadata repository database in an IBM DB2 cluster: Use this road map to create an IBM InfoSphere Information Server configuration in which 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 in the following table. If you want to integrate InfoSphere Information Server into an existing DB2 database cluster, read through the task topics to make sure that your cluster configuration is compatible with InfoSphere Information Server.
Table 54. Setting up an IBM DB2 database cluster Task To set up a DB2 database cluster, first configure the servers, storage, and network. (Optional) Install high availability (HA) software to monitor the health of the servers and to manage failover. Before you install InfoSphere Information Server, install the DB2 database system, create a cluster, and create the metadata repository database on the primary node in the cluster. Link for more information Preparing the servers, file system, and storage on page 127 Installing high availability software on DB2 database system servers on page 128 Installing the DB2 database system and creating the cluster and metadata repository database on page 129
126
Table 54. Setting up an IBM DB2 database cluster (continued) Task Create users and groups. Run the InfoSphere Information Server installation program. To allow IBM WebSphere Application Server to reconnect to the standby server smoothly, configure Automatic Client Reroute. Link for more information Running the installation program for a setup that includes DB2 clustering on page 130 Configuring automatic client reroute on page 131
To enable WebSphere Application Server to Specifying the alternate database address communicate with more than one server, use and port for IBM WebSphere Application the WebSphere Application Server Server on page 142 administrative console to specify an alternate database address and port. Verify the state of the cluster. Verifying the IBM DB2 database cluster on page 135
InfoSphere Information Server does not support cluster configurations of the IBM InfoSphere Information Analyzer analysis database or IBM InfoSphere QualityStage Match Designer database. To deploy a clustered topology, you must have a solid understanding of network technologies such as protocols, layers, devices, and so on. Clustered topologies are technically complex, and require expertise to implement successfully. Preparing the servers, file system, and storage: To set up an IBM DB2 database cluster, first configure the servers, storage, and network. For high availability, the cluster must include at least two physically separate computers. If possible, use identical hardware with identical internal storage, memory, and processing power. The metadata repository database cannot be partitioned. They must exist in a non-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. A secondary server is idle, or in standby mode, ready to take over the workload if there is a failure on the primary system. The servers must be able to communicate with each other over high-speed networks. To minimize single points of failure, each server must have redundant connections to at least two physically separate high-speed networks. To support failover when a problem occurs, the HA software creates a heartbeat signal between the servers. Set up at least two more physically separate networks for this signal. These networks can be serial or other networks. The networks that carry the heartbeat signal must be physically separate and isolated from the high-speed networks. The following diagram shows a two-server active-passive architecture with minimum network redundancy. The diagram shows two servers (Node 1 and Node 2). Each server has four network interfaces (en0, en1, en2, and en3). There are two redundant high-speed networks (Network A and Network B). On each
127
server, two network interfaces are connected to Network A, and two network interfaces are connected to Network B. This arrangement creates redundancy at the network interfaces and within the overall high-speed network architecture. Each server also has two serial interfaces (tty1 and tty2). Each serial interface on one server is connected to a serial interface on the other. This arrangement creates a redundant serial "ring" network for the heartbeat signal. Create the DB2 database system file system on disk partitions that are shared by all cluster nodes. The disk partitions must be on highly available media such as a storage area network (SAN).
en0 tty2 en0 en1 Node 1 en2 tty1 en3 en3 en1
tty2
Node 2 en2 tty1
Serial Network A Network B
Figure 37. Two servers with redundant connections to networks
For more specific information about DB2 database cluster servers, storage, or network 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 system servers: You can optionally install and configure IBM Tivoli System Automation for Multiplatforms (SA MP) to monitor the health of the IBM DB2 database system servers and to manage failover. Tivoli System Automation for Multiplatforms software is shipped as part of the DB2 database system installation package. This high availability (HA) software monitors the health of the servers, the network, the operating system, and selected software components. If a critical item fails, the software triggers a failover to the standby server. Then the automatic client reroute feature causes IBM WebSphere Application Server to connect to another server in the cluster.
128
If you plan to implement SA MP, install it before you install and configure IBM InfoSphere Information Server. When you install SA MP, you configure a floating IP address that is shared between the servers. When you configure automatic client reroute, 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 a failure occurs on the primary server, the database administrator must manually detect the failure and perform a failover. Then automatic client reroute redirects WebSphere Application Server to the new server. To install and configure the software, see the DB2 database system documentation: v Installing and upgrading the SA MP Base Component with the DB2 installer 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.admin.ha.doc/doc/t0051289.html v Installing IBM Tivoli System Automation for Multiplatforms (SA MP) Base Component 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.qb.server.doc/doc/t0051374.html For an example of how to set up SA MP for a simple active-passive server configuration, see Example: Setting up an active-passive configuration by using IBM Tivoli System Automation for Multiplatforms on page 107. Installing the DB2 database system and creating the cluster and metadata repository database: Before you install IBM InfoSphere Information Server, install the IBM DB2 database system, create a cluster, and create the metadata repository database on the primary node. Before you begin A separate copy of the DB2 database system must be installed on each server. Procedure 1. 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. v Within the installation media, the DB2 database system installation packages are in the following directories:
Operating system AIX Directory payloads/Shared/DB2/payload
For information about installing the DB2 database system, see the DB2 database system documentation: v DB2 Database, Version 9.5 for Linux, UNIX, and Windows: publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp
129
v DB2 Database, Version 9.7 for Linux, UNIX, and Windows: publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp The IBM InfoSphere Information Server installation package includes installation packages for DB2. To preinstall DB2 before you run the InfoSphere Information Server installation program, you can run the DB2 database system installation program that is included in the InfoSphere Information Server installation media. To learn what DB2 installation packages are included with your InfoSphere Information Server installation package, see the system requirements at www.ibm.com/support/docview.wss?uid=swg27021833. 2. Set up the cluster. The metadata repository database cannot be partitioned. The database must exist in a non-partitioned environment. For this reason, you cannot set up the system in a mutual takeover configuration. You must set up an idle standby configuration. In this configuration, a primary system processes all the workload. A secondary system is idle, or in standby mode, ready to take over the workload if there is a failure on the primary system. For information about creating a DB2 database cluster, see the DB2 database system 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 DB2 Database, 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 DB2 database system. To create the database, use the scripts that are supplied with the InfoSphere Information Server installation media. Locate the database file system on a disk partition that is shared by all nodes in the cluster. The disk partition must be on highly available media such as a storage area network (SAN).
Operating system AIX Procedure Configuring an existing installation of DB2 database software by using scripts (AIX)
Running the installation program for a setup that includes DB2 clustering: Create administrator and component owner accounts and groups. Run the IBM InfoSphere Information Server installation program. Procedure 1. 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 are identical on both servers. The following sample commands create some of the accounts and groups:
130
Operating system AIX
Commands /usr/bin/mkgroup /usr/bin/mkgroup /usr/bin/mkgroup /usr/bin/mkgroup /usr/bin/mkgroup /usr/bin/mkgroup id=202 id=203 id=204 id=205 id=206 id=207 db2iadm1 db2fadm1 dasadm1 xmeta iauser dstage
/usr/bin/mkuser pgrp=db2iadm1 groups=db2iadm home=/home/db2inst1 db2inst1 /usr/bin/mkuser pgrp=db2fadm1 groups=db2fadm home=/home/db2fenc1 db2fenc1 /usr/bin/mkuser pgrp=dasadm1 groups=dasadm1 home=/home/dasusr1 dasusr1 /usr/bin/mkuser pgrp=xmeta groups=xmeta home=/home/xmeta xmeta /usr/bin/mkuser prgp=iauser groups=iauser home=/home/iauser iauser /usr/bin/mkuser pgrp=dstage groups=dstage home=/home/dsadm dsadm
For details on creating administrator users and groups, see Setting up administrator and owner accounts on page 100. 2. Run the InfoSphere Information Server installation program in graphical mode. Complete the entire InfoSphere Information Server installation as described in Scenario D: Clustered metadata repository tier and services tier configuration on page 51. Configuring automatic client reroute: For IBM WebSphere Application Server to reconnect to the standby server smoothly in a DB2 clustered or HADR configuration, configure automatic client reroute. About this task In an IBM InfoSphere Information Server installation with a clustered DB2 database system setup, automatic client reroute can redirect WebSphere Application Server to connect to an alternate server when the primary server fails. The alternate server is preregistered within automatic client reroute. When the failure occurs, automatic client reroute first tries to reconnect to the primary database. If the connection fails, automatic client reroute establishes a connection with the standby server. If an update, deletion, or insertion transaction was taking place and the failure occurred before the transaction was committed, the user receives an error message. When the user tries the transaction again, the standby server handles the transaction. If a read transaction was taking place, the read transaction is automatically run on the standby server, and no error message is displayed. Procedure 1. Log in to the primary node.
131
2. Run the following command to configure automatic client reroute for the database. The standby_IP can be an IPv4 address or an IPv6 address, as shown in the following example:
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 | ::ffff:192.0.2.7 port 60000
Specifying the alternate address and port for a DB2 database to connect to IBM WebSphere Application Server: For IBM WebSphere Application Server to communicate with more than one server, specify an alternate address and port for a DB2 database. Procedure 1. 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 JDBC Providers. The JDBC providers page opens. 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 indicates that failover occurred. For more information, see the DB2 database system documentation. j. Click OK. k. Click New.
132
l. In the Name field, type maxRetriesForClientReroute m. In the Value field, type 2. This parameter sets the number of connection retry 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 you choose 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 JDBC Provider. The JDBC providers page opens. 8. Under Additional Properties, click Data sources. 9. Repeat step 6 on page 132 for each data source that is listed in the window. 10. If your metadata repository is configured for active-passive failover, but you did not indicate the virtual host name for your metadata repository database in the IBM InfoSphere Information Server installation program, complete the following steps: a. Click Resources > JDBC > Data sources. b. In the Data sources panel, click the first data source that is listed. c. Under Common and required data source properties, update the server name to the virtual host name. d. Click Apply, then click OK. e. Repeat each step for every data source that is listed. f. Click Test connection. Ensure that you see a message that says, The test connection operation for data source data_source_name on server server_name at node node_name was successful. g. If a message displays that asks you to complete synchronization, follow the instructions. 11. Log out of the console. 12. Locate the ojb-conf.jar file on one of the following servers, depending upon your configuration: v If your installation includes a clustered implementation of WebSphere Application Server, locate the file on the server that hosts the WebSphere Application Server Deployment Manager. v Otherwise, locate the file on the server that hosts the services tier.
Operating system AIX Directories /opt/IBM/InformationServer/ASBServer/ apps/lib
133
13. Extract the ojb-conf.jar file in the temporary location by using the jar utility of a Java developer kit such as the one in WebSphere Application Server.
Operating system AIX Command 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
14. Open the repository_database.xml file by using a text editor. You add the alternate server name and port number to this file. 15. Locate all <jdbc-connection-descriptor> elements in the file that have a dbalias attribute. This first instance of 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="fa lse" jcd-alias="pojo" jdbc-level="2.0" password="{xor}tIakDPBAI X2Ao1nHR8j/+A==" platform="Db2" protocol="jdbc" subprotocol="db 2" useAutoCommit="2" username="{xor}tIakDPBAIX2Ao1nHR8j/+A=="> <connection-pool maxActive="21" validationQuery=""/> <object-cache class="org.apache.ojb.broker.cache.ObjectCach ePerBrokerImpl"/> </jdbc-connection-descriptor>
16. Modify the elements to include the client reroute information. Use the same server 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.1 6;clientRerouteAlternatePortNumber=50001;queryCloseImplicit=2;" default-connection="false" driver="com.ibm.db2.jcc.DB2Driver" e ager-release="false" ignoreAutoCommitExceptions="false" jcd-ali as="pojo" jdbc-level="2.0" password="{xor}tIakDPBAIX2Ao1nHR8j/+ A==" platform="Db2" protocol="jdbc" subprotocol="db2" useAutoCo mmit="2" username="{xor}tIakDPBAIX2Ao1nHR8j/+A=="> <connection-pool maxActive="21" validationQuery=""/> <object-cache class="org.apache.ojb.broker.cache.ObjectCach ePerBrokerImpl"/> </jdbc-connection-descriptor>
17. Save your changes and exit the text editor. 18. Navigate to the temporary directory that you created previously and compress the ojb-conf.jar file with the updated information.
Operating system AIX Command The following lines are part of a single command. The period (.) at the end of the command is required:/opt/IBM/WebSphere/ AppServer/java/bin/jar cf /opt/IBM/InformationServer/ASBServer/ apps/lib/ojb-conf.jar .
What to do next Run the FilePropagator utility to propagate the changes to the ojb-conf.jar file to WebSphere Application Server.
134
Running the FilePropagator utility in a clustered configuration (AIX ): To propagate changes to IBM WebSphere Application Server, you must run the FilePropagator utility. You typically run this utility after making configuration changes to WebSphere Application Server. Before you begin Use the isrecovery tool to back up InfoSphere Information Server components and data. See Backing up IBM InfoSphere Information Server components in the IBM InfoSphere Information Server Administration Guide for more information on how to run the isrecovery tool. About this task Attention: The FilePropagator utility requires 1.5 GB or more of temporary disk space to run. Ensure that the following directories have at least 1.5 GB of unused disk space before you run the FilePropagator utility:
Table 55. Temporary system directories that are used by the FilePropagator utility Operating system AIX Temporary directory /tmp
Procedure 1. From the command line, navigate to the install_dir/ASBServer directory, where install_dir is the directory where you installed InfoSphere Information Server. 2. Run the following commands to make a copy of the apps/lib directory and the apps/eclipse directory.
rm -r profile/informationServer/apps mkdir -p profile/informationServer/apps cp -r apps/lib apps/eclipse profile/informationServer/apps
3. Stop the WebSphere Application Server cluster. 4. From the command line, run the FilePropagator utility. Enter the following commands on a single line.
bin/FilePropagator.sh -user wasadmin_user -password wasadmin_password -srcDir profile/informationServer/apps -destDir informationServer/apps
wasadmin_user is the user name that you are using to log into the application server. wasadmin_password is the password for the user name that you specified for wasadmin_user. 5. Start the WebSphere Application Server cluster. Verifying the IBM DB2 database cluster: After you complete the cluster configuration and IBM InfoSphere Information Server installation, verify the state of the cluster.
135
Procedure 1. 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 database HADR configuration: Use this road map to create an IBM InfoSphere Information Server implementation in which the metadata repository database is set up within a DB2 database high availability disaster recovery (HADR) configuration. If you want to create a DB2 database HADR installation, complete the tasks in the following table. If you want to integrate InfoSphere Information Server into an existing HADR configuration, read through the task topics to make sure that your HADR configuration is compatible.
Table 56. Configuring the metadata repository database in a DB2 database HADR configuration. Task Configure the servers, the network, and the storage. Install DB2 database system on both servers in the configuration. Use the scripts in the installation media to configure the database on the primary server. Create administrator and component owner accounts and groups, and complete the InfoSphere Information Server installation and configuration. On the HADR primary server, configure the HADR variables and verify your settings. Back up the database from the primary server and restore it on the standby server. Then set HADR variables on the standby server. Link for more information Preparing the servers, storage, and network on page 137 Installing the DB2 database system and creating the metadata repository database on page 138 Running the installation program for a HADR configuration on page 139
Configuring the HADR primary server on page 139 Configuring the HADR standby server on page 140
To enable IBM WebSphere Application Server Specifying the alternate database address to communicate with either server in the and port for IBM WebSphere Application HADR setup, use the WebSphere Application Server on page 142 Server administrative console to specify an alternate database address and port. Start the HADR software on the standby server and then on the primary server. Starting HADR on page 146
136
Table 56. Configuring the metadata repository database in a DB2 database HADR configuration. (continued) Task Validate the HADR configuration and test the takeover function. Link for more information Validating the HADR configuration on page 147
InfoSphere Information Server does not support HADR configurations of the IBM InfoSphere Information Analyzer analysis database or the IBM InfoSphere QualityStage Match Designer database. To deploy a clustered or HADR topology, you must have a solid understanding of network technologies such as protocols, layers, devices, and so on. Clustered topologies are technically complex, and require expertise to implement successfully. Preparing the servers, storage, and network: To 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 least two physically separate computers. Use identical hardware with identical storage, memory, and processing power. The configuration must satisfy the following requirements: 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 no conflict. The ports on the primary and standby servers do not need to be identical. However, if the ports are identical, configuration is easier. The services file can be found in the following locations:
Operating system AIX Directory /etc/services
The following example shows HADR ports specified within the services file:
# HADR ports assigned by user ha_myhadr 51012/tcp ha_myhadr_int 51013/tcp
For more specific information about DB2 database HADR servers, storage, or network considerations, search for these terms in the IBM DB2 database system documentation: v IBM DB2 Database, Version 9.5 for Linux, UNIX, and Windows: publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp
137
v IBM DB2 Database, Version 9.7 for Linux, UNIX, and Windows: publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp Installing the DB2 database system and creating the metadata repository database: Before you install IBM InfoSphere Information Server, install the IBM DB2 database system on both servers and create the InfoSphere Information Server metadata repository database on the primary node. Before you begin A separate copy of the DB2 database system must be installed on each server. Procedure 1. 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 database system documentation: v IBM DB2 Database, Version 9.5 for Linux, UNIX, and Windows: publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp v IBM DB2 Database, Version 9.7 for Linux, UNIX, and Windows: publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp The IBM InfoSphere Information Server installation package includes installation packages for DB2. To preinstall DB2 before you run the InfoSphere Information Server installation program, you can run the DB2 database system installation program that is included in the InfoSphere Information Server installation media. To learn what DB2 installation packages are included with your InfoSphere Information Server installation package, see the system requirements at www.ibm.com/support/docview.wss?uid=swg27021833. Within the installation media, the DB2 database system installation packages are in the following directories:
Operating system AIX Directory payloads/Shared/DB2/payload
2. On the primary node, create the metadata repository database within the DB2 database system. To create the database, use the scripts that are supplied with the InfoSphere Information Server installation media. Locate the database file system on a disk partition that is shared by all nodes in the cluster. The disk partition must be on highly available media such as a storage area network (SAN).
Operating system AIX Procedure Configuring an existing installation of DB2 database software by using scripts (AIX)
138
Running the installation program for a HADR configuration: Create administrator and component owner accounts and groups. Run the IBM InfoSphere Information Server installation program. Procedure 1. Create identical administrator and component owner accounts and groups on both high availability disaster recovery (HADR) servers. Make sure that the group IDs and user IDs are identical on both servers. For details on creating administrator users and groups, see Setting up administrator and owner accounts on page 100. 2. Run the InfoSphere Information Server installation program in graphical mode. Complete the entire InfoSphere Information Server installation as described in Scenario D: Clustered metadata repository tier and services tier configuration on page 51. Configuring the HADR primary server: On 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 installation must be operational before you complete the HADR configuration. Complete HADR configuration as soon as the InfoSphere Information Server installation is operational. Procedure 1. 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_IP db2 update db cfg for database using hadr_remote_host standby_IP
The primary_IP address and the secondary_IP address can be an IPv4 address or an IPv6 address. For example:
db2 update db cfg for xmeta using hadr_local_host 192.0.2.6 | ::ffff:192.0.2.6 db2 update db cfg for xmeta using hadr_remote_host 192.0.2.7 | ::ffff:192.0.2.7
3. Run the following commands to specify the HADR primary and standby service names:
db2 update db cfg for database using hadr_local_svc primary_svc_name db2 update db cfg for database using hadr_remote_svc standby_svc_name
In the commands, the service names must match the HADR port names that are used in the services file. For example:
db2 update db cfg for xmeta using hadr_local_svc ha_myhadr db2 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 standby server:
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
139
5. Run the following command to specify the time (in seconds) that the HADR process 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 typically provides adequate response time for InfoSphere Information Server. Avoid choosing asynchronous mode (ASYNC) because ASYNC mode has the highest chance of transaction loss if the primary server fails. 7. Run the following command to specify the time (in seconds) that the HADR process 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 reorganization operations are logged. This logging allows indexes to be reconstructed during DB2 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:

For example:
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 HADR HADR HADR HADR HADR HADR HADR database role = STANDARD local host name (HADR_LOCAL_HOST) = myprimary.example.com local service name (HADR_LOCAL_SVC) = ha_myhadr remote host name (HADR_REMOTE_HOST) = mystandby.example.com remote service name (HADR_REMOTE_SVC) = ha_myhadr_int instance name of remote server (HADR_REMOTE_INST) = db2inst1 timeout value (HADR_TIMEOUT) = 120 log write synchronization mode (HADR_SYNCMODE) = SYNC
Configuring the HADR standby server:
140
Back 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 with its client application. Procedure 1. 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_directory cd temp_backup_directory db2 backup db database
For example:
mkdir mytempbackup cd mytempbackup db2 backup db xmeta
Note: You can store more than one database backup in the same temporary directory. 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 HADR primary server and standby server. In the command, specify the standby server for hadr_local_host. Specify the primary server for hadr_remote_host (the opposite of the settings on the primary server).
db2 update db cfg for database using hadr_local_host standby_IP db2 update db cfg for database using hadr_remote_host primary_IP
The primary_IP address and the secondary_IP address can be an IPv4 address or an IPv6 address. For example:
db2 update db cfg for xmeta using hadr_local_host 192.0.2.7 | ::ffff:192.0.2.7 db2 update db cfg for xmeta using hadr_remote_host 192.0.2.6 | ::ffff:192.0.2.6
7. On the standby server, run the following commands to specify the HADR primary and standby service names. In the command, specify the standby server port name for hadr_local_svc. Specify the primary server port name for hadr_remote_svc (the opposite of the settings on the primary server).
db2 update db cfg for database using hadr_local_svc standby_svc_name db2 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_int db2 update db cfg for xmeta using hadr_remote_svc ha_myhadr
141
8. On the standby server, run the following command to set up automatic client reroute. Specify the primary server IP address and port number in the command:
db2 update alternate server for database database using hostname primary_IP port port
For example:
9. On the standby server, 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 HADR HADR HADR HADR HADR HADR HADR database role = STANDARD local host name (HADR_LOCAL_HOST) = mystandby.example.com local service name (HADR_LOCAL_SVC) = ha_myhadr_int remote host name (HADR_REMOTE_HOST) = myprimary.example.com remote service name (HADR_REMOTE_SVC) = ha_myhadr instance name of remote server (HADR_REMOTE_INST) = db2inst1 timeout value (HADR_TIMEOUT) = 120 log write synchronization mode (HADR_SYNCMODE) = SYNC
Specifying the alternate database address and port for IBM WebSphere Application Server: For WebSphere Application Server to communicate with more than one server, specify an alternate database address and port. Procedure 1. 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 JDBC Providers. The JDBC providers page opens. 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.
142
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 indicates that failover occurred. For more information, see the DB2 database system documentation. 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 connection retry 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 you choose 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 JDBC Provider. The JDBC providers page opens. 8. Under Additional Properties, click Data sources. 9. Repeat step 6 on page 132 for each data source that is listed in the window. 10. If your metadata repository is configured for active-passive failover, but you did not indicate the virtual host name for your metadata repository database in the IBM InfoSphere Information Server installation program, complete the following steps: a. Click Resources > JDBC > Data sources. b. In the Data sources panel, click the first data source that is listed. c. Under Common and required data source properties, update the server name to the virtual host name. d. Click Apply, then click OK. e. Repeat each step for every data source that is listed. f. Click Test connection. Ensure that you see a message that says, The test connection operation for data source data_source_name on server server_name at node node_name was successful. g. If a message displays that asks you to complete synchronization, follow the instructions. 11. Log out of the console. 12. Locate the ojb-conf.jar file on one of the following servers, depending upon your configuration:
143
v If your installation includes a clustered implementation of WebSphere Application Server, locate the file on the server that hosts the WebSphere Application Server Deployment Manager. v Otherwise, locate the file on the server that hosts the services tier.
14. Open the repository_database.xml file by using a text editor. You add the alternate server name and port number to this file. 15. Locate all <jdbc-connection-descriptor> elements in the file that have a dbalias attribute. This first instance of 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="fa lse" jcd-alias="pojo" jdbc-level="2.0" password="{xor}tIakDPBAI X2Ao1nHR8j/+A==" platform="Db2" protocol="jdbc" subprotocol="db 2" useAutoCommit="2" username="{xor}tIakDPBAIX2Ao1nHR8j/+A=="> <connection-pool maxActive="21" validationQuery=""/> <object-cache class="org.apache.ojb.broker.cache.ObjectCach ePerBrokerImpl"/> </jdbc-connection-descriptor>
16. Modify the elements to include the client reroute information. Use the same server 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.1 6;clientRerouteAlternatePortNumber=50001;queryCloseImplicit=2;" default-connection="false" driver="com.ibm.db2.jcc.DB2Driver" e ager-release="false" ignoreAutoCommitExceptions="false" jcd-ali as="pojo" jdbc-level="2.0" password="{xor}tIakDPBAIX2Ao1nHR8j/+ A==" platform="Db2" protocol="jdbc" subprotocol="db2" useAutoCo mmit="2" username="{xor}tIakDPBAIX2Ao1nHR8j/+A=="> <connection-pool maxActive="21" validationQuery=""/> <object-cache class="org.apache.ojb.broker.cache.ObjectCach ePerBrokerImpl"/> </jdbc-connection-descriptor>
17. Save your changes and exit the text editor. 18. Navigate to the temporary directory that you created previously and compress the ojb-conf.jar file with the updated information.
144
Command The following lines are part of a single command. The period (.) at the end of the command is required:/opt/IBM/WebSphere/ AppServer/java/bin/jar cf /opt/IBM/InformationServer/ASBServer/ apps/lib/ojb-conf.jar .
19. Modify the database.properties file. This file is located in the ASBServer/bin/sql/ subdirectory of the IBM InfoSphere Information Server installation directory. a. Use a text editor to open the database.properties file. b. Locate the url keyword and value:
Table 57. URL keyword and value format for different database systems Database system IBM DB2 database system Oracle database system and Oracle RAC Microsoft SQL Server database system url keyword and value url=jdbc\:db2\://host\:port/dbname
url=jdbc\:ibm\:oracle\://host\:port;serviceName\=SID;AlternateServers\ =(host:port, host:port, host:port, ...)
url=jdbc\:ibm\:sqlserver\://host\:port;DatabaseName=dbname
c. Change host and port to the match the values that you specified in step 6 on page 142. d. Save the file. 20. Update the values in the Version.xml file. This file contains the installation records that are used by the installation program. Keeping the file current avoids problems with future installations. The Version.xml file is located in the IBM InfoSphere Information Server installation directory on the same server as the ojb-conf.jar file.Edit the file as follows: a. Use a text editor to open the Version.xml file. b. 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. 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 the following XML element:
145
<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. What to do next Run the FilePropagator utility to propagate the changes to the ojb-conf.jar file to WebSphere Application Server. Starting HADR: Start high availability disaster recovery (HADR) on the standby server, and then on the primary server. Before you begin Make sure to configure the HADR variables as described in the previous information. If the parameters are not configured correctly, the HADR servers do not start. Procedure 1. 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 the standby 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 of the 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 db2 activate db database = Standby
4. On the primary server, run the following command to activate the database:
For example:
db2 activate db xmeta
146
5. On the primary server, run the following command to start HADR on the primary 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 of the server:
For example:
The following line is displayed:

Role = Primary
7. On each server, run the following command to verify that the databases are synchronized:
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, the state is reported as Peer:
State = Peer
Validating the HADR configuration: After you configure high availability disaster recovery (HADR), validate your configuration and test the takeover function. Before you begin Configure HADR on your primary and standby servers, and start HADR on the servers. About this task Use the IBM DB2 Control Center to verify the connection status. Then initiate a takeover and a failback to test the takeover function. Procedure 1. 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) window is displayed. 4. Verify that the Connection status field reads Connected. 5. Log in to the primary server as an administrator.
147
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:
For example:
When the takeover is successful, the following result is displayed for the standby server:
Role = Primary
9. Check the IBM WebSphere Application Server log file SystemOut.log to determine whether the application server successfully connected to the standby database. To locate this file, see IBM WebSphere Application Server system log files on page 290. If automatic client reroute worked correctly, the log file indicates that WebSphere Application Server first tried to connect to the primary server. When that connection failed, automatic client reroute connected successfully to the standby server. The following log file excerpt shows these events:
[11/1/11 17:15:39:298 CST] 00000039 ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: /dbview.jsp. Exceptionthrown : javax.servlet.ServletException: A connection failed but has 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 may not 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 of the database:
For example:
148
When the takeover is successful, the following result is displayed for the primary server:
Role = Primary
13. On each server, run the following command to verify that the databases are synchronized:
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, the state is displayed as Peer:
State = Peer
Configuring the metadata repository database in an Oracle RAC cluster: Use this road map to create a metadata repository tier setup that includes a metadata repository database that is set up in an Oracle Real Application Clusters (RAC) configuration. IBM InfoSphere Information Server does not support Oracle RAC configurations of the IBM InfoSphere Information Analyzer analysis database or the IBM InfoSphere QualityStage Match Designer database. Complete the tasks in the following table.
Table 58. Configuring the metadata repository database in an Oracle RAC cluster Task Prepare the Oracle RAC cluster. Use the scripts that are provided with the IBM InfoSphere Information Server installation media to configure the metadata repository database within the cluster. Then run the InfoSphere Information Server installation program to install InfoSphere Information Server software. Within the installation program, specify a single node in the Oracle RAC configuration. After you complete the installation, modify Connecting to an Oracle RAC the JDBC driver configuration to cause configuration on page 150 InfoSphere Information Server to operate with the complete Oracle RAC configuration. Link for more information Oracle RAC requirements Creating the metadata repository database and running the installation program within an Oracle RAC configuration on page 150
To deploy a clustered topology, you must have a solid understanding of network technologies such as protocols, layers, devices, and so on. Clustered topologies are technically complex, and require expertise to implement successfully. Oracle RAC requirements: Follow these guidelines when configuring your Oracle Real Application Clusters (RAC) environment for IBM InfoSphere Information Server. If you are installing into an existing Oracle RAC implementation, make sure that your installation follows these guidelines.
149
Follow Oracle database documentation to set up and configure your cluster. JDBC drivers are shipped with InfoSphere Information Server. They are installed when you run the installation program and install services tier components. Use the services Transparent Failover configuration (TAF policy) to orchestrate how failover occurs during run time. When you set up Oracle RAC, modify the tnsnames.ora configuration file for use by the sqlplus user so that connection and failover operate correctly. Creating the metadata repository database and running the installation program within an Oracle RAC configuration: Use the scripts that are provided with the IBM InfoSphere Information Server installation media to configure the metadata repository database within the Oracle RAC configuration. Then run the InfoSphere Information Server installation program. Procedure 1. To create the metadata repository database, use the scripts that are supplied with the InfoSphere Information Server installation media. See Setting up an existing installation of Oracle database software on page 151. 2. Run the InfoSphere Information Server installation program in graphical mode as described in Installing IBM InfoSphere Information Server by using the wizard (graphical mode) on page 179. Complete the entire InfoSphere Information Server installation as described in Scenario D: Clustered metadata repository tier and services tier configuration on page 51. From the installation program, specify a single node in the Oracle RAC configuration. Connecting to an Oracle RAC configuration: After you complete your services tier installation, modify the JDBC driver configuration to cause IBM InfoSphere Information Server to operate with the complete Oracle RAC configuration. About this task When you installed the services tier as described in Creating the metadata repository database and running the installation program within an Oracle RAC configuration, you provided the connection information for a single node of the Oracle RAC configuration, by using the normal host and system ID (Service Name) information. After the installation, redirect IBM WebSphere Application Server to use an Oracle RAC connection string. In an Oracle RAC configuration, a service name is shared among the different nodes in the cluster. This service name is in the connection string. Also, each of the nodes in the cluster is listed in the string as alternate server. If the primary node goes offline, the database connection is immediately reestablished to one of the alternate servers. The connection string has the following format. Enter the connection string on a single line:
150
primaryhost:port;serviceName=ServiceName; alternateServers=(altserver1:port,altserver2:port,...) For example, in a three-node cluster, the nodes might be named as follows:
Table 59. Example node names Host rac1 rac2 rac3 SID orce1 orce2 orce3
If they share the Service Name orce, a valid connection string for the connection is:
dbalias="oracle://rac1:1521;serviceName=orce;alternateServers= (rac1:1521,rac2:1521,rac3:1521)"
Procedure 1. Update the metadata repository configuration for the new connection string. See http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r7/topic/ com.ibm.swg.im.iis.productization.iisinfsv.install.doc/topics/ wsisinst_xmeta_hostname_port_change.html. 2. Change the string in the WebSphere Application Server configuration. See Specifying the alternate database address and port for IBM WebSphere Application Server.
Setting up an existing installation of Oracle database software

To prepare an existing Oracle database system for IBM InfoSphere Information Server, use scripts to create the metadata repository database.
Before you begin

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?uid=swg27021833. v It must be located on a computer that is accessible by the computers where the services tier and engine tiers are installed. v The Advanced Security option is not supported. If this option is turned on, turn it off before installing IBM InfoSphere Information Server. Before you proceed, complete all tasks that are listed in Setting up the tier computers on page 92. Refer to the Oracle database documentation for information on how to install your database.
Configuring an existing installation of an Oracle database (AIX )

You can use an existing installation of an Oracle database to create a metadata repository for InfoSphere Information Server.
Before you begin

Include the $ORACLE_HOME/bin directory in your system PATH to properly invoke the sqlplus command.
151
Important: You must configure your Oracle database with the following character sets to be compatible with InfoSphere Information Server. If the database is configured to use another character set, the preinstallation check in the InfoSphere Information Server installation program fails. In addition, data that contains unsupported characters are not stored, processed, or displayed correctly.
NLS_CHARACTERSET = AL32UTF8 NLS_NCHAR_CHARACTERSET = AL16UTF16
About this task

This script creates a tablespace within an existing database. Attention: This script also sets the OPEN_CURSORS initialization parameter to the minimum required value of 1500. If this parameter is already set to a higher value, modify the configure_xmeta_db.sql file to not set this parameter.
Procedure
1. Navigate to the install_dir/DatabaseSupport directory of the InfoSphere Information Server installation media, where install_dir is the directory where you extracted the InfoSphere Information Server media.
Database version Oracle 10g R2 Oracle 11g R2 Directory install_dir/DatabaseSupport/UNIX_Linux/ MetadataRepository/Oracle10g install_dir/DatabaseSupport/UNIX_Linux/ MetadataRepository/Oracle11g
2. From the command line, run the create_xmeta_db script to create the database. All arguments are required and must be specified in the order that is shown in the following example.
create_xmeta_db.sh OracleSystemUser OracleSystemPassword ServiceName XmetaUserName XmetaUserPassword XmetaTableSpaceName XmetaDatafilePath
For example,
create_xmeta_db.sh SYSTEM MANAGER DBNAME xmetauser xmetapwd xmetaspace /u01/app/oracle/oradata/dbname
OracleSystemUser The Oracle system user name to log into SQL*Plus with to create the tablespace and user. This user must be assigned the database administrator role. An account other than SYS must be used because the connection to the database is not created as SYSDBA or SYSOPER. OracleSystemPassword The password for the Oracle system user. ServiceName The Oracle TNS service name. This name must reference a working service. XmetaUserName The name of the Oracle user that you are creating for the metadata repository tablespace. XmetaUserPassword The password for the metadata repository tablespace user.
152
XmetaTableSpaceName The name of the metadata repository tablespace. XmetaDatafilePath The location where you want to create the data files for the tablespace. This location must reference an existing directory. For example, /u01/app/oracle/oradata/dbname. 3. Change to the following directory:
Oracle database version Oracle 10g R2 Oracle 11g R2 Directory install_dir/is-suite/DatabaseSupport/ UNIX_Linux/MetadataRepository/Oracle10g install_dir/is-suite/DatabaseSupport/ UNIX_Linux/MetadataRepository/Oracle11g
4. From the command line, run the following command to create the staging area schema. All arguments are required and must be specified in the order that is shown in the following example.
create_xmeta_db.sh OracleSystemUser OracleSystemPassword ServiceName StagingUser StagingUserPassword StagingTableSpace StagingDatafilePath
For example, the following command runs as the user, SYSTEM, using the password sys_pwd. The command connects to Oracle with the TNS name xmeta, and creates a tablespace named xmetasrsp under the /u01/app/oracle/oradata/ dbname directory. The Oracle account named xmetasr is created using the password xmetapwd, and is used to access the staging area schema.
create_xmeta_db.sh SYSTEM sys_pwd xmeta xmetasr xmetapwd xmetasrsp /u01/app/oracle/oradata/dbname
OracleSystemUser The Oracle system user name to log into SQL*Plus with to create the tablespace and user. This user must be assigned the database administrator role. An account other than SYS must be used because the connection to the database is not created as SYSDBA or SYSOPER. OracleSystemPassword The password for the Oracle system user. ServiceName The Oracle TNS service name. This name must reference a working service. StagingUser The name of the user that you are creating to access the staging area schema. This user must be different from the active repository user because the staging area schema must be a different schema within the metadata repository database. StagingUserPassword The password for the staging area schema user. StagingTableSpace The name of the tablespace that you are creating for the staging area schema. StagingDatafilePath The location where you want to create the data files for the staging area tablespace. This location must reference an existing directory. For example, /u01/app/oracle/oradata/dbname.
153
Creating the IBM InfoSphere QualityStage Match Designer database

The IBM InfoSphere QualityStage Match Designer is a component of InfoSphere QualityStage that is used to design and test match specifications. Match specifications consist of match passes that identify duplicate entities in one or more files. If you intend to develop match specifications, use a new or existing database that is dedicated to storing the results of match test passes. Do not use the metadata repository or the analysis database to store these results.
Database requirements
The InfoSphere Information Server installation program does not create the Match Designer results database. You create the database before or after the installation, as long as the database is configured and accessible when you use the Match Designer. You can create the database on a computer where the client or engine tier is installed or on any computer that is accessible to both of these tiers. You must configure the database to receive the type of data that is processed in the Match Designer. For example, you must configure the database to receive double-byte data if the Match Designer processes Asian data. The following table lists the supported databases and describes the configuration requirements:
Table 60. Configuration requirements by database Database All databases Configuration requirements Configure as an empty database. The Match Designer creates the table structure that it requires when it stores the match pass results in the database. Configure the following settings: v Set Default Buffer Pool and Table Space Page Size to 32K. v Set Code Set to UTF-8. Oracle database system Configure the following settings: v Set Character Set for the data being processed. For example, use WE8ISO8859P1 for English and for Western European languages. v Set National Character Set to AL32UTF8. Note: If you use the IBM Wire Protocol driver, select the Enable N-CHAR Support option. Microsoft SQL Server database system No special settings are required.
IBM DB2 database system
Database space requirements

After you create the database, use automatic storage management to allocate database space as needed.
154
To estimate initial space requirements and plan for the appropriate hardware, you need to make some assumptions about the type and volume of matching that you will do. Consider the following factors: v v v v v Estimated number of match specifications Average number of match passes per match specification Average number of input data records per match specification Average number of bytes per input data record Average number of input frequency records per match specification
When you calculate the number of bytes in a Match Designer input record, assume that VarChar columns contain maximum width values. Also, keep in mind that most Match Designer input records will be preprocessed through an InfoSphere QualityStage Standardization Stage. This stage will add 500 bytes to a source record or 1000 bytes if the source record is double-byte. When calculating frequency record volume, consider whether the data values for the source columns that participate in your matches typically have high or low rates of duplication. For data that is highly unique, your frequency record count will be similar to your data record count. For data that has a high rate of duplication, your frequency record count will be significantly less than your data record count. Review the factors described in Table 2. Then, use the factors in the following formula to estimate how many megabytes of space the Match Designer results database is likely to require. (number of match specifications x (match size + (match size x 10%) + frequency size) x replication factor) / 1,000,000
Table 61. Space requirement factors and calculations Factor Match specification count Description Match specifications define and test criteria for matching data. Match passes define the column-level matching criteria applied during a single pass through match specification input. Data records define the content and format of match specification input. Data records define the content and format of match specification input. When calculating data record length, assume sizing scenarios that require the most space. Calculation Approximate number of match specifications you expect to retain in your database Average number of match passes per match specification (used in the Match Size calculation) Average number of input data records per match specification (used in the Match Size calculation) Average number of bytes per match specification input data record (used in the Match Size calculation)
Match pass count
Data record count
Data record length
155
Table 61. Space requirement factors and calculations (continued) Factor Match size (in bytes) Description Match size aggregates the match pass and data record count and length factors into the estimated space requirements for the data component of a single match specification. Frequency records indicate how often a particular value appears in a particular column. For frequency record count, consider high or low rates of duplication for the data values in source columns. Frequency size (in bytes) Frequency size estimates the space requirement for the frequency component of a single match specification. Replication factors account for significant differences in space requirements of different match types: v Unduplicate matches take input from one source, then group and match the data. v One-to-one reference matches compare a record on the data source to a record on the reference source. v Many-to-one reference matches can match any reference source record with many data source records. (Frequency record count per match) x 360 Calculation (Match pass count) x (data record count) x (data record length)
Frequency record count
Average number of frequency records per match specification
Replication factor
Select the replication factor for the match type you expect to run most often: v For unduplicate matches, use a factor of 1 v For one-to-one reference matches, use a factor of 2 v For many-to-one reference matches, use a factor of 5
Installing WebSphere Application Server software

You can use the IBM InfoSphere Information Server installation program to install WebSphere Application Server software. You can install WebSphere Application Server in a non-cluster (stand-alone) installation, or a clustered installation that supports high availability.
Installing WebSphere Application Server by using the installation program

IBM InfoSphere Information Server supports IBM WebSphere Application Server Network Deployment, Versions 7.0 and 8.0. You must install one of these versions.
156
Before you begin

The WebSphere Application Server installation must satisfy the following requirements: v It must be on the same computer where you install the services tier. v It must be a supported version. See the system requirements at www.ibm.com/support/docview.wss?uid=swg27021833. InfoSphere Information Server does not support WebSphere Application Server Extended Deployment (XD) or the WebSphere Application Server base version.
About this task

This task describes installing IBM WebSphere Application Server Network Deployment in a non-cluster (stand-alone) installation. For a cluster installation, see Installing IBM WebSphere Application Server Network Deployment for a cluster installation on page 159. Important: WebSphere Application Server, Version 8.0 is supported only as a preinstalled component. To use this version of WebSphere Application Server, you must install it before you install InfoSphere Information Server. The InfoSphere Information Server installation package includes installation packages for IBM WebSphere Application Server Network Deployment, Version 7.0. To preinstall WebSphere Application Server, Version 7.0 before you run the InfoSphere Information Server installation program, run the WebSphere Application Server installation program that is included in the InfoSphere Information Server installation media. Note: If you preinstall IBM WebSphere Application Server and install a separate front-end HTTP server, you must manually configure the HTTP server to enable WebSphere Application Server to accept HTTPS calls. HTTPS configuration is optional. If you do not configure HTTPS, HTTP is used instead.
Procedure
1. Run the IBM WebSphere Application Server installation program on the InfoSphere Information Server services tier to install IBM WebSphere Application Server Network Deployment. Within the installation media, the WebSphere Application Server installation packages are in the following directories:
Operating system AIX Directory installation_image_directory/payloads/ Shared/WAS/payload/WAS
See the WebSphere Application Server documentation for more information: v For Version 7.0, go to the WebSphere Application Server Network Deployment information center and read Installing your application serving environment. v For Version 8.0, go to the WebSphere Application Server Network Deployment information center and read Installing your application serving environment.
157
2. Create a new application server profile with administrative security disabled. For information about creating a profile, see the WebSphere Application Server documentation: v For Version 7.0, go to the WebSphere Application Server Network Deployment information center and read Managing profiles on non-z/OS operating systems. v For Version 8.0, go to the WebSphere Application Server Network Deployment information center and read Managing profiles on non-z/OS operating systems. 3. Optional: Manually configure the front-end HTTP server for HTTPS. Follow the instructions in the WebSphere Application Server documentation: v For Version 7.0, go to the WebSphere Application Server Network Deployment information center and read Securing communications. v For Version 8.0, go to the WebSphere Application Server Network Deployment information center and read Securing communications. 4. Install any required fix packs and interim fixes. To find the supported fix pack level, Java SDK fix number, and interim fixes that are required for your installed version of IBM WebSphere Application Server Network Deployment, refer to the InfoSphere Information Server system requirements page: www.ibm.com/support/docview.wss?uid=swg27021833. Note: If you use the installation packages for IBM WebSphere Application Server Network Deployment, Version 7.0 that is included in the installation package, the fix packs and interim fixes are automatically installed when you run the installation program.
Implementing a WebSphere Application Server cluster for InfoSphere Information Server

You can set up a clustered environment for high availability, failover, and scalability. First, determine an appropriate cluster topology, and then install and configure the appropriate version of IBM WebSphere Application Server Network Deployment, set up clusters, and install a front-end web server. To deploy a highly available topology, you must have a solid understanding of network technologies such as protocols, layers, and devices. Highly available topologies, especially topologies that involve clustering, are technically complex 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 equipment available, and so on). The cluster topology can include one or more clustered application servers, each running cloned copies of IBM InfoSphere Information Server, one or more front-end web servers (or hardware or software load balancers), one or more firewalls, and so on. Refer to theWebSphere Application Server documentation for information about cluster configurations and manual tuning: v For Version 7.0, go to the WebSphere Application Server information center and read Introduction: Clusters. v For Version 8.0, go to the WebSphere Application Server information center and read Introduction: Clusters.
158
General considerations for clustering on WebSphere Application Server

IBM WebSphere Application Server Network Deployment provides control over the design of the cluster environment through the deployment manager, managed nodes, and unmanaged nodes (stand-alone InfoSphere Information Server instances): 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 InfoSphere Information Server managed node or stand-alone InfoSphere Information Server instance. When you create a cluster, be aware of these InfoSphere Information Server restrictions: v All managed nodes that are participating in a cluster must run on the same operating system. For example, in a cluster, one managed node cannot be running on a Windows system and another managed node running on a UNIX system. v Each InfoSphere Information Server cluster must have its own dedicated Network Deployment domain or cell. That is, within a cell in which an InfoSphere Information Server cluster is deployed, do not deploy any other type of server, which includes the following servers: v InfoSphere Information Server cluster v IBM InfoSphere Master Data Management Server server v InfoSphere Information Server stand-alone server (or any standard application server instance that runs J2EE applications)
Installing IBM WebSphere Application Server Network Deployment for a cluster installation
IBM InfoSphere Information Server supports IBM WebSphere Application Server Network Deployment, Versions 7.0 and 8.0. You must install a supported version.
Before you begin

1. Determine the cluster topology that you want to use, based on your system requirements. 2. On the computer where you want to install the deployment manager and on all computers that will host a managed node, configure the system to support a large number of file descriptors. Refer to your system administrator if you are not familiar with file descriptor allocations. For example, if your login shell is /bin/bash, complete the following tasks:
Operating system AIX Procedure Configure the following environment variable in /etc/profile for system-wide change: unset LDR_CNTRL
159
Procedure
1. Install IBM WebSphere Application Server Network Deployment on all the computers that will host the InfoSphere Information Server services tier. This installation includes the deployment manager system and all computers that will host a managed node. Run the IBM WebSphere Application Server installation program to install IBM WebSphere Application Server Network Deployment. See the WebSphere Application Server documentation for more information: v For Version 7.0, go to the WebSphere Application Server information center and read Installing your application serving environment. v For Version 8.0, go to the WebSphere Application Server information center and read Installing your application serving environment. The InfoSphere Information Server installation package includes installation packages for IBM WebSphere Application Server Network Deployment, Version 7.0. To preinstall WebSphere Application Server, Version 7.0 before you run the InfoSphere Information Server installation program, you can run the WebSphere Application Server installation program that is included in the InfoSphere Information Server installation media. Within the installation media, the WebSphere Application Server installation packages are in the following directories:
Operating system AIX Directory payloads/Shared/WAS/payload/WAS
When creating a profile during the installation, make sure to disable administrative security. 2. Install the required fix pack and interim fixes. To find the supported fix pack level, Java SDK fix number, and interim fixes that are required for your installed version of IBM WebSphere Application Server Network Deployment, refer to the InfoSphere Information Server system requirements page: www.ibm.com/support/docview.wss?uid=swg27021833
Creating a deployment manager profile

You create a deployment manager profile (for example, Dmgr01) that contains the deployment manager process. The deployment manager process is the main administration process that manages all other IBM WebSphere Application Server processes running in the cell, including node agents and application server processes.
Procedure
Create a deployment manager profile by using the Profile Management Tool or the manageprofiles command line tool. The Profile Management Tool is located in the bin/ProfileManagement directory of a WebSphere Application Server installation. See the IBM WebSphere Application Server Network Deployment documentation for more information:
160
Method
Procedure
Using the Profile Management Tool v For Version 7.0, go to the WebSphere Note: If you use the Profile Management Application Server Network Deployment Tool, adhere to the following guidelines information center and read Creating when creating a deployment manager profile: management profiles with deployment v On the Administrative Security panel, managers ensure that the Enable administrative v For Version 8.0, go to the WebSphere security check box is not selected. Security Application Server Network Deployment is enabled during the IBM InfoSphere information center and read Creating Information Server installation process. management profiles with deployment v On the Environment Selection panel, select Deployment Manager. v For most cases, choose the Typical profile creation option. If you want to modify default attributes of the deployment manager profile, select the Advanced profile creation option. Using the manageprofiles command line tool v For Version 7.0, go to the WebSphere Application Server Network Deployment information center and read manageprofiles command v For Version 8.0, go to the WebSphere Application Server Network Deployment information center and read manageprofiles command managers
Example
The following example illustrates how you use the manageprofiles command to create a deployment manager profile in a UNIX environment:
manageprofiles.sh -create -templatePath profileTemplates/dmgr/ -isDefault -profileName dmgr
What to do next
Create a custom profile.
Creating a custom profile

You create a custom profile (for example, Custom01) that contains the node agent process and the managed server process that is part of the cluster.
About this task

It is a good practice to install IBM InfoSphere Information Server on a single-node cluster and then, after the installation, to expand your cluster by adding new managed nodes and cluster members. Refer to the post-installation tasks for details about adding new managed nodes and cluster members.
Procedure
Create a deployment manager profile by using the Profile Management Tool or the manageprofiles command line tool. The Profile Management Tool is located in the bin/ProfileManagement directory of a WebSphere Application Server installation. See the IBM WebSphere Application Server Network Deployment documentation for more information:
161
Method Using the Profile Management Tool

1
Procedure v For Version 7.0, go to the WebSphere Application Server Network Deployment information center and read Creating custom profiles v For Version 8.0, go to the WebSphere Application Server Network Deployment information center and read Creating custom profiles
Using the manageprofiles command line tool
v For Version 7.0, go to the WebSphere Application Server Network Deployment information center and read manageprofiles command v For Version 8.0, go to the WebSphere Application Server Network Deployment information center and read manageprofiles command
If you use the Profile Management Tool, adhere to the following guidelines when creating a custom profile: v On the Federation panel, ensure that the host name and port information match your deployment manager (the default information is localhost and 8879). Make sure that you do not select Federate this node later check box. Federate the node later, when you can verify the availability of the deployment manager. Because administrative security is not enabled yet, do not enter the user name and password for the deployment manager. v For most cases, choose the Typical profile creation option. If you want to modify default attributes of the deployment manager profile (such as the port numbers), select the Advanced profile creation option.
Example
AIX : The following example illustrates how you use the manageprofiles command to create a custom profile:
manageprofiles.sh -create -templatePath profileTemplates/managed/ -profileName <profile_name> -dmgrHost <dmgr_host_name> -dmgrPort <dmgr_port_number>
What to do next
Create a cluster and cluster members.
Creating a cluster and cluster members for the application server

Use the IBM WebSphere administrative console to create a cluster with one cluster member definition.
Before you begin

1. 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 the initial cluster member.
162
4. You must choose one of the following two methods available to manage HTTP sessions in a cluster environment: HTTP session memory-to-memory replication or HTTP session database-based persistence. Both methods ensure that HTTP session data survive in the event of a cluster member failure. Note: HTTP session memory-to-memory replication is easier to set up. If you want to use HTTP session memory-to-memory replication, when creating the cluster in IBM WebSphere Application Server Network Deployment administrative console, in the Step1: Enter basic cluster information window, select the Configure HTTP session memory-to-memory replication check box. By default, the IBM InfoSphere Information Server installation process detects whether HTTP sessions were already configured with database-based session persistence. If it is not yet configured, HTTP session memory-to-memory replication is configured automatically, even if you do not select this check box.
About this task

Create one cluster member to start with. After IBM InfoSphere Information Server is installed, you can create additional cluster members. Refer to the post-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 deploy each InfoSphere Information Server cluster in its own dedicated cell.) The cell cannot contain any other type of server, which includes: InfoSphere Information Server cluster, IBM InfoSphere Master Data Management (MDM) server, InfoSphere Information Server stand-alone servers, or any standard application server instance that runs J2EE applications. For more information, refer to Implementing a WebSphere Application Server cluster for InfoSphere Information Server on page 158.
Procedure
Create clusters and cluster members by using the IBM WebSphere Application Server Network Deployment administrative console. v For Version 7.0, go to the WebSphere Application Server information center and read Creating clusters. v For Version 8.0, go to the WebSphere Application Server information center and read Creating clusters. Replication domains: When you create clusters and cluster members, it is useful to understand the various replications domains that are used to create clusters. Several replication domains are used within an IBM InfoSphere Information Server cluster: v If you chose a memory-to-memory replication approach for HTTP session management, the replication domain replicates HTTP session information and the stateful EJB state across the cluster. v Another type of replication domain is used to replicate cached data (data-cached applications that are part of the InfoSphere Information Server suite). Both types of replication domains replicate cached data to all cluster members (a full-domain strategy). Replication domains are created automatically during the InfoSphere Information Server installation. You use the default IBM WebSphere
163
Application Server settings during installation. You can change these settings from the WebSphere Application Server administrative console after the InfoSphere Information Server installation.
Installing a front-end web server

You install and configure a front-end web server before you run the IBM InfoSphere Information Server installation program so that the various InfoSphere Information Server applications can be mapped to the front-end web server automatically.
Before you begin

Determine which web server and web server version to install, depending on your version of IBM WebSphere Application Server Network Deployment. Review the documentation: v For Version 7.0, go to the WebSphere Application Server information center and read Implementing a web server plug-in. v For Version 8.0, go to the WebSphere Application Server information center and read Implementing a web server plug-in.
About this task

The following steps describe how to install the IBM HTTP Server, Versions 7.0 and 8.0. Refer to the Apache HTTP Server documentation for information about how to install the Apache HTTP Server.
Procedure
1. Determine a web server topology diagram and road map: v For Version 7.0, go to the WebSphere Application Server information center and read Selecting a web server topology diagram and roadmap. v For Version 8.0, go to the WebSphere Application Server information center and read Selecting a web server topology diagram and roadmap. 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 Application Server Network Deployment managed node. When you do so, the web server plug-in file, plugin-cfg.xml, is automatically propagated to the web server by IBM WebSphere Application Server. v For production environments, install the web server remotely on a dedicated server. Because the front-end web server is typically outside the firewall in the DMZ, the front-end web server must be installed remotely on a separate dedicated computer. You manually copy the plugin-cfg.xml file to the computer where the web server is installed. (For more information, see the IBM InfoSphere Information Server Administration Guide.) 3. Install IBM HTTP Server: v For Version 7.0, go to the WebSphere Application Server information center and follow the steps for Installing IBM HTTP Server. v For Version 8.0, go to the WebSphere Application Server information center and follow the steps for Installing IBM HTTP Server using the GUI. 4. Install the web server plug-in module: v For Version 7.0, go to the WebSphere Application Server information center and follow the steps for Installing web server plug-ins.
164
v For Version 8.0, go to the WebSphere Application Server information center and follow the steps for Installing and configuring web server plug-ins. After you install the Workload Manager plug-in binary files, run the configure<webserver_name> script to create a web server definition in WebSphere Application Server.
Operating system AIX Script configure<webserver_name>.sh
Note: For remote installations, running the script also creates an unmanaged node. 5. Configure the web server to accept encoded slashes. See Cannot view report result from InfoSphere Information Server console or InfoSphere Information Server Web console on page 307.
What to do next
You can now install additional components such as backup load balancers, backup web servers, firewalls, and cache proxies. Refer to the external vendors' documentation.
Installing a front-end load balancer (optional)

You install a load balancer in front of the web servers in an IBM WebSphere Application Server cluster installation if your installation requires very high availability. This configuration is called an IP sprayer topology.
About this task

Steps for installing a front-end load balancer are specific to external vendors and are not provided in this documentation. Do not install a load balancer directly in front of a WebSphere Application Server cluster without a web server between the load balancer and the cluster. Web servers with the WebSphere Application Server workload management plug-in adjust to changes in the cluster topology such as adding or removing nodes. Load balancers do not have this functionality, and must be manually reconfigured. Make sure to configure session affinity in the load balancer. There are several methods to achieve session affinity. The method that you choose depends on the product that you use and the forwarding mechanism that you configure. Mechanisms include media access control (MAC) address forwarding, Network Access Translation/Network Address Port Translation (NAT/NAPT) forwarding, and content-based forwarding. Layer 2 load balancers (load balancers that operate at the MAC layer) generally achieve session affinity by using a stickiness to source IP address approach. Layer 3 and higher load balancers (load balancers that operate at the IP layer and above) typically achieve session affinity by using passive cookies or a content-based technique. Session affinity with HTTP servers is typically achieved by using these techniques.
What to do next
After you install a load balancer, you can install any additional components that you need, such as backup load balancers and firewalls.
165
Running the installation program (clustered installation)

After you configure your system, run the IBM InfoSphere Information Server installation program.
Before you begin

v AIX : Ensure sure that all WebSphere Application Server processes will start with the correct ulimit setting on the computer where you will install the deployment manager and on all computers that will host a managed node: Add the following line to the /etc/profile file:
ulimit -n 10240
v Ensure that no firewall is deployed within the IBM WebSphere Application Server Network Deployment cell. v Ensure that the deployment manager process is running. Tip: You can check whether the deployment manager is running by starting the WebSphere Application Server administrative console. If the login screen displays correctly, the deployment manager process is running. If you see an error or a blank screen, you can start the deployment manager by using the startManager command located under the <dmgrProfileName>/bin directory. v Ensure that the managed node and node agent that you created are both running. Tip: You can check whether the node agent is running by logging in to the WebSphere Application Server administrative console and clicking System administration > Node agents. You can start the node agent by using the startNode WebSphere Application Server command under the <customProfileName>/bin directory. v Verify that you have created one cluster with at least one member. Note: Install IBM InfoSphere Information Server on a single-node cluster and then, after the installation, expand your cluster by adding new managed nodes and cluster members. Refer to the post-installation administration tasks for details on how to add new custom profiles. v The front-end web server and plug-in module must be installed.
Procedure
1. Disable any firewall that might be running on your computer and ensure that the firewall is disabled during the entire installation. You can reenable the firewall after the installation is finished. 2. Run the InfoSphere Information Server installation program on the computer that 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 a clustered installation, not a stand-alone installation. 4. During the interview process, specify the host name and port number of the front-end HTTP dispatcher for any requests for the services tier host name and port. Do not specify a port to a specific application server cluster member, such as 9080. A specific port number to cluster member does not allow for high
166
availability and efficient dispatching of requests, because requests are directed to a specific cluster member. This configuration is especially important when specifying the services tier host name and port number during an engine tier installation.
What to do next
After you configure WebSphere Application Server for your cluster installation of InfoSphere Information Server, you can administer your WebSphere Application Server clusters. For more information, refer to the IBM InfoSphere Information Server Administration Guide. Note: When the MetadataServer script is run in a stand-alone (non-cluster) environment, it sets the following system settings:
Operating system AIX Setting uname setting: ulimit -n 10240
These settings are not set when you start a cluster. You can manually produce these settings in a cluster environment, if needed. The MetadataServer script exists in the ASBServer/bin directory of the computer hosting the deployment manager.
Changing the front-end dispatcher location

If you change the front-end dispatcher location or configuration, you must complete a few additional steps. This post-configuration task involves updating two files that exist on all tiers.
About this task

During the installation process, you must enter the host name and port number of the front-end dispatcher for a high availability installation. This information is used by the installation program to configure IBM InfoSphere Information Server. When you modify the front-end dispatcher (for example, if you relocate the dispatcher to another machine, or replace the Web server with a load balancer, and so on), you must update the following files with the new host name and port number: registered-servers.xml and Version.xml. You must update these files on every engine tier computer that is registered to that services tier. Also update the Version.xml file on the services tier system that hosts the Deployment Manager.
Procedure
1. 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, 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.
<asb-server name="domain_name" host-name="dispatcher_hostname" port="dispatcher_port" is-primary-server="true"/>
167
Important: On engine tier systems that have clients installed, you might see multiple <asb-server> elements in the registered-servers.xml file. These instances represent the host name and port number of each services tier that has been successfully logged into from this client system. This is the source of the list of services tiers shown on client login pages. Update the host names and port numbers of only the services tiers that are affected by the front-end dispatcher changes. Note: In the file you are examining, if there is no <asb-server> element with is-primary-server="true" in the registered-servers.xml file, then you are not on the engine tier. Refer to the last step in this topic for information about configuring files on the client tier. 2. Update the Version.xml file with the correct front-end dispatcher host name and 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 tier 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"/>
Note: The was.default.host.port parameter appears if you are using the embedded version of IBM WebSphere Application Server. If you preinstalled WebSphere Application Server, this parameter is not listed in your Version.xml file. 3. On the engine tier, recycle the agents and engine processes. Refer to the IBM InfoSphere Information Server Administration Guide. 4. Restart the cluster and cluster members. Refer to the IBM InfoSphere Information Server Administration Guide. 5. Go to http://dispatcher_hostname:dispatcher_port to verify whether you can log in to the InfoSphere Information Server Web console.
Setting up an existing non-clustered installation of WebSphere Application Server

Instead of installing a new IBM WebSphere Application Server instance for IBM InfoSphere Information Server, you can configure an existing installation to use with InfoSphere Information Server.
Before you begin

The WebSphere Application Server installation must satisfy the following requirements: v It must be on the same computer where you install the services tier. v It must be a supported version. See the system requirements at www.ibm.com/support/docview.wss?uid=swg27021833.
168
InfoSphere Information Server does not support WebSphere Application Server Extended Deployment (XD) or the WebSphere Application Server base version.
Procedure
Configure your WebSphere Application Server installation before you install InfoSphere 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.
Operating system AIX Command /opt/IBM/WebSphere/AppServer64/bin/ versionInfo.sh /opt/IBM/WebSphere/AppServer64/java/bin/ java -fullversion
Compare the values that are returned by these commands to the version numbers in the system requirements to determine if you have a supported version. If you do not have a supported version, do not attempt to configure it for use with InfoSphere Information Server. 2. Create a new application server profile with administrative security disabled. For information about creating a profile, see the WebSphere Application Server documentation: v For Version 7.0, go to the WebSphere Application Server Network Deployment information center and read Managing profiles on non-z/OS operating systems. v For Version 8.0, go to the WebSphere Application Server Network Deployment information center and read Managing profiles on non-z/OS operating systems. 3. Optional: Manually configure the front-end HTTP server for HTTPS. Follow the instructions in the WebSphere Application Server documentation: v For Version 7.0, go to the WebSphere Application Server Network Deployment information center and read Securing communications. v For Version 8.0, go to the WebSphere Application Server Network Deployment information center and read Securing communications.
Setting the locale and character encoding for the engine tier target computer
The installation program uses the locale and encoding information of the target computer to determine whether it can provide language support. For languages other 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 configuration that is the most suitable for the locale and encoding of the target computer. To ensure that server jobs run and compile correctly, make sure that the target computer uses a supported locale and encoding. Set 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, the installation program configures InfoSphere Information Server for the English language, including globalization support.
169
Complete the following procedure to set the locale.
Procedure
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 locale names or alias locale names. A full locale name contains the encoding name in the last component. For example, the full locale name ja_JP.utf8 contains the encoding name, utf8, in the last component. An alias locale name does not include the encoding name. To determine the encoding, you can run the following command:
LANG=alias_name locale charmap
where alias_name is the alias name. For example, the following command returns 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, change the LANG value to a combination that is available on your computer and that is supported by IBM InfoSphere Information Server. To change the locale and encoding, 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 the encoding to UTF-8:
export LANG=ja_JP.utf8 export LC_ALL=ja_JP.utf8
Character encodings supported by IBM InfoSphere Information Server

To ensure that server jobs run and compile correctly, the operating system of the target computer must use an encoding that is supported by the globalization configuration that is used during installation. Verify that the operating system of the target computer uses a supported character encoding. The following table lists the languages and encodings that are supported by InfoSphere Information Server on various operating systems. For more information, see the IBM InfoSphere DataStage and QualityStage Globalization Guide.
Table 62. Supported encodings on AIX computers for InfoSphere Information Server Language Chinese Globalization configuration name DS-CHINESE-SIMPLIFIED Supported encodings AIX EUC-CN, GB18030, GB2312, GBK, IBMEUCCN UTF-8 BIG5 UTF-8 ISO8859-1
Chinese Chinese, Traditional Chinese, Traditional English
DS-CHINESE-SIMPLIFIED-UTF8 DS-CHINESE-TRADITIONAL DS-CHINESE-TRADITIONAL-UTF8 DS-ENGLISH
170
Table 62. Supported encodings on AIX computers for InfoSphere Information Server (continued) Language English French French German German Italian Italian Japanese Japanese Japanese Japanese Korean Korean Portuguese Portuguese Spanish Spanish Thai Globalization configuration name DS-ENGLISH-UTF8 DS-FRENCH DS-FRENCH-UTF8 DS-GERMAN DS-GERMAN-UTF8 DS-ITALIAN DS-ITALIAN-UTF8 DS-JAPANESE DS-JAPANESE-EUC DS-JAPANESE-SJIS DS-JAPANESE-UTF8 DS-KOREAN DS-KOREAN-UTF8 DS-PORTUGUESE-BRAZILIAN DS-PORTUGUESE-BRAZILIAN-UTF8 DS-SPANISH DS-SPANISH-UTF8 DS-THAI Not supported IBM932, IBM943, IBM943C, PCK, SHIFT_JIS, SJIS UTF-8 AIX KSC5601 UTF-8 ISO8859-1 UTF-8 ISO8859-1 UTF-8 TIS620 Supported encodings UTF-8 ISO8859-1 UTF-8 ISO8859-1 UTF-8 ISO8859-1 UTF-8
171
172
Part 2. Installing IBM InfoSphere Information Server software

You can create an installation of IBM InfoSphere Information Server or update an existing installation with a patch or fix pack.
173
174
Chapter 5. Preparing to install IBM InfoSphere Information Server

Before you install InfoSphere Information Server, ensure that you have the correct installation media and that your computers are ready for installation.
Obtaining IBM InfoSphere Information Server software

The first preparation step is to obtain the InfoSphere Information Server software and applicable fix packs.
Before you begin

To ensure uninterrupted connectivity to the installation media, copy the contents of the installation media to a local file system or optical drive. Run the installation program from this location.
About this task

The installation media for installing InfoSphere Information Server is available either as physical CDs or as downloadable installation image files from Passport Advantage. Fix packs are available as downloadable installation image files from Fix Central.
Procedure
1. Acquire the installation media.
Option If you have the installation media in physical form Description Check that you have all of the installation disks.
If you do not have the installation media in Download the installation image files from physical form Passport Advantage. Use the Knowledge Collection support document to determine the image files that are appropriate for your operating systems and configurations.
2. Download any applicable fix packs from Fix Central. 3. If you downloaded installation image files, uncompress the installation image files onto each tier computer.
Configuring your browser

To run the installation program successfully, you must configure your browser.
All browsers
v Verify that you have a supported browser. For details, go to the system requirements at www.ibm.com/support/docview.wss?uid=swg27021833. v Make sure that JavaScript is enabled.
175
Microsoft Internet Explorer

Make sure that the security zone for the computer allows the installation program to 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 installation program will run. 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. 3. 4. 5. Click Content. Enable Load images automatically. Enable Enable JavaScript. Click OK.
Installing InfoSphere Metadata Asset Manager and bridges to import and export metadata
When you install the metadata interchange agent with bridges, you can use bridges to import metadata with InfoSphere Metadata Asset Manager and to export metadata with Import Export Manager. InfoSphere Metadata Asset Manager provides robust functionality for importing metadata. You use bridges or connectors in InfoSphere Metadata Asset Manager to import metadata assets from applications, files, and databases. You import the metadata to a staging area where you can analyze the source metadata and preview the results before you share it to the metadata repository. You can browse and search the metadata repository and manage common metadata assets. Components of InfoSphere Metadata Asset Manager are installed automatically with the suite on the services tier and the repository tier. To use bridges and connectors you must install additional software. To use bridges you must choose to install Metadata interchange agent and bridges on a client tier computer on Microsoft Windows. The metadata interchange agent enables interaction between bridges and InfoSphere Metadata Asset Manager. When you install the metadata interchange agent with bridges, the following components are automatically installed on the client tier computer: v Metadata interchange agent v InfoSphere Metadata Integration Bridges with Import Export Manager. v Apache Tomcat Version 6.0.20
176
You can use Import Export Manager to export metadata. You can also import metadata by using Import Export Manager, but InfoSphere Metadata Asset Manager is the preferred import tool because of its advanced functionality. The computer on which you install the metadata interchange agent and bridges must meet the prerequisites and system requirements for installing bridges: http://www.ibm.com/support/docview.wss?&uid=swg27021981. During installation, you must specify the HTTPS port for the computer. The default HTTPS port is 19443. To use connectors with InfoSphere Metadata Asset Manager you must install InfoSphere DataStage and QualityStage on an engine tier computer. Installing InfoSphere DataStage and QualityStage automatically installs connectors. The following connectors are supported for use with InfoSphere Metadata Asset Manager: v DB2 Connector v ODBC Connector v Oracle Connector v Teradata Connector After you install, but before you can import metadata by using InfoSphere Metadata Asset Manager, a user with the role of Common Metadata Administrator must define metadata interchange servers. A metadata interchange server is a computer where the metadata interchange agent and bridges are installed or where connectors are installed. If you are using the metadata interchange server for bridge imports, you must specify the HTTPS port that you indicated during the installation of InfoSphere Information Server. For more information about InfoSphere Metadata Asset Manager, see the IBM InfoSphere Information Server Guide to Managing Common Metadata.
Preparing to run the installation program

Before you run the installation program to create an installation or add product modules or tiers, make sure that the computers are ready for installation. Also back up critical data.
Before you begin

AIX The Pluggable Authentication Modules (PAM) must be installed on the target computer. For more information about how to configure PAM, see Understanding and configuring PAM on www.ibm.com.
Procedure
Follow this procedure for each target computer: 1. Back up your systems. a. Back up all critical data. b. Back up existing instances of IBM InfoSphere Information Server if your computer already hosts an instance. c. Back up the following directories.
Chapter 5. Preparing to install IBM InfoSphere Information Server
177
Directories /etc/services, /etc/inittab, /etc/passwd, and /etc/group
2. If you removed a previous installation of InfoSphere Information Server on the computer, reboot the computer before continuing. 3. The installation program writes required temporary files to a location that is defined by the following environment variable.
Operating system AIX Environment variable TMP
If you want to redirect the temporary files to a different temporary directory, copy the .jvm_args_debug file at the root installation directory to .jvm_args and edit the new file to remove the existing contents. Then, add the following line with the new temporary directory:
-Djava.io.tmpdir=installation_program_tempdir
4.
5.
6. 7.
After the installation completes, do not delete the installation log files that are in the temporary directory. Preserve these files for troubleshooting and verification purposes. The Advanced Security option is not supported on Oracle database systems. If this option is turned on, turn it off before installing InfoSphere Information Server. If you are installing an instance of InfoSphere Information Server on a computer with an existing instance, disable all scheduled jobs, scheduled tasks, scheduled reports, and enabled IBM InfoSphere Information Services Director applications. Disable firewall software and antivirus software before starting the installation. 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 to the processes by using the ulimit command. See Running the installation program (clustered installation) on page 166. v Verify that you can start and stop the cluster, and restart node agents. See the 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 as business needs dictate post-installation.
8. 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 WebSphere Application Server installation directory and profile directory to be root. Then start WebSphere Application Server as root.
178
Chapter 6. Installing IBM InfoSphere Information Server software

After you have planned your installation and prepared your computers, use the InfoSphere Information Server installation program to create an installation. You can also use the installation program to add product modules or software tiers to an existing installation. The installation program can also install IBM DB2 and IBM WebSphere Application Server Network Deployment if your installation requires stand-alone configurations of these components. Alternatively, the installation program can set up InfoSphere Information Server to use preinstalled instances of these components, or other supported database systems and application servers. The installation program can run in either of two modes: Graphical mode In this mode, the installation program runs within a standard Web browser, either locally on the target computer or remotely. The installation program presents wizard pages for you to select options. When you have selected your options, the program saves them to a response file on the target computer. Then the program performs a prerequisites check. If the check succeeds, the program installs the software. Silent mode In this mode, the installation program does not present a user interface. Instead, it reads settings from a response file. It performs a prerequisites check. If the check succeeds, the program installs the software. As it performs the installation, it can save the report to a text file or display results on the console. Important: During the initial installation session, install all of the product modules that you plan to use either now or in the future. If you install only some of the product modules now, and then install fixes and service packs, you might need to reinstall the fixes and service packs if you add product modules later.
Installing IBM InfoSphere Information Server by using the wizard (graphical mode)
You can use a web browser to run the installation program locally in graphical mode on the target computer. Alternatively, you can use a web browser on any system that has network access to the computer where the installation program is running.
Before you begin

Choose your installation topology, review the installation checklists, and prepare the tier computers. Then, obtain the product media and configure your browser correctly so that the installation program runs smoothly.
179
About this task

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 start a web browser on the computer or on a remote computer and access the graphical interface. After you enter your settings in the wizard pages, the program stores your settings in a response file. If you run the installation program again, you can load your settings from this file into the program instead of entering them again.
Procedure
1. Change to the is-suite directory within the directory that contains the installation media. 2. Run the installation program:
Operating system AIX Command ./setup [-verbose]
The -verbose option is optional. The option causes the installation program to display 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. The program then displays a message about how to access the installation wizard:
======> Enter one of the following URLs to your web browser to begin the installation process: http://localhost:8080/ISInstall https://localhost:8443/ISInstall
3. Open a web browser on the computer or on a remote computer, and navigate to one of the addresses that is listed in the messages from starting the installation program. A message might appear in the browser that reads The publisher cannot be verified... You can safely ignore the message and continue the installation. This message does not indicate a security risk when it appears during InfoSphere Information Server installation. a. Select a language from the menu for the installation program to use, and click Login. This selection applies only to this installation session. Later in the installation process, you select the language to apply to the InfoSphere Information Server installation. b. Follow the prompts in the installation program to continue installing the product. The installation program runs an early prerequisites check to ensure that your installation is configured correctly, as shown in the following figure. The wizard page displays each check. If the check fails, it is marked FAILED in the page. If the check found issues that might cause problems with the installation, it is marked WARNING in the page.
180
Figure 38. Early requirements check showing a failed message for the Windows Script Engine
4. When all prerequisites checks pass, continue to follow the prompts in the installation program.
Installation prerequisites check failed

The installation program runs an early prerequisites check before installing the product to ensure that the target computer meets all system requirements for the selections that you have made.
Symptoms
During the early prerequisites check, you received FAILED or WARNING messages.

Complete these steps by following the prompts in the wizard: 1. Double-click each message to learn more about resolving it. 2. Try to resolve each issue without exiting the installation program. Then, click Check Again in the Prerequisites Check page. 3. If you must exit the installation program, click Cancel, close the web browser window, and type Ctrl+c in the session window to end the installation session. Resolve the issues and then restart the installation program. The following figure shows a portion of the Early Requirements Check page. When you select a FAILED message and click Details, resolution information is
181
displayed.
Figure 39. Early Requirements Check page
Specifying tiers and product modules to install

After you start the installation program, specify the software tiers and product modules that you want to install for each of the tier computers where you are installing InfoSphere Information Server.
Specifying installation options (services tier)

Use the InfoSphere Information Server installation program to specify options for the service tier computer, such as the location where you want to install IBM WebSphere Application Server, the property information for your database system, and configuration information for other product modules.
Procedure
1. Select the directories where you want to install the product that you determined when planning your installation. 2. Select New installation. 3. Select the tiers to install on the target computer. v If you chose Engine in the Tier Selection page but did not choose Services, choose the location where you want to install InfoSphere Information Server. v If your services tier is configured in a clustered implementation of IBM WebSphere Application Server, specify the host name and port number of
182
the front-end HTTP dispatcher. Otherwise, specify the host name of the services tier computer and the port number for WebSphere Application Server (typically 9080). v If the HTTP server is configured to allow HTTPS traffic only, or you want to configure InfoSphere Information Server to use an HTTPS-only connection, select Use Secure Sockets Layer (SSL) for HTTP communication. If you select this option, provide a port number that is configured for HTTPS. Note: Select this option only if the HTTP port has been disabled in your WebSphere Application Server installation. If you do not select this option, you can still set up the client components to use HTTPS. Most installations do not use this option. 4. Enter the InfoSphere Information Server administrator user name and password. Use the information that you determined when planning your installation. 5. Select the product modules that you want to install. Select the same set of product modules for each computer. 6. Choose the InfoSphere DataStage edition and optional features that you want to install. 7. Enter the preconfigured floating host name to share between the servers. 8. Install IBM WebSphere Application Server Network Deployment in a stand-alone configuration or configure an existing application server instance. 9. Install WebSphere Application Server. a. Specify the installation location for the application server. b. Select Customize WebSphere Application Server profile ports if you want to define custom port assignments for WebSphere Application Server within the profile. c. Enter the server administrator user name and password. 10. Configure your application server. a. Specify the application server instance to use. b. Specify an application server profile to use. You must have at least one profile available for installation. The profile that you selected for installation must not have active security settings. If the installation program detects that the type of the selected profile is dmgr, it installs InfoSphere Information Server on a WebSphere Application Server cluster. In this case, your cluster must have been properly configured so that you can restart all node agents and nodes properly. It is highly recommended that you start with a small cluster that has only one WebSphere Application Server deployment manager node and one WebSphere Application Server node for installation c. If your application server profile is a WebSphere Application Server deployment manager, enter an HTTP server host name and port number. d. If your profile is not a deployment manager profile, specify whether to use Secure Sockets Layer (SSL) for HTTP communications. Select this option if the HTTP server is configured to allow HTTPS traffic only, or if you want to configure InfoSphere Information Server to use an HTTPS-only connection. If you select this option, provide a port number that is configured for HTTPS. e. Enter the server administrator user name and password.
183
11. Enter the InfoSphere Information Server administrator user name and password. 12. Specify the database type, host computer name, port, and metadata repository owner information for your database. 13. Specify the following information for the metadata repository database: a. Owner account and database information. b. User name and password for the staging area user (xmetasr). 14. Specify the owner account and database information for the InfoSphere Information Analyzer analysis database. The installation program creates the analysis database within DB2. If you did not create the analysis database owner account before starting the installation program, the installation program creates the account.
Specifying installation options (engine tier)

Use the InfoSphere Information Server installation program to specify options for the engine tier computer, such as the ports to use for the InfoSphere Information Server ASB agent (communication agent) and logging agent, as well as connection details for other product modules.
Procedure
1. Select the directories where you want to install the product that you determined when planning your installation. 2. Select New installation. 3. Select the tiers to install on the target computer. v If you chose Engine in the Tier Selection page but did not choose Services, choose the location where you want to install InfoSphere Information Server. v If your services tier is configured in a clustered implementation of IBM WebSphere Application Server, 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 port number for WebSphere Application Server (typically 9080). v If the HTTP server is configured to allow HTTPS traffic only, or you want to configure InfoSphere Information Server to use an HTTPS-only connection, select Use Secure Sockets Layer (SSL) for HTTP communication. If you select this option, provide a port number that is configured for HTTPS. Note: Select this option only if the HTTP port has been disabled in your WebSphere Application Server installation. If you do not select this option, you can still set up the client components to use HTTPS. Most installations do not use this option. 4. Enter the InfoSphere Information Server administrator user name and password. Use the information that you determined when planning your installation. 5. Select the product modules that you want to install. 6. Enter the preconfigured floating host name to share between the servers. 7. Enter the InfoSphere Information Server administrator user name and password.
184
8. Specify the ports to use for the InfoSphere Information Server ASB agent (communication agent) and logging agent. The ASB agent facilitates communication between tiers and the logging agent logs events to the metadata repository database. 9. Specify connection details for additional InfoSphere Information Server components. a. Specify two TCP/IP ports to use for the IBM InfoSphere DataStage and QualityStage job monitor, which takes snapshots of job performance. The job monitor uses one port to request job information and the second port to report job information. The default port settings are acceptable in most configurations. b. If you want this installation to handle data in languages other than English, install globalization support. Some server jobs might run more slowly after you install globalization, but the performance of parallel jobs is not affected. The code page that is currently configured on the target computer must be supported by InfoSphere Information Server. If the code page is not supported, change to a supported code page and restart the installation program. Important: You cannot change the globalization support after installation. c. If you have existing jobs that depend on the IBMWebSphere MQ Plug-in, choose to install the plug-in. For new jobs, you can use the IBMWebSphere MQ Connector. d. If you have existing jobs that use SAS, enable a legacy SAS configuration and select the SAS that you want to configure. e. Specify the InfoSphere DataStage projects to create. You must create at least one project during installation. The installation wizard defaults to creating a project called dstage1. 10. Specify the ports for the metadata interchange agent to use. You must specify the HTTPS port number for the engine tier computer. The default HTTPS port is 19443.
Specifying installation options (metadata repository tier)

Use the InfoSphere Information Server installation program to specify options for the metadata repository tier computer, such as the property information for your database system.
Procedure
1. Select the directories where you want to install the product that you determined when planning your installation. 2. Select New installation. 3. Select the tiers to install on the target computer. v If you chose Engine in the Tier Selection page but did not choose Services, choose the location where you want to install InfoSphere Information Server. v If your services tier is configured in a clustered implementation of IBM WebSphere Application Server, 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 port number for WebSphere Application Server (typically 9080). v If the HTTP server is configured to allow HTTPS traffic only, or you want to configure InfoSphere Information Server to use an HTTPS-only
185
connection, select Use Secure Sockets Layer (SSL) for HTTP communication. If you select this option, provide a port number that is configured for HTTPS. Note: Select this option only if the HTTP port has been disabled in your WebSphere Application Server installation. If you do not select this option, you can still set up the client components to use HTTPS. Most installations do not use this option. 4. Enter the InfoSphere Information Server administrator user name and password. Use the information that you determined when planning your installation. 5. Select the product modules that you want to install. Select the same set of product modules for each computer. 6. Enter the preconfigured floating host name to share between the servers. 7. Specify the directory where you want to install the DB2 database system. If you are configuring an existing DB2 instance, specify the location of the existing DB2 database system installation and the port number for connecting to the instance. a. AIX : Specify the DB2 instance owner name. The instance owner controls all the DB2 processes and owns all the file systems and devices that are used by the databases within the DB2 instance. v If you created the instance owner account before starting the installation program, click Existing user and specify the DB2 instance owner name. Also specify a port number for the new instance. v If you did not create the instance owner account, click Create a user as an instance owner and specify the user information. This option is not available if the user registry is Lightweight Directory Access Protocol (LDAP) or NIS. b. AIX : Specify the DB2 fenced user name. Any fenced user-defined functions (UDFs) and stored procedures run under this user and group. v If you created the fenced user name before starting the installation program, click Existing user and specify the DB2 fenced user name. v If you did not create the fenced user name, click Create a new user as a fenced user and specify the user information. This option is not available if the user registry is LDAP or NIS. c. AIX : Specify the DB2 administrator user name. This user is the DB2 Administration Server (DAS) user. v If you created the administrator user before starting the installation program, click Existing user and specify the user name. v If you did not create the administrator user, click Create the user as administrator user and specify the user information. This option is not available if the user registry is LDAP or NIS. d. Enter the metadata repository owner information and database name. 8. Specify the database type, host computer name, port, and metadata repository owner information for your database. 9. Specify the following information for the metadata repository database: a. Owner account and database information. b. User name and password for the staging area user (xmetasr). 10. Specify the owner account and database information for the InfoSphere Information Analyzer analysis database. The installation program creates the
186
analysis database within DB2. If you did not create the analysis database owner account before starting the installation program, the installation program creates the account.
Installing the product

After the installation program completes the prerequisites check and you specify installation options for each tier, save a response file and proceed with the installation process. You must save a response file to tell the IBM InfoSphere Information Server installation program how to perform an installation by using your saved configuration information.
About this task

Saving a response file is important if you want to cancel the current installation session and use the response file in a later session. Use the installation wizard to specify a name and location for your response file.
Procedure
1. In the installation wizard, specify a name and location for the response file in the Response file location field (at this point, you can choose to cancel the installation and use the saved response file in a later session). 2. Click Install IBM InfoSphere Information Server and save my settings in a response file, and then click Next to begin the product installation. The program displays a summary of the choices that you made in the wizard. As the installation proceeds, the installation program reports the progress in the window.
187
Figure 40. Response File Review page
Be mindful of the following conditions while the installation program is running: v Leave the command prompt open until the installation is complete, as shown in the following figure.
188
Figure 41. Command prompt open during installation
v If the system encounters an error, it might occasionally request a response from you. Check periodically to make sure that the system is not waiting for you 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 the installation to proceed. Occasionally a pop-up window might be displayed behind the web browser. If the installation halts for a long interval, check for pop-up windows displayed behind the web browser. v After you have started the installation process, keep the web browser open to monitor progress and to respond if there is an error. If you close the web browser, the installation continues to the end. You can reconnect to the session by opening a new web browser to the same URL. You can also monitor the installation process by reading the log files.
Installation program encounters an error

After you start the installation process, the installation program might encounter an error that requires your action to resolve.
Symptoms
The installation program encounters an error and an Installation Exception window appears.

Complete these steps in the Installation Exception window: 1. Click Retry failed action and then click OK. 2. If the problem recurs, review the last statements in the log file to determine what caused the error. a. Investigate and fix the error. b. Click Retry failed action and then click OK. 3. If the issue can be resolved, fix the issue, and then click Retry. Related tasks Specifying tiers and product modules to install on page 182 After you start the installation program, specify the software tiers and product
189
modules that you want to install for each of the tier computers where you are installing InfoSphere Information Server.
Completing the installation process

After the installation program has collected your selections, it runs another, more detailed prerequisites check based on your selections. During this check, it analyzes your computer resources and file system to determine whether the installation is likely to succeed.
About this task

The wizard page displays each check. If the check fails, it is marked FAILED in the page. If the check found issues that might cause problems with the installation, it is marked WARNING in the page. When the installation process is complete, an Installation Summary for Current Computer page is displayed that contains the product, tiers, and product components that you installed, as well as information on how long the installation program ran and whether the installation was successful. If the installation process was successful, the following message is written to the log file:
Installation Engine completed all steps successfully.
Procedure
Click Finish or close the browser window. Related tasks: Specifying tiers and product modules to install on page 182 After you start the installation program, specify the software tiers and product modules that you want to install for each of the tier computers where you are installing InfoSphere Information Server.
Installing IBM InfoSphere Information Server by using the response file (silent mode)
You can use silent mode to run an unattended installation of InfoSphere Information Server. In silent mode, the installation program does not display a user interface. Instead, it reads settings from a response file that you create, performs a prerequisites check, and installs the software if the check succeeds.
About this task

You start the installation program in silent mode with the most commonly used command-line options. For more information, see setup command syntax on page 192. Note: Passwords are not saved in the response file. To use the response file in a subsequent installation, you must first edit the response file with a text editor and add passwords.
190
Creating a response file

You create a response file to use when running the installation program in silent mode. You use the installation program or copy the sample response file template to create your response file.
Before you begin

Obtain the product media.
Procedure
1. Create a response file.
Option Using the installation program Description 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 displays, select either Install IBM InfoSphere Information Server and save my settings in a response file or Do not install IBM InfoSphere Information Server and save my settings in a response file. Either selection causes a response file to be created. 4. Specify a file name and location and click Next. The program saves your parameters in a response file in the specified location. The program then either performs the operation or exits, depending upon your selections in the window. Using the sample response file template that is located with the installation media 1. Copy the sample response file from the following location. AIX media_location/is-suite/ samples/responses
2. Modify the copy of the sample response file. See the readme file included that is included with the templates for more information.
2. Run the genkey command to generate encrypted information. The genkey command is located in the tools directory on your installation media:
Operating system AIX Command install_media/tools/genkey.sh info_to_encrypt
For example:
C:\is-suite\tools\genkey.cmd mypassword
Messages are displayed in the terminal window. Then the command displays the encrypted version of the specified information. For example:
{xor}8Y3lImYJo0sxGOl4igw/pA==
191
3. Replace all passwords with encrypted passwords after using the genkey command. Locations in the response file where passwords must be included are indicated with markers. For example,
app.server.password=mypassword
4. Save and store the response file for use when installing InfoSphere Information Server.
Encrypting information in a response file

You 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 to encrypt passwords or other information in your response files, follow this procedure to encrypt information and include it in the files. You can encrypt any values in a response file. However, this procedure is typically used to encrypt passwords.
Procedure
1. Create a response file. See Response files on page 197. 2. Run the genkey command to generate encrypted information. The genkey command is located in the tools directory on your installation media:
Operating system AIX Directory install_media/tools/genkey.sh info_to_encrypt
For example:
C:\is-suite\tools\genkey.cmd -generate mypassword
Messages are displayed in the terminal window. Then, the command displays the encrypted version of the specified information. For example:
{xor}8Y3lImYJo0sxGOl4igw/pA==
3. In the response file, append the extension .encrypted to the parameter. Replace the 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==
setup command syntax

You use the setup command to run the IBM InfoSphere Information Server installation 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 program to start in graphical mode.
192
-help Displays this usage information and then terminates. -uiMode mode Specifies the mode to run in. Valid values for mode can be graphical (default) or silent. -rsp rspfile Specifies the response file to use for this installation. For a silent mode installation, you must specify a response file by using this parameter. For a graphical mode installation, the settings in the response file that you specify appear in the wizard and you do not have to enter them again. If you specify the -rsp parameter, the installation program runs in silent mode by default. To run in graphical mode with a response file, you must also specify the -uiMode graphical parameter. -reportOnly For a silent mode installation only. Performs the prerequisites check but does not perform the installation. Use with the -reportFile parameter to store the results of the prerequisites check in a text file. If this parameter is specified for a software removal, the parameter is ignored. -force Use this parameter to permit the installation program to continue even if the prerequisites checks fail. In graphical mode, if -force is specified on the command line and a prerequisites check fails, an Ignore FAILED items and continue check box is shown in the window. To continue the installation, click this check box and then click Next. If -force is not specified, the check box is not shown and the Next button is disabled. In silent mode, if -force is specified on the command line and a prerequisites check fails, the installation process continues. If -force is not specified, the installation process halts if prerequisites check tests fail. Important: Prerequisites check FAILED and WARNING messages indicate items that might cause a failed installation or that might cause malfunctions in the installed software. Use the -force option only if directed by IBM Support. -reportFile rptfile For a silent mode installation only. Specifies a text file for the prerequisites check report. If a reportFile value is not specified, the report is displayed to the console. -language languagecode Specifies the language that displays for the installation. The following table lists valid language codes.
Table 63. Language codes Language Chinese (Simplified) Chinese (Traditional) English French Codes zh_CN zh_TW en or en_US fr or fr_FR
193
Table 63. Language codes (continued) Language German Italian Japanese Korean Portuguese (Brazilian) Spanish Codes de or de_DE it or it_IT ja or ja_JP ko or ko_KR pt_BR es or es_ES
-verbose Starts the installation session in trace mode. In this mode, log messages are displayed to the console and are also written to the log file. You can use this option in silent mode or graphical mode. If you do not specify this parameter, log messages are written to the log file only. -secure For a graphical mode installation only. Prompts you to create a password when the installation program starts. The password is used to authenticate access to the installation program from the browser. The password can be any string of alphanumeric characters. The password can include white space characters.
Examples
The following command causes the installation program to prompt for a password and then start in graphical mode. The installation program uses the settings in the rsp.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 log messages in a log file. When the prerequisites checks run, results are stored in prq.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 log messages in a log file. When the prerequisites checks run, results are stored in prq.txt. The installation program stops after the prerequisites check without installing 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 log messages in a log file and also displays them to the console. When the prerequisites check runs, results are stored in prq.txt.
./setup -rsp rsp.txt -reportFile prq.txt -verbose
Starting the installation program with a response file

You can run a silent installation of InfoSphere Information Server by using a response file rather than by using the installation wizard. Follow the progress of the installation by monitoring the installation log file.
194
Procedure
1. Optional: Modify the EXCEPTION_POLICY environment variable. This variable determines how errors are processed that might occur when running in silent mode.
Operating System AIX Command setenv EXCEPTION_POLICY=n
n can be any of the following values: 1 2 Prompt user to try again on error (default behavior) Continue on error Important: Continuing with an installation after an error occurs could result in a nonoperational installation, or might cause existing installed software to stop functioning. Use this option only if directed by IBM Support. 3 Exit on error 2. Log in to the target computer.
Operating system AIX Description Log is as the root user.
3. Open a command prompt or shell window.

Operating system AIX Command Open a shell window on the target computer, or use a graphical desktop sharing system. Keep the shell window open during the entire installation process. If you use telnet or ssh, make sure that the session does not shut down or timeout for the duration of the installation.
4. In the newly created session, run the following command to clear any Java options that might be set.
Operating system AIX Command bash.sh export IBM_JAVA_OPTIONS= csh, tcsh unsetenv IBM_JAVA_OPTIONS
5. AIX : Configure the following settings for the session to help ensure that the installation is successful: v Set the file creation mask to 022:
umask 022
v Ensure that you have enough file descriptor resources allocated for the installation. Set the file descriptor limit to 10240, a higher value, or unlimited. For example:
ulimit -n 10240
v Check that the current setting for the NOFILES kernel parameter is set to a value that is at least equal to the value that you specify for ulimit.
195
6. Change to the is-suite directory within the directory that contains the installation media. 7. Run the setup command with the -reportOnly parameter to perform the prerequisite check. For example,
setup -reportOnly
The installation program runs through a prerequisites check phase. If all prerequisite checks pass, installation continues until the installation process finishes. If one or more prerequisite checks fail, the installation displays errors and stops. The prerequisites check report contains messages like the following line:
FAIL - The DB2 installation directory C:\IBM\SQLLIB must be empty.
If a prerequisites check fails, correct the problem and restart the installation. 8. Run the following command to start the installation program:
Operating system AIX Command ./setup -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 to display 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 display messages in the window if the -verbose option is specified. Be mindful of the following conditions while the installation program is running: v Monitor the installation as described in Monitoring the IBM InfoSphere Information Server installation on page 208. 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 is not shutdown or disabled. Click through the warning to allow the installation program to continue.
Installation program encounters an error

After you start the installation process, the installation program might encounter an error that requires your action to resolve.
Symptoms
The installation program encounters an error and an Installation Exception window appears.

Complete these steps in the Installation Exception window: 1. Click Retry failed action and then click OK. 2. If the problem recurs, review the last statements in the log file to determine what caused the error. a. Investigate and fix the error.
196
b. Click Retry failed action and then click OK. 3. If the issue can be resolved, fix the issue, and then click Retry. Related tasks Specifying tiers and product modules to install on page 182 After you start the installation program, specify the software tiers and product modules that you want to install for each of the tier computers where you are installing InfoSphere Information Server.
Response files
A response file contains parameters and values that tell the IBM InfoSphere Information Server installation program how to perform an installation. You can also use a response file during software removal. Create a response file by using the InfoSphere Information Server installation or software removal program, or by modifying the sample templates that are included on the installation media. Different sets of parameters and values are used depending on the type of software installation or removal. For example, a certain set of parameters and values is used for an installation that includes application server clustering. Another set is used for an installation where the application server is set up in a stand-alone configuration.
Response file syntax

A response file is a text file. In the file, parameters and values are specified one per line. 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 and values 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 the parameter 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 created by the installation or software removal program, the program does not store the passwords in the file. Instead, locations in the file where passwords must be included 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 an encrypted format, see Encrypting information in a response file on page 192.
Response file parameters (AIX )

You can use the IBM InfoSphere Information Server installation program to generate 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 silent installation.
197
The following list of response file parameters is not comprehensive. For the complete list, see the response file templates in the media_location/is-suite/ samples/responses directory, where media_location is the location of your installation media. Use the templates for the following purposes: v Creating a new installation of all products v 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 that apply 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 Application Server ports instead of installing with the default ports. app.server.password=change_to_application_server_admin_password Set 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 ID Set to the user ID for the application server administrator. This ID will be created 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. This option 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 option can 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. This option controls which database to use, and is available if you are using a preinstalled database. An example value is com.ibm.db2.jcc.DB2Driver. db.url=database_url Set the database URL for the metadata repository or given database. These sample values apply only if you created the database using the DatabaseSupport scripts or if the database is on a remote system. The following database URLs are allowed: db.url= jdbc:db2://hostname:port/database
198
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_name Set to the IBM DB2 administrator group name. An example value is dasadm. db2.admin.home.directory=DB2_admin_home_directory Set to the DB2 administrator home directory. An example value is /home/dasusr. db2.admin.user.name=DB2_admin_username Set to the operating system ID to be used as the DB2 administrator ID. This value applies only if you are installing the repository tier. An example value is dasuser. db2.fenced.group.name=DB2_fenced_group_name Set to the DB2 fenced group name. An example value is db2fadm. db2.fenced.home.directory=DB2_fenced_home_directory Set to the DB2 fenced home directory. An example path is /home/db2fenc1. db2.fenced.user.name=DB2_fenced_user_name Set to the DB2 fenced user name. An example value is db2fenc1. db2.fenced.user.password=change_to_DB2_fenced_password Set to the DB2 fenced user password db2.install.location=DB2_absolute_installation_path Set to the absolute path where DB2 is to be installed. An example value is /opt/IBM/db2. db2.instance.group=DB2_instance_group_name Set to the group name of the installed DB2 instance. An example value is db2iadm. db2.instance.home.directory=DB2_instance_home_directory Set to the directory of the installed instance of DB2. An example value is /home/db2inst1. db2.instance.name=DB2_instance_name Set to a string that will identify the DB2 instance. The DB2INSTANCE environment variable will be set to this DB2 instance name by default. An example value is db2inst1. db2.instance.user.name=DB2_instance_user_name Set to the user name of the instance of DB2. An example value is db2inst1. db2.instance.user.password=change_to_DB2_instance_user_password Set to the password of the DB2 instance user.
199
db2.port.number=DB2_instance_port_number Set to the TCPIP port for this DB2 instance. This value applies only if you are installing the repository tier. An example value is 50000. ds.admin.gid=DataStage_admin_group_name Set to the InfoSphere DataStage administrator group name. An example value is dstage. ds.admin.uid=DataStage_admin_username Set 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 64. Supported language codes for InfoSphere DataStage Language English French German Italian Spanish Portuguese-Brazil Chinese-Simplified Chinese-Traditional Japanese Korean Code ENU FRA DEU ITA ESP PTB CHS CHT JPN KOR
An example value is ENU. ds.project.1.name=DataStage_project_name Set the value to the InfoSphere DataStage project name that you want. Replace the number, 1, with the project number that increments, starting with 1. An example value is dstage1. ds.project.1.path=path_to_DataStage_project_files Set the value for the path to the InfoSphere DataStage project files. Replace the number, 1, with the project number that increments, starting with 1. An example value is /opt/IBM/InformationServer/Server/Projects/dstage1. ds.project.1.version=New Replace the number with the incrementing number, starting with 1, of the project to be created for InfoSphere DataStage. Set the value to New for this release. Note: To make a project protected, add (Protected) in English, as demonstrated in the last line in the following example. For example:
ds.project.1.name=dstage1 ds.project.1.path=/opt/IBM/InformationServer/Server/Projects/dstage1 ds.project.1.version=New ds.project.2.name=addedproj
200
ds.project.2.path=/opt/IBM/InformationServer/Server/Projects/addedproj ds.project.2.version=New ds.project.3.name=protect ds.project.3.path=/opt/IBM/InformationServer/Server/Projects/protect ds.project.3.version=New (Protected)
ds.rpc.instance.tag=ITAG_value Set to the InfoSphere DataStage rpc instance tag (ITAG). The ITAG value is a three-digit hexadecimal. ACE, ADE, and DCD are reserved values. The ITAG value must be unique on the system. ADE is the default value if you do not make this an ITAG installation. If you specify a value for an ITAG installation, use a value other than ACE, ADE, or DCD. dsrpc.port=DataStage_dsrpc_port_number Set to the InfoSphere DataStage dsrpc port. An example value is 31538. https.truststore.path=path In a secure HTTP (HTTPS) installation, set to the path to the truststore file that contains the certificate to accept. An example location is tmp/MyFile.jks. ia.db.hostname=Information_Analyzer_db_host_name Set to the IBM InfoSphere Information Analyzer database server name. The host name is the output of the hostname command on the system were the response file was generated. ia.db.location=Information_Analyzer_db_location Set to the path where the InfoSphere Information Analyzer database will be stored. An example location is /opt/IBM/InformationServer/Repos/iadb. ia.db.name=Information_Analyzer_db_location Set 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_password Set to the password for the InfoSphere Information Analyzer database owner. ia.db.port=port_number_for_DB2_instance Set to the port for the DB2 instance where the database is to be created. If this is a repository installation and the InfoSphere Information Analyzer database is to be created in the local DB2 instance, ia.db.port must use the same port as the port used for db2.port.number. An example value is 50000. 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_ID Set to the operating system ID to be used as the InfoSphere Information Analyzer database owner ID. An example value is iauser. install.path=[1|2|3|4|5|6] Set to the type of installation:
201
1 2 3 4 5
= New Installation = Add Product = Add Tier = Remove Product = Remove Tier
6 = Uninstall An example value is 1. is.admin.password=Information_Server_Admin_password Set to the password for the InfoSphere Information Server Administrator ID. is.admin.user=Information_Server_Admin_ID Set to the user name that you want for the InfoSphere Information Server Administrator ID. This ID will be created in the local repository. An example value is admin. is.console.port=port Set to the HTTP or HTTPS port where InfoSphere Information Server is installed. In HTTP installation, the value is typically 9080. In an HTTPS installation, the value 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, and DataStage.SAS is true. is.was.cluster=[true|false] Set to true if you are installing into a WebSphere Application Server cluster configuration. isf.agent.port=[true|false] Set to the port number for the InfoSphere Information Server Agent. An example value is 31531. isf.http.host=host_name Set 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_number Set the HTTP or HTTPS port number of the front-end dispatcher for a cluster installation. An example value is 80. isf.server.host=ISF_server_host_name Set 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_port Set to the port number for the first job monitor port.
202
An example value is 13400. jobmon.port.2=port_number_for_second_job_monitor_port Set to the port number for the second job monitor port. An example value is 13401. LIC_AGREEMENT=ACCEPT Set to ACCEPT to accept the license agreement. logging.agent.port=Logging_Agent_port_number Set to the port number for the Logging Agent. An example value is 31533. 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 and IBM InfoSphere QualityStage. The value, false, is supported only for systems that have the nls.language parameter set to English and a supported system code page. nls.language=[English-UTF8|English|Chinese-Simplified-UTF8|ChineseSimplified|Chinese-Traditional-UTF8|Chinese-Traditional|FrenchUTF8|French|German-UTF8|German|Italian-UTF8|Italian|Japanese-EUC|JapaneseSJIS|Japanese-UTF8|Japanese|Korean-UTF8|Portuguese-BrazilianUTF8|Portuguese-Brazilian|Spanish-UTF8|Spanish|Thai] Set to the language to configure for InfoSphere DataStage and InfoSphere QualityStage. The installation computer code page must be compatible and supported 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 InfoSphere QualityStage support.
Table 65. Supported language codes Language English French German Italian Spanish Portuguese-Brazil Chinese-Simplified Chinese-Traditional Japanese Korean Code ENU FRA DEU ITA ESP PTB CHS CHT JPN KOR
An example value is ENU.
203
product[AVI].selected=[true|false] Set to true if installing IBM InfoSphere QualityStage Address Verification Interface. 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 you are setting is.sas.selected to true to enable legacy InfoSphere DataStage SAS jobs, you must provide a value for sas.install.choice. An example value is SASVersion6. suite.installLocation=IS_installation_path Set to the absolute directory path where InfoSphere Information Server is to be installed. 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.
204
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 Server installation.
Table 66. Supported country or region codes Language Brazil China France Germany Italy Japan Korea Spain Taiwan United States Code BR CN FR DE IT JP KR ES TW 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.
Table 67. Supported language codes Language English French German Italian Spanish Portuguese-Brazil Chinese-Simplified Chinese-Traditional Japanese Korean Code en fr de it es pt_BR zh zh_TW ja ko
An example value is en. use.bundled.db2=[true|false] Set to true if installing the DB2 database that is bundled with InfoSphere Information Server. use.bundled.was=[true|false] Set to true if installing the IBM WebSphere Application Server Network Deployment that is bundled with InfoSphere Information Server. was.admin.host.port=was_console_port_number Set to the port for the WebSphere Application Server administrative console. An example value is 9060. was.bootstrap.port=websphere_bootstrap_port_number Set to the WebSphere bootstrap port.
205
An example value is 2809. was.dcs.unicast.port=was_ha_manager_port_number Set to WebSphere high availability manager communication port. An example value is 9353. was.default.host.port=was_http_transport_port_number Set to the port number for the HTTP transport port. An example value is 9080. was.install.location=empty_was_installation_location The directory must be empty. An example value is /opt/IBM/WebSphere/AppServer. was.mutual.auth.listener.port=was_mutual_bootstrap_port_number Set to the port number for the WebSphere mutual bootstrap port. An example value is 9402. was.orb.listener.port=was_orb_listener_port_number Set to the port number for the WebSphere ORB listening port. An example value is 9100. was.profile.dir=was_profile_directory Set the WebSphere profile directory. An example value is /opt/IBM/WebSphere/AppServer/profiles/InfoSphere. was.profile.name=was_profile_name Set the WebSphere profile name. An example value is InfoSphere. was.sas.ssl.port=SAS_SSL_port Set to the port number for the SAS SSL Server Authentication listener. An example value is 9401. was.secure.admin.host.port=secure_was_port Set to the port number for the secure WebSphere Application Server administrative console. An example value is 9043. was.secure.default.host.port=default_secure_HTTP_transport_port Set to the port number for the default secure HTTP transport port. An example value is 9443. was.secure.sib.mq.port=secure_service_integration_MQ_port_number Set to the port number for the secure service integration MQ interoperability port. An example value is 5578. was.secure.sib.port=secure_service_integration_port_number Set to the port number for the secure service integration port. An example value is 7286. was.server.auth.listener.port=CSIV2_server_auth_port_number Set to the port number for the CSIV2 server authentication port. An example value is 9403.
206
was.server.name=was_server_name Set the WebSphere Application Server server name. An example value is server1. was.sib.mq.port=service_integration_MQ_port_number Set to the port number for the service integration MQ interoperability port. An example value is 5558. was.sib.port=service_integration_port Set to the port number for the service integration port. An example value is 7276. was.sip.port=SIP_port_number Set to the port number for the SIP port. An example value is 5060. was.sip.secured.port=SIP_secured_port_number Set to the port number for the secured SIP port. An example value is 5061. was.soap.connector.port=SOAP_connector_port_number Set to the port number for the SOAP connector port. An example value is 8880. xmeta.db.collection=DB2_JDBC_collection_name Set to the collection name for DB2 JDBC collection. Used for IBM DB2 for z/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_name Set to the host name for the metadata repository database server. An example value is myhostname.mydomain.com. xmeta.db.location=metadata_repository_db_location Set to the path for Linux or UNIX where you want the metadata repository database to be created. An example value is /opt/IBM/InformationServer/Repos/xmeta. xmeta.db.name=metadata_repository_db_name Set to the database name for the metadata repository. An example value is xmeta. xmeta.db.password=metadata_repository_db_owner_password Set to the password for the metadata repository database owner. xmeta.db.port=metadata_repository_db_port Set to the port for the DB2 instance where the database is to be created. The port for xmeta.db.port must be the same as db2.port.number if this is a repository installation and the InfoSphere Information Analyzer database is to be created in the local DB2 instance. An example value is 50000.
207
xmeta.db.tablespace=z/OS_metdata_repository_table_space_name Set to the table space name to be created on the DB2 for z/OS database. This parameter is ignored for other databases. xmeta.db.type=[db2|db2zos|oracle|sqlserver] Set the database type for the metadata repository. An example value is db2. xmeta.db.username=metadata_repository_db_owner_ID Set to the operating system ID to be used as the metadata repository database owner ID. An example value is xmeta. xmeta.driver.type=[DB2_9|DB2_ZOS|ORACLE|SQL_SERVER] Set the driver type for the metadata repository. An example value is DB2_9.
Monitoring log files to monitor installation progress

You can follow the progress of an installation by monitoring log files. To monitor a log file, use the command tail -f logfilename where logfilename is the path and name of the log file. If the tail command is not available, open the log file in a text editor that does not lock the file for editing while it is open. To view updates, close the file and then reopen it.
Monitoring the IBM InfoSphere Information Server installation

You can follow the progress of the InfoSphere Information Server suite installation by monitoring the installation log files.
Before you begin

The monitoring procedures assume that you have installed InfoSphere Information Server in the default installation path. If your installation is different from the following path, substitute your path when you complete the procedures.
Operating system AIX Default installation path /opt/IBM/InformationServer
Procedure
1. On the computer on which the installation program is running, navigate to the ibm_is_logs directory that you specified as the temporary directory. The default temporary directory is:
Operating system AIX Directory /var/tmp
2. Open the log file:
208
Option Use the tail command
Procedure tail -f ISInstall*.log ISInstall*.log is the log file with the most recent date timestamp.
Use a text editor that does not lock the file
Close the file and then reopen it
Important: Do not delete the installation log files or the log file directory during the installation process.
What to do next
When installation is complete, save the log files for troubleshooting and verification purposes.
Monitoring the IBM WebSphere Application Server installation

You can follow the progress of the WebSphere Application Server installation by monitoring the installation log files.
Before you begin

About this task

The installation process updates the WebSphere Application Server suite installation log file sporadically. There might be gaps of up to 20 minutes when no updates are displayed.
Procedure
1. On the computer on which the installation program is running, navigate to the directory that contains the log file:
Operating system AIX Directory cd /opt/IBM/InformationServer/logs

Option Use the tail command Procedure tail -f WebSphereInstall*.log WebSphereInstall*.log is the log file with the most recent date timestamp. Use a text editor that does not lock the file Close the file and then reopen it
209
Monitoring the IBM WebSphere Application Server enterprise archive file deployment
You can follow the progress of the IBM WebSphere Application Server enterprise archive (EAR) file deployment by monitoring the installation log files.
Before you begin

About this task

Some EAR deployments can take up to 25 minutes, which can cause the installation program to seem as if it has stopped running.
Procedure
Operating system AIX Directory cd /usr/IBM/WebSphere/AppServer/profiles/ InfoSphere/log/server1

Option Use the tail command Procedure tail -f SystemOut*.log SystemOut*.log is the log file with the most recent date timestamp. Use a text editor that does not lock the file Close the file and then reopen it
Note: Do not delete the installation log files or the log file directory during the installation process.
Monitoring IBM InfoSphere DataStage component installations

You can follow the progress of individual IBM InfoSphere DataStage component installations by monitoring the component installation log files.
Before you begin

210
Default installation path /opt/IBM/InformationServer
About this task

You can monitor the installation of the following InfoSphere DataStage components: v InfoSphere DataStage plug-ins v Parallel engine operators v Connectors Each component must be installed into each project on each host system. If you have many projects, the plug-in installation can take considerable time.
Procedure
Operating system AIX Directory cd /opt/IBM/InformationServer/Server/ StagingArea/Log
2. Open the log file. Log files are in the following format
Option Use the tail command Procedure tail -f ISInstall*.log ISInstall*.log is the log file with the most recent date timestamp. Use a text editor that does not lock the file Close the file and then reopen it
Verifying and testing the installation

After you install IBM InfoSphere Information Server, verify that your installation was successful by running the IBM Support Assistant (ISA) Lite for InfoSphere Information Server tool. You can also verify the installation of individual components, such as the IBM InfoSphere Information Services Director.
Installation verification and troubleshooting

The ISA Lite for InfoSphere Information Server tool provides functionality to collect data, files, and artifacts from the local installation of IBM InfoSphere Information Server. It focuses on performing non-destructive tests and passive collection of data to report the system health and verify the correct configuration of the installation.
What the tool offers

The ISA Lite for InfoSphere Information Server tool helps you troubleshoot InfoSphere Information Server problems. The tool focuses on automatic collection
211
of problem data and provides diagnostic verifications of an InfoSphere Information Server installation. Information pertinent to a problem is collected and analyzed to identify the origin of the problem. The ISA Lite for InfoSphere Information Server tool reduces the effort and amount of time it takes you to send the appropriate diagnostic data to IBM Customer Support by automating the gathering and collection process. The tool FTPs the results to IBM Support and attaches them to an existing PMR (problem management record). Additionally, the tool performs symptom analysis to help streamline the problem determination process. To verify the installation, run the General Diagnostic Health Checker and other product-specific health checkers. The health checkers are available under the All Diagnostic Tools menu.
Where to find the tool

The ISA Lite for InfoSphere Information Server tool is installed in the IS_install_dir\ISALite folder when you run the installation program, where IS_install_dir is the directory where you installed InfoSphere Information Server. For information about how to get the tool for previous releases and for any updates that are available, see the ISA Lite download document on the support site (http://www.ibm.com/support/docview.wss?uid=swg24008662).
Documentation
Refer to the following documentation that is available under the \doc folder of the ISA Lite installation. IBM Support Assistant Lite for InfoSphere Information Server Quick Start Guide Provides an overview of the ISALite tool and what you must configure to get started. IBM Support Assistant Lite for InfoSphere Information Server User's Guide Provides a detailed description of the ISALite tool. Updates to the documentation are available on the support site (http://www.ibm.com/support/docview.wss?uid=swg27008317).
Testing the installation of IBM InfoSphere DataStage and IBM InfoSphere QualityStage
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 and QualityStage Designer client, you must be either an InfoSphere DataStage administrator or a lower-level user with specific project access granted by an administrator (in the Administrator client). If the services and engine tier do not share a user registry, then you must set up credential mapping. For more information, refer to the IBM InfoSphere Information Server Administration Guide.
Procedure
1. Start the IBM InfoSphere DataStage and QualityStage Administrator client:
212
a. On the computer where you installed the Administrator client, click Start > All Programs > IBM InfoSphere Information Server > IBM InfoSphere DataStage 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 in the list, type the URL into the field. The URL is in the form server_name:port_number. The server name and port values depend on whether IBM WebSphere Application Server clustering is set up within your services tier configuration and whether the services tier and engine tier are configured to use secure HTTP (HTTPS).
Table 68. Host and port values for different configurations WebSphere Application Server configuration Clustering is configured Port value (HTTP protocol) HTTP port of the front-end dispatcher (for example, 80). Do not use the port number of a particular cluster member. Port value (HTTPS protocol) HTTPS secure port of the front-end dispatcher (for example, 443). Do not use the port number of a particular cluster member.
Host value The host name or IP address of the front-end dispatcher (either the Web server or the load balancer). Do not use the host name of a particular cluster member. The host name or IP address of the computer where WebSphere Application Server is installed.
Clustering is not configured
HTTP transport port (configured as WC_defaulthost in WebSphere Application Server). Default: 9080
HTTPS transport secure port (configured as WC_defaulthost_secure in WebSphere Application Server). Default: 9443
d. Select the engine server name in the Host name of the Information Server engine 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 InfoSphere DataStage 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 in the list, type the URL into the field. The URL is in the form server_name:port_number. Use the same server name and port number that you used in the previous step. d. When you are prompted for the server and project, select the server and project in the Project list. If the values are not in the list, type them into the field. 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-clustered application server configuration) and the project is named my-project, type xyz/my-project.
213
Testing the IBM InfoSphere Information Services Director installation

After you install and configure IBM InfoSphere Information Services Director, test the installation.
Before you begin

You must have suite administrator credentials or have already set up credentials that have user authority.
Procedure
1. Start the IBM InfoSphere DataStage and QualityStage Administrator client: a. On the computer where you installed the InfoSphere Information Services Director client, click Start > All Programs > IBM InfoSphere Information Server > IBM InfoSphere Information Server console. b. Log in to the console with credentials that have the Information Services Director 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 in the list, type the URL into the field. The URL is in the form server_name:port_number. The server name and port values depend on whether IBM WebSphere Application Server clustering is set up within your services tier configuration and whether the services tier and engine tier are configured to use secure HTTP (HTTPS).
Table 69. Host and port values for different configurations WebSphere Application Server configuration Clustering is configured Port value (HTTP protocol) HTTP port of the front-end dispatcher (for example, 80). Do not use the port number of a particular cluster member. Port value (HTTPS protocol) HTTPS secure port of the front-end dispatcher (for example, 443). Do not use the port number of a particular cluster member.
Host value The host name or IP address of the front-end dispatcher (either the Web server or the load balancer). Do not use the host name of a particular cluster member. The host name or IP address of the computer where WebSphere Application Server is installed.
Clustering is not configured
HTTP transport port (configured as WC_defaulthost in WebSphere Application Server). Default: 9080
HTTPS transport secure port (configured as WC_defaulthost_secure in WebSphere Application Server). Default: 9443
2. Expand the Enabling Information Services section in the Getting Started pane to begin deploying integration logic as services, cataloging and registering services, and setting up credentials.
214
Chapter 7. Adding additional tiers or products to an installation

After you have installed IBM InfoSphere Information Server, you can add additional tiers or products to your installation. You use the InfoSphere Information Server installation program to install additional tiers and most additional products.
Adding product modules to an installation

You can add product modules to an existing IBM InfoSphere Information Server, Version 8.7 installation by running the installation program.
Before you begin

Choose your installation topology, review the installation checklists, and prepare the tier computers. Then, obtain the product media and configure your browser correctly so that the installation program runs smoothly. Ensure that you have a current backup of your InfoSphere Information Server installation. Do not use the InfoSphere Information Server installation program to add IBM InfoSphere DataStage editions or feature packs after initial installation. Instead, enable them by using the LicensingServiceAdmin tool. Refer to the IBM InfoSphere Information Server Administration Guide. Important: During the initial installation session, install all of the product modules that you plan to use either now or in the future. If you install only some of the product modules now, and then install fixes and service packs, you might need to reinstall the fixes and service packs if you add product modules later.
About this task

Depending on the product modules that you select, you might not have to run the installation program for all tiers. Not all product modules have components on all tiers. You only need to run the installation program on the tier computers that contain components for the product modules. You can skip tier computers that do not contain components for the product modules. The following table lists product modules and indicates the tier computers on which you must run the installation program.
Table 70. Product modules and the tiers on which you must run the installation program Product module IBM InfoSphere FastTrack IBM InfoSphere Information Analyzer Services tier X X Engine tier Metadata repository tier Client tier X
215
Table 70. Product modules and the tiers on which you must run the installation program (continued) Product module IBM InfoSphere Metadata Workbench IBM InfoSphere Business Glossary Services tier X Engine tier X Metadata repository tier Client tier X
IBM InfoSphere X Business Glossary Anywhere (requires InfoSphere Business Glossary). The client is installed separately. Metadata interchange agent and bridges (installs IBM InfoSphere Metadata Interchange Bridges for use with InfoSphere Metadata Asset Manager and Import Export Manager). All others X X X
The installation program only installs the appropriate software for the tiers on a computer. You can run the installation program on all of the computers in your configuration, and select the products to be installed each time. The installation program determines automatically which tiers exist on each computer and adds the appropriate components. Run the program on the computers in the following order: 1. Metadata repository tier, if the product modules you are installing require changes to this tier. If you preinstalled the database system for the metadata repository tier and configured the databases within the database system by using the scripts that are supplied with the installation media, you do not run the installation program on the metadata repository tier computers. 2. Services tier. All product module additions require changes to the services tier. 3. Engine tier, 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, and the engine tier is not present, first install the engine tier as described in the procedure.
216
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 the installation program on the metadata repository tier computer. Then run it on the services tier computer. Lastly, run the program on the engine tier. You can run the installation program on the client tier computers at any point in the sequence. InfoSphere DataStage and IBM InfoSphere QualityStage share many components. For this reason, if you add one of these product modules to a system on which the other product module is installed, the installation process runs faster. IBM InfoSphere Information Analyzer shares many of the same components as InfoSphere DataStage and InfoSphere QualityStage. The installation process for IBM InfoSphere Information Analyzer runs faster if InfoSphere DataStage or InfoSphere QualityStage is already installed.
Procedure
1. Verify that the appropriate software tiers are present in your installation to install the product module. If a required tier is not present, install and configure the tier as described in the Adding additional tiers to an installation topic. For example, if you installed only IBM InfoSphere FastTrack, your installation does not have an engine tier. To add InfoSphere DataStage, first create an engine tier. 2. Run the installation program on the computers. v Follow the prompts. When the installation program detects the existing installation and prompts you to choose whether to add additional products or tiers, select Add products. v Continue to follow the prompts to select the products to install and to complete the installation. 3. Repeat the process for each target computer. 4. Run the IBM Support Assistant Lite for InfoSphere Information Server tool to verify the installation.
What to do next
Configure the newly installed product modules. If you disabled scheduled tasks or deployed applications before running the installation program, restart the tasks and reenable the applications.
Adding additional tiers to an installation

You can add a software tier to a computer that already hosts one or more tiers, by running the installation program.
Before you begin

Choose your installation topology, review the installation checklists, and prepare the tier computers. Then, obtain the product media and configure your browser correctly so that the installation program runs smoothly. Ensure that you have a current backup of your InfoSphere Information Server installation.
Chapter 7. Adding additional tiers or products to an installation
217
Important: During the initial installation session, install all of the product modules that you plan to use either now or in the future. If you install only some of the product modules now, and then install fixes and service packs, you might need to reinstall the fixes and service packs if you add product modules later.
About this task

To add an additional software tier to a computer that already hosts one or more tiers, run the installation program on the target computer. You only need to run the installation program one time on each computer even if you are adding more than one tier. The installation program installs the tiers in the correct order on the computer. For client tier installations, if you want to include multiple versions of the clients on the same computer, install the earlier version clients on the computer before you install the Version 8.7 client tier. Install the clients in order from earliest version to latest version.
Procedure
1. Run the installation program on the computer. v Follow the prompts. When the installation program detects the existing installation and prompts you to choose whether to add additional products or tiers, select Add Tiers. If you are installing a client tier on a computer where an engine tier is installed, the client tier and engine tier must share the same base directory (for example, C:\IBM\InformationServer). Keep the following dependencies in mind when adding additional tiers to an installation:
Table 71. Tier dependencies Tier Metadata repository tier Services tier Engine tier Client tier Dependency None Metadata repository tier Services tier None
v Continue to follow the prompts to select the products to install and to complete the installation. 2. Run the IBM Support Assistant Lite for InfoSphere Information Server tool to verify the installation. Refer to the Installation verification and troubleshooting on page 211 topic for more information.
What to do next
Configure the newly installed product modules. If you disabled scheduled tasks or deployed applications before running the installation program, restart the tasks and reenable the applications.
218
Chapter 8. Removing IBM InfoSphere Information Server software

To remove InfoSphere Information Server from your computers, use the software removal utilities or remove the software manually.
Preparing to remove software

Before you run the software removal program to remove an installation or to remove product modules or tiers, back up critical data on your computers and make sure that the computers are ready for the removal process.
Before you begin

If you are running the software removal program in graphical mode, configure your browser so that the program runs correctly. For an installation that involves WebSphere Application Server clustering, perform the following tasks before you begin the software removal process: 1. Start management processes, including node agents. To ensure that sufficient file descriptor resources are allocated to the processes use the ulimit command. 2. Verify that you can start and stop the cluster and that you can restart the node agents. See Administering IBM InfoSphere Information Server and IBM WebSphere Application Server services in the IBM InfoSphere Information Server Administration Guide. 3. Verify that you can stop and start the Web server.
Procedure
Follow this procedure for each target computer: 1. Back up the following directories, your components, and critical data.
Operating system AIX Directory v /etc/services v /etc/inittab v /etc/passwd v /etc/group
See Backing up and restoring IBM InfoSphere Information Server in the IBM InfoSphere Information Server Administration Guide for more information on how to back up your current IBM InfoSphere Information Server installation. 2. Disable all scheduled jobs, scheduled tasks, scheduled reports, and enabled IBM InfoSphere Information Services Director applications before running the software removal program. 3. Disable firewall software and antivirus software during the software removal session. 4. 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 WebSphere
219
Application Server installation directory and profile directory to be root. Then start WebSphere Application Server as root.
Shutting down tasks and applications before removing software (service tier and engine tier)
Before running the software removal program, shut down scheduled tasks and disable IBM InfoSphere Information Services Director applications on both the service tier computer and the engine tier computer.
Before you begin

For installations that include the Pack for SAP BW or the Pack for SAP R/3 on the engine tier, shut down the SAP BW and SAP R/3 listeners. For details on shutting down the listeners, see the following troubleshooting technote (www.ibm.com/support/docview.wss?uid=swg21409098).
Procedure
1. Shut down all scheduled tasks, such as reports and log purge activities. To shut down these tasks, create an unfiltered schedule view within the IBM InfoSphere Information Server Web console, and then stop all 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 > Views of Schedules. d. In the Scheduling Views pane, click New Scheduling View. Enter a name and description in the Name and Description fields. Click Save and Close. Select the schedule view that you created in the previous steps. Click View Schedules. Select a schedule in the list, and click View Task. 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 the name of the schedule so that you can restart it after the software removal is completed. v If the Status value is not STARTED, click Close. j. Complete the previous step for each schedule in the list. For a product module or tier removal, do not restart the scheduled tasks until both the services and engine tiers are updated. 2. Disable any InfoSphere Information Services Director applications that are currently running. e. f. g. h. i. 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.
220
f. Repeat these steps for each deployed application. For a product module or tier removal, do not reenable the deployed applications until both the services and engine tiers are updated.
Configuring your browser for software removal

To run the software removal program successfully, you must configure your browser.
All browsers
v Verify that you have a supported browser. For details, go to the system requirements at www.ibm.com/support/docview.wss?uid=swg27021833. v Make sure that JavaScript is enabled.
Microsoft Internet Explorer

Make sure that the security zone for the computer allows the installation program to 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 installation program will run. 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. 3. 4. 5. Click Content. Enable Load images automatically. Enable Enable JavaScript. Click OK.
Removing IBM InfoSphere Information Server software by using the software removal program
To remove IBM InfoSphere Information Server software from your computers, you can run the InfoSphere Information Server software removal program. You can remove the entire software suite, individual product modules, or individual software tiers. Attention: Removing the entire software suite, individual product modules, or individual software tiers will result in data loss. Make sure that all file systems and databases are backed up before beginning a software removal.
221
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 you complete the wizard, you save your settings in a response file, and then continue using the wizard to complete the software removal. Alternatively, you can exit the program after saving the response file. The next time that you run the program in graphical mode, you can load the settings in your response file instead of specifying them again. You can also run the program in silent mode. In silent mode, the program uses the settings in a response file and does not display the graphical interface. Run the software removal program on all target computers, in the following order. If you are removing individual software tiers, the program removes all InfoSphere Information Server product module components that belong to the selected tiers. Also, the program removes all InfoSphere Information Server common components that belong to the selected tiers. You run the software removal program only once on each computer even if you are removing more than one tier. The removal program removes the tiers in the correct 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 a computer, you cannot remove a tier without removing the tiers that are dependent on it. 1. Client tier You can run the removal program on any point in the sequence. 2. Engine tier Engine, if your installation includes an engine tier. 3. Services tier If you installed IBM WebSphere Application Server by using the installation program, WebSphere Application Server is removed when the services tier is removed. If you preinstalled the application server, components that are specific to InfoSphere Information Server are removed. However, the application server is not removed. 4. Metadata repository tier If you installed IBM DB2 by using the installation program, the metadata repository database (and analysis database, if present) are dropped and DB2 is removed. If you used the installation program to create the metadata repository database or 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 installation program, do not use the installation program to remove the metadata repository tier.
Removing individual product modules

Depending upon the product modules that you select, you might not have to run the software removal program for all tiers. Not all product modules have components on all tiers. You only need to run the program on the tier computers that contain components for the product modules. The software removal program removes only the appropriate software for the tiers on a computer. You can run the software removal program on all of the computers
222
in your configuration, and select all tiers each time. The removal program determines automatically which tiers exist on each computer and removes the appropriate components. For example, to remove InfoSphere Information Analyzer, first run the software removal program on the engine tier computer. Then, run it on the services tier computer. Lastly, run the program on the metadata repository tier. You can run the software removal program on the client tier computers at any point in the sequence. If you remove all product modules that require a particular tier, the tier is also removed. For example, in a system that includes InfoSphere DataStage and InfoSphere Business Glossary, if you remove InfoSphere DataStage, the entire engine tier is removed because InfoSphere Business Glossary does not require it. The following table indicates the tier computers on which you must run the software removal program for specific product modules:
Table 72. Product modules and the tiers on which you must run the software removal program Product module IBM InfoSphere FastTrack IBM InfoSphere Metadata Workbench IBM InfoSphere Business Glossary Services tier X X X X Engine tier Client tier X X X
IBM InfoSphere X Business Glossary Anywhere (requires InfoSphere Business Glossary). The client is installed separately. IBM InfoSphere Metadata Interchange Bridges All others X X X
Specific product considerations

InfoSphere DataStage To deactivate an InfoSphere DataStage edition or feature pack (for example, if you are no longer entitled to an item), you do not use the IBM InfoSphere Information Server software removal program. Instead, deactivate them by using the LicensingServiceAdmin tool. InfoSphere DataStage and InfoSphere QualityStage share many components between them. For this reason, if you remove one of these product modules from the system on which the other product module is installed, the removal process is extremely rapid. If multiple versions of InfoSphere DataStage client programs are installed on a computer and you remove the Version 8.5 InfoSphere DataStage client
223
programs, older versions of the client programs might not function. To retain older InfoSphere DataStage client programs, complete 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. InfoSphere Information Analyzer Many of these components are also shared by InfoSphere Information Analyzer. The removal process for this product module is faster if InfoSphere DataStage or InfoSphere QualityStage remains installed.
Removing IBM InfoSphere Information Server by using the software removal program (graphical mode)
The software removal program leads you through the process of removing IBM InfoSphere Information Server. To run the software removal program in graphical mode, you can use a Web browser locally on the target computer. Alternatively, you can use a browser on any system that has network access to the computer where the program is running.
Before you begin

Complete the preparation steps that are described in Preparing to remove software on page 219.
About this task

To provide security during the software removal process, access to the software removal application is password protected. When you first start the software removal program, a non-graphical interface is displayed. You are prompted to create a password to use for the software removal session. The software removal program displays a wizard that prompts you for parameters and other data. After you choose your settings in the graphical interface, the program stores your settings in a response file. If you run the software removal program again, you can use the response file to perform the same software removal process again. Be mindful of the following conditions while the software removal program is running: v If you close your browser while the wizard is running, you can continue the same 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.
Procedure
1. Log in to the target computer.
224
Command Open a shell window on the target computer, or use a graphical desktop sharing system. Keep the shell window open during the entire installation process. If you use telnet or ssh, make sure that the session does not shut down or timeout for the duration of the installation.
Operating system AIX Command bash.sh export IBM_JAVA_OPTIONS= csh, tcsh unsetenv IBM_JAVA_OPTIONS
4. Run the software removal program. The following commands start the software removal process in graphical mode and include a response file.
Operating system AIX Procedure 1. Change to the _uninstall directory within the InfoSphere Information Server installation directory. By default, this directory is /opt/IBM/InformationServer. 2. Enter the following command to start the removal process../uninstall -uimode graphical -rsp file_name
A welcome message is displayed. Then the program describes how to access the graphical interface:
======> Installer available at: http://localhost:8080/ISInstall, and https://localhost:8443/ISInstall
Specify options to run the software removal program

After you run the software removal program, you must open a web browser, enter the URL that was specified by the removal program, and configure options before proceeding with the removal process. You can then specify options for each of the tier computers by using the InfoSphere Information Server removal program.
Procedure
1. Open a web browser on the computer or on a remote computer, and navigate to one of the addresses that is listed in the messages from starting the installation program. A Login Uninstallation window is displayed in the web browser. A message might appear in the browser that reads The publisher cannot be verified. You can safely ignore the message and continue the installation. This message does not indicate a security risk when it appears during InfoSphere Information Server installation. 2. To display installation messages in a language other than English, select the language in the Select a language menu, and click Login. 3. Accept the license agreement.
225
Removal prerequisites check fails

The software removal program runs an early prerequisites check before removing the product to ensure that the target computer meets all system requirements for the selections that you have made.
Symptoms
During the early prerequisites check, you received FAILED or WARNING messages.

Complete these steps by following the prompts in the wizard: 1. Double-click each message to learn more about resolving it. 2. Try to resolve each issue without exiting the software removal program. Then, click Check Again in the Prerequisites Check page. 3. If you must exit the software removal program, click Cancel and close your web browser window to end the session. Resolve the issues and then restart the software removal program.
Saving a response file and removing the product

You can save a response file to tell the IBM InfoSphere Information Server removal program how to perform a software removal by using your saved configuration information. Saving a response file is important if you want to cancel the current removal session and use the response file in a later session.
Procedure
1. In the software removal wizard, specify a name and location for the response file in the Response file location field (at this point, you can choose to cancel the removal and use the saved response file in a later session). 2. Click Remove IBM InfoSphere Information Server and save my settings in a response file, and then click Next to begin the product removal. The program displays a summary of the choices that you made in the wizard. As the removal proceeds, the software removal program reports the progress in the window. Be mindful of the following conditions while the software removal program is running: v Leave the command prompt open until the software removal is complete. v If the system encounters an error, it 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 program pauses for a long time, it might fail. v Pop-up windows might be displayed, that you must respond to for the software removal to proceed. Occasionally a pop-up window might be displayed behind the web browser. If the software removal program halts for a long interval, check for pop-up windows displayed behind the web browser. v After you have started the software removal process, keep the web browser open to monitor progress and to respond if there is an error. If you close the web browser, the software removal process continues to the end. You can reconnect to the session by opening a new web browser to the same URL. You can also monitor progress by reading the log files.
226
Removing IBM InfoSphere Information Server by using a response file (silent mode)
Using silent mode, you can run an unattended removal of InfoSphere Information Server software and complete multiple similar software removals quickly. For example, if you want to remove identical client tier software from multiple workstations, you can create a single response file and use silent mode to remove the software from each workstation, rather than repeatedly using the graphical user interface.
Before you begin

Obtain the product media and determine how you want to run the software removal program. In addition, ensure that you have created a response file. Note: Passwords are not saved in the response file. To use the response file in a subsequent installation, you must first edit the response file with a text editor and add passwords.
Procedure
1. Optional: Modify the EXCEPTION_POLICY environment variable. This variable determines how errors are processed that might occur when running in silent mode.
Operating System AIX Command setenv EXCEPTION_POLICY=n
n can be any of the following values: 1 2 Prompt user to try again on error (default behavior) Continue on error Important: Continuing with an installation after an error occurs could result in a nonoperational installation, or might cause existing installed software to stop functioning. Use this option only if directed by IBM Support. 3 Exit on error 2. Log in to the target computer.

Operating system AIX Command Open a shell window on the target computer, or use a graphical desktop sharing system. Keep the shell window open during the entire installation process. If you use telnet or ssh, make sure that the session does not shut down or timeout for the duration of the installation.
227
Command bash.sh export IBM_JAVA_OPTIONS= csh, tcsh unsetenv IBM_JAVA_OPTIONS
5. Run the software removal program. The following commands starts the software removal process in silent mode by using a response file.
Operating system AIX Procedure 1. Change to the _uninstall directory within the InfoSphere Information Server installation directory. By default, this directory is /opt/IBM/InformationServer. 2. Enter the following command to start the removal process../uninstall -rsp -verbose file_name
The -verbose option is optional. The option causes the installation program to display 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. The program runs a prerequisites check and displays the progress to the console. If a prerequisite check fails, the software removal program stops and displays an error. Correct the error before proceeding with the software removal process. Be mindful of the following conditions while the software removal program is running: v Leave the command prompt open until the software removal is complete. v If the system encounters an error, it 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 program pauses for a long time, it might fail. v Pop-up windows might be displayed that you must respond to for the software removal to proceed. When the installation is complete, the following message appears in the log file:
What to do next
If the software removal process fails, perform the following task to remove the software manually:
Operating system AIX Task Manually remove IBM InfoSphere Information Server (AIX )
If the software removal process succeeds, perform the following task:

Operating system AIX Task Complete software removal (AIX )
228
Software removal program encounters an error

During the software removal process, the removal program might encounter an error that requires your action to resolve.
Symptoms
The software removal program encounters an error and an Uninstallation Exception window appears.

Complete these steps in the Uninstallation Exception window: 1. Click Retry failed action and then click OK 2. If the problem recurs, review the last statements in the log file. See Chapter 12, Log files, on page 289 for more information. 3. If the issue can be resolved, fix the issue, and then click Retry.
Completing software removal

When the software removal process is complete, an Installation Summary for Current Computer page is displayed that contains the product, tiers, and product components that you installed, as well as information on how long the installation program ran and whether the installation was successful.
About this task

If the software removal process was successful, the following message is written to the log file:
Completing software removal (AIX )

After you remove IBM InfoSphere Information Server software from computers, perform the following steps to delete any remaining files and complete the software removal.
Removing leftover files from the services tier (AIX )

When you remove suite software, the software removal program removes only the files that were created as part of the installation of InfoSphere Information Server. You must manually remove other files from the services tier computer if you plan to reinstall the suite.
Before you begin

Run the software removal program and ensure that it completed successfully.
Procedure
1. Remove unused databases. a. If you created the metadata repository database before you installed InfoSphere Information Server, manually drop the metadata repository database. The default database name is xmeta. b. If you created the IBM InfoSphere Information Analyzer analysis database before you installed InfoSphere Information Server, manually drop the database. The default database name is iadb.
229
2. Delete the application server directory. v If you installed IBM WebSphere Application Server by using the InfoSphere Information Server installation program, complete the additional WebSphere Application Server removal steps that are listed in the IBM WebSphere Application Server Network Deployment documentation: For Version 7.0, go to the WebSphere Application Server information center and read Preparing for reinstallation after failed uninstallation. For Version 8.0, go to the WebSphere Application Server information center and read Cleaning your system after uninstalling the product. v If the WebSphere Application Server installation folder is empty, delete the folder. The default directory for the folder is /opt/IBM/WebSphere/AppServer. 3. If you used the local operating system user registry, delete the users that you created for InfoSphere Information Server. 4. 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, the profile is removed when you remove the suite from your computer. a. From a shell prompt, change to the WASHome/bin directory, where WASHome is the directory where the application server is installed. The default directory is /opt/IBM/WebSphere/AppServer. b. Run the following command to delete the application serer profile:
./manageprofiles.sh -delete -profileName profile
where profile is the name of the profile to be deleted. c. Delete the profile in the WASHome/profiles directory. 5. Remove any remaining InfoSphere Information Server users and groups if you are not using them for other purposes.
Removing leftover files from the engine tier (AIX )

When you remove suite software, the software removal program removes only the files that were created as part of the installation of InfoSphere Information Server. You must manually remove other files from the engine tier computer if you plan to reinstall the suite.
Before you begin

Procedure
1. Remove unused databases. a. If you created the metadata repository database before you installed InfoSphere Information Server, manually drop the metadata repository database. The default database name is xmeta. b. If you created the IBM InfoSphere Information Analyzer analysis database before you installed InfoSphere Information Server, manually drop the database. The default database name is iadb. 2. Delete the directory where you installed InfoSphere Information Server.
Operating System AIX Directory /usr/IBM/InformationServer
230
3. If you no longer need the dsadm account, delete this user and the related group. 4. Remove any remaining InfoSphere Information Server users and groups if you are not using them for other purposes.
Removing leftover files from the metadata repository tier (AIX )

When you remove suite software, the software removal program removes only the files that were created as part of the installation of InfoSphere Information Server. You must manually remove other files from the metadata repository tier computer if you plan to reinstall the suite.
Before you begin

Procedure
1. Remove unused databases. a. If you created the metadata repository database before you installed InfoSphere Information Server, manually drop the metadata repository database. The default database name is xmeta. b. If you created the IBM InfoSphere Information Analyzer analysis database before you installed InfoSphere Information Server, manually drop the database. The default database name is iadb. 2. Delete the directory where you installed InfoSphere Information Server.
Operating System AIX Directory /usr/IBM/InformationServer
3. If you installed the DB2 database system by using the InfoSphere Information Server installation program, delete the following directories: DB2 installation directory The default directory is /opt/IBM/db2/V9. DB2 instance owner directory Remove the /~db2inst1/sqllib directory, where ~db2inst1 is home directory of the instance owner. For example, the default home directory of the instance owner is typically /home/db2inst1. DB2 administrator directory Remove the /~dasusr1 /das directory, where ~dasusr1 is the home directory of the DB2 administrator. For example, the default home directory of the DB2 administrator is typically /home/dasusr1. 4. If you used the DB2 database system as the metadata repository and it no longer needs a DB2 user account, delete the DB2 user accounts. a. Run the id command to identify the related groups for the following DB2 user accounts: dasusr1, db2inst1, and db2fenc1.
bash-3.00$ id dasusr1 uid=210(dasusr1) gid=206(dasadm1) groups=1(staff)
b. Run the userdel command to delete the user accounts. c. Run the groupdel command to delete the related groups. 5. If you used an Oracle database system or a Microsoft SQL Server database system as the metadata repository, use an Oracle database system command or a Microsoft SQL Server database system command to drop the metadata repository user and schema.
231
6. Remove any remaining InfoSphere Information Server users and groups if you are not using them for other purposes.
Removing IBM InfoSphere Information Server software manually

If a previous installation or removal failed, you might have to manually remove the suite. You remove the software manually only after trying to use the software removal program.
Manually removing IBM InfoSphere Information Server (AIX )

If a previous installation or removal failed, you might have to manually remove the suite. You remove the software manually only after trying to use the software removal program.
Before you begin

Before you manually remove software, try to remove the suite on each computer in your installation by using the software removal program. If the software removal program fails to operate properly, follow this procedure to remove the entire InfoSphere Information Server instance. You can also use this procedure to delete any files that the software removal program does not automatically remove. Attention: Removing an InfoSphere Information Server installation also deletes any projects, jobs, models, and other user-created items that are associated with that installation. Before you remove the software, ensure that you have backed up all computers in the installation. See Backing up and restoring IBM InfoSphere Information Server in the IBM InfoSphere Information Server Administration Guide for more information on how to back up your current IBM InfoSphere Information Server installation. All scheduled tasks must be shut down, and IBM InfoSphere Information Services Director applications must be disabled. See Shutting down tasks and applications before removing software (service tier and engine tier) on page 220.
About this task

You cannot manually remove a single tier or product module only. A manual removal must remove the entire instance.
Manually removing InfoSphere Information Server from the services tier (AIX )
If you cannot remove suite software by using the software removal program, then you must manually remove files and directories from the services tier computer to ensure that the product is completely removed. Completely removing this files and directories is important if you plan to reinstall the suite.
Procedure
1. Back up the computer. 2. Log in as the root user and complete 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.
232
c. Run the following command to determine which startup entries to remove. The MetadataServer.sh files are started automatically by symbolic links in the rc directory. AIX : The directory is /etc/rc.d.
find /etc -name "*" -print | xargs grep -i installation_dir
where installation_dir is the directory where you installed InfoSphere Information Server. The default directory is /opt/IBM/InformationServer. d. Remove all entries that contain 99ISF. 3. Delete the application server directory. v If you installed IBM WebSphere Application Server by using the InfoSphere Information Server installation program, complete the additional WebSphere Application Server removal steps that are listed in the IBM WebSphere Application Server Network Deployment documentation: For Version 7.0, go to the WebSphere Application Server information center and read Uninstalling the WebSphere Application Server product. For Version 8.0, go to the WebSphere Application Server information center and read Cleaning your system after uninstalling the product. v If you pre-installed WebSphere Application Server manually, instead of reinstalling the product, delete the profile and then recreate it. 4. Delete the InfoSphere Information Server installation directory. The default directory is /opt/IBM/InformationServer. 5. Delete the temporary log files for the installation program by running the following command:
rm -rf /tmp/ibm_is_logs
Note: If you chose a different directory for the temporary files, delete that directory instead of the default directories. 6. Delete the InfoSphere DataStage installation location file by running the following command:
rm -rf /.dshome
7. Delete the InfoSphere DataStage log files by running the following command:
Operating system AIX Command rm -rf /ds_logs
8. Remove any InfoSphere Information Server users and groups if you are not using them for other purposes. 9. Restart the computer to ensure that all processes have been terminated.
Manually removing InfoSphere Information Server from the engine tier (AIX )
If you cannot remove suite software by using the software removal program, then you must manually remove files and directories from the engine tier computer to ensure that the product is completely removed. Completely removing this files and directories is important if you plan to reinstall the suite.
Procedure
1. Back up the computer. 2. Log in as the root user and complete the following steps to stop and remove services:
233
a. Change directories to the installation directory for the InfoSphere Information Server engine. The default location is /opt/IBM/ InformationServer/Server/DSEngine. b. Run the following command to source the dsenv file to configure the required environment variables:
. ./dsenv
c. Run the following command to stop the engine services:

./bin/uv -admin -stop
d. Change to the InfoSphere Information Server installation directory. The default directory is /opt/IBM/InformationServer. e. Run the following command to stop the agents:
./ASBNode/bin/NodeAgents.sh stop
f. Run the following command to determine which startup entries to remove. The NodeAgents.sh file is started automatically by symbolic links in the rc directory. AIX : The directory is /etc/rc.d.
find /etc -name "*" -print | xargs grep -i installation_dir
installation_dir is the directory where you installed InfoSphere Information Server. The default directory is /opt/IBM/InformationServer. g. Remove all entries that contain DSEngine or ISFAgent. h. Open the /etc/services file, and search for and remove the entry that starts with dsrpc entry. The following example shows what this entry might look like:
dsrpc 31538/tcp # RPCdaemon DSEngine@/opt/IBM/InformationServer/Server/ DSEngine
3. Delete the InfoSphere Information Server installation directory. The default directory is /opt/IBM/InformationServer. 4. Delete the temporary log files for the installation program by running the following command:
Note: If you chose a different directory for the temporary files, delete that directory instead of the default directories. 5. Delete the InfoSphere DataStage installation location file by running the following command:
rm -rf /.dshome
Manually removing InfoSphere Information Server from the metadata repository tier (AIX )
If you cannot remove suite software by using the software removal program, then you must manually remove files and directories from the engine tier computer to ensure that the product is completely removed. Completely removing this files and directories is important if you plan to reinstall the suite.
234
Procedure
1. Back up the computer. 2. If you installed IBMDB2 database system as part of the InfoSphere Information Server installation, remove the DB2 database system from the computer on which you installed the metadata repository tier. Removing the DB2 database system automatically removes the metadata repository database and the analysis database. a. 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 xmeta db2 drop database iadb
This example uses the default database names: xmeta and iadb. If you used different names, use your database names instead. c. If you installed the DB2 database system as part of the installation of InfoSphere Information Server and it is the only DB2 installation, remove the DB2 database system. See the DB2 Information Center for more information on removing DB2 9.7. d. Use the following commands to remove any remaining files:
rm rm rm rm rm rm rm rm -rf -rf -rf -rf -rf -rf -rf -rf /tmp/db2* /tmp/dascrt* /var/db2 /var/opt/db2 ~dasusr1/das ~db2inst1/db2inst1 ~db2inst1/sqllib /opt/IBM/db2
This example uses the default paths and user accounts. If you used different paths and user accounts, use your paths and user accounts instead. e. Remove any entries in the /etc/services file that start with DB2_db2inst1 or db2c_db2inst1 where db2inst1 is the name of the instance owner that you used during the suite installation. f. If the /etc/inittab file exists and this is the only DB2 database system installation, open the file and search for and remove the fmc entry. The following example shows what this entry might look like:
#DB2 Fault Monitor Coordinator fmc:number:respawn:/opt/IBM/db2/V9/bin/db2fmcd
3. If you used an existing installation of DB2 database system, use the DB2 command prompt to drop the metadata repository database and the analysis database. The default database names are xmeta and iadb. 4. If you used Oracle database system or Microsoft SQL Server database system to create the metadata repository database and the analysis database, manually drop the databases. The default database names are xmeta and iadb. 5. Delete the InfoSphere Information Server installation directory. The default directory is /opt/IBM/InformationServer. 6. Delete the temporary log files for the installation program by running the following command:
Note: If you chose a different directory for the temporary files, delete that directory instead of the default directories.
235
7. Delete the InfoSphere DataStage installation location file by running the following command:
rm -rf /.dshome
236
Part 3. Configuring the software after installation

To finish setting up InfoSphere Information Server, complete the tasks that correspond to the product modules that you installed or the features that you want to enable. For additional setup steps, see the documentation for your specific product modules.
237
238
Chapter 9. Configuring IBM InfoSphere Information Server

After you install the product, you must configure connections to your application server and databases, enable security, and configure other products in the suite. Completing these configuration tasks ensures that your installation of InfoSphere Information Server is set up to run optimally with minimal downtime.
Changing host names and ports

You can change your IBM DB2 host name and ports or your IBM WebSphere Application Server ports after installation.
Changing the WebSphere Application Server HTTP port

To change the IBM WebSphere Application Server HTTP server port, HTTP transport port, or HTTPS port, use the WebSphere Application Server administrative console, restart WebSphere Application Server, and then edit other configuration files.
About this task

This task applies to stand-alone (non-cluster) environments only.
Procedure
1. 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. Click Servers > Server Types > WebSphere application servers. 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 these files current avoids problems with future installations. Update the following Version.xml files: v The file that is on the server that hosts the engine tier v The file that is on the server that hosts the services tier On each server, the Version.xml file is located in the IBM InfoSphere Information 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" />
239
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:
<PersistedVariable encrypted="false" name="isf.http.port" persistent="true" readonly="true" value="port" />
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 239, specify the same value in the following XML element:
<PersistedVariable encrypted="false" name="was.default.host.port" persistent="true" readonly="true" value="port" />
g. If you changed the WC_defaulthost_secure value in step 1 on page 239, specify the same value in the following XML element:
<PersistedVariable encrypted="false" name="was.secure.default.host.port" persistent="true" readonly="true" value="port" />
4. Modify the registered-servers.xml file on each computer that hosts the services tier. This file is located in the following location, where installdir is the location of your InfoSphere Information Server installation directory.
Operating system AIX Installation directory installdir/ASBServer/conf/ Note: The typical installation location is /opt/IBM/InformationServer.
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="port" is-primary-server="true" />
There might be multiple <asb-server> elements in the registeredservers.xml file. Modify the <asb-server> elements for the servers whose port numbers are changing. c. Update the port value. d. Save your changes. 5. Modify the registered-servers.xml file on each computer that hosts the engine tier. This file is located in the following location, where installdir is the location of your InfoSphere Information Server installation directory.
Operating system AIX Installation directory installdir/ASBNode/eclipse/plugins/ com.ibm.isf.client
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="port" is-primary-server="true" />
There might be multiple <asb-server> elements in the registeredservers.xml file. Modify the <asb-server> elements for the servers whose port numbers are changing.
240
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 server lists in the login pages for some client applications. You can update these files if 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 that you log in. However, the old host name and port continue to display in the lists in some client application login pages unless you modify the registered-servers.xml file on the computer. Modify the file in one of the following ways: v Change the file in the same way that you modified the registeredservers.xml files on the engine tier computers. Note: On client-only computers, the is-primary-server="true" attribute does not appear in the <asb-server> element. v Run the RegistrationCommand command:
Operating system AIX Command cd /opt/IBM/InformationServer/ASBNode/bin ./RegistrationCommand -remove -hostname host -port port
Note: These commands use example installation directories, which might be different from your own setup. Tip: To use the RegistrationCommand command to add the new host name and port number for a new server entry, run the command:
Operating system AIX Command ./RegistrationCommand.sh -add -name host -hostname host -port port
Changing other WebSphere Application Server ports

After you change IBM WebSphere Application Server ports in the WebSphere Application Server administrative console, you must restart WebSphere Application Server, and then edit other configuration files.
Procedure
1. Change a port value in the WebSphere Application Server administrative console. a. Start the WebSphere Application Server administrative console. b. Click Servers > Server Types > WebSphere application servers. 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. 2. Stop and restart the application server.
Application server environment Stand-alone Procedure Stop and restart WebSphere Application Server
241
Application server environment Clustered
Procedure Stop and restart the WebSphere Application Server cluster member that you changed the port for
3. If you changed the SOAP_CONNECTOR_ADDRESS port value in the WebSphere port settings, you must update the wsadmin.properties file. Note: For a cluster environment, change wsadmin.properties file only if the SOAP_CONNECTOR_ADDRESS of the deployment manager is changed. Make sure to update the wsadmin.properties files of all the nodes and profiles of the cluster so that they point to the deployment manager. You do not need to update any file if you changed the SOAP_CONNECTOR_ADDRESS of a cluster member only. 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 the profile where IBM InfoSphere Information Server is installed. In a clustered environment, this is the name of the Custom profile where the cluster member, for which the port has been changed, is deployed.
Operating system AIX Directory opt/IBM/WebSphere/AppServer/profiles/ <profile>/properties/
Note: These file paths use example installation directories, which might be different from your own setup. b. Open the file by using a text editor, and locate the com.ibm.ws.scripting.port parameter. c. Change the parameter value to match value that you specified for SOAP_CONNECTOR_ADDRESS. d. Save any changes. Restart WebSphere Application Server after all other changes are complete. In a stand-alone environment, the default value of SOAP_CONNECTOR_ADDRESS is 8880. In a cluster environment, the default value of SOAP_CONNECTOR_ADDRESS for the deployment manager is 8879. The default value for SOAP_CONNECTOR_ADDRESS for a cluster member is 8880. Remember: For a cluster environment, repeat step 3 for all nodes and profiles in the cluster.
Changing the metadata repository database host name and port

You can change the metadata repository database host name or port by modifying configuration files and then changing values in the IBM WebSphere Application Server administrative console.
Updating the database dbalias attribute

You modify an XML file that exists in the ojb-conf.jar archive to update the host name of your metadata repository database.
242
Before you begin

Back up the ojb-conf.jar file to a directory outside of the IBM InfoSphere Information Server directory hierarchy.
Procedure
1. Stop the application server.
Application server configuration Stand-alone Clustered Procedure Stop IBM WebSphere Application Server Stop the WebSphere Application Server cluster members
2. Create a temporary empty directory and make it your default working directory:
mkdir tmp cd tmp
3. Locate the ojb-conf.jar file on one of the following servers, depending upon your configuration: v If your installation includes a clustered implementation of WebSphere Application Server, locate the file on the server that hosts the WebSphere Application Server Deployment Manager. v For non-clustered implementations, locate the file on the server that hosts the services tier.
5. Open the repository_database.xml file in a text editor. 6. Locate the dbalias attribute. The following table describes the attribute format.
Table 73. Attributes for different database system systems Database system IBM DB2 database system Oracle database system dbalias attribute dbalias="//host:port/dbname"
dbalias="oracle://host:port;ServiceName=service"
243
Table 73. Attributes for different database system systems (continued) Database system Oracle RAC dbalias attribute dbalias="oracle:// host1:port;ServiceName=service;AlternateServers=(host:port, host:port, host:port, ...)" dbalias="sqlserver://host:port;DatabaseName=dbname"
Microsoft SQL Server database system Microsoft SQL Server named instance
dbalias="sqlserver://host/named_instance:port;DatabaseName=dbname"
7. Modify the host and port values to match the host name and port values of the new metadata repository database host. 8. Save your changes and exit the text editor. 9. Navigate to the temporary directory that you created in step 2 on page 243 and compress the ojb-conf.jar file with the updated information.
Operating system AIX Command The following lines are part of a single command. The period (.) at the end of the command is required:/opt/IBM/WebSphere/ AppServer/java/bin/jar cf /opt/IBM/InformationServer/ASBServer/ apps/lib/ojb-conf.jar .
Propagating changes to IBM WebSphere Application Server

After you make changes to the files that are contained in the ojb-conf.jar file, you must propagate the changes to WebSphere Application Server so that they take effect. Copying the ojb-conf.jar file to IBM WebSphere Application Server in a stand-alone configuration (AIX ): To propagate changes to WebSphere Application Server in a stand-alone configuration, you must copy the ojb-conf.jar file to the directory where WebSphere Application Server is installed. Procedure 1. Stop WebSphere Application Server. 2. From the command line, navigate to the install_dir/ASBServer/apps/lib directory, where install_dir is the directory where you installed IBM InfoSphere Information Server. 3. Run the following command to copy the ojb-conf.jar file to the WebSphere Application Server apps/lib directory. Enter the command on a single line.
cp ojb-conf.jar /was_install_dir/AppServer/profiles/profile_name/informationServer/apps/lib
was_install_dir is the directory where you installed WebSphere Application Server.
244
profile_name is the name of your InfoSphere Information Server profile name for WebSphere Application Server. 4. Start WebSphere Application Server. Running the FilePropagator utility in a clustered configuration (AIX ): To propagate changes to IBM WebSphere Application Server in a clustered configuration, you must run the FilePropagator utility. You typically run this utility to propagate changed IBM InfoSphere Information Server shared libraries to WebSphere Application Server . Before you begin Use the isrecovery tool to back up InfoSphere Information Server components and data. See Backing up IBM InfoSphere Information Server components in the IBM InfoSphere Information Server Administration Guide for more information on how to run the isrecovery tool. About this task Attention: The FilePropagator utility requires 1.5 GB or more of temporary disk space to run. Ensure that the following directories have at least 1.5 GB of unused disk space before you run the FilePropagator utility:
Table 74. Temporary system directories that are used by the FilePropagator utility Operating system AIX Temporary directory var/tmp
Procedure 1. From the command line, navigate to the install_dir/ASBServer directory, where install_dir is the directory where you installed InfoSphere Information Server. 2. Run the following commands to make a copy of the apps/lib directory and the apps/eclipse directory.
rm -r profile/informationServer/apps mkdir -p profile/informationServer/apps cp -r apps/lib apps/eclipse profile/informationServer/apps
3. Stop the WebSphere Application Server cluster. 4. From the command line, run the FilePropagator utility. Enter the following commands on a single line.
bin/FilePropagator.sh -user wasadmin_user -password wasadmin_password -srcDir profile/informationServer/apps -destDir informationServer/apps
wasadmin_user is the user name that you are using to log into the application server. wasadmin_password is the password for the user name that you specified for wasadmin_user. 5. Start the WebSphere Application Server cluster.
Updating the database properties URL

You update the host and port names for your metadata repository database by specifying the values in the database.properties file.
245
Before you begin

Back up the database.properties file to a directory outside of the IBM InfoSphere Information Server directory hierarchy.
Procedure
1. Locate the database.properties file. This file is located in the ASBServer/bin/sql/ subdirectory of the IBM InfoSphere Information Server installation directory. 2. 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 75. URL keyword and value format for different database systems Database system IBM DB2 database system Oracle database system Oracle RAC Microsoft SQL Server database system Microsoft SQL Server named instance url keyword and value url=jdbc\:db2\://host\:port/dbname
url=jdbc\:ibm\:oracle\://host\:port;serviceName\ =service;AlternateServers\=(host:port, host:port, host:port, ...) url=jdbc\:ibm\:oracle\://racl\:1521;serviceName\ =orcl;AlternateServers\=(racl:1521, rac2:1521, rac3:1521) url=jdbc\:ibm\:sqlserver\://host\:port;DatabaseName=dbname
url=jdbc\:ibm\:sqlserver\://host\\ named_instance:port;DatabaseName=dbname
c. Change host and port to the same values that you specified in Updating the database dbalias attribute. d. Save the file. 3. Restart the application server.
Application server configuration Stand-alone Clustered Procedure Restart IBM WebSphere Application Server Restart the WebSphere Application Server cluster members
Configuring automatic client reroute

For IBM WebSphere Application Server to reconnect to the standby server smoothly in a DB2 clustered or HADR configuration, configure automatic client reroute.
About this task

In an IBM InfoSphere Information Server installation with a clustered DB2 database system setup, automatic client reroute can redirect WebSphere Application Server to connect to an alternate server when the primary server fails. The
246
alternate server is preregistered within automatic client reroute. When the failure occurs, automatic client reroute first tries to reconnect to the primary database. If the connection fails, automatic client reroute establishes a connection with the standby server. If an update, deletion, or insertion transaction was taking place and the failure occurred before the transaction was committed, the user receives an error message. When the user tries the transaction again, the standby server handles the transaction. If a read transaction was taking place, the read transaction is automatically run on the standby server, and no error message is displayed.
Procedure
1. Log in to the primary node. 2. Run the following command to configure automatic client reroute for the database. The standby_IP can be an IPv4 address or an IPv6 address, as shown in the following example:
For example:
Modifying the connection properties for data sources

You must modify the connection properties in the IBM WebSphere Application Server administrative console so that the metadata repository database can be found when WebSphere Application Server starts.
Procedure
1. Log in to the WebSphere Application Server administrative console. Use the WebSphere Application Server administrator username and password. 2. Click Resources > JDBC > Data sources. 3. Complete the following steps for the ASB JDBC DataSource, ASB JDBC XA DataSource, and Jreport JDBC DataSource data sources: a. b. c. d. Click the data source name in the window. Under Additional Properties, click Custom Properties. Modify the connection properties. For Oracle RAC, make the following changes: 1) Remove the following properties:
databaseName SID
2) Add the following properties. The property names are case sensitive:
serviceName service_name alternateServers (host1\:port,host2\:port,host3\:port)
serviceName Replaces the SID and is used to identify the Oracle RAC server. This value should match the serviceName value that you specified in the database.properties file. alternateServers Specifies the host names and ports of the servers in the Oracle RAC configuration. This value should match the AlternateServers value that you specified in the database.properties file.
247
e. In the Messages area at the top of the page, click Apply and then click Save to apply changes to the master configuration. f. Click the Save button again in the next page. g. Return to the Data sources page, click the data source that you modified, and click Test Connection. 4. For clustered metadata repository configurations (DB2 clustering or HADR, Oracle RAC), also update the alternate database host name and port information in WebSphere Application Server. See Specifying the alternate address and port for a DB2 database to connect to IBM WebSphere Application Server on page 132. 5. Log out of the console. 6. Restart the application server.
Application server configuration Stand-alone Clustered Procedure Restart IBM WebSphere Application Server Restart the WebSphere Application Server cluster members
Updating installation records

The Version.xml file contains the installation records that are used by the installation program. Updating the values in this file helps to avoid problems with future installations.
About this task

The Version.xml file is located in the IBM InfoSphere Information Server installation directory on the same server as the ojb-conf.jar file.
Procedure
1. Use a text editor to open the Version.xml file. 2. In the file, locate the following XML element:
<PersistedVariable encrypted="false" name="xmeta.db.hostname" persistent="true" readonly="true" value="myserver"/>
3. Modify the value attribute to the host name of your metadata repository database. 4. In the file, locate the following XML element:
<PersistedVariable encrypted="false" name="xmeta.db.port" persistent="true" readonly="true" value="1433"/>
5. Modify the value attribute to the port number for your metadata repository database. 6. Save your changes and close the Version.xml file.
Enabling Secure Sockets Layer (SSL)

IBM InfoSphere Information Server supports Secure Sockets Layer (SSL) communication between the application server and client components. If your environment requires confidentiality at the EJB or HTTP level, you can enable SSL.
About this task

SSL is not enabled by default within InfoSphere Information Server. If you do not configure HTTPS, HTTP is used instead. SSL adds greater security to your system,
248
but also requires more administrative work and can be error-prone. SSL carries a performance impact, so carefully consider the benefits and drawbacks before enabling SSL. You might not need SSL if you have a strong firewall in place, but SSL provides the following benefits: Encryption Data sent over an SSL connection is encrypted. Identification Communication is permitted only if the server is positively verified. Before communications begin, the server sends the client a certificate. The signature in the certificate is decrypted by the client to verify the authenticity of the sender. You can enable SSL for inbound secure HTTP (HTTPS) or inbound RMI/IIOP (EJB communication) client-server communication.
Procedure
1. Configure the application server to communicate by using SSL. 2. Configure InfoSphere Information Server components on the following tier computers to use SSL.
Engine tier computers v Agents v Command-line tools Services tier computers v Command-line tools Client tier computers v Command-line tools v Rich client programs Rich client programs include the InfoSphere Information Server console, the IBM InfoSphere DataStage and QualityStage Director, Designer, and Administrator clients, and the IBM InfoSphere FastTrack client
3. Use one of the following methods to configure rich client programs to communicate with the application server by using HTTPS.
Method Manual Procedure Edit configuration files on each computer that contains the components, and install the HTTPS certificate on the computer Configure the components from within the installation program during installation (this method is available for most installation scenarios)
Automatic
You must use the manual method in the following scenarios: v You install WebSphere Application Server by using the InfoSphere Information Server installation program. In this case, you must use the manual method after installation to configure the services tier for HTTPS. If you install the client tier or the engine tier in the same installation pass, you must also manually configure the tiers that you install in the pass for HTTPS.
249
v You install the client tier only in an installation pass, either on a computer that has no other tiers installed, or on a computer that has other tiers installed. In this case, you must use the manual method after installation to configure the client tier for HTTPS. 4. After SSL is enabled, specify the following HTTPS information:
Tool type To access web-based InfoSphere Information Server client tools To access rich client tools Procedure Specify an HTTPS URL and port in the web browser Specify an HTTPS-enabled port when logging in to each tool
Enabling SSL for inbound RMI/IIOP transport (stand-alone installation)

In IBM InfoSphere Information Server, Version 8.5 and later, SSL for RMI/IIOP is disabled by default. After you install or upgrade to Version 8.5 or later, you can enable Secure Sockets Layer (SSL) for IBM WebSphere Application Server, Versions 7.0 and 8.0.
About this task

Use the WebSphere Application Server administrative console to reenable this communication protocol in the application server after InfoSphere Information Server is installed. If you are upgrading from a previous version of InfoSphere Information Server that used SSL and you want to continue using SSL, you must enable SSL after installing Version 8.5 or later. If you prefer to use SSL or if your system requires confidentiality at the Enterprise JavaBeans (EJB) level, you must enable SSL because EJB clients interact with the Java Enterprise Edition (J2EE) EJB tier using the RMI/IIOP protocol. Important: You must run the UpdateSignerCerts tool on all client systems when any SSL changes occur in the cell, where a group of application servers and node agents are managed by a deployment manager. For example, when a certificate expires, you must run the tool on every client system in your application server environment.
Procedure
1. Start the WebSphere Application Server processes.
Operating system AIX Procedure Run the MetadataServer.sh or MetadataServer.bat script.
2. Log on to the WebSphere Application Server administrative console to set up your security settings.
Application server version Version 7.0 Procedure Go to the WebSphere Application Server information center and read Securing specific application servers
250
Application server version Version 8.0
Procedure Go to the WebSphere Application Server information center and read Multiple security domains
3. Click OK and save all changes. 4. Stop and restart all WebSphere Application Server processes.
What to do next
Run the IBM InfoSphere Information Server UpdateSignerCerts tool on every client system.
Enabling SSL for inbound RMI/IIOP transport (cluster installation)

In IBM InfoSphere Information Server, Version 8.5 and later, SSL for RMI/IIOP is disabled by default. After you install or upgrade to Version 8.5 or later, you can enable Secure Sockets Layer (SSL) for IBM WebSphere Application Server, Versions 7.0 and 8.0.
About this task

Use the WebSphere Application Server administrative console to reenable this communication protocol in the application server after InfoSphere Information Server is installed. If you are upgrading from a previous version of InfoSphere Information Server that used SSL and you want to continue using SSL, you must enable SSL after installing Version 8.5 or later. If you prefer to use SSL or if your system requires confidentiality at the Enterprise JavaBeans (EJB) level, you must enable SSL because EJB clients interact with the Java Enterprise Edition (J2EE) EJB tier using the RMI/IIOP protocol. Important: You must run the UpdateSignerCerts tool on all client systems when any SSL changes occur in the cell, where a group of application servers and node agents are managed by a deployment manager. For example, when a certificate expires, you must run the tool on every client system in your application server environment.
Procedure
1. Start the WebSphere Application Server processes. a. Ensure that all node agents are up and running. b. Start the WebSphere Application Server deployment manager by running the startManager command. 2. Log in to the WebSphere Application Server administrative console to set up your security settings.
Application server version Version 7.0 Procedure Go to the WebSphere Application Server information center and read Securing specific application servers
251
Application server version Version 8.0
Procedure Go to the WebSphere Application Server information center and read Multiple security domains
3. Click OK and save all changes. 4. Stop and restart all the WebSphere Application Server processes in the cell by stopping all application servers, node agents, and then the Deployment Manager. Then, start the Deployment Manager, all node agents, and all application servers.
What to do next
Run the IBM InfoSphere Information Server UpdateSignerCerts tool on every client system.
Running UpdateSignerCerts after enabling SSL or changing SSL settings

To enable SSL on a computer, you must retrieve the certificate from the server. To retrieve the certificate, run the UpdateSignerCerts tool. Also run the UpdateSignerCerts tool whenever an SSL change occurs in an IBM WebSphere Application Server cell.
About this task

The following table describes when and where to run the UpdateSignerCerts tool.
Table 76. When and where to run the UpdateSignerCerts tool When to run the UpdateSignerCerts tool After reenabling SSL for RMI/IIOP or HTTPS for the first time (after a new installation or after an upgrade). Where to run the UpdateSignerCerts tool Client tiers, engine tiers, and services tiers. WebSphere Application Server configurations Stand-alone and cluster configurations of WebSphere Application Server
After replacing or updating a Client tiers, engine tiers, and server certificate (for services tiers example, when a certificate expires). After installing a new IBM InfoSphere Information Server client or engine tier. New client tiers and new engine tiers (only if SSL is enabled)
Stand-alone and cluster configurations of WebSphere Application Server Stand-alone and cluster configurations of WebSphere Application Server WebSphere Application Server cluster configuration only
After adding a new managed Client tiers, engine tiers, and node to the cluster and a new services tiers (only if SSL is enabled) custom profile is created (horizontal clustering).
Procedure
1. Change to the directory in which the UpdateSignerCerts tool is located. The following table indicates the location from which to run the tool. The location depends upon which computer you are running it on and how WebSphere Application Server is configured:
252
Computer and configuration Services tier computer, clustered WebSphere Application Server environment
Run UpdateSignerCerts from this location The following path on the computer that hosts the Deployment Manager: AIX installdir/ASBServer/bin
If the computer that hosts the services tier also has the engine tier or client tier installed on it, run the UpdateSignerCerts tool in both the ASBServer/bin and ASBNode/bin directories on the computer. Services tier computer, non-clustered (stand-alone) WebSphere Application Server environment The following path on the services tier computer: AIX installdir/ASBServer/bin
If the computer that hosts the services tier also has the engine tier or client tier installed on it, run the UpdateSignerCerts tool in both the ASBServer/bin and ASBNode/bin directories on the computer. Engine tier computers The following path on each engine tier computer: AIX Client tier computers installdir/ASBNode/bin
The following path on each client tier computer: AIX installdir/ASBNode/bin
Metadata repository tier computer
You do not need to run the tool on this computer.
2. Use the following command to run the UpdateSignerCerts tool. The command retrieves a certificate from the server and adds it to the truststore file if the certificate does not already exist in the truststore file. The administrator user must have write permissions for the truststore file.
Operating system AIX Command ./UpdateSignerCerts.sh -host host_name -port port_number
UpdateSignerCerts command syntax

You use the UpdateSignerCerts command to retrieve the SSL certificate from the server.
Command syntax (AIX )

./UpdateSignerCerts.sh-hosthost_name-portport_number
Parameters
-host host_name If your installation has a separate front-end dispatcher, use the host name 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.
253
-port port_number If your installation has a separate front-end dispatcher, use the HTTPS port of the front-end dispatcher if it is configured for HTTPS. 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 if HTTPS is configured, or the HTTP transport port if HTTPS is not configured. If HTTPS is used, the tool might prompt you to accept an HTTPS certificate. 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 of default values. These values might or might not work, depending on your configuration: When the tool is run on a computer that hosts the services tier (other tiers might or might not be installed on the same computer): If the tool is run from the ASBServer/bin directory, the tool connects to the host and port that are designated as the primary-server in the registered-servers.xml file. This is the host and port that were specified during the services tier or engine tier installation unless the registered-servers.xml file was manually updated because of a change in the front-end dispatcher or a change in the HTTP or HTTPS port for the services tier. When the tool is run on a computer that hosts an engine tier (other tiers might or might not be installed on the same computer): If the tool is run from the ASBNode/bin directory, the tool connects to the host and port that are designated as the primary-server in the registered-servers.xml file. This is the host and port that were specified during the services tier or engine tier installation unless the registered-servers.xml file was manually updated because of a change in the front-end dispatcher or a change in the HTTP or HTTPS port for the services tier. When the tool is run on a client tier computer without an engine tier installed on the same computer: The -host and -port values are mandatory.
Manually configuring InfoSphere Information Server components to use HTTPS

If the installation program did not configure HTTPS for a tier computer during the installation process, follow this procedure to manually configure HTTPS for that tier computer.
About this task

The services tier and engine tier are properly configured for HTTPS if you select HTTPS during the installation of these tiers. If you did not select HTTPS during the installation of these tiers, you can manually configure HTTPS communications as described in this procedure. Each client tier must be manually configured to enable HTTPS communications with the services tier.
Procedure
1. (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 the
254
location of your InfoSphere Information Server installation directory. The ASBServer directory is present only if the computer hosts the services tier.
Operating system AIX Directory v installdir/ASBServer/conf v installdir/ASBNode/conf The typical installdir is /opt/IBM/ InformationServer.
2. (Client tier, engine tier, and services tier computers) Use the UpdateSignerCerts command to install the HTTPS certificate on the computer. See Running UpdateSignerCerts after enabling SSL or changing SSL settings on page 252. 3. (Engine tier and services tier computers) Update the port value in the Version.xml files. These files contain the installation records that are used by the installation program. Keeping these files current avoids problems with future installations. Update the following Version.xml files: v The file that is on the server that hosts the engine tier v The file that is on the server that hosts the services tier On each server, the Version.xml file is located in the IBM InfoSphere Information Server installation directory. Edit each file as follows: a. Use a text editor to open the Version.xml file. b. Locate the is.console.port element and change the value attribute to the HTTPS port number.
<PersistedVariable encrypted="false" name="is.console.port" persistent="true" readonly="true" value="80"/>
c. Locate the is.https element and change the value attribute to true.
<PersistedVariable encrypted="false" name="is.https" persistent="true" readonly="true" value="false"/>
d. Locate the isf.http.port element and change the value attribute to the HTTPS port number.
4. Navigate to the appropriate directory for the tier computer and modify the registered-servers.xml file. On the client tier computer, the list of servers in this file is used to populate the server lists in the login pages for some client applications. You update these files if 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 you log in. The old host name and port continue to display in the lists in some client application login pages unless you modify the registered-servers.xml file on the computer.
Tier computer Services tier Directory AIX : installdir/ASBServer/conf/
255
Tier computer Engine tier
Directory AIX : installdir/ASBNode/eclipse/plugins/ com.ibm.isf.client
Client tier
AIX : installdir/ASBNode/eclipse/plugins/ com.ibm.isf.client
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 registeredservers.xml file. Modify the port for all <asb-server> elements to reflect the port for the services tier. c. Update the port value. d. Save your changes. 5. Optional: (Client tier) To remove old server entries, run the RegistrationCommand command.
Operating system AIX Command cd installdir/ASBNode/bin ./RegistrationCommand.sh -remove -hostname host -port port
6. (Client tier) Update the browser bookmarks and URL shortcuts. Change each item so it uses https:// instead of http://, and so it references the HTTPS port instead of the HTTP port.
Replacing WebSphere Application Server certificates

To replace a certificate before it expires, or to use your own certificate, you can replace an IBM WebSphere Application Server certificate by specifying a different certificate for each node.
About this task

In clustered IBM InfoSphere Information Server installations, all signer certificates must be stored in the CellDefaultTrustStore truststore. In stand-alone InfoSphere Information Server installations, all signer certificates must be stored in the NodeDefaultTrustStore truststore. These trustores are the default locations for WebSphere Application Server signer certificates. In WebSphere Application Server, Version 6.1, when certificates expire or if the nodes are out of synchronization, you can replace a certificate by completing the steps in the following technote: http://www.ibm.com/support/ docview.wss?rs=180&uid=swg21305596. Although WebSphere Application Server, Version 6.1 is not supported in InfoSphere Information Server, Version 8.7, the example in this technote is still valid for manually replacing SSL certificates.
256
In WebSphere Application Server, Version 7.0 and Version 8.0, you can renew certificates. WebSphere Application Server generates a new certificate that replaces the old certificate. Alternatively, you can replace a certificate with your own certificate, or you can use a certificate signed by a certificate authority. Refer to the WebSphere Application Server documentation for details.
Procedure
1. Log in to the WebSphere Application Server administrative console. 2. Run the following script to start the application server:
Operating system AIX Script MetadataServer.sh
3. Use the startManager command to start the deployment manager. 4. Renew or replace the WebSphere Application Server certificate. See the WebSphere Application Server documentation for more information on how to renew the certificate: v For Version 7.0, go to the WebSphere Application Server information center and read Replacing an existing self-signed certificate. v For Version 8.0, go to the WebSphere Application Server information center and read Replacing an existing personal certificate. 5. 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. 6. Retrieve the signer certificate for the WebSphere Application Server client trust store. If the WebSphere Application Server client trust store does not include a signer certificate, the application server might fail. By default, WebSphere Application Server prompts you to accept the certificate if it is not trusted when you run the WebSphere Application Server command line utility, such as the serverStatus command or the stopServer command. Ensure that you accept the certificate before you stop or start WebSphere Application Server by using any other application. See the WebSphere Application Server documentation for more information on retrieving the signer certificate and establishing trust for your certificate: v For Version 7.0, go to the WebSphere Application Server information center and read Secure installation for client signer retrieval in SSL. v For Version 8.0, go to the WebSphere Application Server information center and read Secure installation for client signer retrieval in SSL.
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 or changing SSL settings on page 252.
Switching from HTTPS back to HTTP

If your IBM InfoSphere Information Server installation is configured for secure HTTP (HTTPS), you can configure it to use HTTP instead. You might not require HTTPS if you do not need to encrypt data or if you have a strong firewall in place.
257
Procedure
1. (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 of your InfoSphere Information Server installation directory. The ASBServer directory is present only if the computer hosts the services tier.
Operating system AIX Directories v installdir/ASBServer/conf v installdir/ASBNode/conf The typical installdir is /opt/IBM/ InformationServer.
2. (Engine tier and services tier computers) Change the port value in the Version.xml files. These files contain the installation records that are used by the installation program. Keeping these files current avoids problems with future installations. Update the following Version.xml files: v The file that is on the server that hosts the engine tier v The file that is on the server that hosts the services tier On each server, the Version.xml file is located in the IBM InfoSphere Information Server installation directory. Edit each file as follows: a. Use a text editor to open the Version.xml file. b. Locate the is.console.port element and change the value attribute to the HTTP port to use.
<PersistedVariable encrypted="false" name="is.console.port" persistent="true" readonly="true" value="port" />
c. Locate the is.https element and change the value attribute to false.
<PersistedVariable encrypted="false" name="is.https" persistent="true" readonly="true" value="true"/>
d. Locate the isf.http.port element and change the value attribute to the HTTP port to use.
3. Navigate to the appropriate directory for the tier computer and modify the registered-servers.xml file. On the client tier computer, the list of servers in this file is used to populate the server lists in the login pages for some client applications. You update these files if 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 you log in. The old host name and port continue to display in the lists in some client application login pages unless you modify the registered-servers.xml file on the computer.
Tier computer Services tier Directory AIX : installdir/ASBServer/conf/
Engine tier
AIX : installdir/ASBNode/eclipse/plugins/ com.ibm.isf.client
258
Tier computer Client tier
Directory AIX : installdir/ASBNode/eclipse/plugins/ com.ibm.isf.client
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 registeredservers.xml file. Modify the port for all <asb-server> elements to reflect the port for the services tier. c. Update the port value. d. Save your changes. 4. Optional: (Client tier) To remove old server entries, run the RegistrationCommand command.
Operating system AIX Command cd installdir/ASBNode/bin ./RegistrationCommand.sh -remove -hostname host -port port
5. (Client tier) Update the browser bookmarks and URL shortcuts. Change each item so it uses https:// instead of http://, and so it references the HTTPS port instead of the HTTP port.
Configuring security for IBM InfoSphere Information Server

InfoSphere Information Server provides tools to configure your system operations and provide access to various data types. Before users can access different functions and data sets, you must create a user registry, create users and groups in the registry, and assign security roles to define your security profile.
About this task

The following list outlines the tasks that you do to set up security for IBM InfoSphere Information Server. For details on completing each task, refer to the IBM InfoSphere Information Server Administration Guide.
Procedure
1. Choose a user registry and configure it for InfoSphere Information Server. A user registry contains valid user names and passwords. To log in to InfoSphere Information Server, a user must have a user name and password in the user registry. The installation program configures InfoSphere Information Server to use its internal user registry. As part of security setup, you can configure InfoSphere Information Server to use an external user registry such as the local operating system user registry or a Lightweight Directory Access Protocol (LDAP) user registry. 2. Create users and groups in the user registry. If InfoSphere Information Server is configured to use the internal user registry, create users and groups by using
259
the InfoSphere Information Server console or the InfoSphere Information Server Web console. If InfoSphere Information Server is configured to use an external user registry, use standard operating system utilities or user registry utilities. 3. Assign security roles to users and groups. Security roles determine which suite components each user or group has access to and what level of access that user or group has in the suite component. 4. Configure InfoSphere Information Server engine security. The InfoSphere Information Server engine performs user authentication separately from other InfoSphere Information Server components. Depending upon your user registry configuration, you might have to map credentials between the InfoSphere Information Server user registry and the local operating system user registry on the computer where the engine is installed. 5. Assign project roles to users. Assign project roles if required by the installed suite components. 6. Optional: Configure IBM WebSphere Application Server for non-root administration. By default, WebSphere Application Server runs as root. However, it can also be run by using a non-root user ID. You can configure and set appropriate file system permissions for WebSphere Application Server to "run-as" a non-root user ID. 7. Optional: Configure InfoSphere Information Server agents for non-root administration. By default, the InfoSphere Information Server agents (such as the ASB and logging agents) run as root. However, they can also be run by using a non-root user ID. You can configure and set appropriate file system permissions for the agents to "run-as" a non-root user ID. 8. Optional: Configure the Auditing service. The Auditing service creates an audit trail of security-related events. These events include all security-related settings changes and user login and logout operations. You can configure which audit events to log and how much information to include based on your auditing requirements.
260
Chapter 10. Configuring a parallel processing environment

Some tasks are required to configure the parallel engine, and some tasks ensure the parallel engine is running smoothly. A well-performing parallel engine requires monitoring and adjustment to various settings, such as network, processor, and kernel parameter settings.
Adding computers to share engine processing

To configure an massively parallel processing (MPP) system that runs the parallel engine on multiple computers, copy the parallel engine components to each computer, then configure the parallel engine on each computer. Each user who runs parallel jobs must have rsh or ssh access to each computer where the parallel engine components are copied.
Configuring computers to be compute nodes for in an MPP system (AIX )

Follow this procedure to configure your computers to act as a compute nodes in a parallel processing cluster.
About this task

A parallel processing configuration consists of a conductor node that contains the IBM InfoSphere Information Server engine, and compute nodes that contain parallel engines.
Procedure
1. Make the parallel engine components available to each compute node. 2. Configure the parallel engine to run the remote shell (rsh) or the secure shell (ssh) without a password on all compute nodes 3. Set user privileges to run parallel jobs. 4. If you did not globally cross-mount the Projects directory in step 1, set up a method of distributing the transform libraries to the compute nodes.
Making the parallel engine components available to compute nodes (AIX )

When you configure an MPP system, you must make the parallel engine components available to all computers in your MPP system.
About this task

Use one of the following methods to make the parallel engine available to all the compute nodes in the MPP system: v You can globally cross-mount, typically by using network file system (NFS), a single directory on a single system containing the parallel engine software. This configuration makes software upgrades more convenient than if the parallel engine components are installed on all processing systems. If you are using NFS to globally mount the directory, mount it using the soft link option.
261
v You can use a script to copy the parallel engine components to a directory with the same path name on all processing systems that you designate for processing parallel jobs.
Procedure
1. Cross mount your directories. Ensure that all mounted directories are exactly the same path from the root directory on all nodes.
Option For non-NFS disks Description 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). 1. On the computer where you installed the IBM InfoSphere Information Server engine, change the directory to the directory where you installed InfoSphere Information Server (by default /opt/IBM/InformationServer/Server). 2. Change the directory to your InfoSphere Information Server projects directory (by default /opt/IBM/InformatonServer/ Server/Projects).
For NFS disks
2. For non-NFS disks, enter the following command to copy

install_dir/install/copy-orchdist node1 node2 ... nodeN
For node1 to nodeN specify the new node names, separated by spaces. 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 InfoSphere DataStage and QualityStage Parallel Job Developer's Guide.
Configuring the parallel engine to use the secure shell (ssh) program (AIX )
The secure shell (ssh) program provides strong authentication and secure communications between computers on a network.
Before you begin

Ensure that ssh servers are installed on all of the computers where the parallel engine runs.
About this task

When you configure ssh to work with the parallel engine, the engine connects from the conductor node to all of the compute nodes, using RSA public key encryption for authentication. To set up ssh, do the following task for each user that runs parallel jobs. It is also necessary to log in to each computer before it can run parallel jobs.
Procedure
1. On the conductor node, run the following command to create public and private encryption keys. Press the Enter key twice when you run the command.
ssh-keygen -b 1024 -t rsa -f ~/.ssh/id_rsa
262
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 each user on each compute node.
cd ~/.ssh scp id_rsa.pub user@secondary_computer:~/.ssh
3. Log in to each of the compute nodes and add the public key to the list of authorized keys. Repeat this process for each user that runs parallel jobs.
cd .ssh cat id_rsa.pub >> authorized_keys2 chmod 640 authorized_keys2 rm -f id_rsa.pub
The file that contains the authorized keys might be named authorized_keys or authorized_keys2, depending on the version of ssh. 4. On the conductor node, run the following command for each user and compute node to test the ssh configuration:
conductor_node_name% ssh computer_node_name ls
If the command is successful, you should be able to log in to the remote shell without providing a password. 5. On the conductor node, create the remsh file in the /Server/PXEngine/etc/ directory. In the file, specify the following content:
#!/bin/sh exec /usr/bin/ssh "$@"
The /Server/PXEngine/etc/ directory is located in the directory where you installed the engine. The default directory is /opt/IBM/InformationServer/ Server/PXEngine/. 6. Give the file execute permission:
chmod 755 remsh
Allowing users to run the remote shell program (rsh) without a password (AIX )
If you do not want to use a secure shell connection, you can choose instead to use rsh for each parallel engine connection. As with ssh, the connections must be able to be established without a password prompt.
About this task

You achieve rsh connections differently according to your type of system. For example, you can edit the /etc/hosts.equiv file or create a .rhosts file for each user. In both cases, add the host name of each parallel processing node to the /etc/hosts.equiv file or the .rhosts file, specifying one host name per line. The host name that is included in this file must correspond to the setting of the node fastname parameter in the parallel configuration file, which is located in the /opt/IBM/InformationServer/Server/PXEngine directory by default.
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 any other user (file mode of 600).
263
v Create a .rhosts file for each user. The file must be located in the home directory of each parallel user, be owned by the user, and grant read/write access 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 a password:
rsh host_name uptime
host_name is the name of a compute node. If host_name is accessible, this command prints a message displaying the time it has been up. Specifying the location of the remote shell (rsh) program (AIX ): When the parallel engine tries to establish a remote shell, it searches for the remote shell (rsh) program in a specific set of paths, in a specific order. If the rsh program is not in one of these paths, you must specify the path location explicitly in the remsh file. 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 /usr/lpp/ssp/rcmd/bin/rsh v /usr/ucb/rsh v /usr/bin/remsh v /bin/remsh v /usr/bin/rsh If the rsh program is not in one of these paths, follow this procedure to specify the path to rsh in the first path that 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/sh exec /usr/bin/rsh "$@"
2. Edit the last line of the shell script to invoke the specific remote shell command that you are using. For example:
#!/bin/sh exec /usr/local/remsh "$@"
3. To ensure that all users can run the command, run the chmod command:
chmod 755 install_dir/etc/remsh
4. Test the shell script by running rsh on each processing node:

rsh node_name uptime
Setting user privileges to run parallel jobs (AIX )

All users who run parallel jobs must have the necessary privileges on all processing nodes.
Procedure
Ensure that each user who runs parallel jobs has the following privileges: v Log in access.
264
v 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 path specified in the $APT_ORCHHOME environment variable set in the project, or overridden in the parameters for the job. The installation default is /ishome/Server/PXEngine.
Distributing transform libraries to compute nodes

If you cannot globally cross-mount the Projects directory, you must set up a method for distributing compiled transform libraries to all physical compute nodes in the cluster.
About this task

If the project directory is not shared among all servers in a cluster configuration or MPP configuration, then you must choose one of the following methods for distributing the transform libraries:
Table 77. Transform library distribution methods Method Manually distribute the transform libraries. Configuration Use operating system commands to copy the transform libraries to all compute nodes. Advantages Disadvantages
This is the simplest method. This method is time-consuming and error-prone. Also, it requires a time window when jobs are not running on the system. This method is automatic and does not require manual intervention. This method adds the startup overhead. Also, it works correctly only with single instance jobs.
Copy the transform libraries Set the APT_COPY_ automatically at runtime. TRANSFORM_OPERATOR environment variable to True. The environment variable can be set at the job or project level. Copy the transform libraries Set the APT_DIST_ automatically at compile TRANSFORM_OPERATOR time. environment variable to a list of all server names participating in the cluster. The environment variable can be set at the job or project level. The list of server names is merged with the list of fastnames referenced in the configuration file that is used to compile the jobs. If no configuration file is specified, the default configuration file is used.
This method is also automatic and does not require manual intervention. This method does not incur any startup overhead. The method works correctly with both single and multi-instance jobs. This method ensures that compiled transform libraries are distributed to all participating compute nodes regardless of the configuration file that is used at compile time.
This method requires that a compiler be present on the conductor node. This requirement could be difficult to meet in production environments.
Note: If you use compile-time distribution you do not need to use runtime distribution.
265
Setting up a C++ compiler

The computer where you install the IBM InfoSphere Information Server engine must have a C++ compiler. The job compilation process uses it to compile parallel jobs with transformer stages, buildop components, and some lookup stages. To function correctly, the transform feature of the parallel canvas requires the compiler. The parallel canvas requires that the compiler and SDK be installed in their default locations. For some compilers, each developer must have a license at the time that the developer compiles the job with the Designer client. The maximum number of simultaneous processes that compile jobs determines the number of licenses. Install only one compiler on each engine tier for development environments. For production environments, you do not need a C++ compiler unless you have set up a parallel processing environment in which transform libraries are distributed at compile time. Also, some operating systems require additional C++ runtime libraries. For the list of supported C++ compilers, see the system requirements for your operating system: www.ibm.com/support/docview.wss?uid=swg27021833. When InfoSphere Information Server is installed, the compiler settings are preset. However, for some compilers you might need to alter the settings after installation.
Setting up a compiler on IBM AIX

For AIX systems, install a supported compiler and then set compiler parameters before you create and run parallel jobs.
About this task

Complete this task for every engine tier computer where jobs will be recompiled. The compiler settings must be specified for each project that requires them.
Procedure
1. Install the compiler. For information about supported compilers, see the system requirements at www.ibm.com/support/docview.wss?uid=swg27021833. 2. Log into the IBM InfoSphere DataStage and QualityStage Administrator using an account with administrator authority. 3. Select Projects. 4. For each project listed in the window, complete these steps to update compiler settings so that the transforms can be compiled successfully: a. Click the project name, and click Properties. b. Click Environment. c. Select Parallel > Compiler. d. Select APT_COMPILEOPT. In the Value column, change the value to -c -O -q64 e. Select APT_COMPILER. In the Value column, change the value to /usr/vacpp/bin/xlC_r f. Select APT_LINKER. In the Value column, change the value to /usr/vacpp/bin/xlC_r g. Select APT_LINKOPT. In the Value column, change the value to -G -q64
266
h. Click OK. i. Click OK. 5. Click Close.
Setting environment variables for the parallel engine

You 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 all supported operating systems. You can set the environment variables by using the IBM InfoSphere DataStage and QualityStage Administrator.
Procedure
1. Log in to the Administrator client. 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 engine

Set the listed environment variables depending on whether your environment meets the conditions stated in each variable. See the chapter regarding environment variables in the IBM InfoSphere DataStage and QualityStage Parallel Job Advanced Developer's Guide for a complete listing of environment variables that you can set.
Network settings
APT_IO_MAXIMUM_OUTSTANDING If the system connects to multiple processing nodes through a network, set the APT_IO_MAXIMUM_OUTSTANDING environment variable to specify the amount of memory, in bytes, to reserve for the parallel engine on every node for TCP/IP communications. The default value is 2 MB. If TCP/IP throughput at that setting is so low that there is idle processor time, increment it by doubling the setting until performance improves. If the system is paging, however, or if your job fails with messages about broken pipes or broken TCP connections, the setting is probably too high. APT_RECVBUFSIZE If any of the stages within a job has a large number of communication links between nodes, specify this environment variable with the TCP/IP buffer space that is allocated for each connection. Specify the value in bytes. The APT_SENDBUFSIZE and APT_RECVBUFSIZE values are the same. If you set one of these environment variables, the other is automatically set to the same value. These environment variables override the APT_IO_MAXIMUM_OUTSTANDING environment variable that sets the total amount of TCP/IP buffer space that is used by one partition of a stage.
267
APT_SENDBUFSIZE If any of the stages within a job has a large number of communication links between nodes, specify this environment variable with the TCP/IP buffer space that is allocated for each connection. Specify the value in bytes. The APT_SENDBUFSIZE and APT_RECVBUFSIZE values are the same. If you set one of these environment variables, the other is automatically set to the same value. These environment variables override the APT_IO_MAXIMUM_OUTSTANDING environment variable that sets the total amount of TCP/IP buffer space that is used by one partition of a stage.
Transform library
If you are working on a non-NFS MPP system, set the following environment variables: v Set the APT_COPY_TRANSFORM_OPERATOR environment variable to true. This environment variable is set to false by default. IBM InfoSphere DataStage and QualityStage Administrator users must have the appropriate privileges to create project directory paths on all the remote nodes at runtime. v Set the APT_DISABLE_TRACKER_STARTUP environment variable to 1. The value '1' allows the job to run without starting the Resource Tracker. You can set this environment variable in the Administrator client Projects tab, on the Parallel page. You must have the appropriate level of administrator privilege to set the environment variable.
Job monitoring
By default, the job monitor uses time-based monitoring in the InfoSphere DataStage and QualityStage Administrator Director. The job monitor window is updated every five seconds. You can also specify that the monitoring is based on size. For example, the job monitor window is updated based on the number of new entries. To base monitoring on the number of new entries, set a value for the APT_MONITOR_SIZE environment variable. If you override the default setting for the APT_MONITOR_TIME, the setting of the APT_MONITOR_SIZE environment variable is also overridden.
Detailed information about jobs

To produce detailed information about jobs as they run, set the APT_DUMP_SCORE value to True. By default, this environment variable is set to False.
C++ compiler
The environment variables APT_COMPILER and APT_LINKER are set at installation time to point to the default locations of the supported compilers. If your compiler is installed on a different computer from the parallel engine, you must change the default environment variables for every project by using the Administrator client.
Temporary directory
By default, the parallel engine uses the C:\tmp directory for some temporary file storage. If you do not want to use this directory, assign the path name to a
268
different directory by using the environment variable TMPDIR.
Configuring the parallel engine (AIX )

Complete the following tasks to configure the parallel engine.
Setting the maximum number of processes for parallel jobs (AIX)

The setting of the maxuproc kernel parameter on each parallel engine node controls the maximum number of processes per user for that node. Use the chdev command to set an appropriate value.
About this task

A user who runs parallel jobs must be able to run at least 1000 processes on each processing node. Large systems and symmetric multiprocessing (SMP) servers require more than 1000 processes. Complete the following steps on each computer that acts as a processing node in your parallel environment.
Procedure
1. 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 command to 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 sufficient resources. Use the chuser command to set appropriate values.
About this task

The following table describes the parameters that control memory resources and recommends a value for each parameter. Complete the following steps for each user on each processing node in your parallel environment.
Table 78. Per-user kernel parameter values Parameter fsize data Description The largest file that a user can create. The largest data segment, or heap, that a program can have. The largest stack that a program can have. Value 2 GB minus 512 bytes (4,194,303 512-byte blocks). 128 MB (262,144 512-byte blocks) or more. For no limit, specify -1. 32 MB (65,536 512-byte blocks) or more.
stack
269
Table 78. Per-user kernel parameter values (continued) Parameter rss Description The maximum amount of physical memory that a user process can use. Value 64 MB (131,072 512-byte blocks) or more.
Procedure
1. 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, and rss. 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 78 on page 269. The command has the form:
/usr/sbin/chuser param=value user_name
For example:
/usr/sbin/chuser /usr/sbin/chuser /usr/sbin/chuser /usr/sbin/chuser fsize=4194303 operator2 data=262144 operator2 stack=65536 operator2 rss=131072 operator2
4. In an AIX cluster, you can use the dsh command to set the kernel parameters on all cluster nodes. This command must be issued from the control workstation.
dsh -a chuser param=value user_name
What to do next
Users whose per-user kernel parameters have changed must log out and log in again for the changes to take effect.
Setting the paging space for the parallel engine

To process parallel jobs that have large amounts of data, specify the minimum paging space settings.
Setting the paging space for the parallel engine (AIX)

To process parallel jobs that have large amounts of data, specify the minimum paging space settings.
Before you begin

Attention: You must be a system administrator logged in as the root user to reset the system paging space.
About this task

The minimum amount of paging space to run parallel jobs is 500 MB per processor for computers that have fewer than 20 processors and 1 GB per processor for computers that have 20 or more processors. The design of the parallel jobs and the
270
number of jobs that you plan to run at one time affect the paging space requirement. Jobs that have many individual stages require more paging space than jobs that have fewer individual stages. Running more than one job at a time requires more paging space. Complete this procedure on each computer in your parallel processing environment.
Procedure
1. 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 79. Results of lsps command Page space paging01 paging00 hd6 Physical volume hdisk1 hdisk2 hdisk0 Volume pagevg rootvg rootvg Group size 2000 MB 192 MB 64 MB % Used 1 5 23 Active yes yes yes Auto yes yes yes Type lv lv 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 (approximately 2.2 GB). 2. See the AIX documentation for additional information about setting the paging space.
Updating the /etc/magic file

Edit the /etc/magic file to include data set descriptor files for the parallel engine.
About this task

The file command examines a file to classify it by type. The command reads the /etc/magic file to identify files that have a magic number. The magic number is a constant that specifies the file type. The install_dir/etc/magic file contains additions to the /etc/magic file that are specific to the parallel engine. The install_dir directory is the top-level directory of the parallel engine installation. The default path is /opt/IBM/InformationServer/ Server/PXEngine/.
Procedure
1. 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 to the /etc/magic file. For example: 0 string Torrent IBM Information Server parallel 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
271
where file_name is the name of a data set descriptor file. For example, if you enter file t1.ds, the following command returns:
t1.ds: IBM Information Server parallel engine dataset descriptor
Configuring database connectivity in a parallel environment

The following topics describe the steps to take to connect to various databases from a parallel job.
Configuring access to DB2 databases

Configure IBM InfoSphere DataStage to run on all processing nodes that function as IBM DB2 servers.
Procedure
To configure InfoSphere DataStage to access IBM DB2 servers, include a node definition for each IBM DB2 server node in the configuration file. Also, complete the following steps.
Running the IBM DB2 configuration script

Use the IBM DB2 configuration script to configure access to IBM DB2 databases.
Procedure
From the command line, run the $APT_ORCHHOME/bin/db2setup.sh script once for each IBM DB2 database that users will access. Pass the database name as an argument. For example, the following command calls db2setup.sh to configure access to the database db2db:
db2setup.sh db2db
Granting user privileges to run IBM DB2 Enterprise stage jobs

You must grant privileges to each user who runs jobs that contain the IBM DB2 Enterprise 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 the following syntax:
db2grant.sh database_name user_name
Accessing a remote IBM DB2 server from IBM DB2 Enterprise stages
You use an IBM DB2 client to connect from an IBM DB2 Enterprise stage to a remote IBM DB2 server.
About this task

For more information, read about remote connections in the IBM InfoSphere DataStage and QualityStage Connectivity Guide for IBM DB2 Databases.
272
Configuring the DB2 system

The DB2 server can be configured in many ways. The DB2 administrator typically follows this procedure to configure IBM DB2 and IBM InfoSphere DataStage to communicate.
Procedure
1. Install IBM DB2 and make sure it is working correctly. Note: Ensure that the touch utility exists in the /usr/bin directory or create a symbolic link to the touch command. Grant the InfoSphere DataStage users SELECT privileges on the DB2 system tables syscat.nodegroupdef, syscat.tablespaces, and syscat.tables. Make the file db2nodes.cfg readable by the InfoSphere DataStage administrative user. InfoSphere DataStage runs many processes for each job. This can require the system administrator to modify DB2 resources, configuration parameters, and manager configuration parameters. See the DB2 information center for more information. The DB2 Enterprise stage requires that users invoking it in load mode have DBADM privilege on the DB2 database written to by the stage. Among the ways 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_name GRANT DBADM ON DATABASE TO USER user_name
2. 3. 4.
5.
Configuring DB2 users

To access IBM InfoSphere DataStage, parallel jobs use an operating system user ID to connect to the IBM DB2 server. Therefore, user IDs that invoke DB2 read operators must have the SELECT privilege on the tables that they access, and user IDs that invoke DB2 write operators must have INSERT privileges on the tables that they access.
About this task

The following procedure configures an InfoSphere DataStage user to access the DB2 database. Either a system administrator or an InfoSphere DataStage user can perform this task.
Procedure
1. Set the DB2INSTANCE environment variable to the user name of the owner of the DB2 instance. DB2INSTANCE determines the location of the db2nodes.cfg file, as follows:
~owner_user_name/sqllib/db2nodes.cfg
The db2nodes.cfg file contains information that is used to translate DB2 node numbers to host names. The information in this file must agree with the host names that are specified in the InfoSphere DataStage parallel configuration file. For example, if you set DB2INSTANCE to Janet, the db2nodes.cfg file is in the following location:
~Janet/sqllib/db2nodes.cfg.
2. Optional: Set the DB2DBDFT environment variable to the name of the DB2 database that you want to connect to. 3. Source the db2profile file and update the LIBPATH environment variable to include the location of the DB2 library that contains your instance of DB2. In
273
the following example, the owner of the DB2 instance is the user Mary, the location of db2profile is ~Mary/sqllib/db2profile, and the location of the DB2 library is ~Mary/sqllib/lib. For a Korn or Bourne shell, include these statements in the .profile or .kshrc files:
. ~Mary/sqllib/db2profile export LIBPATH=~Mary/sqllib/lib:${LIBPATH:-/usr/lib}
For a C shell, include these lines in the .cshrc file:

source ~Mary/sqllib/db2profile if (! $?LIBPATH) setenv LIBPATH /usr/lib setenv LIBPATH ~Mary/sqllib/lib:$LIBPATH
Configuring access to Oracle databases

Configuring access to Oracle databases includes granting the appropriate access level to users.
Granting access to the Oracle parallel server

To access the Oracle parallel server (OPS), users must have SELECT access to the sys.gv_$instance and sys.v_$cache tables.
Procedure
1. 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_OPS environment variable to disable OPS checking on the Oracle Enterprise stage.
Granting user privileges to run Oracle Enterprise stage jobs

You must grant privileges to each user who runs jobs that contain the Oracle Enterprise stage.
Procedure
1. 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 before you attempt to access it. 5. Obtain the SELECT privilege on the following tables: DBA_EXTENTS DBA_DATA_FILES DBA_TAB_PARTITONS DBA_TAB_SUBPARTITIONS DBA_OBJECTS ALL_PART_INDEXES ALL_PART_TABLES ALL_INDEXES SYS.GV_$INSTANCE (required only if you use the Oracle parallel server)
274
6. Verify that the APT_ORCHHOME/bin directory is before the ORACLE_HOME/bin directory in the PATH statement. 7. Create a role that has SELECT privileges on the tables. The following code creates a role named DSXE, which grants SELECT privileges on the required tables:
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 databases

Configuring access to Teradata databases includes granting the appropriate access level to users.
Installing the Teradata tools and utilities

You must install Teradata Tools and Utilities on all nodes that run parallel jobs. See the installation instructions supplied by Teradata for complete information.
Procedure
1. Ensure that the Teradata Parallel Transporter is installed and that the following environment variables are set in the /etc/profile file:
Operating system AIX Environment variables TWB_ROOT=/usr/tbuild/08.01.00.02 PATH=$TWB_ROOT/bin:$PATH LIBPATH=$TWB_ROOT/lib:$LIBPATH NLSPATH=$TWB_ROOT/msg/%N export TWB_ROOT PATH LIBPATH NLSPATH
2. To run Teradata Connector jobs, add these same environment variables to the dsenv file.
Creating a Teradata user

You must create a Teradata user before you can connect from the parallel server to the Teradata database.
About this task

The Teradata database owner is the user that is referred to by a DB options property in the Teradata stage. The user must be able to create tables and insert and delete data. If you want to use a pre-existing Teradata user, install a database server and configure it to use a new database. Install the new database server with 100 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.
275
CREATE USER user_name FROM database_name AS PASSWORD = user_password PERM = 100000000 SPOOL = 10000000
2. After the account is set up, run the following command:

GRANT SELECT on dbc TO user_name;
Configuring access to Informix XPS databases

You must set the INFORMIXSERVER, INFORMIXDIR, AND INFORMIXSQLHOSTS environment variables. On AIX, you must also set the LIBPATH.
About this task

You must have the correct privileges and settings to use the Informix Enterprise Stage. You must have a valid account and appropriate privileges on the databases to which you connect. You must have read and write privileges on any table to which you connect, and you must have Resource privileges for using the Partition Table property on an output link or for using create and replace modes on an input link.
Procedure
1. 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 and is set to the coserver name of coserver 1. The coserver must be accessible from the node on which you invoke the job. 3. Make sure that the INFORMIXDIR environment variable is set to the installation directory of the Informix server. 4. Make sure that the INFORMIXSQLHOSTS environment variable is set to the path to the sqlhosts file, for example, /disk6/informix/informix_runtime/etc/ sqlhosts. 5. 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/j re/bin:$INFORMIXDIR/lib:$INFORMIXDIR/lib/cli:$INFORMIXDIR/lib/esql
276
Chapter 11. Configuring product modules in the suite

Depending on which products you installed or the tasks that you want to complete, you must complete some configuration tasks, such as configuring access to ODBC data sources for IBM InfoSphere DataStage and IBM InfoSphere QualityStage, setting up application servers to run reports, and configuring additional product modules.
Configuring IBM InfoSphere DataStage and IBM InfoSphere QualityStage

Before you use IBM InfoSphere DataStage and IBM InfoSphere QualityStage, you must perform several configuration tasks.
Procedure
Complete the following tasks to configure and administer IBM InfoSphere DataStage and IBM InfoSphere QualityStage. 1. Configure security. For more information, see the topics on managing security in the IBM InfoSphere Information Server Administration Guide. 2. AIX : Ensure that InfoSphere DataStage users have the correct localization settings. If you installed globalization support (NLS), ensure that IBM InfoSphere DataStage users have the correct settings specified for localization. 3. Configure the ODBC drivers to access ODBC data sources. The drivers are installed with the client tier or the engine tier. 4. Optional: Configure the parallel processing environment by adding computers to share engine processing, setting environment variables for the parallel engine, and configuring the parallel engine. 5. Optional: Migrate jobs that you created in an earlier version of InfoSphere Information Server to the current version. For more information, see the IBM InfoSphere Information Server Guide to Migrating to IBM InfoSphere Information Server, Version 8.5. 6. Optional: If you intend to develop InfoSphere QualityStage matches, ensure that a new or existing supported database is available to receive test pass results for the Match Designer. The IBM InfoSphere QualityStage Match Designer requires an ODBC data source name (DSN) to connect to the database where the Match Designer stores match pass results. 7. Optional: Set up the application server to run SQA or investigation reports. The investigation reports and Standardization Quality Assessment (SQA) reports can read data from a sequential file or a database table. You must set up the application server to find the applicable data source. 8. Optional: Create and configure the Operations Database. If you plan to use the Operations Console to monitor your InfoSphere DataStage and QualityStage engines, projects, and jobs, you must configure Operations Database to provide information to the console. 9. After you install and configure InfoSphere DataStage and InfoSphere QualityStage, test the installation by logging in to the Administrator and Designer clients.
277
Ensuring that InfoSphere DataStage users have the correct localization settings (AIX )
If you installed globalization support (NLS), ensure that IBM InfoSphere 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-wide default. If the user who performed the installation used this default and all InfoSphere DataStage users are expected to inherit the same default, then you 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 user might 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 locale that was not the default, or if a user set a private locale (for example, in their $HOME/.profile directory). To ensure that InfoSphere DataStage users have the correct locale and environment settings, you can edit the environment variables in the dsenv file. The environment variables in the dsenv file affect the entire InfoSphere DataStage environment. To define the environment variables on a per-project or per-job basis, use the IBM InfoSphere DataStage and QualityStage Administrator client or the IBM InfoSphere DataStage and QualityStage Designer client. Perform this task as soon as possible after installation, before any jobs are stored or compiled.
Procedure
1. 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. To determine the current locale that is set for the server operating system, use the 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 were specified during installation. For example, the following settings specify that the locale is ja_JP and the encoding is UTF-8:
LANG="ja_JP.utf8";export LANG LC_ALL="ja_JP.utf8";export LC_ALL LC_CTYPE="ja_JP.utf8";export LC_CTYPE LC_COLLATE="ja_JP.utf8";export LC_COLLATE LC_MONETARY="ja_JP.utf8";export LC_MONETARY
278
LC_NUMERIC="ja_JP.utf8";export LC_NUMERIC LC_TIME="ja_JP.utf8";export LC_TIME LC_MESSAGES="ja_JP.utf8"; export LC_MESSAGES
5. Remove the comment marker (#) that is at the beginning of each line. Save the file. 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 ODBC access (AIX )

If you installed ODBC drivers, you must configure the drivers to access ODBC data sources. The DataDirect Technologies Connect ODBC drivers are installed in install_home/Server/branded_odbc. Documentation for configuring the ODBC drivers is provided within this directory tree. Edit the dsenv, odbc.ini, and uvodbc.config files to set up access to ODBC data sources. Non-wire protocol drivers require different setup information from wire drivers. Non-wire drivers require information about the location of the database client software. 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 the odbcread.me file in the branded_odbc directory and an HTML file in the branded_odbc/odbchelp directory.
Configuring the dsenv file

For some ODBC connections, plug-ins, and connectors, and for interactions with external applications such as IBM WebSphere MQ, you must add environment variables to enable interactive use of ODBC drivers to make a connection to an ODBC data source. This lets IBM InfoSphere DataStage inherit the correct environment for ODBC connections.
Before you begin

You must be logged in as an InfoSphere DataStage administrator with the operating system credentials on the server for the InfoSphere DataStage administrator. Back up the dsenv file before you edit it.
About this task

The dsenv file contains a series of shell arguments that are used when the engine starts. Interactive users, other programs, and scripts can use the dsenv file. For a connection that uses a wire protocol driver, you do not have to modify the dsenv file.
279
Procedure
1. Edit the dsenv file. The file is located in $DSHOME/DSEngine, where $DSHOME identifies the 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 software v Database home location v Database library directory
Table 80. Names of the library path environment variable, by operating system Operating system AIX Library path environment variable LIBPATH
The following examples show typical entries for commonly used databases. The entries vary slightly depending on your operating system. See the data source documentation for more information. Sybase 11
LANG= export LANG SYBASE=/export/home/sybase/sybase export SYBASE LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$SYBASE/lib:/usr/lib:/lib export LD_LIBRARY_PATH
Informix XPS 9.3

INFORMIXDIR=/space/informix export INFORMIXDIR INFORMIXSERVER=solnew2.1 export INFORMIXSERVER ONCONFIG=onconfig.solnew2 export ONCONFIG LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$INFORMIXDIR/lib:$INFORMIXDIR/lib/ esql:$INFORMIXDIR/lib/cli export LD_LIBRARY_PATH LANG=C export LANG
DB2 Version 9.5

DB2DIR=/opt/IBM/db2/V9.5 export DB2DIR DB2INSTANCE=db2inst1 export DB2INSTANCE INSTHOME=/export/home/db2inst1 export INSTHOME PATH=$PATH:$INSTHOME/sqllib/bin:$INSTHOME/sqllib/adm: $INSTHOME/sqllib/misc export PATH LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$INSTHOME/sqllib/lib export LD_LIBRARY_PATH THREADS_FLAG=native export THREADS_FLAG
3. Save your changes. 4. Stop and restart the IBM InfoSphere Information Server engine.
Configuring the odbc.ini file

The odbc.ini file provides information about connecting to all the databases and database client applications that you use. You must configure this file so that IBM InfoSphere Information Server can access ODBC data sources.
280
About this task

The /opt/IBM/InformationServer/Server/branded_odbc/IBM_Tools directory contains example odbc.ini files for each supported platform. Use the contents of these files to create the odbc.ini file for the $DSHOME directory.
Procedure
1. Navigate to the <installation-directory>/Server/DSEngine directory, where <installation-directory> is the directory where you installed InfoSphere Information Server. 2. Run the following command to create a soft link for the sample .odbc.ini file to point to the odbc.ini file.
ln -s odbc.ini.odbc.ini
3. Modify the .odbc.ini to match your database environment.
Specifying data source names in the uvodbc.config file

The uvodbc.config file must specify the ODBC data source name (DSN) for each database.
About this task

A copy of the uvodbc.config file exists in the $DSHOME directory and each project directory. By default, IBM InfoSphere DataStage searches the current project directory for a uvodbc.config file and, if it finds one, uses this file instead of $DSHOME. This file arrangement allows you to configure data sources that are known to some projects but 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 is specified in the .odbc.ini file. The space on each side of the equal sign is required. 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 cause processing errors. Add comments only to the comment block that is at the top of the uvodbc.config file. The following example shows a typical uvodbc.config file:
[ODBC DATA SOURCES] <localuv> DBMSTYPE = UNIVERSE network = TCP/IP service = uvserver host = 127.0.0.1 <Sybase1> DBMSTYPE = ODBC <Sybase2> DBMSTYPE = ODBC <Oracle8> DBMSTYPE = ODBC
281
<Informix> DBMSTYPE = ODBC <DB2> DBMSTYPE = ODBC
2. If you alter uvodbc.config after creating projects, copy the edited file to the project directories.
Creating and binding a DB2 package to a data source name

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/bin directory. 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

You can use ODBC drivers from other vendors to connect to data sources. You might be required to connect to a database not supported by the DataDirect driver pack, for example, Red Brick. You can use only one ODBC Manager at a time. As a result, you cannot use drivers from other vendors at the same time that you use the IBM InfoSphere DataStage drivers, and you must perform some reconfiguration to switch between the two types.
Procedure
1. Install the ODBC manager and drivers. Use the documentation that the driver vendor 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 database client application. You must specify the Data Source Name (DSN), driver name, 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. Edit the dsenv file and 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 ensure that the InfoSphere DataStage ODBC driver library precedes any other ODBC driver libraries.
Testing ODBC driver connectivity

After you configure ODBC connectivity that you defined for IBM InfoSphere DataStage, test the configuration to verify your connection to the data source.
282
Procedure
1. Change directories to the $DSHOME directory and set up the environment by running the following command:
. ./dsenv
2. Enter the following command to start the IBM InfoSphere Information Server engine shell:
./bin/dssh
3. Enter the following command to log in to the project:

LOGTO project_name
where project_name is case-sensitive. 4. Enter the following command to obtain a list of available data source names:
DS_CONNECT
5. Enter the following 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 IBM InfoSphere QualityStage Match Designer

The IBM InfoSphere QualityStage Match Designer requires an ODBC data source name (DSN) to connect to the database where the Match Designer stores match pass results.
Before you begin

Designate a new or existing database to be dedicated to the storage of Match Designer output. See Creating the IBM InfoSphere QualityStage Match Designer database on page 154.
Procedure
1. 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 on each computer. You might want to select from the set of IBM Wire Protocol ODBC drivers installed as part of the IBM InfoSphere Information Server environment. These drivers are convenient because their functionality does not depend on the presence of any additional database-specific client software. 2. On each client tier computer, open the Match Designer and run a Test Environment Update for your match specification. When you run this function, the connection to the Match Designer database is established and your encrypted credentials are retained.
Setting up application servers to run investigation, SQA, or Match Statistics reports

The investigation, Standardization Quality Assessment (SQA), and Match Statistics reports can read data from a sequential file or a database table. You must set up the application server to find the applicable data source.
283
Procedure
1. If the stage writes the report data to a sequential file, perform the action that corresponds to the topology of your installation.
Topology IBM InfoSphere Information Server engine and the services tier are on the same computer. InfoSphere Information Server engine and the services tier are on different computers. Action No additional steps are necessary.
The sequential file exists only on the engine. Because the reports run on the application server, perform one of the following steps: v Create a network shared directory that both the engine and application server can access. v Copy the sequential file from the engine tier computer to the local file system of the services tier. Ensure that the file paths are identical on both the engine tier computer and the services tier computer.
2. If the stage writes the report data to a database table, perform the action that corresponds to the topology and operating system of your installation.
Topology and operating system v All operating systems v InfoSphere Information Server engine and the services tier are on different computers Action Because the necessary ODBC drivers are not installed on the application server, perform the following steps: 1. Set up the JDBC data source on the application server. 2. Ensure that the JNDI name is the same as the ODBC DSN on the engine. v AIX v InfoSphere Information Server engine and the services tier are on the same computer Because the ODBC DSN is not visible to the engine as the system DSN, perform the following steps: 1. Set up the Java Database Connectivity (JDBC) data source on the application server. 2. Ensure that the Java Naming and Directory Interface (JNDI) name is the same as the ODBC DSN on the engine.
Configuring IBM InfoSphere Information Analyzer

Before you use IBM InfoSphere Information Analyzer, you must perform several configuration tasks.
Before you begin

You must have Information Analyzer Data Administrator authority.
About this task

Complete the following high-level tasks to initially configure and administer this product module.
284
For detailed information about analysis configuration, see the IBM InfoSphere Information Analyzer User's Guide.
Procedure
1. On the computer that hosts the engine, define the Data Source Name (DSN) to the analysis database and source databases. To avoid additional changes to the DSN information, validate the DSNs before you complete the next step. 2. Verify the credentials that are used to connect to the IBM InfoSphere Information Server engine. You can validate the settings in the IBM InfoSphere Information Server console, in the Home > Configuration > Analysis Settings > Analysis Engine tab. 3. Verify the credentials that are used to connect to the analysis database. You can validate the settings in the IBM InfoSphere Information Server console, in the Home > Configuration > Analysis Settings > Analysis Database tab. For the 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 in the 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 inherit these global settings. 5. Verify the credentials that are used to connect to the source databases by using 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 in steps 2 through 4. 10. In the Project Properties tab, associate the imported metadata with the project. 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 Glossary

You must configure some settings before you start using InfoSphere Business Glossary.
Before you begin

The IBM InfoSphere Information Server suite administrator must assign security roles to glossary users.
285
About this task

You can configure InfoSphere Business Glossary to suit the needs of your organization. Many configuration tasks are optional. Most tasks are completed by the InfoSphere Business Glossary Administrator.
Procedure
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 the following: v The content of the display page when users log in to InfoSphere Business Glossary v An e-mail address to which users can send feedback v Whether a property name is displayed if its value is undefined v Restrict which terms are displayed based on their status, such as "accepted" or "deprecated " v The order in which parts of user names are listed in relevant displays v Whether a history of changes to terms is displayed v Whether integration with Cognos 8 Go! is enabled 3. Configure viewing permissions. This allows you to restrict the access of selected glossary users to some glossary content. 4. Configure support for right-to-left reading languages (bidirectional language support).
Stopping and starting the IBM InfoSphere Information Server server engine
Restart the InfoSphere Information Server engine after you complete certain tasks such as editing the dsenv file or modifying the uvconfig file.
Procedure
AIX 1. Log in to the engine tier computer as the IBM InfoSphere DataStage administrator (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
286
Part 4. Troubleshooting installations

Resolve installation problems with this installation troubleshooting information. You can find more troubleshooting information in the information centers and customer support technotes for various product modules and components.
287
288
Chapter 12. Log files

To troubleshoot issues with IBM InfoSphere Information Server, you can consult log files and temporary files.
Installation log files

Log files are created during the installation and uninstallation process. You can use the log files to troubleshoot installation errors. During the installation and uninstallation process, the log files are saved to the following directory:
Table 81. Default directory where log files are saved during the installation and uninstallation process Operating system AIX Directory /var/tmp/ibm_is_logs
Note: If you redirected the installation program's temporary files to a different directory in Preparing to run the installation program on page 177, the installation log files are in that location, instead of in the default temporary directory that is specified here. After a successful installation, a .zip file of the log files that are created during the installation process is saved to the IBM InfoSphere Information Server installation directory. This .zip file is named isdump-os-timestamp.zip. After a failed installation, the ISInstall-date-timestamp.log log file is retained in the temporary directory. After a successful uninstallation, the ISInstall-date-timestamp.log log file is retained in the logs directory under the installation directory. After a failed uninstallation, the ISinstall-date-timestamp.log log file is retained in the ibm-is-logs directory within the temporary directory. Note: Do not delete the installation log files or the log file directory during the installation process. When installation is complete, save the log files for troubleshooting and verification purposes.
Temporary files generated by installation program

Temporary files are created during the installation process. The temporary files are not used after the installation is completed. During the installation process, temporary files are saved to the following installation directories:
Table 82. Directories where temporary files are saved during the installation process Operating system AIX Directory /var/tmp
289
If you redirected the installation program's temporary files to a different directory in Preparing to run the installation program, the temporary files are in that location, instead of in the default temporary directory that is specified here. Note: The temporary files that are created during installation are not used after installation is completed. You can delete the installation temporary files after installation is completed.
IBM WebSphere Application Server system log files

The WebSphere Application Server log files contain information that you can use to monitor WebSphere Application Server startup and diagnose errors. The following log files are useful for diagnosing problems with IBM InfoSphere Information Server: SystemOut.log WebSphere Application Server messages to STDOUT are redirected to this file. SystemErr.log WebSphere Application Server messages to STDERR are redirected to this file. These files are located in the following directories on each node in your WebSphere Application Server installation:
Operating system AIX Directory path/profiles/profile/logs/server1
path The WebSphere Application Server installation path. By default, path is one of the following paths:
Operating system AIX Directory opt/IBM/WebSphere/AppServer
profile The profile name where IBM InfoSphere Information Server is installed. For a stand-alone installation, the default value is InfoSphere. For a clustered installation, the default value for a custom profile is Customxx, where xx is the number of the profile. server1 The name of the application server. For a stand-alone installation, the default value is server1. For cluster installations, there might be multiple application server directories under the custom profile. The typical value is serverx, where x is the number of the application server instance. For a Deployment Manager profile, the default value is dmgr. For a node agent under the custom profile, the default value is nodeagent. For more information about WebSphere Application Server log files, see the WebSphere Application Server documentation: v For Version 7.0, go to the WebSphere Application Server information center and read Diagnosing problems with message logs
290
v For Version 8.0, go to the WebSphere Application Server information center and read Diagnosing problems with message logs
Chapter 12. Log files
291
292
Chapter 13. General installation problems

These problems and resolutions are related to general issues that might occur across the product suite.
"User credentials are not valid" error appears unexpectedly during installation
If you receive a "user credentials are not valid" error when you create a new operating system user account from the installation program, specify the correct password or remove the user account.
Symptoms
When you specify a new operating system user account from the IBM InfoSphere Information Server installation program, you receive a "user credentials are not valid" error and you cannot continue the installation. See Setting up administrator and owner accounts on page 100 for more information about operating system user accounts.
Causes
When you specify a new operating system user account from the installation program, the program checks whether the user account already exists. If the account exists, the program checks whether the password is correct. If the account does not exist, the program immediately creates the user account on the computer. If you exit the program before you complete the installation, the user account remains on the computer. If you subsequently restart the installation and specify the same user name but a different password, you receive a "user credentials are not valid" error.
Environment
All supported operating systems.

Use operating system utilities to determine whether the user account exists on the computer. If necessary, change the password. Then continue the installation.
IWAV0003E warning in installation log file

IWAV0003E warnings in the installation log file can be ignored.
Symptoms
A warning similar to the following text is written to the installation log file during the IBM WebSphere Application Server enterprise archive (EAR) deployment phase:
293
[exec] +++ Warning +++: Mon Sep 18 19:36:18 BST 2010 IWAV0003E Could not reflect methods for com.ascential.xmeta.shared. ILocalTransactionalBusiness because one of the methods references a 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 classpath for the EAR installation process. After the EAR is installed, the classes are resolved correctly.
Warnings occur during installation of DB2

While installing IBM InfoSphere Information Server, you might see a message indicating that warnings occurred during the installation of IBM DB2 Database for Linux, UNIX, and Windows, or "Open File - Security Warning" messages might be displayed.
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.InstallDB2Action WRepositoryInstaller65507: 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 ignore warnings such as SQL1362W or SQL20189W, which warn that the updates do not take effect until the next database startup. These warnings are not important because the installation program stops and restarts DB2 during the installation process. For more information about specific warning messages in the DB2 log file, refer to the DB2 documentation: v DB2 9.5: publib.boulder.ibm.com/infocenter/db2luw/v9r5/ v DB2 9.7: publib.boulder.ibm.com/infocenter/db2luw/v9r7/
294
User creation errors appear in log files (AIX )

If several errors about user creation are included in the log files, check that the users 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 type SEVERE: com.ibm.is.install.core.util.User CDIIN3185E: Changing ownership failed WARNING: 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 failed with return code: 9
Causes
The users do not yet exist. On a system that runs the Lightweight Directory Access Protocol (LDAP) or the Network Information Service (NIS), you must create all users in the user registry before you run the IBM InfoSphere Information Server installation program. The installation program attempts to create the metadata repository database owner and IBM InfoSphere Information Analyzer user if the accounts do not exist. The installation program cannot create users on an LDAP or NIS-enabled system. Any user that you create before you run the installation program must have a valid home directory defined.

Create all users and then run the installation program again. See Setting up administrator and owner accounts on page 100.
Installation process hangs when a web browser session is closed

If an exception occurs after a web browser or browser tab has been closed, or if the browser session has timed out, the installation process will be stuck waiting for user 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 is closed during the installation session, if the installation runs into exception, the installation process gets stuck waiting for a user response. Note: To avoid this problem, keep the browser or browser tab open throughout the installation session.
Environment
Graphical mode installation
295

1. Uninstall your current IBM InfoSphere Information Server installation by running the following commands:
cd /opt/IBM/InformationServer/_uninstall ./uninstall -verbose
2. Complete the manual cleanup:

Operating system AIX Procedure Completing software removal (AIX )
3. Start a new InfoSphere Information Server installation by running the following commands:
cd <image>/is-suite ./setup -rsp response.txt -force -verbose
Fix pack version errors during IBM InfoSphere Information Server installation
When you pre-install IBM WebSphere Application Server separately before you install InfoSphere Information Server, the installation program halts with an error if fix packs later than 7.0.0.11 are installed. The problem also occurs if you have installed Fix Pack 7.0.0.11 and iFix IFPM20596. You can ignore these errors and continue the installation.
Symptoms
The Prerequisites Check page displays messages like the following lines. The messages also appear in the installation log file: WARNING: com.ibm.is.install.check.WebSphereVersionChecker No iFixes found in the WebSphere Application Server installation. INFO: FAILED: CDIPR2118I: Ensure that the WebSphere Application Server version has the fix packs 6.1.0.29:IFPK96868, 6.1.0.29:MultiOS-IFPK99266, 6.1.0.29:IFPK99560, 7.0.0.11:IFPK96868, 7.0.0.11:IFPM20596, 7.0.0.11:IFPM21207. Detected fix packs for version 7.0.0.11. Resolution: Follow WebSphere Application Server Fix Pack installation instructions to install the Java SDK and Fix Packs to the required level.
Causes
The Java software development kit (SDK) that is installed with these fix packs is a higher version than the installation program expects. However, InfoSphere Information Server supports this version.
Environment
All environments

Restart the installation program with the -force option on the command line. This option enables a check box within the Prerequisites Check page that allows you to continue even if the prerequisites check returns warnings or errors.
296
Use the -force option with caution. Be sure to resolve any other warnings or errors that appear during the prerequisites check. Continuing an installation with unresolved warnings or errors might result in a non-operational InfoSphere Information Server instance.
297
298
Chapter 14. Authentication problems

These problems and resolutions are related to authentication.
Directory and user permissions

If installation fails, confirm that the users who install IBM InfoSphere Information Server have read and write permissions for the InfoSphere Information Server installation directories. The following table shows the default InfoSphere Information Server installation directories that require read and write permissions by the specified users.
Table 83. Required directory permissions Installation components InfoSphere Information Server Directories Installation parent directories: AIX v /opt v /opt/IBM Permissions Read or read and write Users AIX Root user
InfoSphere Information Server Engine tier and IBM InfoSphere DataStage
Installation directory: AIX /opt/IBM/ InformationServer
Read and write
AIX
Root user
Installation parent directories: AIX v /opt v /opt/IBM
Read or read and write
InfoSphere DataStage administrator (default user name is dsadm)
Engine tier and InfoSphere DataStage InfoSphere Information Server
Installation directory: AIX /opt/IBM/ InformationServer
Read and write
InfoSphere DataStage administrator (default user name is dsadm)
Temporary directory: AIX /tmp
Read and write
AIX v Root user v Database instance owner (default user name is db2inst1)
299
Table 83. Required directory permissions (continued) Installation components Metadata repository Directories Database server directories for IBM DB2: AIX v /opt v /opt/IBM v /opt/IBM/db2/ V9.5/ (DB2 Version 9.5) v /opt/IBM/db2/ V9.7/ (DB2 Version 9.7) If you are using another database system, refer to the documentation for the database system for directory permissions information. Metadata repository Database storage directories: AIX /opt/IBM/ InformationServer/ Repository Read and write AIX Database instance owner (default user name is db2inst1) Permissions Read or read and write Users AIX Database instance owner (default user name is db2inst1)
IBM WebSphere Application Server
Installation directory: AIX /usr/IBM/ WebSphere/ AppServer
Read and write
AIX
Root user
Confirming user privileges

If the installation fails, confirm that the users who install IBM InfoSphere Information Server have the necessary privileges.
Symptoms
The installation fails to complete successfully.
Environment
All supported operating systems.

Log in to the computer with the proper privileges.
Operating system AIX Procedure Log in as the root user.
300
Chapter 15. Application server problems

These problems and resolutions are related to the services tier and the application server.
Resolving IBM WebSphere Application Server installation problems

Use this troubleshooting information when you install IBM WebSphere Application Server with IBM InfoSphere Information Server.
Symptoms
When you install WebSphere Application Server with IBM InfoSphere Information Server, the WebSphere Application Server installation fails.
Environment
All supported environments.
Diagnosing the problem

If the WebSphere Application Server installation fails, review the following log files: 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 7.0: WebSphere Application Server Network Deployment 7.0: Troubleshooting installation v InfoSphere Information Server installation log file:
Operating system AIX Directory /opt/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 Application Server installation process: AIX The /etc/filesystems file contains a duplicate entry. If the /etc/filesystems file contains a duplicate entry, the WebSphere Application Server installation reports 0 MB of available disk space. Edit the /etc/filesystems file, and comment out the duplicate entry.
301
Installation fails when the IBM WebSphere Application Server port is changed after installation
After you install IBM InfoSphere Information Server, if you change the WebSphere Application Server HTTP port (WC_defaulthost) by using the IBM WebSphere Application Server administrative console, future installations, product additions, and updates fail.
Symptoms
A Connection refused error message is displayed on the user interface or in the log file.
Causes
The original installation settings are stored in several configuration files are used for subsequent installation activities. If the WebSphere Application Server port number changes after installation, the installation settings in these files are incorrect.

Follow the procedure in Changing the WebSphere Application Server HTTP port to change the HTTP port in the WebSphere Application Server administrative console and in the configuration files.
Resolving connection problems

An installation might fail because the Domain Name System (DNS) server is unable to resolve system names or because the application server is not running.
Symptoms
IBM InfoSphere Information Server installation fails when the Domain Name System (DNS) is unable to resolve system names. The installation program returns an error message that is similar to the following message:
CDIIN2107E: Unable to validate the IBM InfoSphere Information Server user name name and password for host hostname at port port_number. The returned message is: java.net.UnknownHostException: hostname. Confirm that 1) WebSphere Application Server is running; 2) you entered the correct user name and password; 3) the port number is correct.
Causes
The communication between the installation computer and the application server on the services tier is not established. The following issues might cause this problem: 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.
302

When the services tier is installed on hostname.domain, use the following ping commands to test the connection to the short host name and to the long host name:
ping hostname ping hostname.domain

1. 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 was installed. 5. Ensure that localhost and the computer host name are not both mapped to the loopback IP address. The IPv4 version of this address is 127.0.0.1 and the IPv6 version is ::1/128. Map only localhost to IP address 127.0.0.1. The following example shows an etc/hosts file where these entries are specified correctly:
127.0.0.1 | ::1/128 localhost.localdomain localhost xx.xx.xx.xx | xx:xx::xx:xx machinelonghostname machineshorthostname
xx.xx.xx.xx | 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 name changes or expires
If the user name or password that you created for WebSphere Application Server or for the metadata repository changes or expires, the application server does not start.
Symptom
The application server does not start.
Cause
The WebSphere Application Server user name or password changed or expired, or the metadata repository user name or password changed or expired. Starting and stopping WebSphere Application Server requires user authentication. These start and stop commands fail when user authentication is unsuccessful because the user names or passwords changed or expired.

The IBM InfoSphere Information Server installation directory is shown as install_home in the following commands. Note: The AppServerAdmin commands do not validate user names or passwords.
303
AIX
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 the following 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 -password new_password
c. Restart all WebSphere Application Server processes. See the IBM InfoSphere Information Server Administration Guide. For details on adding a new WebSphere Application Server user when using the internal registry, see Adding an IBM WebSphere Application Server administrator user to an internal user registry.
Adding an IBM WebSphere Application Server administrator user to an internal user registry
If you do not know the WebSphere Application Server administrator user and password, you can create a user in the internal user registry.
Symptom
You are using the internal user registry and you do not know the WebSphere Application Server administrator user and password.
Cause
The password changed, or the user was deleted.

The IBM InfoSphere Information Server installation directory is shown as install_home in the following commands. AIX 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 user name or password within the WebSphere Application Server configuration:
/opt/IBM/InformationServer/ASBServer/bin/AppServerAdmin.sh -was -user name -password password
304
Repairing the WebSphere Application Server registry after switching to LDAP

If you have switched from an internal registry to a Lightweight Directory Access Protocol (LDAP) user registry without using the documented procedure, "Switching to an LDAP user registry," you might be unable to stop IBM WebSphere Application Server processes.
Symptoms
You can not stop WebSphere Application Server when using either the MetadataServer.sh stop command or the stopServer.sh command.
Environment
Optional. Describe any environmental details that are not already in the title or short 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 console does not prompt you for a password. 5. In Security > Global Security, click Configure and enter the following information: 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. Click Apply and then OK. This returns you to the Global Security page. Select the check boxes: Enable administrative security and Enable application security Clear the Java 2 security check box. Click Apply. A message appears on the top of the form. Click the Save link inside the message.
6. 7. 8. 9.
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 is fixed.
305
b. Start WebSphere Application Server. c. Stop WebSphere Application Server. It should be able to stop without errors.
Services tier performance

If the services tier is slow, ensure that you have not turned on IBM WebSphere Application Server tracing.
Symptoms
The services tier is running slowly. The default setting for IBM WebSphere Application Server tracing is off.

To avoid the problem, ensure that any changes made to IBM WebSphere Application Server are restored to the default settings before installing and using IBM InfoSphere Information Server. To resolve the problem, ensure that you have not turned on the IBM WebSphere Application Server tracing.
306
Chapter 16. IBM InfoSphere Information Server reporting problems

These problems and resolutions are related to reporting.
Cannot view report result from InfoSphere Information Server console or InfoSphere Information Server Web console
In a cluster environment, if a Page Not Found error message is displayed while you are trying to view a report result, a security process might be running. You can edit the httpd.conf configuration file to allow encoded slash characters, and then restart the Web server.
Symptoms
After you run a process in a cluster environment, a Page Not Found error message 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 is encoded as special character that the httpd.conf configuration file reads and then rejects by default.
Environment
This advice applies to cluster environments that run on IBM HTTP Server or Apache Web Server.

1. 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 administrative console to restart it. Otherwise, log into the computer where the web server is installed, and restart the web server.
Enabling and disabling trace logging of the reporting engine

When you encounter a problem or an error that requires attention by IBM Software Support, you can set up trace logging to report detailed internal processes. You can enable trace logging in the reporting engine to generate logs that help IBM Software Support diagnose errors.
Symptoms
Not applicable.

1. Open a command prompt or a terminal window on the computer.
307
2. Enter the following command to enable logging in the reporting engine:

Operating system AIX Command installdir/ASBServer/bin/ ReportingAdmin.sh -user username -password password -el
If you specify the -authfile parameter, the -user and -password parameters are optional. Use the -authfile parameter to specify the location of your credentials file. 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 each server, the reporting workspace is located in the temp folder that is defined by the operating system. The path has the following format: \tempfolder\informationServer\servername\engine\JREPORT v If clustering is not enabled, the log files are located in the following directory:
Operating system AIX Directory 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 to disable logging:
Operating system AIX Command installdir/ASBServer/bin/ ReportingAdmin.sh -user username -password password -dl
308
Chapter 17. Client and console problems

These problems and resolutions are related to client errors and login problems.
Java Virtual Machine fails to load

During startup, client applications might fail to load the Java Virtual Machine (JVM) if the operating system is unable to allocate a sufficient amount of heap memory.
Symptoms
The client application fails with an error message that is similar to the following message:
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. This error typically occurs when too many client processes are running concurrently.

Decrease the value that is specified for MaximumHeapSize in the application-specific sections of the following file: \ASBNode\conf\proxy.xml. This file is located in the IBM InfoSphere Information Server installation directory. Continue to decrease this value until clients start normally. If multiple client applications are running, you might need to decrease this value for all clients. Comments in the proxy.xml file identify the configuration section for each client application. 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 failure

If the rich client login fails because the services tier cannot be reached, you can troubleshoot 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 connection failure might be identified with an error message about network connection, such
309
as "Could not connect to server" or "port out of range." A connection failure might also be revealed in a stack trace that is similar to the following example:
Exception type: javax/security/auth/login/LoginException Exception 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 more Caused by: java.net.ConnectException: Connection refused: connect at 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 the cause of the failure:
Cause The client computer host file has an invalid host name or IP address entry. Solution Update the client computer hosts file so that the server host name can be resolved from client.
310
Cause The server listening port might be blocked by a firewall. The application server is not running.
Solution Ensure that the application server TCP/IP ports are not blocked by the firewall. Ensure that the application server is running.
In a cluster environment, you did not specify If IBM WebSphere Application Server the host name and port of the front-end clustering is implemented within your HTTP dispatcher. installation, direct the client to the host name and port of the front-end HTTP dispatcher. (The default port is 80.) The client login will fail if you specify the Deployment Manager host name and port or if you specify the host name and port of a single cluster member. You changed a WebSphere Application Server port or modified the host file on the system, but you did not restart WebSphere processes 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 Application Server administrative console
Use this troubleshooting information when you are running WebSphere Application Server with IBM InfoSphere Information Server and you cannot log in to the WebSphere Application Server administrative console.
Symptoms
You cannot log in to the WebSphere Application Server administrative console of an WebSphere Application Server installation that is running InfoSphere Information Server.
Causes
There are multiple reasons why the login fails.
Environment
This advice applies to all environments that are supported by InfoSphere Information Server.

Ensure that you are using the default IBM WebSphere Application Server administrator user name and password. If you are not sure of the WebSphere Application Server administrator user name, you can view the WebSphere Application Server security.xml file. Attention: Do not modify this file.
The security.xml file is in the following directory:

Operating system AIX Directory /opt/IBM/WebSphere/AppServer/profiles/ profile_name/config/cells/cell
311
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 Application Server cell. The user name is specified by the serverId attribute in the userRegistries element of the active user registry. Ensure that you are looking at the serverId of the active user registry. To find the active user registry in the security.xml file, look for the activeUserRegistry string in the file. The file contains an entry that is similar to activeUserRegistry=UserRegistry, where the UserRegistry value depends on your configuration. Search the remainder of the security.xml file for this value, which determines 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 server is running and that you can connect to it. If you are using the InfoSphere Information Server internal registry, ensure that the database server that is used by InfoSphere 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 to change the password:
Operating system AIX Command 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 a local operating system user registry or an LDAP user registry), use operating system or LDAP utilities to change the password. 2. Enter the following the AppServerAdmin command to update the WebSphere Application Server and InfoSphere Information Server configurations:
Operating system AIX Command install_home/ASBServer/bin/ AppServerAdmin.sh -was -user username -password password
Connection problems after IBM WebSphere Application Server cluster members are removed
You might experience connection problems with the WebSphere Application Server administrative console or IBM InfoSphere DataStage clients if you remove all members of a WebSphere Application Server cluster.
Symptoms
You cannot access the WebSphere Application Server administrative console, or log in to InfoSphere DataStage clients. You recently removed all members of the WebSphere Application Server cluster and then added members again.
312
Causes
When all cluster members are removed from the cluster, the cluster template is removed. New cluster members are set up with the default cluster template. The default template is not compatible with IBM InfoSphere Information Server.
Environment
All environments.

1. 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:
Operating system AIX Command installdir/ASBServer/bin/ reconfigure_was_cluster.sh -user wasadmin_user -password wasadmin_password
wasadmin_user and wasadmin_password are the user name and password of the WebSphere Application Server administrator. 3. Start the cluster as described in "Restarting application server processes" in the IBM InfoSphere Information Server Administration Guide.
313
314
Chapter 18. Removal problems

These problems and resolutions are related to removing IBM InfoSphere Information Server products.
IBM InfoSphere Information Server installation fails repeatedly

If an installation fails repeatedly on a computer that has been used for a previous IBM InfoSphere Information Server installation, verify that the previous installation was completely removed.
Symptoms
Installation fails on a computer that has been used for a previous IBM InfoSphere Information Server installation.
Causes
Previous installations are not completely removed, or the computer was not restarted after the software removal process completed.
Environment
This advice applies to all operating systems.

Before you install InfoSphere Information Server, you must completely remove previous installations, including failed installations, of InfoSphere Information Server. You must remove previous versions of InfoSphere Information Server from the installation location where you intend to install the new instance. You must also remove DB2 and WebSphere from the target installation locations before the InfoSphere Information Server installation program can reinstall DB2 and WebSphere. To ensure that the previous installation is completely removed, follow the manual software removal steps for the previous installation.
315
316
Part 5. Appendixes
317
318
Contacting IBM
You can contact IBM for customer support, software services, product information, and general information. You also can provide feedback to IBM about products and documentation. The following table lists resources for customer support, software services, training, and product and solutions information.
Table 84. IBM resources Resource IBM Support Portal Description and location You can customize support information by choosing the products and the topics that interest you at www.ibm.com/support/ entry/portal/Software/ Information_Management/ InfoSphere_Information_Server You can find information about software, IT, and business consulting services, on the solutions site at www.ibm.com/ businesssolutions/ You can manage links to IBM Web sites and information that meet your specific technical support needs by creating an account on the My IBM site at www.ibm.com/account/ You can learn about technical training and education services designed for individuals, companies, and public organizations to acquire, maintain, and optimize their IT skills at http://www.ibm.com/software/swtraining/ You can contact an IBM representative to learn about solutions at www.ibm.com/connect/ibm/us/en/
Software services
My IBM
Training and certification
IBM representatives
Providing feedback
The following table describes how to provide feedback to IBM about products and product documentation.
Table 85. Providing feedback to IBM Type of feedback Product feedback Action You can provide general product feedback through the Consumability Survey at www.ibm.com/software/data/info/ consumability-survey
319
Table 85. Providing feedback to IBM (continued) Type of feedback Documentation feedback Action To comment on the information center, click the Feedback link on the top right side of any topic in the information center. You can also send comments about PDF file books, the information center, or any other documentation in the following ways: v Online reader comment form: www.ibm.com/software/data/rcf/ v E-mail: comments@us.ibm.com
320
Accessing product documentation

Documentation is provided in a variety of locations and formats, including in help that is opened directly from the product client interfaces, in a suite-wide information center, and in PDF file books. The information center is installed as a common service with IBM InfoSphere Information Server. The information center contains help for most of the product interfaces, as well as complete documentation for all the product modules in the suite. You can open the information center from the installed product or from a Web 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 Server Manager, the main Help item opens a local help system. Choose Help > Open Info Center to open the full suite information center. v Press the F1 key. The F1 key typically opens the topic that describes the current context 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. The host_name is the name of the services tier computer where the information center is installed, and port_number is the port number for InfoSphere Information Server. The default port number is 9080. For example, on a Microsoft Windows Server computer named iisdocs2, the Web address is in the 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 and periodically refreshed at http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r7/ index.jsp.
Obtaining PDF and hardcopy documentation

v A subset of the PDF file books are available through the InfoSphere Information Server software installer and the distribution media. The other PDF file books are available online and can be accessed from this support document: https://www.ibm.com/support/docview.wss?uid=swg27008803&wv=1. v You can also order IBM publications in hardcopy format online or through your local IBM representative. To order publications online, go to the IBM Publications Center at http://www.ibm.com/e-business/linkweb/publications/ servlet/pbi.wss.
321
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: comments@us.ibm.com
322
Product accessibility
You can get information about the accessibility status of IBM products. The IBM InfoSphere Information Server product modules and user interfaces are not fully accessible. The installation program installs the following product modules and components: v IBM InfoSphere Business Glossary v IBM InfoSphere Business Glossary Anywhere v IBM InfoSphere DataStage v IBM InfoSphere FastTrack v v v v IBM IBM IBM IBM InfoSphere InfoSphere InfoSphere InfoSphere Information Analyzer Information Services Director Metadata Workbench QualityStage
For information about the accessibility status of IBM products, see the IBM product accessibility information at http://www.ibm.com/able/product_accessibility/ index.html.
Accessible documentation
Accessible documentation for InfoSphere Information Server products is provided in an information center. The information center presents the documentation in XHTML 1.0 format, which is viewable in most Web browsers. XHTML allows you to set display preferences in your browser. It also allows you to use screen readers and other assistive technologies to access the documentation.
IBM and accessibility

See the IBM Human Ability and Accessibility Center for more information about the commitment that IBM has to accessibility.
323
324
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 in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd. 1623-14, Shimotsuruma, Yamato-shi Kanagawa 242-8502 Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web
325
sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation J46A/G4 555 Bailey Avenue San Jose, CA 95141-1003 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to
326
IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable 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, must include 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 rights reserved. If you are viewing this information softcopy, the photographs and color illustrations may not appear.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM 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 United States, and/or other countries. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office UNIX is a registered trademark of The Open Group in the United States and other countries. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.
Notices and trademarks
327
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. The United States Postal Service owns the following trademarks: CASS, CASS Certified, DPV, LACSLink, ZIP, ZIP + 4, ZIP Code, Post Office, Postal Service, USPS and United States Postal Service. IBM Corporation is a non-exclusive DPV and LACSLink licensee of the United States Postal Service. Other company, product or service names may be trademarks or service marks of others.
328
Index Special characters

/etc/magic file editing 271 .ds files data set descriptor files 271 .zip files installation log files 289 application server (continued) removing profiles (continued) metadata repository tier (AIX) 231 services tier (AIX) 229 troubleshooting 302, 303, 304 architecture engine 3 installation 11 services 5 ASB agents 3 automatic client reroute configuring for a DB2 database cluster 131 configuring for an HADR configuration 246 configuring for HADR setup 139 conductor nodes 45 configuring InfoSphere Information Server 239 configuring the browser removing software 221 connectivity DB2 272 planning 92 testing ODBC drivers 283 Connector access services agent 3 customer support contacting 319
Numerics
32-bit systems 64-bit systems 57 57
A
accounts, user 100 active-passive configuration configuration example (MSCS) 108 configuration overview (AIX) 105 creating users and user groups (System Automation for MultiPlatforms example) 115 defining and starting resource group (System Automation for Multiplatforms example) 112 high availability control scripts 120 installing high availability software (System Automation for Multiplatforms example) 110 installing InfoSphere Information Server in cluster (System Automation for Multiplatforms example) 115 preparing server hardware (MSCS example) 109 road map for installation 72 setting up network (MSCS example) 109 setting up resource agent scripts (System Automation for Multiplatforms example) 116 setting up virtual IP address (System Automation for Multiplatforms example) 111 testing (System Automation for Multiplatforms example) 118 analysis database creating in existing DB2 instance by using installation program 122 setting up in existing DB2 instance 122 setting up in Oracle database system 151 analysis databases sizing 21 topologies 18 application server planning 57 removing profiles 229 engine tier (AIX) 230 Copyright IBM Corp. 2005, 2011
D
data collection and analysis 211 data source names creating 283 specifying 281 data sources modifying connection properties 247 database Match Designer database 154 database clustering overview 40 database connection properties modifying 247 database system determining how to install 55 database.properties file modifying 246 DB2 database clustering configuration overview 126 configuring automatic client reroute 131 creating a cluster 129 creating the metadata repository database 129 creating users and groups 130 heartbeat 127 installing DB2 database system 129 installing HA software 128 overview 40 preparing servers, file system, and storage 127 running installation program 130 specifying alternate database address and port 132 verifying 136 DB2 database system configuring 273 configuring InfoSphere DataStage 272 using existing instance for metadata repository and analysis database 122 DB2 installation warnings 294 DB2 setup program running 272
B
backing up planning 47 primary to standby in HADR setup 141 bind DB2 package 282 buildop components compilers 266
C
C++ compiler IBM AIX 266 C++ compilers installing 266 caching proxies 39 capacity planning 47 character encodings supported 170 cluster members resolving connection problems after removing 312 clustering application servers 32 clusters planning 11 code pages 170 command prompt installing from 190 running software removal program from 227 component installer described 3 components described 3 compute node AIX 261 compute nodes 45 distributing transform libraries to 265
329
DB2DBDFT environment variable configuring 273 DB2INSTANCE environment variable configuring 273 db2nodes.cfg file configuring 273 deployments installation topologies 11 diagnostic tools 211 domain connections troubleshooting 302 DS_CONNECT 283 dsenv file sample entries 279 DSNs creating 283
graphical mode configuring the browser 175 removing software configuring the browser 221 starting software removal program in 224 grids configuring 45 planning 11
I
IBM DB2 database system determining how to install 55 preinstallation 121 using existing instance for metadata repository database (AIX) 124 individual modules removing 222 information analysis planning 21 Informix XPS configuring access 276 InfoSphere Business Glossary configuring 285 InfoSphere DataStage configuring 277 configuring globalization (NLS) 278 configuring on DB2 database servers 272 testing the installation 212 InfoSphere DataStage plug-ins monitoring installation 210 InfoSphere Information Analyzer agent 3 configuring 284 database, analysis 21 InfoSphere Information Server installing 215, 217 on AIX 232 engine tier 233 metadata repository tier 235 services tier 232 preparing to install 177 removing 219, 222, 229, 232, 233, 235 shutting down tasks and applications before removing 220 InfoSphere Information Server installation program running 166 InfoSphere Information Server Web console described 5 InfoSphere Information Services Director agent 3 testing installation 214 InfoSphere Metadata Server troubleshooting startup 303, 304 InfoSphere QualityStage configuring 277 configuring globalization (NLS) 278 testing the installation 212 installation CDs 175 kernel parameter configuration 99 log files 289 monitoring overview 208 planning 3 process overview 3 sample checklist: basic installation with no high availability 59 sample checklist: isolated engine tier and parallel engine configuration 65 sample road map: high availability active-passive configuration 72 sample road map: high availability clustered configuration 78
H
HA software installing 128 HADR configuration configuring automatic client reroute 246 hardware requirements 91 health checkers 211 high availability active-passive configuration example 108 active-passive configuration scripts (System Automation for Multiplatforms example) 116 active-passive configuration testing (System Automation for Multiplatforms example) 118 configuration overview 23 DB2 options 40 design considerations 23 failover 105 installing management software (System Automation for Multiplatforms example) 110 required configuration 167 setting up network (MSCS example) 109 high availability clustered configuration road map for installation 78 high availability control scripts overview 120 using (System Automation for Multiplatforms example) 116 high availability disaster recovery (HADR) configuring automatic client reroute 139 configuring primary server 139 configuring standby server 141 creating the database 138 creating users and groups 139 installing DB2 database system 40, 138 preparing servers and storage 137 running installation program 139 setting up metadata repository in 136 specifying alternate database address and port 142 starting 146 validation 147 HTTP port 239 HTTPS example scenario 49 https.conf 254, 258
E
EAR deployment warnings during 293 encoded slashes allowing 307 encodings supported 170 engine tier example scenario with isolated engine 49 overview 3 topology example 11 Enterprise stage jobs granting user privileges 272 environment variables parallel engine 267 setting 267 setting for InfoSphere DataStage
279
F
failover 105 FilePropagator utility propagating changes 244 propagating configuration changes (AIX) 135, 245 firewall clustering 40 Fix Central 175 fix packs 175 front-end dispatcher modifying 167 front-end load balancer installing 165 front-end web server alternative, front-end load balancer 164 installing 164 front-end Web server clustering 35
G
genkey 192 globalization (NLS) configuring 278 supported character encodings 170
330
installation (continued) scenario with basic client-server topology 49 scenario with clustered metadata repository tier and services tier 52 scenario with isolated engine tier 49 scenario with parallel engine configuration 49 scenario with two-server active-passive high availability topology 50 strategy overview 55 temporary files 289 topologies 11 troubleshooting on AIX 92 troubleshooting permissions 299 user privileges 300 verification 211 installation logs monitoring 208 installation program 179 running for DB2 database clustered configuration 130 running for HADR configuration 139 installation records updating 248 installation software obtaining 175 installing C++ compilers 266 command prompt (silent) 190 completing the installation process 190 InfoSphere Information Server 215, 217 preparation steps 177 running the installation wizard 187 saving a response file 187 specifying options 182 investigation reports WebSphere Application Server 284 IP sprayer topology 38, 165 ISALite 211 ISInstall*.log 208, 210 ITAG installations 3, 13 IWAV0003E 293
library path environment variables InfoSphere DataStage libraries 279 load balancers introduction 37 locale 169 log files installation 289 WebSphere Application Server 290 log.txt 209 logical tiers 3 login troubleshooting 309 LOGTO 283 lssam 136
monitoring (continued) WebSphere Application Server ear deployment 210 WebSphere Application Server installation 209 monitoring installation overview 208 MPP 261
N
naming conventions projects 104 national language support supported character encodings networks planning 92 170
M
maintenance planning 47 massively parallel processing configurations 45 configuring compute node (AIX) 261 Match Designer database configuring 283 database requirements 22, 154 locations 18 planning 154 maxuproc parameter setting 269 memory setting for parallel jobs 269 metadata importing with Metadata Asset Manager 176 installing importing applications 176 metadata repository changing host name and port 242 overview 7 metadata repository database creating for HADR configuration 138 creating in existing DB2 instance by using installation program 122 creating in existing DB2 instance by using scripts (AIX) 124 creating within DB2 database cluster 129 determining how to create 55 setting up in existing DB2 instance 122 setting up in Oracle database system 151 supported topologies 18 updating dbalias 243 updating properties 246 metadata server troubleshooting startup 303, 304 Microsoft SQL Server database system determining how to install 55 Microsoft Windows Cluster service (MSCS) setting up network 109 monitoring InfoSphere DataStage plug-in installation 210 installation logs 208 PX operators installation 210
O
ODBC data source bind 282 vendor drivers 282 ODBC data sources configuring access (AIX 279 ODBC drivers testing connectivity 283 ojb-conf.jar file modifying 243 Oracle database system configuring 274 determining how to install 55 high availability options 43 Oracle Enterprise stage job privileges 274 Oracle parallel server granting access 274 Oracle RAC creating database by using scripts 150 establishing communication with WebSphere Application Server 150 high availability 43 node names 150 requirements 150 running installation program 150 setting up metadata repository in 149 orchserver accounts creating 275
J
Java Virtual Machine (JVM) troubleshooting 309
K
kernel parameters modifying 99 setting 269
P
Page Not Found errors troubleshooting 307 paging space on IBM AIX 270 setting 270 parallel engine adding computers 261 C++ compilers 266 connecting to Teradata databases copying components 261 data set descriptor files 271 environment variables 267 example scenario 49 Index
L
language 169 legal notices 325 libicu libraries removing 92 LIBPATH environment variable configuring 273
275
331
parallel engine (continued) monitoring system resources 3 running rsh without a password 263 setting paging space 270 setting paging space (IBM AIX) 270 using ssh 262 parallel jobs configuring 269 setting the maximum memory 269 user privileges 264 parallel processing configuring compute nodes (AIX) 261 massively parallel processing (MPP) systems 45 overview 45 symmetric multiprocessing (SMP) systems 45 transform library distribution methods 265 Passport Advantage 175 passwords in response files 192, 197 installation 100 naming restrictions 103 permissions directory and user 299 planning capacity 47 clusters 11 connectivity 92 engine tier 3 grids 11 IDs 100 installation 3 Match Designer database 154 metadata repository tier 7 naming, projects 104 networks 92 ports 92 services tier 5 tier computers 91 topologies 11 users 100 WebSphere Application Server 57 ports changing 241 configuring for HADR 139 planning 92 preinstallation requirements tier computers 58 processes, used by InfoSphere Information Server 97 product accessibility accessibility 323 product documentation accessing 321 profiles removing (AIX) 229 engine tier 230 metadata repository tier 231 services tier 229 project naming 104 propagating changes WebSphere Application Server AIX 244
PX operators monitoring installation
210
R
RAID 47 registered-servers.xml modifying to configure HTTPS 254 modifying to switch back to HTTP 258 remote shell command configuring 263 removing command prompt (silent) 227 InfoSphere Information Server 219 removing software manual removal 232 requirements system 91 Resource Tracker monitoring system resources 3 response files 190 AIX parameters 198 creating 191 encrypting information in 192 passwords 197 samples 197 silent mode (removing software) 227 syntax 197 rsh command configuring 263 program location 264
S
SAN (storage area networks) 47 secure HTTP (HTTPS) configuring for InfoSphere Information Server 248 manually configuring components for 254 switching back to HTTP 258 secure shell program configuring 262 Secure Sockets Layer (SSL) configuring for InfoSphere Information Server 248 security configuring 259 encrypting information in response files 192 server engine starting and stopping 286 services tier troubleshooting 306 services, used by InfoSphere Information Server 97 setup command syntax 192 silent installation 190 AIX parameters 198 by using a response file 195 silent mode starting installation program in 190 starting software removal program in 227
software removal Microsoft Windows security notifications 224 overview 221 silent mode 227 starting in graphical mode 224 troubleshooting 315 verifying 315 software requirements 91 software services contacting 319 SQA reports WebSphere Application Server 284 ssh program configuring 262 stage, Oracle Enterprise 274 starting and stopping InfoSphere Information Server engine 286 starting the installation program by using a response file 195 storage area networks (SAN) 47 suite installation monitoring 208 suite removal manually on AIX 232 engine tier 233 metadata repository tier 235 services tier 232 on AIX 229 removing remaining files engine tier (AIX) 230 metadata repository tier (AIX) 231 services tier (AIX) 229 shutting down tasks and applications 220 support customer 319 symmetric multiprocessing (SMP) systems 45 sys.gv_$instance table granting access 274 sys.v_$cache table granting access 274 System Automation for Multiplatforms configuration example 108 system health checker 211 system requirements 91 SystemErr.log 290 SystemOut.log 210, 290
T
Teradata database program installing the Teradata Tools and Utilities 275 Teradata database system creating users 275 Teradata databases setting up connectivity 275 Teradata Tools and Utilities installing 275 testing the installation running the IBM Support Assistant Lite tool 211
332
tier computers required directories 58 tiers described 3 engine 3 installation options 182 product components contained in 3 relationships among 8 services 5 Tivoli System Automation for Multiplatforms creating users and user groups 115 defining and starting resource group 112 installing 110 installing InfoSphere Information Server in cluster 115 setting up high availability control scripts 116 setting up virtual IP address 111 testing the configuration 118 Tivoli System Automation for Multiplatforms (SA MP) installing in DB2 database cluster 128 topologies active-passive 26 analysis databases and 18 computer for each tier 12 dedicated engine tier 11 fully clustered 30 installation 11 instance with multiple server engines 17 ITAG installations 13 Match Designer database and 18 multiple InfoSphere Information Server instances 13 trace logs disabling 307 enabling 307 trademarks list of 325 troubleshooting application server 302 DB2 installation warnings 294 domain connections 302 enabling trace logs 307 failed installations 295, 315 ISALite tools 211 JVM failure 309 log files 289, 295 login failure 309 Page Not Found errors 307 report results, viewing 307 services tier 306 software removal 315 temporary files 289 user accounts 293 user privileges for installation 300 WebSphere Application Server administrative console 311 WebSphere Application Server installation with InfoSphere Information Server 301 WebSphere Application Server registry 305
U
updateSignerCerts 254 UpdateSignerCerts command command syntax 253 UpdateSignerCerts tool SSL, reenabling 252 upgrading monitoring overall suite installation 208 user IDs naming restrictions 103 user limits modifying 99 user privileges Enterprise stage jobs 272 overview 300 parallel jobs 264 users planning 100 uvodbc.config file configuring 281
V
verifying the installation running the IBM Support Assistant Lite tool 211 Version.xml modifying to configure HTTPS 254 modifying to switch back to HTTP 258 virtual IP address setting up for active-passive configuration (System Automation for Multiplatforms example) 111
WebSphere Application Server clustering configurations, required 157, 159 WebSphere Application Server clusters load balancing 37 WebSphere Application Server deployment manager administrative security 160 custom profile, creating 161 deployment manager profile, creating 160 node, federating 161 Profile Management Tool 160, 161 WebSphere Application Server ear deployment monitoring 210 WebSphere Application Server installation monitoring 209 WebSphere Application Server Network Deployment cluster environments, installing 157, 159 clustering overview 33 installation 157, 159 replication domains 163 WebSphere Application Server, Version 7.0 SSL, enabling 250, 251 WebSphere Application Server, Version 8.0 SSL, enabling 250, 251
W
WebSphere Application Server changing HTTP port 239 changing ports 241 cluster members, creating 162 cluster, creating 162 configurations, required 157 front-end load balancer, for clustering 164 front-end web server, for clustering 164 front-end Web server, for clustering 34 HTTP session persistence 162 installation troubleshooting 301 installing 157 non-clustered installation 168 planning 57 planning for clusters 158 profile certificates, change default 256 propagating changes 244 clustered configuration (AIX) 245 stand-alone configuration (AIX) 244 removing profiles 229 reports 284 troubleshooting startup (Windows) 303, 304 Index
333
334
Printed in USA
GC19-3612-00
Spine information:
Version 8 Release 7

AIX Server

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

AIX Server

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AIX Server

Uploaded by

Copyright:

Available Formats

Version 8 Release 7

Plan, Install, and Configure IBM InfoSphere Information Server

Plan, Install, and Configure IBM InfoSphere Information Server

Chapter 2. Selecting your installation topologies . . . . . . . . . . . . . 11

Part 2. Installing IBM InfoSphere Information Server software . . . . 173

Chapter 3. Reviewing installation checklists . . . . . . . . . . . . . 55

Chapter 6. Installing IBM InfoSphere Information Server software . . . . . 179

Chapter 4. Preparing the tier computers 91

210 210 211 211 212 214

. 256 . 257 . 259

Chapter 10. Configuring a parallel processing environment. . . . . . . 261

Chapter 7. Adding additional tiers or products to an installation . . . . . . 215

Chapter 8. Removing IBM InfoSphere Information Server software . . . . . 219

224 227 229 229 229 232 232

Chapter 11. Configuring product modules in the suite . . . . . . . . 277

Part 3. Configuring the software after installation . . . . . . . . . 237

Part 4. Troubleshooting installations . . . . . . . . . . . 287

Chapter 13. General installation problems . . . . . . . . . . . . . 293

293 293 294 295

Enabling and disabling trace logging of the reporting engine . . . . . . . . . .

Chapter 17. Client and console problems . . . . . . . . . . . . . 309

Chapter 14. Authentication problems

Chapter 15. Application server problems . . . . . . . . . . . . . 301

Chapter 18. Removal problems . . . . 315

Part 5. Appendixes . . . . . . . . 317

302 302 303 304 305 306

Accessing product documentation

Product accessibility . . . . . . . . 323 Notices and trademarks . . . . . . . 325 Index . . . . . . . . . . . . . . . 329

Chapter 16. IBM InfoSphere Information Server reporting problems 307

Part 1. Planning to install IBM InfoSphere Information Server

Copyright IBM Corp. 2005, 2011

Chapter 1. Tiers and components

Copyright IBM Corp. 2005, 2011

DataStage Telnet Service

DataStage Engine Resource service

istool command line

*IBM Metabrokers and bridges

Source and target data

Figure 1. Engine tier components

Chapter 1. Tiers and components

Figure 2. Services tier services

Metadata repository tier

Chapter 1. Tiers and components

Metadata repository tier

Metadata repository database

Information Analyzer analysis databases

Figure 3. Metadata repository tier components

Engine tier ODBC drivers Engine

Metadata repository tier

Figure 4. Tier relationships

Chapter 1. Tiers and components

Chapter 2. Selecting your installation topologies

Designing an installation topology

Basic installation topologies

Dedicated engine tier topology

Copyright IBM Corp. 2005, 2011

Engine tier Metadata repository tier

Figure 5. Dedicated engine tier topology

Dedicated computer for each tier topology