There are many ways to integrate services with VMware Tanzu Application Service for VMs and Ops Manager. The right one for each service depends on what the service does, and how customer applications consume it. To determine the best way to integrate your service, you’ll need a good understanding of TAS for VMs concepts like applications, containers, services, brokers, and buildpacks.
This page provides a collection of links to documentation for the most relevant concepts. If you prefer to learn through guided training, ask us about available training options.
For general overview of TAS for VMs, and the various ways to interact with it, use the following links:
Cloud Foundry is primarily a cloud native application platform. To understand how to integrate your services with Cloud Foundry, you should understand how your customers are using the platform to develop, deploy, and operate their applications.
Most value-add integrations are done by exposing your software to customer applications as services. To understand the service concepts, and what a service integration looks like, read the following documentation:
When application code is deployed to Cloud Foundry, it is processed by a language-specific buildpack. Language buildpacks provide a convenient integration hook for any service that needs to inspect or embellish application code. Supplying buildpacks also provides a language-agnostic way to inject your code into the application container image.
Some integrations depend on the ability to inject code into the application container. We refer to these injected components as “container-embedded agents”. Buildpacks provide a mechanism to inject components into the application container image, and the
.profile.d directory provides a way to start agents before or alongside the customer application.
Cloud Foundry’s logging system, Loggregator, has a feature named firehose. The firehose includes the combined stream of logs from all apps, plus metrics data from Cloud Foundry components, and is intended to be used by operators and administrators.
A nozzle takes this data and forwards it to an external logging and/or metrics solution.