Getting Started

MessageBroker - Getting Started

 

Understand the concept

MessageBroker - Understand the Concept

MessageBroker has a defined set of actions called Routes which basically receives input from the Producer and producing some output for the Consumer. The Producer or Consumer needs to know on what basis the data is coming in or going out by defining the actions provided by the Connectors.

In MessageBroker, a message may be handled by multiple Routes. For example, we use the first Route to get data input and then transform the output using XSLT technologies. Afterwards, we redirect the result to the second Route to store it.

MessageBroker - Understand the Concept - Endpoint

Endpoint is a defined action that takes place in the beginning or the end of a Route. This action is taken from the Connectors installed in MessageBroker.

In certain cases, Endpoint requires credential information in order to connect to the system the connector allows us to connect to.

MessageBroker - Understand the Concept - Route

A Route is fundamentally what the MessageBroker is capable of.

Each route has to be considered like a transportation route that has a beginning and an end. In this case, the Producer delivers the data (message), while we have the Consumer handling the data at the end.

Route can also point to another route for sequential steps. Here the Consumer of the first route will be the Producer of the second route and so on.
Each route can also define a transformation process. This is needed when the format of the message from the Producer is different than the Consumer’s, and therefore has to be transformed.

MessageBroker - Understand the Concept - Message

Message is what the Producer delivers to the Consumer. In the case of multiple routes, the message is what the first Producer delivers that will eventually ends up at the last Consumer.

A message may have some transformations along the way before it gets to the Consumer.

MessageBroker - Understand the Concept - Receiver

Every process has a starting point. This can be a system or IBS MessageScheduler. The first message sent from this starting point is directed to Receiver - a MessageBroker’s agent that controls the steps within a route and the flows between each route.

MessageBroker Receiver runs as a server listening for incoming messages to be dispatched to routes.

MessageBroker Receiver can receive a message with different protocols: HTTP XML Post, Web service, and REST.

MessageBroker - Understand the Concept - Scheduler

Scheduler is beneficial when your message sender (can be any external system) does not have the ability to push the message to MessageBroker. In this case, we can instead pull the data to MessageBroker using a scheduler by defining which message to be sent, the target URL and the time interval setting.

 

Install MessageBroker Core

MessageBroker - Getting Started - Install MessageBroker Core

Installing a MessageBroker Core is as simple as downloading the setup files for free from this page: MessageBroker Core and install it to your server following the steps on this page: Install MessageBroker.

 

Install MessageBroker Connector

MessageBroker - Getting Started - Install MessageBroker Connector

After you have successfully installed MessageBroker Core, you need to install the corresponding connector for your systems. Find the connector you need on the Connector Hub page.

To install your connector please refer to: Install MessageBroker Connector.

 

Test Connector

MessageBroker - Getting Started - Test MessageBroker Connector

If you have completed the above steps, that means you are ready to run a test on your MessageBroker installation. However, please do check the following points first:

  • Do you have access to the MessageBroker Admin Page?
  • In the Admin Page, go to the System Information-menu. Can you see the installed connectors here?

We recommend that you also download and install the WebPlugin connector for running this test. Afterwards please go to this page: Test your connector(coming soon) and follow the described steps.

 

Build Scenario

MessageBroker - Getting Started - Build Scenario

Congratulations! Now you can start connecting systems with MessageBroker.

We always recommend people to first build a scenario, how they want their system to interact with their target system. From this scenario, they get a rough idea on how to set up MessageBroker for their uses. The scenario includes the following elements:

  • How many routes you should create
  • Whether it’s a continuous or an independent route
  • What message you need to generate
  • Whether you need to transform the message

The questions above and perhaps some other questions can be answered by analyzing the scenario. We trust that this will make your integration steps easier.

 

FAQ and Support

You can find the frequently asked questions on this page: FAQ. But if you have more questions please feel free to contact us through our Q&A platform and our developer team will be ready to help you with your questions there.

About MessageBroker

Easy and cost-efficient approach for system integration. With our MessageBroker-Core and lots of flexible connectors, you can start integrating your systems today.

Didn't find the Connector you were looking for? Request or create one yourself using the provided Connector API.

Latest Systems

Web SystemMay 29, 2015
Survey SystemMay 29, 2015
Operating SystemOctober 16, 2015
Groupware SystemMay 29, 2015
ERP SystemMay 29, 2015
CRM SystemsMay 29, 2015

Get in touch

Schwarzwaldstr. 122
60528 Frankfurt am Main
Germany

Ferdinand-Porsche-Straße 11
60386 Frankfurt am Main
Germany

mb@message-broker.com

Connect with us

Log in

Create an account

Register