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

Requirements:

You must have:

Step-by-step guide

The import scripts below are destructive.  Information stored in the database will be deleted including 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.  Please note, if you are importing a district's data again, you need to follow the steps outlined in the above Requirements section in order to ensure a clean import.

  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=ftp://username:password@vmsserver.example.org/
    export IMP_PATH=[.directory] 


  3. To import USAS, do: 

    /ssdt/prod/import-usas.sh

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

    nohup /ssdt/prod/import-usas.sh &


  4. To import USPS, do: 

    /ssdt/prod/import-usps.sh

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

    nohup /ssdt/prod/import-usps.sh &


Explanation

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

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/backup-usas.sh

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.


Related articles



Related issues