User Tools
Writing /app/www/public/data/meta/development/applications/polaris/pullconfiguration.meta failed
development:applications:polaris:pullconfiguration
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| development:applications:polaris:pullconfiguration [2018/05/04 14:46] – [Troubleshooting] ashevyakov | development:applications:polaris:pullconfiguration [2021/06/25 10:09] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ===== PULL SnmpManager Configuration ===== | ||
| + | Note: PULL and GET terms are used interchangeably and mean the exact same thing. | ||
| + | |||
| + | ==== General ==== | ||
| + | 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**, | ||
| + | \\ | ||
| + | \\ | ||
| + | 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 [[https:// | ||
| + | \\ | ||
| + | \\ | ||
| + | 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**). | ||
| + | |||
| + | ==== Current Configuration (ATC Production) ==== | ||
| + | === Remote File === | ||
| + | {{: | ||
| + | |||
| + | ==== Data Model ==== | ||
| + | |||
| + | === RemoteFile === | ||
| + | {{: | ||
| + | |||
| + | === RemoteFileRetrievalStrategy (Enum) === | ||
| + | {{: | ||
| + | |||
| + | === RemoteFileTransferType (Enum) === | ||
| + | {{: | ||
| + | |||
| + | === RemoteFileDiscoveryConfiguration === | ||
| + | {{: | ||
| + | ==== Troubleshooting ==== | ||
| + | * 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, | ||
Page Tools
