The TIBCO BusinessWorks Container Edition Buildpack
The TIBCO BusinessWorks Container Edition Buildpack must be uploaded in your Cloud Foundry environment before deploying any applications.
Customize the Buildpack
This Buildpack can be customized for the supported third-party drivers, OSGI bundles, integration with application configuration management systems, and application certificate management.
Note: Customization of the Buildpack is not supported on the Windows platform.
- Procedure
- Download the TIBCO BusinessWorks Container Edition Buildpack zip file from
http://edelivery.tibco.com.
To download this file:
- Select
Container from the
Operating Systems
dropdown list. - Read and accept the TIBCO End User License Agreement.
- Select the radio button for Individual file Download.
- Click
+ sign to view the individual components and select
bwce_buildpack_cf-vx.x.x.zip
.
- Select
Container from the
- Extract the contents of the zip file to a temporary location.
- Customize the Buildpack for the database drivers.
- Follow the steps outlined in JBDC Connection in the TIBCO BusinessWorks™ Container Edition Bindings and Palettes Reference.
- Copy the appropriate driver bundle from
TIBCO_HOME/bwce/version/config/drivers/shells/<driverspecific runtime>/runtime/plugins/
to the<your local buildpack repo>/resources/addons/jars
folder in your temporary location.
- Provision the OSGi bundle jars.
Copy the OSGi bundle jars into the
<your buildpack repo>/resources/addons/jars
folder in your temporary location. - Application Configuration Management
For more information, see Using Configurations from Configuration Management Services for Cloud Foundry.
- Certificate Management
Certificates are used by applications to connect to different systems. For example, a certificate to connect to Spring Cloud Config service or a certificate to connect to TIBCO Enterprise Message Service.Bundling certificates with your application is not a good idea as you would need to rebuild your application when the certificates expire. To avoid that, copy your certificates into the
<your local buildpack repo>/resources/addons/certs
folder in your temporary location.Once the certificates expire, you can copy the new certificates into the Buildpack without rebuilding your application. Deploy your application with the new Buildpack. To access the certificates folder from your application, use the environment variableBW_KEYSTORE_PATH
. For example,#BW_KEYSTORE_PATH#/mycert.jks
in your application property. - Provision the BusinessWorks Container Edition Plug-in Runtime
To add TIBCO certified plug-ins:
- Download the appropriate Plug-in packaging. For example, TIBCO ActiveMatrix BusinessWorks™ Plug-in for WebSphere MQ, from https://edelivery.tibco.com.
- Locate the plug-in zip file,
<product id>_ePaas.zip
orTIB_<version>_<build number>_bwce-runtime.zip
from the downloaded artifacts and copy into<your local buildpack repo>/resources/addons/plugins
.
To add a plug-in created using the TIBCO ActiveMatrix BusinessWorks™ Plug-in Development Kit to the runtime into your Buildpack:- Install the plug-in if it is not installed.
- Navigate to the
TIBCO_HOME/bwce/palettes/<plug in name>/<plugin version>
directory and zip thelib
andruntime
folders into<plugin name>.zip
. - Copy
<plugin name>.zip
to the<your buildpack repo>/resources/addons/plugins
folder.
Copy any required OSGi bundles. For example, driver bundles into<your buildpack repo>/resources/addons/jars
- Provision to add third-party client installation at runtime
- Package third-party client installation into zip.
- Copy zip file to
<YOUR-BUILDPACK-REPO>/resources/addons/thirdparty-installs
folder.
- Provision to add custom JDBC driver
- For more information, see the "Enabling Custom Drivers" section of the JDBC Connection topic in the TIBCO BusinessWorks™ Container Edition Bindings and Palette Reference.
- After the project has been exported as a plug-in to the location you specified, locate the JAR file in the plug-in folder, and copy paste the JAR to the
<YOUR-BUILDPACK-REPO>/resources/addons/jars
folder.
- Provision to add custom JMS driver
- For more information, see the "Enabling Custom Drivers" section of the JNDI Connection topic in the TIBCO BusinessWorks™ Container Edition Bindings and Palette Reference.
- After the project has been exported as a plug-in to the location you specified, locate the JAR file in the plug-in folder, and copy paste the JAR to the
<YOUR-BUILDPACK-REPO>/resources/addons/jars
folder.
- Provision to use custom logs
- Create a new folder
custom-logback
in the<YOUR-BUILDPACK-REPO>/resources/addons
folder. - Add the customized logback file in the folder. The name of the logback file should be
logback.xml
.Note: While running the application, set the environment variable CUSTOM_LOGBACK="true".
- Create a new folder
- Provision to add multiple BuildpackTo push an application with multiple Buildpack, specify each Buildpack with a
-b
flag and run the following command:cf push YOUR-APP -b BUILDPACK-NAME-1 -b BUILDPACK-NAME-2 ... -b BUILDPACK-NAME-3
Where:YOUR-APP
is the name of the application.BUILDPACK-NAME-1 -b BUILDPACK-NAME-2 ... -b BUILDPACK-NAME-3
are the names of the Buildpack that you want to push with the application.
The GitHub branch location from where multiple Buildpack are created is https://github.com/TIBCOSoftware/bwce-buildpack/tree/multi-buildpack-supportThe last Buildpack specified is the final TIBCO BusinessWorks Container Edition Buildpack, which modifies the open environment and sets the start command. - Zip the contents of the temporary location to create the TIBCO BusinessWorks Container Edition Buildpack zip file.
- Push the Buildpack to the Cloud Foundry environment.