Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Before You Install
  4. Data Archive Installation
  5. Data Vault Installation
  6. Application Accelerator Installation
  7. Application Retirement for Healthcare Accelerator Installation
  8. MongoDB Accelerator Installation
  9. Salesforce Accelerator Installation
  10. After You Install
  11. Data Archive Upgrade
  12. Data Vault Upgrade
  13. Upgrading Oracle History Data
  14. Upgrading PeopleSoft History Data
  15. ILM Data Validation Option Setup
  16. Data Archive Source and Target Database Requirements
  17. Data Archive Connectivity
  18. Data Archive Uninstallation
  19. SAP Application Retirement
  20. Database Users and Privileges
  21. Data Visualization Designer Installation
  22. Data Archive Installation Requirements Checklist and Architecture Options

Installation and Upgrade Guide

Installation and Upgrade Guide

Starting the Data Vault Agent

Starting the Data Vault Agent

You can start each Data Vault Agent separately. The Data Vault Service must be running when the agent starts. If you start the components separately, start the Data Vault Service before you start the agent.
When the Data Vault Agent process starts, it reads the local ssa.ini file and uses information in the [SERVER] section to connect to the Data Vault Service. If an agent is started on a remote machine, there must be an ssa.ini file on that machine containing the same HOST and EXEPORT parameters and values as the ssa.ini file on the machine that hosts the Data Vault Service. Parameters that are specific to the agent can also be found in the [AGENT] section of the ssa.ini file.
You can start the Data Vault Agent with the following command:
ssaagent [ -u
AID
][ -p
priority
]
where:
  • AID
    is an optional user-defined numeric ID for the ssaagent process. Ssaagent processes viewed through the Data Vault Service administration command line program are identified by this Agent ID ("AID"), or if the AID was not set, by the operating system process ID (PID). Each ssaagent process started on the same machine must be given a unique AID value. A space must separate the -u flag from its value.
  • priority
    specifies an optional priority level for the ssaagent process. This must be a value from 0 to 10 inclusive, where a larger number means higher priority. A priority level of 0 effectively "freezes" the agent, making it unavailable for task execution after it completes its current task (if applicable). A priority level of 1 reserves the ssaagent process for administrator tasks, such as compressed data file registration. A space must separate the -p flag from its value.
You can start as many Data Vault Agents as required. At minimum, there must be one Data Vault Agent running. On UNIX, you can use the & option to run the agent in the background.
If the agent starts up successfully, it displays a message similar to the following (server names and port numbers will vary):
New connection 1 to the <Host: ALPHA1, PN: 6500> has been established LOG>Info : The agent: <host: alpha1, AID: 1368>, priority: 10 was successfully registered

0 COMMENTS

We’d like to hear from you!