Messaging system support for integrations
You can use the messaging system supported with BMC Release Process Management to push message notifications for certain events in the queue. If you are integrating with an external system (product or solution), you can configure the external system to read these message notifications and take appropriate actions. You can use this capability to trigger changes in the external system depending on the events created by BMC Release Process Management.
For the examples of XML messages pushed in the queue when the plan created event and the plan updated event occur, see the attached files.
Configurations required for using the messaging system
To use the messaging system functionality, create the messaging processor file and save it to the <RLM_HOME>/releases/<current_product_version>/RPM/script/messaging_processor folder.
The following code block provides a sample processor source code in the Ruby programming language:
require 'rubygems'
require 'torquebox'
require 'torquebox-messaging'
class MessagingProcessor < TorqueBox::Messaging::MessageProcessor
MESSAGING_PATH = '/topics/messaging/brpm_event_queue'
def initialize
puts 'initialize'
@destination = TorqueBox::Messaging::Topic.new(
MESSAGING_PATH,
host: 'localhost',
port: 5445,
username: 'msguser',
password: '<your-password>'
)
puts "Destination: #{@destination}"
end
def on_message(serialized_message)
p '==============================================='
p serialized_message
p '==============================================='
end
def run
on_message(@destination.receive)
end
end
consumer = MessagingProcessor.new
puts 'Listening...'
loop do
consumer.run
end
Note
In the processor file, ensure that values for host, port, username, and password are the same as you entered in the installer program during the BMC Release Process Management installation.
Click the image to expand.
List of events available in messaging system
Plan | Request | Run | Step | Ticket |
|---|---|---|---|---|
|
|
|
| Ticket after update |