Installing and Configuring Spring Cloud® Data Flow for PCF
Follow the below steps to install Spring Cloud Data Flow for PCF.
Spring Cloud Data Flow for PCF is built using Spring Boot 1.5, which requires version 3.8 or later of the Java Cloud Foundry buildpack. The default Java buildpack—the buildpack at the lowest position of all Java buildpacks—on your PCF installation must therefore be at version 3.8 or later.
You can use the Cloud Foundry Command Line Interface tool (cf CLI) to see the version of the Java buildpack that is currently installed.
$ cf buildpacks Getting buildpacks... buildpack position enabled locked filename java_buildpack_offline 1 true false java-buildpack-offline-v3.8.1.zip ruby_buildpack 2 true false ruby_buildpack-cached-v1.6.19.zip nodejs_buildpack 3 true false nodejs_buildpack-cached-v1.5.15.zip go_buildpack 4 true false go_buildpack-cached-v1.7.10.zip
If the default Java buildpack is older than version 3.8, you can download a newer version from Pivotal Network and update Pivotal Cloud Foundry by following the instructions in the Managing Custom Buildpacks topic. To ensure that the newer buildpack is the default Java buildpack, you may delete or disable the older buildpack or make sure that the newer buildpack is in a lower position.
Spring Cloud Data Flow relies on other PCF services for its service broker, for the Data Flow server created for each service instance, and for the Spring Cloud Skipper application created for each service instance. You can configure these in the tile settings. When following the installation steps below, review all of these settings, ensuring that you have previously installed the specified services and that the specified service plans are active.
Important: If any of the services or service plans configured in the Data Flow tile settings are not available in your PCF deployment, the tile installation may fail.
Download the product file from Pivotal Network.
Navigate to the Ops Manager Installation Dashboard and click Import a Product to upload the product file.
Under the Import a Product button, click + next to the version number of Spring Cloud® Data Flow for PCF. This adds the tile to your staging area.
Click the newly added Spring Cloud Data Flow tile. In the Settings tab, click Assign AZs and Networks.
Select the availability zones for the tile to use. In the Network section, select the PAS (or ERT) network.
In the Settings tab, click Service Broker.
Enter the relational database service name and plan name for the Spring Cloud Data Flow tile to use for storing its service broker’s service instance data.
You can also configure the Java buildpack to use for deploying the broker and service instance applications (by default, the tile will use the highest-priority Java buildpack).
In the Settings tab, click Data Flow Server.
Configure the default services and service plans used by the Spring Cloud Data Flow server that is deployed for each Data Flow service instance. These values can be overridden when creating a Data Flow service instance.
Still in the Settings tab, click Skipper.
Configure the relational database service name and plan used by the Spring Cloud Skipper application deployed for each Data Flow service instance.
Still in the Settings tab, click Errands.
Each of the four lifecycle errands can be set to run conditionally (When Changed), always (On), or not at all (Off). Pivotal recommends that all Spring Cloud Data Flow lifecycle errands be set to always run (On).
Return to the Ops Manager Installation Dashboard and click Apply Changes to install the Spring Cloud® Data Flow tile.