Boomi Logo

In this tutorial, you will learn how to configure and use the Solace Boomi connector. This is done in 4 easy steps

  1. Configure your Solace PubSub+ Event Broker (Hardware, Software, SasS)
  2. Setup your Boomi AtomSphere
  3. Configure the Solace connector in the Boomi AtomSphere
  4. Send/Receive messages between Boomi and Solace

Prerequisite

This tutorial assumes:

Access to a Solace messaging service, Solace PubSub+, can be achieved in either one of the three flavours

  1. Hardware Appliance
  2. Software broker image (Docker, Virtual image)
  3. Solace Cloud service instance

This tutorial will walk you through setting up a Solace Cloud service instance. If you are interested in setting up a local broker running on Docker or a virtual machine check out the PubSub+ Event Broker: Software documentation

Sign up for free Solace Cloud account

Navigate to the Create a New Account page and fill out the required information. No credit card required!

Create a messaging service

After you create your Solace Cloud account and sign in to the Solace Cloud Console, you'll be routed to the event mesh page.

Solace Cloud Event Mesh Page

Click on β€˜Messaging Services' and all the messaging services associated with your account will show up if you have any already created. To create a new service, click either button as depicted in the image below:

Solace Cloud Landing Page

Fill out all the details for your messaging service, and then click "Create" at the bottom of the page.

Create Solace Cloud Messaging Service

Your service should be ready to use in a couple seconds! πŸŒͺ

Core concepts

Boomi builds, deploys and manage all the processes in a concept called Atoms, which is a lightweight Java application that is deployed on a host with Internet access. Think of it as your single-tenant, single-node runtime engine. There are two deployment models for Atoms:

  1. In-the-cloud deployment (using Boomi Atom Cloud)
  2. On-premise deployment (using local Atom setup)

Atom gif

4 Steps to get started with Boomi

1. Create a Boomi trial account

if you dont have an account, navigate to https://boomi.com/form/trial/ and sign up for a free account.

After you sign up for a Boomi platform account and login, you will have access to the Boomi AtomSphere - your one stop shop for all your integrations πŸ€“

AtomSphere

You will see the menu at the top

menu

2. Configure and deploy your local Atom

In this tutorial, we will be setting up a local Atom.

You can either navigate to the links below for more information or follow the steps after

  1. Windows Machine.
  2. Using Docker.

πŸ‘‰ Navigate to the Manage tab and click on Atom Management

manage

πŸ‘‰ Click on +New and choose Atom

new-atom

πŸ‘‰ Choose the operating system of choice in the Atom Setup box

atom-setup

πŸ“ Notes on Docker installation

The installer is a shell script that you run locally and automatically configure your docker setup

  1. ./atomdocker_install64.sh -h for more information on how to run it
  2. You can generate a token by clicking on Generate Token under Security Options
  3. Create a /var/boomi directory because the script assumes it already exists and make sure its owned by the current user
    1. Navigate to /var/boomi/ after you create it
    2. Execute the following from terminal chown $USER .
    3. Make sure this directory is shared on docker. This is done by opening the docker preferences and adding it under File Sharing Resources tab

docker-menudocker-sharing

πŸƒβ€β™‚οΈ Run the atom

Execute the atom docker installation shell script as follows
./atomdocker_install64.sh -n <name_of_atom> -k <insert_token>

At this point, you can confirm that the Atom has been created and linked to your AtomSphere when you navigate to the Atom Management in the Manage tab and you will see your newly created atom under the Unattached Atoms section

unattached-atom

3. Setup Boomi environment

Boomi Environments are synonymous to workspaces thats used for testing or production purposes. You need an environment to "attach" the atom to. You can read more about Boomi Environments on the Environment Management Boomi User Guide

Under the Manage menu, navigate to the Atom management and add a new environment env-menu

Give it a name and choose Test for the environment classification env-setup

4. Attach the Atom to the environment

Select your newly created environment and search for your atom to attach it env-wiz

πŸŽ‰ Viola! Now you have your Solace and Boomi environments setup

Let's assume that you want to collect real-time events from Taxi's in NYC and stream them over a Solace Broker into your Boomi architecture and applications. These events could represent anything from ride status analytics to payment methods.

We will first need to configure a queue so that the Solace PubSub+ connector on the Boomi AtomSphere can bind to and listen to any incoming messages on a given topic.

πŸ‘‰ Navigate to the Solace Cloud console Messaging Service tab

messaging-service

πŸ‘‰ Click on the previously created service from step 2 and navigate to the Manage Service option

solace-service

πŸ‘‰ Now you are in the PubSub+ management console. Navigate to the Queue section from the left hand side panel and click on the + Queue button to create a new queue. Name the queue taxi

queue

πŸ‘‰ After creating the new queue, click on it and navigate to the Subscriptions tab. Add a new subscription to the topic taxi/nyc/v1/dropoff/>

queue-sub

Now back to the Boomi AtomSphere!

1. Create a new Boomi component

πŸ‘‰ Click on the New button to create a new component

AtomSphere2

πŸ‘‰ Make sure the Type is Process. Give it a name and folder to be saved in

component

canvas

2.. Configure Solace Shape

πŸ‘‰ Hover over the Start shape to configure it

canvas-start

πŸ‘‰ Configure the Start shape to be a Solace PubSub+ Connector with the a Listen action as seen in the screenshot below

connector-config

A. Configure Connection

πŸ‘‰ In the Connection section, click on the + icon to configure the connection parameters

connector-connection

πŸ‘‰ Fill in the connection parameters with the Host, Message VPN Name, Client Username and Password. This is obtained by navigating back to the Solace Cloud console, clicking on the previously created service and navigating to the Connect tab. Note that you will have to expand the "Solace Messaging" menu to get the connection details

connection-service

πŸ‘‰ Test the connection, by clicking on the Test Connection button. Note: Choose your Atom here

testconnection

success-connection

B. Configure Operation

Back to the Start Shape configuration, click on the + icon for the Operation section to configure the operation parameters as seen in the screenshot below

Mode: Persistent Transacted
Destination: taxi <– (thats the name of the queue we previously configured on the Solace Pubsub+ broker!)
Batch Size: 1

operation-options

Save and close!

Now your Canvas should look like this with the newly added shape

canvas1

3. Add a Notify shape

In order to test out the end to end connection and make sure that the events sent from the Solace PubSub+ broker are being received by the Solace Boomi Connector, we want to add a way to log the events received. To do so, lets go ahead and add a Notify shape

πŸ‘‰ Search for and drag the notify shape into the canvas

notify-search

πŸ‘‰ Configure the Notify shape to log the payload received from the message sent

notify-config

Note that {1} in the Boomi context means variables. Click on the + icon to add a new variable and choose the type to be Current Data

notify-vars

4. Connect the Solace PubSub+ Listener to the Notify Shape

boomi-connect

stop

Save the process flow!

To connect everything together, we will need to package the newly created process flow and deploy it on the locally running Atom

arch

Package and Deploy the Process

πŸ‘‰ Click on the Create Package button

package

πŸ‘‰ The newly created component will be automatically selected by default

πŸ‘‰ Click Next to add details. No need to add any more details

πŸ‘‰ Click create package and you will see this notification

package-success

Deploy the packaged process on the running atom

πŸ‘‰ Click on the Deploy button and choose the Environment that you created previously

πŸ‘‰ Click Next until you get to the Review Deploy step

πŸ‘‰ Click on the Deploy button!

deploy-success

Publish events πŸ’₯!

πŸ‘‰ Navigate back to your Solace Cloud console, select the messaging service and navigate to the Try Me! tab

tryme

πŸ‘‰ In the Publisher section, click on the Connect button, change the topic to be taxi/nyc/v1/dropoff/rideX (since we have our queue subscribing to this topic, remember!) and update the message body to whatever you want

publisher-connect

πŸ‘‰ Smash that Publish button.

Check out the logs

πŸ‘‰ From the Boomi AtomSphere, navigate to the Process Reporting section under the Manage tab

process-reporting

You will see the process reporting menu with your newly created NewProcess process. Note that you can click on the refresh icon reporting-menu

πŸ‘‰ Click on the view process logs icon

logslogs2logs3

You're done!

βœ… Sign up for a Solace PubSub+ Cloud account and configure a messaging service broker with a queue
βœ… Sign up for a Boomi AtomSphere account and setup a Solace Pubsub+ Connector for a listen configuration and bind to a message queue
βœ… Send events to the same topic the queue is subscribed to

Soly wave

Thanks for participating in this codelab! Let us know what you thought in the Solace Community Forum!