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. Seamless Access Setup for Oracle R12 in Data Archive
  21. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  22. Using Multiple Engines in an ILM Environment
  23. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  24. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To Guide

Guidelines for Setting the Agent Priority Level

Guidelines for Setting the Agent Priority Level

Set the priority level of Data Vault agents based on how you want to distribute the processing load.
Use the following guidelines when you set the priority level of an agent:
  • You can set the priority level to a number between zero and two million. A high number indicates a high priority.
  • If you set the agent priority level to 0 or 1, the Data Vault Service assigns the following status to the agent:
    • Priority level 0. Indicates that the agent is not available to process any task. The Data Vault Service does not assign a task to an agent with a priority level of 0. To make the agent available to process tasks, change the priority level to a value higher than 0.
    • Priority level 1. Indicates that the agent primarily processes high-priority tasks such as registering data files or other administration tasks. The Data Vault Service can assign query tasks to an agent with priority level 1 if the agent is not busy and the Data Vault Service receives a high volume of queries.
  • The Data Vault Service assigns tasks based on the availability and priority level of an agent. For example, the agent on one node has a priority level of 100 and the agent on a second node has a priority level of 90. The Data Vault Service assigns a task to the agent on the first node because it has the highest priority level. If the Data Vault Service receives another query and the agent on the first node is still busy with the first task, the Data Vault Service assigns the next task to the agent on the second node. However, if the agent on the first node has completed the first task and is available, then the Data Vault Service assigns the task to the agent on the first node.
  • The Data Vault Service uses an algorithm to ensure that agents process the most number of queries possible. For example, two agents are available to process queries and the Data Vault Service receives one query that generates ten long-running tasks and a second query that generates four tasks. The Data Vault Service does not wait until all tasks for the first query are completed before it assigns the tasks of the second query to an agent. It balances the task assignment between the two agents so that agents process the two queries in parallel.