This site requires JavaScript to be enabled
Welcome Guest|
Recent searches
IE BUMPER

Integration Services

Integration Services is provided by the Middleware and Common Applications group within ITS Applications. The service provides a core set of offerings which include the API (Application Programming Interface) Registry, Enterprise Service Bus (ESB), and a Message Broker.    

  • Enterprise Service Bus (ESB)

    This Enterprise Service Bus offering combines real-time application integration and orchestration with robust data integration capabilities. This service is provided by the vendor MuleSoft.

    Available to:Faculty and Staff
    Features

    Alerts: CloudHub Alerts (email, UI)

    Data Transformation: The conversion of data from one format to another.

    Data Transport: Movement of data or information from one system to another, via transport protocols http, https, ftp, sftp, queues, pub/sub, topics, routing, JMS, AMQP

    Development Tooling: Access to Anypoint Studio Enterprise Edition

    Monitoring: CloudHub Application Management UI, Anypoint API Analytics

    SAML Authentication: Shibboleth SAML Authentication for CloudHub Console

    Orchestration: Ability to create composite services

    Protocol Mediation: Receiving data with one transport protocol and dispatching it with another.

    Rate Limiting: Ability to set a limit on the number of transactions processed in a certain time frame. Transaction over the limit within the specified time frame are discarded.

    SaaS Integration: Examples: Workday, SalesForce, ServiceNow, JIRA

    API Authentication/Authorization: Ability to automatically apply authn/authz policies to the API 

    Throttling: Ability to set a limit on the number of transactions processed in a certain time frame. Transactions over the limit within the specified time frame are queued for later processing, but not discarded.

    Optional - Guaranteed Delivery: Ability to deliver data to another system once, and only once, and if in multiple parts, in order.

    Optional - Outage Notification: Programmatic notifications of service outages (ex: via messaging)

    Optional - High Availability: If required, horizontal or vertical scaling of workers can be done automatically.

    Optional- UT-based  Authentication/Authorization: Use of a UT EID as  service account to verify permissions for the API.

    Optional - Self-Administration: Ability to administer services on the Integration Platform (e.g. ESB, Gateway, or Message Broker)

    Cloudhub Non-Prod Environment: Environment to support API development

    Optional - VPN Support: Connectivity to on premise resources.

    Optional - Data Caching: The Cache Scope saves on time and processing load by storing and reusing frequently called data.

     

    Unit of Measure

     The unit of measurement is vCore. vCore is defined as the compute power in cloud in terms of memory and processor.

    Cost

     This service and its offerings are provided as Common Good.

    Service Level Objectives

    Fulfillment time    

    Fulfillment time is the estimated time taken to fulfill the customer requests that both provider and consumer will use to track progress.

    Consumer Requests Areas:

    CloudHub Development

    Access to Development Environment

    vCore Assignment

    Removal of Access

    Consumer request will be fulfilled within 48 business hours.

    Hours of Coverage

    Hours of coverage defines the hours of operation during which support services are available to address any consumer request regarding this environment. 

    Consumer Requests:

    Normal hours of operation are 8:00 a.m. to 5:00 p.m., Monday – Friday except University holidays, and announced University closures.

    Customers should open a ticket by clicking here.

    Regular requests can be submitted 24 hours a day, 7 days a week. After hours, requests submitted will be processed during the next business day.

    Requests for off-hours work must be scheduled a week in advance.

    Guaranteed Service Availability

    Guaranteed service availability defines the percentage of time this offering is guaranteed to be in available for this environment, with the exception of scheduled maintenance, and within service availability hours.

    Service availability hours:

    Core Network – 99.98%

    Internet/External Connectivity – 99.95%

    UDCC Network Core – 99.98%

    UDCC Network Edge – 99.98%

    Shibboleth – 98.9%

    VPN – 99.7%

    CloudHub(vendor) - at 99.99%

    Based on the lowest i.e. Shibboleth at 98.9%,  CloudHub(vendor) at 99.99%,  the SLA for ESB  is 98.9% x 99.99% = 98.89%

    These Services depend on Vendor’s SLA and the underpinning services listed above.

    Service Requests  

    A Service Request means any request made by a consumer to the Service Provider team for routine operational support. To make a Service request, the consumer must create a ticket in the ITS Help Desk ticketing system.         

    How to Submit a Service Request:

    Please submit a new request by clicking here.  

    For escalation send email with reference to the open ticket at integration-stewards@utlists.utexas.edu.

    Incident Reporting

    An Incident means any interruption of the normal function of the integration service where it is severely malfunctioning.       

    Types to Incidents:

    Production - During normal business hours, Incidents will be responded to within 30 minutes after notification to Service Provider team. Off business hours, Incidents will be responded to within 45 minutes after notification to the Integration Service Team.

    Development, Qual - Incidents will be responded to within 24 hours.

    Escalation

    If an Incident is not responded to within the response times outlined above, the Customer may escalate by directly contacting the Service Provider contact. 

  • Message Broker (RabbitMQ)

    Message Broker provides a messaging platform that allows users to send and receive messages programmatically in response to events. 

    Available to:Faculty and Staff
    Features

    Broadcast publications: Ability to send data to multiple recipients at once 

    Broadcast subscriptions: Message Broker Ability to subscribe to data from multiple senders 

    Polyglot client support: Clients available for Java and Python, Ruby, Go, PHP, Perl, C and many other languages. 

    Data Transport: Movement of data or information from one system to another via transport protocol AMQP with the broker as an in-between. 

    Monitoring:  RabbitMQ Management Console

    Optional - High Availability: Replication across multiple instances. If a node becomes unavailable due to failure or planned downtime, another node in the cluster can assume the workload and continue to process existing events and messages. 

    UT Authentication: Use of a UT EID as a service account to verify identity

    UT-based Authorization: Use of a UT EID as a service account to verify permissions

    Optional - Self-Administration: Ability to administer services on  Message Broker

    Cost

     This service and its offerings are provided as Common Good.

    Service Level Objectives

    Fulfillment time    

    Fulfillment time is the estimated time taken to fulfill the customer requests that both provider and consumer will use to track progress.

    Measurement:

    Consumer Requests: Measurement

    Access Request: Consumer request will be fulfilled within 48 business hours

    Removal of Access: Consumer request will be fulfilled within 48 business hours 

    Hours of Coverage

    Hours of coverage defines the hours of operation during which support services are available to address any consumer request regarding this environment. 

    Measurement:

    Normal hours of operation are 8:00 a.m. to 5:00 p.m., Monday – Friday except University holidays, and announced University closures.

    Customers should click here  to open a ticket.

    Regular requests can be submitted 24 hours a day, 7 days a week. After hours, requests submitted will be processed during the next business day.

    Requests for off-hours work must be scheduled a week in advance.

    Guaranteed Service Availability

    Guaranteed service availability defines the percentage of time this offering is guaranteed to be in available for this environment, with the exception of scheduled maintenance, and within service availability hours.

    Message Broker is dependent on the below services in calculating its SLA:

    Core Network – 99.98%

    Internet/External Connectivity – 99.95%

    UDCC Network Core – 99.98%

    UDCC Network Edge – 99.98%

    uTexas Enterprise Directory – 98.9%

    UT-V Enterprise - 99.90%

    PYPE – 98.76%

    Based on the lowest, the SLA for Message Broker is 98.76%

    Service availability hours: Non-production 8:00am to 5:00 pm, Monday-Friday except University holidays and announced University closures

    Service Requests

    A Service Request means any request made by a consumer to the Service Provider team for routine operational support. To make a Service request, the consumer must create a ticket in the UT Service Desk ticketing system.

    Wiki: https://wikis.utexas.edu/display/middleware/Message+Broker-+RabbitMQ 

    Email: Send an email to integration-requests@utlists.utexas.edu. This email will generate a ticket that will be assigned to the Service Provider team.

    Online: Submit a ticket through the UT Service Desk at https://www.utexas.edu/its/helpdesk/forms/emailform.php.

    Phone: Call 512-475-9400 to contact the UT Service Desk.

    Incident Reporting
    An Incident means any interruption of the normal function of the database service where it is severely malfunctioning.       

    Production: During normal business hours, Incidents will be responded to within 30 minutes after notification to Service Provider team. Off business hours, Incidents will be responded to within 45 minutes after notification to the Integration Services team.

    Test: Incidents will be responded to within a week after notification to Service Provider team.

    Escalation   

    If an Incident is not responded to within the response times outlined above, the Customer may escalate by directly contacting the Service Provider contact. 

    Email: send email to integration-stewards@utlists.utexas.edu

  • MuleSoft API Registry

    This online catalog and portal combination allows registering or searching for connectors, templates, APIs, and examples shared within the enterprise.

    Available to:Faculty and Staff
    Features

    Service Registration: Ability to list an API in a central location that is available to the campus community

    Service Discovery: Ability for the community to find existing registered APIs

    UT Authentication Single Sign-On: UT Authentication Single Sign-On ability to sign on using existing EID/password

    Cost

     This service and its offerings are provided as Common Good.

    Service Level Objectives

    Fulfillment time    

    Fulfillment time is the estimated time taken to fulfill the customer requests that both provider and consumer will use to track progress.

    Measurement:

    Consumer Requests: Measurement

    Access Request: Consumer request will be fulfilled within 48 business hours

    Removal of Access: Consumer request will be fulfilled within 48 business hours 

    Hours of Coverage

    Hours of coverage defines the hours of operation during which support services are available to address any consumer request regarding this environment. 

    Measurement:

    Normal hours of operation are 8:00 a.m. to 5:00 p.m., Monday – Friday except University holidays, and announced University closures.

    Customers should click here to open a ticket.

    Regular requests can be submitted 24 hours a day, 7 days a week. After hours, requests submitted will be processed during the next business day.

    Requests for off-hours work must be scheduled a week in advance.

    Guaranteed Service Availability

    Guaranteed service availability defines the percentage of time this offering is guaranteed to be in available for this environment, with the exception of scheduled maintenance, and within service availability hours.

     

    Service availability hours: This is a hosted, internet based SaaS solution. Availability is dependent on the Vendor’s SLA and underpinning services:

    Core Network – 99.98%

    Internet/External Connectivity – 99.95%

    UDCC Network Core – 99.98%

    UDCC Network Edge – 99.98%

    Shibboleth – 98.9%

    CloudHub(vendor) - at 99.99%

    Based on the lowest i.e. Shibboleth at 98.9%, CloudHub(vendor) at 99.99%, the SLA for API Registry is 98.9% x 99.99% = 98.89%

    Service Requests

    A Service Request means any request made by a consumer to the Service Provider team for routine operational support. To make a Service request, the consumer must create a ticket in the UT Service Desk ticketing system by clicking here. Other ways to create ticket are:

    Online: Submit a ticket through the UT Service Desk at https://www.utexas.edu/its/helpdesk/forms/emailform.php.

    Phone: Call 512-475-9400 to contact the UT Service Desk.

    Incident Reporting
    An Incident means any interruption of the normal function of the database service where it is severely malfunctioning.       

    Production: During normal business hours, Incidents will be responded to within 30 minutes after notification to Service Provider team. Off business hours, Incidents will be responded to within 45 minutes after notification to the Integration Services team.

    Escalation   

    If an Incident is not responded to within the response times outlined above, the Customer may escalate by directly contacting the Service Provider contact. 

    Email: send email to integration-stewards@utlists.utexas.edu