Preface
Backing Up and Restoring the Data Vault
- Overview
  - Backup and Restore Guidelines
- Offline Backup and Restore
- Online Backup and Restore
Configuring Centera as a Remote Data Vault Store
- Overview
- Step 1. Install the XAM Libraries
- Step 2. Set Up the Target Connection
- Step 3. Run the Create Archive Folder Job
- Step 4. Add the XAM Connection to the SSA.ini File
- Step 5. Validate the Connection to Centera
Configuring Data Archive for a Legacy Source Using Legacy Adapters
- Abstract
- Configuring Data Archive for a Legacy Source Using Legacy Adapters
Data Archive Seamless Access for PeopleSoft
- Abstract
- Overview
- Prerequisites
  - System Privileges
  - Object Privileges
- Data Archive Seamless Data Access Job
- Modifying the tnsnames.ora
- PeopleSoft Seamless Access Script
- Creating an Application Server Domain
- Creating a Process Scheduler (Batch Server)
- Process Scheduler Setup
- Creating a PeopleSoft PIA
  - Adding Multiple Sites to a Single WebLogic Domain
- Appendix A
  - Script Changes
- Appendix B
Data Archive Transaction Restore API
- Abstract
- Overview
  - List of Terms
- Solution Overview
  - Features
- Calling the Transaction Restore API
Dropping and Truncating Partitions in Data Archive
- Abstract
- Overview
- When to Drop and Truncate Partitions
- Entity Configuration
- How to Configure an Entity to Truncate or Drop Partitions
- How to Choose Partitions
- How to Drop or Truncate Partitions from Multiple Tables
- How to Drop and Truncate Partitions from Multiple Tables within the Same Entity
  - Interim One - Drop Partitions
  - Interim Two - Truncate Partitions
- Log Messages
  - Normal Completion
  - Exception Handling
High Availability Configuration for the Data Archive and File Archive Service Versions 6.1 to 6.3
- Overview
- High Availability Configuration
  - High Availability Configuration for the ILM Repository
- High Availability Requirements
- Primary Server Installation and Configuration
  - Set the Location of the Data Vault Repository File
  - Set the Location of the Shared Run-Time Files
- Failover Server Installation and Configuration
  - Data Vault Service Configuration
    - Set the Location of the Data Vault Repository File
    - Set the Location of the Shared Run-Time Files
  - Data Vault Service Agent Configuration
- Operation
  - Load Management
    - Guidelines for Setting the Agent Priority Level
  - Failover Management
    - Restoring Primary Server Operation
    - Guidelines for Server Operation
- Troubleshooting
0955-High Availability Configuration for the Data Vault Version 6.4 and Later
- Overview
- High Availability Configuration
  - High Availability Configuration for the ILM Repository
- High Availability Requirements
- Primary Server Installation and Configuration
  - Set the Location of the Data Vault Repository File
  - Set the Location of the Shared Run-Time Files
- Failover Server Installation and Configuration
  - Data Vault Service Configuration
    - Set the Location of the Data Vault Repository File
    - Set the Location of the Shared Run-Time Files
  - Data Vault Service Agent Configuration
- Operation
  - Load Management
    - Guidelines for Setting the Agent Priority Level
  - Failover Management
    - Restoring Primary Server Operation
    - Guidelines for Server Operation
- Restoring Data Visualization Report Functionality
  - Updating the JDBC URL or Password for Non-Healthcare Reports
  - Updating the JDBC URL or Password for Healthcare Reports
- Troubleshooting
How to Create Business Rules to Archive and Purge Transactional Data
- Abstract
- Overview
- Candidate Generation Process
How to Uninstall Data Archive 5.1
- Abstract
- Overview
- Step 1. Delete the History Instance
- Step 2. Delete the Applimation Agent
- Step 3. Delete the Source Instance
- Step 4. Delete the Agent Schema
- Step 5. Create and Run the drop_data_access.sql Script
- Step 6. Delete the Applimation Application
- Step 7. Drop the amhome Schema and Tablespace
How to Uninstall Data Archive 5.3
- Abstract
- How to Uninstall Data Archive 5.3
How to Use Scripts to Change Database User Passwords in the ILM Repository
- Abstract
- Overview
- Properties File
- Changing Database User Passwords
IBM DB2 Database Connectivity and Setup for Data Archive
- Abstract
- Overview
- Step 1. Set Up IBM DB2 Privileges
- Step 2. Bind the Packages on IBM DB2
- Step 3. Mine the Source Database and Create Entities
  - IBM DB2 Connection Properties
  - Mining the Database
- Step 4. Create a Source Connection
- Step 5. Create a Target Connection
- Step 6. Create an Archive Project
- Known Limitations
Installing Data Visualization
- Installing Data Visualization Overview
- Before You Install
- Installing Data Visualization
Integrating Third-Party Schedulers in ILM Engine
- Abstract
- Overview
- Integrating a Third-Party Scheduler
  - Replacing the Quartz Scheduler
- Using the Third-Party Scheduler API
- Integrating External Schedulers
Parallel Processing in Data Archive
- Abstract
- Introduction
- Metadata Tuning
- Performance-Related Source Repository Attributes
- Archive Definition Setup
- Restore Definition Setup
- Java Parallelism - Processing Multiple Tables Simultaneously
- Database Link Setup for Restore Cycles
Seamless Access Configuration for Siebel Applications
- Abstract
- Objective
- Dedicated Client Mode
- Web Client Mode
Seamless Access Setup for Oracle E-Business Suite
- Abstract
- Overview
- Setting Up Seamless Access Between Informatica Data Archive and Oracle E-Business Suite
- Appendix
  - Sample Script for Archive Only Schema
  - Sample Script for Combined Schema
Using the Data Vault Service JDBC Driver to Connect to the Data Vault
- Data Vault Service JDBC Driver Overview
- JDBC Driver Requirements
- JDBC Driver Installation
- ODBC Data Source for the Data Vault
- Connecting to the Data Vault
Using Multiple Engines in an ILM Environment
- Abstract
- Challenge
- Description
- Workflow Best Practices
- Keeping Track of Tomcat Engines
- Keeping the ./webapp/file_archive Directories Synchronized
- Keeping the ./webapp/xsl Directories Synchronized
Using PowerExchange ODBC Connections in a Data Archive Retirement Project
- Abstract
- Overview
- Implementation Scenario
- Task Flow
- Step 1: Install and Configure PowerExchange on z/OS
- Step 2: Install and Configure PowerExchange on the Data Archive Server
- Step 3: Install and Configure PowerExchange on the Validation Server
- Step 4: Install and Configure PowerExchange on Windows
  - Install PowerExchange on Windows
  - Edit the DBMOVER Configuration File on the Windows System
- Step 5: Create PowerExchange Data Maps
- Step 6: Configure PowerExchange ODBC Data Sources on the Data Archive Server
  - Configure ODBC Data Sources on Linux or UNIX
  - Configure ODBC Data Sources on Windows
- Step 7: Configure PowerExchange ODBC Data Sources on the Validation Server
- Step 8: Import z/OS Metadata
- Step 9: Define and Run the Retirement Project
  - Define the Retirement Archive Project
  - Run the Retirement Project
- Step 10: Validate the Retired Data
Discovering Foreign Key Relationships in Enterprise Data Manager
- Overview
- Airline Ticket Example
- Step 1. Configure Profile and Discovery Parameters
- Step 2. Start Enterprise Data Manager
- Step 3. Import Metadata from the Database
- Step 4. Discover Table Relationships
- Step 5. Define Foreign Keys

Data Archive How-To Guide

6.4.4
- 6.5.1
- 6.5 HotFix 1
- 6.5
- 6.4.3 HotFix 1
- 6.4.3

Back Next

Step 4. Discover Table Relationships

Define the type of profiling that you want to implement in Enterprise Data Manager.

When the import metadata job is complete, select

View

Refresh

and expand the entity tree in the

View

Constraints

view of Enterprise Data Manager.

The following image shows the entity tree hierarchy:

The Custom Apps Only application contains a Custom Product Family Version application version, an AIRLINE_LOYALTY schema, and TICKET tables.

Right-click the schema that you want to run the profile on, and select

Discover Keys and Relationships

. For example, right-click the AIRLINE_LOYALTY schema.

The

Metadata Import Wizard

opens.

In the

Metadata Import Wizard

, select

Discovery and Profiling with Informatica Data Quality

and

Discover Table Relationships

The following image shows the

Metadata Import Wizard

with the correct parameters selected:

Click

In the Connection Name field, select the connection that you defined in Step 3. Optionally, you can define a new connection.

If you choose to define a new connection, enter the following parameters:

Database Type: The type of database that you want to connect to.
Host: The name of the machine that hosts the source data.
Port: The port number that the source database uses.
Database Name / SID: Unique identifier or system identifier for the source database server.
Source Connection String: Connect string that determines how the database native client connects to the database. The Data Integration Service uses the connect string to create a connection object to the source database.
The following table describes the service name for each source database:

Source Database
Description
Connect String Syntax

IBM DB2
Database alias name of the remote database configured from the IBM DB2 Connect client.
dbname

Microsoft SQL Server
Name of the host of the Microsoft SQL Server database.
servername@dbname

Oracle
Full service name or SID for the Oracle database. The TNS name that is configured from the ILM application server to the database server. The name is defined in the application server
TNSNAMES.ORA
file.
dbname.world

Data Vault
The ODBC data source name created on the machine hosting Informatica Data Quality.
dsn
User Name: The name of the user that connects to the source database. The user is the owner of the schema that you want to run the profile on. The user must own the tables that you want to run the profile on and must have privileges to select table catalogs.
For Oracle and IBM DB2, the user name is the same as the schema name.
Password: The password for the database user name.

Source Database	Description	Connect String Syntax
IBM DB2	Database alias name of the remote database configured from the IBM DB2 Connect client.	dbname
Microsoft SQL Server	Name of the host of the Microsoft SQL Server database.	servername@dbname
Oracle	Full service name or SID for the Oracle database. The TNS name that is configured from the ILM application server to the database server. The name is defined in the application server TNSNAMES.ORA file.	dbname.world
Data Vault	The ODBC data source name created on the machine hosting Informatica Data Quality.	dsn

Optionally, you can click

Advanced Options

to define the following parameters:

Data Types Used in Comparison: Determines whether the profile uses data dictionary data types or generic data types.
Choose one of the following options:
Inferred Data Types. Select to use generic data types.
Metadata. Select to use data dictionary data types.
Comparison Case Sensitivity: Determines whether profiling takes into account case differences.
Choose one of the following options:
Case Sensitive. Select to run case sensitive profiling. The Case Sensitive option can affect job performance.
Not Case Sensitive. Select to ignore case differences.
Trim Spaces before Comparison: Determines whether the Data Integration Service includes leading or trailing spaces in column data.
Maximum Foreign Keys Returned: The maximum number of inferred columns that the Data Integration Service returns.
Minimum Confidence Percent: The minimum percentage of key violations that the profile permits for foreign key discovery. For example, if you enter 90, the profile returns foreign keys that have more than 90% accuracy.
Regenerate Signature: Reloads column signatures if the source data changes.

The following images shows the advanced parameters:

The advanced parameters are Datatypes Used in Comparison, Comparison Case Sensitivty, Trim Spaces Before Comparison, Maximum Foreign Keys Returned, Minimum Confidence Percent, and Regenerate Signature.

Click

Save

to exit the

Advanced Options

window.

Click

in the

Metadata Import Wizard

Select the tables that you want to include in the profiling job. You can double-click a table to move it to the Selected box or you can highlight tables and click the down arrow.

The following image shows the Metadata Import Wizard with the tables that contain ticket information selected: