Deploy either a standalone Solace Message Router or a three node High Availability cluster of Solace Message Routers onto Azure Linux VM(s).
The Solace Virtual Message Router (VMR) is enterprise-grade messaging middleware that meets the needs of big data, cloud migration, and internet of things initiatives, and enables microservices and event-driven architecture. Capabilities include topic-based publish/subscribe, request/reply, message queues/queueing, and data streaming for IoT devices and mobile/web apps. The VMR supports open APIs and standard protocols including AMQP, JMS, MQTT, REST, and WebSocket. The VMR can be deployed in on-premise datacenters, natively within private and public clouds, and across complex hybrid cloud environments.
VMRs can either be deployed as a 3 node HA cluster or a single node. For simple test environments that need to validate application functionality, a single instance will suffice.
Note that in production or any environment where message loss can not be tolerated, an HA cluster is required.
This is a 2 step process:
- Go to the Solace Developer portal and request a Solace Community edition VMR or Evaluation edition VMR. This process will return an email with a Download link. Do a right click "Copy Hyperlink" on the "Download the VMR for Docker" hyperlink. This URL link will be needed in the following section. The link below will take you to the correct version of the VMR you require depending on whether you want a single instance or an HA Cluster.
| COMMUNITY EDITION FOR SINGLE NODE | EVALUTAION EDITION FOR HA CLUSTER |
|---|
- Hit the "Deploy to Azure" button, and in the deployment template add the link to the VMR provided by Solace.
The fields that you need to fill out are:
- Resource Group - A new group, or an existing group that will be available in the pulldown menu once "Use existing" is selected.
- Location - Select region most suitable to you.
- Storage Account Name – New or existing storage account, your VHD will be stored here.
- Admin Username - Username for the virtual Machine.
- Admin Password - Password for the virtual Machine.
- Security Group Name – New or existing security group, VMR default ports will be made publicly available.
- DNS Label – Used for the public DNS name for the virtual machine.
- CentOS version – Use Centos 7.2 or CentOS 7.3
- VM Size – Use Standard_D2_V2 or Standard_F2s
- Solace VMR URI – The URI link from the registration email received during Step 1 of the install process.
- Deployment Model - High Availability, Single Node
After completing the template fields and accepting the legal terms, you need to purchase the deployment, the cost will only be related to the Azure instance costs.
Once the deployment has started you can view its progress under the Resource Groups tab. Select the resource group you have deployed into, then select the correct deployment across the top. You can then scroll down and see its progress.
In this example the resource group is testvmr3, the Microsoft.Template template is in progress. You can see the VMs have started, SolaceVMR0,1,2; the Docker extensions have been installed and the VMR configurations are taking place. Once the VMRs are configured, the Primary VMR validates the cluster and will signal the deployment complete. After this point you can access the VMRs.
For persons used to working with Solace message router console access, this is still available with the Azure instance. The [connect] button to the upper left displays this information: Use the "Admin Username" and "Admin Password" provided.
Once you have access to the base OS command line you can access the SolOS CLI with the following command:
sudo docker exec -it solace /usr/sw/loads/currentload/bin/cli -A
It would be advised to change the SolOS cli admin user password, as per these instructions
If you are unfamiliar with the Solace message router, or would prefer an administration application, the SolAdmin management application is available. For more information on SolAdmin see the SolAdmin page. To get SolAdmin, visit the Solace download page and select OS version desired. Management IP will be the External IP associated with your Azure instance and the port will be 8080 by default.
To test data traffic though the newly created VMR instance, visit the Solace developer portal and and select your preferred programming language to send and receive messages. Under each language there is a Publish/Subscribe tutorial that will help you get started.
All startup logs are located here: /var/lib/waagent/custom-script/download/0/ and are readable by root only.
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 about writing Azure Resource Manager(ARM) templates and Azure quickstart templates try these resources:
For more information about Solace technology in general please visit these resources: