#Tibco bw process monitor how to
#Tibco bw process monitor zip file
#Tibco bw process monitor plus

We need to slightly modify the generated manifest.json file (of BW app) to expose an additional port, 9095 (shown below) .Īlso, to tell TCI that we want to enable Prometheus endpoint we need to set a property in the manifest.json file. Note: This document does not cover the details on setting the Prometheus server (it is NOT needed for this PoC) but you can find the relevant information on

#Tibco bw process monitor zip file

Import the project from the zip file generated before.īefore you deploy the BW application on TCI, we need to enable an additional port on TCI to scrape the Prometheus metrics.īy default, a TCI app using the manifest.json file only exposes one port to be consumed from outside (related to functional services) and the other to be used internally for health checks.įor Prometheus integration with TCI, we need an additional port listening on 9095, so Prometheus server can access the metrics endpoints to scrape the required metrics for our TCI application.Remove the Prometheus project from the workspace.Export the project with the Prometheus module to a zip file.NOTE: If the EAR doesn’t get generated once you add the Prometheus plugin, please follow the below steps: Step three is just to build the EAR file along with manifest.json. Step two involves adding the Prometheus module previously imported to the specific application as shown below: Import the Prometheus plugin by choosing Import → Plug-ins and Fragments option and specifying the directory downloaded from the above mentioned GitHub location. To do that, you just need to clone the GitHub Repository available here: OR Step one is to import the Prometheus plugin from the current GitHub location into your BusinessStudio workspace. While the monitoring metrics provided out-of-the-box by TCI are sufficient for most scenarios, there are hybrid connectivity use-cases (application running on-prem and microservices running on your own cluster that could be on a private or public cloud) that might require a unified single-pane view of monitoring.

#Tibco bw process monitor plus

TCI has its own embedded monitoring tools (shown below) to provide insights into Memory and CPU utilization, plus network throughput, which is very useful.

Isn’t it magical? Yes, it is! As explained in my previous post related to Prometheus integration with BWCE, which allows you to customize your base images, TCI allows integration with Prometheus in a slightly different manner. You need your packaged application (a.k.a EAR) and manifest.json - both generated by the product to simply deploy the application. TCI is TIBCO’s iPaaS and primarily hides the application management complexity of an app from users. In this post, I will explain steps to leverage Prometheus for integrating with applications running on TIBCO Cloud Integration (TCI). Prometheus is one of the most widely used solutions to monitor your microservices inside a Kubernetes cluster.

#Tibco bw process monitor how to

In previous posts, I’ve explained how to integrate TIBCO BusinessWorks 6.x / BusinessWorks Container Edition (BWCE) applications with Prometheus, one of the most popular monitoring systems for cloud layers.