Table of Contents

Search

  1. Preface
  2. Backing Up and Restoring the Data Vault
  3. Configuring Centera as a Remote Data Vault Store
  4. Configuring Data Archive for a Legacy Source Using Legacy Adapters
  5. Data Archive Seamless Access for PeopleSoft
  6. Data Archive Transaction Restore API
  7. Dropping and Truncating Partitions in Data Archive
  8. How to Create Business Rules to Archive and Purge Transactional Data
  9. How to Uninstall Data Archive 5.1
  10. How to Uninstall Data Archive 5.3
  11. How to Use Scripts to Change Database User Passwords in the ILM Repository
  12. IBM DB2 Database Connectivity and Setup for Data Archive
  13. Installing Data Visualization
  14. Integrating Third-Party Schedulers in ILM Engine
  15. Parallel Processing in Data Archive
  16. Seamless Access Configuration for Siebel Applications
  17. Seamless Access Setup for Oracle E-Business Suite
  18. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  19. Using Multiple Engines in an ILM Environment
  20. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  21. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To Guide

Creating a Process Scheduler (Batch Server)

Creating a Process Scheduler (Batch Server)

To run batch jobs on the combined (production + archive) data or the archived data, you will need to create two additional process schedulers. Respectively, they will use the COMBINED and ARCHIVE tns aliases and access the data through the COMBINED and ARCHIVE schemas.
To configure a Process Scheduler, the psadmin program is used. It can be found in the
$PS_HOME/appserv
directory.
------------------------------------------------------------ Quick-configure menu -- Scheduler for Database: COMBINED ------------------------------------------------------------ Features Settings ========== ========== 1) Master Schdlr : Yes 5) DBNAME :[COMBINED] 2) App Eng Server : Yes 6) DBTYPE :[ORACLE] 7) PrcsServer :[COMBINED] 8) UserId :[VP1] 9) UserPswd :[VP1] 10) ConnectID :[people] 11) ConnectPswd:[peop1e] 12) ServerName :[] Actions 13) Log/Output Dir:[%PS_SERVDIR%\log_output] ========= 14) SQRBIN :[c:\psft\HRMS83\bin\sqr\ORA\binw] 3) Load config as shown 15) AddToPATH :[%WINDIR%;%WINDIR%\SYSTEM32] 4) Custom configuration 16) DBBIN :[C:\oracle\ora92\bin] h) Help for this menu q) Return to previous menu HINT: Enter 5 to edit DBNAME, then 3 to load Enter selection (1-16, h, or q): 5) DBNAME the name of the db alias in the tnsnames.ora. It will be checked against the PSDBOWNER and PSSTATUS tables 7) PrcsServer the unique instance name of the Process Scheduler 8) UserId a PeopleSoft user id. Either the super-administrator (PS, VP1) or PSAPPS which can only start the app server 9) UserPswd the PeopleSoft user password. The psadmin program can encrypt it. 10) ConnectId this is always "people" Notice the "l" 11) ConnectPswd this is always "peop1e” Notice the "1" 12) ServerName this is only for Sybase and Informix customers
Go to the Custom Configuration (choice 4) and provide a unique value for the field PrcsServerName. COMBINED is used in this example.
In the process monitor, you should see both process schedulers. To run a report on the combined data, you have to run the respective report on the COMBINED process scheduler. To run a report on only the archived data, you would need to create an ARCHIVE process scheduler as detailed above.
The Server name in the following screen corresponds to the PrcsServerName field above: