Solace Messaging for Pivotal Cloud Foundry (Beta)

Solace Messaging for PCF enables developers to take advantage of the leading multi-cloud, multi-protocol messaging solution which makes application inter-connectivity easy and makes production applications scalable, robust, high-performant, and easy to manage. Solace Messaging supports all kinds of messaging APIs, QoS, and data streaming as part of one platform across all clouds in a high performance, WAN optimized, easy to manage solution. It’s easily deployed in your public and private cloud environments and forms the perfect backbone for single or multi-cloud messaging support of your cloud native micro-services, IoT, big data capture, and next generation digital applications.

Solace Messaging for PCF provides plans for both shared message router instances for cost-effective development as well as a variety of plans for dedicated message routers of varying performance and scale for robust test and production deployments.

One of the key strengths of Solace Messaging is its support for many different open transports and protocols, making Solace message routers ideal data distribution platforms to connect to any application.

Solace overview

Getting Started

In addition to the documentation here, there is also a wealth of information on the Solace Developer Portal.

Cloud Operators

For cloud operators, the following section shows you how to install and configure Solace Messaging for PCF in your environments.


For developers, there are a few resources to help you easily get started with Solace Messaging for PCF. Within this documentation, see the following sections:

There is also simple sample code which shows you how to easily connect to a Solace Messaging Service Instance:

PCF Marketplace Plans

Solace Messaging currently offers the following plans to meet the needs of applications. More plans will be introduced as the Solace Messaging for PCF tile evolves towards GA.

Service Plan Description
Shared A single Message VPN in a shared Solace Message Router. Useful for light traffic and development. This plan is not feature limited but does have a time limited 90-day evaluation period.
Large A single message VPN on a dedicated Solace Message Router. This plan is not feature limited but does have a time limited 90-day evaluation period.
Community A single message VPN on a dedicated Solace Message Router. The plan does not have a time limit but is limited by the features available on the Community Edition VMR.

Solace Messaging Features

In addition to easy and natural APIs for your applications, Solace Messaging supports the following key features:


Solace Messaging is a Managed Service. The tile deploys the Virtual Message Routers onto PCF’s IaaS. The Solace Messaging tile registers a service broker with PCF and exposes its service plans in the PCF Marketplace. The following diagram provides an overview of the product architecture of Solace Messaging for PCF.

Deployment overview

Product Snapshot

Current Solace Messaging for Pivotal Cloud Foundry Details:

  • Version: v0.3.0
  • Release Date: December 7, 2016
  • Software component version: Solace Messaging for PCF v0.3.0
  • Solace Virtual Message Router version: v7.2pcf2.1.6, which is similar in functionality to VMR v7.2.1
  • Compatible Ops Manager Version(s): v1.7.x, v1.8.x
  • Compatible Elastic Runtime Version(s): v1.7.x, v1.8.x
  • vSphere support? Yes
  • AWS support? Yes
  • Solace Messaging is expected to function on other PCF-supported IaaS platforms as it does in the above IaaS platforms

Beta Limitations

This version of Solace Messaging for PCF currently has the following limitations:

  • No support for Solace Message Router High availability
  • No support for Client certificate-based authentication
  • No support for LDAP and RADIUS-based authentication
  • No routes are set up which would allow access to the Virtual Message Router from external networks
  • All Persistent Messages are lost during a tile upgrade


Provide any bugs, feature requests, or questions to the Pivotal Cloud Foundry Feedback list.

Was this helpful?
What can we do to improve?
Create a pull request or raise an issue on the source for this page in GitHub