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.
Make sure you’ve already added the job to the driver. If you haven’t, see Section 2.0, Adding a Predefined Job.
On the General tab in OpenText Identity Console (under Advanced > Jobs), configure the following options:
Enable job: Leave this option selected unless you don’t want the job to run.
Delete the job after the first run: Select this option if you want the job to run one time only and then be deleted.
Select the server(s) this job should run on: 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 search button to locate and select the Default Notification Collection object or any other notfTemplateCollection object that defines an SMTP mail server. To send notifications, the job reads the target mail server and authentication credentials (except the password, which is specified in the Email server password field) from the selected Default Notification Collection object.
Email server password: Set the password for your email server account.
NOTE:If you do not specify a password, one of the following conditions will apply depending on the authentication method used by the mail server:
For basic authentication, the job reads the email server password from named passwords using the direxml.engine.smtp key, which is stored at the active driverset level.
For modern authentication, the client secret is used instead of email server password. In this case, the job reads the client secret from named passwords using the dirxml.engine.smtp.clientsecret key, which is also stored in the active driverset level.
Display name: Displays the name assigned to the job.
Description: Displays the description assigned to the job.
On the Schedule tab, select one of the following options:
Toggle to schedule job: 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.
Toggle to run job manually: Runs the job only when you initiate it through the Run Now option (see Section 5.0, Starting a Job).
On the Scope tab, click + Add an object to the job scope icon to add the objects for which you want the job to trigger events. For each identified object, the job creates an event document. If no object is scoped, the job trigger creates one event document.
On the Parameters tab, set the parameters for which you want the job to submit trigger documents.
If you want to submit a trigger document for scoped objects that do not have a driver association, select true. Otherwise, keep the default of false.
If you want to use the job’s Common Name (CN) as a document identifier trigger, keep the default of true. Otherwise, select false.
(Optional) If you select false, enter the string that the job can use as the value for the trigger element’s Source attribute.
Select a method for submitting the trigger documents. If you want to queue the job the trigger is from, keep the default of Queue (use cache). Otherwise, select Direct (bypass cache).
(Optional) If you select Direct (bypass cache), you are presented with the Start driver if not running option. If you want to start the driver if it is not running, keep the default of true. Otherwise, select false.
(Optional) If you select true on the Start driver if not running option, you are presented with the Stop driver when finished processing triggers option with the default of true. Use the default to stop the driver after it finishes processing the trigger job, or select false to keep the driver running.
A customized job definition has its own parameter set.
On 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. For each result, you can specify the action you want performed when it occurs. For more information, see Understanding the Different States of a Job.
Click the No action link next to the result to display the Result Notification dialog box.
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.
Click OK to save your changes.
When you have finished configuring the job, click the Save icon to save your changes.
Select the job in the list (by selecting the check box next to the job name), then click the Get Status icon.
The Job Status dialog box displays any configuration errors.
Click Grant rights, then click OK to confirm the action.
If other errors are displayed, resolve the errors. Otherwise, click OK to close the Job Status dialog box.