MIT Progress Adapter for Fuse

Copyright (c) 2009 Flusso B.V.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in

Change log for the Progress Adapter for Fuse


  • ????????
    • Logging more flexible (undocumented).
    • No more default output for log messages using LOG-MANAGER.
    • Tests modified to produce same output as in previous release.
  • 20090423
    • Initial public release.









Using the Progress Adapter for Fuse Message Broker

Using the OpenEdge Adapter for Fuse Message Broker

Getting started


  • The message broker must be running. If the broker requires authentication
    you must know a user name and password.
  • The STOMP listener must be accessible over the network. You must know the
    host name and port number.
  • The directory stompAdapter from the adapter code distribution must be in
    the PROPATH.

Defining the connection with the broker

Progress Fuse Adapter Documentation

OpenEdge Adapter for Fuse Message Broker


The OpenEdge Adapter for Fuse Message Broker enables connections from an
OpenEdge™ ABL application to Fuse™ Message Broker or Apache ActiveMQ (or
other messaging solution as described below). It consists of a number of ABL
classes that should be referenced in an ABL application that needs to exchange
messages with the outside world using one of the supported world class
messaging solutions.

Progress Fuse Adapter Project

Progress Fuse Adapter
Written in OO ABL and supports the stomp protocol.
Code comments in Dutch


  • Using the adapter
  • API details
  • Change log

  • Syndicate content