Solace Messaging for PCF
Solace Messaging for Pivotal Cloud Foundry (PCF) enables developers to take advantage of the leading multi-cloud, multi-protocol messaging solution which makes app interconnectivity easy and makes production apps scalable, robust, high-performant, and easy to manage.
Solace Messaging was designed to be deployed across all your IT environments including your non-cloud datacenter, all leading public clouds (AWS, Azure, and Google Cloud Platform) and the popular Platform as a Service, PCF, in order to provide a uniform messaging fabric for all your apps and connect them no matter where they are deployed.
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 is 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 apps.
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, scale, and high-availability. Together, they meet the requirements for a range of 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 app.
In addition to the documentation here, there is also a wealth of information on the Solace Developer Portal.
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:
Solace Messaging currently offers the following plans:
|Service Plan||Description||Evaluation Tile||Enterprise Tile 2|
|Shared||A single Message VPN in a shared Solace Message Router. Useful for light traffic and development.||✔ 1||✔|
|Large||A single message VPN on a dedicated Solace Message Router.||✔ 1||✔|
|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.||✔|
|Medium-HA||A single message VPN implemented across 3 medium Solace Message Routers in a highly-available configuration.||✔ 1||✔|
|Large-HA||A single message VPN implemented across 3 large Solace Message Routers in a highly-available configuration.||✔ 1||✔|
1 Note: This Evaluation Tile plan is fully featured but has a time-limited 90-day evaluation period.
A Solace Messaging deployment under PCF can be configured to support integration with existing cloud services and hybrid cloud deployments.
TCP routes allow access to Solace messaging services hosted inside your PCF domain from external networks. By default, a PCF-hosted service is not accessible to external networks.
Having TCP routes enables many use cases:
- Hybrid cloud: Other Solace appliances or VMRs deployed outside PCF can establish Bridge connections to Solace messaging services inside your PCF cloud.
- External client app: Apps deployed outside PCF can communicate via messaging with apps deployed inside PCF by connecting to a Solace messaging service deployed in PCF.
- IoT: Devices using MQTT or REST can connect to Solace messaging services from outside PCF to communicate with your apps deployed inside PCF, look for the TCP Routes for IoT—MQTT Java Application Tutorial Getting Started Samples with full source code available in GitHub.
- Mobile apps: Mobile and web apps can use web messaging to connect to Solace messaging services from outside PCF to communicate with your apps deployed inside PCF.
To use TCP routes, you must enable and configure TCP Routes at installation time with a selection of default settings for each messaging protocol you wish to use. Once enabled, TCP routes can be fine-tuned per service at service creation time.
System logging allows you to redirect the logs from the Solace Messaging PCF components to an external syslog service. To use system logging, you must enable and configure system logging at installation time.
You can enable the use of an LDAP server for the VMR’s authentication and authorization needs. This configuration allows you to grant an LDAP server control over Management access and Application access. To use LDAP, you must enable and configure LDAP at installation time and make a choice about Management Access and Application Access.
In addition to easy and natural APIs for your apps, Solace Messaging supports the following key features:
- Easy integration with 3rd party products such as big data, ESBs, JEE, DataPower, and more.
- Comprehensive authentication, authorization, and encryption features to ensure that your infrastructure and information are protected at all times.
- The most robust data movement infrastructure available today, offering fault tolerance and disaster recovery.
- Integrated federation and distribution for connectivity between Solace message routers.
- High-performance messaging middleware which can cost-effectively meet the needs of any app.
- Fast, efficient WAN distribution.
- Simplified operations with multiple management administration interfaces.
- Virtualize application groups on a single Solace message router with complete message isolation through Solace Message VPNs.
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 diagram below provides an overview of the product architecture of Solace Messaging for PCF.
Note: As of PCF v2.0, Elastic Runtime is renamed Pivotal Application Service (PAS).
The following table provides version and version-support information about Solace Messaging for PCF.
|Release date||April 13, 2018|
|Solace Virtual Message Router version||v8.9.0.x|
|Compatible Ops Manager version(s)||v1.11.x, v1.12.x, v2.0.x, and v2.1.x|
|Compatible Pivotal Application Service version(s)||v1.11.x, v1.12.x, v2.0.x, and v2.1.x|
|IaaS support||AWS, Azure, GCP, OpenStack, and vSphere|
This version of Solace Messaging for PCF currently has the following limitations:
- No support for client certificate-based authentication.
- No support for RADIUS-based authentication.
Provide any bugs, feature requests, or questions to Solace Support.