The Advanced Message Queuing Protocol (AMQP) is an open standard application layer protocol for message-oriented middleware, and Solace PubSub+ Message Brokers support AMQP 1.0.
In addition to information provided on the Solace Developer Portal, you may also look at external sources for more details about AMQP:
- http://www.amqp.org
- https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=amqp
- http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf
The "Getting Started" Samples will get you up to speed and sending messages with Solace technology as quickly as possible. There are four ways you can get started:
- Follow these instructions to quickly spin up a cloud-based Solace messaging service for your applications.
- Follow these instructions to start the Solace PubSub+ software message broker in leading Clouds, Container Platforms or Hypervisors. The tutorials outline where to download and how to install the Solace PubSub+ software message broker.
- If your company has Solace PubSub+ appliances deployed, contact your middleware team to obtain the host name or IP address of a Solace PubSub+ appliance to test against, a username and password to access it, and a VPN in which you can produce and consume messages.
- Pull the solace-pubsub-standard docker image from Docker Hub repository.
This repository contains sample code for the following scenarios:
- Publish to a Queue, see send
- Receive from a Queue, see receive
- Publish on a Topic using address prefix, see producer
- Receive from Durable Topic Endpoint using address prefix, see dte_solconsumer
- Receive from Durable Topic Endpoint using address prefix and terminus durability fields, see dte_consumer
Note AMQP address prefixes are not supported until Solace PubSub+ software message broker version 8.11.0 and Solace PubSub+ appliance version 8.5.0.
There are two environments for the Samples.
Must have docker version 18 or later installed and available. Must have bash shell script environment.
Must have the Apache Qpid Proton C library version 0.23 or later. Must have make, and gcc tools available to use makefile.
Check out the images folder in the docker-qpid-proton project for how the docker container built the Apache qpid Proton environment. For building on platforms not supported by the docker-qpid-proton project check out the Apache Qpid Proton project.
Building and Running in a Docker Container tailored to getting started with Apache Qpid Proton C quickly.
Just clone and make. For example:
- clone this GitHub repository
./env.sh make
All executables are built using the docker container and place on the local host machine under src/bin.
Take a look at ./env.sh make help for more details about make targets.
To try individual examples, build the project from source and then run them like the following:
./env.sh run send -a <msg_backbone_ip> -p <port>
Note: the env.sh run <example_executable> for
senddoes not have a path. All executables undersrc/bincan be run in the docker container using theenv.sh runcommand. Look atenv.sh helpfor details.
Just clone and make. For example:
- clone this GitHub repository
make -f src/makefile
All executables are built to the src/bin directory.
To try individual examples, build the project from source and then run them like the following:
./src/bin/send -a <msg_backbone_ip> -p <port>
Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.
See the list of contributors who participated in this project.
This project is licensed under the Apache License, Version 2.0. - See the LICENSE file for details.
For more information try these resources:
- The Solace Developer Portal website at: http://dev.solace.com
- Get a better understanding of Solace technology.
- Check out the Solace blog for other interesting discussions around Solace technology
- Ask the Solace community.