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

Keeping Track of Tomcat Engines

Keep track of which instance runs each job, in case you later need to view the logs or to troubleshoot or resume a job.

To keep track of the instances, follow these best practices:

In ILM 5.3.3 and previous versions, incorporate the instance in the project name to associate the job with the instance. For example, use a project name such as AR_ACME_PROD1 where PROD1 is the instance that the job is running on.

Effective in ILM 5.3.4, use the informia.appendHostAndPortInLog parameter in the conf.properties file to identify the host name and port number of the instance where the job is running. Edit the conf.properties file for each instance and set the parameter to informia.appendHostAndPortInLog=Y. ILM appends the host name and port number to the timestamps in the logs. The configuration applies to all Data Archive, Data Masking, and Data Subset jobs and all standalone jobs.

To see which instance has the least load for a new job, go to each instance and check the Thread Queue Manager. The queue manager can be found at http://URL:port/jsp/tqm.jsp. This page shows you how many threads are running and pending for each instance. You can pick the least active instance to begin the new job.

The following is an example of the tqm.jsp output:

Thread Status
ThreadId=86 ThreadName=SCHEDULEJOB$86$174_WYETHIDR_IDR_201011 174_WYETHIDR_IDR_201011 Status=Running GroupId=SCHEDULEJOB$86 ParentIds=null
Priority=1
ThreadId=148 ThreadName=JOBSTEP$148$Copy To Destination Status=Running GroupId=JOB$86 ParentIds=null Priority=0
ThreadId=33906 ThreadName=33$RES_FACT$FLAT_FILE Status=Running GroupId=STEP$148 ParentIds=null Priority=1
ThreadId=33914 ThreadName=33$SAMP_BRIDGE$FLAT_FILE Status=Running
GroupId=STEP$148 ParentIds=null Priority=1

Each thread that has "status=Running" will count against the total thread count allocated through the amMaxServerThreads parameter. For example, if you have the parameter set to 30, then, for this instance, 27 threads are left for other processes.

The best instance to start a new job is one where the tqm.jsp returns the following status:

Thread Status
No threads in queue

Effective in ILM 5.3.4, if you set informia.appendHostAndPortInLog parameter=Y to append the host name and port number to the logs, the job logs in View Current Jobs indicate what instance a job is running on. Using this information, you can open the job log for any process in a running state to see which engine has the heaviest load and which one has the lightest load.

Rename Saved Search

Table of Contents

Data Archive How-To Guide

Data Archive How-To Guide

Keeping Track of Tomcat Engines

Keeping Track of Tomcat Engines