• Workforce Connect Profile Manager Customer Administrator Guide
View Import Job History
View Import Job History

View Import Job History

Your privileges must permit you to view the job history.
  1. From the dashboard, click
    Jobs
    .
  2. Click For the import job history you wish to view.
    The
    Import Job History
     screen appears.
    Import Job History Screen
    Process State displays the job execution status. The status gets periodically updated depending on the BULK_UPDATE_RECORD_SIZE (Default Value = 50) configuration in the AD-Connector service. The import job execution runs parallel with multiple threads depending on the number of PTT Pro instances configured for that tenant. BULK_UPDATE_RECORD_SIZE is applicable per thread. Hence the exact number of records processed in each status update varies for each deployment.
    For example, if the number of PTT Pro instances is 24 and BULK_UPDATE_RECORD_SIZE = 50, the status is updated and displayed after 24*50 = 1200 records.
    Along with the status update, all relevant job history and delta records also get updated in the Profile Manager.
    After the job is executed, it goes through the following statuses:
    Job Status
    Description
    IN_PROGRESS
    When the job started execution.
    FAILURE
    When the job execution fails.
    SUCCESSFUL
    When the job execution becomes successful.
    STOP_TRIGGERE
    If the user has initiated the Stop feature on the running job. From this state, jo,b status can go into the following status:
    • FAILURE
      : If execution fails before the stop is processed.
    • STOPPED
      : If more records are pending to be completed, and can stop the job before processing all the records.
    • SUCCESSFUL
      : If no more records are pending processing. All the records are already processed before the Stop feature is processed.
    STOPPED
    If the job execution is stopped and records remain to be processed. The stopped jobs can be restarted like any other jobs.
    The Message column displays the error message in case of FAILURE or a summary of the import relevant to job configuration.
    This includes:
    • The number of records processed.
    • The number of successful and failed records for the Profile Manager and PTT Pro.
    • The number of modified, unmodified, new, and deleted Profile Manager and PTT Pro records.
    • The number of ignored records is because of either no matching site entry defined in the sitemap file or the site is defined for a different Profile Manager cluster (This applies only to the non-proxy environment with sitemap present in AD-Connector-service).
    • In case of Flat File Import, the job can also fail if the number of records in the usermap CSV file exceeds the flat-file variance threshold percentage allowed for this tenant. Variance is checked against the previous successful run on upper and lower boundaries. This would prevent any wrongly generated CSV file from being used for import which causes deleting previous records not present in the current CSV file.
    • In case of Flat File Import, the job can also fail if the usermap CSV file does not contain the header row. Two mandatory columns Department and UserName, identify the header row. The name of these columns can be changed during deployment based on the usermap header format.
      • The Department column header name can be changed using the general site-header-name or CSV_SITE_HEADER environment variable. (Default Value: Department).
      • The UserName column header name can be changed using ldap.uniqueName or LDAP_UNIQUE_NAME environment variable (Default value: samaccountname).
      • For all other header columns, it just loads the column as is. The sample error message for missing header follows:
    • In case of PFM-Proxy, the number of records processed is equal to the number of records of either Profile Manager or PTT Pro, depending on the selected dispatcher.
    • In case of non-proxy, the number of records processed is equal to the number of records of either Profile Manager or PTT Pro.
    The sitemap file contains the mapping for the site to the Profile Manager instance.
    Actions available on the
    Import Job History
     screen are view details, view deltas, and view dispatcher.
  3. Click to view details.
  4. Click to stop the running job. This icon is visible only for the jobs that have started execution.
    After clicking the Stop icon, the job goes into the STOP_TRIGGERED state. The execution of the job stops after processing all the current set of records as defined by the BULK_UPDATE_RECORD_SIZE (Default Value = 50 per thread). The exact number of records in a chunk depends on the number of threads (number of PTT Pro instances).
    When all the records in the current chunk are processed, the job goes to either STOPPED (if there are more records to be processed) or SUCCESSFUL (if all the records are processed).
    If the job status is in the STOPPED state, during the next subsequent execution, all unprocessed records from the previous run, along with any error and modified records, are processed.
    • The number of enhanced PTT Pro instances configured in the sitemap determines the number of users created/updated in parallel. The number of enhanced PTT Pro server names determines the number of users deleted in parallel. Refer to the Profile Manager Provisioning Guide for information about importing the users using flat files.
    • Clicking the Stop icon stops the execution of the jobs that are in process with a large number of records, allows fixing the configuration error, and then restarts the jobs.
  5. Click
    View Deltas
     to view more information.
    The
    Deltas
     dialog box appears.
    The
    Type
     column displays the status of the record, such as new, modified, deleted, or unmodified. Whether or not the unmodified records are listed depends on the AD-Connector service configuration. Typically, we should turn this off for the user import using a flat file to reduce the required storage.
    The Import function checks for changes to the user data by comparing it with the current user data and ignoring the AD whitelist attributes configured for the tenant. If there is no AD whitelist configured for the tenant, it uses the default whitelist attributes configured in the ad-connector service system setting (general.attributesWhitelist).
    In the AD-Connector service, the default whitelist attributes are: “uncreated, whenchanged, dscorepropagationdata, unchanged, whencreated, pwdlastset, lastlogontimestamp” unless it is changed in the deployment configuration.
    This page supports sorting for entire database records instead of just the displayed page. All the displayed columns are included in the sorting.
    This page also supports search on the following columns:
    • User/Group
    • System (Profile Manager/PTT Pro)
    • Type (new/modified/unmodified/deleted)
    Deltas Dialog Box
  6. Click an option in the
    Dispatchers
     column to more information.
    The
    Dispatcher History
     dialog box appears in the STOPPED in this example, and it is for the PTT Pro dispatcher:
    This page supports sorting for entire database records instead of just the displayed page. All the displayed columns are included in the sorting.
    This page also supports search on the following columns:
    • User/Group
    • Action (new/modified/deleted)
    • Process State (FAILURE/SUCCESSFUL)
    Dispatcher History (PTT Pro) Dialog Box
    The User/Group field is populated using the LDAP_UNIQUE_NAME attribute value specified in the AD Connector service. By default, this is mapped to samaccounname during deployment.