Page tree
Skip to end of metadata
Go to start of metadata
Steps to Deploy a Production Instance of USAS/USPS
  1. First, follow the steps in Upload a Local Docker Backup to the MCOECN to get a backup of your district data to the MCOECN. When the Service Broker task below runs, it will find your backup by IRN and restore it to the new application.
  2. Log into https://cloud.managementcouncil.org and go to Service Broker

  3. Find the "USxS-RunAsProd" catalog item, and click Request to run it.
  4. Fill out the form.  

    ITC Name will be filled in for you (unless you manage Redesign for other ITCs as well, if so, choose the ITC under the Project dropdown).

    Select USAS or USPS.

    Choose which district to create USAS/USPS for from the District Name drop-down.

  5. Click the button to run the task.   The USxS-RunAsProd item will:
    1. Find your backup file by the IRN
    2. Automatically create a new instance of USAS/USPS/INVENTORY/WORKFLOWS
    3. Will restore your backup into it
    4. Will email you a notice when the task is complete (takes about 10 minutes or less).

  6. Run reports, do what you need to do to verify that everything looks good.  When you are ready to "go live",  you will run the VRA "Mark As Live" option 
    to flag this deployment as "live".   

    This protects the deployment from being overwritten by running another "USxS-RunAsProd" over top of it.
    It also adds the USAS/USPS deployment to the MCOECN Automated nightly backups.

  7.  If you have Kiosk integrated with USPS, you must update your OLD SOAP service URL to be the new "ssdt-ohio.org" URL.
  8.  AND if the district has OTHER 3rd-party apps that integrate with SOAP, you must update those URLs as well.



    You can run USxS-RunAsProd for a district as many times as you need to, until you run "Mark as Live" on that district's USAS/USPS application. 

    After that, running USxS-RunAsProd will fail....it will not overwrite a LIVE district.

  • No labels