Tile Configuration

See below for information about configuring options in the Pivotal Spring Cloud Data Flow tile settings.

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

Tile Configuration Options

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

Configure Broker Database Service and Plan

By default, the Spring Cloud Data Flow product uses the MySQL for PCF product and its default db-small service plan to provision a database service instance for the Data Flow service broker. If you are using the MySQL for PCF product and it does not have an active db-small plan or if you wish to use an alternative service, you must configure the Spring Cloud Data Flow product for the service and service plan you wish to use. You can configure an alternative relational database service and service plan in the Service Broker pane of the Spring Cloud Data Flow settings.

Configuring MySQL Service

The broker’s database service should be configured only during the Spring Cloud Data Flow tile installation process. If you have already completed the tile installation process, do not alter that setting (you may still configure the broker’s database service plan after the tile installation).

WARNING: Configuring the service broker’s dependent relational database service after the tile installation has finished can result in orphaned Data Flow service instances or in multiple data sets and corruption of the broker database’s data.

See below for more information about the results of configuring the service broker’s relational database.

If you and change then
install the tile the service name or plan the tile uses the specified service and plan. You may also use the default values of p.mysql and db-small.
update the tile the service plan the tile’s relational database service instance is changed to use the specified plan. No data is lost.
update the tile the service name the service name change is ignored. If you have also changed the service plan, this may leave the broker in an inoperative state. To resolve this issue, revert your changes.

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 will be 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 in the Service Broker pane of the Spring Cloud Data Flow tile settings.

Configuring Java Buildpack

In the Buildpack field, enter the name of the desired Java buildpack. Click Save and return to the Installation Dashboard. If using Ops Manager 2.3 or later, review your changes (see Reviewing Pending Product Changes). Apply your 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 MySQL for PCF and RabbitMQ for PCF products to provision dependent service instances for the Data Flow server application deployed for each Data Flow service instance. If you wish to use other services or to change the service plans used, you must configure the services and service plans you wish to use for the Data Flow server. You can configure alternate services or service plans in the Data Flow Server pane of the Spring Cloud Data Flow settings.

Configuring Data Flow Server Database Service

Disable Data Flow Server Internet Access

You can disable internet access for all Spring Cloud Data Flow service instances. To do this, select the “Disable public Internet access” checkbox in the Data Flow Server pane of the Spring Cloud Data Flow settings.

Disabling Data Flow Server Internet Access

Configure Skipper Database Service and Plan

By default, the Spring Cloud Data Flow product uses the MySQL for PCF 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 MySQL for PCF product and it does not have an active db-small plan or if you wish to use an alternative service, you must configure the service and service plan you wish 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.

Configuring Skipper Database Service

Enable or Disable Global Marketplace Access

By default, the Spring Cloud Data Flow product enables access to its service offering, called p-dataflow, across all orgs in the PCF deployment as part of the tile installation process. If you wish to manually grant service access to specific organizations, you can configure the default global access in the Service Access pane of the Spring Cloud Data Flow settings.

Configuring Service Access

To disable the default of service access enabled for all orgs, clear the Enable global access to plans of service p_dataflow checkbox. Click Save and return to the Installation Dashboard. If using Ops Manager 2.3 or later, review your changes (see Reviewing Pending Product Changes). Apply your changes. You can now enable or disable access to the Data Flow service offering for specific orgs.