Informatica Data Archive for Application Retirement How to ... Library/1/0120-RetirementHowTo.pdf3....

Informatica Data Archive for Application Retirement How To Guide

© 2009 Informatica Corporation

Table of Contents

Chapter 1: Installation Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1Data Archive Server Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1Minimum Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

VMWare ESX/ESXI Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2ILM Service Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Client Machine Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Verifying Installer Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Chapter 2: Running the Application Retirement Installer . . . . . . . . . . . . . . . . . . . . . . 3Run the Data Archive for Retirement Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Installation Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3Handling Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Chapter 3: Starting the Informatica Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Logging into Data Archive for Application Retirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Chapter 4: File Archive Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Configuring File Archive Server VMimage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Configuring the File Archive Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Configuring the File Archive Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Creating Archive Area in File Archive Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Converting the VMimage for ESX/ESXi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Using external password authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

About the properties.xml file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Changing Administrator Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 5: Enabling Reporting / SQL Queries Against the File Archive . . . . . . . . . . 13Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Installing the ODBC/JDBC client Driver on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Installing ODBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Installing JDBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Installing the ODBC/JDBC under Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Chapter 6: Configuring Legacy Application Adapter . . . . . . . . . . . . . . . . . . . . . . . . . 17Creating Source Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17Configuring Maximum Number of Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17Configure Source / Destination Repository in Archive UI for Legacy Application Adapter . . . . . . .17Creating a Legacy Application Adaptor Connection in Enterprise Data Manager . . . . . . . . . . . . .17Creating a Legacy Application Adaptor Connection in a Database Query Tool . . . . . . . . . . . . . .18

Table of Contents iii

Chapter 7: Mining Source Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Logging In to Enterprise Data Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Defining Constraints for the Mined Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Auto-Creating the Retirement Archive Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Creating Additional Business Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Adding Additional Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Chapter 8: Retiring Legacy Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Running a Retirement Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Pointing Data Discovery to Required Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Adding Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Adding Webserver Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

iv Table of Contents

C H A P T E R 1

Installation Prerequisites

This chapter includes the following topics:

♦ Overview, 1♦ Data Archive Server Installation Information, 1♦ Minimum Hardware Requirements, 1♦ ILM Service Parameters, 2♦ Client Machine Settings, 2♦ Verifying Installer Files, 2

OverviewVerify the following parameters prior to running the Data Archive for Application Retirement installer.

Data Archive Server Installation InformationVerify that the following information supplied during Data Archive Server installation is available:

♦ Connection details for database where Informatica home schema is installed:− Host name and IP address− Port− SID− Database Name (Microsoft SQL server specific)− Password for built-in SYSTEM account.

♦ User name and password for Informatica Home Schema.♦ Absolute path for ILM Service.Note: The above mentioned database details are only specific to Oracle. Hence, it is suggested to configure the Data Archive server according to the intended database specific details.

Minimum Hardware Requirements♦ 32 GB Ram♦ 64 Bit 8 Core Processor♦ 30 GB Disk Space

Overview 1

VMWare ESX/ESXI RequirementsThis section discusses the minimum hardware configurations supported by

ESX Server 3i version 3.5.

You need the following hardware and system resources to use ESX Server.

♦ One or more Ethernet controllers. Supported controllers include:− Broadcom NetXtreme 570x Gigabit controllers− Intel PRO/1000 adapters

♦ A SCSI adapter, Fibre Channel adapter, or internal RAID controller.♦ 2GB RAM

ILM Service ParametersVerify that the following ILM Service parameters are set:

♦ 1 GB heap space available to the web application♦ Arial Unicode font used to generate reports and support non-Roman alphabets

Client Machine SettingsVerify that the client machine has the following application settings:

♦ Browser, such as Mozilla Firefox, Microsoft Internet Explorer, and Safari with the following configuration:− Support for executing Java scripts− Popup windows enabled

Verifying Installer FilesVerify that the following installer files are available:

♦ Command files including install.bat for Windows and install.sh for Linux♦ “lib” folder containing.jar files for setting up parameters♦ Installer file for Data Archive Enterprise Edition (with extension “.apf”)Note: The “lib” folder and install command file is usually present as a compressed file and will require extraction to the same folder where the.apf file is present.

2 Chapter 1: Installation Prerequisites

C H A P T E R 2

Running the Application Retirement Installer


♦ Run the Data Archive for Retirement Installer, 3♦ Installation Flow, 3♦ Handling Errors, 4

Run the Data Archive for Retirement InstallerInitiate installation procedure from the command prompt. Type the following command after navigating to the folder containing.apf file:

install -d5 -c -f <apf-installer-name>

Syntax for install command: install <switch-statements> <apf-installer-name>For example,install -d5 -c -f archive-51-install.apf

The following table describes the available Switch parameters:

Installation FlowThe Data Archive for Application Retirement installer extracts required files and gathers information. Click the Forward button to proceed.

1. Close all Informatica applications before starting installation of Data Archive for Application Retirement.

2. Run Data Archive for Application Retirement installer in Windows environment.

Switch Usage

-a Run the Installer in the analyse mode, which checks the target environment without installing.

-c Log installation information to the console as well as a log file.

-d{level} Set the debug level between 0 and 5.

-f{path} Specify the path of the package to be installed.

-w Specify a URL where the installation file can be found.

-h Print help with list of these switch parameters.

-l List the components in the package specified with the -f or -w option.

-p Store all information entered by the user in a file for reuse in subsequent runs. The file is stored on the Informatica Home Schema, and can contain sensitive password information.

-x Notify the installer to delete the file created by the -p option upon completion of installation.

-S Run the installer in console mode.

Run the Data Archive for Retirement Installer 3

3. Data Archive for Application Retirement- Installation Splash Screen.

4. Select JDBC driver for Database.

Choose a JDBC driver type according to database where home schema creation is intended. JDBC Type 4 drivers might be selected for one of the following database types:♦ IBM DB2♦ Oracle♦ Microsoft SQL Server

5. Specify Database connection information that stores home schema.♦ Hostname. IP address and host name of the database server.♦ SID. Unique database identifier.♦ Port. Port number used to access the database.♦ SYSTEM password: Password for accessing the SYSTEM user account.

Home schema parameters will be displayed according to the database selected.

6. Specify username and password for home schema.♦ Specify actual name and password for home schema.♦ This step assumes that the home schema was created during installation of Data Archive Server. If it is not

present, the relevant error message is displayed, and the installation stops.

7. Specify web user interface Deployment Directory.♦ Specify the folder location for the web user interface and use the Browse button to browse for a folder. ♦ The Web Application Deploy directory created during installation of Data Archive server.

8. Start Installation process.♦ The installer starts creating core tables in the home schema for all supported database platforms and installs

files for Archive Enterprise web user interface.♦ The user has an option to quit installation and reuse supplied information later. The -p option must be specified

in the install command to achieve this.

9. Installation Progress.♦ Installation progress is indicated through a progress bar, and information about the current installation step is

displayed.♦ In case the debug level was set to 5 (-d5) while executing the install command, debug information is displayed

in the command prompt running in the background.♦ In case “-c” option was supplied while running install command, installation information is also written to a log

file. In case of an error during installation, relevant information must be handed over to Informatica Global Customer Support.

10. Click Finished to complete installation.

Handling Errors If there is an error during installation, an Error Screen is displayed. In addition, the Command Prompt running in the background displays relevant information about the log file.

In such a situation, contact Informatica Global Customer Support.

The following information is required for resolving the issue:

♦ “Error details” as displayed in the Error Screen.♦ Name of the “Installation Log File” as displayed in the Command Prompt.

4 Chapter 2: Running the Application Retirement Installer

C H A P T E R 3

Starting the Informatica Web Service

The web application deploy directory specified during the installation process contains scripts for starting and stopping the ILM Service.

Batch Files for Windows♦ startApplimation.bat♦ stopApplimation.bat

Shell Scripts for Linux Variants♦ startApplimation.sh♦ stopApplimation.sh

Logging into Data Archive for Application RetirementAfter the ILM Service is started, the Data Archive for Application Retirement user interface can be accessed using the following URL format from a web browser:

http://<hostname>:<portnumber>/<WebApplicationName>

Note: <Webapplication-Name> is not required if using ILM Service.

5

6 Chapter 3: Starting the Informatica Web Service

C H A P T E R 4

File Archive Service


♦ Configuring File Archive Server VMimage, 7♦ Configuring the File Archive Server, 7♦ Creating Archive Area in File Archive Server, 10♦ Using external password authentication, 10

Configuring File Archive Server VMimageTo start using File Archive Server VMimage, it is first required to configure the File Archive Server VMimage with VMware Server.

Assumptions: VMserver is pre-installed.

To configure File Archive Server.

1. Download the file InformiaStorage.zip from the provided ftp location.

2. Run VMware server.

3. From the Commands tab, click Add Virtual Machine to Inventory.

4. Select the VMimage that was added to Inventory.

5. Start the VMimage by clicking the Power button.

6. Go to Console tab.

7. Start the VMimage.

8. At the prompt, specify the login credentials as applmgr / applmgr.

9. Specify the VMImage Networking information:

IP address. IP address of the database server.

Subnet Mask. Subnet Mask of the IP network.

Default Gateway. Default Gateway of the IP network.

DNS Details. Preferred and Alternative DNS server details.

Configuring the File Archive ServerWhen you configure File Archive Server, the procedure takes you through the following stages:

♦ Configuring the File Archive Server

Configuring File Archive Server VMimage 7

♦ Setting up the general administration user ♦ Testing the configuration ♦ Installing the system archive ♦ Starting the installed service manager Note: If you are using Informatica VMImage for File Archive Server, following steps are optional.

Configuring the File Archive Server

IP address and ports 1. The initial values to be configured are the IP address and port numbers that will be used by this implementation’s

service manger. In basic configuration mode the configuration script configures the default values for the service manager IP address and port numbers. These are:

♦ IP address: 127.0.0.1 ♦ Service manager port number: 3730 ♦ ODBC server port: 3731

Processors, memory, and JAVA_HOME directory 2. The next values to be configured are the number of processor cores, query memory limit, build memory limit, and

JAVA_HOME directory. In basic configuration mode these items are all configured with default values. These defaults are:

♦ Number of processor cores: the number of processor cores detected, minus one (unless only one core is detected). ♦ Query active process memory limit: the total detected memory divided by the number of processor cores selected. ♦ Build active process memory limit: the total detected memory divided by the number of processor cores selected. ♦ JAVA_HOME directory: the detected path for Java JDK 1.5. If no version of Java is detected, the path is set to

ArchiveStore_dist/lib/jre/bin. You will see this path listed when you are prompted to confirm the parameters. At that stage you must select to change the parameters, and then choose the advanced configuration mode so that you can enter the correct path. If no version of Java is detected, this might indicate that you do not have Java installed.

Setting up the archive layout 3. The next parameters you need to configure are the archive layout parameters. You can configure either a single

archive root directory or separate archive data, metadata, and queue directories. In either case, File Archive Server must have read/write access to the selected device and directories.

♦ If you choose to configure a single archive root directory, you specify the full path to that directory. File Archive Server will then set up separate data, metadata, and queue directories within the archive root directory. You should only select this configuration if you do not want to store your archive data on immutable storage.

♦ If you choose to configure separate data, metadata, and queue directories, you specify the full path to each of these directories. This enables you to store your archive data on immutable storage, while retaining the metadata and queue directories on mutable storage. Your metadata and queue directories must not be located on immutable storage.

To configure the archive layout you see the following prompt: Would you like to specify a single root archive directory or separate data, metadata, and queue directories? 1. single directory 2. multiple directories enter a selection:

Enter 1 to configure a single archive root directory, or 2 to configure separate data, metadata, and queue directories.

If you select a single archive root directory, you see the following prompt:

Enter the full path to the archive root directory:

8 Chapter 4: File Archive Service

Enter the path to the archive root directory. For example: /home/ArchiveStoreHome/root

If you select separate data, metadata, and queue directories, you see a series of prompts:

♦ The first prompt asks for the path to the archive data directory: Enter the full path to the archive data directory:

This is the top level directory for the archive data store. This directory is written to, but the records are never updated, so it can be on immutable storage. For example:

/home/ArchiveStoreHome/data ♦ The second prompt asks for the path to the archive metadata directory: Enter the full path to the archive metadata directory:

This is the top level directory for the archive metadata. This holds security files and high-level information about the archives. For example:

/home/ ArchiveStoreHome /metadata ♦ The third prompt asks for the path to the archive queue directory: Enter the full path to the archive queue directory:

This is the top level directory for the archive queues. This will hold task files and temporary working files. For example: /home/ ArchiveStoreHome/queue

Configuring the locale 4. The next value to be configured is the locale. This determines the formats of dates, times, and datetimes in

queries. In basic configuration mode the locale is configured with the default value, which is en_ISO.

Confirming the configured values 5. When you have configured all the values described in the preceding sections, you have the chance to confirm or

modify the settings. You see the following configuration summary (with appropriate values according to your selected configuration settings): The following settings will be used: ---- Java Home : /usr/java/jdk1.5.0_09 IP Address : 10.0.0.20 SM Port : 3737 ODBC Port : 3738 Query Memory : 10660 MB Build Memory : 10660 MB CPU cores : 3 Locale : en_ISO Archive Data Path : /home/npahome/npdata Archive Metadata Path: /home/npahome/npmetadata Archive Queue Path : /home/npahome/npqueue ---- Enter 'c' to continue with these settings, 'm' to modify the settings, or 'a' to abort:

Take one of the following actions:

♦ Enter c to confirm the displayed settings and continue with the installation. ♦ Enter m to modify the settings. If you select this option, you go back to the step where you have to select the

configuration mode (page 10). You must then complete all the configuration parameters again. If you need to change a default value that was set up using the basic configuration mode, you must now choose the advanced mode.

♦ Enter a to abandon the installation at this stage.

6. When you confirm the configuration settings and continue with the installation, you see the following messages: updating templates ... Creating <installation_directory>/FileArchiveRepository-dist/conf/ sm-config.xml Configuration complete Initializing archive layout

Configuring the File Archive Server 9

The next step in the installation process is setting up the general administration user.

Note: When you have completed the configuration steps in the installation script, your selected configuration values are stored in the service manager's configuration file. If you subsequently want to change any of the configured values, you must edit the configuration file entries.

Creating Archive Area in File Archive ServerArchive Area is a specific area on the destination repository where all the archived data will be copied to, when the selected platform is a flat file.

This section explains the procedure to create the Archive Area in File Archive Server. To create an Archive Area:

1. Browse to the ILM web container directory.Example: -../webapps/applimation/script

2. Execute Create_Archive.shSyntax: - sh.Create_Archive.sh TEST

Where “TEST” is the variable name of the Archive Area in the above syntax.

All the subsequent Data Archive job executions will copy the data.

Converting the VMimage for ESX/ESXiYou can use the free VMware vCenter Converter to import virtual machines that were created using VMware Server. VMware vCenter Converter also supports conversions from sources such as physical machines and certain 3rd party disk image formats.

Using external password authenticationTo configure your File Archive Server installation to use external password authentication, you must edit the following file:

<metadata_directory>/properties.xml

The <metadata_directory> is the directory defined as the metadata directory during File Archive Server installation and configuration.

The contents of the properties.xml file are described below. If you configure File Archive Server to use external password authentication, you must provide an authentication script. File Archive Server includes an example LDAP authentication script that you can adapt to your organization’s specific requirements.

About the properties.xml fileThe properties.xml file is a shared file that contains properties common to all service managers.

The default contents of the properties.xml file are shown below:<?xml version=1.0 encoding=UTF-8?><!DOCTYPE properties SYSTEMhttp://java.sun.com/dtd/properties.dtd><properties><entry key=authenticate_method>internal</entry></properties>


In the example, the entry authenticate_method has the value internal. This means that usernames and passwords are maintained and authenticated solely within File Archive Server. There is no external authentication.

To use external password authentication, you must change the value of the authenticate_method to external. You must also add a new authenticate_command entry. The value of this entry must be the path to an authentication script. This path must be the same for all service managers, regardless of which server they are running on.

The following script is an example of the properties.xml file configured for external authentication:<?xml version=1.0 encoding=UTF-8?><!DOCTYPE properties SYSTEMhttp://java.sun.com/dtd/properties.dtd><properties><entry key=authenticate_method>external</entry><entry key=authenticate_command>/home/npahome/ArchiveStore-dist/sbin/authenticate_command.sh</entry></properties>

The script file shown in the authenticate_command entry above is provided with the File Archive Server installation. This is an example script only. The contents are shown below.

Changing Administrator PasswordAdministrator is the super user that is created while installing File Archive Server and the default username for this user is SA.

Following is the syntax to change a user’s password. n>change_password <username>, <old_password>, <new_password>

Using external password authentication 11

C H A P T E R 5

Enabling Reporting / SQL Queries Against the File Archive


♦ Overview, 13♦ Installing the ODBC/JDBC client Driver on Windows, 13♦ Installing the ODBC/JDBC under Linux, 15

OverviewTo establish a connection to Archive Area on the File Archive Server, install ODBC/JDBC drives. The connection will be accessed through Data Discovery for all the data reporting purposes.

Installing the ODBC/JDBC client Driver on Windows

Installing ODBCFollow the instructions below to install the ODBC driver on a Windows client. To perform the installation, you will need Administrator privileges on the Windows client.

1. Unzip the ODBC zipped folder from the File Archive Server distribution medium to a suitable Windows folder on your computer.

2. Locate the setup.exe file from the unzipped folder. Either double-click the file to run the setup process, or run it from the command prompt.

3. An initial dialog box (Preparing Setup) opens briefly, and then you see the ODBC Driver v1.0.2 Setup – Welcome dialog.

4. Click the Next button to proceed with the installation.

5. The License Agreement opens. This contains the End User License Agreement (EULA).

Read the terms of the license agreement. You can use the Print button to obtain a hard copy. If you accept the Terms and Conditions, click Yes.

6. The Choose Destination Location dialog opens: ♦ To install the ODBC driver in the default location, click Next. ♦ To install the ODBC driver in a different location, click Browse, navigate to the required folder, and then click

Next.

7. The Database Configuration dialog opens. Specify Database Configuration details:

Overview 13

Name: DSN

Description: DSN connection

TCP/IP Address: 10.0.0.20

TCP/IP Port: 3731Complete the following:

When you have completed the details, click Next.

8. The License Information dialog opens. This contains the name of the license key file. This file is provided with the installer, so you can accept the license key unchanged.

When you have accepted the license key, click Next.

9. The Select Program Folder dialog opens.Either accept the suggested installation folder, or choose a different folder.

When you have selected the folder, click Next.

10. The Start Copying Files dialog opens.Check the displayed settings. If they are correct, click Next.

11. The Setup Status dialog displays a progress bar showing the progress of the file copy.

12. When the copy is complete, the InstallShield Wizard Complete dialog opens.If you want to read the ODBC driver warranty information, put a check mark in the View the ODBC Readme file check box.

Click the Finish button to complete the installation. If you selected to read the ODBC driver warranty information, the readme file opens in the default text editor. When you have read the contents, close the file.

Installing JDBCFollow the instructions below to install the JDBC driver on a Windows client. To perform the installation, Administrator privileges on the Windows client are required.

1. Unzip the JDBC folder from the File Archive Server distribution medium.

2. Locate the setup.exe file from the unzipped folder. Either double-click the file to run the setup process, or run it from the command prompt.

The JDBC Driver v1.0.2 Setup starts.

3. Click the Next button to proceed with the installation.

The License Agreement dialog opens. This contains the End User License Agreement (EULA).

4. Click Yes.

Field Description

Name Enter the name you want to use for the first DSN (Domain Name System) connection. You can subsequently create different DSNs for different archives.

Description Enter a description for the DSN to help you identify the correct connection. This is an optional item, but we recommend that you enter a suitable description.

TCP/IP Address

Enter the IP address or name of the ODBC server. You should be able to obtain this information from an File Archive Server system administrator if you are not sure what to enter. This address must match the configured ODBC hostname for the File Archive Server service manager that you want to connect to. For example: 10.0.0.20.

TCP/IP Port Enter the port number of the ODBC server. You should be able to obtain this information from an File Archive Server system administrator if you are not sure what to enter. This must match the configured ODBC port for the service manager that you want to connect to. The default value is 3731.

14 Chapter 5: Enabling Reporting / SQL Queries Against the File Archive

The Choose Destination Location dialog opens.♦ To install the JDBC driver in the default location, click Next. ♦ To install the JDBC driver in a different location, click Browse, navigate to the required folder, and then click Next.

5. The Database Configuration dialog opens. Specify Database Configuration details:

Name: JDBC

Description: JDBC connection

TCP/IP Address: 10.0.0.20

TCP/IP Port: 3731

Complete the following:

6. Click Next.

The License Information dialog opens.

7. Click Next.

The Select Program Folder dialog opens. Either accept the suggested installation folder, or choose a different folder.

8. Click Next.

The Start Copying Files dialog opens.

9. Click Next.

10. When the copy is complete, the InstallShield Wizard Complete dialog opens.

11. Click the Finish button to complete the installation.

Installing the ODBC/JDBC under LinuxFollow the instructions below to install the JDBC driver on a Linux client.

1. Copy FileArchiveRepository-Client.Linux.tar [Operating system compatible (32 bit / 64 bit)] file to the required location.

2. Un tar the file by navigating to the copied location.

Navigate to install/ilinux

3. Execute the following command to start the installation.Sh setup.sh

A message appears Do you want to continue Y/N.

4. Enter Y to continue.

Follow the on screen instructions / install license to continue the installation.

Field Description

Name Enter the name for the first DSN (Domain Name System) connection. Later, different DSNs for different archives can be created.

Description An intuitive description is suggested.

TCP/IP Address

Enter the IP address or name of the ODBC server. This address must match the configured ODBC hostname of the File Archive Server service manager. For example: 10.0.0.20.

TCP/IP Port Enter the port number of the ODBC server. This number must match the configured ODBC port number of the service manager. The default value is 3731.

Installing the ODBC/JDBC under Linux 15

5. Add user variables to point to the installed client using the following linux command.export PATH=$PATH: ../client/bin/ilinux: ../client/config/ilinux

6. Add the following values to user bash_profile to set the environment.export PATH=$PATH: ../client/bin/ilinux: ../client/config/ilinux. /home/npemc/NParchive-dist/bin/npa_env.sh. /home/npemc/npclient/config/ilinux/setenv.ksh

16 Chapter 5: Enabling Reporting / SQL Queries Against the File Archive

C H A P T E R 6

Configuring Legacy Application Adapter

Note: The following instructions are specific to i-way Adapter.

Starting Application Adapter Server

Navigate to Start > Programs >Iway Server > Start with Alternate Security modes > Start Security off

Note: Stop the Legacy Application Adapter server if it is already running.

Post successful installation / restarting of Iway Server, navigate to browser and type following URL, http://<hostname>:<http_port_provided_while_installing>/webconsole

(Or) Navigate to web console URL from Start Menu ' Programs ' Iway > web console.

Creating Source AdapterStep 1: click Configure data adapter (create connection information) in web console.

Step 2: Click Adapters and click Add, Select appropriate Database and follow steps to configure the adaptor.

Step 3: Click the created adapter and Test the configuration by clicking Test.

Note: If Test adapter is unsuccessful, Follow above procedure / provide precise credentials while configuring.

Configuring Maximum Number of ConnectionsNavigate to Workspace --> Configuration--> Listeners

Update following:

DEFAULT - 10

WC_DEFAULT - 10

DFM_DEFAULT - 10Follow above procedure to increase connections with Legacy Application Adapter server installed at source.

Configure Source / Destination Repository in Archive UI for Legacy Application Adapter

Go to Administrator > AddAarchive Data Source.

Select the appropriate platform and provide the Source connection details for Legacy Application Adapter server source.

Example:- Select Legacy Adapter for Iway as platform Or Select DD Adapter for IBM DB2 as platform.

Note: Install Extended Database Enabler patch to establish connection to legacy source database.

Creating a Legacy Application Adaptor Connection in Enterprise Data ManagerStart Enterprise Data Manager, and provide connection information to connect to Legacy Application Adapter source.

17

Connection Profile: User defined name to recognize the connection.

Database Type: Legacy Application Adapter should be utilized for all subsequent Legacy Application Adapter connections.

Database Host: Source Host

Database Port: Source Port

Database Name: EDASERVE default for all Legacy Application Adapter Source.

Username: edadb [default, if Legacy Application Adapter server is started in “OPSYS security mode off” mode]

Password: edadb

Note: Install Extended Database Enabler patch to establish connection to legacy source database.

Creating a Legacy Application Adaptor Connection in a Database Query ToolStep 1: Copy ibtrace.jar, jlink.jar, ngxxj.jar, nlslt.jar to database query tool/lib folder.

Step 2: Edit datastudio.bat and update the file with location of all jars which have been copied in lib folder.

Step 3: Copy ADS/lib absolute path in CLASSPATH (or) Edit datastudio.bat to add all jars added in step 1 to get included in classpath.

Step 4: Open datastudio.bat, register new server and provide following parameters:

Select Generic/jdbc in RDBMS section

Login Name: edadb

Password: edadb

URL: jdbc:eda://<hostname:port>;server=EDASERVE

Driver: ibi.jdbc.EdaDriver

Click Save.

18 Chapter 6: Configuring Legacy Application Adapter

C H A P T E R 7

Mining Source Database


♦ Overview, 19♦ Defining Constraints for the Mined Tables, 20♦ Auto-Creating the Retirement Archive Entity, 21♦ Creating Additional Business Entities, 23

OverviewTo create retirement archive metadata, it is required to mine the source file.

Logging In to Enterprise Data ManagerA user can login to the Enterprise Data Manager from the user interface and also from the c:\applimation\edm.bat.

To login from the user interface, click Accelerators > Enterprise Data Manager.

To mine a database:

1. Login to Enterprise Data Manager.

2. In the Explorer Pane double-click Custom Apps Only and then click Custom application.

3. Click File > Mine Database.

It is required to create a Connection Profile to the source files for the first time. Otherwise choose a previously created connection profile. Following are the steps to create a new Connection Profile:

4. Enter the following values:

1.Connection Profile = “--New Connection --”

2.Database Type = Legacy Application Adapter

3.Database Host = 10.155.243.23

4.Database Port = 8100

5.Database Name=EDASERVE

6.Username=edadb

7.Password=*********

8.Click OK.

9.Enter a name to the save the profile (e.g., SOURCE).

10.Click OK.

Overview 19

The Database Mining Wizard will open.

5. Select EDADB from the Schema list. Click the Down Arrow button. The EDADB schema will appear in the Selected field box.

6. Click Next.

7. Select the table or tables you want to mine. You can select multiple tables by holding down the CTRL key when you click a table name.

8. After the tables are selected, click the Down Arrow button. The table names will move to the selected text field box.

9. Click Finish.

A dialog box will appear:Do you want to mine child tables of these tables?

1.Click No. If the selected platform is Oracle or Microsoft SQL Server, click Yes.

2.The progress of the mining will list the tables being mined.

When the mining is complete a dialog box appears: The mined data has not been saved yet. Select File -> Save from the menu bar to save.

3.Click Ok. Close the Database Mining Progress window.

4.Click Save.

The tables should appear in the Explorer pane under Custom Apps Only > Custom Application > EDADB.

5.Click the table(s) that are added. On the Basics tab on the right side of the window select the table type from the Type drop down list. Choose either Transactional or Configurational.

6.Click Save.

Repeat this step for each table that is mined.

Defining Constraints for the Mined TablesThe first step in creating Retirement Archive metadata is to define the Primary Key and the Foreign Key relationships between the tables being retired. The Primary Key needs to be defined for the driving table and also for any table that is a parent table. Due to bugs in Enterprise Data Manager for Retirement Archive, constraints must be defined in an older version of Enterprise Data Manager (from patchset edm53_plat53_patchset1_1939).

For example:

♦ Header table is a parent to the Lines table− Define a PK for Header− Define a FK for Lines to Header

♦ Lines table is a parent to the Line Details table− Define a PK for Lines− Define a FK for Line Details to Lines

♦ Vendor Master is a parent to the Header table− Define a PK for Vendor Master− Define a FK for the Header to the Vendor Master

20 Chapter 7: Mining Source Database

To define constraints for the Mined Tables:


2. Click View > Constraints.


4. Select the table you want to define a constraint for.

5. Click the Constraints tab.

6. Click the Green Plus Sign button on the right hand side of the window, to insert a new constraint.

7. Name the constraint - e.g., FRE_PK1 - use the table name and add PK as suffix for Primary Keys and FK for Foreign Keys.

8. Select the constraint type:♦ Primary Key - for single column unique keys.♦ Unique - for multi column (or composite) unique keys.♦ Referential - for foreign key constraints which are created on the Child table.

9. Click the Enabled Check box.

10. Now add the columns for the constraint.

11. Click the Green Plus Sign button in the bottom middle part of the window, to insert a constraint column.

For Primary Keys:

12. Select Column from the Type drop down list box.

13. Select the column name that represents the PK from the Name drop down list box and click Save.

For Unique Keys:


15. Select the column name that represents the first column in the unique key from the Name drop down list box.

16. Repeat steps 11, 12, and 13 until all columns have been added and click Save.

For Referential constraints:

17. Click the Ref Table Search

18. Select the Parent Table

19. Select the Primary Key or Unique Key constraint from the Ref. Constraint drop down list box. This key must be defined previously.


21. Select the column name that represents the PK from the Name drop down list box.

22. For Unique keys, select the column name that represents the first column in the unique key. Repeat steps 11, 20, and 21 until all columns of the unique key have been added and click Save.

Auto-Creating the Retirement Archive EntityTo create a retirement object:



3. Select the parent table that you want to auto-create a Retirement Archive entity for.

Auto-Creating the Retirement Archive Entity 21

4. Right-click the entity and select “Create Archive Entity.”

The Entity Creation Wizard will open.

5. For “Include Child Tables” select “Yes - Within Module.”

6. Click the Down Arrow button. “Yes - Within Module” will move to the Selected field box. Click Next.

7. For “Table Types” select Transactional.

8. Click the Down Arrow button. “Transactional” will move to the Selected field box. Click Finish.

9. Possible messages generated by Auto Create:♦ If there are no child tables for table, then a message box will appear “There are no child tables to be added for

- < selected table name>”. If this message box appears then click OK.♦ The archive and delete metadata may not be able to be auto-generated. A message box will appear - “Parent

Table does not have WHERE clause. Unable to generate WHERE clause for child tables, do you want to Continue?” Click Yes.

♦ When the entity is created, a message box appears “Entity <entity name> created”. Click OK.

10. Click the Save button in the Toolbar.

11. Click the Online Archive tab in the Explorer pane (bottom left corner).

12. The newly created entity appears under Custom Only Apps -> Custom Application.

To associate additional tables with the created entity:− Navigate to the entity created earlier in the Online Archive tab.− Right-click the entity and click “Insert where 1=1”, to select all the data from tables, which has “Insert where 1=1”

configured.− Select the interim and then select tables to associate additional tables with the entity.

The auto-creation process does not create the entity completely. There are still steps to be performed to complete the entity. These steps include:♦ Modifying/Adding the Insert statement and Delete statement clauses for each table:

Since we want to archive all rows in all tables, we will enter 1=1 to ensure we select all rows from each table.♦ Modifying the Interim table for Candidate Generation:

Remember the Interim is used for Candidate Generation which identifies the rows to be archived. Since we are retiring all rows, the Candidate Generation job is not important. Therefore, the completion of the interim table is simple (and the below steps are not applicable to a situation where we are selectively retiring data).♦ Modifying the Entity Steps to be performed:

The interim tables are usually dropped and created as part of the Candidate Generation job. But since we are integrating with Legacy Application Adapter to access the source files, the interim table must be manually created in the Staging schema (which is defined in the UI). It must also have an Legacy Application Adapter synonym created in the Legacy Application Adapter Windows client and the Legacy Application Adapter Sun client. These steps are specified later in this document.♦ Adding reference tables to the entity.

13. In the Explorer pane click the Online Archive tab (or select View -> Online Archive from the Menu bar).

14. Expand the newly created Entity under Custom Apps Only > Custom Application. You should see the interim table (in Italics) and the parent table and all of its children.

15. Click the interim table and click the Tables tab.

All the parent table and its child tables are listed.

16. Click the Insert statement field for the first table.

17. A window pops up with the Insert Statement and Delete Statement and Update Statement fields.

18. Enter 1=1 in the Insert Statement and Delete Statement fields. Click OK.


19. Click Save and repeat steps 15-19 for each table.

20. Click the Interims tab.

21. Select the STATS_DATE and ORG_ID columns. Press the Red X (Delete) button. The only row remaining should be the PURGEABLE_FLAG column.

22. Click in the “Where clause” field. Enter 1=2 in this field and Click Save.

23. In the Explorer pane select the Entity Name (e.g., EM1_1).

24. Click the Steps tab and Uncheck the Enabled check box for the following Actions:

25. Drop Interim Table.

26. Create Interim Table and click Save.

27. In the Explorer pane click the File Archive tab (or select View -> File Archive from the Menu bar).

28. Select the entity name.

29. Right-click the entity name and select Import Constraints from the menu.

30. The Import Constraints wizard opens.

31. Uncheck the “Show constraints within the entity” checkbox.

32. Select all of the appropriate constraints from the Referring Constraints list. These constraints must have been pre-created - these steps were outlined in “Defining Constraints for the Mined Tables” section. Only select the constraints for the non-transactional tables.

33. Click the Down arrow button. All of the selected constraints will move down to the “Selected” field box. Click Finish.

34. Click Save and Click the Ref Tables tab.

35. The selected constraints will now appear in the list.The entity is now ready for the retirement cycle.

Creating Additional Business Entities1. Login to Enterprise Data Manager.

2. In the Explorer Pane double-click Custom Apps Only and then click the Custom application.

3. Right-click Custom Application and click Add Application.

The Entity Creation Wizard will open.

4. Provide Application name and click Next.

5. Provide Entity name and click Next to generate default Interim and click Finish.

6. Right-click entity and click Insert Table.

The Add Table Wizard will open.

7. Select schema to select table.

8. Select the required Interim and click Default Columns tab.

9. Specify Primary key, From Clause, and Where Clause details of the table created above.

10. Click the Tables tab.

11. Click the created table and specify Insert and Delete statements and click Save.

Creating Additional Business Entities 23

Adding Additional TablesIf it is required to add additional tables to the entity perform the following steps.

1. Right-click the entity and click “Insert where 1=1”, to select all the data from tables, which has “Insert where 1=1” configured.

2. Select the interim and then select tables to associate additional tables with the entity and click Save.The entity is now ready for the retirement cycle.


C H A P T E R 8

Retiring Legacy Applications


♦ Running a Retirement Cycle, 25♦ Pointing Data Discovery to Required Entity, 25

Running a Retirement CycleFollowing are the steps that need to be performed to run a Retirement cycle.

1. Login to Web UI.

2. Navigate to Workbench -> Retirement Workbench.

3. Enter the Application Name you are retiring.

4. Enter the Retirement Date (just select the current date).

5. Select the Custom application from the Product Family Version.

6. Select MillenniumProd-Source from the Source drop down list of values.

7. Select MillenniumProd-Destination from the Destination drop down list of values.

8. Click Next.

9. Click the Add Retirement Object button.

10. Select your Entity and click Next.

11. Specify your Policy details and click Next or skip this step.

12. Specify details for Approved by and Approved date fields and click Next.

13. Click Schedule to schedule the Retirement job.

Pointing Data Discovery to Required EntityThe procedure of pointing Data Discovery to the required entity is divided into two sections:

1. Adding Constraints to required entity.

2. Adding webserver parameters to conf.properties.

Running a Retirement Cycle 25

Adding Constraints

To add Constraints to the required entity:

1. Start Enterprise Data Manager.

2. In the Explorer pane click the File Archive tab (or select View -> File Archive from the Menu bar).

3. Select the entity created.

4. Right-click the entity name and select Import Constraints from the menu.

Create Constraints if additional constraints are required.

5. The Import Constraints wizard opens.

6. Uncheck the Show constraints within the entity checkbox.

7. Select all of the appropriate constraints from the Referring Constraints list. These constraints must have been pre-created - these steps were outlined in Defining Constraints for the Mined Tables section. Only select the constraints for the non-transactional tables.

8. Click the Down arrow button. All of the selected constraints will move down to the Selected field box. Click Finish.

9. Click Save

10. Click the Ref Tables tab.

11. The selected constraints will now appear in the list.

Adding Webserver ParametersNavigate to webcontainer and edit conf.properties to add the following parameters.

informia.dataDiscoveryMetadataQuery=AMHOME

26 Chapter 8: Retiring Legacy Applications

Informatica Data Archive for Application Retirement How to ... Library/1/0120-RetirementHowTo.pdf3....

Documents

Transcript of Informatica Data Archive for Application Retirement How to ... Library/1/0120-RetirementHowTo.pdf3....