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
Seamless Access Setup for Oracle R12 in Data Archive
- Abstract
- Apply Oracle Patch 9015132 "ENABLING INVOKERS PROCESSING IN R12"
- Configure the Seamless Access Users and Responsibilities
- Release 12 Applications Tier Configuration for Informatica ILM Seamless Access
  - Example: AMQUERY GL Administrator Responsibility
- References
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.5
- 6.5.1
- 6.5 HotFix 1
- 6.4.4
- 6.4.3 HotFix 1
- 6.4.3

Back Next

Step 3. Import Metadata from the Database

To import table metadata, define a connection to the database in Enterprise Data Manager.

In Enterprise Data Manager, select

View

Constraints

The constraints entity tree appears.

The entity tree is organized in a hierarchy. The folder icon represents an application. In the tree, applications contain application versions, schemas, and tables. The following image shows the constraints entity tree:

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

To expand the entity tree, double-click an application.

Application versions are directly below the applications in the entity tree. Select an application version and click

File

Import Metadata from Database

The

Connect to Import Metadata from Database

window opens.

The following image shows the connection parameters:

In the

Connect to Import Metadata from Database

window, you can use the Connection Name parameter to select a connection that you previously defined, or you can create a connection. Configure the following parameters to create a connection:

Database Type: The type of database that you want to connect to.
Database Host: The name of the machine that hosts the source data.
Database Port: The port number that the source database uses.
Service Name: Unique identifier or system identifier for the source database server.
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 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.

Click

The

Import Metadata from Database Wizard

opens.

Select the schemas that you want to import metadata from. Double-click a schema to move it to the

Selected

box.

Click

Choose one of the following options:

Submit Import Metadata as a Background Job

. Runs the job in the background. If you run the job in the background, you can continue to perform other tasks. Run the job in the background if you have a large volume of metadata to import and to avoid memory errors.

You must run the job in the background to import metadata from SAP applications.

Continue Import Metadata through EDM

. Runs the job in the foreground. If you run the job in the foreground, you must wait until the job completes to perform another task. Additionally, if you run the job in the foreground and you have a large volume of metadata to import, you might receive memory errors. You might want to run the job in the foreground if you have a low volume of metadata to import.

Click

Select

Update Metadata for Existing Tables

Click

Finish

A message window appears that confirms that the job was successfully submitted.

Click

to close the message window.

To view the status of the job, select

Jobs

Monitor Jobs

in Data Archive. When the job is complete, the job status is Completed.