Here you will find information about configuring options in the Spring Cloud Data Flow for VMware Tanzu tile settings.

Tanzu Operations Manager administrators can use Role-Based Access Control (RBAC) to manage which operators can make deployment changes, view credentials, and manage user roles in Tanzu Operations Manager. Therefore, your role permissions might not allow you to perform every procedure in this operator guide. For more information about roles in Tanzu Operations Manager, see Understand Role-Based Access Control (RBAC) in Tanzu Operations Manager.

The Spring Cloud Data Flow tile includes settings for various options. You can configure these by visiting the Installation Dashboard of Tanzu Operations Manager and clicking the Spring Cloud Data Flow tile.

Configure buildpack for broker and service instances

By default, the Spring Cloud Data Flow service broker application and service instance backing applications use the buildpack chosen by the platform’s buildpack detection; normally, this is the highest-priority Java buildpack.

To cause these applications to use a particular Java buildpack regardless of priority, you can set the name of the buildpack to use.

1. In the Spring Cloud Data Flow tile, go to Settings > Security Groups.

2. In Buildpack to use when pushing apps, enter the name of the desired Java buildpack.

3. Click Save and return to the Installation Dashboard.

4. Review your changes. For more information, see Reviewing Pending Product Changes.

5. Click Apply Changes. The broker application and service instance applications will now use the selected buildpack.

Configure Data Flow server dependent services

By default, the Spring Cloud Data Flow product uses the VMware Tanzu for MySQL and VMware Tanzu RabbitMQ products to provision dependent service instances for the Data Flow server application deployed for each Data Flow service instance.

If you want to use other services or change the service plans used, you must configure the services and service plans to use for the Data Flow server.

1. In the Spring Cloud Data Flow tile, click Settings > Data Flow Server.

2. If you want to change services, in the Service name to use for default Data Flow server relational database or Service name to use for default Data Flow server messaging data service field, enter the service you want to use as default.

3. If you want to change the service plans to use, in the Service plan to use for default Data Flow server relational database or the Service plan to use for default Data Flow server messaging data service field, enter the service plan to use.

4. Click Save and return to the Installation Dashboard.

5. Review your changes. For more information, see Reviewing Pending Product Changes.

6. Click Apply Changes.

Deactivate Data Flow Server internet access

You can deactivate internet access for all Spring Cloud Data Flow service instances.

1. In the Spring Cloud Data Flow tile, click Settings > Data Flow Server.

2. Select Disable public Internet access.

3. Click Save and return to the Installation Dashboard.

4. Review your changes. For more information, see Reviewing Pending Product Changes.

5. Click Apply Changes.

Specify URL for Composed Task Runner

By default, the Spring Cloud Data Flow product downloads the Composed Task Runner app from Maven Central. If you want to use a different app:

1. In the Spring Cloud Data Flow tile, click Settings > Data Flow Server.

2. In URL to download Composed Task Runner, enter the URL for the app.

3. Click Save and return to the Installation Dashboard.

4. Review your changes. For more information, see Reviewing Pending Product Changes.

5. Click Apply Changes.

Configure Skipper database service and plan

By default, the Spring Cloud Data Flow product uses the VMware Tanzu for MySQL product and its default db-small service plan to provision a database service instance for the Spring Cloud Skipper application deployed for each Data Flow service instance. If you are using the VMware Tanzu for MySQL product and it does not have an active db-small plan or if you want to use an alternative service, you must configure the service and service plan to use for Skipper.

You can configure an alternative relational database service and service plan in the Skipper pane of the Spring Cloud Data Flow settings.

1. In the Spring Cloud Data Flow tile, click Settings > Skipper.

2. Under Default configuration settings for Spring Cloud Skipper:

   • In Service name to use for default Skipper relational database, enter p.mysql for the default, or change to your database.
   • In Service plan to use for default Skipper relational database, enter db-small for the default, or change to your service plan.

3. Click Save and return to the Installation Dashboard.

4. Review your changes. For more information, see Reviewing Pending Product Changes.

5. Click Apply Changes.

Configure default Maven repositories

A Spring Cloud Data Flow service instance can be given Maven repository connection information in its configuration. See the Setting Maven Properties section of Managing Service Instances.

If you want to provide default Maven repository information for use by all Spring Cloud Data Flow service instances:

1. In the Spring Cloud Data Flow tile, click Settings > Maven Repositories.

2. Click Add, and enter the following information:

   • In The property key for the Maven repository, enter a key for the repository (used in Data Flow configuration properties; for example, maven.remote-repositories[KEY].url).
   • In The URL to the Maven repository, enter the URL of the repository.
   • In The user used to authenticate to the Maven repository, enter the username used to connect to the repository (optional).
   • In The password used to authenticate to the Maven repository, enter the password used to connect to the repository (optional).

3. Click Save and return to the Installation Dashboard.

4. Review your changes. For more information, see Reviewing Pending Product Changes.

5. Click Apply Changes. New Spring Cloud Data Flow service instances are now given the Maven repository information in their configuration automatically.

Configure App Security Groups (ASGs)

You can configure a list of App Security Groups (ASGs) that the Spring Cloud Data Flow service broker binds to the backing Spring Cloud Data Flow and Spring Cloud Skipper apps created for new service instances.

To configure the list:

1. In the Spring Cloud Data Flow tile, click Settings > Security Groups.

2. In Security Groups, enter a comma-separated list of ASGs for the Data Flow service broker to use when creating a new service instance.

3. Click Save.

4. Return to the Installation Dashboard, and review your changes. For more information, see Reviewing Pending Product Changes.

5. Click Apply Changes. The ASGs are now automatically bound to the backing apps for all new Spring Cloud Data Flow service instances.

Configure Wavefront

Spring Cloud Data Flow can integrate with VMware Tanzu Observability by Wavefront to monitor deployed event-streaming and batch applications.

To activate Wavefront integration:

1. In the Spring Cloud Data Flow tile, click Settings > Wavefront.

2. In Wavefront key, enter the user API key.

3. In Wavefront URI, enter the URI.

4. If desired, you can change the default source prefix for Data Flow metrics. Enter the new default in Default Wavefront source prefix.

5. Click Save.

6. Return to the Installation Dashboard, and review your changes. For more information, see Reviewing Pending Product Changes.

7. Click Apply Changes. Spring Cloud Data Flow will use the specified Wavefront instance and settings.

Activate or deactivate Global Marketplace Access

By default, the Spring Cloud Data Flow product activates access to its service offering, called p-dataflow, across all orgs in the Tanzu Platform for CF deployment as part of the tile installation process.

If you want to manually grant service access to specific organizations, you can configure the default global access:

1. In the Spring Cloud Data Flow tile, click Settings > Service Access.

2. To deactivate the default service access activated for all orgs, unselect Enable global access to plans of service p_dataflow.

3. Click Save.

4. Return to the Installation Dashboard, and review your changes. For more information, see Reviewing Pending Product Changes.

5. Click Apply Changes. You can now activate or deactivate access to the Data Flow service offering for specific orgs.