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

Appendix B

Issue:

Change user's access rights to "Read Only" for all Pages they currently have access to in Production. This solution assumes that users will not be doing any kind of security or account maintenance in the Seamless Access environment.

Solution:

This is controlled by the DISPLAYONLY flag in the PSAUTHITEM table. A value of "1" means the page is display only. A value of "0" states the page is updateable. We modified the view of PSAUTHITEM table to add select statement to return pages that are flagged as display only.

Issue:

Enable user's access to in-page buttons so users can perform drilldown to detail information (i.e. PO Inquiry)

Solution:

The PO Inquiry page by definition is a display only page. To allow the user the ability to click on buttons on the page it must not be set as display only. The view PSAUTHITEM will not set this page to display only.

Future Inquiry Pages:

For future pages that are by nature inquiry only, the DISPLAYONLY flag in the PSAUTHITEM view should be set to 0 for these pages. A value of "0" states the page is updateable. The item should be added to the 1^st and 2^nd select statement in the PSAUTHITEM view as noted below where "PO_INQUIRY" is located.

CREATE OR REPLACE VIEW &&DATAACCESSSID..PSAUTHITEM (CLASSID, MENUNAME, BARNAME, BARITEMNAME, PNLITEMNAME, DISPLAYONLY, AUTHORIZEDACTIONS) AS

select 
    a1.CLASSID,
    a1.MENUNAME,
    a1.BARNAME,
    a1.BARITEMNAME,
    a1.PNLITEMNAME,
    1 DISPLAYONLY,
    a1.AUTHORIZEDACTIONS 
   from &&ACCESSID..PSAUTHITEM a1
   WHERE a1.BARITEMNAME NOT IN ('PROCESSMONITOR','QUERY_MANAGER',
   'PO_INQUIRY')               -- This Allows the user to click on buttons in PO Inquiry
   and a1.BARNAME NOT IN ('REPORT')
union
select 
    a2.CLASSID,
    a2.MENUNAME,
    a2.BARNAME,
    a2.BARITEMNAME,
    a2.PNLITEMNAME,
    0 DISPLAYONLY,
    a2.AUTHORIZEDACTIONS 
   from &&ACCESSID..PSAUTHITEM a2
   WHERE a2.BARITEMNAME IN ('PROCESSMONITOR','QUERY_MANAGER',
      'PO_INQUIRY')        -- This Allows the user to click on buttons in PO Inquiry
   and a2.BARNAME NOT IN ('REPORT')

Issue:

Don't allow the user the ability to revise nVision parameters (Scope, Report Requests).

Solution:

nVision pages access rights are set to "Read Only" with the resolution for issue 1.

Report layouts are not controlled via the 3 tier environment. There is no programmatic way to remove the user's ability to create or modify report layouts. They are controlled via 2 tier installation of nVision.

Issue:

Have a way to turn on/off the user's ability to run a query to HTML.

Solution:

This is controlled by the flag QRY_OUT_LISTBOX in the table PS_SCRTY_QUERY. We added a new view (PS_SCRTY_QUERY) based off this table. A value of "N" will prevent the user from being able to run a query to HTML. A value of "Y" will give the user the ability to run to HTML.

Issue:

Have a way to turn on/off the user's ability to run a query to Excel.

Solution:

This is controlled by the flag QRY_OUT_NVISION in the table PS_SCRTY_QUERY. We added a new view (PS_SCRTY_QUERY) based off this table. A value of "N" will prevent the user from being able to run a query to Excel. A value of "Y" will give the user the ability to run to Excel.

Issue:

Remove user's ability to create/edit Public or Private Queries. Users will still be able to run all queries that they have access to in Production.

Solution:

This is controlled by the flag QRY_RUN_ONLY in the table PS_SCRTY_QUERY. We added a new view (PS_SCRTY_QUERY) based off this table. A value of "Y" will prevent the user from being able to edit or create queries. A value of "N" will give the user the ability to create/edit queries.

Issue:

Have a way to turn on/off user's ability to Schedule a query (thru the Process Scheduler)

Solution:

There is no way without a customization to the page to remove the "Schedule Query" Link on the query page. To prevent them from scheduling a query we are setting the field AUTHORIZEDACTIONS in the 3^rd sql for the PSAUTHITEM to 0. The users will receive a security error saying they are not authorized to access this component which prevents them from scheduling queries.

Rename Saved Search

Table of Contents

Data Archive How-To Guide

Data Archive How-To Guide

Appendix B

Appendix B