Overview

User Job Mapping jobs do not transfer any data. They are used to map user accounts on the source and destination platforms. The User Job Mapping job automatically generates child jobs based on the settings you’ve chosen for the job. These child jobs perform all the data transfers. You can select an account map for automatic user mapping rules and exceptions and filter out users by explicitly including or excluding them.

Adding Locations

In addition to choosing the source and destination platforms for the User Job Mapping job, you need to specify the child job source and destination paths that should be used when creating the child jobs. This directory within each folder will be used as the source.

• Target the root of each folder: The child job will be created for the first-level folder relative to the source path.
• Target a specific directory within each folder: If folders exist in every directory, this option allows you to define a specific directory.

Setting the Job Schedule 

You will be prompted to schedule the job after configuring policies, behaviors, and advanced features. This schedule will be applied to the child jobs. The parent job will run immediately to create the child jobs. After the child jobs are created, the default schedule is set to run every six hours to review the source for any new content. You can edit the schedules for the parent and child jobs anytime.

Configuring Mappings for the User Job Mapping Job

Before running a User Job Mapping job, you must configure the settings that determine the general rules for how the child jobs are generated. The user mappings and filters allow you to override automatic user mapping rules and filter out users by explicitly including or excluding them. The job status and button you see on this screen vary based on the job settings. If you have not selected a user map for the job, the job status will be “Awaiting user interaction,” and you will see a Return to job button. You cannot run the job until you add a user map.

Once a user map has been assigned to the job, the status will be “Paused,” and you will see a Run job button so you can run the job. See “Running User Job Mapping Jobs” below for more information.

Configurations

• Map specific users to one another: Select this option to use an existing account/user map created to map users. Select the map you want to use for this job from the list.
• Create new user map policy: Select this option to create a new user map. Refer to “Understanding Maps” for more information about the options used to create the user map.
• User Account Job Generation: Use this section to identify which connection should be used to determine user accounts. If you select Source, DryvIQ will use the source connection as the source of user accounts when generating user account jobs. If you select Destination, DryvIQ will use the destination connection as the source of user accounts when generating user account jobs.
• Remove user account jobs that are no longer valid: This is an on/off setting that deletes jobs that are no longer valid.
• Email Domain: Specify an email domain to limit the generation of User job mapping child jobs to only users with this email domain. For example, enter "example.com" to create a job for the user "test@example.com" but not for the user "test@something.com."
• Import user filters: Import an inclusion or exclusion mapping file that should be applied to the job. You can upload the file from your computer or use a file on the source platform. (See “Mapping Import CSV File Guidelines” for information about generating mapping files to include or exclude users.)
  • An inclusion map specifies which users to include when generating child jobs. Child jobs are only created for users in the map that can be matched. All other users will be excluded. 
  • An exclusion map specifies which users to exclude when generating child jobs. Child jobs will not be created for the users in this map. Jobs will be created for all other users.

Run User Job Mapping Job

After configuring your user job mapping job, run it. This will execute the parent job, which will create the child jobs. After the child jobs are created, the default schedule is set to run every six hours to review the source for any new content. You can edit the schedule for the parent and child jobs anytime.