First, you must have a backup of a local Docker production deployment that you can use to create the MCOECN Hosted deployment.
If your ITC is copying nightly backups to MCOECN for an offsite copy, you already have a backup that will be used. Proceed to Step 2.
If your ITC does NOT host with MCOECN and does not send offsite backups to MCOECN, 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 is run, it will find your backup by IRN and restore it to the new application.
Make sure you can log into https://cloud.managementcouncil.org and see Service Broker and the catalog items. If this is the first time your ITC is using MCOECN Hosting, we may need to create an MCOECN.ORG account for you, or grant access to the VRA portal to your existing account.
If you are having trouble logging into https://cloud.managementcouncil.org, you can use the Self Service website to reset your password if you have previously registered an alternative account for password recovery.
- Run the Redesign Production catalog item by clicking Request.
- 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).
- Choose the district from the District Name drop-down.
- Check the boxes next to the application(s) you wish to create.
- Click the button to run the task. The Redesign Production item will:
- Find your backup file by the IRN
- Automatically create a new deployment of USAS/USPS/INVENTORY/WORKFLOWS
- Will restore your backup into it
- Will email you a notice when the task is complete (takes about 10 minutes per application).
- APPLICATION INTEGRATION: USAS and USPS will automatically integrate with each other in the MCOECN Hosted Environment. No manually intervention is required to get USAS and USPS integrated. You do NOT need to create API Keys within the applications if you are using MCOECN hosting (doing so can actually BREAK the integration within the MCOECN hosted Kubernetes environment).
If you deploy Inventory or Workflows, API keys will be automatically generated and added to the USAS and USPS configuration files. However, you must run the catalog item Reconfig USXS to apply the Inventory/Workflows integration configuration to USAS and USPS (which will restart the applications). This part does not happen automatically. We do this because we do not want the creation of a Workflows or Inventory deployment to restart USAS/USPS outside of ITC Staff control. We do not want production applications taken down unexpectedly/accidentally during business hours.
- Do what you need to do to verify that everything looks good (run reports, compare balances, etc). When you are ready to "go live", you will run the VRA Mark As Live option
to flag each application as "live".
This protects the application from being overwritten by running another Redesign Production over top of it.
It also adds the application to the MCOECN Automated nightly backups.
- If you have Kiosk integrated with USPS, you must update your OLD SOAP service URL to be the new "ssdt-ohio.org" URL.
- If the district has OTHER 3rd-party apps that integrate with SOAP, you must update those URLs as well.
You can run Redesign Production for a district as many times as you need to, until you run Mark as Live on that district's applications.
After that, running Redesign Production on that same district's applications will fail....it will not overwrite a district application marked as "LIVE".
If you connect your local Redesign applications to your own ITC's Active Directory, you will need to allow LDAP access from the MCOECN hosted environment to your local Active Directory server(s) through your ITC firewall.
All LDAP requests from the MCOECN Hosted applications will come from source IP address :
This only needs to be completed one time per ITC.
Steps to Create a Production Deployment of USAS/USPS