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. High Availability Configuration for the Data Archive and File Archive Service Versions 6.1 to 6.3
  9. 0955-High Availability Configuration for the Data Vault Version 6.4 and Later
  10. How to Create Business Rules to Archive and Purge Transactional Data
  11. How to Uninstall Data Archive 5.1
  12. How to Uninstall Data Archive 5.3
  13. How to Use Scripts to Change Database User Passwords in the ILM Repository
  14. IBM DB2 Database Connectivity and Setup for Data Archive
  15. Installing Data Visualization
  16. Integrating Third-Party Schedulers in ILM Engine
  17. Parallel Processing in Data Archive
  18. Seamless Access Configuration for Siebel Applications
  19. Seamless Access Setup for Oracle E-Business Suite
  20. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  21. Using Multiple Engines in an ILM Environment
  22. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  23. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To Guide

Creating an Application Server Domain

Creating an Application Server Domain

Create two additional application server domains: one for the combined access schema and one for the archive only schema.
To configure an application server domain, the psadmin program is used. It can be found in the following directory:
$PS_HOME/appserv
---------------------------------------------- Quick-configure menu -- domain: COMBINED ---------------------------------------------- Features Settings ========== ========== 1) Pub/Sub Servers : Yes 15) DBNAME :[COMBINED] 2) Quick Server : No 16) DBTYPE :[ORACLE] 3) Query Servers : No 17) UserId :[VP1] 4) Jolt : Yes 18) UserPswd :[VP1] 5) Jolt Relay : No 19) DomainID :[COMBINED] 6) WSL : No 20) AddToPATH :[c:\oracle\ora92\bin] 7) PC Debugger : No 21) ConnectID :[people] 8) Event Notification: No 22) ConnectPswd:[peop1e] 9) MCF Servers : No 23) ServerName :[] 10) Perf Collator : No 24) WSL Port :[7010] 11) Analytic Servers : No 25) JSL Port :[9010] 12) Domains Gateway : No 26) JRAD Port :[9100] Actions ========= 13) Load config as shown 14) Custom configuration h) Help for this menu q) Return to previous menu HINT: Enter 15 to edit DBNAME, then 13 to load Enter selection (1-26, h, or q): The only fields that need particular attention are: 15) DBNAME the name of the db alias in the tnsnames.ora file. It will be checked against the PSDBOWNER and PSSTATUS tables 17) UserId a PeopleSoft user id. Either the super-administrator (PS, VP1) or PSAPPS which can only start the app server 18) UserPswd the PeopleSoft user password. The psadmin program can encrypt it. 19) DomainID a label used internally by Tuxedo. There is no reason why it should differ from DBNAME 21) ConnectId this is always "people" Notice the "l" 22) ConnectPswd this is always "peop1e” Notice the "1" 23) ServerName this is only for Sybase and Informix customers
You will need to create an application server domain for the ARCHIVE schema in the same fashion.

0 COMMENTS

We’d like to hear from you!