Testing the JMS Basic Sample with Spring Cloud Config Server

Prerequisites

  • The Cloud Foundry environment updated with TIBCO BusinessWorks™ Container Edition buildpack.
  • User provided service for TIBCO Enterprise Message Service.
  • User provided service for Spring Cloud Config or a managed Spring Cloud Config service. See https://docs.pivotal.io/spring-cloud-services/config-server/ for more info.
  • Read the procedure for creating an user provided service from the Cloud Foundry documentation. See https://docs.cloudfoundry.org/.
  • The cf command line interface tool installed on your machine.

Config Server for Cloud Foundry is an externalized application configuration service which gives you a central place to manage an application's external properties across all environments. Spring Cloud Config Server is used for this purpose, that provides HTTP, resource-based API for external configuration (name-value pairs, or equivalent YAML content). The default backend storage repository is a Git Repo that stores the application configuration files. For running this sample, its assumed that the spring cloud config server is running with Git Repo backend and that the configuration files can be retrieved as a client.

In this example, foo maps to the application name and default maps to your Application Profile or Environment. 

curl http://54.67.121.175:8888/foo/default 
{"name":"jmsspringcloud","profiles":["default"],"label":null,"version":"0fd3f399e2fb5de96aa07a130d59fbe5e03232ed","propertySources":[{"name":"https://github.com/TIBCOSoftware/bwcf-spring-config-server-data/jmsspringcloud-default.properties","source":{"EMS_QUEUE":"springconfig.queue","MESSAGE":"This message is from GIT repo","EMS_URL":"tcp://localhost:7222","REPLY_QUEUE":"springconfigreply.queue"}}]}