When GCP or SFTP is used to import data, the customer provides a repository to Profile Manager to access and retrieve the user and site mapping files. These two files define each user and the server to which the user belongs.
The configuration of the import job is the same as the AD/ADFS import job. The job can be scheduled and, once established as working, can be setup to run automatically through the scheduler. The job populates PFM and PTT Pro users.
You are required to configure Attribute Transformation before running the import job.
The requirements of a flat file import job include:
The query field can be populated with anything.
A best practice is to describe the import job as GCP or SFTP.
The configuration for GCP or SFTP is setup by the Zebra administrators in the AD Connector.
This information is provided by the customer to Zebra.
The Filter is the exact file name (encrypted file name) of the user import file.
The Site Map file is a mutually agreed upon name that is established in the Profile Manager database. The Site Map file is not referenced in the Import Job configuration.
Do not schedule the initial import that includes PTT Pro users. The import into PTT Pro can take a long time and the scheduler should not be configured and activated until PTT Pro is fully populated.
For each Import Job the customer can:
Review import history in the job history interface. The job history displays user updates as Added, Deleted, and Modified
Can setup job status notifications.
Can schedule import jobs .
Import jobs can be scheduled to run on a regular basis.
The import file should be encrypted. An unencrypted file is supported but not recommended.
The import file must be a comma separated value format with UTF-8 or ANSI encoding.
There are several csv file types available in Excel, but not all are UTF-8 or ANSI encoded. One method to validate a csv file is to open it in Notepad++ and click the
