Data Synchronization facilitates the automatic upload and updating of subscriber data from an institutional directory system. This section describes how this element functions, and the various features available to users in the configuration and maintenance of the Data Feed.

Please see the File Format Options page for information on the formats we support.

FTPS/SFTP Connection

AppArmor provides an FTP folder where you can place the extracts from your directory. This tab provides the connection details you’ll need to set up an FTP connection, along with some basic information about file format.

FTPS

This section of the Dashboard contains the FTPS connection details we’ve set up for your institution, if applicable.

FTPS connections should be made over Port 2100

SFTP

If you'd like to use SFTP, please generate a public key that is at least 2048 bits and send it to your AppArmor Onboarding/Support contact so we can load it into our SFTP server.

SFTP connections should be made over Port 2200

Custom Subscriber Sync

You can view all of the files in the CUSTOM folder on the FTP site. Most clients rely on AppArmor Staff to create file mappings for these files. We recommend that for the most part any interaction with this page (other than downloading a file to verify its contents) is left to AppArmor Staff.

Sync Logs and Data Sync Notifications

AppArmor provides information about the status of the Data Synchronization by giving authorized Dashboard users access to the full logs from the Data Synchronization and allowing users to opt-into receiving automated email notifications about the activity of the Data Synchronization. We strongly recommend subscribing to these notifications to keep an eye on the status of your automated Data Synchronization.

While there's no Menu Item for the Data Synchronization section, you can access it through a button in the top right corner of the Alerting Mechanisms page:

Sync Service Error

The way our system works is that when you drop in a file the system automatically starts the import when it detects a new file.

If you receive a Sync Service Error Email that looks something like this for example:

Error: Error: Can't process c:\FTPSites\data.apparmor.com\LocalUser\[clientWebsiteURL]\CUSTOM\tmpAppArmor.csv

This means that the system you are using is writing a file with this name, and then renaming it to AppArmor.csv.

To resolve this issue, the client will need to eliminate the step where we get the "tmpAppArmor.csv" file. We think this should solve the problem and allow our system to import the file as expected.