Have you had experience with configuring and using the BAS ticket broker in RabbitMQ?

BAS (Business Automation Studio) is a platform for automating business processes that can use RabbitMQ as a message broker for organizing queues and message exchange. In the context of RabbitMQ, configuring a ticket broker is usually related to managing queues and message routing.

Experience with BAS in RabbitMQ includes:

• Setting up queues and exchanges for message transfer between components.
• Configuring policies and access rights for security.
• Using RabbitMQ plugins to extend functionality.

Example in C# for sending a message to a RabbitMQ queue:

var factory = new ConnectionFactory() { HostName = "localhost" };
using(var connection = factory.CreateConnection())
using(var channel = connection.CreateModel())
{
    channel.QueueDeclare(queue: "task_queue",
                         durable: true,
                         exclusive: false,
                         autoDelete: false,
                         arguments: null);

    string message = "Hello BAS via RabbitMQ!";
    var body = Encoding.UTF8.GetBytes(message);

    var properties = channel.CreateBasicProperties();
    properties.Persistent = true;

    channel.BasicPublish(exchange: "",
                         routingKey: "task_queue",
                         basicProperties: properties,
                         body: body);
    Console.WriteLine(" [x] Sent {0}", message);
}

Thus, setting up and using the BAS ticket broker in RabbitMQ boils down to proper configuration of queues and exchanges, as well as integration with the application's business logic.