Common Questions on Argent Job Scheduling

Active Directory

The Argent Job Scheduler security implementation is fully-compliant with Active Directory

User accounts and passwords used by Job Scheduler are defined through Windows tools

Argent Job Scheduler does not have a separate or private mechanism to define user accounts or passwords

Fail Over Procedure

Customers can easily configure alternate Argent Queue Engine servers to be selected if a given Queue Engine server fails

Argent Job Scheduler has a failover/failback methodology requiring two separate machines

Argent Job Scheduler is installed on both machines with configuration values to control whether the server is operating in a primary or a secondary role

When a failover outage occurs on the primary machine, the secondary server takes over and continues running jobs

SNMP Flags

Argent Job Scheduler does not use SNMP

Argent Job Scheduler does not expose an SNMP MIB

Customers that want to check on the status/health of an Argent Queue Engine server, for example, should strongly consider Argent’s AT technology

Argent Job Scheduler servers and Argent Queue Engine servers can be discovered by SNMP crawlers


Triggers are a way to change the functionality of a SQL-compliant database

Argent Job Scheduler does not use any triggers in the database schema

Argent does not support customers adding triggers to the Argent Job Scheduler tables

Virtual Machines

Argent does not recommend using Virtual Machines for critical production products such as the Argent Job Scheduler and the Argent Queue Engine

For more details, click here