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

Data Vault Service Agent Configuration

Data Vault Service Agent Configuration

After you update the configuration files for the Data Vault Service, update the
ssa.ini
configuration file for the Data Vault Service agent.
You must update the QUERY, SERVER, and STARTER sections of the
ssa.ini
file. Before you start the configuration, verify that the Data Vault Service agent is shut down. Back up the
ssa.ini
file before you modify it.
  1. Use a text editor to open the
    ssa.ini
    file located in the root of the Data Vault Service agent directory.
  2. Find the section labeled [QUERY].
    The SHAREDIR parameter in the QUERY section stores the location of the shared run-time files.
    The following text shows an example of the QUERY section in the
    ssa.ini
    file:
    [QUERY] THREADS=2 MAXVMEM=4096 MEMORY=512 TEMPDIR=C:\Informatica\DataArchive\FAS\temp SHAREDIR=C:\Informatica\DataArchive\FAS\temp
  3. Update the location of the shared run-time files in the SHAREDIR parameter.
    Set the value of the SHAREDIR parameter to the directory that you created in shared storage. For example, update the value of the SHAREDIR parameter with the
    <SANRootDirectory>/FAS_Shared
    directory you created in the shared storage area.
  4. Find the section labeled [SERVER].
    The HOST parameter in the SERVER section stores the host name of the server that hosts the Data Vault Service. The EXEPORT parameter stores the administration port for the Data Vault Service.
    The following text shows an example of the SERVER section in the
    ssa.ini
    file
    [SERVER] THREADS=10 HOST=calvin EXEPORT=8600 PORT=8500 ROWSETBUFFER=64 TEMPDIR=C:\Informatica\DataArchive\FAS\temp LOGDIR=C:\Informatica\DataArchive\FAS\fas_logs
  5. Update the HOST parameter with the host name of the primary server.
  6. Update the port number in the EXEPORT parameter with the administration port number set in the primary server.
    The default administration port is 8600.
  7. Find the section labeled [STARTER].
    The AGENT_COUNT parameter stores the number of agent processes to run for query processing on the failover server.
    The following text shows an example of the SERVER section in the
    ssa.ini
    file
    [STARTER] AGENT_CONTROL=1 AGENT_COUNT=2 VERBOSE=2 SERVER_CONTROL=1 AGENT_CMD=ssaagent SERVER_CMD=ssaserver LOGDIR=C:\Informatica\DataArchive\FAS\fas_logs
  8. Update the AGENT_COUNT parameter with the number of agent processes you want to start for processing queries.
    The default number of agents is 2. If you want to start more agents in the failover server to process queries, set the AGENT_COUNT parameter to a higher number. Or you can set the number of agents based on the number of CPUs in the server.
  9. Save the
    ssa.ini
    file.