Boomi Service Offering at UConn

ITS offers sub-accounts in Boomi for project teams to develop, deploy and schedule integrations. Boomi lives on managed servers running Red Hat Enterprise Linux (RHEL) in the Math-Science Building Data Center at UConn. There are three production integration nodes, two production gateway nodes for API publishing, three test integration nodes, and two test gateway nodes. There is also an SFTP server.

The following information describes the individual and shared responsibilities the Enterprise Systems support team and project teams will have regarding sub-accounts.

Enterprise Systems

All sub-accounts are centrally managed by the Enterprise Systems support team that will:

  • Monitor the health of the clusters.

  • Maintain firewall rules.

  • Monitor the components with cost impact.

  • Promote best practice for Boomi SDLC.

  • Facilitate activities with Boomi that are outside the default customer support framework.

  • Assist with using Boomi for specific UConn systems and use cases.

  • Publish the Knowledge Base framework and SharePoint for Admins.

  • Keep the OS and other system-level components up to date with the latest and most secure versions.

Individual Project Teams

Within their sub-accounts, individual project teams must:

  • Complete the recommended Boomi trainings.

  • Define and enforce project team standards related to security, documentation and organization.

  • Manage users, roles and project team access.

  • Develop documentation specific to the given project team.

  • Build individual processes and APIs for the project team.

  • Monitor the health and reliability of project team processes.

  • Refer to the Boomi Knowledge Base for UConn-agnostic issues.

Shared Responsibilities

The Enterprise Systems support team and individual project teams both are accountable for:

  • Responsible pattern implementations.

  • Single, standardized data endpoint delivery.

  • Responsible use of the platform and interactions with Boomi staff.

  • A supportive integration community.

  • Awareness of cost considerations.

  • Sustainable design.

  • A comprehensive Knowledge Base.

Related Articles