You are on page 1of 149

IBM Information Server

Version 8 Release 1

Planning, Installation, and Configuration Guide

GC19-1048-03

IBM Information Server

Version 8 Release 1

Planning, Installation, and Configuration Guide

GC19-1048-03

Note Before using this information and the product that it supports, read the information in Notices on page 133.

Copyright International Business Machines Corporation 2005, 2008. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents
Chapter 1. Installing and upgrading IBM Information Server . . . . . . . . . . 1 Chapter 2. Planning for the installation of IBM Information Server . . . . . . . 3
Step 1: Review system requirements and release notes . . . . . . . . . . . . . . . . . 4 Step 2: Select an installation topology for your products . . . . . . . . . . . . . . . . 4 Tiers and components in the IBM Information Server topology . . . . . . . . . . . . 4 Types of topologies . . . . . . . . . . . 10 Topology example . . . . . . . . . . . 11 Consider the installation methods: graphical wizard, console, or response file . . . . . . 12 Step 3: Prepare disk, file, and network resources . . 13 Setting up file systems and directories . . . . 16 Assessing your network and connectivity . . . 20 Capacity planning . . . . . . . . . . . 22 Project naming conventions . . . . . . . . 23 Step 4: Modify kernel parameters and user limits (Linux, UNIX) . . . . . . . . . . . . . 24 Step 5: Set up users for installation . . . . . . 26 Step 6: Select an application server . . . . . . 30 Preparing the 64-bit application server (Red Hat) 30 Step 7: Select a location for the metadata repository 32 Installation options for DB2 Version 9.1 versus 9.5 . . . . . . . . . . . . . . . . 33 Manually creating a DB2 database for the metadata repository . . . . . . . . . . 34 Creating an Oracle tablespace for the metadata repository . . . . . . . . . . . . . . 34 Creating a Microsoft SQL Server database for the metadata repository . . . . . . . . . . 34 Step 8: Prepare for your products . . . . . . . 35 Accessing the license file . . . . . . . . . 35 ODBC drivers for WebSphere DataStage and WebSphere QualityStage . . . . . . . . . 35 WebSphere QualityStage Match Designer . . . 36 WebSphere Information Analyzer . . . . . . 38 Upgrading from IBM Information Server, Version 8.0.1 . . . . . . . . . . . . . . . . Upgrading from DataStage or QualityStage, Versions earlier than 8.0.1. . . . . . . . . Updating Version 8.1 products and components . . Updating the license before adding new product modules and components . . . . . . . . . Installing components that are not in the suite installation program . . . . . . . . . . . Installing IBM Information Server Business Glossary Anywhere clients . . . . . . . . Installing WebSphere MetaBrokers and bridges Installing z/OS components for IBM WebSphere DataStage MVS Edition . . . . . . . . . 59 62 63 63 64 64 65 66

Chapter 4. Configuring IBM Information Server . . . . . . . . . . . . . . . 71


Creating users and groups for IBM Information Server . . . . . . . . . . . . . . . . 71 Configuring national language support (Linux, UNIX) . . . . . . . . . . . . . . . . 71 Configuring environment variables for the engine (Linux, UNIX) . . . . . . . . . . . . . 72 Configuring product modules in the suite . . . . 73 Configuring WebSphere DataStage and WebSphere QualityStage . . . . . . . . . 73 Testing the WebSphere Information Services Director installation. . . . . . . . . . . 75 Configuring WebSphere Information Analyzer . . 75 Configuring WebSphere Business Glossary . . . 76 Configuring IBM Metadata Workbench . . . . 76 Configuring IBM Information Server FastTrack 76 Configuring a parallel processing environment . . 76 Adding computers to share engine processing . . 76 C++ compilers for job development . . . . . 82 Setting environment variables for the parallel engine . . . . . . . . . . . . . . . 82 Configuring the parallel engine (Linux, UNIX) . 84 Configuring the parallel engine (Windows) . . . 88 Configuring database connectivity in a parallel environment . . . . . . . . . . . . . 91 Configuring access to ODBC data sources . . . 96 Stopping and starting the engine . . . . . . . 100

Chapter 3. Installing, upgrading, and applying updates . . . . . . . . . . 41


Creating a new installation of IBM Information Server . . . . . . . . . . . . . . . Launching the installation program by using the installation wizard . . . . . . . . . . Launching the installation program from the command prompt (silent or console) . . . . Encodings that are supported by the installation program . . . . . . . . . . . . . Upgrading from Version 7.5.2 or 7.5.3 . . . . Planning for upgrading to IBM Information Server, Version 8.1 . . . . . . . . . .
Copyright IBM Corp. 2005, 2008

. 41 . 44 . 45 . 58 . 59 . 59

Chapter 5. Troubleshooting installations . . . . . . . . . . . . 101


Installation log files . . . . . . . . . . . Troubleshooting command-line scripts . . . . . Verifying uninstallation of IBM Information Server Ignoring runtime error during uninstallation . . . Verifying that sufficient disk space is available . . Resolving incompatible Java Runtime Executable error (Linux, UNIX) . . . . . . . . . . . Resolving incompatible Java Runtime Executable error (Windows) . . . . . . . . . . . . 101 101 101 102 102 103 104

iii

Resolving failed installations for Red Hat Linux systems . . . . . . . . . . . . . . Directory and user permissions . . . . . . User privileges . . . . . . . . . . . . Correcting errors with kernel parameter values . Resolving connection problems . . . . . . Resolving WebSphere Application Server installation problems . . . . . . . . . .

. . . . .

105 106 108 109 109

Removing application server profiles (Linux, UNIX) . . . . . . . . . . . . . . Removing IBM Information Server from a command prompt (Linux, UNIX) . . . . . Manually removing IBM Information Server (Linux, UNIX) . . . . . . . . . . .

. 120 . 120 . 122

. 110

Product documentation . . . . . . . 127


Contacting IBM . . . . . . . . . . . . 127

Chapter 6. Removing IBM Information Server . . . . . . . . . . . . . . 113


Removing IBM Information Server from your system (Windows) . . . . . . . . . . Removing application server profiles . . Removing IBM Information Server from a command prompt (Windows) . . . . . Manually removing IBM Information Server (Windows) . . . . . . . . . . . Removing IBM Information Server from your system (Linux, UNIX) . . . . . . . . . . . . . . 113 . 114 . 115 . 117 . 119

How to read syntax diagrams . . . . 129 Product accessibility . . . . . . . . 131 Notices . . . . . . . . . . . . . . 133
Trademarks . . . . . . . . . . . . . . 135

Index . . . . . . . . . . . . . . . 137

iv

Planning, Installation, and Configuration Guide

Chapter 1. Installing and upgrading IBM Information Server


IBM Information Server includes a set of collaborative product modules and components that can be distributed across multiple computers. The current version and the translated versions of this information are on the Web: http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r1/topic/ com.ibm.swg.im.iis.productization.iisinfsv.install.doc/topics/ cont_iisinfsrv_install.html This outline covers the high-level process to install IBM Information Server, its product modules, and optional components: 1. Plan for the deployment of IBM Information Server and its product modules in your enterprise by filling in the planning worksheets. 2. Install IBM Information Server in your enterprise. This step requires you to install a combination of products and components that is dependent on products that you purchased and on the number of computers in your deployment: v Databases to hold application data and metadata v WebSphere Application Server v Product modules v Additional prerequisites 3. Configure environment variables, security, and connectivity. 4. Tune the deployment for performance. 5. If you are upgrading, back up your existing installation.

Copyright IBM Corp. 2005, 2008

Planning, Installation, and Configuration Guide

Chapter 2. Planning for the installation of IBM Information Server


Before you install IBM Information Server, you select the installation topology and location, review your information integration and hardware needs, and complete the preparation activities. The process that you use to install IBM Information Server depends on whether you install the product for the first time, add a new product module to an existing installation, or upgrade from an earlier release. The following table describes the types of installation:
Table 1. Installation types Installation type Install IBM Information Server, Version 8.1, for the first time Add an additional product module to an existing installation of IBM Information Server, Version 8.1 Process information Run the IBM Information Server, Version 8.1, installation program. Run the IBM Information Server, Version 8.1, installation program to install additional product modules.

Add a component that is not included in the Install the additional components by using installation program for IBM Information their installation programs. Server, Version 8.1, to an existing installation of IBM Information Server, Version 8.1 Upgrade from IBM Information Server, Version 8.0 to Version 8.1 Upgrade from DataStage or QualityStage, Version 7.5.x or earlier to IBM Information Server, Version 8.1 Run the Version 8.1 installation program. Either upgrade your existing installation or create a new installation by running the Version 8.1 installation program. Then, migrate your projects and jobs.

During an upgrade, the upgrade preserves the DataStage and QualityStage project directories and metadata repository, but the upgrade migrates the metadata repository to the new database model for the metadata repository. Before you attempt any installation or upgrade, it is good practice to back up your system, especially your critical data. The planning documentation provides checklists and worksheets to help you verify that your computers and network meet the basic requirements for the installation. The checklists cover the big tasks that you do sequentially before you install IBM Information Server. The worksheets are tables in some of the tasks that you fill out so that you can later install based on the information from the worksheets. To help you keep track of the various settings and parameters that are required to install an IBM Information Server system, you are encouraged to print and complete the checklists before you run the installation program. Also, you can include the checklists in the documentation that you create about your installation environment.

Copyright IBM Corp. 2005, 2008

Step 1: Review system requirements and release notes


Ensure that all computers meet the hardware and software requirements for the product modules and components that you want to install. To obtain the most up-to-date information about the installation, go to the system requirements at www.ibm.com/software/data/infosphere/info-server/overview/ requirements.html and the release notes at publib.boulder.ibm.com/infocenter/ iisinfsv/v8r1/topic/ com.ibm.swg.im.iis.productization.iisinfsv.relinfo.doc/topics/ cont_infsrv_rnote.html.

Step 2: Select an installation topology for your products


To select a topology, you must consider your performance needs by reviewing the capacity requirements for the topology elements: the server, disk, network, data sources, targets, data volumes, processing requirements, and any service-level agreements. Depending on how you plan to use IBM Information Server and its product modules, you can determine where you want to install the product suite.

Tiers and components in the IBM Information Server topology


You install IBM Information Server in logical tiers: client, metadata repository, services, and engine. A tier is a logical grouping of software that you map to the physical hardware. In addition to the main product modules, you install the product components in each tier as needed: Client Product module clients that are not Web-based and that are used for development and administration in IBM Information Server Engine Runtime engine that runs the IBM Information Server tasks Metadata repository Database that stores the shared metadata, data, and configuration for IBM Information Server and the product modules. Also, it can store extended analysis information as an analysis database. Services Common and product-specific services for IBM Information Server along with IBM WebSphere Application Server (application server) These tiers work together to provide services, processing power, and metadata storage, as shown in the following diagram:

Planning, Installation, and Configuration Guide

Client tier

Services tier
Services for IBM Information Server Common services

Engine tier
IBM Information Server engine

Connectors Product-specific services

Packs

WebSphere QualityStage modules

Application server

Service agents
(Logging, Communication [ASB], Job Monitor, PerfMon)

Metadata repository tier

Figure 1. Tier relationships

The following table shows the products and components that the installation program installs by tier. For a complete installation of a product and its components, you must select the product and components as indicated in the table when you install each tier. For example, to install IBM WebSphere DataStage, select WebSphere DataStage and QualityStage on the product selection panel of the installation wizard when you install the metadata repository, client, services, and engine. Tiers that are installed separately must be at the same version, release, fix pack, and patch level of IBM Information Server.
Table 2. Products and the tiers on which they must be installed. Product or component IBM Information Server FastTrack IBM Information Server Manager IBM Metadata Workbench IBM WebSphere Business Glossary IBM Information Server Business Glossary Anywhere (requires WebSphere Business Glossary)* Tiers on which to install Services, Client Services, Engine, Client Services, Engine Services Services

IBM WebSphere DataStage and QualityStage Services, Engine, Client IBM WebSphere Information Analyzer IBM WebSphere Information Services Director IBM WebSphere Metadata Server Metadata repository, Services, Engine, Client Services, Engine, Client Metadata repository, Services
Chapter 2. Planning for installation

Table 2. Products and the tiers on which they must be installed. (continued) Product or component
*

Tiers on which to install

The client is installed separately.

Client tier
The client tier includes the IBM Information Server console, IBM WebSphere DataStage and QualityStage clients, and other clients. The following tools are installed as part of the client tier, based on the products and components that you select: v IBM Information Server console (for administration, IBM WebSphere Information Analyzer, and IBM WebSphere Information Services Director) v IBM Information Server Manager client v IBM WebSphere DataStage and QualityStage Administrator client v IBM WebSphere DataStage and QualityStage Designer client v IBM WebSphere DataStage and QualityStage Director client v IBM Information Server FastTrack client Two additional clients have separate installation programs, which are provided on the installation media. v IBM Information Server Business Glossary Anywhere client v Import Export Manager and the IBM WebSphere MetaBrokers and bridges Use of the IBM WebSphere DataStage and QualityStage clients is controlled by the server license.

Web clients
The clients listed here, unlike the preceding items, are Web clients and are installed as part the services tier. v IBM Information Server Web console (for administration, reporting, IBM WebSphere Business Glossary, and the Information Services Catalog for WebSphere Information Services Director ) v IBM Metadata Workbench client v IBM WebSphere Business Glossary Browser client

Multi-client manager
You must install the multi-client manager to run multiple versions of WebSphere DataStage clients, such as Version 8 and 7.5. The installation program installs the manager on your computer when you install the clients on a computer where DataStage Version 7.5 clients are installed.

WebSphere MetaBrokers and bridges


WebSphere MetaBrokers and bridges are used by certain clients to import metadata into and export metadata out of the metadata repository. For details about the client tools with which they are used, as well as installation instructions, see Installing WebSphere MetaBrokers and bridges on page 65.

Planning, Installation, and Configuration Guide

Engine tier
The engine tier consists of the IBM Information Server engine and related components. The following product modules require the engine tier and have components that are installed with the engine: IBM WebSphere DataStage, IBM WebSphere Information Analyzer, IBM WebSphere Information Services Director, IBM Information Server FastTrack, and IBM WebSphere QualityStage. When you install the engine tier separately from the services tier, you must select the same product modules that you installed on the services tier. The engine tier must have access to the services tier. Before you install the engine tier, you must install the services tier on the same computer or on a different computer that is in the same network segment. On Windows, only one IBM Information Server engine can be installed on a single computer. On Linux and UNIX, multiple engines of the same or different versions can be installed on the same computer. The installation program installs the following engine components with the IBM Information Server engine: Engine The IBM Information Server engine runs jobs to extract, transform, load, and standardize data. The engine runs parallel, server, and sequencer jobs. ASB agents The ASB agent is a Java process that runs in the background on each computer that hosts IBM Information Server engine or client tiers. When a service that runs on the services tier receives a service request that requires processing by an IBM Information Server component, the agent receives and conveys the request. On Microsoft Windows, the agent runs as a service. On Linux and UNIX, the agent runs as a daemon. The service name and the daemon name are ASBAgent. ODBC drivers A set of ODBC drivers that works with IBM Information Server components is installed with the engine components. Resource Tracker The installation program installs the Resource Tracker for parallel jobs with the engine components for WebSphere DataStage and WebSphere QualityStage. The Resource Tracker logs the processor, memory, and I/O usage on each computer that runs parallel jobs. You must do a custom installation to install the Resource Tracker. Component installer The component installer is a command line tool that adds or updates WebSphere DataStage components, such as plug-ins and stages.

Metadata repository tier


The logical tier for the metadata repository contains the metadata for IBM Information Server and can contain the analysis database for WebSphere Information Analyzer. The services for IBM Information Server are hosted by the application server and connect to the metadata repository to store and retrieve data.

Chapter 2. Planning for installation

The services tier must have access to the metadata repository tier. When a product module needs to store or retrieve metadata, services on the services tier connect to the metadata repository and manage the interaction between the repository and the product module. For WebSphere Information Analyzer, the engine and client tiers must also have direct access to the analysis database.

Services tier
The services tier includes IBM WebSphere Application Server (application server), services for IBM Information Server (both common and product-specific services), and the information center.

Services for IBM Information Server


These services manage metadata services, shared services, and repository services for the suite components that you install in a particular services tier. The services tier must have access to the metadata repository tier and the engine tier. An instance of WebSphere Application Server hosts these services. WebSphere Application Server is included with the suite. Alternatively, you can use an existing instance of a supported version of the application server.

IBM Information Server Web console


The Web console is installed as part of the services tier and consists of administration and reporting tools, and the following clients: v IBM WebSphere Business Glossary v IBM WebSphere Information Services Director v IBM Metadata Workbench The Web console has the following tabs: Administration tab In the Administration tab, administrators perform the following tasks: v Create users and authorize them to use components and features of IBM Information Server. v Set up an authentication scheme for users of IBM WebSphere DataStage and WebSphere QualityStage. v Create views of logged events. v Create views of scheduled tasks. Using the Administration tab, authorized users can access logging and scheduling views. Glossary tab From the glossary tab, you can work with WebSphere Business Glossary. You install WebSphere Business Glossary with the services tier. Information Services Catalog tab The Information Services Catalog tab contains information about deployed information services. You can integrate WebSphere Information Services Director Services Catalog with WebSphere Service Registry and Repository. WebSphere Service Registry and Repository is an IBM service registry where users

Planning, Installation, and Configuration Guide

manage and register services. With this integration, you can easily publish deployed WebSphere Information Services Director services to WebSphere Service Registry and Repository. Reporting tab The type of reports that are available to you vary according to the component that you work in. Each report corresponds to a task and displays information about the task. Reports can also display general information about the project that you work in.

Documentation for IBM Information Server, DB2 Database, and WebSphere Application Server
Documentation for IBM Information Server is available as an information center (online documents), PDF files, and context-sensitive help. Information centers for IBM DB2 Database and IBM WebSphere Application Server are also available. With an information center, you can search and browse online information. The following list describes what documentation is available and how to access it: IBM Information Server v Information center on the installation media The information center, which is automatically installed when you install the services tier, contains content for the product modules that you install. v Information center on the Web: publib.boulder.ibm.com/infocenter/ iisinfsv/v8r1/index.jsp This information center, which is available directly from the Web, contains documentation for the product modules. In addition, because the Web-based information center is updated from time to time, it contains the most up-to-date product documentation. v PDF files on the quick start media PDF files are available on the quick start media for IBM Information Server. In addition, if you choose Documentation in the installation program, PDF files are installed in the Documentation subdirectory of the IBM Information Server installation directory. By default location is: Microsoft Windows: C:\IBM\InformationServer\Documentation UNIX or Linux: /opt/IBM/InformationServer/Documentation DB2 Database Information center on the Web: publib.boulder.ibm.com/infocenter/ db2luw/v9/index.jsp You can access or download this information center directly from the Web. WebSphere Application Server Information center on the Web: publib.boulder.ibm.com/infocenter/ wasinfo/v6r0/topic/com.ibm.websphere.base.doc/info/welcome_base.html You can access or download this information center directly from the Web. After you use the IBM Information Server installation program to install the documentation, context-sensitive help and PDF files are available from each client. To open a PDF file, from Windows click Start IBM Information Server Documentation and then click the link for the PDF that you want to view.

Chapter 2. Planning for installation

Types of topologies
You install IBM Information Server and its product modules in a topology to fit your information integration and hardware needs. Use the same topology for your test and production environments to minimize issues when a job is deployed into production. Thus you can test your application in an environment that mirrors the production environment. This table describes the types of topologies by the number of computers for your installation, where additional clients can be on additional computers:
Table 3. Types of topologies and associated hardware Hardware in the topology One computer Tier mapping to hardware Engine, metadata repository, services, and clients all on one computer Notes A single computer with adequate resources is convenient for demonstrations and small-scale development. This one computer ideally is a server-class computer that must meet the system requirements, such as memory, disk space, and other requirements. Two computers Computer 1: engine, metadata repository, and services Computer 2 or more: one or more computers as clients High availability and failover are simpler to manage with all of the server components on a single computer, because the server components fail over all at one time. This topology also eliminates network latency between the services and metadata repository tiers when they are on the same server. Three computers Computer 1: engine Computer 2: metadata repository and services Computer 3 or more: one or more computers as clients The engine can require additional processing power for larger data integration jobs. The location of the engine on a different server prevents the engine from affecting the operations of the services and metadata repository. Failover configuration is more complex because of the increased number of failover scenarios with the engine separated from the metadata repository and services.

For all topologies, you can add clients and engines on additional computers. After you select a topology, ensure that you document your hardware environment.

10

Planning, Installation, and Configuration Guide

Grid environment for the engine


You can also install multiple engines across multiple computers to achieve a grid configuration. This configuration enables parallel jobs to use these multiple engines and to achieve increased scaling and performance. In the grid environment, each computer that hosts an engine must meet these requirements: v Use the same operating system and release level v Be connected and accessible within the same high-speed local area network v Be configured in the parallel configuration file For more information about the parallel engine configuration file, see the IBM WebSphere DataStage and QualityStage Parallel Job Developer Guide.

Topology example
To set up your installation, you first plan how you want to map the tiers to your hardware. This example shows a three-logical-tier mapping to three computers. The following diagram shows the installation of the tiers: v Computer A: Client tier v Computer B: Metadata repository tier, services tier (including IBM WebSphere Application Server), and the IBM WebSphere Information Analyzer database v Computer C: Engine tier and the IBM WebSphere QualityStage match database

Chapter 2. Planning for installation

11

Computer A

Client tier

Computer B
Services tier
Services for IBM Information Server

Computer C
Engine tier

IBM Information Server engine Common services Product-specific services Connectors Application server Service agents (Logging, Communication [ASB],
Job Monitor, PerfMon)

Packs

WebSphere QualityStage modules

Metadata repository tier

Analysis database

Match databases for WebSphere QualityStage

Data sources

Structured

Unstructured

Applications

Mainframe

Figure 2. Topology diagram of the architecture

You can install the client tier on more computers, as needed. Specifically, in order to perform information analysis, the WebSphere Information Analyzer client needs to communicate directly with the analysis database. For WebSphere QualityStage, the Match Designer needs to communicate directly with the match database scratch area.

Consider the installation methods: graphical wizard, console, or response file


You can choose to use the graphical wizard, the console, or a response file to install IBM Information Server. If your topology consists of multiple computers,

12

Planning, Installation, and Configuration Guide

you might choose to use the response file for some of them. Or, if you are unable to display a graphical interface when accessing a particular computer in your topology, you might choose to use the console method. Procedure Consider using any of the following installation methods: Graphical user interfaces: the graphical wizard A graphical user interface leads you step-by-step through the installation process. On UNIX and Linux, the computer on which you run the installation wizard must be able to display a graphical user interface, for example, by using the X Window System. Non-graphical installations: the console The installation program displays text prompts at the command line and records the installation options that you specify. After you specify the installation options, you can review a summary and then start the installation. Use this installation method if the computer on which you run the installation cannot display a graphical user interface. Silent installations: the response file You can create a response file that contains the installation options and then use that response file to perform the same installation on multiple computers. This type of installation is known as a silent installation. To create a response file, you can use the graphical wizard or console method.

Example
For example, several users need access to the IBM WebSphere DataStage and QualityStage Designer client. You can use a response file to expedite the installation of the client software on those multiple computers.

Step 3: Prepare disk, file, and network resources


Before installation, you must prepare your disk, volume group, and file system resources. Use the worksheet to document these resource preparations. For guidance about the values to use for this worksheet, see Setting up file systems and directories on page 16, Assessing your network and connectivity on page 20, and Capacity planning on page 22.
Table 4. Disk, volume, and file system worksheet Name IBM Information Server installation directory IBM WebSphere Application Server installation directory (services tier) Metadata repository installation directory (when installing DB2) Metadata repository database location (xmeta) IBM WebSphere Information Analyzer DBMS installation directory WebSphere Information Analyzer database location (iadb)
Chapter 2. Planning for installation

Volume

Path

13

Fill in the following worksheet with the information about your file systems:
Table 5. Planning worksheet for file systems Information needed Home directory for pre-created user IDs or the default location of the home directory for IDs that the install program creates Location of temporary storage for the installation program Location of installation directories Location of data set and scratch directories Record your information here Description Confirm that the Administrator or root ID used for the installation is able to write to these directories. If these directories are defined on mounted drives, authentication might not recognize the root ID as having write authority. Reserve extra space for the installation program to store temporary files as described in the system requirements. Plan for these directories on high-performance, shared file systems. Plan for these directories outside of the installation directory for IBM Information Server. Use local (internal) storage that is on a high-performance, shared file system with the same mount point that is available on all servers. For even better performance, create separate file systems for each data and scratch resource partition. For example, if the development and the production teams share an installation, separate each teams data and scratch directories on different file systems to completely isolate each environment. IBM WebSphere DataStage and IBM WebSphere QualityStage: Location of all application aspects except project data Plan for another directory structure for items such as secured parameter files, data set header files, custom components, schemas, SQL, shell scripts, custom job logs, and reports.

14

Planning, Installation, and Configuration Guide

Table 5. Planning worksheet for file systems (continued) Information needed Installation locations for the IBM Information Server components Record your information here Description UNIX and Linux: Do not install the components on the top-level mount point. Instead, install each component in a separate subdirectory within a mount point. The installation components change ownership and permissions of directories that you install, and not all mount points allow these changes, causing the installation to fail. Windows: Do not install on virtual drives (mapped or substituted drives). IBM DB2 installation: Date that you set and verified permissions for these file systems UNIX and Linux: The user who runs the installation program must have write access to file systems including /var and /usr/local/bin directories that are mounted from network file systems such as AFS or that are configured as read-only file systems. The user who runs the installation program must have write access to file systems including /var and /usr/local/bin directories. If these directories are on network mounted file systems, such as AFS, confirm that the installation user ID has access and that the file systems are not configured as read-only. Engine tier: Date that you set and verified permissions for these file systems UNIX and Linux: The dsadm account (administrator for the IBM Information Server engine) must have these permissions: Read and execute For everything under the /opt/IBM/ InformationServer directory Read For the /opt, /opt/IBM, and /opt/IBM/ InformationServer directories

Chapter 2. Planning for installation

15

Table 5. Planning worksheet for file systems (continued) Information needed Metadata repository: Date that you set and verified permissions for these file systems Record your information here Description UNIX and Linux: The DB2 database instance owner (db2inst1) must own the directories that store the metadata repository (xmeta) and the analysis database (iadb). By default, the installation program creates the database under the IBM Information Server installation directory. You can specify a different location. Windows: You can specify which drive the metadata repository (xmeta) and the analysis database (iadb) are stored on. Metadata repository and engine tiers: Date that you set and verified permissions for these file systems DB2 database, WebSphere Application Server, and IBM Information Server: Date that you verified the file systems UNIX and Linux: The user who runs the installation program must have read, write, and execute permissions to the /tmp directory or any location that the install -is:tempdir command specifies. Make sure that the installation directory is empty; otherwise, the following errors occur, based on your installation method: v Installation program: you receive an error message that directs you to switch to a different directory v Console: you receive an error message that directs you to switch to a different directory v Silent: installation fails immediately When you add product modules or components to an existing installation, the existing directory must be a working IBM Information Server installation that contains the appropriate tier or appropriate product installation structure. Cluster and grid environments: Date that you verified the shared mount point Share the installation file systems across all servers at the same mount point.

For information about disk space sizes, see the system requirements.

Setting up file systems and directories


As part of planning for your IBM Information Server installation, you set up the file systems and directories to hold the installation and the future growth of IBM Information Server. Prerequisites

16

Planning, Installation, and Configuration Guide

Before you make changes to your computers, back up those systems where you plan to install IBM Information Server. Procedure To set up file systems and directories: 1. Make the file systems expandable without requiring destruction or re-creation, if the operating system that you are installing on permits it. 2. Create a separate staging file system and directory structure for storing, managing, and archiving various source data files. 3. Plan for these file systems: Temporary directories Holds extracted installation program files. The installation program automatically removes these files when it finishes. When you install IBM Information Server, the installation program creates temporary files that the directory specifies by the TEMP environment variable. The temporary files are typically set to x:\Documents and Settings\user_name\Local Settings\temp directory, where user_name is the Microsoft Windows login name for the user performing the installation. The total number of characters in the temporary directory path and the path of the files that the installation program extracts into the path cannot exceed 256 characters. Long user names might cause the installation to fail.
Windows

To avoid exceeding the maximum path length, create a temporary directory, for example C:\tmp. Then, specify the directory as a temp directory by using the command install -is:tempdir c:\tmp when you start the installation program.
Linux UNIX The file system that contains the temporary directory used during installation must meet the system requirements for temporary space on its physical partition. On UNIX, you can run the following command to see the amount of available disk space, in megabytes, per file system. If the command results do not list the /tmp directory, use the amount on the root file system (/).

df -m

Software installation directories Holds the installed software: v IBM Information Server v Services tier (IBM WebSphere Application Server) v Metadata repository tier (IBM DB2) Database storage Holds the data for the operations of IBM Information Server. This data is separate and distinct from that of your actual data sources. v Metadata repository v Analysis database of IBM WebSphere Information Analyzer v Test results database for IBM WebSphere QualityStage Project directories (runtime shadow repository) for the IBM Information Server engine Holds these items: v Job executables
Chapter 2. Planning for installation

17

Compiled routines Buildop stage types Job runtime artifacts Job status records Cached versions of design objects Message handler files DSParams file for project-specific variables that the IBM WebSphere DataStage administrator defines v Files that the Hashed File stage creates for server jobs (default location). However, a best practice is to create the files for the Hashed File stage on a separate file system. v v v v v v v When a job is compiled, its source is extracted from the metadata repository and stored in the runtime repository to facilitate job compilation. WebSphere Information Analyzer creates its own project directory for use by information analysis operations like column analysis. Project directories can grow to contain thousands of files and subdirectories depending on the number of projects, jobs, and runtime metadata for each job.
Linux UNIX File system guidelines Use these guidelines for setting up the file system before you install: v Create projects in their own file system, because disk space typically is limited in the default directory within the installation file system. v For most operating systems, mount the file system at a level other than the root. Specifically, do not mount the file system in the / directory.

Data file storage Holds temporary and intermediate data files for the parallel engine: v Engine temporary storage (scratch, temp, and buffer) v IBM Information Server artifacts, such as surrogate key files v Segment files for parallel data sets v Staging and archival storage for possible source files After installation, you edit the parallel configuration files to assign resources, such as the disk and scratch file systems, to jobs at runtime. For high-availability failover environments, use a shared file system with the servers. For more information about the parallel engine configuration file, see the IBM WebSphere DataStage and QualityStage Parallel Job Developer Guide. 4. Isolate each storage class in its own separate file system to accommodate their different performance and capacity characteristics and backup requirements. The following table list default installation directories:

18

Planning, Installation, and Configuration Guide

Table 6. Default directory paths Component IBM Information Server Contents Engine, libraries, communication agents, Job Monitor, Resource Tracker, Java JRE, and uninstallation files WebSphere Application Server executable files, and libraries: Default directory path Linux, UNIX: /opt/IBM/ InformationServer/ Windows: C:\IBM\ InformationServer\ Linux, UNIX: /opt/IBM/ WebSphere/AppServer/

Services

v Shared services of IBM Information AIX: /usr/IBM/WebSphere/ Server AppServer/ v Product module-specific services Windows: C:\IBM\WebSphere\ AppServer\ Database server IBM DB2 database server executable files and libraries Metadata repository, analysis database, and test results database (no default directory) Linux, UNIX: /opt/IBM/db2/ Windows: C:\IBM\SQLLIB\ For new DB2 databases that IBM Information Server installs: v Linux, UNIX: /opt/IBM/ InformationServer/Repository v Windows: C:\DB2 For existing databases, the database administrator creates table spaces on an existing file system. Projects Project-related data Linux, UNIX: /opt/IBM/ InformationServer/Server/Projects Windows: C:\IBM\ InformationServer\Server\Projects Parallel engine Data sets for jobs and temporary storage (scratch) for sort and buffer overflows Linux, UNIX: v /opt/IBM/InformationServer/ Server/Datasets v /opt/IBM/InformationServer/ Server/Scratch Windows: v C:\IBM\InformationServer\ Server\Datasets v C:\IBM\InformationServer\ Server\Scratch InstallShield registry Critical information for future system maintenance, such as upgrades, patches, and uninstallation. Back up this directory after your installation is complete. AIX: /usr/lib/objrepos/ InstallShield/Universal/IBM/ InformationServer Linux: /root/InstallShield/ Universal/IBM/InformationServer Windows: C:\Program Files\Common Files\InstallShield\ Universal\IBM\InformationServer

Database storage

Chapter 2. Planning for installation

19

Assessing your network and connectivity


Before you install IBM Information Server, you must assess your network to ensure connectivity for high data volumes. Restrictions For performance reasons, do not install IBM Information Server in a wide area network (WAN) configuration because of the data exchanges that are required. Clients can work over a WAN if the latency is low. When the network latency increases, it has a detrimental effect on the clients. If the WAN has a higher latency, you can use the clients with Microsoft Windows Remote Desktop. Procedure To assess your network: 1. Ensure that a TCP/IP network is used for all communications in the installation. 2. Verify that the systems in the installation can resolve all the other server systems by both the short and long name, for example mycomputer.mydomain.com and mycomputer. Verify that both the short and long host names resolve to the same IP address. Also ensure that host name of the local host resolves to 127.0.0.1. Specifically, verify that you can resolve the IP addresses for both short and long host names of the following nodes: Repository node On the computer where the metadata repository tier is installed Service node On the computer where the services tier is installed On the computer where the engine tier is installed Engine node On the computer where the engine tier is installed On the computer where the services tier is installed 3. Ensure that you install the metadata repository and engine tiers in the same network segment. 4. For connectivity to data sources, see the vendor-supplied documentation for additional port assignments. 5. Open and make these TCP ports available through firewalls for IBM Information Server and the application server. Use the following tables as a reference: v The left column lists the component that resides within the tier. v The center column lists the default port number. The actual port number might differ. The installation program uses the next available port if the port that is specified cannot be used. v The right column lists the tiers that use the port to communicate to the tier that contains the component.
Table 7. Port numbers for IBM Information Server: metadata repository tier Metadata Repository Tier Component Default port numbers Access from the tier... Services

IBM DB2 database for the metadata 50000 repository (default)

20

Planning, Installation, and Configuration Guide

Table 7. Port numbers for IBM Information Server: metadata repository tier (continued) Metadata Repository Tier Component IBM DB2 database for the analysis database (default) Oracle database for the metadata repository This database is not the default database for the metadata repository. Oracle database for the analysis database This database is not the default database for the metadata repository. SQL Server database for the metadata repository This database is not the default database for the metadata repository. SQL Server database for the analysis database This database is not the default database for the metadata repository. Table 8. Port numbers for IBM Information Server: services tier Services Tier Component DHTML reports server IBM Information Server Web-based clients IBM Information Server Web-based clients - HTTPS WebSphere Application Server Administrative console (redirects to HTTPS) WebSphere Application Server Administrative console (HTTPS) IBM Information Server services (RMI/IIOP) IBM WebSphere Information Services Director services with JMS bindings*** Default port numbers 16581 9080 9443* 9060** Access from the tier... Client Services, Engine, Client Client Client 1433 Services, Engine, Client 1433 Services 1521 Services, Engine, Client Default port numbers 50000 1521 Access from the tier... Services, Engine, Client Services

9043* 2809, 9100, 94019403 7276, 7286, 5558, 5578

Client Services, Engine, Client

Chapter 2. Planning for installation

21

Table 8. Port numbers for IBM Information Server: services tier (continued) Services Tier Component * ** *** Default port numbers Access from the tier...

Used only when using HTTPS to access web clients. Used only if you need access to the WebSphere Application Server Administration console. Used only when publishing services using a JMS binding. The port needs to be accessible to services consumers.

Table 9. Port numbers for IBM Information Server: engine tier Engine Tier Component IBM Information Server ASB agent IBM Information Server logging agent IBM WebSphere DataStage and QualityStage services Parallel job monitors Parallel engine (APT_PM_STARTUP_PORT) Parallel engine remote process startup (rsh/ssh, multiple nodes only) Parallel engine (APT_PLAYER_CONNECTION_PORT, multiple nodes only) * Default port numbers 31531, and a random port number greater than 1024* 31533 31538 13400 (port 1) and 13401 (port 2) multiple ports, uses a port number of 10000 or greater 22514 multiple ports, uses a port number of 11000 or greater Access from the tier... Services Engine Engine, Client Engine** Engine Engine Engine

Can be fixed to a specific port by specifying agent.objectport=# in 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. 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 IBM WebSphere DataStage and QualityStage server is installed, if that node is different from the conductor node.

**

Capacity planning
You plan the use of disk, volume group, and file system resources to create an optimal system for IBM Information Server. As part of your capacity planning for your installation, you must size your file systems and databases to accommodate a growing amount of business data and metadata. After the installation, you must continue to monitor these sizes over time to ensure that sufficient space is available. A maintenance and backup plan helps to ensure sufficient space is available for the data. Attention: If the file system runs out of space, IBM Information Server stops functioning properly.

RAID and SAN configurations


Ultimate performance of a job (for IBM WebSphere DataStage, IBM WebSphere QualityStage, and IBM WebSphere Information Analyzer) depends on all

22

Planning, Installation, and Configuration Guide

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 tuned optimally v Ensure that computers where you install the metadata repository tier and the services tier are on high speed network. v Minimize contention between temporary (scratch, buffer, and sort) and data file systems. v Minimize contention between the disks and controllers that are associated with IBM 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 expertise from hardware, storage, operating system, and application (IBM Information Server) personnel. v Remember that previous experience in designing I/O systems for nonparallel engines might lead to non-optimal configurations for IBM Information Server. The optimal disk configuration strikes a balance among cost, complexity, ease of administration, and ultimate performance.

Project naming conventions


As you plan for your installation of IBM Information Server, you document how your projects must be named. IBM WebSphere DataStage, IBM WebSphere QualityStage, and IBM WebSphere Information Analyzer store jobs, analysis, and logs in these projects. You need to choose the name of one IBM WebSphere 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:
Chapter 2. Planning for installation

23

dev it uat prod

Development Integration test User acceptance test Production

Step 4: Modify kernel parameters and user limits (Linux, UNIX)


Modify the kernel parameters and user limits and restart your system before you start the installation program. The kernel parameter and user limit requirements are minimum requirements for IBM Information Server. The optimal value for each parameter might be higher depending on the topology of your installation and the operational data load. These factors vary widely from system to system. 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 system before you install IBM Information Server.

Kernel parameters for the services tier


You can find system tuning information for IBM WebSphere Application Server in the documentation for that product: v WebSphere Application Server 6.0 information center: Preparing the operating system for product installation

DB2 kernel parameters for metadata repository tier


The minimum metadata repository kernel parameter requirements apply only to IBM DB2 database installations. Before you install IBM DB2 as part of IBM Information Server, ensure that your system meets the kernel parameter requirements for DB2. If you use another database for your metadata repository, consult the kernel parameter requirements for your configuration. You can find kernel parameter requirements for IBM DB2 in the documentation for that product. You can find the kernel parameter requirements for IBM DB2 in the DB2 9.5 documentation: v DB2 9.5 information center: Kernel parameters (Linux) v DB2 9.5 information center: OS user limit requirements (Linux and UNIX) For DB2 v9.1 kernel parameter requirements, see the IBM DB2 Database for Linux, UNIX, and Windows Information Center at http://publib.boulder.ibm.com/ infocenter/db2luw/v9/topic/com.ibm.db2.udb.doc/welcome.html. Ensure that your system meets the kernel parameter requirements for DB2. When the DB2 kernel requirements are different from the IBM Information Server kernel parameter requirements, use the largest minimum value. The following table contains the minimum kernel parameters for the metadata repository tier on DB2:

24

Planning, Installation, and Configuration Guide

Table 10. Minimum Linux kernel parameters and user limits for the metadata repository tier on DB2 Parameter MSGMAX MSGMNB MSGMNI SEMMNI SEMMNS SEMMSL SEMOPM SHMALL SHMMAX Metadata repository tier 65536 65536 1024 1024 256000 250 32 8388608 KB v 32bit: 32768 KB v 64bit: 1073741824 KB SHMMNI 4096

Minimum AIX kernel parameters and user limits


The following table contains the minimum kernel parameters and user limits for the installation:
Table 11. Minimum AIX kernel parameters and user limits Parameter SHMMAX SHMMNI SHMSEG MAXUPROC NOFILES Engine tier 536870912 2000 200 200 1000 Services tier No requirement No requirement No requirement 1000 or unlimited 10000

Minimum Linux kernel parameters and user limits


The following table contains the minimum kernel parameters and user limits for the installation:
Table 12. Minimum Linux kernel parameters and user limits Parameter MSGMAX MSGMNB MSGMNI SEMMNI SEMMNS SEMMSL SEMOPM SHMALL SHMMAX SHMMNI Engine tier 8192 16384 No requirement 1024 128000 250 32 No requirement 307200000 2000 Services tier No requirement No requirement No requirement No requirement No requirement No requirement No requirement 2511724800 2511724800 No requirement
Chapter 2. Planning for installation

25

Table 12. Minimum Linux kernel parameters and user limits (continued) Parameter SHMSEG rlim_fd_max rlim_fd_cur MAXUPROC NOFILES Engine tier 200 No requirement No requirement 200 1000 Services tier No requirement Greater than or equal to 8193 Greater than or equal to 8193 1000 or unlimited 10000

Step 5: Set up users for installation


Before installing IBM Information Server, you set up the users for your installation. Restrictions Create the accounts for DB2 manually, before the installation, to ensure that operating system policies, such as requiring a password change on first login, do not interfere with the installation programs ability to use them. Activate each DB2 account by logging in. Some systems are set up to force a password change during the first login, therefore a manual login is required to activate the accounts properly. The following restrictions apply to the names you choose for user IDs and passwords. All user IDs and passwords The following characters are not permitted: $ (dollar sign) ! (exclamation point) % (percentage sign) (blank space) Internal user registry user IDs Only alphanumeric characters and the following characters are permitted: _ (underscore) - (dash) , (comma) \ (backslash) = (equal sign) . (period) : (colon) Spaces IBM DB2 database user names v You can use these characters in IDs: A through Z 0 through 9 # (number sign) Linux and UNIX user names and passwords cannot start with a numeric digit. v You cannot begin a user ID with these characters:

26

Planning, Installation, and Configuration Guide

SQL SYS IBM v You 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 UNIX and Linux 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: UNIX and Linux: 8 Windows: 14 About this task When you install IBM Information Server, the installation program creates an internal registry within IBM Information Server. This internal registry stores user IDs and passwords within IBM Information Server for authentication. The installation program does not create these users on the operating system level. After you install IBM Information Server, you can change to an external user registry or configure an LDAP-compliant user registry. The installation program creates these user accounts in the internal registry:
Table 13. Administrator accounts set up by the installation program Account description Administrator for IBM WebSphere Application Server Administrator for IBM Information Server To tighten security and avoid administration issues, make this account different from the WebSphere administrator. Default user name wasadmin isadmin Record the password

While you create the user accounts, record the name and password for each user. Then specify each name and password when the installation program prompts you for that information. Procedure To set up users and registries for the installation:

Chapter 2. Planning for installation

27

1. On the operating systems where you install IBM Information Server, ensure that the user who installs IBM Information Server is logged in using these accounts: v On UNIX and Linux, the root user account v On Windows, a user account in the local Administrators group. The account must have read and write access to the installation directories. A member of the domain administrator group can run the installation program only if that administrator also has local administrator group privileges. 2. On the operating systems where you install the engine, the metadata repository, and the services, create these additional accounts and record the passwords:
Table 14. Accounts that you create Account description DB2 administration server Default user name Linux, UNIX: dasusr1 Windows: db2admin Linux, UNIX: db2inst1 Windows: db2admin DB2 fenced user on Linux and UNIX Owner of the metadata repository db2fenc1 db2fadm1 Record the password Secondary Primary group group Linux, UNIX: dasadm1 Windows: db2admns and Administrators Linux, UNIX: db2iadm1 Linux, UNIX: dasadm1 Windows: None None Metadata repository tier Metadata repository tier Metadata repository tier None Location for account Metadata repository tier Notes DB2 database only, operating system account

DB2 instance owner

DB2 database only, operating system account

DB2 database only, operating system account DB2 database only, operating system account. When you use the DB2 database for the repository, the DB2 database uses the authentication for the operating system for connection requests.

xmeta

xmeta

None

28

Planning, Installation, and Configuration Guide

Table 14. Accounts that you create (continued) Account description Administrator for the IBM Information Server engine Default user name dsadm Record the password Secondary Primary group group dstage Location for account Notes This user performs administrative tasks, such as adding new projects and defining their properties. Instead of running jobs under this account, create a user with the developer role. DB2 database only, operating system account. DB2 database uses the authentication for the operating system.

You customize Engine tier this group to apply to your security model.

WebSphere Information Analyzer: owner of the analysis database

iauser

iauser

None

Engine tier or metadata repository tier

In addition to requiring root access, on UNIX and Linux the DB2 installation program must have write permissions for several file systems, such as /var and /usr/local/bin. This requirement might not be met when the directories are mounted from network file systems such as AFS. 3. Log into each account to confirm that it functions properly.

Example
These sample UNIX commands create some of the user accounts and groups:
groupadd groupadd groupadd groupadd useradd useradd useradd useradd useradd useradd db2iadm1 db2fadm1 dasadm1 dstage -gdb2fadm1 -pPa55w0rd -m -d /home/db2fenc1 db2fenc1 -gdb2iadm1 -Gdasadm1 -pPa55w0rd -m -d /home/db2inst1 db2inst1 -gdasadm1 -pPa55w0rd -m -d /home/dasusr1 dasusr1 -gdstage -pPa55w0rd -m -d /home/dsadm dsadm -pPa55w0rd -m -d /home/iauser iauser -pPa55w0rd -m -d /home/xmeta xmeta

The following items require additional configuration for users and registries: v During the installation, use the user names and passwords from this task. v Optional: After installation, change to an external user registry or configure an LDAP-compliant user registry. See the information about Configuring WebSphere security for local operating system user registries in the IBM Information Server Administration Guide.

Chapter 2. Planning for installation

29

Step 6: Select an application server


In the services tier, you can install IBM WebSphere Application Server (the application server) as part of the IBM Information Server installation or use an existing installation of the application server. The easier method is to install a new application server during the IBM Information Server installation. Depending on your usage of IBM Information Server and whether your operating system supports both versions, either the 32-bit or the 64-bit version of the application server might be more appropriate as you plan for your longer term performance and number of users. For 64-bit Linux, install the 64-bit version of the application server before you install IBM Information Server. For other 64-bit UNIX platforms, you can choose to install the 32-bit or 64-bit WebSphere Application Server. For installation instructions, see the product documentation for the application server. After you install the 64-bit application server, verify that you have the correct versions of the application server and the Java SDK with these commands:
/opt/IBM/WebSphere/AppServer64/bin/versionInfo.sh /opt/IBM/WebSphere/AppServer64/java/bin/java -version

New application server


If you install the application server as part of the IBM Information Server installation, the installation program creates a server profile that is named default and an application server instance that is named server1. This application server is licensed for use only with IBM Information Server.

Existing application server


To use an existing application server, you must use the stand-alone version of WebSphere Application Server (not WebSphere Network Deployment or WebSphere Extended Deployment). Also before you start the IBM Information Server installation program, create a new application server profile. That profile must contain a server that is named server1 with the security disabled. The IBM Information Server installation program enables security as part of its configuration. For information about creating a profile, see the WebSphere Application Server information center at publib.boulder.ibm.com/infocenter/wasinfo/v6r0/ index.jsp?topic=/com.ibm.websphere.base.doc/info/welcome_base.html.

Preparing the 64-bit application server (Red Hat)


Before you install IBM Information Server on a 64-bit Red Hat system, you must install the 64-bit version of IBM WebSphere Application Server. Prerequisites Obtain the required files for WebSphere Application Server, its updates, and fix packs from Passport Advantage. The prereqChecker.xml and prereqChecker.dtd files are available from this site: http://www.ibm.com/support/docview.wss?rs=180&context=SSEQTP &q1=rhel5cert&uid=swg21266724&loc=en_US&cs=utf-8&lang=en

30

Planning, Installation, and Configuration Guide

Disable your firewall and antivirus software to avoid possible installation problems. If SELinux is enabled, disable it before installing WebSphere Application Server. For more information on how to disable SELinux, see the Red Hat Enterprise Linux Deployment Guide. Procedure To prepare the 64-bit application server: 1. Install WebSphere Application Server, Version 6.0.1 (part# C828NML): a. Place the uncompressed installation files in a temporary directory. b. Copy the prereqChecker.xml and prereqChecker.dtd files into the temporary directory. c. Run the installation command including the XML file:
./install -W oslevelcheckactionInstallWizardBean.configFilePath="prereqChecker.xml"

For detailed installation instructions, see the WebSphere Application Server documentation. 2. Upgrade the application server to Version 6.0.2. Detailed instructions are available at http://www.ibm.com/support/docview.wss?rs=180 &uid=swg27006336#steps. a. Obtain the refresh package (6.0-WS-WAS-LinucX64-RP000002.tar ). b. Place the uncompressed installation files in the /opt/IBM/WebSphere/ AppServer directory. c. Stop all WebSphere processes: /opt/IBM/WebSphere/AppServer/bin/stopServer.sh server1 /opt/IBM/WebSphere/AppServer/java/bin/java /opt/IBM/WebSphere/AppServer/java/jre/bin/java d. From the updateinstaller directory, run the update command:
./update

3. Install the Update Installer, Version 6.1.0.17 for the application server: a. Obtain the update installer package (download.updii.61017.linux.amd64.zip). b. Place the uncompressed installation files in a temporary directory. c. From the UpdateInstaller directory, run the installation command:
./install

The Update Installer is created in the /opt/IBM/WebSphere/ UpdateInstaller directory. 4. Use the Update Installer to install the Java SDK for the application server. Detailed instructions are available at http://www-1.ibm.com/support/ docview.wss?rs=180&uid=swg24018618. a. Obtain the update installer package (6.0.2-WS-WASJavaSDK-LinuxX64FP00000027.pak). b. Stop the application server processes as described previously. c. From the /opt/IBM/WebSphere/UpdateInstaller directory, run the installation command:
./update.sh

d. Specify the Java SDK as the available maintenance package to install.

Chapter 2. Planning for installation

31

5. Use the Update Installer to install the fix pack for the application server. Detailed instructions are available at http://www-1.ibm.com/support/ docview.wss?rs=180&uid=swg24018618. a. Obtain the update installer package (6.0.2-WS-WAS-LinuxX64FP00000027.pak). b. Stop the application server processes as described previously. c. From the /opt/IBM/WebSphere/UpdateInstaller directory, run the installation command:
./update.sh

d. Specify the fix pack as the available maintenance package to install. 6. Verify the installed versions. The following command should display Version 6.0.2.27.
/opt/IBM/WebSphere/AppServer64/bin/versionInfo.sh

The following command should display 1.4.2 IBM build caix64142-20080515 (SR11).
/opt/IBM/WebSphere/AppServer64/java/bin/java -version

Step 7: Select a location for the metadata repository


Before installation, you must decide the locations for your metadata repository. Create the metadata repository using one of the following methods: v The installation wizard installs a new IBM DB2 database system and creates a new metadata repository. v The installation wizard refers to an existing local DB2 database system and creates the metadata repository in it. v The installation wizard refers to an existing local or database system and a uses a manually created metadata repository. Also, the computer where you install the services tier must be able to access the metadata repository. By default, the database name of the metadata repository is xmeta. If you are installing WebSphere Information Analyzer, the engine and client tiers must be able to access the analysis database. By default, the database name of the analysis database is iadb.

New local DB2 server and database


You use the IBM Information Server installation program to install the metadata repository tier. When you install this tier, you install the DB2 database system (or reuse an existing local DB2 installation), create the database for the metadata repository, and create the required users (if needed). Note: To reuse an existing DB2 installation on Linux and UNIX, you must use DB2 Fault Monitoring components that require the fault monitor entry in the /etc/inittab file.

Existing local DB2 server and new database


If you choose to use an existing DB2 installation, it must not be set up as a partitioned database environment. This type of environment and the fast communications manager (FCM) are not supported for use with IBM Information Server.

32

Planning, Installation, and Configuration Guide

When installing DB2, the installation program installs DB2 Version 9.5. DB2 9.5 is only supported on 64-bit Linux systems. On 32-bit Linux systems you must pre-install the 32-bit version of DB2 Version 9.1 before installing IBM Information Server.

Manually created Oracle, Microsoft SQL Server, or DB2 database


Alternatively, you manually create the database for the metadata repository and the required users for these databases. During the installation process, do not select the Metadata Repository tier. The installation program will prompt you for the database connection information. You must meet these prerequisites to use an existing database: v Before you install IBM Information Server, you create the database for the metadata repository and for any users that are needed. v You establish database connectivity from the services tier to the database for the metadata repository. v For DB2 instances, the database cannot be partitioned. v For Oracle instances, Oracle Real Application Clusters (Oracle RAC) are not supported

Installation options for DB2 Version 9.1 versus 9.5


For the metadata repository and analysis database, you can choose to use either IBM DB2 Version 9.1 or Version 9.5.

Installing the DB2 database system as part of a new installation of IBM Information Server or upgrading from DataStage or QualityStage, Version 7.5.x or earlier
If you install the DB2 database system, you can install either Version 9.5 or Version 9.1. The IBM Information Server installation program can install DB2 Version 9.5 when the operating system supports this version. On operating systems where DB2 Version 9.5 is not supported, you must install DB2 Version 9.1 separately before you install IBM Information Server. You might also choose to install DB2 Version 9.1 if your organization standardized on this version.

Using an existing installation of the DB2 database system with a new installation of IBM Information Server or upgrading from DataStage or QualityStage, Version 7.5.x or earlier
If you already have an installation of DB2 Version 9.5 or Version 9.1, you can use this installation by specifying database connection information during the installation of IBM Information Server. In this case, do not select the Metadata Repository tier.

Using DB2 Version 9.5 when upgrading from IBM Information Server, Version 8.0.1
If you upgrade from IBM Information Server, Version 8.0.1 and you currently use DB2 Version 9.1, you can choose to continue using DB2 Version 9.1 or upgrade to DB2 Version 9.5. If you choose to upgrade to DB2 Version 9.5, first upgrade IBM Information Server to Version 8.1 before you upgrade DB2. You can acquire the installation media for DB2 Version 9.5 through your IBM Information Server license.
Chapter 2. Planning for installation

33

Once you have upgraded to DB2 Version 9.5, you must reconfigure the database and database instance.

Manually creating a DB2 database for the metadata repository


To use an existing installation of IBM DB2, you run a script to create the metadata repository database before you install IBM Information Server. Prerequisites The existing instance of DB2 must be on a computer that is accessible by the computers where you install the services and the engine tiers. If the metadata repository also includes the analysis database, the computer that hosts DB2 must also be accessible to clients. Procedure Refer to the appropriate Readme file in the DatabaseSupport directory of the IBM Information Server installation media for more details on how to create a DB2 database for the metadata repository.

Creating an Oracle tablespace for the metadata repository


To use an Oracle database for the metadata repository, you run a script that creates a tablespace and owner for the metadata repository. You must create the database before you install IBM Information Server. Prerequisites The Oracle database must be on a computer that is accessible by the computers where you install the services and the engine tiers. If the metadata repository also includes the analysis database, the computer that hosts the Oracle database must also be accessible to clients. Procedure Refer to the appropriate Readme file in the DatabaseSupport directory of the IBM Information Server installation media for more details on how to create an Oracle tablespace for the metadata repository.

Creating a Microsoft SQL Server database for the metadata repository


To use Microsoft SQL Server for the metadata repository, you run a script to create the database. You must create the database before you install IBM Information Server. Prerequisites The Microsoft SQL Server database must be on a computer that is accessible by the computers where you install the services and the engine tiers. If the metadata repository also includes the analysis database, the computer that hosts Microsoft SQL Server must also be accessible to clients. Procedure

34

Planning, Installation, and Configuration Guide

Refer to the appropriate Readme file in the DatabaseSupport directory of the IBM Information Server installation media for more details on how to create a Microsoft SQL Server database for the metadata repository.

Step 8: Prepare for your products


Based on the product modules that you want to install, complete these planning activities. For additional requirements and preinstallation steps, see the documentation for your specific product modules.

Accessing the license file


The .xml license file controls which product modules you can install, which features are available in each client, and whether a client can connect to the services for IBM Information Server. About this task When you install the services tier, you must specify the location of a license file. When you install additional product modules, the installation program reads the license information that is stored at services tier. If you later obtain additional products, you must obtain a new license file and upload the file to the services tier. The license file controls which features are enabled in the clients. For example, if you have a license for IBM WebSphere Information Analyzer, after you install the client and start the IBM Information Server console, the user interface that you use to analyze data is available. For a client to connect to a services tier, the services that correspond to the client must be installed and licensed for that services tier. You must obtain a license file before you start the installation. Procedure To access the license file: 1. Obtain your license file from your IBM Sales Administrator or directly through the IBM Information Server License Key Portal as described in your product Proof Of Entitlement. 2. Before you install the suite, ensure that the computer where you perform the installation can access the license file. After you install the suite, the license information is stored at the services tier, and the original .xml file is no longer used. 3. After you install the suite, use the IBM Information Server Web console to update the license.

ODBC drivers for WebSphere DataStage and WebSphere QualityStage


ODBC drivers for IBM WebSphere DataStage and IBM WebSphere QualityStage are installed with the clients or engine. The DataDirect Technologies Connect ODBC drivers for WebSphere DataStage and WebSphere QualityStage are installed in the ODBCDrivers subdirectory of your installation. The default path is InformationServer\ODBCDrivers. Documentation for configuring the ODBC drivers is available from this directory by default.

Chapter 2. Planning for installation

35

WebSphere QualityStage Match Designer


The IBM WebSphere QualityStage Match Designer is a component of IBM WebSphere QualityStage that is used to design and test match specifications, which consist of match passes that identify duplicate entities within 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. The Match Designer database can be hosted by the following database systems: v IBM DB2, which you can choose to install during the IBM Information Server installation v Oracle v Microsoft SQL Server

Database requirements
The IBM Information Server installation 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 also create the database on the client or engine tier or on any system 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 15. 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 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 UTF-8. Note: If you use the IBM Wire Protocol driver, select the Enable N-CHAR Support option. Microsoft SQL Server database No special settings are required.

IBM DB2 database

36

Planning, Installation, and Configuration Guide

Database space requirements


After you create the database, use automatic storage management to allocate database space as needed. 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 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 will be preprocessed through a 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 16. Space requirement factors and calculations Factor Match specification count Description Calculation

Match specifications define Approximate number of and test criteria for matching match specifications you data. expect to retain in your database. 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. 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

Chapter 2. Planning for installation

37

Table 16. 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) Calculation Average number of bytes per match specification input data record (used in the Match Size calculation)

Match size aggregates the (Match pass count) x (data match pass and data record record count) x (data record count and length factors into length) the estimated space requirements for the data component of a single match specification. 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. Average number of frequency records per match specification

Frequency record count

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

WebSphere Information Analyzer


The analysis database is a component of IBM Information Server that IBM WebSphere Information Analyzer uses when it runs analysis jobs. By default, the installation program can create this database in a new DB2 database system.

38

Planning, Installation, and Configuration Guide

The extended analysis information is stored in the analysis database. The extended analysis information includes the high-volume, detailed analysis results, such as column analysis, primary key analysis, and domain analysis. Before you create the analysis database, you review the quantity of data to be analyzed. This review helps you to determine an appropriate storage size, location, and configuration of the analysis database. After IBM Information Server is installed, an administrator configures the analysis settings for the engine and the analysis database. On the server where the engine is installed, you must configure ODBC connections to the analysis database and to the data source before you perform any analysis work.

Location of the analysis database


The analysis database can be in a number of different configurations relative to other components of IBM Information Server: v The analysis database and the metadata repository are in the same database server installation as distinct databases. This topology is the default. v The analysis database and the metadata repository are in different database server installations: for example, one is in the IBM DB2 database system and the other in Microsoft SQL Server. Additionally, you must configure an ODBC data source name (DSN) connection to the database by using an IBM DataDirect driver. Furthermore, the analysis database, the engine, and the source database can be on the same server or on different servers. If they are on different servers, a number of configurations are possible, for example: v The analysis database and the source database are on one server, and the engine is on a different server. v The analysis database and the engine are on one server, and the source database is on a different server. The analysis database is empty upon creation; no tables are created in it by the installation process. All the tables, indexes, and stored procedures in the analysis database are dynamically created at runtime during analysis processing. By default, the analysis database is accessible to all authorized WebSphere Information Analyzer users. The default name of the analysis database is iadb.

Type of database vendor


You put the analysis database in one of these database systems: v In a new DB2 database system that the installation program creates for you v In an existing local DB2 database system where the installation program automatically creates the database for the analysis database v In an existing database system where you reuse an existing analysis database v In an existing database system where you manually create the analysis database You can use either DB2 Version 9.1 or DB2 Version 9.5 for the analysis database. The installation options for a DB2 analysis database are the same as the ones for the metadata repository.

Chapter 2. Planning for installation

39

If you want to use the Microsoft SQL Server or Oracle databases, you must install and configure them before you install IBM Information Server. For these database types, you must manually create the analysis database by using the scripts. The scripts are in the DatabaseSupport directory in the extracted installation image. For usage details, see the readme files in the same directory.

Size of the database


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

40

Planning, Installation, and Configuration Guide

Chapter 3. Installing, upgrading, and applying updates


You can install, upgrade, or update IBM Information Server depending on whether you want to create a new installation, upgrade from a previous release, or update an existing release with a patch or fix pack.

Creating a new installation of IBM Information Server


Use this checklist to guide you through creating a new installation or adding product components to an existing Version 8.1 installation. Prerequisites 1. Read and complete the planning steps. 2. Before you attempt a new installation of IBM Information Server, back up all of the critical data on your system. If you are adding an additional product module, back up your current IBM Information Server components and critical data. Also, back up the following items:
Linux UNIX

Back up /etc/services, /etc/inittab, /etc/passwd, and /etc/group.


Windows

Back up the Windows registry and the C:\Windows\System32\ drivers\etc directory. Failures during installation or upgrade might result in the installation being left in a non-operational state. 3. Save the XML license file that you received with your purchase onto a file system that is accessible to the installation program. 4.
Windows If MKS Toolkit is already installed on your system, you must uninstall it before you run the IBM Information Server installation program. MKS Toolkit 9.1P1 is installed as part of IBM Information Server. If an existing, earlier version of MKS Toolkit is present on the system, the IBM Information Server installation program attempts to upgrade the installation to MKS Toolkit 9.1P1. Depending on the state of your existing MKS Toolkit installation, the upgrade might not succeed, and the IBM Information Server installation might fail or unexpected errors might occur when you use IBM Information Server. In a non-English environment, the installation program uses the system locale setting. Refer to the supported encodings to determine if your locale is supported. If it is not listed, English will be installed, but with national language support enabled. If you are installing IBM Information Server and using Microsoft SQL, Oracle, or a remote DB2 for the repository, then do not select the Metadata Repository layer when installing Information Server. If you plan to use an existing database as your metadata repository, ensure that the computer where you install the services tier has network connectivity. Access the installation media from a local file system or optical drive. The installation program requires uninterrupted connectivity to the installation media. Even a momentary interruption in connectivity might cause the installation to fail. The best practice is to copy the contents of the installation media to a local file system and run the installation program from there.

5.

6.

7. 8.

Copyright IBM Corp. 2005, 2008

41

9. Disable firewall software and antivirus software during the installation session. Some antivirus software blocks the installation program and network operations from running or prompts for a confirmation. These actions interfere with the installation program and might cause a silent installation to fail. 10.
Linux If SELinux is enabled on the Red Hat Enterprise operating system, disable it before installing IBM Information Server. For more information on how to disable SELinux, see the Red Hat Enterprise Linux Deployment Guide.

About this task Run the installation program on each computer that will host the IBM Information Server tiers for your chosen installation topology. If you install on two or more computers, you must install the tiers in the following order: 1. Metadata repository 2. Services 3. Engine You can install the client tier at any time. If you install multiple tiers on the same computer, install them all at the same time within the same installation session. Procedure To create a new installation: 1. Optional: Set the JITC_COMPILEOPT and IBM_MIXED_MODE_THRESHOLD environment variables as shown to improve installation program performance.
AIX

export JITC_COMPILEOPT=NALL export IBM_MIXED_MODE_THRESHOLD=100

2. Log on as an administrator.
Linux UNIX

Log on as the root user or as a user with root privileges.


Windows

Log on as a local administrator or as a domain administrator with local administrator privileges. 3. 4. 5.


Linux UNIX Open a command prompt or shell window and change to the directory location of the installation image. Linux UNIX

Set the file creation mask to 022:

umask 022

Ensure that you have enough system resources allocated for the installation. Set the file descriptor limit to 102400, a higher value, or unlimited. For example:
Linux UNIX

ulimit -n unlimited

Also, check the current setting for the NOFILES kernel parameter. This parameter must be set to a value that is at least equal to the value that you specify for ulimit. 6.
Linux

Ensure that the lockd daemon is running.

ps -ef | grep -i lockd

42

Planning, Installation, and Configuration Guide

If it is not running, refer to your operating system documentation for the preferred method of starting daemon services such as this. 7. Start the installation program. You can run the installation program as a wizard, or to run it without a graphical interface you can run it in console or silent mode. 8. When the installation program prompts you to select the tiers to install, refer to the table of topologies. 9. When the installation program prompts you to select the products to install, always select all of the products that you want to install. Many products have components that must be installed on one or more tiers; therefore, you will be asked to select the products multiple times. Attention: When installing the client tier on the same computer as the services tier, carefully review the selected products to ensure that your license includes the selected products. If a product is listed with Client only, not licensed, then your license does not include that product and it will not be installed on the services tier.
Table 17. Products and the tiers on which they must be installed. Product or component IBM Information Server FastTrack IBM Information Server Manager IBM Metadata Workbench IBM WebSphere Business Glossary IBM Information Server Business Glossary Anywhere (requires WebSphere Business Glossary)* Tiers on which to install Services, Client Services, Engine, Client Services, Engine Services Services

IBM WebSphere DataStage and QualityStage Services, Engine, Client IBM WebSphere Information Analyzer IBM WebSphere Information Services Director IBM WebSphere Metadata Server
*

Metadata repository, Services, Engine, Client Services, Engine, Client Metadata repository, Services

The client is installed separately.

10. Install the metadata repository tier if you are using the DB2 database that is installed as part of the IBM Information Server installation program or a local preexisting installation of the DB2 server. If the you are using a remote installation of DB2 or using Oracle or Microsoft SQL Server for the metadata repository database, do not install the metadata repository tier.
Linux UNIX When the installation program prompts you for an installation location for IBM Information Server, or the DB2 server, ensure that the specified directories are writable and have enough disk space as stated in the system requirements. Also confirm that IBM Information Server , WebSphere Application Server, and the DB2 server are each installed in a separate directory. 12. When the installation program prompts you for user information, use the user IDs and passwords that you created during the planning tasks. 13. If the installation program prompts you for WebSphere DataStage projects, you must add at least one project. 14. For the English version of the installation program, determine if you want to enable national language support. Leave the Install NLS for WebSphere DataStage server option selected, unless you are certain that your server will

11.

Chapter 3. Installing, upgrading, and applying updates

43

never process non-ASCII characters, such as accented Latin characters or extended ASCII punctuation characters. And, certain packs require national language support. This option cannot be changed after IBM Information Server is installed. In a non-English environment, the installation program enables national language support automatically. 15. Click Install to begin the installation. After a successful installation, a zip file that contains installation log files is saved to the IBM Information Server installation directory. This file is named isdump-operating_systemsystem_timestamp.zip. 16. Repeat the process for each computer in your installation topology. When the installation completes, you start the IBM Information Server console and configure the required users. If the installation fails: 1. View the installation logs for more information. The ISInstall-timestamp.log file is available in the temporary directory. 2. Resolve any issues that are listed in the installation log file. 3. Remove the installation directory structure and the installation log file. 4.
Windows

Restart the computer.

5. Run the installation program again.

Launching the installation program by using the installation wizard


The installation wizard provides a graphical interface that leads you step-by-step through the process of installing IBM Information Server. About this task The wizard presents you with installation choices. v You can install IBM Information Server and create a response file that contains your choices v You can run the installation wizard and save your choices in a response file. The second choice does not install IBM Information Server on the computer. It only provides a response file that you can use to later perform the actual installation. Note that passwords are not saved in the response file; you must edit the file to add the passwords. Procedure To launch the installation program as a wizard: v Enter this command:
Linux UNIX

./install -is:tempdir temp_directory_path


Windows

install -is:tempdir temp_directory_path

The temporary directory argument is optional. If not specified, the default system temporary directory is used. Ensure, however, that the disk volume or drive that contains the temporary directory contains sufficient available disk

44

Planning, Installation, and Configuration Guide

space and that the path to the directory does not exceed 256 characters. Also, ensure that the temporary directory is writable by the DB2 instance owner. v If you are not concerned about the amount of temporary disk space or the length of the path to the default temporary directory, then, in Windows, double-click the installation program; in Linux or UNIX, enter ./install.

Launching the installation program from the command prompt (silent or console)
You can install IBM Information Server without launching the graphic interface. The two alternate installation methods are silent and console. About this task The console method is useful if you want to interact with the installation program but you do not have a system capable of displaying the graphic interface (for example, if you are accessing the system remotely in a secure shell). Alternatively, the silent method is useful if you access the systems remotely. In each of the following command examples, the specified temporary directory argument is optional and the default system temporary directory is otherwise used. Ensure, however, that the disk volume that contains the temporary directory contains sufficient available disk space. Procedure To launch the installation program from a command prompt: v Console method: 1. Run the installation program with the -console parameter.
install -is:tempdir temp_directory_path -console

v Silent method: 1. Create a response file by running the installation program in GUI or console mode. As an alternative, you can use one of the templates that are on your installation media. The response file does not contain the password information; therefore, you must edit the response file and add the passwords before proceeding. Using the installation wizard to create a response file and install the product locally: Run the installation program in graphic or console mode. On the Installation and Response File Selection panel, select Save the installation settings in a response file. No software will be installed on this computer. Using a response file template located on the installation media Refer to the Response file parameters topic to manually create your own response file. 2. In the resulting response file, find every instance of <replace_with_your_password> and replace it with the appropriate password. If you generate the response file on one computer and perform the installation on another computer, change these parameters in the response file as necessary: the installation destination, license file location, host name, port, and the user names and passwords. Also check the disk space availability on the computer where you will perform the installation.

Chapter 3. Installing, upgrading, and applying updates

45

3. Run the installation program with the -silent parameter. Provide the -options parameter with the name of the response file that you edited.
install -silent -options full_pathname_to_responsefile -is:tempdir temp_directory_path

The temporary directory argument is optional. If not specified, the default system temporary directory is used.

Response file parameters (Windows)


Refer to this topic to modify a response file to use for a new installation or to use a provided response file template to run a silent installation on a Windows system. The response file templates are located on the installation media. Response files for Windows are slightly different than the response files for Linux and UNIX. You use them for the following purposes: v Creating a brand new installation of all products v Installing selected tiers and products v Upgrading an existing installation This reference is for a new installation on a Windows system and is divided into sections. The first two sections, Common and Product and Tier selection, contain required parameters. Whether you must complete the remaining parameters depends on your selections in the Product and Tier selection section. If your resulting response file contains parameters that are not required for the products and tiers that you selected, the extra parameters are ignored by the installation program. Some parameter values shown have quote characters surrounding their values. Quotes are optional around true and false values. For all other values, if quote characters are shown, enter them; if quote characters are not shown, do not enter them.

Common
This section and each parameter in it is required. -V licenseAccepted=true|false If you accept the terms of the license, specify true. You must specify true for the installation to proceed. -V LICENSE_FILE=pathname Specify the absolute path to the XML license file. -V IS_SELECTED_INSTALLATION_TYPE=typical|custom You can specify either typical or custom. -V NEW_SUITE=true|false If you are creating a new installation, specify true. This parameter and -V EXISTING_SUITE are mutually exclusive. Specify both parameters, but set only one of them to true. -V EXISTING_SUITE=true|false If you are adding new product modules to an existing Version 8.1 installation, specify true. This parameter and -V NEW_SUITE are mutually exclusive. Specify both parameters, but set only one of them to true.

46

Planning, Installation, and Configuration Guide

-V IS_DESTINATION=pathname Specify the absolute path where you want to install IBM Information Server. The typical path is C:\IBM\InformationServer. -V INFORMATION_SERVER_LANGUAGE=lang Specify the language to be used for IBM Information Server.
Table 18. Valid values -V INFORMATION_SERVER_LANGUAGE Language Brazilian Portuguese English French German Italian Japanese Korean Simplified Chinese Spanish Traditional Chinese Value pt_BR en fr de it ja ko zh es zh_TW

-V DESKTOP_SHORTCUTS=true|false Specify true if you want the installation program to create shortcuts on your desktop. -V ASB_HOST=hostname Specify the TCP/IP host name of the computer that hosts the services tier. All IBM Information Server tiers must be able to communicate with the services tier. If you are installing the services tier on this computer, specify the host name of this computer. -V ASB_PORT=9080 Do not modify this parameter. The port number that IBM Information Server Web clients use is determined during installation and recorded in this parameter. You cannot specify a specific port to use. Regardless of the installation method, the installation program always locates the first available port, starting with port 9080. The response file must contain this parameter and specify a value, even though the value is ignored. -V ASB_USER=user_id Specify the user ID for the suite administrator. -V ASB_PASSWORD=password Specify the password for the suite administrator. -V ASB_DIRECTORY_TYPE=internal You must specify internal .

Product and Tier selection


This section and each parameter in it are required. For each product and tier parameter with a true value, you must provide values for the parameters in its associated section that follows, if one exists. -V DOCUMENTATION_SELECTED=true|false Specify true if you want to install the documentation in context-sensitive help and PDF files on this computer.
Chapter 3. Installing, upgrading, and applying updates

47

-V CLIENT_SELECTED=true|false Specify true if you want the client tier installed on this computer. -V DOMAIN_SELECTED=true|false Specify true if you want the services tier installed on this computer. Complete the Metadata repository and services tiers section. -V DATABASE_SELECTED=true|false Specify true if you want the metadata repository tier installed on this computer. Complete the Metadata repository and services tiers section -V SERVER_SELECTED=true|false Specify true if you want the engine tier installed on this computer. Complete the Engine tier section. -AP businessglossary.businessGlossary.active=true|false Specify true if you want to install IBM WebSphere Business Glossary on this computer. -AP businessglossaryanywhere.businessGlossaryAnywhere.active=true|false Specify true if you want to install IBM Information Server Business Glossary Anywhere on this computer. -AP datastage.datastage.active=true|false Specify true if you want to install IBM WebSphere DataStage and QualityStage on this computer. Complete the WebSphere DataStage section. -AP datastagedocs.isPdfDocs.active=true|false Specify true if you want to install the PDF documentation on this computer. -AP fasttrackinstaller.fasttrackinstaller.active=true|false Specify true if you want to install IBM Information Server FastTrack on this computer. -AP informationanalyzer.informationAnalyzer.active=true|false Specify true if you want to install IBM WebSphere Information Analyzer on this computer. Complete the WebSphere Information Analyzer section. -AP informationserver.informationServer.active=true|false Specify true if you want to install IBM WebSphere Information Services Director on this computer. -AP isenterprise.isenterprise.active=true|false Specify true if you want to install IBM Information Server Manager on this computer. -AP metadataworkbench.metadataworkbench.active=true|false Specify true if you want to install IBM IBM Metadata Workbench on this computer.

Metadata repository and services tiers


Each parameter in this section must be completed if -V DOMAIN_SELECTED=true or if -V DATABASE_SELECTED=true. -V USE_EXISTING_APPSERVER=true|false Specify true if you want to use an existing IBM WebSphere Application Server installation. This parameter and -V USE_EMBEDDED_APPSERVER are mutually exclusive. Specify both parameters, but set only one of them to true. -V USE_EMBEDDED_APPSERVER=true|false Specify true if you want to install a new IBM WebSphere Application Server.

48

Planning, Installation, and Configuration Guide

This parameter and -V USE_EXISTING_APPSERVER are mutually exclusive. Specify both parameters, but set only one of them to true. -V APP_SERVER_HOME=pathname Specify the install location for the application server. If you are using an existing application server, specify the existing location. A typical location is C:\IBM\WebSphere\AppServer. -V REGISTRY_INTERNAL=true You must specify true. -V REGISTRY_LOCALOS=false You must specify false. -V APP_SERVER_USER=user_id Specify the IBM WebSphere Application Server administrator user ID. The typical name used is wasadmin. -V APP_SERVER_PASSWORD=password Specify the password for the WebSphere Application Server administrator user ID. -V SAME_USER_ADMIN=true|false Specify true if you want to use the same ID for the suite administrator user and the WebSphere Application Server administrator. Note that even if you specify true, you must still specify a value for APP_SERVER_USER, APP_SERVER_PASSWORD, ASB_USER, and ASB_PASSWORD. -V DB_TYPE_NAME=db2|Microsoft SQL Server|oracle Specify the type of database to used for the repository. A DB2 server is provided with the installation and can be installed and used as the metadata database server. -V XMETA_DATABASE_NAME=database_name Specify the name of the metadata repository database. The typical name used is xmeta -V XMETA_DATABASE_USERNAME=user_id Specify the user ID for the metadata repository database. The typical name used is xmeta. -V XMETA_DATABASE_PASSWORD=password Specify the password for the user ID for the metadata repository. -V XMETA_DATABASE_HOST=hostname Specify the TCP/IP host name of the computer that hosts the metadata repository. -V XMETA_DATABASE_PORT_NUMBER=port_number Specify the TCP/IP port number of the metadata repository database. (If DB2, the value is typically 50000.) Complete these additional parameters if -V DB_TYPE_NAME=db2 and you want to install DB2 as part of the IBM Information Server installation. -V DB2_DESTINATION=path_name Specify the absolute path location in which to install the DB2 database server. A typical location is C:\Program Files\IBM\sqllib. -V DB2_COPY_NAME=copy_name Specify the name to give this copy of the DB2 database server installation. A typical name is DB2COPY1.

Chapter 3. Installing, upgrading, and applying updates

49

-V DB2_INSTANCE_NAME=instance_name Specify the name to give the DB2 instance. A typical name is DB2. -V DB2_INSTANCE_PORT_NUMBER=port_number Specify the TCP/IP port number for the DB2 server. A standard port number is 50000 -V DB2_INSTANCE_OWNER_ID=user_ID Specify the instance owner ID for the DB2 server. A typical user ID is db2admin. -V DB2_INSTANCE_PASSWORD=password Specify the password for the instance owner ID for the DB2 server. Complete these additional parameters if -V DB_TYPE_NAME=db2 and you want to use an existing installation of DB2 for the metadata repository database. -V SELECTED_EXISTING_DB2_LOCATION=path_name Specify the absolute path location where DB2 is installed. A typical location is C:\Program Files\IBM\sqllib -V USE_EMBEDDED_DATABASE=true|false Specify false. -V USE_EXISTING_DATABASE=true|false Specify true.

Engine tier
Each parameter in this section must be completed if -V SERVER_SELECTED=true. -V ASB_AGENT_HOST=host_name Specify the TCP/IP host name for the engine. -V ASB_AGENT_PORT=port_number Specify the TCP/IP port number for the ASB Agent. A typical value is 31531. -V LOGGING_AGENT_PORT=port_number Specify the TCP/IP port number for the logging agent. A typical value is 31533.

WebSphere DataStage product


Each parameter in this section must be completed if -AP datastage.datastage.active=true. -V projects=project_string[;project_string] If you want to create new projects during the installation, specify the project_string for the projects. The string has the form project_nameNew|New (Protected)full_path_to_project. Multiple project strings can be specified in the string, each separated by a semicolon. For example, the following string (entered on one line) would indicate a new project and a new protected project to be created during the installation:
-V projects="dstage1--New--C:\Users\Jamie\dstage1;dstage2--New (Protected)-C:\IBM\InformationServer\Server\Projects\dstage2"

-V nlsEnabled=true|false If the language identifier, which is specified in the -V INFORMATION_SERVER_LANGUAGE parameter, is anything other than en, this value must be true. If you are installing English and are not certain whether you will use non-Latin characters, specify true.

50

Planning, Installation, and Configuration Guide

-V JOBMON_PORT_1=port_number Specify one of the two parallel engine job monitoring ports. A typical value is 13400 -V JOBMON_PORT_2=port_number Specify one of the two parallel engine job monitoring ports. A typical value is 13401 -V WSMQ_VERSION=version If you want to install an IBM WebSphere MQ plug-in, specify the version of WebSphere MQ. Valid versions are: v WSMQ_Server v WSMQ_Client

WebSphere Information Analyzer product


Each parameter in this section must be completed if -AP informationanalyzer.informationAnalyzer.active=true. -V CREATE_NEW_IA_DATABASE=true|false Specify true if you want to install a new analysis database. This parameter and -V USE_EXISTING_IA_DATABASE are mutually exclusive. Specify both parameters, but set only one of them to true. -V USE_EXISTING_IA_DATABASE=true|false Specify true if you want to use an existing analysis database. This parameter and -V CREATE_NEW_IA_DATABASE are mutually exclusive. Specify both parameters, but set only one of them to true. -V IA_DATABASE_SERVER=db2|oracle|sqlserver If you are using an existing analysis database, specify the database type. -V IA_DATABASE_USERNAME=iauser The user ID for the analysis database. The typical user ID used is iauser. -V IA_DATABASE_PASSWORD=password The password for the analysis database user ID. -V IA_DATABASE_NAME=database_name The name of the analysis database. The typical database name used is iadb -V IA_INSTANCE_PORTNUMBER=port_number Specify the port number for the analysis database. -V IA_DATABASE_LOCATION=pathname If you have not precreated the analysis database and want to create a new analysis database in DB2 as part of the installation procedure, specify the drive on which you want the analysis database installed, followed by a backslash, for example, C:\.

Response file parameters (Linux, UNIX)


Refer to this topic to modify a response file to use for a new installation or to use a provided response file template to run a silent installation on a Linux or UNIX system. The response file templates are located on the installation media. Response files for Windows are slightly different than the response files for Linux and UNIX. You use them for the following purposes: v Creating a brand new installation of all products v Installing selected tiers and products
Chapter 3. Installing, upgrading, and applying updates

51

v Upgrading an existing installation This reference is for a new installation on a Linux or UNIX system and is divided into sections. The first two sections, Common and Product and Tier selection, contain required parameters. Whether you must complete the remaining parameters depends on your selections in the Product and Tier selection section. If your resulting response file contains parameters that are not required for the products and tiers that you selected, the extra parameters are ignored by the installation program. Some parameter values shown have quote characters surrounding their values. Quotes are optional around true and false values. For all other values, if quote characters are shown, enter them; if quote characters are not shown, do not enter them.

Common
This section and each parameter in it is required. -V licenseAccepted=true|false If you accept the terms of the license, specify true. You must specify true for the installation to proceed. -V LICENSE_FILE=pathname Specify the absolute path to the XML license file. -V IS_SELECTED_INSTALLATION_TYPE=typical|custom You can specify either typical or custom. -V NEW_SUITE=true|false If you are creating a new installation, specify true. This parameter and -V EXISTING_SUITE are mutually exclusive. Specify both parameters, but set only one of them to true. -V EXISTING_SUITE=true|false If you are adding new product modules to an existing Version 8.1 installation, specify true. This parameter and -V NEW_SUITE are mutually exclusive. Specify both parameters, but set only one of them to true. -V IS_DESTINATION=pathname Specify the absolute path where you want to install IBM Information Server. The typical path is /opt/IBM/InformationServer. -V INFORMATION_SERVER_LANGUAGE=lang Specify the language to be used for IBM Information Server.
Table 19. Valid values -V INFORMATION_SERVER_LANGUAGE Language Brazilian Portuguese English French German Italian Japanese Korean Value pt_BR en fr de it ja ko

52

Planning, Installation, and Configuration Guide

Table 19. Valid values -V INFORMATION_SERVER_LANGUAGE (continued) Language Simplified Chinese Spanish Traditional Chinese Value zh es zh_TW

-V ASB_HOST=hostname Specify the TCP/IP host name of the computer that hosts the services tier. All IBM Information Server tiers must be able to communicate with the services tier. If you are installing the services tier on this computer, specify the host name of this computer. -V ASB_PORT=9080 Do not modify this parameter. The port number that IBM Information Server Web clients use is determined during installation and recorded in this parameter. You cannot specify a specific port to use. Regardless of the installation method, the installation program always locates the first available port, starting with port 9080. The response file must contain this parameter and specify a value, even though the value is ignored. -V ASB_USER=user_id Specify the user ID for the suite administrator. -V ASB_PASSWORD=password Specify the password for the suite administrator. -V ASB_DIRECTORY_TYPE=internal You must specify internal .

Product and Tier selection


This section and each parameter in it is required. For each product and tier parameter with a true value, you must provide values for the parameters in its associated section that follows, if one exists. -V DOCUMENTATION_SELECTED=true|false Specify true if you want to install the documentation in context-sensitive help and PDF files on this computer. -V CLIENT_SELECTED=true|false Specify true if you want the client tier installed on this computer. -V DOMAIN_SELECTED=true|false Specify true if you want the services tier installed on this computer. Complete the Metadata repository and services tiers section. -V DATABASE_SELECTED=true|false Specify true if you want the metadata repository tier installed on this computer. Complete the Metadata repository and services tiers section -V SERVER_SELECTED=true|false Specify true if you want the engine tier installed on this computer. Complete the Engine tier section. -AP businessglossary.businessGlossary.active=true|false Specify true if you want to install IBM WebSphere Business Glossary on this computer.

Chapter 3. Installing, upgrading, and applying updates

53

-AP businessglossaryanywhere.businessGlossaryAnywhere.active=true|false Specify true if you want to install IBM Information Server Business Glossary Anywhere on this computer. -AP datastage.datastage.active=true|false Specify true if you want to install IBM WebSphere DataStage and QualityStage on this computer. Complete the WebSphere DataStage section. -AP datastagedocs.isPdfDocs.active=true|false Specify true if you want to install the PDF documentation on this computer. -AP fasttrackinstaller.fasttrackinstaller.active=true|false Specify true if you want to install IBM Information Server FastTrack on this computer. -AP informationanalyzer.informationAnalyzer.active=true|false Specify true if you want to install IBM WebSphere Information Analyzer on this computer. Complete the WebSphere Information Analyzer section. -AP informationserver.informationServer.active=true|false Specify true if you want to install IBM WebSphere Information Services Director on this computer. -AP isenterprise.isenterprise.active=true|false Specify true if you want to install IBM Information Server Manager on this computer. -AP metadataworkbench.metadataworkbench.active=true|false Specify true if you want to install IBM IBM Metadata Workbench on this computer.

Metadata repository and services tier


Each parameter in this section must be completed if -V DOMAIN_SELECTED=true or if -V DATABASE_SELECTED=true. -V USE_EXISTING_APPSERVER=true|false Specify true if you want to use an existing IBM WebSphere Application Server installation. This parameter and -V USE_EMBEDDED_APPSERVER are mutually exclusive. Specify both parameters, but set only one of them to true. -V USE_EMBEDDED_APPSERVER=true|false Specify true if you want to install a new IBM WebSphere Application Server. This parameter and -V USE_EXISTING_APPSERVER are mutually exclusive. Specify both parameters, but set only one of them to true. -V APP_SERVER_HOME=pathname Specify the install location for the application server. If you are using an existing application server, specify the existing location. A typical location is C:/IBM/WebSphere/AppServer. -V REGISTRY_INTERNAL=true You must specify true. -V REGISTRY_LOCALOS=false You must specify false. -V APP_SERVER_USER=user_id Specify the IBM WebSphere Application Server administrator user ID. The typical name used is wasadmin.

54

Planning, Installation, and Configuration Guide

-V APP_SERVER_PASSWORD=password Specify the password for the WebSphere Application Server administrator user ID. -V SAME_USER_ADMIN=true|false Specify true if you want to use the same ID for the suite administrator user and the WebSphere Application Server administrator. Note that even if you specify true, you must still specify a value for APP_SERVER_USER, APP_SERVER_PASSWORD, ASB_USER, and ASB_PASSWORD. -V DB_TYPE_NAME=db2|Microsoft SQL Server|oracle Specify the type of database to used for the repository. A DB2 server is provided with the installation and can be installed and used as the metadata database server. -V XMETA_DATABASE_NAME=database_name Specify the name of the metadata repository database. The typical name used is xmeta -V XMETA_DATABASE_USERNAME=user_id Specify the user ID for the metadata repository database. The typical name used is xmeta. -V XMETA_DATABASE_PASSWORD=password Specify the password for the user ID for the metadata repository. -V XMETA_DATABASE_HOST=hostname Specify the TCP/IP host name of the computer that hosts the metadata repository. -V XMETA_DATABASE_PORT_NUMBER=port_number Specify the TCP/IP port number of the metadata repository database. (If DB2, the value is typically 50000.) The following DB2 parameters must be completed if -V DB_TYPE_NAME=db2 and if you are not using an existing database. -V DB2_DESTINATION=path_name Specify the absolute path location in which to install the DB2 database server. A typical location is /opt/IBM/db2/V9.5. -V DB2_ADMIN_NEW_USER=true|false If you want the installation wizard to create a new user, specify true. This parameter and -V DB2_ADMIN_EXISTING_USER are mutually exclusive. Specify both parameters, but set only one of them to true. -V DB2_ADMIN_EXISTING_USER=true|false If you want the installation wizard to use an existing user, specify true. This parameter and -V DB2_ADMIN_NEW_USER are mutually exclusive. Specify both parameters, but set only one of them to true. -V DB2_ADMIN_USER_NAME=user_name Specify the DB2 admin user name. A typical name is dasusr1. -V DB2_ADMIN_USER_PASSWORD=password Specify the DB2 admin user password. -V DB2_ADMIN_USER_GROUP_NAME=group_name Specify the DB2 admin users group name. A typical name is dasadm1. -V DB2_ADMIN_USER_HOME_DIRECTORY=pathname Specify the DB2 admin users home directory. A typical name is /home/dasusr1

Chapter 3. Installing, upgrading, and applying updates

55

-V DB2_INSTANCE_NEW_USER_SELECTION=true|false If you want the installation wizard to create a new instance user, specify true. This parameter and -V DB2_INSTANCE_EXISTING_USER_SELECTION are mutually exclusive. Specify both parameters, but set only one of them to true. -V DB2_INSTANCE_EXISTING_USER_SELECTION=true|false If you want the installation wizard to use an existing instance user, specify true. This parameter and -V DB2_INSTANCE_NEW_USER_SELECTION are mutually exclusive. Specify both parameters, but set only one of them to true. -V DB2_INSTANCE_PORT_NUMBER=port_number Specify the TCP/IP port number for the DB2 server. A standard port number is 50000 -V DB2_INSTANCE_OWNER_ID=user_ID Specify the user ID for the DB2 instance owner. A typical user ID is db2inst1. -V DB2_INSTANCE_PASSWORD=password Specify the password for the DB2 instance owner user ID. -V DB2_INSTANCE_GROUP_NAME=groupname Specify the group name for the DB2 instance owner user ID. A typical group name is db2iadm1 -V DB2_INSTANCE_HOME_DIRECTORY=pathname Specify the home directory for the DB2 instance owner user ID. A typical directory is /home/db2inst1 -V DB2_FENCED_NEW_USER_SELECTION=true|false If you want the installation wizard to create a new fenced user, specify true. This parameter and -V DB2_FENCED_EXISTING_USER_SELECTION are mutually exclusive. Specify both parameters, but set only one of them to true. -V DB2_FENCED_EXISTING_USER_SELECTION=true|false If you want the installation wizard to use an existing fenced user, specify true. This parameter and -V DB2_FENCED_NEW_USER_SELECTION are mutually exclusive. Specify both parameters, but set only one of them to true. -V DB2_FENCED_USER_NAME=user_ID Specify the DB2 fenced user ID. A typical user ID is db2fenc1. -V DB2_FENCED_USER_PASSWORD=password Specify the DB2 fenced users password. -V DB2_FENCED_USER_GROUP_NAME=groupname Specify the DB2 fenced users group name. A typical group name is db2fadm1. -V DB2_FENCED_USER_HOME_DIRECTORY=pathname Specify the DB2 fenced users home directory path. A typical path name is /home/db2fenc1.

Engine tier
Each parameter in this section must be completed if -V SERVER_SELECTED=true. -V ASB_AGENT_HOST=host_name Specify the TCP/IP host name for the engine. -V ASB_AGENT_PORT=port_number Specify the TCP/IP port number for the ASB Agent. A typical value is 31531.

56

Planning, Installation, and Configuration Guide

-V LOGGING_AGENT_PORT=port_number Specify the TCP/IP port number for the logging agent. A typical value is 31533. -V DS_USER_NEW_USER=true|false Specify true if you want the installation program to create a new user as the engine owner. This parameter and -V DS_USER_EXISTING_USER are mutually exclusive. Specify both parameters, but set only one of them to true. -V DS_USER_EXISTING_USER=true|false Specify true if you want the installation program to use an existing user ID as the engine owner. This parameter and -V DS_USER_NEW_USER are mutually exclusive. Specify both parameters, but set only one of them to true. -V DS_USER_NAME=username Specify the user ID for the user to own the engine. This user is an operating system user, and a typical value is dsadm. -V DS_USER_PASSWORD=password Specify the engine owners password. -V DS_USER_GROUP_NAME=groupname Specify the engine owners group name. A typical value is dstage. -V DSENGINE_PORT_NUMBER=port_number Specify the engines port number. A typical value is 31538 -V instanceTag=ITAG Specify the unique ITAG for the DataStage engine. Valid examples are ade and bed.

WebSphere DataStage product


Each parameter in this section must be completed if -AP datastage.datastage.active=true. -V DS_UPGRADE_SELECTED_UNIX=true|false Specify true if you are upgrading a 7.5.2 or 7.5.3 DataStage installation. This parameter and -V DS_NEW_INSTALLATION_SELECTED are mutually exclusive. Specify both parameters, but set only one of them to true. -V DS_NEW_INSTALLATION_SELECTED=true|false Specify true if you are installing WebSphere DataStage for the first time on this computer. This parameter and -V DS_UPGRADE_SELECTED_UNIX are mutually exclusive. Specify both parameters, but set only one of them to true. -V projects=project_string[;project_string] If you want to create new projects during the installation, specify the project_string for the projects. The string has the form project_nameNew|New (Protected)full_path_to_project. Multiple project strings can be specified in the string, each separated by a semicolon. For example, the following string (entered on one line) would indicate a new project and a new protected project to be created during the installation:
-V projects="dstage1--New--/opt/IBM/InformationServer/Server/Projects/dstage1; dstage2--New (Protected)--/opt/IBM/InformationServer/Server/Projects/dstage2"

-V nlsEnabled=true|false If the language identifier, which is specified in the -V INFORMATION_SERVER_LANGUAGE parameter, is anything other than en, this value must be true. If you are installing English and are not certain whether you will use non-Latin characters, specify true.
Chapter 3. Installing, upgrading, and applying updates

57

-V JOBMON_PORT_1=port_number Specify one of the two parallel engine job monitoring ports. A typical value is 13400 -V JOBMON_PORT_2=port_number Specify one of the two parallel engine job monitoring ports. A typical value is 13401 -V WSMQ_VERSION=version If you want to install an IBM WebSphere MQ plug-in, specify the version of WebSphere MQ. Valid versions are: v WSMQ_Server v WSMQ_Client

WebSphere Information Analyzer product


Each parameter in this section must be completed if -AP informationanalyzer.informationAnalyzer.active=true. -V CREATE_NEW_IA_DATABASE=true|false Specify true if you want to install a new analysis database. This parameter and -V USE_EXISTING_IA_DATABASE are mutually exclusive. Specify both parameters, but set only one of them to true. -V USE_EXISTING_IA_DATABASE=true|false Specify true if you want to use an existing analysis database. This parameter and -V CREATE_NEW_IA_DATABASE are mutually exclusive. Specify both parameters, but set only one of them to true. -V IA_DATABASE_SERVER=db2|oracle|sqlserver If you are using an existing analysis database, specify the database type. -V IA_DATABASE_USERNAME=iauser The user ID for the analysis database. The typical user ID used is iauser. -V IA_DATABASE_PASSWORD=password The password for the analysis database user ID. -V IA_DATABASE_NAME=database_name The name of the analysis database. The typical database name used is iadb -V IA_INSTANCE_PORTNUMBER=port_number Specify the port number for the analysis database. -V IA_DATABASE_LOCATION=pathname If you have not precreated the analysis database and want to create a new analysis database in DB2 as part of the installation procedure, specify the drive on which you want the analysis database installed, followed by a slash, for example, C:/.

Encodings that are supported by the installation program


The encodings supported by the IBM Information Serverare listed. If your currently specified language and code page do not map to a supported encoding, the installation program configures IBM Information Server for the English language, including National Language Support.

58

Planning, Installation, and Configuration Guide

Table 20. Supported encodings Language Brazilian Portuguese English French German Italian Japanese Korean Spanish Simplified Chinese Traditional Chinese Supported encodings UTF-8, Windows-1252, ISO-8859-1 UTF-8, Windows-1252, ISO-8859-1 UTF-8, Windows-1252, ISO-8859-1 UTF-8, Windows-1252, ISO-8859-1 UTF-8, Windows-1252, ISO-8859-1 UTF-8, Windows-932, EUC, EUC-JP, IBM-EUC-JP, IBM-33722, IBM-33722C, Shift-JIS, SJIS, UJIS, IBM-932, IBM-943, IBM-943C, PCK UTF-8, Windows-949, EUC, EUC-KR UTF-8, Windows-1252, ISO-8859-1 UTF-8, Windows-936, EUC-CN, IBM-EUC-CN, GB-2312, GBK UTF-8, Windows-950, Big5

Note: During an upgrade from Version 8.0.1 to Version 8.1, you cannot use the UTF-8 encoding. For more information see the IBM WebSphere DataStage and QualityStage National Language Support Guide.

Upgrading from Version 7.5.2 or 7.5.3


You can upgrade from previous versions of IBM Information Server, IBM WebSphere DataStage, and IBM WebSphere QualityStage. You might also need to migrate your projects and jobs depending on the version of software that you want to upgrade.

Planning for upgrading to IBM Information Server, Version 8.1


Before you upgrade to IBM Information Server, Version 8.1, review your data integration and hardware needs, and complete the preparation activities. The installation planning documentation provides checklists and worksheets to help you prepare for installing and upgrading IBM Information Server. The checklists cover the tasks that you do sequentially before you install or upgrade IBM Information Server. The worksheets are tables in some of the tasks that you fill out so that you can later install from the worksheets. Review the Planning for the installation of IBM Information Server section to prepare your systems. Always back up your system before you upgrade, in case the upgrade fails. Before it attempts the upgrade, the installation program checks the integrity of your existing installation and warns you if it discovers missing components.

Upgrading from IBM Information Server, Version 8.0.1


The installation program leads you step-by-step through the process of upgrading to IBM Information Server, Version 8.1. Prerequisites

Chapter 3. Installing, upgrading, and applying updates

59

1. NLS consideration: If your IBM Information Server 8.0.1 product is NLS-enabled, the IBM Information Server 8.1 upgrade will also be NLS-enabled. However, the Information Server 8.1 user interface will not be localized and will be presented in English. If you want your Information Server 8.1 user interface to be localized, you must install a fresh a new IBM Information Server 8.1 instance. 2. If you are upgrading IBM Information Server FastTrack Version 8.0.1: v If the FastTrack client is the only Version 8.0.1 IBM Information Server software on the system, then uninstall the FastTrack client and complete new installation steps rather than the following upgrade steps. v If the system contains other IBM Information Server Version 8.0.1 software along with the FastTrack client, then uninstall the FastTrack client, upgrade the other IBM Information Server software using the Version 8.1 installation wizard as documented in the following steps. When complete, upgrade your license in the web console and run the installation wizard again to install Version 8.1 of IBM Information Server FastTrack. 3. You must back up your systems and export your DataStage projects before you begin the upgrade process. After you begin the upgrade, you cannot reverse the changes. If a failure occurs during upgrade, IBM Information Server is either uninstalled, including your Version 8.0.1 installation, or the installation is left in an inoperable state. 4.
AIX When upgrading from a version 8.0.1 32-bit system to a version 8.1 64-bit system, change your operating system from 32-bit to 64-bit and reboot the machine. Review the Planning for the installation of IBM Information Server section to prepare your systems. Shut down IBM Information Server. Reboot the system. Ensure that IBM Information Server has started and is running successfully. Ensure that the following applications are running: v Metadata repository database v IBM WebSphere Application Server v IBM Information Server engine Ensure that you can log in to the IBM Information Server Web console. If you have running WebSphere Information Services Director services, disable them: a. Log in to the IBM Information Server Console. b. From the Operate pillar, open the Deployed information Services Applications workspace. c. In the left panel, select the application and click Edit.

5. 6. 7. 8.

9. 10.

d. Click Disable and select Disable from the menu. The application is grayed out. e. Repeat steps 10c and 10d for each deployed application. 11. Shut down all scheduled tasks, such as DataStage jobs, reports, and log purge activities. 12. Ensure that all IBM Information Server clients are closed and that the following applications are not running: v WebSphere Application Server First Steps v Profile Creation wizards v The IBM Information Server information center

60

Planning, Installation, and Configuration Guide

Specifically, the upgrade fails if programs other than WebSphere Application Server are using the same instance of Java that is used by WebSphere Application Server. 13. Log in as root for Linux or UNIX systems, or as a local administrator for Windows systems. 14. Disable the firewall and antivirus software on each computer that you want to upgrade. Some antivirus software blocks the installation program and network operations from running or prompts for a confirmation. These actions interfere with the installation program and might cause an installation to fail. About this task You run the installation program on each computer in your installation. For example, if you use a three-computer topology, you run the installation wizard on each of the three computers to upgrade all of the tiers. You must upgrade all of the tiers in your installation to the same version. Procedure To upgrade Version 8.0.1 to Version 8.1: 1. Run the installation program on each system in your configuration to upgrade all of the tiers. Upgrade your computers in the following order: a. Metadata repository tier b. Services tier (referred to as the Domain in version 8.0.1) c. Engine tier d. Client tier If two or more tiers are on the same computer, the installation program upgrades them in the appropriate order. 2. Select an existing installation of IBM Information Server on the Installation Directory page of the installation program. The installation program determines which tiers and products on each computer to upgrade. 3. Complete the rest of the installation program to upgrade the system to Version 8.1. 4. Repeat steps 1-3 for each computer in your installation.

Response file parameters for an upgrade from version 8.0.1


Refer to this topic if you choose to use the response file templates to run a silent installation to upgrade an existing IBM Information Server version 8.0.1 product to version 8.1. The response file templates are located on the installation media. Response files for Windows are slightly different than the response files for Linux and UNIX. You use them for the following purposes: v Creating a brand new installation of all products v Installing selected tiers and products v Upgrading an existing installation This reference is for an upgrade installation. Each parameter is required. -V licenseAccepted=true|false If you accept the terms of the license, specify true. You must specify true for the installation to proceed.
Chapter 3. Installing, upgrading, and applying updates

61

-V INFORMATION_SERVER_LANGUAGE=en For an upgrade from version 8.0.1, the only supported language is English. -V ASB_USER=user_id Specify the user ID for the suite administrator. -V ASB_PASSWORD=password Specify the password for the suite administrator. -V APP_SERVER_USER=user_id Specify the IBM WebSphere Application Server administrator user ID. The typical name used is wasadmin. -V APP_SERVER_PASSWORD=password Specify the password for the WebSphere Application Server administrator user ID.

Upgrading from DataStage or QualityStage, Versions earlier than 8.0.1


To upgrade from DataStage and QualityStage, Versions earlier than 8.0.1 to IBM Information Server, Version 8.1, you upgrade the software or install a new Version 8.1 instance and then migrate your projects and jobs. Prerequisites 1. You must back up your systems and export your DataStage projects before you begin the upgrade process. After you begin the upgrade, you cannot reverse the changes. 2. Review the Planning for the installation of IBM Information Server section and prepare your systems. 3. Before you upgrade, ensure that the DataStage server is running and that all DataStage clients are closed. 4. 5.
Linux UNIX

Log on as the root user or as a user with root privileges.

Windows Log on as a local administrator or as a domain administrator with local administrator privileges.

About this task The installation program updates the software to IBM Information Server, Version 8.1. To use existing projects and jobs in the new installation, you must migrate those separately. You must upgrade all of the tiers in your installation to the same version of IBM Information Server. Procedure To upgrade to Version 8.1: 1. Back up DataStage and save settings and configurations files.

62

Planning, Installation, and Configuration Guide

2. Choose one of the following upgrade options:


Option Basic method Description Preserves the directory structure of your existing projects and upgrades the projects to IBM Information Server, Version 8.1. During the installation process, your projects are prepared for migration to the new metadata repository. You then use the WebSphere DataStage and QualityStage Administrator client to migrate each of your projects. Moves all of your migrated projects to the WebSphere DataStage Version 8.1 directory structure. You can also use this method to migrate your DataStage installation to a different computer. On Linux or UNIX systems, keeps an existing instance of DataStage and also installs IBM Information Server, Version 8.1. Preserves your existing DataStage project directory structure. You upgrade DataStage first to 7.5.3 and then to IBM Information Server, Version 8.1..

Complete method

Multiple server method

Upgrade method for versions earlier than 7.0

If you want to upgrade from a DataStage release that is earlier than Version 7.5.2, you must upgrade DataStage to IBM Information Server Version 7.5.3, and then you must upgrade to For more information about the upgrade methods, see Migrating to IBM Information Server Version 8.1.

Updating Version 8.1 products and components


You can update IBM Information Server and associated product modules by using the Update Installer. The Update Installer is installed as part of IBM Information Server Version 8.1 in the C:\IBM\InformationServer\Updates directory. On Linux and UNIX, the Update Installer is installed in the opt/IBM/InformationServer/Updates directory. Details on how to use the Update Installer are provided online in a tech note at: http://www.ibm.com/support/docview.wss?rs=14&uid=swg27012519.

Updating the license before adding new product modules and components
The suite installation wizard registers your license when you install IBM Information Server. If you purchase additional product modules or components after you install the suite, you must update the license in the services tier before you can install the new modules. Prerequisites v You must have suite administrator authority. v Obtain a new license from the IBM Information Server License Portal or your IBM Sales Administrator. A license file always contains all of the products that

Chapter 3. Installing, upgrading, and applying updates

63

you are licensed to use. When you add new products to your license, the license file must include all of the existing licensed products as well as the newly acquired products. About this task Obtain a license file and complete this task if any of the following conditions apply: v You are adding additional product modules. v You are upgrading from IBM Information Server FastTrack Version 8.0.1. * v You are upgrading from IBM Metadata Workbench Version 8.0.1. * v You are upgrading from IBM Information Server Business Glossary Anywhere, Version 8.0.1. * * If the current license has a date that is before May 20, 2008 and if you previously installed this product, you can use the IBM Information Server installation program to upgrade the product. However, you must obtain and upload a new license file that includes this product. You can obtain and upload the updated license file either before or after you upgrade to IBM Information Server Version 8.1. If the current license has a date prior to May 20, 2008 but you did not previously install the product, you must obtain and upload a new license file that includes this product before you can use the IBM Information Server Version 8.1 installation program. Procedure To update the license: 1. Ensure that your new license file is on a computer that can run the Information Server Web console. 2. Use one of the following methods to log in to the Web console as a suite administrator: v Click Start IBM Information Server IBM Information Server Web Console. v Open a Web browser and go to the URL for the Web console. The URL takes the form, services_host:port, where services_host is the URL or IP address of the server where the services tier is installed and port is the port that is assigned to the Web console. The default port is 9080. 3. On the Administration tab, click Domain Management Licensing. 4. Click Upload a Licensing File. 5. Select your .xml license file and click Upload.

Installing components that are not in the suite installation program


Some components have their own installation programs. You install these components after you install IBM Information Server.

Installing IBM Information Server Business Glossary Anywhere clients


To use IBM Information Server Business Glossary Anywhere, you must install and configure the client for each user. Prerequisites

64

Planning, Installation, and Configuration Guide

Ensure that your client system meets the IBM Information Server Business Glossary Anywhere client requirements as specified in the Information Server system requirements. Procedure To install the IBM Information Server Business Glossary Anywhere client on each desktop computer: 1. On the installation media, go to the client\op_sys directory, where op_sys is the directory that corresponds to your Microsoft Windows operating system. Double-click BGASetup.exe and then click Install to start the installation. 2. Click OK to close the Welcome screen. 3. Confirm that the IBM Information Server Business Glossary Anywhere book icon is now in the system tray. 4. Configure the server parameters on all clients. For details, take the tour or read the configuration information at Getting started with the desktop browser.

Installing WebSphere MetaBrokers and bridges


After you install the IBM Information Server clients, you can install WebSphere MetaBrokers and bridges. WebSphere MetaBrokers and bridges import metadata into and export metadata out of the metadata repository. Prerequisites v Ensure that your system meets the WebSphere MetaBrokers and bridges requirements, as specified in Information Server system requirements. v You must have administrator access to the installation system. v If you have a previous version or a pre-release version of WebSphere MetaBrokers and bridges installed, you must uninstall it before installing the new version. v At least one of the following clients must be on the computer where you plan to install the WebSphere MetaBroker and bridges: IBM Information Server console IBM WebSphere DataStage and QualityStage Administrator client IBM WebSphere DataStage and QualityStage Designer client IBM WebSphere DataStage and QualityStage Director client A required component for the WebSphere MetaBroker and bridges is installed with those clients. Restrictions The WebSphere MetaBroker and bridges must be installed on the same computer as the client with which you plan to use them. You can use WebSphere MetaBroker and bridges with the following clients: v The Import Export Manager, which is provided and installed with the WebSphere MetaBroker and bridges. v IBM WebSphere DataStage and QualityStage Designer client, which is installed by the IBM Information Server installation program. v IBM Rational Data Architect. In this case, you must also install the IBM Rational Data Architect MetaBroker where you install the WebSphere MetaBroker and bridges.

Chapter 3. Installing, upgrading, and applying updates

65

Procedure To install WebSphere MetaBrokers and bridges: 1. Log on to the system as an administrator. 2. On the installation image, open the MetaBrokersAndBridges directory and double-click setup.exe. 3. Follow the instructions in the wizard to install WebSphere MetaBrokers and bridges.

Installing z/OS components for IBM WebSphere DataStage MVS Edition


If you want to compile and run IBM WebSphere DataStage jobs on a z/OS system, you must first install COBOL copybook files and the Runtime Library (RTL) on the z/OS system. Procedure To install the z/OS components:

Installing COBOL copybook files


Upload the COBOL copybook files to the z/OS system to add them as members of a copybook library (copylib). Procedure To install the COBOL copybook files: 1. Using FTP, upload the COBOL copybook files to copylib members. On the installation media, the files are in the Mainframe Components directory.
Table 21. Copybook to copylib associations Copy these files ArdtIMSg.cob ArdtMsg1.cob ArdtMsg2.cob ArdtUBgn.cob ArdtUCod.cob ArdtUDat.cob ArdtUEnd.cob ArtdtUFct.cob ArtdtuFdf.cob RTLMsgs.cob To these copylib members ARDTIMSG ARDTMSG1 ARDTMSG2 ARDTUBGN ARDTUCOD ARDTUDAT ARDTUEND ARDTUFCT ARDTUFDF RTLMSGS

2. In the JCL templates for compiling the COBOL program, specify the name of the copylib that contains the uploaded copybook files. a. Start the Designer client. b. Under the Tools menu option, edit the CompileLink, DB2CompileLinkBind, and TDCompileLink JCL templates. c. In the SYSLIB DD statement of each COBCOMP step, specify the copylib. Copylib members:

66

Planning, Installation, and Configuration Guide

The copylib members for IBM WebSphere DataStage contain message text or code templates that you can customize. Message text The following table describes copylib members that contain runtime message text.
Table 22. Copylib members with message text that you can customize copylib member ARDTIMSG ARDTMSG1 ARDTMSG2 RTLMSGS Customizes Message text for IMS DB errors Message text that displays after a job runs Message text about file processing errors Message text about errors and warnings that the runtime library generates

Templates The following table describes copylib members that can control the initialization or termination of the generated COBOL program for a job.
Table 23. Copylib members that can control the operation of generated COBOL programs copylib member ARDTUBGN ARDTUCOD ARDTUDAT Adds Program initialization code for the generated COBOL program. Paragraphs to the end of the generated COBOL program. Code before the PROCEDURE DIVISION statement of the generated COBOL program. For example, you can add WORKING-STORAGE variables and a LINKAGE SECTION. Program termination code before each GOBACK statement. Statements, such as SELECT, to the end of FILE-CONTROL paragraph in the ENVIRONMENT division. FD statements at the end of the FILE SECTION in the DATA DIVISION.

ARDTUEND ARDTUFCT ARDTUFDF

Installing the runtime library for z/OS jobs


The runtime library for z/OS jobs contains routines that are used when a job is run. Procedure To install the runtime library for z/OS jobs: 1. Log on to the z/OS system. 2. Allocate a runtime library data set. a. In ISPF, access function 3.2 (Data Set Utility). b. In the Option line, type A. c. Tab to the Data Set Name prompt, type a data set name, and press Enter. d. In the Allocate New Data Set panel, in the Space units field, type TRKS.

Chapter 3. Installing, upgrading, and applying updates

67

e. In the Allocate New Data Set panel, type the following values:
Field Primary quantity Secondary quantity Directory blocks Record format Record length Block size Value 10 10 0 FB 80 3120

3. Transfer the runtime library data file to the allocated runtime library data set. On your workstation, start FTP. Connect to the z/OS system and log in. Set the transfer mode to BIN. Use the PUT command to send the ArdtRTL.data file to the allocated runtime library data set. This file contains the IBM WebSphere DataStage runtime library in binary format. 4. In the z/OS system, receive the runtime library data set. a. Run the TSO RECEIVE command: RECEIVE INDA(input_dataset_name) input_dataset_name is the data set that you specified in Step 2. b. At the prompt, type DA(output_dataset_name) output_dataset_name is the name of the data set that the TSO RECEIVE command creates. This output data set is a sequential file that is used by the job that you create and run in steps 5, 6, and 7. 5. Transfer the file ArdtRTL.jcl to z/OS. This file contains sample JCL to create the runtime library. a. On your workstation, start FTP. b. Connect to the z/OS system and log in. c. Set the transfer mode to ASCII. d. Use the PUT command to send the ArdtRTL.jcl file to a member of a JCL library. 6. In the z/OS system, edit the JCL library member specified in step 5d. a. Modify the JOB statement to meet your site standards. b. In the SEQ1 statement, change the DSN value to the name of the output data set that the TSO RECEIVE command creates in Step 4b. The output data set is the source data set for an IEBCOPY operation. c. In the PDS2 statement, change the DSN value to the name of the link library to contain the contents of the WebSphere DataStage runtime library. The link library is the target for the IEBCOPY operation. a. b. c. d. 7. Submit the JCL file from the previous step to copy the data set to the link library. 8. Start the Designer client. 9. Edit the JCL templates for CompileLink and DB2CompileLinkBind. In the LKED step, change the ARDTLIB DD statement to use the data set name that you specified in the PDS2 statement in Step 6c.

Installation verification process for z/OS components


The installation verification Process (IVP) validates that an z/OS environment is configured for compiling and running z/OS jobs.

68

Planning, Installation, and Configuration Guide

The installation verification process uses IBM WebSphere DataStage jobs to validate an z/OS environment.
Job IVPFLAT IVPDB2 IVPIMS Purpose Tests the runtime library. Tests connectivity to DB2 for z/OS and the runtime library. Tests connectivity to the IMS database and the runtime library.

For information about installing and running the installation verifications process, see the x:\Utilities\Supported\IVP\IVP Installation Instructions.doc file on the installation media.

Chapter 3. Installing, upgrading, and applying updates

69

70

Planning, Installation, and Configuration Guide

Chapter 4. Configuring IBM Information Server


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

Creating users and groups for IBM Information Server


You complete several tasks to set up users and groups for the suite. About this task The following list outlines, at a high level, the tasks that you do to set up the security for IBM Information Server. For information about users and security, see the IBM Information Server Administration Guide. Procedure To create users and groups: 1. For the suite administrator (isadmin by default), set access levels for each product module by assigning security roles in the IBM Information Server console. 2. For the suite administrator, map credentials for your account in the IBM Information Server Web console. 3. Optional: Configure the user registry. 4. Optional: Create additional users and groups for IBM Information Server. 5. Optional: Control access levels by assigning security roles. 6. Optional: Map the credentials for the users.

Configuring national language support (Linux, UNIX)


If you installed national language support (NLS) but you did not configure it, edit the dsenv file to specify the locale that the server uses. This locale is different from the default locales for projects or jobs. Server jobs depend on the server locale to compile correctly. About this task Change the lines in the dsenv file only if you want to run the IBM Information Server engine by using different locale settings from the defaults that are inherited by a operating system user. In this situation, you set the operating system locale settings specifically for use by the engine, rather than allowing the operating system defaults to set them. For example, you might choose to set the LC_NUMERIC locale to a specific value. Then, operating system commands or programs that run from within a job use that value to determine the decimal and thousands separators for numbers.

Copyright IBM Corp. 2005, 2008

71

You can also define the environment variables on a per-project and per-job basis, from the Administrator and Designer clients. The dsenv file is for use only at the whole system level. Procedure To configure national language support: 1. Locate the following section in the dsenv file.
#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

2. Replace each occurrence of langdef with the locale that the server uses. To find the server locale, use the locale command
locale -a

3. Remove the comment marker (#) that is at the beginning of each line. 4. Restart the engine. For more information see the IBM WebSphere DataStage and QualityStage National Language Support Guide.

Configuring environment variables for the engine (Linux, UNIX)


The dsenv file must contain the listed environment variables for the IBM Information Server engine. Prerequisites You must be logged in as an IBM WebSphere DataStage administrator with the operating system credentials on the server for the WebSphere DataStage administrator. About this task The dsenv file contains a series of shell arguments that are referenced when the engine starts. Shared libraries must be loaded for some ODBC connections, plug-ins, connectors, and for interacting with external applications, such as WebSphere MQ. In addition, you must include the library path in an environment variable. Interactive users, other programs, and scripts can reference the dsenv file. Procedure To configure the environment variables: 1. Edit the dsenv file located in the $DSHOME/DSEngine directory, and set the library path.
Operating system IBM AIX Linux Library path environment variable LIBPATH LD_LIBRARY_PATH

2. Restart the engine.

72

Planning, Installation, and Configuration Guide

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.

Configuring WebSphere DataStage and WebSphere QualityStage


Before you use IBM WebSphere DataStage and WebSphere QualityStage, you must perform several configuration tasks. About this task The following list outlines, at a high level, the tasks that you do to initially configure and administer this product module. For information about users and security, see the IBM Information Server Administration Guide. Procedure To complete the configuration tasks: 1. Use the IBM Information Server Web console to create users and groups and assign administrator and user roles. 2. If the operating system where the engine tier is installed does not use the same user registry as IBM Information Server (default mode), create credential mappings. 3. Assign user roles and project roles and give project access privileges to users. 4. Optional: Configure the parallel processing environment. 5. Optional: Migrate jobs that you created in an earlier version of WebSphere DataStage to the current version. 6. Optional: If you intend to develop WebSphere QualityStage matches, ensure that a new or existing supported database is available to receive test pass results for the Match Designer.

Configuring WebSphere QualityStage Match Designer


The IBM WebSphere QualityStage Match Designer requires an ODBC data source name (DSN) to connect to the database where the Match Designer stores match pass results. Prerequisites Designate a new or existing IBM DB2, Oracle, or Microsoft SQL Server database dedicated to the storage of Match Designer output. If the IBM Information Server client and engine tiers are installed on different computers, you must create an ODBC DSN with the same name on each computer and then test the connection to the database before running the Match Designer. To configure the Match Designer database connection: 1. On the client tier, define a System DSN that points to your Match Designer database. You might want to select from the set of IBM Wire Protocol ODBC drivers installed as part of the IBM Information Server environment. These

Chapter 4. Configuring

73

drivers are convenient because their functionality does not depend on the presence of any additional database-specific client software. 2. If the client and engine tiers are installed on the same computer, skip this step. Otherwise, on the engine tier, define a second ODBC System DSN using the same name and pointing to the same Match Designer database. The connection to the Match Designer database is established and your encrypted credentials are retained when you run a Test Environment Update for your match specification in the Match Designer.

Testing the installation of WebSphere DataStage and WebSphere QualityStage


After you install and configure WebSphere DataStage and WebSphere QualityStage, test the installation by logging in to the Administrator and Designer clients. Prerequisites To run these tests, especially to connect to the DataStage Designer client, you must either be a DataStage administrator or a lower-level user with specific project access granted by an administrator (in the Administrator client). Therefore, it is recommended that any tests be carried out by a DataStage administrator. If credential mapping is being used, then the credential mapping must be set up. Procedure To test the installation: 1. Start the WebSphere DataStage and QualityStage Administrator client: a. On the computer where you installed the Administrator client, click Start All Programs IBM Information Server WebSphere DataStage and QualityStage Administrator. Or, if you selected Create desktop icons, when installing, click the desktop icon. 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, type server_name:port_number in the Domain field. For example, if you installed the services tier (domain) on the xyz server and the default port number was used, type xyz:9080 as the server. d. Type the engine server name in the DataStage server field. 2. Start the WebSphere DataStage and QualityStage Designer client: a. On the computer where you installed the Designer client, click Start All Programs IBM Information Server WebSphere 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, type server_name:port_number in the Domain field. For example, if you installed the services tier (domain) on the xyz server and the default port number was used, type xyz:9080 as the server. d. When you are prompted for the server and project, type server_name/project_name in the Project field. For example, if the engine is installed on the xyz server and the project is named my-project, type xyz/my-project.

74

Planning, Installation, and Configuration Guide

Testing the WebSphere Information Services Director installation


After you install and configure WebSphere Information Services Director, test the installation. Prerequisites You must have suite administrator credentials or have already set up credentials that have user authority. Procedure To test the installation of WebSphere Information Services Director: 1. On the computer where you installed the WebSphere Information Services Director client, click Start All Programs IBM Information Server IBM Information Server Console and log in to the console. Log into the console with credentials that have the Suite Administrator authority or with credentials that have the user authority. 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.

Configuring WebSphere Information Analyzer


Before you use IBM WebSphere Information Analyzer, you must perform several required configuration tasks. About this task The following list outlines, at a high level, the tasks that you do to initially configure and administer this product module. For detailed information about analysis configuration, see the WebSphere Information Analyzer User Guide. Procedure To configure WebSphere Information Analyzer: 1. Assign the Information Analyzer Data Administrator role to the suite administrator. 2. Verify the WebSphere DataStage credentials that are used to connect to the IBM Information Server engine. You can validate the settings in the Home Configuration Analysis Settings Analysis Engine and Analysis Database tabs. 3. On the computer that hosts the engine, define the data source name (DSN) to the analysis database. 4. Locate and configure connections to the host computers and data stores in your organization. 5. Import metadata into the metadata repository. 6. Create a project and provide basic project details. 7. Associate the imported metadata with the project. 8. Modify the project and data source analysis settings. 9. Set up security for the project.
Chapter 4. Configuring

75

10. Customize the project dashboard.

Configuring WebSphere Business Glossary


To use IBM WebSphere Business Glossary, the suite administrator must assign roles to WebSphere Business Glossary users, authors, and administrators. For more information, see the Managing glossary access.

Configuring IBM Metadata Workbench


To use IBM Metadata Workbench, the suite administrator must assign roles to IBM Metadata Workbench users and administrators. For more information, see the Introduction to IBM Metadata Workbench.

Configuring IBM Information Server FastTrack


To use IBM Information Server FastTrack, the suite administrator must create FastTrack administrator and FastTrack user IDs. For more information, see the Getting started configuration steps for IBM Information Server FastTrack.

Configuring a parallel processing environment


Some tasks are required to configure the parallel engine, and some tasks ensure the parallel engine are 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 run the parallel engine on multiple computers, copy the parallel engine components to each computer and configure the systems. Each user who runs parallel jobs must have rsh or ssh access to each computer where the parallel engine components are copied.

Copying the parallel engine components to system nodes (Linux and UNIX)
When you configure an MPP system, you must copy the parallel engine components to all of your processing nodes. About this task There are two ways to make the parallel engine available to all the nodes in an MPP system: v You can globally cross-mount, typically via 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 hard or the hard, intr option. Do not mount it by using the soft option. Start up times are faster if you copy the engine to each node, however.

76

Planning, Installation, and Configuration Guide

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 To copy the parallel engine components to several nodes in a single operation, do the following steps: 1. On the computer where you have installed the IBM Information Server engine, change directory to the parallel engine directory (by default /opt/IBM/InformationServer/Server/PXEngine). 2. Enter the following command:
install_dir/install/copy-orchdist node1 node2 ... nodeN

Where node1 to nodeN is a space-separated list of the new node names. 3. Add the nodes to your configuration file. For more information about the parallel engine configuration file, see the IBM WebSphere DataStage and QualityStage Parallel Job Developer Guide.

Configuring a computer to be a processing node for MPP (UNIX and Linux)


After you have copied the parallel engine to each computer that is a member of the MPP environment, you must configure the computer to act as a processing node. About this task Repeat this procedure for each UNIX or Linux computer that is to be a parallel processing node in your environment. Procedure To configure a computer to be a processing node for MPP: Configuring remote and secure shells (Linux, UNIX): You must configure the parallel engine to run the remote shell (rsh) or the secure shell (ssh) without a password on all processing nodes that run parallel jobs. Configuring the parallel engine to use the secure shell (ssh) program (Linux, UNIX): The secure shell (ssh) program provides strong authentication and secure communications between computers on a network. Prerequisites 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 primary computer to all of the other computers, using RSA public key encryption for authentication. This task must be completed for each user that runs parallel jobs. It is also necessary to log in to each computer before it can run
Chapter 4. Configuring

77

parallel jobs. In the following steps, the primary computer is the computer that contains the IBM Information Server engine. The secondary computers are the other computers that contain parallel engines. Procedure To configure the parallel engine to use ssh: 1. On the primary computer, 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

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 secondary computer.
cd ~/.ssh scp id_rsa.pub user@secondary_computer:~/.ssh

3. Log in to each of the secondary computers and add the public key to the list of authorized keys. This process must be repeated for each user that will run 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 called authorized_keys or authorized_keys2, depending on the version of ssh. 4. On the primary computer, run the following command for each user and secondary computer to test the ssh configuration:
primary_computer% ssh secondary_computer ls

If successful, you should be able to log in to the remote shell without providing a password. 5. On the primary computer, create the remsh file in the /Server/PXEngine/etc/ directory with the following content.
#!/bin/sh exec /usr/bin/ssh "$@"

The /Server/PXEngine/etc/ directory is located in the directory where you installed the engine. 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 (Linux, UNIX): 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 password-less 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, one host name per line.

78

Planning, Installation, and Configuration Guide

The host name that is included in this file must correspond to the setting of the node fastname parameter in the parallel configuration file. Procedure 1. Use one of these methods to allow users to run rsh without a password: v Edit the /etc/hosts.equiv file. The file must be owned by root and must grant read and write access to root and grant no access to any other user (file mode of 600). 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

where host_name is the name of a processing node that you use with the parallel engine. If hostname is accessible, this command prints a message displaying the time it has been up. Specifying the location of the remote shell (rsh) program (Linux, UNIX): The parallel engine has a set of paths it uses when trying to establish a remote shell. You must explicitly specify the path location in the remsh file if the rsh program is not in the engines list of paths. About this task The parallel engine searches the paths in the following order: 1. install_dir/etc/remsh, where install_dir is the top-level directory where the engine tier is installed. 2. 3. 4. 5. 6. /user/lpp/ssp/rcmd/bin/rsh /usr/ucb/rsh /usr/bin/remsh /bin/remsh /usr/bin/rsh
AIX

If the parallel engine cannot establish a remote shell connection using these paths, explicitly specify the path to rsh in the first place the engine searches: install_dir/etc/remsh. Procedure 1. Copy or rename the file install_dir/etc/remsh.example to install_dir/etc/remsh. This file contains the following shell script, which invokes /usr/bin/rsh:
#!/bin/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, use the chmod command:
chmod 755 install_dir/etc/remsh

4. Test the shell script by running rsh on each processing node:


Chapter 4. Configuring

79

rsh node_name uptime

Setting user privileges to run parallel jobs (Linux, UNIX): A user who runs a parallel job must have the necessary privileges on all processing nodes that the application uses. Each user who runs a parallel job requires the following privileges: v Log in access Read, write, and modify access to these directories: /ishome/Server/Scratch /ishome/Server/Datasets /tmp v Run permission on local copies of programs and scripts. v Read access to the disk location is referred to by the $APT_ORCHHOME environment variable set in the project, or overridden in the parameters for the job. The installation default for this is /ishome/Server/PXEngine. v

Copying parallel engine components to system nodes (Windows)


When you configure an MPP system, you must copy the parallel engine components to all of your processing nodes. About this task Repeat this procedure for each Windows computer that is to be a parallel processing node in your environment. Procedure To copy the parallel engine components to several nodes: 1. On each computer that is a node, run the IBM Information Server installation program. 2. Select the engine tier only. 3. After you have installed the engine tier on each computer, add an entry in the parallel engine configuration file for each additional node.

Configuring a computer to be a processing node for MPP (Windows)


If your parallel environment is a massively parallel processing environment (MPP), complete these steps to configure a computer to be a member of your MPP environment. About this task Repeat this procedure for each Windows computer that is to be a parallel processing node in your environment. Procedure To configure a computer to be a processing node for MPP: 1. Create a generic user account. a. Log in as a user with Administrator privileges. b. At a command prompt, create a generic user named dstage:

80

Planning, Installation, and Configuration Guide

NET USER dstage password /ADD /COMMENT:"DataStage user account" /FULLNAME:"DataStage User" /ACTIVE:YES /EXPIRES:NEVER /PASSWORDCHG:NO

where password is the password for the dstage user. All computers that participate in the MPP configuration must use the generic user name and password. c. Log off and log in as the dstage user. d. Edit the User environment variable named HOME. If the entry contains other environment variables, for example %HOMEPATH%, replace the entire contents with the literal value of HOMEPATH. The default location is typically C:\Documents and Settings\dstage. MKS does not have the ability to resolve the environment variable when connecting remotely. e. You can set APT_ORCHHOME as a system variable. This variable points to the parallel engine install directory. The default value is C:\IBM\InformationServer\Server\PXEngine. You must restart the rshd service after setting up this variable. f. Set APT_PM_NOWAITPID=1 at the project level. This environment variable must be set for all jobs. g. Log off as the dstage user and log back in as an Administrator user. 2. Set user permissions for the dstage account. The new user must have sufficient access rights to run jobs. The following table lists the minimum directories that you must set and the appropriate permissions.
Directory X:\tmp X:\IBM\InformationServer\Server\Scratch X:\IBM\InformationServer\Server\Datasets Permissions Write, Read, Modify Write, Read, Modify Write, Read, Modify

3. Set the remote shell permissions: a. At a command prompt, type ksh b. From the ksh shell, run the ssh command to connect to the remote engine: ssh -l dstage hostname. If prompted for an RSA certificate, accept it. You must enter the password for the dstage user. c. After you are connected, run the rsetup command to add the dstage user and password to the Windows XP or Windows 2003 Server LSA database for use by the rshd service. Enter the same password when prompted. d. Edit the .rhosts file in the dstage users home directory. You might need to create the .rhosts file if it does not already exist. e. Add the following line:
+ dstage

f. Exit from the ssh session. g. Edit the hosts.equiv file located in the $ROOTDIR/etc folder. The path name is shown in UNIX format, which is required by MKS. That location is equivalent to C:\Program Files\MKS Toolkit\etc on the Windows file system, if you installed MKS in the default location.. h. For testing purposes, add the following line:
+ +

You might need to create this file if it does not already exist. i. Test your configuration by attempting a remote directory listing:
rsh -l dstage hostname ls
Chapter 4. Configuring

81

4. Configure the parallel engine for remote shell (rsh) or secure shell (ssh). To run parallel jobs on remote hosts, you must use a remote shell script. A sample script named remsh.example is provided for this purpose. The script is located in the PXEngine\etc folder. a. Copy the sample script file, and rename it remsh. b. Edit the script file to include the name of the dstage user:
#!/bin/sh # Example $APT_ORCHHOME/etc/remsh rsh -l dstage "$@"

5. Configure the distribute-component script, which is located in the PXEngine\etc directory. This script installs and removes the PXEngine component binaries on remote compute nodes. This script enables jobs that contain compiled PX transforms to copy their transformer binaries to the remote nodes. a. Make a backup copy of the distribute-component script file. b. Edit the script file to include the name of the dstage user:
# The user (optional) # theUser=dstage

c. Save the changes.

C++ compilers for job development


Before you successfully run IBM WebSphere DataStage or IBM WebSphere QualityStage, you must install a C++ compiler. The job compilation process uses it to compile parallel jobs with transformer stages, buildop components, and some lookup stages. The compiler must be specific to your operating system where you install the IBM Information Server engine. For some compilers, each developer needs an individual license at the time that the developer compiles the job with the Designer client. The maximum number of simultaneous processes that compile DataStage jobs determines the number of licenses. Install only one compiler on each engine for development environments. For production environments, you do not need a C++ compiler, but some operating systems require additional C++ runtime libraries. For the list of C++ compilers, go to the system requirements for your operating system: www.ibm.com/software/data/infosphere/info-server/overview/ requirements.html.

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. You set the same environment variables for both Windows and UNIX or Linux platforms. You can set the environment variables by using the WebSphere DataStage Administrator client. 1. Click Start All Programs IBM Information Server WebSphere DataStage and QualityStage Administrator, and 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.

82

Planning, Installation, and Configuration Guide

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 IBM WebSphere DataStage and QualityStage Parallel Job Advanced Developer Guide for a complete listing of environment variables you can set

Network settings
APT_IO_MAXIMUM_OUTSTANDING If your 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. 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 APT_COPY_TRANSFORM_OPERATOR environment variable to true to enable Transformer stages to work in this environment.IBM WebSphere DataStage and QualityStage users must have the appropriate privileges to create project directory paths on all the remote nodes at runtime. This environment variable is set to false by default.

Chapter 4. Configuring

83

Job monitoring
By default, the job monitor uses time-based monitoring in the IBM WebSphere DataStage and QualityStage 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 is also overridden.

Transport block size


To automatically calculate the block size for transferring data internally as job runs, set the APT_AUTO_TRANSPORT_BLOCK_SIZE to True. Alternately, you can specify a specific block size. By default, this environment variable is set to 32768.

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 different directory by using the environment variable TMPDIR.

Configuring the parallel engine (Linux, UNIX)


The following tasks must be performed to configure the parallel engine for Linux and UNIX

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 100 processes on each processing node. Large systems and symmetric multiprocessing (SMP) servers require more than 100 processes. Complete the following steps on each computer that acts as a processing node in your parallel environment. Procedure

84

Planning, Installation, and Configuration Guide

To set the number of processes for parallel jobs: 1. Issue this command to determine the current setting for the number of processes:
lsattr -E -l sys0 | grep maxuproc

2. If the value of the maxuproc parameter is less than 100, enter this command to increase it to 100
chdev -l sys0 -a maxuproc=100

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 100 on all cluster nodes.
dsh -a chdev -l sys0 -a maxuproc=100

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 steps below for each user on each processing node in your parallel environment.
Table 24. Per-user kernel parameter values. The description and value to which to set each of the four per-user kernel parameters is shown. 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. The maximum amount of physical memory that a users process can use. 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. 64 MB (131,072 512-byte blocks) or more.

stack rss

Procedure To set per-user kernel parameters for parallel jobs: 1. Run the following command to determine the value of the memory size parameters for a user:
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 root.

Chapter 4. Configuring

85

3. Set the parameters for each user as defined by the values in Table 24 on page 85. The command has the form:
chuser param=value user_name

For example:
chuser chuser chuser 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

Users whose per-user kernel parameters have changed must log out and log in again for the changes to take effect.

Setting the system paging space for the parallel engine


For parallel jobs that process large amounts of data, your system must have the minimum settings for the paging space. Attention: Resetting the system paging space is potentially destructive to the processing environment. A system administrator with root privileges must perform this task. Setting the system paging space for the parallel engine (AIX): For parallel jobs that process large amounts of data, your system must have the minimum settings for the paging space. Prerequisites Resetting the system paging space is potentially destructive to the processing environment. A system administrator with root privileges must perform this task. About this task The minimum amount of paging space to run parallel jobs is 500 MB per processor for systems with fewer than 20 processors and 1 GB per processor for systems with 20 or more processors. The design of the parallel jobs and the number of jobs that you plan to run at one time affects the system 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 To set the paging space on an IBM AIX system: 1. Run the lsps command on each node or workstation to display the current size of the paging space:
lsps -a

86

Planning, Installation, and Configuration Guide

The lsps command displays information in the form shown in this table.
Table 25. 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 information about setting the paging space for your system. Setting the system paging space for the parallel engine (Linux): For parallel jobs that process large amounts of data, your system must have the minimum settings for the paging space. Prerequisites Resetting the system paging space is potentially destructive to the processing environment. A system administrator with root privileges must perform this task. About this task The minimum amount of paging space to run parallel jobs is 500 MB per processor for systems with fewer than 20 processors and 1 GB per processor for systems with 20 or more processors. The design of the parallel jobs and the number of jobs that you plan to run at one time affects the system 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 See the documentation for your Linux distribution for information about setting the paging space for your system.

Updating the /etc/magic file


Edit the /etc/magic file to include data-set descriptor files for the parallel engine. About this task The UNIX file command examines a file to classify it by type. The command reads the /etc/magic file to identify files that have a magic number. The magic number is a constant that specifies the file type.

Chapter 4. Configuring

87

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 root. 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

where file_name is the name of a data-set descriptor file. For example, if you enter file t1.ds, the command should return:
t1.ds: IBM Information Server parallel engine dataset descriptor

Configuring the parallel engine (Windows)


The following tasks must be performed to configure the parallel engine for Windows.

Setting environment variables for Microsoft Visual Studio .NET 2003 C++ compiler (Windows)
Before you create and run parallel jobs, you must set the APT_COMPILEOPT and APT_LINKOPT environment variables for each project. Procedure This task must be performed on development computers where you create and run parallel jobs. You must set the environment variables only on production computers that recompile the jobs. To set the environment variables for Microsoft Visual Studio .NET 2003: 1. Select Start IBM Information Server IBM WebSphere DataStage and QualityStage Administrator, and then log in to the Administrator client. 2. Select Projects Properties Environment. 3. Select Parallel Compiler APT_COMPILEOPT and delete the string -W/Zc:wchar_t- from the end of the existing setting in the Value field. 4. Select Parallel Compiler APT_LINKOPT and delete the string -W/Zc:wchar_t- from the end of the existing setting in the Value field.

Setting required environment variables for Microsoft Visual Studio .NET 2005 compiler (Windows)
Before you create and run parallel jobs, you must update the LIB and INCLUDE environment variables so that the compiler can find the SDK library and the include files. Before you begin Download the SDK from the Microsoft Web site.

88

Planning, Installation, and Configuration Guide

Procedure To enable the compiler to find the SDK library and the include files: 1. From the Windows Control Panel, select System Advanced Environment Variables System Variables. 2. Set the LIB environment variable to the location of the library directory for the SDK. A typical location is C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Lib. 3. Set the INCLUDE environment variable to the location of the include directory for the SDK. A typical location is C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include. 4. Save the settings and restart the computer.

Configuring the Windows registry: increasing heap size


If your parallel engine is installed on a Microsoft Windows 2003, Standard or Enterprise edition system, then you can increase the heap size to improve performance. About this task You increase the size of the non-interactive desktop heap by editing the SharedSection parameter in the HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet\Control\Session Manager\SubSystems key. The SharedSection parameter specifies the system and desktop by using the following format:
SharedSection=xxxx,yyyy,zzzz

The value xxxx defines the maximum size of the system-wide heap (in kilobytes), yyyy defines the size of the per desktop heap, and zzzz defines the size of the desktop heap associated with a non-interactive Windows station. Procedure To increase the size of the non-interactive desktop heap, do the following steps: 1. Select Start Run regedit.exe to start the Registry Editor. 2. Browse to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Control\Session Manager\SubSystems key. 3. In the right pane of Registry Editor, click Windows. 4. Select Edit Modify. 5. In the Edit String window, locate the SharedSection parameter string in the Value field. 6. Change the last SharedSection parameter from 512 to 1024: Windows SharedSection=1024,3072,1024 7. Click OK. 8. Close the Registry Editor.

Configuring Windows: changing swap area size


If your parallel engine is installed on a Microsoft Windows 2003, Standard or Enterprise edition system, then you can change the size of the swap area to improve performance. Procedure To change the size of the swap area, do the following steps:
Chapter 4. Configuring

89

Select Start My Computer to open My Computer. In the left panel, under System Tasks, select View System information. In the System Properties window, select the Advanced tab. In the Performance section of the Advanced panel, click Settings to open the Performance Options window. 5. Select the Advanced tab. 6. In the Virtual Memory section, click Change to open the Virtual Memory window. 1. 2. 3. 4. 7. Change the Maximum size to the value that is recommended in the bottom panel. 8. Click Set. 9. Click OK to close each window.

Configuring the Windows registry: TCP/IP buffers and connections


If your parallel engine is installed on a Microsoft Windows system, then you should check the TCP/IP buffers and connections, and change them if necessary. About this task You can check to see if the following two keys are defined in your registry: v MaxUserPort v TcpNumConnections These keys are not added to the registry by default. The TcpNumConnections has a major impact on the number of concurrent osh processes allowed. Procedure To check, and if necessary edit or add the registry keys, do the following steps: 1. Select Start Run regedit.exe to start the Registry Editor. 2. Browse to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Services\Tcpip\Parameters keys. 3. If the MaxUserPort and TcpNumConnections are not there, then add them by doing the following steps: a. Select Edit New. b. Add the MaxUserPort key by setting the following fields: v Value Name: MaxUserPort v Value Type: DWORD v Value data: 65534 v Valid Range: 5000-65534 (decimal) v Default: 0x1388 (5000 decimal) v Description: This parameter controls the maximum port number that is used when a program requests any available user port from the system. Typically, ephemeral (short-lived) ports are allocated between the values of 1024 and 5000 inclusive. c. Select Edit New d. Add the TcpNumConnections key by setting the following fields: v value Name: TcpNumConnections v Value Type: DWORD

90

Planning, Installation, and Configuration Guide

Value data: 65534 Valid Range: 0 - 0xfffffe (65534 decimal) Default: 0xfffffe Description: This parameter limits the maximum number of connections that TCP can have open at the same time. 4. Close the Registry Editor. 5. Restart the computer. v v v v

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 WebSphere DataStage to run on all processing nodes that function as DB2 servers. Procedure To configure IBM WebSphere DataStage to access DB2 servers, include a node definition for each DB2 server node in the configuration file. Also, complete the following steps. Running the DB2 configuration script: Use the DB2 configuration script to configure access to DB2 databases. Procedure To run the configuration script: From the Linux or UNIX command line, run the $APT_ORCHHOME/bin/ db2setup.sh script once for each DB2 database that users will access. Pass the database name as an argument. For example, the following command calls db2setup.sh to configure access the database db2db:
db2setup.sh db2db

Granting user privileges to run DB2 Enterprise stage jobs: You must grant privileges to each user who runs jobs that contain the DB2 Enterprise stage. Prerequisites You must have DBADM privileges to complete this task. Procedure To grant user privileges: Run the $APT_ORCHHOME/bin/db2grant.sh script once for each user. Use the following syntax:
db2grant.sh database_name user_name
Chapter 4. Configuring

91

Accessing a remote DB2 server from DB2 Enterprise stages: You use a DB2 client to connect from a DB2 Enterprise stage to a remote DB2 server. See Remote connection in the IBM WebSphere DataStage and QualityStage Connectivity Guide for IBM DB2 Databases. Configuring the DB2 system: The DB2 server can be configured in many ways on your system. The DB2 administrator typically follows this procedure to configure DB2 and WebSphere DataStage to communicate. Procedure To configure the DB2 system: 1. Install IBM DB2 and make sure it is working properly. 2. Grant the WebSphere DataStage users SELECT privileges on the DB2 system tables syscat.nodegroupdef, syscat.tablespaces, and syscat.tables. 3. Make the file db2nodes.cfg readable by the WebSphere DataStage administrative user. 4. WebSphere DataStage runs many processes for each job. This can require the system administrator to modify DB2 resources, configuration parameters, and manager configuration parameters of your system. See the DB2 information center for more information. 5. 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

Configuring DB2 users: To access IBM WebSphere DataStage, parallel jobs use an operating system user ID to connect to the DB2 server. Therefore, user IDs that invoke DB2 read operators must have the SELECT privilege on the tables that they access, and user ISs that invoke DB2 write operators must have INSERT privileges on the tables that they access. About this task The following procedure configures a WebSphere DataStage user to access the DB2 database. Either a system administrator or a WebSphere DataStage user can perform this task. Procedure To configure DB2 users: 1. Set the DB2INSTANCE environment variable to the user name of the owner of the DB2 instance. DB2INSTANCE determines the location of thedb2nodes.cfg file, as follows:
~owner_user_name/sqllib/db2nodes.cfg

92

Planning, Installation, and Configuration Guide

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 WebSphere DataStage parallel configuration file. For example, if you set DB2INSTANCE to Janet, this is the location of db2nodes.cfg file:
~Janet/sqllib/db2nodes.cfg.

2. 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 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 To grant access to the Oracle parallel server: 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 To grant privileges to users that use the Oracle Enterprise stage: 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.

Chapter 4. Configuring

93

3. Add ORACLE_HOME/bin to your PATH and ORACLE_HOME/lib to your operating systems 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) 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 After installing the Teradata Tools and Utilities: 1. Ensure that the Teradata Parallel Transporter is installed and that the following environment variables are set in the /etc/services file: v
AIX

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

94

Planning, Installation, and Configuration Guide

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 To create a Teradata user: 1. Run these Basic Teradata Query (BTEQ) commands to create a user account that is stored in the terasync table.
CREATE USER user_name FROM database_name 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 in order 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 To configure access to Informix XPS databases: 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.
Chapter 4. Configuring

95

5.

AIX

Set the LIBPATH environment variable as follows:

LIBPATH=$APT_ORCHHOME/lib:$INFORMIXDIR/lib:dirname $DSHOME/branded_odbc/ lib:$DSHOME/lib:$DSHOME/uvdlls:$DSHOME/java/jre/bin/classic:$DSHOME/java/j re/bin:$INFORMIXDIR/lib:$INFORMIXDIR/lib/cli:$INFORMIXDIR/lib/esql

Configuring access to ODBC data sources


You can configure ODBC access on Windows, Linux, and UNIX operating systems
Windows If you installed ODBC drivers, you must configure the drivers to access ODBC data sources. Refer to your ODBC driver vendor documentation for information on how to configure the driver.

Linux

UNIX

You edit the dsenv, odbc.ini, and uvodbc.config files to set up access to ODBC data sources. The three files are located in the $DSHOME directory. A copy of the uvodbc.config file is also placed in each project directory. Non-wire protocol drivers require different setup information than 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 Data Direct Drivers Reference manual, which is available as a PDF file (odbcref.pdf), which is in the $DSHOME/Server/branded_odbc/books/odbc directory. Also review the odbcread.me file in the branded_odbc directory. There is also an HTML file in the branded_odbc/odbchelp directory.

Setting the library path in the dsenv file


The IBM Information Server engine has a centralized file for storing environment variables called dsenv in $DSHOME. $DSHOME identifies the WebSphere DataStage installation directory. The default directory is /opt/IBM/ InformationServer/Server/DSEngine. About this task You might need to add new environment variables as you configure WebSphere DataStage to connect to different databases by using ODBC drivers and the database APIs. Any environment variables you need for interactive use of ODBC drivers to make a connection to an ODBC data source must be added to the dsenv file. This lets the WebSphere DataStage server inherit the proper environment for ODBC connections. For a connection that uses a wire protocol driver, there are no changes required to the dsenv file. Procedure To set the library path for a connection that uses a non-wire protocol driver: 1. Specify the following information in the dsenv file: v Environment variables for the database client software v Database home location v Database library directory

96

Planning, Installation, and Configuration Guide

Table 26. Names of the library path environment variable, by operating system Operating system IBM AIX Linux Library path environment variable LIBPATH LD_LIBRARY_PATH

The following examples show typical entries for commonly used databases. They vary slightly depending on your operating system. Refer to your 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

Oracle 9i
ORACLE_HOME=/space/oracle9i LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib:$ORACLE_HOME/rdbms/lib export LD_LIBRARY_PATH ORACLE_SID=WSMK5 export ORACLE_HOME ORACLE_SID

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

2. Stop and restart the WebSphere DataStage server whenever you edit dsenv.

Configuring the .odbc.ini file


The .odbc.ini file must provide information about connecting to all of the databases and database client applications in your system. The /opt/IBM/InformationServer/branded_odbc/IBM_Tools directory contains example odbc.ini files for each supported Linux and UNIX platform. Use the contents of these files to create the .odbc.ini file for the $DSHOME directory.

Chapter 4. Configuring

97

Specifying data source names in the uvodbc.config file


The uvodbc.config file must specify the ODBC data source name (DSN) for each database in the system. About this task A copy of the uvodbc.config file is also in each project directory. For example, the default path for projects on Linux is /opt/IBM/WDIS/Server/Projects. These copies are useful where you configure data sources that are known to some projects but not others. By default, WebSphere DataStage searches the current project directory for a uvodbc.config file and, if it finds one, uses this file instead of $DSHOME. Procedure To specify data source names: 1. Use this syntax to add entries to the uvodbc.config file:
<DSN_name> DBMSTYPE = ODBC

where DSN_name is the ODBC DSN. this should be the same name as specified in the .odbc.ini file. The space on each side of the equal sign is required. 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 <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 To create and bind a package to a data source name: 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.

98

Planning, Installation, and Configuration Guide

Configuring other ODBC drivers


You can use ODBC drivers from other vendors to connect to data sources. You might require to connect to a database not supported by the Data Direct 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 WebSphere DataStage drivers, and you must perform some reconfiguration to switch between the two types. To configure other ODBC drivers: 1. Install the ODBC manager and drivers. Use the documentation that the driver vendor provides. 2. Configure the system 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 DSN, driver name, and log in information. c. In the uvodbc.config file, specify the data source name (DSN) to use to connect to the database. 3. Include the shared library libodbc.sl for the ODBC Manager in the WebSphere DataStage load library path. Do this by editing dsenv and ensuring that the path to the ODBC Manager precedes that to $DSHOME/../branded_odbc/lib in the shared library path environment variable. 4. After you install and configure the driver, test the connectivity. To use the Data Direct drivers again, reverse the procedure in Step 3 and ensure that the WebSphere DataStage ODBC driver library precedes any other ODBC driver libraries.

Testing ODBC driver connectivity


After you configure ODBC connectivity, test the configuration to verify your connection to the data source. Procedure To test the connectivity of the ODBC connections that you defined for WebSphere DataStage: 1. Change directories to $DSHOME and set up the environment by running the following command:
. ./dsenv

2. Enter this command to start the WebSphere DataStage server shell:


./bin/dssh

3. Enter this command to log in to the project:


LOGTO project_name

where project_name is case-sensitive. 4. Enter this command to obtain a list of available data source names:
DS_CONNECT

5. Enter this command to test the connection:


DS_CONNECT dsn

where dsn is the data source name of the connection to test. 6. Enter your user name and password to connect to the specified database.
Chapter 4. Configuring

99

7. Enter .Q to quit the connection.

Stopping and starting the engine


You must stop and then restart the IBM Information Server engine after you complete certain tasks such as editing the dsenv file on Linux or UNIX, modifying the uvconfig file, or finishing the installation of a tier. Procedure To stop and start the engine: v
Linux UNIX

1. Log in as root or the 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

Windows

1. In the Windows control panel, open the DataStage Control Panel. 2. Click Stop all services. Wait until the services have stopped. 3. Click Start all services.

100

Planning, Installation, and Configuration Guide

Chapter 5. 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.

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 directory specified with the -is:tempdir parameter, or to the following default directory if you did not use the -is:tempdir parameter:
Windows

%TEMP%\ibm_is_logs
Linux UNIX

/tmp/ibm_is_logs

After a successful installation, a .zip file of the log files that are created during the installation process is saved to the IBM 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 temporary directory.

Troubleshooting command-line scripts


Certain characters in user names or passwords might cause command-line scripts to fail. When you create directory names, user names, and passwords, do not include any spaces or any of the following characters: % ^ & ) < > \ | ! $ Each operating system has its own requirements. Review your operating system documentation for rules about user names and passwords. You can find naming conventions for IBM DB2 database systems and IBM WebSphere Application Server products in the documentation for those products. See the information about DB2 general naming rules in the DB2 Version 9 for Linux, UNIX, and Windows Administration Guide: Implementation.

Verifying uninstallation of IBM Information Server


If an installation fails, verify that a previous installation has been completely uninstalled.

Symptoms
101

Copyright IBM Corp. 2005, 2008

Installation fails on a computer that has been used for a previous IBM Information Server installation.

Causes
Previous installations are not completely removed. A typical cause is not restarting the computer after the uninstallation process is complete.

Environment
This advice applies to all operating systems.

Resolving the problem


Completely removing previous installations, including failed installations, of IBM Information Server is required before you install IBM Information Server. Before you reinstall IBM Information Server, follow these steps to completely remove previous installations of IBM Information Server: 1. Perform the uninstallation process to remove IBM Information Server. 2. Delete the installation directory and any remaining contents. 3. Restart your computer.

Ignoring runtime error during uninstallation


A known problem causes an unimportant error message to be displayed during the uninstallation process.

Symptoms
During the uninstallation process, the following error message is displayed when the ASBAgent is being removed:
This application has requested the Runtime to terminate it in an unusual way

Causes
This is a known problem with the Visual C++ Runtime .dll file (msvcrt.dll), which is documented in the Microsoft Knowledge Base.

Environment
This advice applies to the Microsoft Windows XP operating system.

Resolving the problem


Ignore this error message. The uninstallation process completes successfully with no errors encountered in the process.

Verifying that sufficient disk space is available


If an installation fails, confirm that your system has sufficient free disk space in the temporary directory, which is required by IBM Information Server, in addition to the disk space required for the installed components.

Symptoms
102
Planning, Installation, and Configuration Guide

Installation fails with an error message similar to the following messages: v


Windows

WARNING: C: has insufficient space to install the items selected. 1200.4 MB additional space would be needed to install the selected items.

Linux

UNIX

WARNING: / partition has insufficient space to install the items selected. 1200.4 MB additional space would be needed to install the selected items.

Causes
The drive or partition does not have enough free disk space in the temporary directory in addition to the disk space required for the installed components.

Diagnosing the problem


When the IBM Information Server installation program determines that there is insufficient free disk space for a successful installation, the installation program only identifies which disk or file system has insufficient space, not which directories.

Resolving the problem


Verify that the required free disk space is available for the installation: 1. Analyze your disk space and plan your installation.
Windows

v In the Explorer window, right-click the drive or folder and click Properties to view the disk space.
Linux UNIX

v Type this command to view the file system space in KB:


df -k

2. Ensure that the temporary directory has 500 MB free disk space. (See the system requirements for the exact amount). If your temporary directory has less than the required free disk space, use the -is:tempdir command to designate a temporary directory that has the required free disk space. Your temporary directory does, however, require some additional free space, even when you use the -is:tempdir command to designate another temporary directory. 3. Ensure that you have the required free disk space to install IBM Information Server and the IBM Information Server components. 4. If you are planning a large deployment, install the metadata repository and the IBM WebSphere Information Analyzer analysis database to a location that has more disk space.

Resolving incompatible Java Runtime Executable error (Linux, UNIX)


If an installation fails, confirm that an incompatible Java Runtime Executable (JRE) is not installed.

Symptoms
Installation fails.

Causes
Chapter 5. Troubleshooting installations

103

Java libraries that are not installed by IBM Information Server are installed on the target installation computer.

Environment
This advice applies to Linux and UNIX operating systems.

Diagnosing the problem


Symptoms vary by environment and configuration and can be difficult to diagnose.

Resolving the problem


Confirm that an incompatible JRE version is not installed before you reinstall IBM Information Server: Type the following command: which java. If the location of Java is returned, remove it from the system path. Repeat steps 1 and 2 until no Java JREs are identified. Type the following commands to find libraries that belong to an installed JRE: find /usr/lib -name "libjvm.*" and find /usr/local/lib -name "libjvm.*. If the results include libraries, uninstall the Java JRE to remove all of the Java libraries in the /usr/lib and /usr/local/lib directories. 5. Start the installation. 1. 2. 3. 4.

Resolving incompatible Java Runtime Executable error (Windows)


If an installation fails, confirm that an incompatible Java Runtime Executable (JRE) is not installed.

Symptoms
Installation fails.

Causes
Java libraries that are not installed by IBM Information Server are installed on the target installation computer.

Environment
This advice applies to Windows operating systems.

Diagnosing the problem


Symptoms vary by environment and configuration and can be difficult to diagnose.

Resolving the problem


Confirm that an incompatible JRE version is not installed before you reinstall IBM Information Server: 1. Open a command prompt window. 2. Ensure that the JAVA_HOME environment variable is not set by typing the following command: set JAVA_HOME.

104

Planning, Installation, and Configuration Guide

3. Ensure that Java is not on the system path by typing the following command: java. 4. If the command is recognized, modify your system path to exclude it. 5. Start the installation from the same command prompt window in which you verified that the Java JRE is not present in the environment.

Resolving failed installations for Red Hat Linux systems


Installation on 32-bit and 64-bit Red Hat Enterprise Linux Advanced Server 4 and Red Hat Enterprise Linux 5 Advanced Platform systems fails when the required 32-bit packages are not installed.

Symptoms
Installation fails with error messages. The following table includes the missing package name and the corresponding error message:
Table 27. Package names and installation error messages when the package is not found 32-bit package name v glibc-2.3.4-2.9 Error message during installation when package is not found warning: /etc/localtime saved as /etc/localtime.rpmsave warning: /etc/ld.so.conf saved as /etc/ld.so.conf.rpmsave error: %postun(glibc-2.3.4-2.25.i686) scriptlet failed, exit status 255 *** glibc detected *** double free or corruption (fasttop): 0x09796e40 *** error: %trigger(redhat-lsb-3.0-8.EL.i386) scriptlet failed, exit status 0 The installer is unable to run in graphical mode. Try running the installer with the -console or silent flag.

v xorg-x11-libs-6.8.2-1.EL.13.6 v xorg-x11-deprecated-libs-6.8.21.EL.13.6 v xorg-x11-libs-6.8.2-1.EL.13.6 v libXmu.so.6 v libXt.so.6 v libX11.so.6 v libXtst.so.6 v libXp.so.6 v libSM.so.6 v libICE.so.6 v libXext.so.6 v libstdc++-3.4.3-22.1

./bin/uvsh: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory ESuite10092: One or more assemblies did not install correctly Error while loading the shared libraries:libdl.so.2 :cannot open shared object file: No such file or directory

v compat-libstdc++-33-3.2.3-47.3 v libdl.so.2

Chapter 5. Troubleshooting installations

105

Table 27. Package names and installation error messages when the package is not found (continued) 32-bit package name v libpthread.so.0 v libc.so.6 v Error message during installation when package is not found No Java Runtime Environment (JRE) was found in this system.

Causes
IBM Information Server runs as a 32-bit application on 64-bit Red Hat Enterprise Linux Advanced Server 4 and Red Hat Enterprise Linux Advanced Platform 5. Successful installation and operation requires installation of the 32-bit requirements on these Red Hat Linux systems, including packages and compilers.

Environment
This advice applies to Red Hat Enterprise Linux Advanced Server 4 and Red Hat Enterprise Linux 5 Advanced Platform operating systems.

Resolving the problem


Review the IBM Information Server Version 8.1 system requirements and ensure that your system meets the requirements for installing IBM Information Server on Red Hat Enterprise Linux Advanced Server 4 and Red Hat Enterprise Linux 5 Advanced Platform operating systems. After you install any missing packages or libraries, reinstall IBM Information Server.

Directory and user permissions


If installation fails, confirm that the users who install IBM Information Server have read and write permissions for the IBM Information Server installation directories. The following IBM Information Server installation directories require read and write permissions by the specified users.
Table 28. Required directory permissions Installation components IBM Information Server Directories Installation parent directories:
Linux UNIX

Permissions Read or read and write

Users
Linux UNIX

v Root user
Windows

v /opt v /opt/IBM
Windows

v Local administrator or domain administrator with local administrator privileges

v C:\ v C:\IBM

106

Planning, Installation, and Configuration Guide

Table 28. Required directory permissions (continued) Installation components IBM Information Server Directories Installation directory:
Linux UNIX

Permissions Read and write

Users
Linux UNIX

v Root user
Windows

v /opt/IBM/ InformationServer
Windows

v C:\IBM\ InformationServer Engine tier and IBM WebSphere DataStage Installation parent directories:
Linux UNIX

v Local administrator or domain administrator with local administrator privileges Read or read and write WebSphere DataStage administrator (default user name is dsadm)

v /opt v /opt/IBM
Windows

v C:\ v C:\IBM Engine tier and IBM WebSphere DataStage Installation directory:
Linux UNIX

Read and write

WebSphere DataStage administrator (default user name is dsadm)

v /opt/IBM/ InformationServer
Windows

v C:\IBM\ InformationServer IBM Information Server Temporary directory, and any temporary directories specified with the -is:tempdir command Read and write
Linux UNIX

v Root user v Database instance owner (default user name is db2inst1)


Windows

v Local administrator or domain administrator with local administrator privileges v Database owner (default user name is db2admin)

Chapter 5. Troubleshooting installations

107

Table 28. Required directory permissions (continued) Installation components Metadata repository Directories Database server directories:
Linux UNIX

Permissions Read or read and write

Users
Linux UNIX

v /opt v /opt/IBM v /opt/IBM/db2/V9/


Windows

v Database instance owner (default user name is db2inst1)


Windows

v Database owner (default user name is db2admin)

v C:\ v C:\IBM v C:\IBM\SQLLIB Metadata repository Database storage directories: Read and write
Linux UNIX Linux UNIX

v /opt/IBM/ InformationServer/ Repository


Windows

v Database instance owner (default user name is db2inst1)


Windows

v C:\DB2 WebSphere Application Server Installation directory:


Linux UNIX

v Database owner (default user name is db2admin) Read and write


Linux UNIX

v Root user
Windows

v /opt/IBM/WebSphere/ AppServer
Windows

v C:\IBM\WebSphere\ AppServer
AIX

v Local administrator or domain administrator with local administrator privileges

v /usr/IBM/WebSphere/ AppServer

User privileges
If installation fails, confirm that the users who install IBM Information Server have administrator privileges. You must be logged on as a user with administrator privileges to install IBM Information Server. v You must be logged on as the local administrator with read and write access to the IBM Information Server installation directories. A member of the domain administrator group can run the installation program only if that administrator also has local administrator privileges.
Windows Linux UNIX You must be logged on as the root user or use sudo to root to install IBM Information Server.

108

Planning, Installation, and Configuration Guide

Correcting errors with kernel parameter values


If an installation fails because of incorrect kernel parameter values, confirm the values and restart the installation process.

Symptoms
Installation fails with one or more of the following error messages:
Unable to create a new process Process number is too small Out of memory Stack overflow

Causes
Incorrect kernel parameter values. The Out of memory error message is an indication that physical memory is insufficient. For configurations that use IBM DB2, the optimum kernel parameters are suggested by the db2osconf utility, which is available after you install DB2.

Environment
This advice applies to Linux and UNIX operating systems.

Resolving the problem


v The resolution to these error messages can typically be achieved by modifying the kernel parameters to meet the minimum requirements for your system. v For all other configurations: Confirm that your system meets the minimum kernel requirements and installation system requirements.

Resolving connection problems


An installation can fail because of connection problems between IBM WebSphere Application Server on the services tier and the installation computer.

Symptoms
Installation fails when the Domain Name System (DNS) is unable to resolve system names and displays an error message that is similar to:
A communication failure occurred while attempting to obtain an initial context with the provider URL...

Causes
The communication between the installation computer and WebSphere Application Server on the services tier is not established. Connection to WebSphere Application Server uses the short host name or a host name that does not match the computers host name at the time WebSphere Application Server was installed. Or, the domain name mapping for short and long host names do not map to the same IP address.

Diagnosing the problem

Chapter 5. Troubleshooting installations

109

When the services tier is installed on hostname.domain, test the connection to the short and long host names by using the ping commands:
ping hostname ping hostname.domain

Resolving the problem


1. Ensure that the etc/hosts file is correctly configured with the short and long host names of the services tier computer. 2. Ensure that all necessary ports are open between the client, engine, and services tier computers. 3. Ensure that the host name that is used to access the services tier computer is the same host name configured on that computer at the time that WebSphere Application Server was installed. 4. Ensure that the localhost and the machine hostname are not both mapped to IP Address 127.0.0.1. Only the localhost should be mapped to IP 127.0.0.1. Heres an example of how these entries should appear in the etc/hosts file:
127.0.0.1 localhost.localdomain localhost xx.xx.xx.xx machinelonghostname machineshorthostname

Where xx.xx.xx.xx is the machines unique IP Address. 5. If the engine or services tier was installed on a computer with incorrectly configured host names, reinstall IBM Information Server.

Resolving WebSphere Application Server installation problems


Use this troubleshooting information when you install IBM WebSphere Application Server with IBM Information Server.

Symptoms
When you install WebSphere Application Server with IBM Information Server, the WebSphere Application Server installation fails.

Causes
This WebSphere Application Server installation problem is unrelated to the IBM Information Server installation or configuration.

Environment
This advice applies to Microsoft Windows environments.

Diagnosing the problem


If the WebSphere Application Server installation fails, review one of the following log files: v WebSphere Application Server log file: %TEMP%\log.txt v IBM Information Server installation log file:
Windows

%TEMP%\ibm_is_logs\isdump-operating_system-timestamp.zip
Linux UNIX

/tmp/ibm_is_logs\isdump-operating_system-timestamp.zip

110

Planning, Installation, and Configuration Guide

. Search for following error:


INSTCONFFAILED: Cannot create profile: The profile does not exist

Resolving the problem


Verify that the DEBUG variable is not set in your system environment variables. If the DEBUG variable is set: 1. Remove the DEBUG variable from your system environment variables. 2. Restart the computer. 3. Reinstall IBM Information Server. 4. After the installation is complete, reset the DEBUG variable.

Chapter 5. Troubleshooting installations

111

112

Planning, Installation, and Configuration Guide

Chapter 6. Removing IBM Information Server


It might be necessary to remove IBM Information Server from your computers for various reasons, such as upgrading to a newer computer or to clean up a test computer.

Removing IBM Information Server from your system (Windows)


You can use the Add or Remove Programs utility in the Windows Control Panel to remove the suite from your system. Before you begin To complete this task, you must log in as a local administrator or a domain administrator with local administrator privileges to the Windows system where the suite is installed. About this task Uninstalling always removes all of the tiers and products in an installation on a computer. There is no way to remove a single tier or a single product when they are installed on the same computer. If you installed the IBM DB2 database with the suite and the installation program created the metadata repository database, then the metadata repository database is dropped when IBM Information Server is removed. If you created the metadata repository database before you installed IBM Information Server, you must manually drop the metadata repository database. The default database name is xmeta. If you originally installed all of the tiers on a single computer, they are automatically uninstalled in the correct order. If you installed the tiers on multiple computers, you must uninstall the tiers in the following order: 1. Engine tier 2. Services tier 3. Metadata repository tier You can uninstall the client tier at any time. Procedure To remove IBM Information Server from Windows: 1. Use the Add or Remove Programs utility in the Windows Control Panel to remove the following software. a. Any add-on product modules such as IBM WebSphere DataStage Packs and MetaBrokers and bridges, which you installed separately from IBM Information Server. b. IBM Information Server. If multiple versions of WebSphere DataStage clients are installed on your computer and you want to use older versions of the WebSphere DataStage client, you must reinstall those clients after you uninstall WebSphere DataStage.
Copyright IBM Corp. 2005, 2008

113

2. Remove the following files from your system, if they still exist. When you uninstall, the installation program removes only the files that were created as part of the operation of IBM Information Server. In the following steps, C:\IBM\InformationServer is the directory where the suite was installed. Substitute the location where you installed the suite. You must manually remove these files if you plan to reinstall the suite. a. Delete the C:\IBM\InformationServer directory. b. If you used the IBM Information Server installation program to install WebSphere Application Server, remove the application server directory. The default directory is C:\IBM\WebSphere. c. If you used an existing installation of WebSphere Application Server, remove the profile that you created for the suite. d. If you used the IBM Information Server installation program to install DB2, remove the following directories: v \DB2Home. DB2Home is the directory where the DB2 database system is installed. The default directory is C:\IBM\sqllib. v x:\DB2, where x is the drive where you installed DB2. v C:\Documents and Settings\All Users\Application Data\IBM\DB2 v C:\Documents and Settings\All Users\Application Data\IBM\ DB2History 3. If you used the IBM Information Server installation program to install the DB2 server, delete the DB2 administrative user, the metadata repository user, and the analysis database user. 4. If you used the IBM Information Server installation program to install WebSphere Application Server, edit the vpd.properties file and delete all of the entries that contain references to the installation directory for the application server. The default directory for the file is C:\Windows. If the vpd.properties file is empty, delete the file. 5. Required: Restart your computer. To prevent problems, you must restart your computer after you uninstall the suite. If you attempt to reinstall the suite before restarting, the installation might fail. 6. Repeat steps 1 on page 113 - 5 on each computer in your topology to remove all of the tiers.

Removing application server profiles


If you used an existing installation of WebSphere Application Server to host the services tier, you must remove the IBM WebSphere Application Server profile that you created. If the suite installation program installed the application server, the profile is removed when you remove the suite from your computer. Procedure To remove profiles: 1. Click Start All Programs IBM WebSphere Application Server Profiles profileName Stop the server. profileName is the name of the profile to be deleted. 2. Open a Windows command prompt. 3. Change to the WASHome\bin directory. WASHome is the directory where the application server is installed. The default directory is C:\Program Files\IBM\WebSphere\AppServer.

114

Planning, Installation, and Configuration Guide

4. Run the following command.


wasprofile.bat -delete -profileName profile

profile is the name of the profile to be deleted. 5. Delete the directory for the profile. The directory is in the WASHome\profiles\ profileName directory.

Removing IBM Information Server from a command prompt (Windows)


You can uninstall IBM Information Server from your system by using the command prompt. You can also perform a silent uninstallation of the suite. Before you begin You must log in as a local administrator or a domain administrator with local administrator privileges to the Windows system where the suite is installed. About this task Uninstalling always removes all of the tiers and products in an installation on a computer. There is no way to remove a single tier or a single product when they are installed on the same computer. If you installed the IBM DB2 database with the suite, and if the installation program created the metadata repository database, then the metadata repository database is dropped when IBM Information Server is removed. If you created the metadata repository database before you installed IBM Information Server, you must manually drop the database. The default database name is xmeta. If you installed all of the tiers on a single computer, they are automatically uninstalled in the correct order. If you installed the tiers on multiple computers, you must uninstall the tiers in the following order: 1. Engine tier 2. Services tier 3. Metadata repository tier You can uninstall the client tier at any time. Procedure To remove IBM Information Server from Windows: 1. Use one of the following methods to open the command prompt and uninstall the suite:
Option Console mode uninstallation Description cd X:\IBM\InformationServer\_uninst\suite uninstall -console

Chapter 6. Removing IBM Information Server

115

Option Silent mode uninstallation

Description cd X:\IBM\InformationServer\_uninst\suite uninstall -silent On computers that host the services tier or engine tier, specify these additional options: -V -V -V -V ASB_USER=suite_admin_username ASB_PASSWORD=suite_admin_password APP_SERVER_USER=was_admin_username APP_SERVER_PASSWORD=services_admin_password

On each computer that hosts the client tier or the engine tier, specify this option if you did not use a previously installed MKS Toolkit: -V MKS_UNINSTALL_FLAG=true

These examples use the default installation path. If you installed the suite in a different directory, adjust the path to match your installation. If multiple versions of WebSphere DataStage and Quality Stage clients are installed on your computer and you want to use older versions of the WebSphere DataStage or Quality Stage clients, you must reinstall those clients after you uninstall WebSphere DataStage and QualityStage. 2. Remove the following files from your system, if they still exist. When you uninstall, the installation program removes only the files that were created as part of the operation of IBM Information Server. In the following steps, C:\IBM\InformationServer is the directory where the suite was installed. Substitute the location where you installed the suite. You must manually remove these files if you plan to reinstall the suite. a. Delete the C:\IBM\InformationServer directory. b. If you used the IBM Information Server installation program to install WebSphere Application Server, remove the application server directory. The default directory is C:\IBM\WebSphere. c. If you used an existing installation of WebSphere Application Server, remove the profile that you created for the suite. d. If you used the IBM Information Server installation program to install DB2, remove the following directories: v \DB2Home. DB2Home is the directory where the DB2 database system is installed. The default directory is C:\IBM\sqllib. v x:\DB2, where x is the drive where DB2 was installed. v C:\Documents and Settings\All Users\Application Data\IBM\DB2 v C:\Documents and Settings\All Users\Application Data\IBM\ DB2History e. If you used the IBM Information Server installation program to install the DB2 server, delete the DB2 administrative user, the metadata repository user, and the analysis database user. f. If you used the IBM Information Server installation program to install WebSphere Application Server, edit the vpd.properties file and delete all of the entries that contain references to the installation directory for the application server. The default directory for the file is C:\Windows. If the vpd.properties file is empty, delete the file. 3. Required: Restart your computer. You must restart your computer after uninstalling the suite to prevent problems. If you attempt to reinstall the suite before restarting, the installation might fail.

116

Planning, Installation, and Configuration Guide

4. Repeat steps 1-3 on each computer in your topology to remove all of the tiers.

Manually removing IBM Information Server (Windows)


If the Add or Remove Programs utility in the Microsoft Windows Control Panel fails to uninstall the suite, manually uninstall the suite. Before you begin Back up your system before manually uninstalling. You must log in as a local administrator or a domain administrator with local administrator privileges to the Windows system where the suite is installed to complete this task. You can only uninstall all tiers and all products on a computer. You cannot uninstall a single product or tier. Before you manually uninstall, on each computer in your installation, try to uninstall the suite by using the Add or Remove Programs utility in the Windows Control Panel. If that utility fails to uninstall the entire suite, you can follow the procedure below. You can also use this procedure to clean up any files that the uninstallation program does not automatically remove. Procedure To manually remove IBM Information Server: 1. On the computer where the engine tier is installed, remove IBM Information Server services. From a command prompt, run the following commands:
sc sc sc sc sc sc sc sc sc sc stop stop stop stop stop ASBAgent LoggingAgent DSEngine dsrpc dstelnet ASBAgent LoggingAgent DSEngine dsrpc dstelnet

delete delete delete delete delete

2. If you installed DB2 as part of the IBM Information Server installation, follow these steps: a. Remove the DB2 database system by using the Add or Remove Programs utility in the Windows Control Panel . If DB2 cannot be uninstalled by using the Add or Remove Programs utility, uninstall DB2 manually. b. Remove the DB2 administrator user from your operating system user accounts. The default user name is db2admin. c. Delete the following directories: v Delete the home directory for the DB2 administrator account. The default directory is C:\Documents and Settings\db2admin v Delete the installation directory. The default directory is C:\IBM\SQLLIB\ v Delete the DB2 data directory. The default directory is C:\DB2\. v Delete the C:\Documents and Settings\All Users\Application Data\IBM\DB2 and C:\Documents and Settings\All Users\Application Data\IBM\DB2History directories.
Chapter 6. Removing IBM Information Server

117

d. Remove the metadata repository database and analysis database users. The default user names are xmeta and iauser. e. Remove the GSK7 entries from the PATH environment variable. 3. If you used an existing installation of DB2, use the DB2 Control Center or a 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 or Microsoft SQL Server for the metadata repository database and the analysis database, manually drop the users, table spaces (Oracle) or databases (Microsoft SQL Server). The default table space or database names are xmeta and iadb. 5. On the computer where the services tier is installed, if you installed WebSphere Application Server as part of IBM Information Server, uninstall the application server. a. Uninstall WebSphere Application Server by using the Add or Remove Programs utility in the Windows Control Panel. If WebSphere Application Server cannot be uninstalled by using the Add or Remove Programs utility, manually uninstall WebSphere Application Server. b. Remove the following files and directories: v Delete the WebSphere Application Server installation directory. The default directory is C:\IBM\WebSphere\AppServer\. v Search for and delete all of the portdef.props file. The default location for this file is the home directory of the user who installed the suite. You might find several files that match the pattern portdef*.props files. Be sure to delete only the files that correspond to the installation that you are removing. 6. If you installed MKS Toolkit as part of the IBM Information Server installation, uninstall the MKS Toolkit by using the Add or Remove Programs utility in the Windows Control Panel . The MKS Toolkit is installed on all tiers. 7. On the computers where the client tier is installed, remove the following desktop shortcuts: Administrator Client.lnk, Designer Client.lnk, Console for IBM Information Server.lnk, and Web Console for IBM Information Server.lnk 8. On each computer in your installation, remove the following files and directories: a. Delete the IBM Information Server installation directory. The default directory is C:\IBM\InformationServer\. b. Back up your registry and then delete the \HKEY_LOCAL_MACHINE\ SOFTWARE\Ascential Software and \HKEY_LOCAL_MACHINE\ SOFTWARE\IBM\InformationServer registry keys. c. Delete the InstallShield registry directory: C:\Program Files\Common Files\InstallShield\Universal\IBM\InformationServer\ d. Delete the temporary log files for the installation program. Remove %TEMP%\ibm_is_logs and %TEMP%\ISInstall*. You can enter cd %TEMP% at a command prompt or type %TEMP% in the address bar of Windows Explorer to go to that directory. e. Delete the Windows Start menu shortcuts. The default directory is C:\Documents and Settings\All Users\Start Menu\Programs\IBM Information Server\. 9. Remove the IBM Information Server users and groups if they still exist and if you are not using them for other purposes.

118

Planning, Installation, and Configuration Guide

10. Restart your system. Microsoft Windows might not be able to remove some files and services until the system is restarted. Attention: Do not perform a new installation before restarting. If you reinstall before restarting, the new installation might fail.

Removing IBM Information Server from your system (Linux, UNIX)


You can remove the suite from your system with the product uninstallation program. Before you begin You must have root authority on the Linux or UNIX system to complete this task. About this task If you installed the IBM DB2 database with the suite, and if the installation program created a metadata repository database, then the metadata repository database is dropped when IBM Information Server is removed. If you created the metadata repository before you installed IBM Information Server, you must manually drop the database. The default database name is xmeta. If you originally installed all tiers on a single computer, they are automatically uninstalled in the correct order. If you installed tiers on multiple computers, you must uninstall the tiers in the following order: 1. Engine tier 2. Services tier 3. Metadata repository tier If you installed multiple engine tiers on one computer, you can uninstall one engine tier at a time. Procedure To remove the suite from Linux and UNIX: 1. Run the following commands to start the program that removes IBM Information Server.
cd /opt/IBM/InformationServer/_uninst/suite ./uninstall

This command launches the graphical uninstaller. You can also run in console mode by appending the -console parameter. 2. Follow the instructions in the wizard to remove the suite. 3. Remove the following files from your system, if they still exist. When you uninstall, the installation program removes only the files that were created as part of the operation of IBM Information Server. You must manually remove these files if you plan to reinstall the suite. a. Delete the directory where IBM Information Server was installed. The default directory for Linux is /opt/IBM/InformationServer, for AIX it is /usr/IBM/InformationServer. b. If you installed the application server by using the installation wizard, delete the application server directory. The default directory is /opt/IBM/WebSphere/AppServer.
Chapter 6. Removing IBM Information Server

119

c. If you installed the DB2 database system by using the installation program, remove the following directories: DB2 installation directory The default directory for Linux is /opt/ibm/db2/V9.5. The default directory for UNIX is /opt/IBM/db2/V9.5. 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 /~dasuser1 /das directory, where ~dasuser1 is the home directory of the DB2 administrator. For example, the default home directory of the DB2 administrator is typically /home/dasuer1. 4. If you used the IBM Information Server installation program to install the DB2 server, delete the DB2 administrative user, fenced user, instance owner, metadata repository user, and analysis database user. 5. If the application server was not installed by the suite installation program, you must remove the profile for the metadata server. 6. Repeat steps 1 on page 119 - 5 on each computer in your configuration to remove all of the tiers.

Removing application server profiles (Linux, UNIX)


If you used an existing installation of WebSphere Application Server to host the services tier, you must remove the WebSphere Application Server profile when you remove the suite from your system. If the suite installation program installed the application server, the profile is removed when you remove the suite from your system. Procedure To remove profiles from Linux and UNIX: 1. Open a Linux or UNIX shell prompt. 2. From a Linux or UNIX shell prompt, change to the WASHome/bin. WASHome is the directory where the application server is installed. The default directory is /opt/IBM/WebSphere/AppServer 3. Run the following command to delete the profile.
./wasprofile.sh -delete -profileName profile

profile is the name of the profile to be deleted. 4. Delete the directory for the profile. The directory is in the WASHome/profiles directory.

Removing IBM Information Server from a command prompt (Linux, UNIX)


You can remove the suite from your system with the product uninstallation program. Before you begin You must have root authority on the Linux or UNIX system to complete this task.

120

Planning, Installation, and Configuration Guide

About this task Uninstalling always removes all of the tiers and products that are on a computer. There is no way to remove a single tier or a single product. The only exception is if you are removing an engine tier from a computer where you originally installed multiple engine tiers. Then you can remove one engine tier at a time. If you installed the IBM DB2 database with the suite, and if the installation program created a metadata repository database, then the metadata repository database is dropped when IBM Information Server is removed. If you created the metadata repository database before you installed IBM Information Server, you must manually drop the metadata repository database. The default database name is xmeta. If you originally installed all of the tiers on a single computer, they are automatically uninstalled in the correct order. If you installed the tiers on multiple computers, you must uninstall the tiers in the following order: 1. Engine tier 2. Services tier 3. Metadata repository tier Procedure To remove the suite from Linux or UNIX: 1. Open the terminal and uninstall IBM Information Server by using one of the following methods:
Option Console mode uninstallation Silent mode uninstallation Description cd /opt/IBM/InformationServer/_uninst/suite ./uninstall -console cd /opt/IBM/InformationServer/_uninst/suite ./uninstall -silent -V ASB_USER=suite_admin_username -V ASB_PASSWORD=suite_admin_password -V APP_SERVER_USER=was_admin_username -V APP_SERVER_PASSWORD=was_admin_password

These examples use the default installation path. If you installed the suite in a different directory, adjust the path to match your installation. IBM Information Server is removed from your system. 2. Remove the following files from your system, if they still exist. When you uninstall, the installation program removes only the files that were created as part of the operation of IBM Information Server. You must manually remove these files if you plan to reinstall the suite. a. Delete the directory where IBM Information Server was installed. The default directory for Linux is /opt/IBM/InformationServer, for AIX it is /usr/IBM/InformationServer. b. If you installed the application server by using the installation wizard, delete the application server directory. The default directory is /opt/IBM/WebSphere/AppServer. c. If you installed the DB2 database system by using the installation program, remove the following directories:

Chapter 6. Removing IBM Information Server

121

DB2 installation directory The default directory for Linux is /opt/ibm/db2/V9.5. The default directory for UNIX is /opt/IBM/db2/V9.5. 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 /~dasuser1 /das directory, where ~dasuser1 is the home directory of the DB2 administrator. For example, the default home directory of the DB2 administrator is typically /home/dasuer1. 3. If you used the IBM Information Server installation program to install the DB2 server, delete the DB2 administrative user, fenced user, instance owner, metadata repository user, and analysis database user. 4. If you used an existing installation of the application server, remove the profile that you created for the suite.

Manually removing IBM Information Server (Linux, UNIX)


If a previous installation or uninstallation failed, you might need to manually uninstall the suite. You only uninstall manually after trying to use the product uninstallation program. Before you begin Back up your system before manually uninstalling. You must have root authority on the Linux or UNIX system to complete this task. Before you manually uninstall, try to uninstall the product by using the product uninstallation program. If that procedure fails to completely uninstall the suite, you can follow the procedure below. You can also use this procedure to clean up any files that the product uninstallation program does not remove. Removing the remaining files is important if you need to reinstall the suite. About this task Uninstalling always removes all of the tiers and products that are on a computer. There is no way to remove a single tier or a single product. The only exception is if you are removing an engine tier from a computer where you originally installed multiple engine tiers. Then you can remove one engine tier at a time. If you installed the IBM DB2 database with the suite, and if the installation program created a metadata repository database, then the metadata repository database is dropped when IBM Information Server is removed. If you created the metadata repository database before you installed IBM Information Server, you must manually drop the metadata repository database. The default database name is xmeta. Procedure To manually remove IBM Information Server from Linux or UNIX systems: 1. On the computer where the engine tier is installed, stop and remove these services:

122

Planning, Installation, and Configuration Guide

a. Change directories to the installation directory for the IBM Information Server engine. The default location is /opt/IBM/InformationServer/Server/ DSEngine. b. Source the dsenv file to set up the required environment variables. Enter the following command:
. ./dsenv

c. Stop the engine services by running the following command:


./bin/uv -admin -stop

d. Change directories to /opt/IBM/InformationServer. e. Stop the agents by running the following command:
./ABSNode/bin/NodeAgents.sh stop

f. Stop the metadata server by running the following command:


./ASBServer/bin/MetadataServer.sh stop

g. Remove the startup entries. The NodeAgents.sh and MetadataServer.sh files are started automatically during system start by symbolic links in the rc directory. On AIX and Linux, the directory is /etc/rc.d. To determine which entries to remove, run the following command:
find /etc -name "*" -print | xargs grep -i InformationServer

Remove all of the entries that contain 99ISF. h. Edit the /etc/services file, and search for and remove the dsrpc entry, which is similar to this entry:
dsrpc 31538/tcp # RPCdaemon DSEngine@/opt/IBM/InformationServer/Server/DSEngine

2.

If you installed DB2 as part of the IBM Information Server installation, you must remove DB2 from the computer on which you installed the metadata repository tier. Removing DB2 automatically removes the metadata repository database and the analysis database. a. On the computer where the metadata repository is installed, log in as the DB2 instance owner. This account is db2inst1 by default. b. Drop the databases by running the following commands:
db2 drop database xmeta db2 drop database iadb

This example uses the default database names: xmeta and iadb. If you used different names, replace xmeta and iadb with your database names. c. If you installed the DB2 database system as part of the installation of IBM Information Server and it is the only DB2 installation, uninstall the DB2 database system. d. Remove the remaining files:
rm rm rm rm rm rm rm -rf -rf -rf -rf -rf -rf -rf /tmp/db2* /tmp/dascrt* /var/db2 /home/dasusr1/das /home/db2inst1/db2inst1 /home/db2inst1/sqllib /opt/IBM/db2

This example uses the default paths and user accounts. Adjust your paths to match your system configuration. 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 you used during the suite installation.
Chapter 6. Removing IBM Information Server

123

f. If the /etc/inittab file exists and this is the only DB2 installation, edit the file, and search for and remove the fmc entry, which looks similar to this entry:
fmc:number:respawn:/opt/IBM/db2/V9/bin/db2fmcd #DB2 Fault Monitor Coordinator

3. If you used an existing installation of DB2, use the DB2 Control Center or a 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 or Microsoft SQL Server to create the metadata repository database and the analysis database, manually drop the databases. The default database names are xmeta and iadb. 5. On the computer where the services tier is installed, if you installed WebSphere Application Server, uninstall WebSphere Application Server. The following steps use the default location /opt/IBM/WebSphere/AppServer. If you installed the program to a different directory, specify your location instead of the default location. a. Run the uninstallation script:
/opt/IBM/WebSphere/AppServer/_uninst/uninstall

b. Edit the vpd.properties file, and remove and each line that references /opt/IBM/WebSphere/AppServer. The vpd.properties file is in one of these directories:
AIX

/usr/lib/objrepos
UNIX

/root c. Remove the remaining files from WebSphere Application Server. Attention: If you have another WebSphere Application Server installation, do not remove the files that are listed below. In the case of another installation, you must edit these files to remove the references to the uninstalled WebSphere Application Server.
Linux

Remove the following files and directories:


rm rm rm rm
UNIX

-rf /root/.WASRegistry -rf /root/portdef.props -rf /opt/IBM/WebSphere /tmp/log.txt

Remove the following files and directories:


rm rm rm rm -rf /.WASRegistry -rf /portdef.* -rf /opt/IBM/WebSphere /tmp/log.txt

6. On each computer in your installation, remove remaining files and directories: a. Delete the IBM Information Server installation directory. The default directory is /opt/IBM/InformationServer. b. Delete the InstallShield registry directory:
AIX

Delete the /usr/lib/objrepos/InstallShield/Universal/IBM/ InformationServer directory.

124

Planning, Installation, and Configuration Guide

UNIX

Delete the /root/InstallShield/Universal/IBM/InformationServer directory. c. Delete the temporary log files for the installation program.
rm -rf /tmp/ibm_is_logs rm -rf /tmp/ISInstall* rm -rf /.dshome

7. Remove the IBM Information Server users and groups if they still exist and if you are not using them for other purposes. To ensure that all processes have been terminated, restart each computer after you uninstall the suite.

Chapter 6. Removing IBM Information Server

125

126

Planning, Installation, and Configuration Guide

Product documentation
Documentation is provided in a variety of locations and formats, including in help that is opened directly from the product interface, in a suite-wide information center, and in PDF file books. The information center is installed as a common service with IBM Information Server. The information center contains help for most of the product interfaces, as well as complete documentation for all product modules in the suite. A subset of the product documentation is also available online from the product documentation library at publib.boulder.ibm.com/infocenter/iisinfsv/v8r1/ index.jsp. PDF file books are available through the IBM Information Server software installer and the distribution media. A subset of the information center is also available online and periodically refreshed at www.ibm.com/support/docview.wss?rs=14 &uid=swg27008803. 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 www.ibm.com/shop/publications/order. 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

Contacting IBM
You can contact IBM for customer support, software services, product information, and general information. You can also provide feedback on products and documentation.

Customer support
For customer support for IBM products and for product download information, go to the support and downloads site at www.ibm.com/support/us/. You can open a support request by going to the software support service request site at www.ibm.com/software/support/probsub.html.

My IBM
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/us/.

Copyright IBM Corp. 2005, 2008

127

Software services
For information about software, IT, and business consulting services, go to the solutions site at www.ibm.com/businesssolutions/us/en.

IBM Information Server support


For IBM Information Server support, go to www.ibm.com/software/data/ integration/support/info_server/.

General information
To find general information about IBM, go to www.ibm.com.

Product feedback
You can provide general product feedback through the Consumability Survey at www.ibm.com/software/data/info/consumability-survey.

Documentation feedback
You can click the feedback link in any topic in the information center to comment on the information center. You can also send your 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

128

Planning, Installation, and Configuration Guide

How to read syntax diagrams


The following rules apply to the syntax diagrams that are used in this information: v Read the syntax diagrams from left to right, from top to bottom, following the path of the line. The following conventions are used: The >>--- symbol indicates the beginning of a syntax diagram. The ---> symbol indicates that the syntax diagram is continued on the next line. The >--- symbol indicates that a syntax diagram is continued from the previous line. The --->< symbol indicates the end of a syntax diagram. v Required items appear on the horizontal line (the main path).
required_item

v Optional items appear below the main path.


required_item optional_item

If an optional item appears above the main path, that item has no effect on the execution of the syntax element and is used only for readability.
optional_item required_item

v If you can choose from two or more items, they appear vertically, in a stack. If you must choose one of the items, one item of the stack appears on the main path.
required_item required_choice1 required_choice2

If choosing one of the items is optional, the entire stack appears below the main path.
required_item optional_choice1 optional_choice2

If one of the items is the default, it appears above the main path, and the remaining choices are shown below.
default_choice required_item optional_choice1 optional_choice2

v An arrow returning to the left, above the main line, indicates an item that can be repeated.

Copyright IBM Corp. 2005, 2008

129

required_item

repeatable_item

If the repeat arrow contains a comma, you must separate repeated items with a comma.
, required_item repeatable_item

A repeat arrow above a stack indicates that you can repeat the items in the stack. v Sometimes a diagram must be split into fragments. The syntax fragment is shown separately from the main syntax diagram, but the contents of the fragment should be read as if they are on the main path of the diagram.
required_item fragment-name

Fragment-name:
required_item optional_item

v Keywords, and their minimum abbreviations if applicable, appear in uppercase. They must be spelled exactly as shown. v Variables appear in all lowercase italic letters (for example, column-name). They represent user-supplied names or values. v Separate keywords and parameters by at least one space if no intervening punctuation is shown in the diagram. v Enter punctuation marks, parentheses, arithmetic operators, and other symbols, exactly as shown in the diagram. v Footnotes are shown by a number in parentheses, for example (1).

130

Planning, Installation, and Configuration Guide

Product accessibility
You can get information about the accessibility status of IBM products. The IBM Information Server product modules and user interfaces are not fully accessible. The installation program installs the following product modules and components: v IBM Information Server Business Glossary Anywhere v IBM Information Server FastTrack v IBM Metadata Workbench v IBM WebSphere Business Glossary v IBM WebSphere DataStage and QualityStage v IBM WebSphere Information Analyzer v IBM WebSphere Information Services Director For more information about a products accessibility status, go to http://www.ibm.com/able/product_accessibility/index.html.

Accessible documentation
Accessible documentation for IBM 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.

Copyright IBM Corp. 2005, 2008

131

132

Planning, Installation, and Configuration Guide

Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the users 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: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Copyright IBM Corp. 2005, 2008

133

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 IBMs future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

134

Planning, Installation, and Configuration Guide

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 trademarks and certain non-IBM trademarks are marked on their first occurrence in this information with the appropriate symbol. IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ( or ), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at Copyright and trademark information at www.ibm.com/legal/ copytrade.shtml. The following terms are trademarks or registered trademarks of other companies: Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks 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

135

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. 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.

136

Planning, Installation, and Configuration Guide

Index Special characters


/etc/magic file editing 87 .ds files data set descriptor files 87 .odbc.ini file configuring 97 .xml files 35 .zip files installation log files 101

C
C++ compilers installing 82 capacity planning 22 client WebSphere Business Glossary Anywhere 64 clients described 6 cluster 76 clusters planning 10 COBOL copybook files installing 66 code pages 58 command prompt installing from 45 Compilers environment variables 88 component installer described 7 components enabling 63 components, installation tiers 4 configuring IBM Information Server 71 Match Designer 73 connectivity DB2 91 ODBC drivers 35 planning 20 testing ODBC drivers 99 console installation 45 creating data source names 73 DSNs 73 customer support 127

Numerics
32-bit systems 30, 32 64-bit application servers Red Hat 30 64-bit systems 30, 32 30

deployments examples 11 installation topologies 10 directories, planning 16 disk space requirements installation 102 documentation accessible 127 location 9 domain connections troubleshooting 109 DS_CONNECT 99 dsenv file sample entries 96 DSNs creating 73

E
encodings supported 58 engine starting and stopping 100 engine tier locations 39 overview 7 Enterprise stage jobs granting user privileges 91 environment variables 72 configuring 72 INCLUDE 88 LIB 88 Microsoft Visual Studio .NET 2003 C++ 88 Microsoft Visual Studio .NET 2005 C++ 88 parallel engine 83 setting 82 setting for WebSphere DataStage server 96 error messages troubleshooting 103, 104

A
accessibility 127 accounts, users 26 analysis databases locations 39 size 39 application server removing profiles Linux, UNIX 120 Windows 114 application servers 64-bit 30 planning 30 Red Hat 30 APT_COMPILEOPT environment variable 88 APT_LINKOPT environment variable 88 architecture engine 7 examples, installation 11 installation 10 services 8

D
data source names creating 73 specifying 98 data sources ODBC 96 database Match Designer 36 DB2 database system configuring WebSphere DataStage 91 DB2 Setup program running 91 DB2 Version 9.5 or 9.1 planning 33 DB2DBDFT environment variable configuring 92 DB2INSTANCE environment variable configuring 92 db2nodes.cfg file configuring 92

B
backing up planning 22 bind DB2 package 98 bridges installing 65 planning MetaBrokers 6 buildop components compilers 82

F
file systems, planning fix packs 63 16

G
grids planning 10 groups creating 71

H
hardware requirements 4

Copyright IBM Corp. 2005, 2008

137

heap size increasing 89 help online location

kernel parameters (continued) setting 84 troubleshooting errors 109 9

N
naming conventions projects 23 national language support supported encodings 58 networks planning 20 NLS configuring 71

I
IBM Information Server configuring 71 installing 41 ODBC drivers 35 removing console mode 115, 120 Linux, UNIX 119, 120 manually 117, 122 silent mode 115, 120 Windows 113, 115 uninstalling console mode 115, 120 Linux, UNIX 120 silent mode 115, 120 Windows 113, 115 IBM Information Server FastTrack configuring 76 IBM Information Server Web console described 8 IBM Metadata Workbench configuring 76 IBM support 127 information analysis planning 39 information centers locations 9 Information Server Business Glossary Anywhere client installation 64 Informix XPS configuring access 95 installation kernel parameter configuration 24 log files 101 planning 3 process overview 3 troubleshooting permissions 106 user privileges 108 installation wizard 59, 62 starting 44 upgrading 59 installing C++ compilers 82 command prompt (console or silent) 45 fix packs 63 IBM Information Server 41

L
layers 4 legal notices 133 LIB environment variable 88 LIBPATH environment variable configuring 92 library path environment variables WebSphere DataStage libraries 96 licenses .xml files 35 installing 63 using 35 log files installation 101 logical tiers 4 LOGTO 99

O
ODBC data source bind 98 vendor drivers 99 ODBC data sources configuring access 96 ODBC drivers testing connectivity 99 WebSphere DataStage and WebSphere QualityStage 35 ODBC, Windows 96 operators enabling 63 Oracle database configuring 93 Oracle databases metadata repositories 34 Oracle Enterprise stage job privileges 93 Oracle parallel server granting access 93 orchserver accounts creating 95

M
mainframe components installing 66 Mainframe jobs installing runtime libraries 67 mainframes running jobs 69 maintenance planning 22 massively parallel processing 80 configuring a node (UNIX and Linux) 77 configuring a node (Windows) 80 Match Designer configuring 73 database requirements database size 36 planning 36 maxuproc parameter setting 84 memory setting for parallel jobs 85 MetaBrokers and bridges installing 65 planning 6 metadata repositories DB2 databases 34 described 32 Microsoft SQL Server 34 Oracle databases 34 overview 8 owners, Oracle 34 Microsoft SQL Server metadata repositories 34 Microsoft Visual Studio .NET 2003 C++ environment variables 88 Microsoft Visual Studio .NET 2005 C++ environment variables 88 MKS Toolkit uninstalling 115 MPP 76

P
paging space IBM AIX 86 setting 86 setting on Linux 87 parallel engine C++ compilers 82 configuring 76, 77, 78 connecting to Teradata databases 94 data set descriptor files 87 environment variables 82, 83 paging space 86 paging space requirements 86 remote shell command 77 setting paging space Linux 87 parallel engines monitoring system resources 7 parallel jobs configuring 84 setting the maximum memory 85 user privileges 80 parallel processing 80 configuring a node (UNIX and Linux) 77 configuring a node (Windows) 80 passwords installation 26 troubleshooting 101

J
Java Runtime Executable errors troubleshooting 103, 104

K
kernel parameters IBM Information Server installation 24 installation 24

138

Planning, Installation, and Configuration Guide

PDF files documentation 9 permissions directory and user 106 planning application servers 30 bridges, MetaBroker 6 capacity 22 clusters 10 command line installation 13 connectivity 20 directories 16 disk size 13 file systems 13, 16 grids 10 IDs 26 installation 3 installation methods 13 log collection 4 Match Designer 36 MetaBroker 6 metadata repositories 32 naming, projects 23 networks 13, 20 ports 20 product modules 35 response files 13 topologies 10 upgrade 59 users 26 WebSphere Application Server 30 wizard installation 13 plug-ins enabling 63 ports planning 20 processing node Windows 77, 80 product updates 63 product accessibility accessibility 131 profiles removing Linux, UNIX 120 Windows 114 project naming 23

roles 71 rsh program location 79 rsh command configuring 78 parallel engine 77 runtime errors troubleshooting 102 runtime libraries installing for z/OS jobs

67

S
SAN 22 screen readers 127 secure shell program configuring 77 silent installation 45 8.0.1 upgrade parameters 61 Linux and UNIX parameters 51 Windows parameters 46 software requirements 4 software services 127 ssh command parallel engine 77 ssh program configuring 77 stage, Oracle Enterprise 93 starting and stopping WebSphere DataStage 100 suite removing console mode 115, 120 Linux, UNIX 119, 120 manually 117, 122 silent mode 115, 120 Windows 113, 115 uninstalling console mode 115, 120 Linux, UNIX 120 silent mode 115, 120 Windows 113, 115 support, customer 127 swap area increasing 89 sys.gv_$instance table granting access 93 sys.v_$cache table granting access 93 system requirements 4

tiers client 6 engine 7 product components contained in 4 services 8 topologies examples, installation 11 installation 4, 10 trademarks 135 troubleshooting command-line script fails 101 disk space for installation 102 domain connections 109 errors with kernel parameter values 109 failed installations 101 Java Runtime Executable errors 103, 104 log files 101 runtime errors, installation 102 uninstallation 101 user names and passwords 101 user privileges for installation 108 WebSphere Application Server installation with IBM Information Server 110

U
uninstallation troubleshooting 101 verifying 101 uninstalling MKS Toolkit 115 updates 63 upgrade planning 59 process overview 59 upgrading from DataStage or QualityStage 59 from IBM Information Server Version 8.0.1 59 metadata repositories 33 existing 33 overview 59 to IBM Information Server Version 8.1 59 Version 8.0.1 to Version 8.1 59 versions earlier than Version 8.0.1 to Version 8.1 62 user limits IBM Information Server installation 24 installation 24 user names troubleshooting 101 user privileges 108 Enterprise stage jobs 91 parallel jobs 80 users creating 71 planning 26 uvodbc.config file configuring 98

R
RAID 22 Red Hat application servers 30 registries, user 71 registry keys 89, 90 remote shell command configuring 78 repositories metadata 8 requirements system 4 Resource Tracker monitoring system resources 7 response file 45 Linux and UNIX parameters 51 upgrade parameters 61 Windows parameters 46

T
tablespaces Oracle 34 TCP/IP buffers 90 TCP/IP connections 90 Teradata database program installing the Teradata Tools and Utilities 94 Teradata database system creating users 95 Teradata databases setting up connectivity 94 Teradata Tools and Utilities installing 94

Index

139

W
WebSphere Application Server installation troubleshooting 110 planning 30 removing profiles Linux, UNIX 120 Windows 114 WebSphere Business Glossary configuring 76 described 8 WebSphere DataStage configuring 73 configuring NLS 71 configuring on DB2 servers 91 environment variables 72 starting and stopping 100 WebSphere Information Analyzer configuring 75 WebSphere Information Services Director testing installation 75 WebSphere Metabrokers and bridges installing 65 WebSphere QualityStage configuring 73 Configuring NLS 71 environment variables 72

Z
z/OS verifying the installation of z/OS components 69 z/OS components installing 66 z/OS jobs installing runtime libraries 67

140

Planning, Installation, and Configuration Guide

Printed in USA

GC19-1048-03

Spine information:

IBM Information Server

Version 8 Release 1

Planning, Installation, and Configuration Guide

You might also like