Note: PULL and GET terms are used interchangeably and mean the exact same thing.

Polaris asset (i.e. site) data is retrieved daily at 02:00 EST via RemoteFile domain which retrieves the specified file from the remote server (ATC FTP, refer to the PwSafe for details; file name is Errigal_Polaris_Assets.csv, it is located in the root directory of the ATC FTP server).

The retrieved file is processed via a relevant RemoteFileDiscoveryConfiguration assigned to the RemoteFile responsible for retrieving the asset flat file. Such RemoteFileDiscoveryConfiguration entry must have a Polaris assets processing script (found here) assigned as a parse data script.

All the PULL attempts are recorded via the GeneralDiscoverySyncHistory domain with the jobType being REMOTE_FILE_REQUEST (the targetAddress field will also say that the remote file interaction was GET).

• Verify that the configuration (Configuration) specifies the existing directory as the file transfer directory
• Verify that the remote file is assigned to the correct RemoteFileHost entry and that its details are correct
• Verify that the remote file transfer type is GET
• Verify that the remote file is active
• Verify that the remote file directory is correct and pointing to an existing location on the remote server (i.e. the file to be retrieved)
• Verify that the remote file remote file retrieval strategy is RETRIEVE_ONE_FILE_BY_NAME
• Verify that the correct remote file discovery configuration is assigned to the remote file
• Verify that the correct assets flat file parsing script is assigned to that remote file discovery configuration
• If the Reconcile Data Script and Process Data For KPI Script are not specified for that remote file discovery configuration, create new remote discovery script with the following content: log.debug 'ASSET PULL IN PROGRES…' and specify it for the role of the aforementioned scripts