key.txt
(See "Generating Key" below)FDS
(capitalization matters)NOTE: This container is targeting
FDSLoader64
version2.13.6.0
Environment variable control the behavior of this container.
During local development, these can are via .env
which docker-compose reads, or set as part of azure-deploy.json
for cloud deployments.
$BYPASS_LOADER
: Set to non-empty string to disable running FDSLoader (restore-only).$DEPLOY_START_TIME
: UTC timestamp used to distinguish exported datasets.$FACTSET_SERIAL
: Serial number for FactSet account, provided by FactSet.$FACTSET_USER
: Username for FactSet account, provided by FactSet.$FDS_LOADER_PATH
: Path in container to FDSLoader64
application. Default: /home/fdsrunner
.$FDS_LOADER_SOURCE_PATH
: Path in container to volume mount containing Loader zip file downloaded from FactSet and key.txt
. Default: /mnt/factset-loader
$FDS_LOADER_ZIP_FILENAME
: Name of zip file downloaded from factset. Default: FDSLoader-Linux-2.3.6.0.zip
$MACHINE_CORES
: Integer setting parallelism level for Loader application. Acceptable values: [1, 2, 4, 8, 16]
. Default: 1
$PGDATABASE
: Database name to load data into. Default FDS
$PGHOST
: Hostname for PostgreSQL server. Default: db
for local/docker, localhost
for Azure deployment.$PGPASSWORD
: Password for PostgreSQL database.$PGUSER
: Username for PostgreSQL superuser$WORKINGSPACEPATH
: Path to empy directory used for downloading data file from FactSet. This path should have available space equal to 16 Gb * $MACHINE_CORES
(suggested by FactSet documentation).$RESTORE_FILE
: filepath to backup file to use as base for restoring databaseIn the FactSet Resource Library, find the resource titled "DataFeed Loader for Linux". Note that this resource requires you to log in with your FactSet ID before downloading.
You may also find it useful to have a copy of the DataFeed Loader User Guide and DataFeed Loader resources (also require login before downloading)
Create key at: https://auth-setup.factset.com/
and copy contents to key.txt
in the same directory as the FDSLoader64
executable.
Example:
KeyId: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Counter: 0000000000000000001
Place key.txt
in the same directory as the FDSLoader64
executable.
# login to docker registry
az acr login -n transitionmonitordockerregistry
# build image
docker build . -t transitionmonitordockerregistry.azurecr.io/factset_data_loader
# push to registry
docker push transitionmonitordockerregistry.azurecr.io/factset_data_loader:latest
# replace these values with storage account name and resource group appropriate to your deployment
ACI_PERS_STORAGE_ACCOUNT_NAME="pactadata"
ACI_PERS_RESOURCE_GROUP="pacta-data"
STORAGE_KEY=$(az storage account keys list --resource-group "$ACI_PERS_RESOURCE_GROUP" --account-name "$ACI_PERS_STORAGE_ACCOUNT_NAME" --query "[0].value" --output tsv)
echo "$STORAGE_KEY"
# change this value as needed.
RESOURCEGROUP="myResourceGroup"
# run from repo root
az deployment group create --resource-group "$RESOURCEGROUP" --template-file azure-deploy.json --parameters @azure-deploy.parameters.json
az container logs --resource-group "$RESOURCEGROUP" --name <CONTAINER GROUP NAME> --container-name loader-runner --follow
az container exec --name "<CONTAINER GROUP NAME>" --container-name loader-runner --resource-group $RESOURCEGROUP --exec-command "/bin/bash"
To start a long-running process (to allow for attaching and debugging), add this to properties
for the container:
"command": [
"tail", "-f", "/dev/null"
]