Page last updated:
The topics in this subsection explain how to integrate your software service with Pivotal Platform to create a brokered service and service tile for Pivotal Platform.
You can achieve the first real improvement in your Pivotal Platform customers user experience by creating a Service Broker for your service.
A brokered service runs external to Pivotal Platform, 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 Pivotal Platform.
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 Pivotal Platform rather than by hosted Pivotal Platform 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 Pivotal Platform.
Once you have the individual components for your brokered service integration, you can work through Building Your First Tile to create your tile.
At any level of integration, Pivotal recommends and supports using Concourse for continuous integration during development.