In todays modern DevOps and CI/CD environments container platforms such as Docker, rkt, LXD or OpenVZ have significantly improved productivity of IT departments. Continues delivery, a discipline which enables rapid release cycles in production environments, has experienced a dramatic increase in acceptance across the industries and is heavily relying on the features of containerized runtime stacks. There probably is not a single cloud based service not relying on the powerful features and benefits of such environments.

Our customers expect an ever increasing productivity in solution delivery. In the era of an API economy, where the success of businesses is directly linked to their ability to deliver value via the means of a publicly accessible and easily consumable programming interface, the pressure is on IT to deliver robust and feature rich solutions more rapidly.

Operational Aspects of Cloud Based Services

The providers of API platforms, such as TIBCO Software with their amazing TIBCO BusinessWorks 6, embrace the change in the market and enabled their tools to seamlessly operate in such environments. However, it is not good enough to make an existing software compatible with a new runtime environment. Also the ecosystem surrounding such new technologies has to be considered.

Containerized and deployed in the cloud software solutions no longer can expect to have local, persistent storage for configuration or log data. In these environments other services are required to provide such functionality. For example Zuul, Spring Cloud Config, Github or Consul are getting used to provide cloud based configuration management; TIBCO LogLogic, Splunk, Papertrail and the almighty Elastic Stack take care of log files.

Finally, the management of these dynamic environments, where services auto scale up and down and transparently fail over so that users virtually never experience downtimes, needs to foster this change. Container orchestration solution like Docker Swarm, Kubernetes and Nomad are added to the landscape to provide an infrastructure overview and enable management of the deployed applications.

Monitoring of Business Processes

Having sorted out the development, deployment and operational aspects in this brave new world, it becomes more important to understand the status of a certain business process and how well it has been executed. And it is exactly that very business process nJAMS looks after; its outcome, its performance, its well-being.

nJAMS is monitoring executions within TIBCO BusinessWorks Container Edition since the latter’s very first release back in 2015. However, we always felt that simply providing a technical compatibility can only be the first step. The entire nJAMS experience must seamlessly fit into our customers’ DevOps and CI/CD strategy and the tool chain laid out above. That’s why we carefully listen to the power houses of applied container technology – luckily our customer base has a few of them.

Configuring nJAMS Client for BWCE

So – you probably read all this because you are looking for the step-by-step guide for configuring nJAMS to work with TIBCO BusinessWorks Container Edition in a Docker environment. And still the article does not show any indication on how to actually do it. Well, that’s simply because we believe it should not be more complicated than this:

docker build –t tibco/bwce-with-njams

That’s right; that’s all. Once the command completes a fully configured and ready-to-use Docker image with TIBCO BusinessWorks Container Edition monitored by nJAMS is just waiting to be started. Obviously there are more advances configuration options available (all in the manuals) to override the default behavior of the nJAMS Client for BWCE.

In summary: nJAMS Client for BWCE is shipped with a ready-to-use Docker configuration adding nJAMS support to all your standard or customized TIBCO BusinessWorks Container Edition Docker images; it seamlessly and natively integrates into your CI/CD processes and containerized environments. Because it natively supports Docker, your teams can fully leverage all build, configuration and deployment options they are used to.

And, by the way, exactly the same nJAMS support is available for your vanilla TIBCO BusinessWorks 6, whether inside Docker or not. Obviously.

If you have any comment or further questions around our support for containers, just contact us via our Website or any of the following channels: LinkedIn, Twitter, Facebook.

About the Author: Hendrik Siegeln is co-founder and Managing Director of Integration Matters.