The topics in this subsection explain how to integrate your software service with Pivotal Cloud Foundry (PCF) to create a brokered service and service tile for PCF.
You can achieve the first real improvement in your PCF customers user experience by creating a Service Broker for your service.
A brokered service runs external to PCF, but it has a tile on Pivotal Network (PivNet). Operators install, configure, and upgrade the tile through the Ops Manager Installation Dashboard.
The service broker eliminates the need for your customers to know the URLs and credentials for your services; they are managed automatically by the broker.
Building a broker for a (still) externally deployed service is generally a good way to publish a first tile that adds real value for customers who have both your software and PCF.
A brokered service requires a service broker, which publishes an API to the Cloud Controller.
Service Brokers explains how to create one.
Route Services explains how to create a route service, for use in the routing layer of PCF rather than by hosted PCF apps.
Catalog explains how to design the part of your service broker API that publishes service plan information to the Services Marketplace.
You can write your service broker in the language of your choice.
Buildpacks explains how to create a language-specific buildpack that compiles and packages your service broker to run on PCF.
A PCF buildpack lets you inject embedded agent code into application containers, such as for application performance monitoring (APM) or client-side routing.
Embedded Agents explains how to do this.
Once you have the individual components for your brokered service integration, you can work through the development steps to create your tile.
At any level of integration, Pivotal recommends and supports using Concourse for continuous integration during development.