De 861 InstallGuide

7/28/2019 De 861 InstallGuide

1/78

Installation Guide

Informatica

Data Explorer(Version 8.6.1)


2/78

Informatica Data Explorer Installation GuideVersion 8.6.1September 2008

Copyright 2001-2008 Informatica Corporation. All rights reserved.

This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containingrestrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may bereproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. ThisSoftware may be protected by U.S. and/or international Patents and other Patents Pending.

Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and asprovided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR52.227-14 (ALT III), as applicable.

The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please reportthem to us in writing.

Informatica, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica

Data Quality, Informatica Data Explorer, Informatica B2B Data Exchange and Informatica On Demand are trademarks or registered trademarks of InformaticaCorporation in the United States and in jurisdictions throughout the world. Al l other company and product names may be trade names or trademarks of theirrespective owners.

DISCLAIMER: Informatica Corporation provides this documentation as is without warranty of any kind, either express or implied, including, but not limitedto, the implied warranties of non-infringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software ordocumentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. Theinformation in this software and documentation is subject to change at any time without notice.

Part Number: IDE-ING-86100-0000


3/78

iii

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi ii

Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Informat ica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Informatica Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Informat ica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Informatica Global Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Chapter 1: Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Data Explorer Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Data Explorer Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Databases Supported for the Data Explorer Repository . . . . . . . . . . . . . . . 4

Teradata Driver Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Calculating Repository Disk Space Requirements . . . . . . . . . . . . . . . . . . . 5

Installation and Upgrade Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Deployment Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Data Explorer Product Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Reporting Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Data Analyzer Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Crystal Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2: Data Explorer Installation on Windows. . . . . . . . . . . . . . .13

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Installing Data Explorer on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 3: Data Explorer Server Installation on Unix . . . . . . . . . . . .19

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Installing Data Explorer Server on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21


4/78

iv Table of Contents

Installing Data Explorer Server in Console Mode . . . . . . . . . . . . . . . . . .21

Installing Data Explorer Server in GUI Mode . . . . . . . . . . . . . . . . . . . . . 23

Chapter 4: Post-Installation Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Obtaining and Installing the Data Explorer License . . . . . . . . . . . . . . . . . . .29

Obtaining the Data Explorer License . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Installing the Data Explorer License . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Starting and Stopping the Data Explorer Listener . . . . . . . . . . . . . . . . . . . . . 32

Chapter 5: Setting Up the Data Explorer Server Environment. . . . . .33

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Configuring Data Explorer Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Setting the Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Granting Privileges to a Remote Server . . . . . . . . . . . . . . . . . . . . . . . . .35

Configuring the Windows Server as an Application Server . . . . . . . . . . .36

Running Server Component Across Subnets . . . . . . . . . . . . . . . . . . . . . . . . . 37

Chapter 6: Reviewing Configuration Files . . . . . . . . . . . . . . . . . . . . .39

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Configuring ODBC Drivers for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Reviewing and Editing Importer Configuration Files . . . . . . . . . . . . . . . . . .43

Reviewing Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Reviewing and Editing Tag Configuration Files . . . . . . . . . . . . . . . . . . . . . . 45

Updating Repository Tag Information . . . . . . . . . . . . . . . . . . . . . . . . . .45

Blank Stripping Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Chapter 7: Installing VSAM and IMS Importers. . . . . . . . . . . . . . . . . .49

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50Installing Importers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Author izat ion Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Setting Up Repository Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Running Crystal Reports from Data Explorer . . . . . . . . . . . . . . . . . . . . . 54


5/78

Table of Contents v

Chapter 8: Upgrading Data Explorer Installations . . . . . . . . . . . . . . .55

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Upgrading from Data Explorer 5.0 SP4 to 8.6.1 . . . . . . . . . . . . . . . . . . . . . . 57

Upgrading Data Explorer from 8.6 to 8.6.1 . . . . . . . . . . . . . . . . . . . . . . . . . 58

Editing The Properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Running The Silent Installer On All Platforms. . . . . . . . . . . . . . . . . . . . 58

Installation Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Upgrading the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Chapter A: Uninstalling Data Explorer . . . . . . . . . . . . . . . . . . . . . . . .61

Uninstalling on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Uninstalling on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65


6/78

vi Table of Contents


7/78

vii

Preface

Welcome to Data Explorer, the Informatica software product suite that provides a completeand accurate picture of enterprise data through data profiling . Data Explorer is a complete set

of data investigation, discovery, and mapping tools that allows you to quickly analyze multiplesource systems and eases the process of scoping the size and complexity of a migration or dataintegration project.


8/78

viii Preface

About This Book

The Data Explorer Installation Guideprovides information about installing and configuringData Explorer. The Data Explorer Installation Guideis written for the system administrators

who are responsible for setting up Data Explorer for an organization. This guide as sumes youhave knowledge of the operating systems and relational databases in your environment.

The material in this book is also available online.


9/78

Informatica Resources ix

Informatica Resources

Informatica Customer Portal

As an Informatica customer, you can access the Informatica Customer Portal site at http://my.informatica.com. The site contains product information, user group information,newsletters, access to the Informatica customer support case management system (ATLAS),the Informatica Knowledge Base, Informatica Documentation Center, and access to theInformatica user community.

Informatica Documentation

The Informatica Documentation team takes every effort to create accurate, usabledocumentation. If you have questions, comments, or ideas about this documentation, contactthe Informatica Documentation team through email [email protected]. We will use your feedback to improve ourdocumentation. Let us know if we can contact you regarding your comments.

Informatica Web Site

You can access the Informatica corporate web site at http://www.informatica.com. The sitecontains information about Informatica, its background, upcoming events, and sales offices.

You will a lso find product and partner information. The services area of the site includesimportant information about technical support, training and education, and implementationservices.

Informatica Knowledge Base

As an Informatica customer, you can access the Informatica Knowledge Base at http://my.informatica.com. Use the Knowledge Base to search for documented solutions to knowntechnical issues about Informatica products. You can also find answers to frequently askedquestions, technical white papers, and technical tips.

Informatica Global Customer Support

There are many ways to access Informatica Global Customer Support. You can contact aCustomer Support Center through telephone, email, or the WebSupport Service.

Use the following email addresses to contact Informatica Global Customer Support:

[email protected] for technical inquiries

[email protected] for general customer service requests

WebSupport requires a user name and password. You can request a user name and password athttp://my.informatica.com.


10/78

x Preface

Use the following telephone numbers to contact Informatica Global Customer Support:

North America / South America Europe / Middle East / Africa Asia / Australia

Informatica CorporationHeadquarters

100 Cardinal Way

Redwood City, California

94063

United States

Toll Free

+1 877 463 2435

Standard Rate

Brazil: +55 11 3523 7761

Mexico: +52 55 1168 9763

United States: +1 650 385 5800

Informatica Software Ltd.6 WalthamPark

WalthamRoad, White Waltham

Maidenhead, Berkshire

SL6 3TN

United Kingdom

Toll Free

00 800 4632 4357

Standard Rate

Belgium: +32 15 281 702

France: +33 1 41 38 92 26

Germany: +49 1805 702 702

Netherlands: +31 306 022 797

United Kingdom: +44 1628 511 445

Informatica BusinessSolutions Pvt. Ltd.

Diamond District

Tower B, 3rd Floor

150 Airport Road

Bangalore 560 008

India

Toll Free

Australia: 1 800 151 830

Singapore: 001 800 4632 4357

Standard Rate

India: +91 80 4112 5738


11/78

1

Chapter 1

Before You Begin

This chapter includes the following topics:

Overview, 2

System Requirements, 3

Data Explorer Product Licensing, 9

Disk Space Requirements, 5

Installation and Upgrade Options, 7

Data Explorer Product Licensing, 9

JDBC Drivers , 10

Reporting Capabilities, 11


12/78

2 Chapter 1: Before You Begin

Overview

The Data Explorer installers provide a unified install environment for Data Explorerapplications. It also installs a Crystal Reports viewer and provides install options for new

reports for PowerCenter Data Analyzer, DataDirect ODBC drivers, and the Microsoft .NETframework.

Data Explorer supports a client-server architecture and works on the .NET framework.

Note: Data Explorer does not install the full Crystal Reports application. It installs a runtimeengine for Crystal Reports that allows you to view but not edit Crystal reports.

This chapter discusses the minimum hardware, software, and database requirements for Data

Explorer. It also provides information about Data Explorer license requirements and theOBBC and JDBC drivers you require to connect to the Data Explorer repository.


13/78

SystemRequirements 3

System Requirements

The system on which you install the Data Explorer components must meet the minimumhardware and software requirements.

You can install the client and server on the same system or on separate sys tems.

Data Explorer Client

The Data Explorer Client requires approximately 280 MB of disk space. To install DataExplorer Client, you need the following:

Windows operating system

1.0 GHz Pentium III or equivalent processor or greater

512 MB RAM

.NET Framework v.1.1

If your system does not have the .NET Framework installed, the Data Explorer installerprovides you an option to install it

Screen resolution of 1024 x 768 pixels or above

Data Explorer Server

The Data Explorer Server requires approximately 200 MB of disk space. To install DataExplorer Server, you need the following:

Red Hat Enterprise Linux-based server

SUN SPARC-based server

IBM PowerPC-based server

HP PA-RISC-based server

Windows

A data profiling project requires a minimum of 512 MB of physical memory backed by512-1024 MB of swap space. Large projects might require two to three times more memoryand swap space. If you are running other applications in addition to Data Explorer, additionalmemory and swap space might be necessary.

Memory Limitations on Solaris Platforms

There are no memory limitations if you are installing Data Explorer on a Solaris platform.

Memory Limitations on AIX Platforms

On an AIX platform, the limits file in the /etc/security/ directory defines the default settings

and the limits for processes such as memory usage and file size. Depending on the size of themachine, type, and amount of data your system will need to process, the default data space


14/78


will be inadequate. Increase the default data space size to a higher value, for example 512 MB,or set an unlimited setting (-1).

Memory Limitations on HP-UX Platforms

On an HP-UX platform, the data space size is controlled by the OS parameter maxdsiz. Thedefault size is too small for large projects and must be increased to 512 MB or the maximumsystem-allowed value.

You can use the HP system adminis tration tool sam to increase the maxdsizparameter in thekernel.

Memory Limitations on Windows Platforms

There are no memory limitations if you are installing Data Explorer on a Windows platform.

Databases Supported for the Data Explorer Repository

Data Explorer supports the following databases:

Oracle

DB2/UDB

Microsoft SQL Server

Sybase ASE

Informix

Data Explorer applications use ODBC or JDBC drivers to connect to the Data Explorerrepository. Data Explorer installs these drivers.

Teradata Driver RequirementsIf you will work with ODBC 5.3 Teradata drivers, verify that the Teradata 32-bit nativebinaries are installed before running the Data Explorer installer.

Note: Following a Data Explorer install on UNIX, Teradata users must append theappropriate value from this table to the path in the file server860/config/odbc/ideodbc.ini:

HPUX SHLIB_PATH

Solaris LD_LIBRARY_PATH

AIX LIBPATH


15/78

Disk Space Requirements 5

Disk Space Requirements

All disk space requirements indicated in this section are for the components insta lled from theData Explorer installe r. The amount of disk space you need for a project depends on the size

of the databases you intend to profile and map, the size of the projects you create, and the sizeof the repository.

Table 1-1 provides a list of the platforms that Data Explorer supports and the disk space foreach Data Explorer application:

Note: For more information about project disk space requirements, see the Data ExplorerSystem Administration Guide.

Calculating Repository Disk Space Requirements

Use the following formula to calculate the disk space requirements of the repository:

RDBMS overhead

+ (RDBMS factor [Data Explorer project size Number of projects])

+ (Source Profiler schema size Number of Source Profiler schemas)

+ (Data Explorer FTM schema size x number of schemas)

Contact your database administrator to determine the RDBMS overhead and RDBMS factor.To ensure that you have enough disk space for your repository, have your databaseadministrator build tablespaces that you can expand later as per your requirements.

Table 1-1. Disk Space Requirements

Application Platform-Specific ConsiderationsSpace

Required

Data Explorer Server Red Hat Enterprise Linux

Sun Solaris

HP-UX

IBM AIX

200 MB

Windows 280 MB

Additional disk space required during installation 45 MB

Data Explorer Client Windows 230 MB


16/78


Table 1-2 describes the factors used in calculating the disk space requirements for therepository:

Consider the following example:

You install Data Explorer without Data Explorer FTM or Data Explorer Source Profiler and

have only one Data Explorer project with a size of 35 MB. Your database administratorestablishes that the RDBMS overhead is 13 MB and that a factor of 6 must be applied to anydata loaded into the database. You can use the formula given on page 5 to calculate therepository disk space requirements:

RDBMS factor 6 x Project size 35 MB 210 MB

RDBMS overhead 13 MB

Total Estimated Disk Space for the Repository 223 MB

For information about managing temp space and swap space and other space considerations,see the Data Explorer System Administration Guide.

Table 1-2. Disk Space Calculation

Term Meaning

Data Explorer project size Value calculated for the projects metric.

Number of Data Explorer projects Maximumnumber of Data Explorer projects expected to be stored in the repository

at any given time.

Number of Data Explorer FTM

Schemas

Maximumnumber of schemas, originally created by the Data Explorer FTM

product, stored in the repository at any given time.

Number of Source Profiler

Schemas

Maximumnumber of schemas, originally created by the Source Profiler product,

stored in the repository at any given time.

RDBMS factor Factor that adjusts the RDBMS storage overhead. The storage overhead is

directly related to data that is loaded into the database. An RDBMS factor of 1

indicates that the RDBMS has no data-dependent overhead. A factor of 2

indicates that for every byte of data loaded into the repository, the RDBMS also

consumes a byte of data-dependent storage.

RDBMS overhead Number of bytes consumed by the RDBMS installation after building the repository

tables, and before loading any data into the database.

Data Explorer FTM Schema size Number of bytes expected to be stored in schemas created by the Data Explorer

FTM/XML product.

Data Explorer Source Profiler

Schema size

Number of bytes expected to be stored in schemas created by the Data Explorer

Source Profiler product.


17/78

Installation and Upgrade Options 7

Installation and Upgrade Options

Bear in mind the following conditions when deciding on an installation or upgrade strategy:

If you are installing Data Explorer for the first time, run the 8.6.1 installer.

To upgrade Data Explorer 5.0 to Data Explorer 8.6.1, run the 8.6.1 installer. This installsData Explorer 8.6.1 in parallel with Data Explorer 5.0.

You must use the 8.6.1 s ilent insta ller to upgrade Data Explorer 8.6 to Data Explorer8.6.1. You cannot upgrade Data Explorer 8.6 with the Data Explorer 8.6.1 ins taller.

Deployment Summary

To install and activate Data Explorer, complete the following steps:

1. If you will deploy Data Explorer reports for Data Analyzer, verify that PowerCenterAdvanced Edition is installed, the reporting ser vice used by Data Analyzer is running andavailable, and you know the URL, username, password, and namespace of the reportingservice you will connect to.

2. Run the Data Explorer installer. You can choose to install the Data Explorer Client,Server, and Data Analyzer Reports on the same machine. You can also select options to

install ODBC drivers and the Microsoft .NET framework.

If you are applying Data Explorer 8.6 Service Pack 1 to Data Explorer 8.6, run the silentinstaller. You may need to update Data Analyzer reports, ODBC drivers, or the Microsoft.NET framework separately.

3. Obtain a product license from Informatica Global Customer Support and add the licenseto the system.

The Global Customer Support team needs the UMI (unique machine identifier) of theinstall machine to generate your license. The install process displays the UMI of themachine that hosts the install files. For more information, see Obtaining and Installingthe Data Explorer License on page 29.

4. Set up the Data Explorer repository.

Create a Data Explorer repository in a relational database. The Data Explorer installerincludes SQL scripts that you can run on a database to create the relevant repository

tables. These repository tables store information about Data Explorer projects.

For more information, see Data Explorer Repository Administration in the DataExplorer System Administration Guideand the readme.txt files located in the/Repository/sql/ directory.

5. Set up the Data Explorer Server environment.

Configure the machine that hosts the Data Explorer Server. For more information, see

Setting Up the Data Explorer Server Environment on page 33.


18/78


Data Explorer includes configuration files that you can modify to enable Data Explorerestablish data sources from which to profile data and export the results. For moreinformation, see Reviewing Configuration Files on page 39.

You can also install and set up Data Explorer Import extracts running on MVS or

OS/390 platforms. For more information, see Installing VSAM and IMS Importers onpage 49.


19/78

Data Explorer Product Licensing 9

Data Explorer Product Licensing

Before you can use Data Explorer, the Data Explorer Listener must be running. The Listeneris a service that starts when you start your system and it is responsible for starting the Data

Explorer Server and is a license manager for all of the Data Explorer family of products.The Listener's license manager component controls user access to Data Explorer, DataExplorer Source Profiler, Data Explorer FTM, Data Explorer Import, Data Explorer XML,and the DataDirect ODBC drivers. It maintains a central database of tokens based onpredetermined licenses.

Additionally, it performs the following tasks:

It verifies clients.

It grants tokens to valid licensed applications when tokens are available.

When the number of requests for a token exceeds the number of tokens available, theListener denies the request.

It collects tokens when applications terminate or when it determines that an application isno longer running.


20/78


JDBC Drivers

If you are using Data Explorer FTM/XML or Repository Navigator, use JDBC Type IVdrivers.

These drivers are included in the Data Explorer installer, which installs them in the\Navigator\jdbc directory.

The DataDirect Technologies JDBC drivers support the following databases:

DB2/UDB

Oracle

Microsoft SQL Server

Sybase ASE

Informix

Note: Data Explorer XML or Data Explorer Navigator users should use Oracle Type IV JDBC

drivers instead of ODBC drivers for Oracle.


21/78

Reporting Capabilities 11

Reporting Capabilities

Data Explorer supports report generation with PowerCenter Data Analyzer and throughCrystal Reports.

Data Analyzer Reports

The Data Explorer installer can load pre-designed repository reports to the Data Explorerrepository that PowerCenter Advanced Edition users can run from PowerCenter Data

Analyzer.

If you will use these reports in Data Analyzer, verify that an internet connection toPowerCenter Advanced Edition is available before you install Data Explorer.

If you select the option to deploy Data Analyzer Reports, the Data Explorer insta ller promptsyou to provide the following information:

Data Analyzer URL. The address of the Data Analyzer reporting service. This address hasthe following format:

http://:/ias-

The reporting service at this URL must be running and available to the Data Explorer

installer. If the installer cannot connect to the reporting service, the installation will fail.

User ID. A valid user ID for Data Analyzer. It must include the namespace used by DataAnalyzer in the format u sername@namespace.

The default namespace is Native: [username]@Native

Password. A valid password for Data Analyzer.

Username and password information is case-sensitive.

Data Analyzer requires PowerCenter Advanced Edition. For more information, see yourPowerCenter Data Analyzer documentation.

Crystal Reports

Data Explorer installs a runtime Crystal Reports viewer. You can install an external version ofthe Crystal Reports application in addition to the runtime Crystal Reports viewer installed byData Explorer.


22/78



23/78

13

Chapter 2

Data Explorer Installation

on Windows


Overview, 14

Installing Data Explorer on Windows, 15

O i


24/78

14 Chapter 2: Data Explorer Installation on Windows

Overview

This chapter provides the steps to install the Data Explorer product suite on Windowsmachines.

The Data Explorer install wizard provides the following high-level installation options:

Complete. Installs the complete Data Explorer product suite.

Custom. Installs selected Server or Client components, including reports for PowerCenterData Analyzer.

The installable components with each option are as follows:

The installation process installs ODBC drivers and a Java Runtime Environment if the installtarget machine requires them. For Complete and Client installations the installation processalso installs the Microsoft .NET framework if it does not detect it on the target machine.

Component Complete Client Server

Data Explorer Client Y Y

Data Explorer Listener Y Y

Data Explorer Repository Creation Scripts Y Y

Data Explorer Batch Y Y Y

Data Explorer Listener Y Y

Data Explorer FTM Y Y

Data Explorer XML Y Y

Data Explorer Header Generator Y Y

Data Explorer Navigator Y Y

Crystal Reports repository reports Y Y

Data Explorer Source Profiler Y Y

Data Explorer Port Settings (Windows only) Y Y

Data Explorer UMI Generator (Windows only) Y Y Y

Crystal Reports Viewer for Data Explorer Y Y

DataDirect ODBC Drivers Y Y Y

Sun Java 2 Runtime Environment Version 1.4.2 Y Y Y

Microsoft .NET Framework 1.1 with SP1 for Windows Y Y

I t lli D t E l Wi d


25/78

Installing Data Explorer on Windows 15

Installing Data Explorer on Windows

Before installing, verify that your environment meets the minimum system requirementsdescribed in Before You Begin on page 1.

To install Data Explorer on Windows:

1. Open the installation fileset that you received from Informatica. Locate and run theinstall.bat file.

2. The InstallAnywhere installation wizard opens. At the Welcome screen, click Next.

3. For users running the client-only Data Explorer Installer: The following step does notapply to your installation. Skip to Step 7.

4. Choose the product set to install. Choose Complete to install all components on the localmachine. Choose Custom to select from Server, Client, and Reports options.

5. Copy the unique machine identifier (UMI). Informatica uses the UMI to generate yourproduct license.

Note: The Client-only installer does not display the UMI. If you are running theclient-only installer, you must generate your UMI later in the install process, as described

in Step 15.6. If you selected Custom installation in Step 4, select the options you wish to install. When

you select either Client or Server, the Deploy DA (Data Analyzer) Reports option isselected by default. This option installs dashboards and reports that you can run fromPowerCenter Data Analyzer to the Data Explorer repository. Clear this option if you donot wish to install these reports.

7. Specify the installation directory. The default directory is:

C:\Informatica\DataExplorer8.6

8. Server installations only: Choose the directory to which Data Explorer can writetemporary files. The default directory is:C:\Windows\temp

Note: For performance reasons, this directory should not reside on the same drive thatstores the paging file. Data Explorer Server uses this directory to write potentially largesets of temporary results during profiling.

9. Client and Complete installations only: The client installer prompts you to installMicrosoft .NET Framework 1.1 if it does not detect it on the local system. If prompted,accept this install option. Microsoft .NET Framework 1.1 is mandatory for DataExplorer client installations.

10. If you are installing Data Explorer reports for Data Analyzer, check the Deploypre-designed reports for Data Analyzer option and enter the connection details for Data

Analyzer. Provide the following information:

Data Analyzer URL. The address of the reporting service used by Data Analyzer. Thisaddress has the following format:

http://:/ias


26/78


http://:/ias-

The reporting service at this URL must be running and available to the Data Explorerinstaller. The reporting service is started on the PowerCenter Admin Console.

User ID. A valid user ID for Data Analyzer in the format [username@namespace]. The

user ID must include the namespace used by Data Analyzer. The default is namespace isNative.


Username and password information is case-sensitive.


11. Choose the ODBC drivers to install. The options are ODBC 5.2 Service Pack 2 andODBC 5.3.

12. Review the summary of your installation selections, and click Install. The Data Explorerinstallation commences. Your installation may include the following items:

ODBC Driver Installation. The DataDirect ODBC driver installation launches as partof the Data Explorer install. Use Alt-Tab if necessary to toggle to the ODBC Driverinstall window.

Microsoft .NET Installation. For Data Explorer Client installations, the Microsoft .NETinstaller launches if the Microsoft .NET Framework 1.1 with Service Pack 1 is notdetected. Accept the prompts to install the .NET framework. The .NET installationrequires a machine restart. Select the option to Restart Later when prompted.

13. Server and Complete installations only: Review the Data Explorer Listener and LicenseManager settings and edit them if required:

Listener Port Number. The port used by the Listener in communications between Server

and Client. The default port is 1416.

Hostname of License Manager. The host machine of the Data Explorer License Manager.

Port Number for License Manager. The port used by the License Manager incommunications between Server and Client. The default port is 1416.

Accept the defaults for these sett ings or type new sett ings that match the systemconfiguration. For more information, see Data Explorer Product Licensing on page 9.

14. Review the installation summary and verify the successful installation of Data Explorer.Click Done to exit the installer.

15. For users running the client-only Data Explorer Installer:After installation, run theUMI utility that installs with Data Explorer to obtain the UMI. Informatica uses theUMI to generate your product license.

In a default installation, the path to this utility is:

C:\Informatica\DataExplorer8.6\Client\ideumi.exe


27/78


28/78



29/78

19

Chapter 3


Installation on Unix


Overview, 20

Installing Data Explorer Server on UNIX, 21

Overview


30/78

20 Chapter 3: Data Explorer Server Installation on Unix

Overview

This chapter provides the steps to install Data Explorer Server on UNIX.

The following components are installed as part of the Data Explorer Server installation:


Data Explorer Listener

Repository Creation Scripts

Installing Data Explorer Server on UNIX


31/78

Installing Data Explorer Server on UNIX 21

sta g ata p o e Se e o U

You can install Data Explorer Server on a Linux, IBM AIX, HP-UX, or a Sun Solaris UNIXserver system. The installer runs in console mode or in GUI mode.

Preparing for Installation

To install the Data Explorer Server, you need the following:

Installation files. Verify that the installation fileset is stored on the machine to which youwill insta ll Data Explorer Server.

Root permission on the UNIX server on which you will install the Data Explorer Server.

As the instal lation script modifies system files during the installation, you must log onwith root permissions.

Files are added to the /etc/rc.d and the /etc/init.d/ idelistener directories.

Platform-dependent startup scripts are modified to automatically start the Data ExplorerLicense Manager.

To run Data Explorer, you will need a valid license.elf file for your computer. For moreinformation, see Obtaining and Installing the Data Explorer License on page 29.

Installing Data Explorer Server in Console Mode

The following steps describe Server installation on Unix with a Bourne shell.

To install Data Explorer Server in console mode:

1. Log in to the UNIX system with root permission.

2. At a terminal prompt, navigate to the directory where you have copied the UNIX instal lfiles.

3. Start the installer with the following command:

sh install.bin

4. When prompted, type C for console mode and press Enter.

5. Accept the option to stop any Data Explorer Listener services. These services may be

active if an earlier version of Data Explorer is installed. The installation cannot proceed ifListener services are running.

Choose 1 (default) to continue or 2 to cancel, and press Enter.

6. At the Installation Welcome prompt, press Enter.

Note: To move to a previous option during the insta ll, type back. To exit the installer atany stage, type quit.

7. Choose the install set, and press Enter. The options are 1 for Complete install (default)and 2 for Custom install. Choose Complete for all server components, and press Enter.

8. Take note of the unique machine ID. Press Enter.


32/78


9. Custom installers only: choose the install components. The options are 1 (default) forServer and 2 for deployment of Data Analyzer reports. Press Enter.

10. Choose the install directory. The default directory on UNIX is

/opt/Informatica/DataExplorer860

Press Enter to accept the default, or type an absolute path and press Enter.

11. If you have entered a non-default directory, type Y to confirm your directory path, andpress Enter.

12. Choose the directory that the installer will use for temp directory. The default directoryis /tmp. Press Enter to accept the default or type an alternative directory path and press

Enter.Note: For performance reasons, this directory should not reside on the same drive thatstores the paging file. Data Explorer Server uses this directory to write potentially largesets of temporary results during profiling.

13. Indicate if you wish to deploy Data Analyzer Reports. The options are 1 (default) for Noand 2 for Yes. Make your selection and press Enter.

14. If you selected to deploy Data Analyzer Reports, provide the following information whenprompted:


http://:/ias-

The reporting service identified in this URL must be running and available to the DataExplorer installer. The reporting service is started on the PowerCenter Admin Console.

User ID. A valid user ID for Data Analyzer in the format username@namespace. Thismust include the namespace used by Data Analyzer. The default user ID is

Adminis trator@Native , where Native i s the namespace used by Data Analyzer.


User ID and password information i s case-sensitive.


15. Review the pre-installation details, and press Enter to continue.

16. The installer attempts to find the IDE 5.0 SP4 installation directory. If the installercannot locate this path, you are prompted to confirm whether or not you haveIDE 5.0 SP4 installed. Type the path for the IDE 5.0 SP4 installation directory, or typeNo if you do not have IDE 5.0 SP4 installed.

17. At the next three prompts, enter the Listener port number, License Manager hostname,

and the port number for the License Manager:


33/78

Click Browse to select a new directory. Click Next to accept the directory shownonscreen


34/78


onscreen.

10. Choose the directory that the installer will use for temp directory. The default directory is/tmp.

Click Browse to select a new directory. Click Next to accept the directory shownonscreen.

11. Optional: select the option to deploy Data Analyzer Reports. If you are deploying DataAnalyzer Reports, provide the following information:


http://:/ias-

The reporting service identified in this URL must be running and available to the DataExplorer installer. The reporting service is started on the PowerCenter Admin Console.

User ID. A valid user ID for Data Analyzer in the format username@namespace. Thismust include the namespace used by Data Analyzer. The default user ID is

Adminis trator@Native , where Native i s the namespace used by Data Analyzer.


User ID and password information i s case-sensitive.


12. Review the pre-installation details, and click Install.

13. The installer attempts to find the IDE 5.0 SP4 installation directory. If the installercannot locate this path, you are prompted to confirm whether or not you haveIDE 5.0 SP4 installed. Select Yes to enter the path for the IDE 5.0 SP4 installation

directory, or select No if you do not have IDE 5.0 SP4 installed.

14. Review the Data Explorer Listener and License Manager settings and edit them ifrequired:

Listener Port Number. The port used by the Listener in communications between Serverand Client. The default port is 1416.

Hostname of License Manager. The host machine of the Data Explorer License Manager

application.Port Number for License Manager. The port used by the License Manager incommunications between Server and Client. The default port is 1416.

To accept the defaults for these settings, click Next, or alternatively type new settings thatmatch the system configuration. For more information on Listener and License Managersettings, see Data Explorer Product Licensing on page 9.

15. Review the post-installat ion summary, and click Next.


35/78


36/78


37/78

27

Chapter 4

Post-Installation Steps


Overview, 28

Obtaining and Installing the Data Explorer License, 29

Starting and Stopping the Data Explorer Listener, 32

Overview


38/78

28 Chapter 4: Post-Installation Steps

This chapter describes the steps to take following installation to activate your Data Explorerinstallation.

It also contains information on configuring a Data Explorer installation to run alongside anolder Data Explorer installation.

Obtaining and Installing the Data Explorer License


39/78

Obtaining and Installing the Data Explorer License 29

Before you run Data Explorer, you must obtain a Data Explorer license and install it on thesystem that hosts the Data Explorer Server. Informatica uses the UMI to create a license filespecific to your installation.

Note: If you set up the Data Explorer Server and Listener on separate systems, you need toobtain UMIs for both systems.

To install the Data Explorer license, complete the following steps:

1. Identify the UMI.

2. Obtain a license .

3. Install the Data Explorer license.

Identifying the UMI on a Windows System

The install wizard provides the UMI of the machine that runs the installer.

You can also determine the determine the UMI for a Data Explorer installat ion by runningthe UMI util ity. This file is named ideumi.exe. For Client installations, the default locationfor this file is:

C:\Informatica\DataExplorer8.6\Client

For Server installations, the default location for this file is:

C:\Informatica\DataExplorer8.6\Server\bin

Identifying the UMI on a UNIX System

The install script for UNIX provides an option to determine the UMI of the system.

The UNIX commands to display the UMI for a machine are as follows:

Obtaining the Data Explorer License

To use Data Explorer, you must obtain a license file from Informatica Global CustomerSupport. Informatica requires a Unique Machine Identifier (UMI) to generate the license forthe system on which you install the Data Explorer Server. The UMI is a series of digits and

letters that uniquely identify a machine.

Informatica generates license files based on the following factors:

Platform Command

Linux /listener/bin/./idelistener umi

HP-UX /usr/bin/uname -i

AIX /usr/bin/uname -l

Solaris /usr/bin/hostid


40/78

For more information about setting up the Data Explorer Listener, see the Data ExplorerSystem Administration Guide.


41/78

Obtaining and Installing the Data Explorer License 31

Starting and Stopping the Data Explorer Listener


42/78

32 Chapter 4: Post-Installation Steps

The following steps explain the options for starting and stopping the Data Explorer Listeneron Windows and UNIX platforms.

You must log on as a root user to run UNIX commands.

To start or stop the Listener using Windows Control Panel

1. Open the Windows Control Panel.

2. Open Administra tive Tools.

3. Open the Services window.

4. Select Data Explorer Listener and right-click to stop or start it.

Starting and Stopping the Listener on UNIX

To start the Data Explorer Listener on UNIX, run the following command:

/listener/bin/S99idelistener start

To stop the Data Explorer Listener on UNIX, run the following command:

/listener/bin/S99idelistener stop

Stopping the Listener using a web interface:

You can stop the Listener on Windows and UNIX using a web interface. You cannot use thisinterface to start the Listener.

1. Open a web browser at a URL in the following format:

http://:

where the port number is the Data Explorer Listener port. The default installation settingis port 1416.

2. Log in and select the Administration option in the Listener section. If you are accessingthe web interface for the first time, log in as administrator (lowercase) with no password.

3. Click Stop next to the Listener module.

Note: To add or delete Data Explorer users and administrators on the Administration page,

click Edit next to Password Manager.


43/78

Overview

l ff l d f h h h


44/78

34 Chapter 5: Setting Up the Data Explorer Server Environment

For Data Explorer Server to run more efficiently, you need to configure the system that hoststhe Data Explorer Server.

This chapter describes the steps you can take to configure Data Explorer and to run servercomponents across subnets.

Configuring Data Explorer Server

T h D E l S i l h f ll i


45/78

Configuring Data Explorer Server 35

To set up the Data Explorer Server environment, complete the following steps:

1. Set the environment variables.

2. Grant privileges to a remote server. (Windows installations)

3. Configure the Windows server as an application server. (Windows installations)

Setting the Environment Variables

The ide_server.ini file contains the environment variables associated with ide_server.exe(Windows) and ide_server (UNIX) executable files and must be in the same directory as the

executable file.

The default install location for the file on Windows isC:\Informatica\DataExplorer8.6\Server\bin.

The default install location for the file on /opt/Informatica/DataExplorer860/server860/bin

The installation process creates and modifies the ide_server.ini file for your system, and the

listener reads this file before running the related executable file.Table 5-1 lists the environment variables within the ide_server.ini file that you can configure:

Granting Privileges to a Remote Server

If your users run the Data Explorer Client against a remote Windows server, you must grantthem logon privileges to access the Windows server.

The users must also have write access on the Windows server to save their projects and logfiles on the server. To grant write access to the Windows server, you must grant Log onLocally privileges to a user or group of users.

Table 5-1. Environment Variables for Data Explorer Server

Variable Purpose

IDE_ELMHOST Indicates the location of the Data Explorer License Manager. You need to configure this

variable only if the Data Explorer License Manager and Data Explorer Server are on different

subnets.

TMP (Windows) or

TMPDIR (UNIX)

Identifies the location of the temporary directory. Set this variable when you want to specify a

location for the temporary files created by Data Explorer tasks such as column profiling. Both

TMP and TMPDIR must be set to the same directory name.

IDE_ELMPORT Set this variable if the port of the Data Explorer license server is not 1416 (the default). You

need this variable for the Source Profiler component.

IDE_HOME Indicates the location of the Data Explorer Server installation.

To grant local log on rights on a Windows XP Professional system:

1. Double-click Administrative Tools from the Control Panel.

2 D bl li k L l S it P li


46/78


2. Double-click Local Security Policy.

The Local Security Settings window appears.

3. Expand the Local Policies directory.

4. Double-click User Rights Assignment.

The Policy window is populated with user right policies.

5. Double-click Log on Locally.

The Local Security Policy Setting dialog box appears.

6. Click Add.

The Select Users and Groups dialog box appears.

7. Click Show Users.

8. Select the users or groups to whom you wish to grant access privileges, from the Namefield.

9. Click Add.

10. Click OK.

11. In the User Rights Policy dialog box, click OK.

Configuring the Windows Server as an Application Server

You can configure a Windows 2000 or a Windows 2003 server to run as a file server insteadof an application server. The default file server setting of Maximize Throughput for File

Sharing gives the file cache priority to use the memory.

The file cache grows and consumes physical memory, and leaves insufficient space forapplications to run. This causes the system to slowdown and the applications to crash. Thissetting dramatically improves performance when reading files equal to or greater than thephysical memory of the machine or when multiple applications are processing large amountsof I/O.

If you plan to run the Data Explorer Server on Windows, you might need to configure theseservers to Maximize Throughput for Network Applications.

Running Server Component Across Subnets

To run the Data Explorer Server and l icense server on different subnets you must set the


47/78

Running Server Component Across Subnets 37

To run the Data Explorer Server and l icense server on different subnets, you must set theIDE_ELMHOST environment variable. Locate this variable in the ide_server.ini file.

Note: To run Data Explorer Navigator, Source Profiler, and FTM/XML, set theIDE_ELMHOST environment variable on the client system. This enables the programs tocommunicate with a license server.

To set the IDE_ELMHOST variable where the Server and Listener reside on different

subnets:

1. Open the ide_server.ini file in a text editor.

2. Search for the following line in the ide_server.ini file:IDE_ELMHOST=@localhost

Note: The @ symbol is a required syntactical element.

3. Verify that there is no hash symbol at the start of the line. A comment symbol (#) rendersthe variable inactive.

4. Replace localhostwith the name or IP address of the machine running the license server.

5. Save the file.


48/78



49/78

39

Chapter 6

Reviewing Configuration

Files


Overview, 40

Configuring ODBC Drivers for UNIX, 41 Reviewing and Editing Importer Configuration Files, 43

Reviewing and Editing Tag Configuration Files, 45

Overview

This chapter describes the configuration tasks you can perform to prepare Data Explorer for


50/78

40 Chapter 6: Reviewing Configuration Files

your environment. The procedures in this chapter cover reviewing and editing configurationfiles on Windows and UNIX and configuring ODBC drivers for UNIX.

Data Explorer configuration files perform the following tasks:

They create the data sources that Data Explorer can load, profile, and investigate.

They establish the Data Explorer repository export data sources.

They configure profiling and other parameters.

If you installed Data Explorer in the default directory, the configuration fi les reside indirectories beneath the following directory:

C:\Informatica\DataExplorer8.6\Server\config

If your Data Explorer installation directory is /opt/informatica, the configuration files are inthe following directory:

/opt/Informatica/DataExplorer860/config

The config directory also contains configuration files used by Data Explorer that provideproject-specific values and settings.

For more information about configuration, see the Data Explorer System AdministrationGuide.

Configuring ODBC Drivers for UNIX

On UNIX, you must verify the environment variables for the ODBC driver and database.


51/78

Configuring ODBC Drivers for UNIX 41

This table shows the locations of the files that you may need to update to enable ODBCexport to the repository:

The ODBC configuration files are defined in the ide_server.ini file as include values. Theodbc.odbc file must be included.

The odbc.odbc file defines the location of the ODBC drivers. It provides the location of theodbc.ini file to the Data Explorer Server.

If you plan to export data to the Data Explorer repository, you may want to uncomment theline relating to the files that define custom configuration options for ODBC drivers:

# include= $(IDE_HOME)/config/informix7/informix7.odbc

# include= $(IDE_HOME)/config/oracle8/oracle8.odbc

# include= $(IDE_HOME)/config/oracle9/oracle9.odbc

# include= $(IDE_HOME)/config/sqlsrvr7/sqlsrvr7.odbc

# include= $(IDE_HOME)/config/sybase10/sybase10.odbc

# include= $(IDE_HOME)/config/sybase11/sybase11.odbc

# include= $(IDE_HOME)/config/udb5/udb5.odbc

In addition, the ide_server.ini file contains many variables that impact the ODBC drivers onWindows and UNIX. These variables a re as follows. They are described in the ide_server.inifile.

# IDE_NO_BLOCK_XFER=1

# IDE_LIMIT_LOGIC=4000

# IDE_LIMIT_TEXT=4000

# IDE_STRING_LOGIC=1

# IDE_STRING_TEXT=1

# IDE_CLOB_SIZE=32000

# IDE_NO_INT_COMMIT=1

# IDE_RETRIES=3

IDE_NOT_ISOLATION_SERIAL=1

# IDE_MAP_8BIT_ASCII="?"

Source Path File Use

\Server\config\odbc odbc.odbc DataDirect Technologies - ODBC Export

\Server\config\oracle9 ideora9.odbc DataDirect Technologies - Oracle 9 Export

\Server\config\udb5 ideudb5.odbc DataDirect Technologies - UDB5 Export


52/78

Reviewing and Editing Importer Configuration Files

After insta llation, review the Data Explorer configuration files and ver ify that their settingsill p rmit D t E pl r r t rk in r n ir nm nt


53/78

Reviewing and Editing Importer Configuration Files 43

will permit Data Explorer to work in your environment.

You do not need to customize all of the configuration f iles. You need to customize only thosefiles that are required by the import and export features you want to use.

You can reta in the modifications to configuration file s from a previous release in the currentrelease. Review the configuration files that you modified in the previous release, and make thesame modifications to the corresponding configuration file in the new release.

Reviewing Configuration Files

You may need to configure one or more of these configuration files fo r your installation. Ifthere are configuration files from older versions, you must reconcile them with thenewly-installed files. If this is a first-time install, determine the data sources you will use andthe configuration files that apply to them.

When you review configuration files, follow these guidelines:

Compare the configuration files from previous releases to determine the changes that needto be incorporated into the new configuration files.

Identify new lines when comparing tag files to previous versions.

Table 6-1 shows the importer configuration files and their usage. All files are in subdirectoriesof the Config directory:

Table 6-1. Data Explorer Importer Configuration Files

Default Windows Path File Use

..\Server\Config colprof.ini Column profiling configuration

..\Server\Config\fileimp idedb2file.ini Importer - DB2

..\Server\Config\fileimp idefile.ini Importer - Flat File

..\Server\Config\informix7 ideifx.ini Importer - Informix

..\Server\Config\odbc ideodbc.ini Importer - ODBC

..\Server\Config\oracle7 ideora7.ini Importer - Oracle7



..\Server\Config\sybase10 idesyb10.ini Importer - Sybase 10

..\Server\Config\sybase11 idesyb11.ini Importer - Sybase 11

..\Server\Config\teradata ideteradata.ini Importer - Teradata

..\Server\Config\fileimp idetrillium.ini Importer - Trillium

Table 6-1. Data Explorer Importer Configuration Files



54/78


..\Server\Config\udb5 ideudb5.ini Importer - UDB5

Reviewing and Editing Tag Configuration Files

The tag configuration files are grouped in subdirectories of the config directory.

d h f ff l h l f


55/78

Reviewing and Editing Tag Configuration Files 45

Note: Updating the tag configurat ion affects only the Data Explorer user interface. You must

update the repository tables to reflect the changes you make to the configuration files.To modify the values available in Data Explorer, use tag drop down menus.

Table 6-2 lists the files you can modify:

Author, Sponsor, Assignee fields draw from the same list of values in the user.def file .

Warning: Do not change the files in the /links directory.

To update tag configuration files:

1. Using a text editor, open the appropriate text file for the field. From Data Explorer, youcan select File-Edit Server File to browse to the file location.

At the bottom of the file, the entries designate what will be displayed in the drop downmenus. An entry consists of the description that will be displayed followed by an = anda number. The numbers are sequential.

For example:

Need a decode = 3

Cleanup = 4

2. Edit the values as needed and save the file.

Updating Repository Tag Information

You must update the reposito ry tables to reflect the changes you made to the configuration

files.

Table 6-2. Data Explorer Tag Configuration Files


..\Server\Config\actions priority.tag Tag - Action ItemPriorities

..\Server\Config\actions status.tag Tag - Action ItemStatuses

..\Server\Config\actions type.tag Tag - Action ItemTypes

..\Server\Config\notes type.tag Tag - Note Types

..\Server\Config\links type.tag Tag - Link Types

..\Server\Config\rules type.tag Tag - Rule Types

..\Server\Config\xforms type.tag Tag - Transformation Types

..\Server\Config\users users.def Tag - Author/Sponsor/Assignee

Table List

To carry the descriptions you made in the configuration files into the repository, thefollowing repository tables need to be updated. The user definition (Author, Sponsor,

Assignee) does not need to be added to the repository.


56/78


actions

priority - 01ACTITMPRIO

status - E01ACTITMSTATUS

type - E01ACTITMTYPE

notes

type - E01NOTETYPE

rules

type - E01RULETYPE

xforms

type - E01TRANSFTYPE

Update Commands

To update the tag descr iptions in the repository to correspond with the type .tag, priority.tag,

or status.tag files, use the following approaches:

1. Update the initial value configuration script.

There are 10 default values registered automatically in Data Explorer if the config.sql wasrun when the repository was setup. The default values are the sequential number and theexact same description. The values can be modified prior to running the config.sql scriptfor creating the repository.

For example, the following entry inserts a type ID 2 with a description of 2 that will bedisplayed in the repository running on Microsoft SQL Server:

insert into E01NoteType values (

2, '2'

)

go

2. Update existing values.

To update the tables after the repository has been configured, it is possible to update theentries using Repository Navigator (or another query tool).

Update the necessary table entries using SQLPlus or another query tool. The followingexample changes the entry for the NoteType field that has a NoteType Description of 2.(This command needs to be run for each description that was changed).

UPDATE E01NOTETYPE

SET Description = '2'

WHERE Description = 'Dependency Assumption'


57/78

# If not specified, "NONE" is the default.

# TRIM_BLANKS= NONE

2. Uncomment the TRIM_BLANKS line by removing the # symbol and specify the


58/78


_ y g y p ystripping rule.

The default is NONE.


59/78

49

Chapter 7

Installing VSAM and IMS

Importers


Overview, 50

Installing Importers, 51

Overview

This chapter describes components that you might need to install or configure to use DataExplorer.


60/78

50 Chapter 7: Installing VSAM and IMS Importers

You can install Data Explorer Import for VSAM and Data Explorer Import for IMS onWindows systems. After installat ion, you might need to move parts of the installat ion to themainframe. For more information, see Installing Importers on page 51.

Installing Importers

Data Explorer Import for VSAM and Data Explorer Import for IMS are IBM OS/390 (MVS)applications that are used to extract data from MVS sequential files, VSAM files, or IMSdatabases The output is a flat file that can be imported to Data Explorer


61/78

Installing Importers 51

databases. The output is a flat file that can be imported to Data Explorer.

This chapter describes how to install and set up Data Explorer Import extracts running onMVS or OS/390 platforms. It also includes information about system and authorizationrequirements.

Note:An MVS system programmer must perform the tasks to install Data Explorer Import.

System Requirements

You must have the following hardware and software to install and use Data Explorer Import:

An MVS or OS/390 platform and operating system

Capability to upload the installation files from the Windows to the MVS platform

IMS for executing Data Explorer Import for IMS

Authorization Requirements

To install Data Explorer Import, the installer must have the authority to:

Copy files from the Data Explorer installation library.

Create and edit MVS data sets.

Transfer files between your workstation and MVS, using IND$FILE or FTP.

Execute the TSO/E RECEIVE command.

Submit and retrieve output from Data Explorer Import executions.

Have the proper retrieval authorizations for the data being read during an importexecution.

Have the appropriate runtime keys from Informatica to use the products.

Separate keys are required for Data Explorer Import for VSAM and Data Explorer Import forIMS.

Installation OverviewData Explorer Import is distributed with the Data Explorer installer and is installed with DataExplorer Source Profiler. The mainframe PDSs are provided as sequential files. Thesesequential files were created with the TSO/E TRANSMIT command. During installation,you recreate the PDSs from the sequential files using the TSO/E RECEIVE command.

The following steps outline the procedure you use to install Data Explorer Import:

1. Complete installation preparation tasks.

2. Upload the LOADLIB.XMI and CNTL.XMI sequential files to MVS data sets andRECEIVE the sequential files to create the LOADLIB and CNTL PDSs.


62/78


3. Create a Key dataset and populate the key entries.4. Create the Data Explorer Source Profiler JCL template files.

5. Customize the sample JCL to verify installation.

For more information on steps 4 - 5, see Command and JCL files in the Data ExplorerSource Profiler User Guide.

Step 1. PreparationThis section describes the tasks to perform before installing Data Explorer Import.

To prepare for installation:

1. Determine library usage and JOB statement changes.

Determine the libraries you will create and use for Data Explorer Import, and thechanges you must make to the Data Explorer Import JCL template files to customizethem for your site.

2. Obtain user ID and authorization.

Obtain a TSO user ID with authority to submit jobs and create the libraries you willneed to install Data Explorer Import.

You must have the appropriate authorities, including the authority to execute programsretrieving data from IMS databases. For more information, see AuthorizationRequirements on page 51.

Step 2. Upload and Receive the Sequential Files

The LOADLIB.XMI and CNTL.XMI data sets must be converted and loaded into thepartitioned data sets LOAD and JCL.

Load the data sets using the TSO/E RECEIVE command.

To populate the LOAD data set, issue the following command from the TSO READY

prompt or ISPF option 6:RECEIVE INDATASET(prefix.LOADLIB.XMI)

When prompted for the output data set name, enter:

DSNAME(prefix.LOADLIB)

Step 3. Create a Key Dataset

Use ISPF to allocate a sequential dataset or PDS that will contain runtime keys. This datasetshould be allocated with RECFM=FB and LRECL=80. Populate this dataset with the keyinformation received from Informatica.

To install and access the Data Explorer Import license key, you must have a Data Explorer


63/78

Installing Importers 53

To install and access the Data Explorer Import license key, you must have a Data Explorer

license file (ELF file) provided by Informatica, which generates licenses based on:

CPU ID of the MVS system on which Data Explorer Import products will run

Start date

End date

List of components that you have been licensed to run

To obtain and install a license key:

1. Find the CPU ID of the MVS system on which you intend to run Data Explorer Import.

2. Provide the CPU ID to Informatica Global Customer Support.

3. Informatica will respond with an ELF file (usually in the form of an email attachment).

4. Transfer the license key file to a MVS file.

5. Edit the Data Explorer Source Profiler JCL templates to refer to the key dataset.

Setting Up Repository Reports

These reports use the repository and Crystal Reports. A Crystal Reports viewer installs withthe Data Explorer client installation.

Th f ll in pr d rib h t t p th r p it r


64/78


The following process describes how to set up the repository:

1. If necessary, define ODBC.

2. Open the Repository Report.

3. Set the locat ion

4. Save the report.

Repeat steps 2-4 for each repository report.

If you have Crystal reports installed on the same machine, you can edit the databaseconnection information to use another ODBC connection or schema.

Running Crystal Reports from Data Explorer

To run Crystal Reports from Data Explorer, follow these steps:

1. Create an ODBC connection with the name IDEREPOSITORY (all caps).

2. Create a database schema "ide_repo" for the repository. Export your project(s) to thisdatabase schema.

3. To run the packaged reports on this schema, open the report and select "Refresh".

4. Provide the prompt information, the schema, and ODBC connection information.

The report will display information from the repository above.

Chapter 8


65/78

55

Chapter 8

Upgrading Data Explorer

Installations


Overview, 56

Upgrading from Data Explorer 5.0 SP4 to 8.6.1, 57 Upgrading Data Explorer from 8.6 to 8.6.1, 58

Upgrading the Repository, 60

Overview

This chapter provides information on upgrading Data Explorer installations and repositories.

To upgrade your Data Explorer installation:


66/78

56 Chapter 8: Upgrading Data Explorer Installations

1. Perform the appropriate installer upgrade procedure:

Upgrading from Data Explorer 5.0 SP4 to 8.6.1 on page 57

Upgrading Data Explorer from 8.6 to 8.6.1 on page 58

2. Perform the appropriate repository upgrade procedures:

Upgrade 5.0 to 8.6 on page 60

Upgrade 8.6 to 8.6.1 - DB2 and Sybase only on page 60

Note: If you are upgrading across multiple versions, you must perform the appropriaterepository upgrades consecutively. For example, if you are upgrading a DB2 repository from5.0 SP4 to 8.6.1, you must perform both of the above procedures in the order that they arelisted.

Upgrading from Data Explorer 5.0 SP4 to 8.6.1

Use the Data Explorer 8.6.1 installer to upgrade from Data Explorer 5.0 SP4 to 8.6.1. Thisupgrade does not overwrite Data Explorer 5.0 SP4 with the newer version. Instead, theupgrade process installs Data Explorer 8.6.1 in parallel with Data Explorer 5.0 SP4.


67/78

Upgrading fromData Explorer 5.0 SP4 to 8.6.1 57

When you upgrade Data Explorer 5.0 SP4 to Data Explorer 8.6.1, Data Explorer installs anew Listener service and alistener.ini file that contains Service Descriptions for DataExplorer 5.0 SP4 and 8.6.1. Once this process is completed, the 8.6 Listener can run both the5.0 SP4 and 8.6.1 Servers.

During the upgrade process, the installer performs the same steps used for first-timeinstallations. To upgrade Data Explorer 5.0 SP4, follow the install steps for the appropriateplatform:

To upgrade on Windows, follow the steps in Data Explorer Installation on Windows onpage 13.

To upgrade on Unix, follow the steps in Data Explorer Server Installation on Unix onpage 19.

After you upgrade your installation, perform the appropriate repository upgrade proceduresspecified in Upgrading the Repository on page 60.

Upgrading Data Explorer from 8.6 to 8.6.1

Use the 8.6.1 silent installer to upgrade Data Explorer 8.6 to Data Explorer 8.6.1.Informatica delivers the silent installer as a compressed file with the following contents:

Install executable file


68/78

58 Chapter 8: Upgrading Data Explorer Installations

installer.properties file

Readme file

Unzip this file to the Data Explorer host machine. Before running the installer, you must addwith your 8.6 installation details to the installer.properties fil e. The installer executable readsthis file to determine the location of the current installation and the type of installation toperform.

Note: The silent installer updates the Informatica components installed with Data Explorer8.6. It does not add or change the capabilities of Data Analyzer reports, ODBC drivers,Microsoft .NET framework, or the Crystal Reports viewer.

Editing The Properties File

The install.properties file contains the following settings:

USER_INSTALL_DIR. The path to the home directory of the current Data Explorer 8.6installation.

Windows Example: USER_INSTALL_DIR=C:\\Informatica \\DataExplorer8.6

UNIX Example: USER_INSTALL_DIR=/opt/Informatica/DataExplorer8.6

INSTALLER_TYPE. The type of installation: Client, Server, or Complete.

INSTALLER_UI. The type of install executable. This property is set to SILENT and mustnot be edited.

Modify the USER_INSTALL_DIR and INSTALLER_TYPE settings and save the file to thedirectory from which you will run the silent installer file.

Running The Silent Installer On All Platforms

The procedures to run the silent installer are identical for Windows and UNIX installations.

You must run the silent installer that corresponds to the product you originally installed. For

example, to upgrade Data Explorer Server you must run the Server Only version of the silentinstaller.

To run the silent installer:

1. Verify that the Listener and all other services or applications that access the InformaticaData Explorer 8.6 installation folder are not running.

On Windows machines, verify also that all client applications and any text editors used

for monitoring the log files are not running.

2. Verify your edits to the installer.properties file. Ensure that the saved file resides in thesame directory as the executable file you will run in Step 3.

3. Run the install executable.

Windows: Double-click install.exe or run install.exe from a command line.


69/78

Upgrading Data Explorer from 8.6 to 8.6.1 59

UNIX: Type sh install.bin.4. After you upgrade your insta llation, perform the appropriate reposi tory upgrade

procedures specified in Upgrading the Repository on page 60.

Note: The silent installer does not overwrite the Data Explorer 8.6 installation. Instead, theData Explorer 8.6 installation folder is renamed by adding the string backup to the end ofthe folder name. If you need to revert to the 8.6 installation for any reason, rename or deletethe current installation folder. Then, remove the string backup from the folder name of the8.6 installation folder.

Installation Logging

The silent installer creates a file named Informatica_IDE861_SilentInstaller_Debug.log. Itwrites this f ile to one of the following locations:

Windows: C:\[SYSTEM_ROOT]

UNIX: USER_HOMEThe log file replicates the values entered to the installer.properties file and reports any errorsin the file settings.


70/78

Appendix A


71/78

61

Uninstalling Data Explorer

This appendix includes the following topics:

Uninstalling on Windows, 62

Uninstalling on UNIX, 63

Uninstalling on Windows

To uninstall Data Explorer on Windows, use the Uninstall options in the Data Explorerprogram group, or use the Add or Remove Programs option provided in the WindowsControl Panel.

To uninstall the Cr stal Reports runtime application installed b Data E plorer use the Add


72/78

62 Appendix A: Uninstalling Data Explorer

To uninstall the Crystal Reports runtime application installed by Data Explorer, use the Addor Remove Programs option provided in the Windows Control Panel. If the Data Explorerclient installer installed the Microsoft .NET framework on your machine, you can also use the

Add or Remove Programs option to remove th is framework.


73/78


74/78

64 Appendix A: Uninstalling Data Explorer

Index


75/78

65

AAIX

memory limitations 3application servers

configuring 36

CClient

system requirements 3configuring

application servers 36UNIX Server environment variables 37

creating

key datasets 53Crystal Reports

prerequisites 11

DData Analyzer Reports 11Data Explorer

disk space requirements 5

installation on UNIX 21installation requirements 3

disk space

minimum requirements 5

Eenvironment variables

IDE_ELMHOST 37IDE_HOME 35ide_server.ini 35

HHP-UX

memory limitations 4

IIDE_ELMHOST

environment variables 37IDE_HOME

environment variable 35

ide_server.inienvironment variables 35

importer configuration filesUNIX 43

Windows 43installation

system requirements 3installing

Data Explorer on UNIX 21

preparing for 52

JJOB statement changes

determining before installation 52

Kkey datasets

TTag Configuration Files 45

tag configuration files 45Teradata Driver Requirements 4

U


76/78

66 Index

key datasets

creating 53

Llibrary usage

determining before installation 52

License ManagementListener 9licenses

obtainingobtaining on MVS 53

Listenersubnets 37

Mmemory limitations

database 3

Metadata Importer Configuration Files 43

Pprivileges

required for UNIX installation 21

RRepository

disk space requirements 5

Ssequential files

uploading and receiving 52Server

system requirements 3system requirements

Data Explorer 3minimum 5

UUMI

ethernet addressfor a Windows machine 29generating for a UNIX machine 29

Unique Machine IdentifierSeeUMI

UNIX

configuring the Server 37generating a UMI 29

importer configuration files 43required privileges 21stopping the install script 21

upgrade options 7user ID

obtaining before installation 52

WWindows

importer configuration files 43

NOTICES

This Informatica product (the Software) includes certain drivers (the DataDirect Drivers) from DataDirect Technologies, an operating company of ProgressSoftware Corporation (DataDirect) which are subject to the following terms and conditions:

1. THE DATADIRECT DRIVERS ARE PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNON-INFRINGEMENT.

2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT,

INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS,WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE THESE LIMITATIONS APPLY TO ALL CAUSES OF


77/78

WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OFACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY,MISREPRESENTATION AND OTHER TORTS.


78/78

Documents

De 861 InstallGuide