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

API Registry (MuleSoft)

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

 

 

  • Request API Registry (MuleSoft)

    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