DE 86 InstallGuide

Installation Guide
Informatica® Data Explorer

(Version 8.6)
Informatica Data Explorer Installation Guide
Version 8.6
June 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 containing
restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be
reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This
Software 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 as
provided 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 FAR
52.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 report
them 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 Informatica
Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their
respective owners.
DISCLAIMER: Informatica Corporation provides this documentation “as is” without warranty of any kind, either express or implied, including, but not limited
to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or
documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The
information in this software and documentation is subject to change at any time without notice.
Part Number: IDE-ING-86000-0010

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Informatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Informatica Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Informatica 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Databases Supported for the Data Explorer Repository . . . . . . . . . . . . . . . 4
Teradata Driver Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Calculating Repository Disk Space Requirements . . . . . . . . . . . . . . . . . . . 5
Data Explorer Product Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
JDBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Reporting Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Data Analyzer Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Crystal Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 2: Installing Data Explorer on Windows . . . . . . . . . . . . . . . . 11

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Deployment Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Installing The Complete Data Explorer Product Set . . . . . . . . . . . . . . . . . . . 14
Installing Data Explorer Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Installing Data Explorer Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Chapter 3: Installing Data Explorer on UNIX. . . . . . . . . . . . . . . . . . . . 21

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Installing Data Explorer on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
iii
Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Installing Data Explorer Server in Console Mode . . . . . . . . . . . . . . . . . . 23
Installing Data Explorer Server in GUI Mode . . . . . . . . . . . . . . . . . . . . . 25
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
Working with Data Explorer Listener Services . . . . . . . . . . . . . . . . . . . . . . . 31
Installing Data Explorer 8.6 on a System with Data Explorer 4.4 . . . . . . . 31
Starting and Stopping the Data Explorer Listener . . . . . . . . . . . . . . . . . . . . . 33
Chapter 5: Setting Up the Data Explorer Server Environment . . . . . . 35

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Configuring Data Explorer Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Setting the Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Granting Privileges to a Remote Server . . . . . . . . . . . . . . . . . . . . . . . . . 37
Configuring the Windows Server as an Application Server . . . . . . . . . . . 38
Running Server Component Across Subnets . . . . . . . . . . . . . . . . . . . . . . . . . 39
Chapter 6: Reviewing Configuration Files . . . . . . . . . . . . . . . . . . . . . 41

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Configuring ODBC Drivers for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Reviewing and Editing Importer Configuration Files . . . . . . . . . . . . . . . . . . 45
Reviewing Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Reviewing and Editing Tag Configuration Files . . . . . . . . . . . . . . . . . . . . . . 47
Updating Repository Tag Information . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Blank Stripping Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Chapter 7: Installing VSAM and IMS Importers. . . . . . . . . . . . . . . . . .51

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Installing Importers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Authorization Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Setting Up Repository Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
iv Table of Contents
Running Crystal Reports from Data Explorer . . . . . . . . . . . . . . . . . . . . . 56
Chapter 8: Upgrading the Data Explorer Repository . . . . . . . . . . . . . 57

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Upgrading the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Running the Data Explorer Repository Upgrade Scripts . . . . . . . . . . . . . 59
Chapter A: Uninstalling Data Explorer . . . . . . . . . . . . . . . . . . . . . . . . 61

Uninstalling on Windows and UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Table of Contents v
vi Table of Contents
Preface
Welcome to Data Explorer, the Informatica software product suite that provides a complete
and 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 multiple
source systems and eases the process of scoping the size and complexity of a migration or data
integration project.
vii
About This Book
The Data Explorer Installation Guide provides information about installing and configuring
Data Explorer. The Data Explorer Installation Guide is written for the system administrators
who are responsible for setting up Data Explorer for an organization. This guide assumes you
have knowledge of the operating systems and relational databases in your environment.
The material in this book is also available online.
viii Preface
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 the
Informatica user community.
Informatica Documentation
The Informatica Documentation team takes every effort to create accurate, usable
documentation. If you have questions, comments, or ideas about this documentation, contact
the Informatica Documentation team through email at
infa_documentation@informatica.com. We will use your feedback to improve our
documentation. 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 site
contains information about Informatica, its background, upcoming events, and sales offices.
You will also find product and partner information. The services area of the site includes
important information about technical support, training and education, and implementation
services.
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 known
technical issues about Informatica products. You can also find answers to frequently asked
questions, technical white papers, and technical tips.
Informatica Global Customer Support

There are many ways to access Informatica Global Customer Support. You can contact a
Customer Support Center through telephone, email, or the WebSupport Service.
Use the following email addresses to contact Informatica Global Customer Support:
♦ support@informatica.com for technical inquiries
♦ support_admin@informatica.com for general customer service requests
WebSupport requires a user name and password. You can request a user name and password at
http://my.informatica.com.
Informatica Resources ix
Use the following telephone numbers to contact Informatica Global Customer Support:
North America / South America Europe / Middle East / Africa Asia / Australia
Informatica Corporation Informatica Software Ltd. Informatica Business

Headquarters 6 Waltham Park Solutions Pvt. Ltd.
100 Cardinal Way Waltham Road, White Waltham Diamond District
Redwood City, California Maidenhead, Berkshire Tower B, 3rd Floor
94063 SL6 3TN 150 Airport Road
United States United Kingdom Bangalore 560 008
India
Toll Free Toll Free Toll Free

+1 877 463 2435 00 800 4632 4357 Australia: 1 800 151 830
Singapore: 001 800 4632 4357
Standard Rate Standard Rate Standard Rate

Brazil: +55 11 3523 7761 Belgium: +32 15 281 702 India: +91 80 4112 5738
Mexico: +52 55 1168 9763 France: +33 1 41 38 92 26
United States: +1 650 385 5800 Germany: +49 1805 702 702
Netherlands: +31 306 022 797
United Kingdom: +44 1628 511 445
x Preface
Chapter 1
Before You Begin
This chapter includes the following topics:

♦ Overview, 2
♦ System Requirements, 3
♦ Data Explorer Product Licensing, 7
♦ Disk Space Requirements, 5
♦ Data Explorer Product Licensing, 7
♦ JDBC Drivers, 8
♦ Reporting Capabilities, 9
1
Overview
The Data Explorer 8.6 installers provide a unified install environment for Data Explorer
applications. It also installs a Crystal Reports viewer and provides install options for new
reports for PowerCenter Data Analyzer, DataDirect ODBC drivers, and the Microsoft .NET
framework.
Data Explorer supports a client-server architecture and works on the .NET™ framework.
Note: Data Explorer 8.6 does not install the full Crystal Reports application. It installs a
runtime engine for Crystal Reports that allows you to view but not edit such reports.
This chapter discusses the minimum hardware, software, and database requirements for Data
Explorer. It also provides information about Data Explorer license requirements and the
OBBC and JDBC drivers you require to connect to the Data Explorer repository.
2 Chapter 1: Before You Begin

System Requirements
The system on which you install the Data Explorer components must meet the minimum
hardware and software requirements.
You can install the client and server on the same system or on separate systems.
Data Explorer Client

The Data Explorer Client requires approximately 280 MB of disk space. To install Data
Explorer 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 installer
provides 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 Data
Explorer Server, you need the following:
♦ 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 by
512-1024 MB of swap space. Large projects might require two to three times more memory
and swap space. If you are running other applications in addition to Data Explorer, additional
memory 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 the
machine, type, and amount of data your system will need to process, the default data space
will be inadequate. Increase the default data space size to a higher value, for example 512 MB,
or set an unlimited setting (-1).
System Requirements 3
Memory Limitations on HP-UX Platforms
On an HP-UX platform, the data space size is controlled by the OS parameter maxdsiz. The
default size is too small for large projects and must be increased to 512 MB or the maximum
system-allowed value.
You can use the HP system administration tool sam to increase the maxdsiz parameter in the
kernel.
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 Explorer
repository. Data Explorer installs these drivers.
Teradata Driver Requirements

If you will work with ODBC 5.3 Teradata drivers, verify that the Teradata 32-bit native
binaries are installed before running the Data Explorer installer.
Note: Following a Data Explorer install on UNIX, Teradata users must append the
appropriate value from this table to the path in the file server860/config/odbc/ideodbc.ini:
HPUX SHLIB_PATH
Solaris LD_LIBRARY_PATH
AIX LIBPATH

Disk Space Requirements
All disk space requirements indicated in this section are for the components installed from the
Data Explorer installer. 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 size
of the repository.
Table 1-1 provides a list of the platforms that Data Explorer supports and the disk space for
each Data Explorer application:
Table 1-1. Disk Space Requirements
Space
Application Platform-Specific Considerations
Required
Data Explorer Server Sun Solaris 200 MB

HP-UX
IBM AIX
Windows 280 MB
Additional disk space required during installation 45 MB
Data Explorer Client Windows 230 MB
Note: For more information about project disk space requirements, see the Data Explorer
System 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 database
administrator build tablespaces that you can expand later as per your requirements.
Table 1-2 describes the factors used in calculating the disk space requirements for the
repository:
Table 1-2. Disk Space Calculation
Term Meaning
Data Explorer project size Value calculated for the project’s metric.
Number of Data Explorer projects Maximum number of Data Explorer projects expected to be stored in the repository
at any given time.
Disk Space Requirements 5

Table 1-2. Disk Space Calculation
Term Meaning
Number of Data Explorer FTM Maximum number of schemas, originally created by the Data Explorer FTM
Schemas product, stored in the repository at any given time.
Number of Source Profiler Maximum number of schemas, originally created by the Source Profiler product,
Schemas 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 Number of bytes expected to be stored in schemas created by the Data Explorer
Schema size Source Profiler product.
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 administrator
establishes that the RDBMS overhead is 13 MB and that a factor of 6 must be applied to any
data loaded into the database. You can use the formula given on page 5 to calculate the
repository 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.

Data Explorer Product Licensing
Before you can use Data Explorer, the Data Explorer Listener must be running. The Listener
is 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, Data
Explorer Source Profiler, Data Explorer FTM, Data Explorer Import, Data Explorer XML,
and the DataDirect ODBC drivers. It maintains a central database of tokens based on
predetermined 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, the
Listener denies the request.
♦ It collects tokens when applications terminate or when it determines that an application is
no longer running.
Data Explorer Product Licensing 7

JDBC Drivers
If you are using Data Explorer FTM/XML or Repository Navigator, use JDBC Type IV
drivers.
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.

Reporting Capabilities
Data Explorer supports report generation with PowerCenter Data Analyzer and through
Crystal Reports.
Data Analyzer Reports

The Data Explorer 8.6 installer can load pre-designed repository reports to the Data Explorer
repository 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 to
PowerCenter Advanced Edition is available before you install Data Explorer.
If you select the option to deploy Data Analyzer Reports, the Data Explorer installer prompts
you to provide the following information:
♦ Data Analyzer URL. The address of the Data Analyzer reporting service. This address has
the following format:
http://<hostname>:<port>/ias-<reporting_service_name>
♦ User ID. A valid user ID for Data Analyzer. This password must include the namespace
used by Data Analyzer. The default namespace is Native, and the format for the user ID is
as follows:
[userid]@Native
♦ Password. A valid password for Data Analyzer.
Data Analyzer requires PowerCenter Advanced Edition. For more information, see your
PowerCenter Data Analyzer documentation.
Crystal Reports
Data Explorer install a runtime Crystal Reports viewer. Uninstall any current versions of
Crystal Reports before you run the Data Explorer installer. You can install an external version
of the Crystal Reports application after you install Data Explorer.
Reporting Capabilities 9
Chapter 2
Installing Data Explorer on

Windows
♦ Overview, 12
♦ Installing The Complete Data Explorer Product Set, 14
♦ Installing Data Explorer Client, 16
♦ Installing Data Explorer Server, 18
11
Overview
This chapter provides the steps to install the Data Explorer product suite on Windows
machines.
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 PowerCenter
Data Analyzer.
The installable components with each option are as follows:
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 SP1 for Windows Y Y
The installation process installs the ODBC drivers, Java Runtime Environment, and
Microsoft .NET framework if it does not detect them on the install target machine.
Deployment Summary
To install and activate Data Explorer, complete the following steps:
12 Chapter 2: Installing Data Explorer on Windows

1. If you will deploy Data Explorer reports for Data Analyzer, verify that PowerCenter
Advanced Edition is installed and that you know the URL, username, password, and
namespace used by PowerCenter Analyzer.
2. Run the Data Explorer installer. You can choose to install the Data Explorer Client,
Server, and Data Analyzer Reports on the same machine.
3. Obtain a product license from Informatica Global Customer Support and add the license
to the system.
The Global Customer Support team needs the UMI (unique machine identifier) of the
install machine to generate your license. The install process displays the UMI of the
machine that hosts the install files. For more information, see “Obtaining and Installing
the 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 installer
includes 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 Data
Explorer System Administration Guide and the readme.txt files located in the
<installDirectory>/Repository/sql/<databaseType> 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 35.
Data Explorer includes configuration files that you can modify to enable Data Explorer
establish data sources from which to profile data and export the results. For more
information, see “Reviewing Configuration Files” on page 41.
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” on
page 51.
Overview 13
Installing The Complete Data Explorer Product Set
This procedure installs all client and server components on a single machine.
Before installing, verify that your environment meets the minimum system requirements
described in chapter 1.
To install a complete version of Data Explorer on Windows:
1. Open the installable files that you received from Informatica. Locate and run the
install.bat file.
2. The InstallAnywhere installation wizard opens. At the Welcome screen, click Next.
3. Choose the product set to install. The options are Complete and Custom.
Choose Complete to install all components on the local machine. Choose Custom to
select from Server, Client, and Reports options.
4. If you are running the installer on the machine that will host Data Explorer, copy or
write down the unique machine identifier (UMI) that displays in the Choose Install set
window. You will need the UMI of the machine that will run Data Explorer to obtain
your product license.
You can also run the UMI utility that installs with Data Explorer post-install to obtain
the UMI.
5. Specify the installation directory. The default directory is
C:\Informatica\DataExplorer8.6
6. Choose the directory to which Data Explorer can write temporary files. The default
directory is C:\Windows\temp.
Note: For performance reasons, this directory should not reside on the same drive that
stores the paging file. Data Explorer Server uses this directory to write potentially large
sets of temporary results during profiling.
7. The client installer prompts you to install Microsoft. 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 Data Explorer client installations.
8. If you are installing Data Explorer reports for Data Analyzer, check the Deploy DA
Reports option and enter the connection details for Data Analyzer. Provide the following
information:
− Data Analyzer URL. The address of the Data Analyzer reporting service. This address
has the following format:
The reporting service is started on the PowerCenter Admin Console.
− User ID. A valid user ID for Data Analyzer. This password must include the namespace
used by Data Analyzer. The default namespace is Native, and the format for the user ID
is as follows:

[userid]@Native
− Password. A valid password for Data Analyzer.
9. Choose the ODBC drivers to install. The options are ODBC 5.2 Service Pack 2 and
ODBC 5.3.
10. Review the summary of your installation selections, and click Install.
The Data Explorer and ODBC driver installation commences.
11. ODBC Driver Installation. ODBC driver installation launches as part of the Data
Explorer install. When prompted, click Done to acknowledge the installation of the
ODBC Drivers.
Use Alt-Tab if necessary to toggle to the ODBC Driver install window.
12. Microsoft .NET Installation. The Microsoft. NET Framework 1.1 installation
commences. Accept the prompts to install.
The Microsoft. NET Framework 1.1 installation requires a machine restart. Select the
option to Restart Later when prompted.
13. Review the Data Explorer Listener settings and edit them if required. The settings are as
follows:
Listener Port Number. The port used by the Listener in communications between Server
and Client. The default port is 1416.
Hostname of Listener. The host machine of the Data Explorer Listener application.
Port Number for Listener. The port used by the Listener in communications between
Server and Client. The default port is 1416.
Click Apply to implement the Listener settings.
Note: If you use a non-default port, you must edit the ide_server.ini file to remove the
quotation marks from the IDE_ELMPORT and IDE_LISTENER_PORT entries.
14. Review the installation summary and verify the successful installation of Data Explorer.
Click Done to exit the installer.
Following installation, you must add your license file to the Listener folder. For more
information, see “Obtaining and Installing the Data Explorer License” on page 29.
Installing The Complete Data Explorer Product Set 15

Installing Data Explorer Client
To install Data Explorer Client on Windows:
install.bat file.
Choose Custom to access the Client options.
the UMI.
5. Select the Client option from the Custom Install Component screen.
When you select this option, the Deploy DA (Data Analyzer) Reports option is selected
by default. This option installs dashboards and reports that you can run from
PowerCenter Data Analyzer to the Data Explorer repository. Clear this option if you do
not wish to install these reports.
The Client installer installs Crystal Reports independently of the Data Analyzer Reports
option.
7. The client installer prompts you to install Microsoft. 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 Data Explorer client installations.
information:
is as follows:

[userid]@Native
ODBC 5.3.
ODBC Drivers.
12. Microsoft .NET Installation. The Microsoft. NET Framework 1.1 installation
commences. Accept the prompts to install.
The Microsoft. NET Framework 1.1 installation requires a machine restart. Select the
option to Restart Later when prompted.
Following installation, you must add your license file to the Listener folder. For more
information on installing the license file, see For more information, see “Obtaining and
Installing the Data Explorer License” on page 29.
Installing Data Explorer Client 17

Installing Data Explorer Server
To install Data Explorer Server on Windows:
install.bat file.
Choose Custom to access the Server options.
the UMI.
5. Select the Server option from the Custom Install Component screen.
When you select this option, the Deploy DA (Data Analyzer) Reports option is selected
by default. This option installs dashboards and reports that you can run from
PowerCenter Data Analyzer to the Data Explorer repository. Clear this option if you do
not wish to install these reports.
7. Choose the directory to which Data Explorer can write temporary files. The default
directory is C:\Windows\temp.
information:
is as follows:

[userid]@Native
ODBC 5.3.
ODBC Drivers.
12. Review the Data Explorer Listener settings and edit them if required. The settings are as
follows:
Listener Port Number. The port used by the Listener in communications between Server
and Client. The default port is 1416.
Hostname of Listener. The host machine of the Data Explorer Listener application.
Port Number for Listener. The port used by the Listener in communications between
Server and Client. The default port is 1416.
Click Apply to implement the Listener settings.
Installing Data Explorer Server 19

Chapter 3
Installing Data Explorer on

UNIX
♦ Overview, 22
♦ Installing Data Explorer on UNIX, 23
21
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 Server
♦ Data Explorer Listener
♦ Repository Creation Scripts
22 Chapter 3: Installing Data Explorer on UNIX

Installing Data Explorer on UNIX
You can install Data Explorer Server on an IBM AIX, HP-UX, or a Sun Solaris UNIX server
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 you
will install Data Explorer Server.
♦ Root permission on the UNIX server on which you will install the Data Explorer Server.
The installation script modifies certain system files during the installation for which it is
necessary for you to have root privileges:
− 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 Explorer
License Manager.
♦ A copy of the license file (license.elf ). For more information, see “Obtaining and
Installing the Data Explorer License” on page 29.
Installing Data Explorer Server in Console Mode

The following steps describe the Server installation on a Solaris machine with a Bourne shell.
To install Data Explorer Server in console mode:
1. Log in to the UNIX system with root permission.

2. Navigate to the directory where you have copied the UNIX install files.
3. Run sh install.sh.
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 if
Listener 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 install, type back. To exit the installer at
any 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.
Installing Data Explorer on UNIX 23

9. Custom installers only: choose the install components. The options are 1 (default) for
Server 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, and
press Enter.
12. Choose the directory that the installer will use for temp directory. The default directory
is /tmp. Press Enter to accept the default or type an alternative directory path and press
Enter.
13. Indicate if you wish to deploy Data Analyzer Reports. The options are 1 (default) for No
and 2 for Yes. Make your selection and press Enter.
14. If you are deploying Data Analyzer Reports, provide the following information when
prompted:
− The url to the PowerCenter reporting service machine. This address has the following
format:
− The reporting service is started on the PowerCenter Admin Console.
− A valid user ID for Data Analyzer. The default is Administrator@Native, where native is
the namespace used by Data Analyzer.
− A valid password for Data Analyzer.
15. Review the pre-installation details, and press Enter to continue.
16. Enter the listener port number. Press Enter to accept the default (1416) or type a port
number and press Enter.
17. The installer completes with a message informing you of successful installation to your
selected directory. Press Enter to end the install process.
If you have an license key file (license.elf ), you may install it by copying it to the
/opt/Informatica/DataExplorer860/listener directory. The Data Explorer Listener will
auto detect it and start issuing licenses.
Note: The UNIX installation automatically writes the DataDirect 5.3 ODBC drivers to the
installed path when it installs the Data Explorer Server. For more information, see
“Configuring ODBC Drivers for UNIX” on page 43.

Installing Data Explorer Server in GUI Mode
The following steps describe the Server installation on a UNIX machine with X Window
System support.
To install Data Explorer Server in GUI mode:
1. Log in to the UNIX system with root permission.

2. Navigate to the directory where you have copied the UNIX install files.
3. Run sh install.sh.
4. When prompted, type G for GUI 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 if
Listener services are running.
6. At the Welcome screen, click Next.
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.
8. On the Choose Install set screen, take note of the unique machine ID, and click Next.
9. Custom installers only: choose the install components. The options are Server and
Deploy Data Analyzer reports. Click Next.
10. Choose the install directory. The default directory on UNIX is
/opt/Informatica/DataExplorer860
Click Browse to select a new directory. Click Next to accept the directory shown
onscreen.
11. 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 shown
onscreen.
12. Optional: select the option to deploy Data Analyzer Reports. If you are deploying Data
Analyzer Reports, provide the following information:
is as follows:
[userid]@Native
Installing Data Explorer on UNIX 25

13. Review the pre-installation details, and click Install.
14. The installer completes with a message informing you of successful installation to your
selected directory. Click Done to end the install process.
If you have an license key file (license.elf ), you may install it by copying it to the
/opt/Informatica/DataExplorer860/listener directory. The Data Explorer Listener will
auto detect it and start issuing licenses.
The UNIX installation automatically writes the DataDirect 5.3 ODBC drivers to the
installed path when it installs the Data Explorer Server. For more information, see
“Configuring ODBC Drivers for UNIX” on page 43.

Chapter 4
Post-Installation Steps

♦ Overview, 28
♦ Obtaining and Installing the Data Explorer License, 29
♦ Working with Data Explorer Listener Services, 31
♦ Starting and Stopping the Data Explorer Listener, 33
27
Overview
This chapter describes the steps to take following installation to activate your Data Explorer
8.6 installation.
It also contains information on configuring a Data Explorer 8.6 installation to run alongside
an older Data Explorer installation.
28 Chapter 4: Post-Installation Steps

Obtaining and Installing the Data Explorer License
Before you run Data Explorer, you must obtain a Data Explorer license and install it on the
system that hosts the Data Explorer Server. Informatica uses the UMI to create a license file
specific to your installation.
Note: If you set up the Data Explorer Server and Listener on separate systems, you need to
obtain 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

To determine the UMI for the system hosting the Data Explorer Server, run the UMI utility.
This file is named ideumi.exe. On Windows, the default location for this file is
C:\Informatica\DataExplorer8.6\Server\bin directory.
The install wizard provides the UMI of the machine that hosts the installer. If this is also the
machine on which Data Explorer is being installed, you can use this UMI.
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:
Platform Command
HP-UX /usr/bin/uname -i
AIX /usr/bin/uname -l
Solaris /usr/bin/hostid
Obtaining the Data Explorer License

To use Data Explorer, you must obtain a license file from Informatica Global Customer
Support. Informatica requires a Unique Machine Identifier (UMI) to generate the license for
the 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:
♦ UMI
♦ Start date
Obtaining and Installing the Data Explorer License 29

♦ End date
♦ Number of tokens
♦ List of licensed machines on which the Data Explorer Server can run
♦ List of components you have licensed
Informatica sends you a license file, license.elf, in the form of an email attachment when you
provide the UMI. Although you can install all components, you can use only those
components for which you have purchased licenses.
As the license file includes information on the UMI, start date, and end date, the Data
Explorer Listener will run only on the specific system and within the defined time period.
You can change the token count by requesting for a new license file from Informatica Global
Customer Support.
To obtain a license:
1. Determine the UMI of the machine on which you installed the Data Explorer
Listener/License Manager.
2. Determine the UMI(s) of the system on which you installed the Data Explorer Server
components.
3. Email your UMI(s) with a license request to Informatica Global Customer Support.
Informatica Global Customer Support sends you a license file as an email attachment.
4. Copy the license file to the system on which you installed the Listener.
The Data Explorer install process writes a placeholder key file named license.elf to the
listener directory. Replace this file with the file from Global Customer Support. You can
modify the license file name. if you do so, you must modify the entry for the license file
name in the listener.ini file to match the new name.
If you want to purchase additional licenses, contact Informatica to obtain Data Explorer
licenses for your UMI.
Installing the Data Explorer License

To install a new Data Explorer license on a Windows system, copy the license.elf file into the
Listener directory of your installation. The Data Explorer Listener reads the license.elf file
and manages access to the licensed components. You do not need to stop and restart the
Listener Service after you copy the license.elf file.
To install a new Data Explorer license on a UNIX system, copy or FTP the license.elf file in
ASCII mode to the system where the Data Explorer Listener is installed, and then copy the
file to the following directory:
/opt/Informatica/DataExplorer860/listener
For more information about setting up the Data Explorer Listener, see the Data Explorer
System Administration Guide.

Working with Data Explorer Listener Services
The Data Explorer 8.6 installer can detect a Data Explorer 5.0 installation and migrate the
5.0 Listener entries to the newly installed 8.6 Listener. Once this process is completed, the 8.6
Listener can run both the 5.0 and 8.6 Servers.
To install Data Explorer 8.6 alongside Data Explorer 4.4, you must make several
configuration changes. You must also inform Informatica Global Customer Support that your
license.elf file must support this configuration.
Installing Data Explorer 8.6 on a System with Data Explorer 4.4

On the Windows platform, if you are installing Data Explorer 8.6 to a system with a current
Data Explorer 4.4 installation, Data Explorer will install a new Listener service and a
listener.ini file that contains Service Descriptions for Data Explorer 8.6 only. The installer
does not update the listener.ini file to reflect the Data Explorer 4.4 Services Description
paths.
To continue using Data Explorer 4.4 alongside Data Explorer 8.6:
1. Back up the Data Explorer 4.4 Listener file before you begin the Data Explorer 8.6
installation.
2. Once Data Explorer 8.6 is installed, copy the Service Descriptions that reflect the Data
Explorer 4.4 installation path from the 4.4 listener file to the 8.6 listener file.
For example, if you used the default installation path for Axio 4.4, the copied section
resembles the section below:
[Axio_Server_440]
Service= "Axio Server"

Version= 4.4.0.1039
Type= service
Executable= "C:\Program Files\Evoke Software\Axio Server

4.4\bin\axio_server.exe"
Arguments= ""
Description= "Axio Server Build 4.4.0.1039"
[Axio_B_Server_440]
Service= "Axio B Server"
Version= 4.4.0.1039
Type= service
Executable= "C:\Program Files\Evoke Software\Axio Server

4.4\bin\axio_server.exe"
Arguments= "-batch"
Description= "Axio Batch Server Build 4.4.0.1039"
Working with Data Explorer Listener Services 31

Add this information under the Service Description section. You now have two Service
Descriptions detailing the path to the binaries for the Data Explorer 4.4 and Data
Explorer 8.6 installations.
3. Browse the 4.4 installation for a password.txt file. This file exists if a 4.4 user created
Listener users. Copy this file to the same path in the new installation.
4. Copy any other configuration options, such as port numbers or firewall settings, from the
old listener.ini file to the 8.6 listener.ini file.
5. Stop and uninstall the old Listener.
6. Restart the 8.6 Listener
For more information on required updates, contact Informatica Global Customer
Support.

Starting and Stopping the Data Explorer Listener
The following steps explain the options for starting and stopping the Data Explorer Listener
on 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 Administrative 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:
<Install_dir>/listener/bin/S99idelistener start
To stop the Data Explorer Listener on UNIX, run the following command:
<Install_dir>/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 this
interface to start the Listener.
1. Open a web browser at a URL in the following format:
http://<ServerMachineName>:<PortNumber>
where the port number is the Data Explorer Listener port. The default installation setting
is port 1416.
2. Log in and select the Administration option in the Listener section. If you are accessing
the 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.
Starting and Stopping the Data Explorer Listener 33

Chapter 5
Setting Up the Data Explorer

Server Environment
♦ Overview, 36
♦ Configuring Data Explorer Server, 37
♦ Running Server Component Across Subnets, 39
35
Overview
For Data Explorer Server to run more efficiently, you need to configure the system that hosts
the Data Explorer Server.
This chapter describes the steps you can take to configure Data Explorer and to run server
components across subnets.
36 Chapter 5: Setting Up the Data Explorer Server Environment

Configuring Data Explorer Server
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 is
C:\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:
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 Identifies the location of the temporary directory. Set this variable when you want to specify a
TMPDIR (UNIX) 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. If you use a non-default port, edit the
ide_server.ini file to remove the quotation marks from the IDE_ELMPORT and
IDE_LISTENER_PORT entries.
IDE_HOME Indicates the location of the Data Explorer Server installation.
Granting Privileges to a Remote Server

If your users run the Data Explorer Client against a remote Windows server, you must grant
them logon privileges to access the Windows server.
The users must also have write access on the Windows server to save their projects and log
files on the server. To grant write access to the Windows server, you must grant Log on
Locally privileges to a user or group of users.
Configuring Data Explorer Server 37

To grant local log on rights on a Windows XP Professional system:
1. Double-click Administrative Tools from the Control Panel.

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 Name
field.
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 instead
of 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 for
applications to run. This causes the system to slowdown and the applications to crash. This
setting dramatically improves performance when reading files equal to or greater than the
physical memory of the machine or when multiple applications are processing large amounts
of I/O.
If you plan to run the Data Explorer Server on Windows, you might need to configure these
servers to Maximize Throughput for Network Applications.

Running Server Component Across Subnets
To run the Data Explorer Server and license server on different subnets, you must set the
IDE_ELMHOST environment variable. Locate this variable in the ide_server.ini file.
Note: To run Data Explorer Navigator, Source Profiler, and FTM/XML, set the
IDE_ELMHOST environment variable on the client system. This enables the programs to
communicate 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 (#) renders
the variable inactive.
4. Replace localhost with the name or IP address of the machine running the license server.
5. Save the file.
Running Server Component Across Subnets 39

Chapter 6
Reviewing Configuration
Files
♦ Overview, 42
♦ Configuring ODBC Drivers for UNIX, 43
♦ Reviewing and Editing Importer Configuration Files, 45
♦ Reviewing and Editing Tag Configuration Files, 47
41
Overview
This chapter describes the configuration tasks you can perform to prepare Data Explorer for
your environment. The procedures in this chapter cover reviewing and editing configuration
files 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 files reside in
directories beneath the following directory:
C:\Informatica\DataExplorer8.6\Server\config
If your Data Explorer installation directory is /opt/informatica, the configuration files are in
the following directory:
/opt/Informatica/DataExplorer860/config
The config directory also contains configuration files used by Data Explorer that provide
project-specific values and settings.
For more information about configuration, see the Data Explorer System Administration
Guide.
42 Chapter 6: Reviewing Configuration Files

Configuring ODBC Drivers for UNIX
On UNIX, you must verify the environment variables for the ODBC driver and database.
This table shows the locations of the files that you may need to update to enable ODBC
export to the repository:
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
The ODBC configuration files are defined in the ide_server.ini file as include values. The
odbc.odbc file must be included.
The odbc.odbc file defines the location of the ODBC drivers. It provides the location of the
odbc.ini file to the Data Explorer Server.
If you plan to export data to the Data Explorer repository, you may want to uncomment the
line 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 on
Windows and UNIX. These variables are as follows. They are described in the ide_server.ini
file.
# 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="?"
Configuring ODBC Drivers for UNIX 43

# IDE_REPOS_TRACE=trace.log

Reviewing and Editing Importer Configuration Files
After installation, review the Data Explorer configuration files and verify that their settings
will permit Data Explorer to work in your environment.
You do not need to customize all of the configuration files. You need to customize only those
files that are required by the import and export features you want to use.
You can retain the modifications to configuration files from a previous release in the current
release. Review the configuration files that you modified in the previous release, and make the
same 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 for your installation. If
there are configuration files from older versions, you must reconcile them with the
newly-installed files. If this is a first-time install, determine the data sources you will use and
the 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 need
to 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 subdirectories
of 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
Reviewing and Editing Importer Configuration Files 45

Table 6-1. Data Explorer Importer Configuration Files
..\Server\Config\fileimp idetrillium.ini Importer - Trillium
..\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.
Note: Updating the tag configuration 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:
Table 6-2. Data Explorer Tag Configuration Files
..\Server\Config\actions priority.tag Tag - Action Item Priorities
..\Server\Config\actions status.tag Tag - Action Item Statuses
..\Server\Config\actions type.tag Tag - Action Item Types
..\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
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, you
can 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 down
menus. An entry consists of the description that will be displayed followed by an “=” and
a 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 repository tables to reflect the changes you made to the configuration
files.
Reviewing and Editing Tag Configuration Files 47

Table List
To carry the descriptions you made in the configuration files into the repository, the
following repository tables need to be updated. The user definition (Author, Sponsor,
Assignee) does not need to be added to the repository.
actions
priority - 01ACTITMPRIO
status - E01ACTITMSTATUS
type - E01ACTITMTYPE
notes
type - E01NOTETYPE
rules
type - E01RULETYPE
xforms
type - E01TRANSFTYPE
Update Commands
To update the tag descriptions 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 was
run when the repository was setup. The default values are the sequential number and the
exact same description. The values can be modified prior to running the config.sql script
for creating the repository.
For example, the following entry inserts a type ID 2 with a description of 2 that will be
displayed 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 the
entries using Repository Navigator (or another query tool).
Update the necessary table entries using SQLPlus or another query tool. The following
example 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'

3. Manually insert values.
It is possible to manually add entries using the Repository Navigator (or another query
tool).
If it is necessary to add entries into the table, use SQLPlus or another query tool to run
the necessary insert command. The following example inserts a new entry for the
NoteType field that has a NoteType ID 50 and a description of Marks Test. (This
command needs to be run for each description that was changed).
insert into E01Notetype values (50, 'Marks Test')
4. Validate table entries, listing all of the existing values in the tag configuration tables.
To do this:
♦ Start Repository Navigator.
♦ Choose Table Viewer.
♦ Type the necessary entries into the Query window. The following query returns all
values for the NoteType table:
Select * FROM E01Notetype
♦ Click Run Query.

The response that comes back displays all of the type IDs and the corresponding
description that exist for that table.
Blank Stripping Configuration

Each of the configuration files are grouped according to the importer type in the directories
described below. To modify the blank stripping rule used by default in Data Explorer, modify
the appropriate file. For more information on blank stripping, see the appendixes of the Data
Explorer User Guide.
Table 6-2 on page 47 lists the configuration files for the importers.
To update the importer configuration files for blank stripping:
1. Using a text editor, open the appropriate file for the field.
From Data Explorer, you can select File/Edit Server File to browse to the file location. In
each of the configuration files there is a section that designates the blank stripping rules.
The section appears as follows:
# The following defines the blank (white space) removal rule for # reading
in values. The valid rules are:
# NONE - No stripping of blanks should take place.
# LEADING - Remove leading blanks only.
# TRAILING - Remove trailing blanks only.
# BOTH - Remove leading and trailing blanks only.
Reviewing and Editing Tag Configuration Files 49

# If not specified, "NONE" is the default.
# TRIM_BLANKS= NONE
2. Uncomment the TRIM_BLANKS line by removing the # symbol and specify the
stripping rule.
The default is NONE.

Chapter 7
Installing VSAM and IMS

Importers
♦ Overview, 52
♦ Installing Importers, 53
51
Overview
This chapter describes components that you might need to install or configure to use Data
Explorer.
You can install Data Explorer Import for VSAM and Data Explorer Import for IMS on
Windows systems. After installation, you might need to move parts of the installation to the
mainframe. For more information, see “Installing Importers” on page 53.
52 Chapter 7: Installing VSAM and IMS Importers

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 IMS
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 on
MVS or OS/390 platforms. It also includes information about system and authorization
requirements.
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 import
execution.
♦ 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 for
IMS.
Installation Overview
Data Explorer Import is distributed with the Data Explorer installer and is installed with
Data Explorer Source Profiler. The mainframe PDSs are provided as sequential files. These
sequential 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.
Installing Importers 53
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 and
RECEIVE the sequential files to create the LOADLIB and CNTL PDSs.
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 Explorer
Source Profiler User Guide.
Step 1. Preparation
This 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 the
changes you must make to the Data Explorer Import JCL template files to customize
them for your site.
2. Obtain user ID and authorization.
Obtain a TSO user ID with authority to submit jobs and create the libraries you will
need to install Data Explorer Import.
You must have the appropriate authorities, including the authority to execute programs
retrieving data from IMS databases. For more information, see “Authorization
Requirements” on page 53.
Step 2. Upload and Receive the Sequential Files

The LOADLIB.XMI and CNTL.XMI data sets must be converted and loaded into the
partitioned 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 dataset
should be allocated with RECFM=FB and LRECL=80. Populate this dataset with the key
information received from Informatica.
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.
Installing Importers 55
Setting Up Repository Reports
These reports use the repository and Crystal Reports. A Crystal Reports viewer installs with
the Data Explorer client installation.
The following process describes how to set up the repository:
1. If necessary, define ODBC.
2. Open the Repository Report.
3. Set the location
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 database
connection 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
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
Upgrading the Data

Explorer Repository
♦ Overview, 58
♦ Upgrading the Repository, 59
57
Overview
This chapter provides steps to upgrade a Data Explorer repository for use with Data
Explorer8.6.
You cannot upgrade a Data Explorer installation to Data Explorer 8.6. You must first
uninstall all Data Explorer components and re-install using the latest Data Explorer installer.
58 Chapter 8: Upgrading the Data Explorer Repository

Upgrading the Repository
If you are using a Data Explorer repository version older than version 5.0, you must first
upgrade these repositories to Data Explorer version 5.0. The upgrade scripts are named based
on the version that is being updated.
For example, when you upgrade from Data Explorer 4.2 to Data Explorer 4.3, you need to
run the upgrade_420to430.sql script. For information about the location of specific upgrade
scripts, see the Data Explorer System Administration Guide.
After you install Data Explorer:
1. Back up your database.
2. Run the appropriate upgrade script to upgrade the repository.
Running the Data Explorer Repository Upgrade Scripts

The Data Explorer installer copies SQL scripts to database-specific directories under the sql
directory of your installation. The directories provide sql upgrade scripts for Informix,
Oracle, Microsoft SQL Server, Sybase, and UDB. For example, the Windows installer creates
this directory for Oracle upgrade sql:
C:\Informatica\DataExplorer8.6\Repository\sql\ora
Each directory contains a set of upgrade files that allow you to upgrade your database schema
from older to newer Data Explorer versions.
You must run each sql script in sequence from your repository version to the 8.6 version. You
cannot skip a product version. The following lists describes the script you must run to
upgrade your repository to the 8.6 schema. Start with the database schema for your Data
Explorer repository version.
Upgrade 4.4.0 to 5.0

♦ Run dropviews.sql from the 4.4 repository setup scripts
♦ Run upgrade_440to500.sql
♦ Run views.sql from the Data Explorer installation.
Upgrade 5.0 to 8.6

♦ Run upgrade_500_to860.sql
♦ Run views.sql from the Data Explorer installation.
Contact Global Customer Support if you do not have the views.sql file.
Upgrading the Repository 59

60 Chapter 8: Upgrading the Data Explorer Repository
Appendix A
Uninstalling Data Explorer
This appendix includes the following topics:

♦ Uninstalling on Windows and UNIX, 62
61
Uninstalling on Windows and UNIX
To uninstall Data Explorer on Windows, use the Uninstall options in the Data Explorer
program group, or use the Add or Remove Programs option provided in the Windows
Control Panel.
The Data Explorer client installer may have installed Microsoft .NET framework on your
machine. Use the Add or Remove Programs option to remove Microsoft .NET framework if
necessary.
The default location for the uninstaller options on UNIX is this directory:
/opt/Informatica/DataExplorer860/uninstaller
To run the installer, log on with root privileges and run this command:
./Uninstaller
Before you uninstall Data Explorer Server, verify that you have root or administrator
privileges on the machine where the Data Explorer server is installed. Verify also that no
clients are using the server. If Data Explorer is in use, the setup script can cause active users to
lose work.
To view the details of the machine that hosts the Data Explorer server, use a Web browser to
display the Data Explorer Listener HTML pages. Enter a URL in this format:
http://server:listener_port_number/
Uninstalling and reinstalling does not corrupt or affect the contents of the Data Explorer
Repository or any saved projects. The Data Explorer install utility stops Listener services
during uninstallation. All configuration files are backed up to
/opt/InformaticaDataExplorerBackup860.
62 Appendix A: Uninstalling Data Explorer

Index
A disk space
minimum requirements 5
AIX
memory limitations 3
application servers E
configuring 38
environment variables
IDE_ELMHOST 39
C IDE_HOME 37
ide_server.ini 37
Client
system requirements 3
configuring H
application servers 38
HP-UX
UNIX Server environment variables 39
memory limitations 4
creating
key datasets 55
Crystal Reports
prerequisites 9
I
IDE_ELMHOST
environment variables 39
D IDE_HOME
environment variable 37
Data Analyzer Reports 9
ide_server.ini
Data Explorer
environment variables 37
disk space requirements 5
importer configuration files
installation on UNIX 23
UNIX 45
installation requirements 3
Windows 45
databases
installation
backing up after install 59
system requirements 3
63
installing Server
Data Explorer on UNIX 23 system requirements 3
post-installation tasks 59 SQL scripts
preparing for 54 upgrading after install 59
system requirements
Data Explorer 3
J minimum 5
JOB statement changes
determining before installation 54
T
Tag Configuration Files 47
K tag configuration files 47
tasks
key datasets
post-installation 59
creating 55
Teradata Driver Requirements 4
L U
library usage
UMI
determining before installation 54
ethernet address
License Management
for a Windows machine 29
Listener 7
generating for a UNIX machine 29
licenses
Unique Machine Identifier
obtaining
See UMI
obtaining on MVS 55
UNIX
Listener
configuring the Server 39
subnets 39
generating a UMI 29
importer configuration files 45
M required privileges 23
stopping the install script 23
memory limitations upgrade scripts
database 3 using after install 59
Metadata Importer Configuration Files 45 user ID
obtaining before installation 54
P
privileges W
required for UNIX installation 23 Windows
importer configuration files 45
R
Repository
disk space requirements 5
upgrading after install 59
S
sequential files
uploading and receiving 54
64 Index
NOTICES
This Informatica product (the “Software”) includes certain drivers (the “DataDirect Drivers”) from DataDirect Technologies, an operating company of Progress
Software 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 AND
NON-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
ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY,
MISREPRESENTATION AND OTHER TORTS.

DE 86 InstallGuide

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

DE 86 InstallGuide

Enviado por

Direitos autorais:

Formatos disponíveis

Installation Guide

Informatica® Data Explorer

Copyright © 2001-2008 Informatica Corporation. All rights reserved.

Part Number: IDE-ING-86000-0010

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

Chapter 2: Installing Data Explorer on Windows . . . . . . . . . . . . . . . . 11

Chapter 3: Installing Data Explorer on UNIX. . . . . . . . . . . . . . . . . . . . 21

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

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

Chapter 6: Reviewing Configuration Files . . . . . . . . . . . . . . . . . . . . . 41

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

Chapter 8: Upgrading the Data Explorer Repository . . . . . . . . . . . . . 57

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

Informatica Customer Portal

Informatica Web Site

Informatica Knowledge Base

Informatica Global Customer Support

Informatica Corporation Informatica Software Ltd. Informatica Business

Toll Free Toll Free Toll Free

Standard Rate Standard Rate Standard Rate

Before You Begin

This chapter includes the following topics:

2 Chapter 1: Before You Begin

Data Explorer Client

Data Explorer Server

Memory Limitations on Solaris Platforms

Memory Limitations on AIX Platforms

Memory Limitations on Windows Platforms

Databases Supported for the Data Explorer Repository

Teradata Driver Requirements

4 Chapter 1: Before You Begin

Table 1-1. Disk Space Requirements

Data Explorer Server Sun Solaris 200 MB

Additional disk space required during installation 45 MB

Data Explorer Client Windows 230 MB

Calculating Repository Disk Space Requirements

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

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

Table 1-2. Disk Space Calculation

Disk Space Requirements 5

Consider the following example:

Total Estimated Disk Space for the Repository 223 MB

6 Chapter 1: Before You Begin

Data Explorer Product Licensing 7

8 Chapter 1: Before You Begin

Data Analyzer Reports

Installing Data Explorer on

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