Integration Infrastructure (iHub)

Document Operations
The process begins when you fill out the API Operational Readiness form, which provides all the information required to build, deploy, and support your API on our infrastructure. Completing the form creates a ServiceNow ticket, which we'll use to communicate with each other until Jira issues are created (see below).

Schedule Deployment
We prefer deployments to be scheduled for weekday evenings, 5-7pm, but actual times are negotiable depending on your needs. If the need for an emergency redeployment arises, you should contact us via Slack. We'll respond within one hour during business hours and within two hours otherwise.

We schedule our work using the campus Application Development Management (Jira) service. We'll add you to our deployment project, "Hub Release Management" (HSRM) and ask you to create requests there for both the UAT and Production environment deployments. For complete details on creating these requests, see the Create Jira Issues for Integration Infrastructure Deployments page.

Deploy to UAT & Verify
Once we've agreed on a schedule you should reassign the UAT Jira issue to "DSIS Release Management." We'll then change its "Fix Version/s" to an actual release (named for the Monday of the week of deployment–e.g., "WS 2026-04-02").

When the time for deployment comes, one of our DevSecOps team will "take" the Jira issue and attempt to build and deploy your code. Should problems arise, they'll work with you to resolve them, communicating through Jira comments to keep a complete record of activity. When the API has been successfully deployed in our UAT environment, you'll be informed via a comment and asked to verify it. We'll repeat these steps as needed until your API is running properly in UAT.

Deploy to Production & Verify
All deployments to production must be reviewed by the campus Change Advisory Board (CAB) during weekly meetings held Tuesdays at 3pm. To allow us to accurately represent the deployment at that meeting, you need to enter a Change Request into ServiceNow by Monday at 5pm, at least seven days prior to the planned deployment. For complete details on creating this request, see the Create a Change Request page.

We prefer that someone other than the API developer (perhaps the project's release manager) enter an explicit approval into the Prod Jira issue, e.g., "Approved to migrate to prod in release 2026-04-16." Then you can reassign it to "DSIS Release Management."

Integration Services will handle production deployment much the same as UAT, except that failures in build or deploy will require that we move back to the UAT environment to resolve issues.