forked from mboldt/docs-tiledev
-
Notifications
You must be signed in to change notification settings - Fork 0
/
brokered.html.md.erb
36 lines (22 loc) · 2.16 KB
/
brokered.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
---
title: Brokered Service
owner: Services
---
The topics in this subsection explain how to integrate your software service with <%= vars.platform_name %> to create a brokered service and service tile for <%= vars.platform_name %>.
## <a id="overview"></a> Overview
You can achieve the first real improvement in your <%= vars.platform_name %> customers user experience by creating a [Service Broker](service-brokers.html) for your service.
A brokered service runs external to <%= vars.platform_name %>, but it has a tile on [VMware Tanzu Network](http://network.pivotal.io). 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 <%= vars.platform_name %>.
## <a id="create"></a> Create a Brokered Service
* A brokered service requires a service broker, which publishes an API to the Cloud Controller.
[Service Brokers](./service-brokers.html) explains how to create one.
* [Route Services](./service-brokers.html#route) explains how to create a route service, for use in the routing layer of <%= vars.platform_name %> rather than by hosted <%= vars.platform_name %> apps.
* [Catalog](./service-brokers.html#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](./buildpacks.html) explains how to create a language-specific buildpack that compiles and packages your service broker to run on <%= vars.platform_name %>.
* Once you have the individual components for your brokered service integration, you can work through [Building Your First Tile](./index.html#tile-steps) to create your tile.
At any level of integration, <%= vars.company_name %> recommends and supports using [Concourse](./concourse.html) for continuous integration during development.