A job combines multiple Mappings and/or Roles into a single object, so NIM can evaluate & execute them simultaneously.

To get started, Create a job.

A common way to set up jobs is:

  • One job per target system, which contains:

    • One or more mapping operations (crud type) per user lifecycle stage.

    • A single role operation (groupmembership type).

      Role operations take place on a per-system basis (not a per-lifecycle stage basis). Only a single role operation should exist per target system. It will execute all roles pertaining to the system that currently exist in the active role model.

For example:


However, you can set up your jobs differently, if makes more sense for your organization. For example, you can split the mappings and roles for a single target system into multiple jobs. Or, you can combine the mappings and roles for multiple target systems into a single job. It depends on what should be executed, when, and in what combination. You may also want to split up jobs to make them easier to maintain.

When a job is executed, the mappings and role operations that it contains are executed sequentially, in the order that you've specified (the Index value, ascending).

Although it is possible to Evaluate and execute a job manually, you will usually want to schedule your jobs on a recurring basis using Sync tasks.

Jobs are trigger events of type job. See Events.