Novell IDENTITY MANAGER 3.6.1 - JOBS GUIDE User manual

Novell®
www.novell.com
novdocx (en) 13 May 2009
AUTHORIZED DOCUMENTATION
Identity Manager 3.6 Jobs Guide
Identity Manager
3.6.1
June 05, 2009
Jobs Guide

novdocx (en) 13 May 2009
Legal Notices
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.
reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to
notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities
on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export
laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses.
Please refer to the International Trade Services (http://www.novell.com/company/policies/trade_services) for more
information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary
export approvals.
Copyright © 2008 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied,
stored on a retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or
more additional patents or pending patent applications in the U.S. and in other countries.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the latest online documentation for this and other Novell products, see
the Novell Documentation Web page (http://www.novell.com/documentation).

novdocx (en) 13 May 2009
Novell Trademarks
For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/
trademarks/tmlist.html).
Third-Party Materials
All third-party trademarks are the property of their respective owners.

4Identity Manager 3.6 Jobs Guide
novdocx (en) 13 May 2009

Contents 5
Contents
novdocx (en) 13 May 2009
About This Guide 7
1Overview 9
2 Adding a Predefined Job 11
3 Configuring a Predefined Job’s Properties 15
3.1 Configuring the Random Password Generator Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2 Configuring the Schedule Driver Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.3 Configuring the Subscriber Channel Trigger Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.4 Configuring the Driver Health Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.5 Configuring the Password Expiration Notification Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4 Creating a Custom Job 25
4.1 Job Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.2 Creating the Job Definition and Job Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
4.3 Adding the Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5 Starting a Job 29
6 Stopping a Job 31
7 Disabling a Job 33
8 Checking a Job’s Status 35
9 Deleting a Job 37

6Identity Manager 3.6 Jobs Guide
novdocx (en) 13 May 2009

About This Guide 7
novdocx (en) 13 May 2009
About This Guide
This guide contains information about managing Identity Manager jobs. The guide is organized as
follows:
Chapter 1, “Overview,” on page 9
Chapter 2, “Adding a Predefined Job,” on page 11
Chapter 3, “Configuring a Predefined Job’s Properties,” on page 15
Chapter 4, “Creating a Custom Job,” on page 25
Chapter 5, “Starting a Job,” on page 29
Chapter 6, “Stopping a Job,” on page 31
Chapter 7, “Disabling a Job,” on page 33
Chapter 8, “Checking a Job’s Status,” on page 35
Chapter 9, “Deleting a Job,” on page 37
Audience
This guide is intended for administrators, consultants, and network engineers who require a high-
level introduction to Identity Manager business solutions, technologies, and tools.
Documentation Updates
For the most recent version of this document, see the Identity Manager Documentation Web site
(http://www.novell.com/documentation/idm36/index.html).
Additional Documentation
For documentation on other Identity Manager drivers, see the Identity Manager Drivers Web site
(http://www.novell.com/documentation/idm36drivers/index.html).
Documentation Conventions
In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and
items in a cross-reference path.
A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
trademark.
When a single pathname can be written with a backslash for some platforms or a forward slash for
other platforms, the pathname is presented with a backslash. Users of platforms that require a
forward slash, such as Linux* or UNIX*, should use forward slashes as required by your software.

8Identity Manager 3.6 Jobs Guide
novdocx (en) 13 May 2009

Overview
1
9
novdocx (en) 13 May 2009
1
Overview
Identity Manager provides the ability to launch jobs that perform specific tasks. The jobs can be run
one or more times either manually or at scheduled times.
Identity Manager provides five predefined jobs:
Random Password Generator: Generates a random password for each object defined in the
job’s scope. The password is generated by NMASTM to match a Password Policy object that the
job references. The job submits the generated passwords one at a time to a driver’s Subscriber
channel. The Subscriber channel policies must take action on the passwords.
Schedule Driver: Starts or stops a driver.
Subscriber Channel Trigger: Sends event documents to be processed by a driver’s Subscriber
channel. For example, a job could generate an event document to trigger policies associated
with a user. Submitted event documents can be queued to the driver cache, or they can bypass
the cache and be processed immediately.
Driver Health: Evaluates the health conditions for a driver, assigns the health state, and carries
out any actions associated with the health state. This job is used in conjunction with driver
health monitoring. For complete instructions about setting up driver health monitoring,
including using the Driver Health job, see “Monitoring Driver Health” in the Identity Manager
3.6.1 Common Driver Administration Guide.
Password Expiration Notification: Searches an LDAP directory for objects whose passwords
expire in a specified number of days. When an object that meets the criteria is discovered, the
job sends an e-mail to the address contained in the object’s mail LDAP attribute.
Information about using the predefined jobs is provided in Chapter 2, “Adding a Predefined Job,” on
page 11 and Chapter 3, “Configuring a Predefined Job’s Properties,” on page 15.
You can also develop custom jobs to perform tasks. A custom job requires you to create a Job
Definition and a Job Implementation. The Job Definition is XML code that defines the parameters
for the job. The Job Implementation is a JAR file that contains the Java* classes that perform the
task. The job can perform any task that you can implement through Java classes. Because the job is
initiated through the Metadirectory engine, the job also has access to the Identity Vault data. For
more information, see Chapter 4, “Creating a Custom Job,” on page 25.

10 Identity Manager 3.6 Jobs Guide
novdocx (en) 13 May 2009

Adding a Predefined Job
2
11
novdocx (en) 13 May 2009
2
Adding a Predefined Job
Identity Manager includes the following predefined jobs:
Random Password Generator: Generates a random password for identified objects.
Schedule Driver: Starts or stops the driver.
Subscriber Channel Trigger: Submits XML documents to the Subscriber channel to trigger
events.
Driver Health: Evaluates the health conditions for the driver, assigns the health state, and
carries out any actions associated with the health state.
Password Expiration Notification: Sends e-mail notifications to users whose passwords are
about to expire.
The first three jobs (Random Password Generator, Schedule Driver, and Subscriber Channel
Trigger) operate at the driver level, which means that you add them to individual drivers. The other
two jobs (Driver Health and Password Expiration Notification) operate at the driver set level; they
automatically apply to all drivers in the driver set unless you change the job’s scope to exclude some
drivers.
The following steps provide instructions for using iManager to add predefined jobs. For information
about using Designer to add jobs, see “Scheduling Jobs” in the Designer 3.5 for Identity Manager
3.6 Administration Guide.
1In iManager, click to display the Identity Manager Administration page.
2Open the Overview page for the driver or driver set where you want to add the job:
2a In the Administration list, click Identity Manager Overview to display the Identity
Manager Overview page.
2b In the Search in field, specify the fully distinguished name of the container where you
want to start searching for driver sets and then click , or leave [root] in the field and
click to search from the root of the tree.
You can also click to browse for and select the container in the tree structure, or click
to select the container from a list of previously selected objects.
2c After the available driver sets are displayed on the Driver Sets page, click the desired
driver set to display the Driver Set Overview page.
2d (Conditional) If you are adding the job to a driver, click the driver to display the Driver
Overview page.
3Click the Jobs tab.
4Click New to display the Create Job page.

12 Identity Manager 3.6 Jobs Guide
novdocx (en) 13 May 2009
5In the Job Name field, specify a descriptive name for the job.
6Under Job Type, make sure that Installed is selected, then choose one of the following job
types:
Random Password Generator (Driver Only): Generates a random password for each
object in the job’s scope. The password is generated by NMASTM to match the Password
Policy object that the job references. These Password Policy objects are not usually the
same as those used for eDirectoryTM user password policies.
The job submits the generated passwords one at a time to the driver’s Subscriber channel.
The Subscriber channel policies must take action on the passwords.
Schedule Driver (Driver Only): Starts or stops the associated driver. You can also toggle
a driver to start the driver if it is stopped or to stop the driver if it is running.
Subscriber Channel Trigger (Driver Only): Submits zero or more trigger documents to
the Subscriber channel. The submission can either be a document per object if a scope is
defined, or it can be a single trigger event if no scope is defined.
Trigger event documents identify the job and the scope object. A trigger event can bypass
the cache and be processed immediately if desired. Trigger jobs allow you to use driver
policies that you can customize for your personal requirements.

Adding a Predefined Job 13
novdocx (en) 13 May 2009
Driver Health (Driver Set): Evaluates the health conditions for a driver, assigns the
health state, and carries out any actions associated with the health state.
Password Expiration Notification (Driver Set): Sends e-mail notifications to users
whose passwords are about to expire.
7In the Server field, select the servers where you want to run the job.
8Click OK to create the job and display its configuration properties.
9To configure the job’s properties, continue with the instructions in the appropriate section:
Section 3.1, “Configuring the Random Password Generator Job,” on page 15
Section 3.2, “Configuring the Schedule Driver Job,” on page 17
Section 3.3, “Configuring the Subscriber Channel Trigger Job,” on page 18
Section 3.4, “Configuring the Driver Health Job,” on page 19
Chapter 3, “Configuring a Predefined Job’s Properties,” on page 15

14 Identity Manager 3.6 Jobs Guide
novdocx (en) 13 May 2009

Configuring a Predefined Job’s Properties
3
15
novdocx (en) 13 May 2009
3
Configuring a Predefined Job’s
Properties
The following sections provide instructions for using iManager to configure the properties for the
five predefined jobs: Random Password Generator, Schedule Driver, Subscriber Channel Trigger,
Driver Health, and Password Expiration Notification. For each job, you can schedule the runtimes,
define the scope of objects that the job applies to, set the job-specific parameters, and determine the
methods used for results notification. For information about using Designer to configure a job, see
“Scheduling Jobs” in the Designer 3.5 for Identity Manager 3.6 Administration Guide.
The steps assume that you’ve already added the job to a driver or driver set. If you have not, see
Chapter 2, “Adding a Predefined Job,” on page 11.
Section 3.1, “Configuring the Random Password Generator Job,” on page 15
Section 3.2, “Configuring the Schedule Driver Job,” on page 17
Section 3.3, “Configuring the Subscriber Channel Trigger Job,” on page 18
Section 3.4, “Configuring the Driver Health Job,” on page 19
Section 3.5, “Configuring the Password Expiration Notification Job,” on page 21
3.1 Configuring the Random Password
Generator Job
The Random Password Generator job creates a random password for each object defined in the job’s
scope. The password is generated by NMASTM to match a Password Policy object that the job
references. Generally, each driver requires a password policy designed specifically for the connected
system. If you don’t have a password policy to use, you need to create one before continuing with
the job configuration.
The job submits the generated passwords one at a time to the driver’s Subscriber channel. The
Subscriber channel policies must take action on the passwords.
1Make sure you’ve already added the job to the driver. If you haven’t, see Chapter 2, “Adding a
Predefined Job,” on page 11.
2On the General page, configure the following options:
Enable Job: Leave this option selected unless you don’t want the job to run.
Delete the Job After it Runs Once: Select this option if you want the job to run one time only
and then be deleted.
Servers: Select the servers where you want the job to run. Multiple servers are available only if
the driver is running on multiple servers.
Email Server: To monitor the job, you (or others) can receive e-mail notifications whenever
certain results occur for the job. You configure e-mail notification on the Results page.
However, to enable this e-mail notification to work, you must first specify the e-mail server that
will be used to send the notifications. Click the button to locate and select the Default
Notification Collection object or any other notfTemplateCollection object that defines an
SMTP mail server.

16 Identity Manager 3.6 Jobs Guide
novdocx (en) 13 May 2009
Display Name: Displays the name assigned to the job.
Description: Displays the description assigned to the job.
3On the Schedule page, select one of the following options:
Run on a Schedule: Runs the job on a daily, weekly, monthly, or yearly schedule. You can also
specify a custom schedule; use the crontab standard when specifying a custom schedule.
Run Manually: Runs the job only when you initiate it through the Run Now option (see
Chapter 5, “Starting a Job,” on page 29).
4On the Scope page, click Add to add the objects for which you want to generate passwords.
5On the Parameters page, fill in the following fields:
Password Policy Object Used for Password Generation: Select the Password Policy object
you want to use to generate the passwords. NMAS uses the password policy to generate the
passwords. Generally, each driver requires a password policy designed specifically for the
connected system. If you don’t have a password policy to use, click OK to save the job’s
current configuration, then create a password policy.
Generate a Password for Objects without a Driver Association: This is set to False by
default. If you added objects to the Scope page that are not associated with objects in the
driver’s connected system, and you want to generate passwords for these objects, select True.
6On the Results page, define the actions you want performed based on the results for the job.
Each time the job runs, it generates Intermediate results and a Final result. The possible results
are Success, Warning, Error, and Aborted. Intermediate results are generated at various points
throughout the job. The Final result is generated when the job is finished. For each result, you
can specify the action you want performed when it occurs: 1) generate an event for Novell®
Audit or Novell SentinelTM and 2) generate an e-mail notification. For example, you might want
no action to occur for an Intermediate Success result and an e-mail notification to be sent for an
Intermediate Error result.
To define an action for a result:
6a Click the No action link next to the result to display the Result Notification dialog box.
6b Select Audit result if you want to generate an event for Novell Audit or Novell Sentinel.
or
Select Send email, then fill in the recipient and e-mail template information.
6c Click OK to save your changes.
7When you have finished configuring the job, click OK to save your changes.
The job is added to the job list.
8Select the job in the list (by selecting the check box next to the job name), then click Get Status.
The Job Status dialog box displays any configuration errors. Because the job requires rights to
the driver object and those rights have not yet been granted, you see an
Insufficient
rights to driver object
error.
9Click Grant rights, then click OK to confirm the action.
10 If other errors are displayed, resolve the errors. Otherwise, click Close to close the Job Status
dialog box.

Configuring a Predefined Job’s Properties 17
novdocx (en) 13 May 2009
3.2 Configuring the Schedule Driver Job
The Schedule Driver job starts or stops the driver based on an established schedule.
1Make sure you’ve already added the job to the driver. If you haven’t, see Chapter 2, “Adding a
Predefined Job,” on page 11.
2On the General page, configure the following options:
Enable Job: Leave this option selected unless you don’t want the job to run.
Delete the Job After it Runs Once: Select this option if you want the job to run one time only
and then be deleted.
Servers: Select the servers where you want the job to run. Multiple servers are available only if
the driver is running on multiple servers.
Email Server: To monitor the job, you (or others) can receive e-mail notifications whenever
certain results occur for the job. You configure e-mail notification on the Results page.
However, to enable this e-mail notification to work, you must first specify the e-mail server that
will be used to send the notifications. Click the button to locate and select the Default
Notification Collection object or any other notfTemplateCollection object that defines an
SMTP mail server.
Display Name: Displays the name assigned to the job.
Description: Displays the description assigned to the job.
3On the Schedule page, select one of the following options:
Run on a Schedule: Runs the job on a daily, weekly, monthly, or yearly schedule. You can also
specify a custom schedule; use the crontab standard when specifying a custom schedule.
Run Manually: Runs the job only when you initiate it through the Run Now option (see
Chapter 5, “Starting a Job,” on page 29).
4Ignore the Scope page; it does not apply to the Schedule Driver job.
5On the Parameters page, select the type of action you want the job to perform:
Start the Driver: Starts or restarts the driver.
Stop the Driver: Stops the driver.
Toggle the Driver: Starts the driver if it is stopped. Stops the driver if it is running.
6On the Results page, define the actions you want performed based on the results for the job.
Each time the job runs, it generates Intermediate results and a Final result. The possible results
are Success, Warning, Error, and Aborted. Intermediate results are generated at various points
throughout the job. The Final result is generated when the job is finished. For each result, you
can specify the action you want performed when it occurs: 1) generate an event for Novell
Audit or Novell Sentinel and 2) generate an e-mail notification. For example, you might want
no action to occur for an Intermediate Success result and an e-mail notification to be sent for an
Intermediate Error result.
To define an action for a result:
6a Click the No action link next to the result to display the Result Notification dialog box.
6b Select Audit result if you want to generate an event for Novell Audit or Novell Sentinel.
or

18 Identity Manager 3.6 Jobs Guide
novdocx (en) 13 May 2009
Select Send email, then fill in the recipient and e-mail template information.
6c Click OK to save your changes.
7When you have finished configuring the job, click OK to save your changes.
The job is added to the job list.
8Select the job in the list (by selecting the check box next to the job name), then click Get Status.
The Job Status dialog box displays any configuration errors. Because the job requires rights to
the driver object and those rights have not yet been granted, you see an
Insufficient
rights to driver object
error.
9Click Grant rights, then click OK to confirm the action.
10 If other errors are displayed, resolve the errors. Otherwise, click Close to close the Job Status
dialog box.
3.3 Configuring the Subscriber Channel Trigger
Job
The Subscriber Channel Trigger job sends event documents to be processed by the driver’s
Subscriber channel. For example, a job could generate an event document to trigger policies
associated with a user.
You configure the job to generate zero, one, or more event documents by defining a scope for the
job. The scope identifies objects for which you want the job to trigger events. If you do not include a
scope (no objects), the job creates one event document. If you identify one or more objects, the job
creates event documents for each object.
Submitted event documents can be queued to the driver cache, or they can bypass the cache and be
processed immediately.
1Make sure you’ve already added the job to the driver. If you haven’t, see Chapter 2, “Adding a
Predefined Job,” on page 11.
2On the General page, configure the following options:
Enable Job: Leave this option selected unless you don’t want the job to run.
Delete the Job After it Runs Once: Select this option if you want the job to run one time only
and then be deleted.
Servers: Select the servers where you want the job to run. Multiple servers are available only if
the driver is running on multiple servers.
Email Server: To monitor the job, you (or others) can receive e-mail notifications whenever
certain results occur for the job. You configure e-mail notification on the Results page.
However, to enable this e-mail notification to work, you must first specify the e-mail server that
will be used to send the notifications. Click the button to locate and select the Default
Notification Collection object or any other notfTemplateCollection object that defines an
SMTP mail server.
Display Name: Displays the name assigned to the job.
Description: Displays the description assigned to the job.
3On the Schedule page, select one of the following options:
Run on a Schedule: Runs the job on a daily, weekly, monthly, or yearly schedule. You can also
specify a custom schedule; use the crontab standard when specifying a custom schedule.

Configuring a Predefined Job’s Properties 19
novdocx (en) 13 May 2009
Run Manually: Runs the job only when you initiate it through the Run Now option (see
Chapter 5, “Starting a Job,” on page 29).
4On the Scope page, click Add to add the objects for which you want to generate passwords.
5On the Parameters page, fill in the following fields:
Password Policy Object Used for Password Generation: Select the Password Policy object
you want to use to generate the passwords. NMAS uses the password policy to generate the
passwords. Generally, each driver requires a password policy designed specifically for the
connected system. If you don’t have a password policy to use, click OK to save the job’s
current configuration, then create a password policy.
Generate a Password for Objects without a Driver Association: This is set to False by
default. If you added objects to the Scope page that are not associated with objects in the
driver’s connected system, and you want to generate passwords for these objects, select True.
6On the Results tab, define the actions you want performed based on the results for the job.
Each time the job runs, it generates Intermediate results and a Final result. The possible results
are Success, Warning, Error, and Aborted. Intermediate results are generated at various points
throughout the job. The Final result is generated when the job is finished. For each result, you
can specify the action you want performed when it occurs: 1) generate an event for Novell
Audit or Novell Sentinel and 2) generate an e-mail notification. For example, you might want
no action to occur for an Intermediate Success result and an e-mail notification to be sent for an
Intermediate Error result.
To define an action for a result:
6a Click the No action link next to the result to display the Result Notification dialog box.
6b Select Audit result if you want to generate an event for Novell Audit or Novell Sentinel.
or
Select Send email, then fill in the recipient and e-mail template information.
6c Click OK to save your changes.
7When you have finished configuring the job, click OK to save your changes.
The job is added to the job list.
8Select the job in the list (by selecting the check box next to the job name), then click Get Status.
The Job Status dialog box displays any configuration errors. Because the job requires rights to
the driver object and those rights have not yet been granted, you see an
Insufficient
rights to driver object
error.
9Click Grant rights, then click OK to confirm the action.
10 If other errors are displayed, resolve the errors. Otherwise, click Close to close the Job Status
dialog box.
3.4 Configuring the Driver Health Job
The Driver Health job evaluates the conditions for a driver’s health states and assigns the driver the
appropriate state. The job also executes any actions associated with the assigned state. For more
information about setting up health monitoring for a driver, see “Monitoring Driver Health” in the
Identity Manager 3.6.1 Common Driver Administration Guide.
1Make sure you’ve already added the job to the driver set. If you haven’t, see Chapter 2,
“Adding a Predefined Job,” on page 11.

20 Identity Manager 3.6 Jobs Guide
novdocx (en) 13 May 2009
2On the General page, configure the following options:
Enable Job: Leave this option selected unless you don’t want the job to run.
Delete the Job After it Runs Once: Select this option if you want the job to run one time only
and then be deleted.
Servers: Select the servers where you want the job to run. Multiple servers are available only if
the driver is running on multiple servers.
Email Server: To monitor the job, you (or others) can receive e-mail notifications whenever
certain results occur for the job. You configure e-mail notification on the Results page.
However, to enable this e-mail notification to work, you must first specify the e-mail server that
will be used to send the notifications. Click the button to locate and select the Default
Notification Collection object or any other notfTemplateCollection object that defines an
SMTP mail server.
Display Name: Displays the name assigned to the job.
Description: Displays the description assigned to the job.
3On the Schedule page, specify when you want the job to run:
The Driver Health job is a continuously running job, meaning that it does not stop unless a
health state action shuts it down or it is shut down manually. The job must run continuously to
be able to support transaction data collection for use in Transactions History conditions.
If the job does stop, it is restarted based on the schedule.
Run on a Schedule: Runs the job on a daily, weekly, monthly, or yearly schedule. You can also
specify a custom schedule; use the crontab standard when specifying a custom schedule. The
default schedule checks every minute to see if the job is running. If the job is not running, it is
started.
Run Manually: Runs the job only when you initiate it through the Run Now option (see
Chapter 5, “Starting a Job,” on page 29).
4On the Scope page, add the driver sets or individual drivers you want the job applied to.
By default, the job applies to all drivers in the driver set. You can, however, modify the list so
that the job applies only to specific drivers in the driver set. You can also add other driver sets
or drivers from other driver sets.
5On the Parameters page, select the type of action you want the job to perform:
Login ID: This defaults to the login ID that was used when creating the driver job. You should
change this only if you want the driver to authenticate by using different credentials.
Login password: This is the password required for the login ID that you supplied in the Login
ID field.
Subscriber Heartbeat: Controls whether the Driver Health job does a heartbeat query on a
driver's Subscriber channel before performing a healthcheck on the driver.
Polling interval: Determines how often the job evaluates the conditions for the health states,
assigns the driver the appropriate state, executes any actions associated with the assigned state,
and stores the driver’s transaction data. The default polling interval is one minute.
Polling interval units: Specifies the time unit (minutes, hours, days, weeks) for the number
specified in the Polling interval setting.
Duration sampling data is kept: Specifies how long a driver’s transaction data is kept. The
default, two weeks, causes a transaction to be retained for two weeks before being deleted. A
longer duration provides a greater time period that can be used in Transactions History