Installing, Configuring, and Upgrading the Tile

This topic describes how to install, configure, and upgrade the TIBCO BusinessWorks Container Edition Buildpack for Pivotal Cloud Foundry (PCF) tile.

Install and Configure the TIBCO BusinessWorks Container Edition Buildpack

  1. Download the product file from Pivotal Network.

  2. Navigate to Ops Manager and click Import a Product to upload the product file on the Ops Manager Installation Dashboard.

  3. Click Add next to the uploaded TIBCO BusinessWorks Container Edition Buildpack for PCF tile in the Ops Manager Available Products view to add it to your staging area.

  4. Click the newly added TIBCO BusinessWorks Container Edition Buildpack for PCF tile to configure it.

  5. Click Buildpack Settings and enter the position for the buildpack installed by the tile. This sets the order of the buildpack relative to the other buildpacks in the detection priority list. For more information, see the Buildpack Detection topic. Buildpack settings

  6. Click Stemcell. Download the BOSH stemcell version appropriate for your IaaS from Pivotal Network and click Import Stemcell to import it. Stemcell

  7. Click Save.

  8. Return to the Ops Manager Installation Dashboard and click Apply Changes to install the tile.

Upgrade the TIBCO BusinessWorks Container Edition Buildpack

  1. Download the latest version of the product from Pivotal Network.

  2. Navigate to Ops Manager and click Import a Product to upload the product file on the Ops Manager Installation Dashboard.

  3. Click Add next to the uploaded TIBCO BusinessWorks Container Edition Buildpack for PCF tile in the Ops Manager Available Products view to add it to your staging area.

  4. Click the newly added TIBCO BusinessWorks Container Edition Buildpack for PCF tile to configure it.

  5. Follow the configuration steps in the section above. Download and import the new stemcell associated with the update, if required.

  6. Click Save.

  7. Click Apply Changes to install the upgraded tile.

Create a pull request or raise an issue on the source for this page in GitHub