Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

This article explains how to execute the importers from the docker host.


You must have:

  • SSDT Utils package installed and up-to-date
  • the district's compose project must be configured for USAS, USPS or both
  • Exports of USAS / USPS
  • If you have previously imported into this project, you might want to delete any existing data and volumes so there are no remaining components.  THIS IS DESTRUCTIVE and will remove all components for the project, so use with extreme caution and make sure you are in the correct project directory.

    ###To delete all (both usas and usps):
    docker-compose down -v
    ###If it's just one (in this example usas):
    docker-compose stop usasapp
    docker-compose stop usasdb
    docker-compose rm usasapp (answer Y)
    docker-compose rm usasdb (answer Y)
    docker volume ls ##(to make sure of the volume name)
    docker volume rm xxxx_usasdb_1

Step-by-step guide

The import scripts below are destructive. When executed, the existing database for the project will be deleted. All information stored in the database will be deleted this includes all data, custom configuration options, installed modules etc.  You must not run these scripts in a district which already has data loaded, unless you intend to replace it.

  1. Navigate to the district's project to run the import
  2. The import scripts require environment variables to define the source and IRN to be imported.  You can use the same values for both USAS and USPS, if the files are in the same location.  Define the following environment variables as follows: 

    export IMP_IRN=999999
    export IMP_URL=
    export IMP_PATH=[.directory] 
  3. To import USAS, do: 


    If you prefer to execute the script in the background then:

    nohup /ssdt/prod/ &
  4. To import USPS, do: 


    If you prefer to execute the script in the background then:

    nohup /ssdt/prod/ &


The import scripts assume that the district has been configured with the script from /ssdt/prod.  The scripts do the following:

  • will automatically stop and remove any existing database and app containers for the district
  • create a new database container
  • launch the import utility.  This creates a temporary container for the importer and attaches to the database container.  The import process runs in the foreground and will tie up the console until completed
  • after completion, the temporary import container is removed and the app container started

After completion, the directory will contain log file(s) containing the entire import process.  You should review the logs to ensure successful complete and for errors which may need to be reviewed. 

After the import completes, it can time a while before the instance is up (the first time only).  There are adjustments being made and patches applied. Do NOT assume the instance is hung and restart the application; this can cause delays or issues.  Monitor the usxsapp logs while the patches are applying if errors are suspected.

Examples of typical USAS import errors

Examples of typical USPS import errors

Requesting SSDT Assistance Troubleshooting Errors

If the ITC and district cannot resolve import related errors, ITC staff can open a support request with the SSDT. Import logs can be securely transferred to the SSDT using the method described in Securely Send Files to SSDT for Support.

Post Import Recommendations

We recommend you immediately execute a backup after completing the import process. From the district's project directory do:

> /ssdt/scripts/

You will also want to review the post import procedures outlined for both USAS and USPS.  These documents can be found the in Appendix section of the online documentation.

  • No labels