Adding the Sealights java agent into you Pivotal Cloud Foundry / (formerly VMWare Tanzu Application Services) is done by using the standard java buildpack 4.39 or later.
Info |
---|
Complimentary information is detailed in https://github.com/cloudfoundry/java-buildpack/blob/main/docs/framework-sealights_agent.md |
Prerequisite: Installing CF Java buildpack
The java-buildpack
is a Cloud Foundry buildpack for running JVM-based applications and configured in one of the following ways:
...
If you need to create an offline buildpack without network access you can do so following the instructions here: https://github.com/cloudfoundry/java-buildpack#offline-package
Create your Sealights User-Provided service
Create a Sealights User-Provided Service and configure it with an agent token. This should be done once, before configuring the first application.
Linux |
| |||||
Windows |
|
Note |
---|
A different name for the user-provided service may be used, but it has to include the word |
The token may later be changed using: cf update-user-provided-service sealights -p ....
Bind your application to your Sealights service
Bind the User-Provided Service with your application using the following command
...
Available configuration keys are
Name | Description |
---|---|
| Sealights' Build Session ID for the application. Leave blank to use the value embedded in the jar/war artifacts |
| Specify a HTTP proxy used to communicate with the Sealights backend. Required when a corporate network prohibits communication to cloud services. |
| Specify a Sealights Lab ID |
| Enable/disable agent auto-upgrade. Off by default. |
| The version of Auto-reconfiguration to use. Candidate versions can be found in this listing. |