This site requires JavaScript to be enabled
Recent searches

Message Broker (RabbitMQ)

Learn more  about getting started in our  Documentation




  • Request Message Broker (RabbitMQ)


    Messaging enables software applications to connect and scale. Messaging is asynchronous, decoupling applications by separating sending and receiving data. The Message Broker is a common platform to send and receive messages, gives messages a safe place to live until received, and translates a message from the formal messaging protocol of the sender to the formal messaging protocol of the receiver.


    Available to:Faculty and Staff

    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


     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: 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. 


    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%

    CMP 99.9%

    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.


    Email: Send an email to 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

    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.


    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