Foundations & Core Principles

The TIBCO Platform reimagines the BW5 architecture for the modern cloud. While the core engine remains consistent to ensure backward compatibility, the management layer has shifted:

• Infrastructure Shift: Traditional components like TIBCO Administrator, Hawk Domains, and TIBCO Runtime Agent (TRA) are replaced by Kubernetes-native constructs.

• Self-Healing: Kubernetes Deployment objects replace legacy Fault Tolerant (FT) groups. The Control Plane leverages Kubernetes to automatically restart failed pods or reschedule them.

• Unified Management: The Control Plane acts as a single pane of glass for BW5, BWCE, and Flogo, providing a "Control Tower" view across hybrid environments (on-prem and containerized).

Deployment Strategy & Prioritization

Not all BW5 patterns are equal in a container environment. TIBCO recommends a phased "Wave" approach based on workload characteristics:

• Priority 1 (Stateless & Service-Oriented): Focus on SOAP, REST, or HTTP services and JMS-based messaging. These are the easiest to containerize as they are typically stateless and use standard protocols.

• Priority 2 (Batch & Basic Adapters): Scheduled or batch processes that previously ran in Active-Passive mode can now run in single-instance mode, relying on Kubernetes self-healing.

• Priority 3 (Complex Ecosystems): Includes applications using Checkpointing (Database-driven) or File Management. These require consideration for shared storage or external DB dependencies.

• Priority 4 (Legacy/Monolithic): Custom patterns or those with heavy Rendezvous (RV) dependencies may require deconstruction into smaller services or a hybrid approach where some components remain on-prem.

To successfully deploy TIBCO BusinessWorks 5 in a containerized environment managed by the Control Plane, follow these strategic steps:

1. Assess Compatibility: Identify stateless workloads for the initial migration phase.

   • Review plugins and adapters; ensure they are supported in the containerized runtime.

2. Establish Foundations:

   • Provision the TIBCO Control Plane and register a Data Plane (Kubernetes cluster).

   • Configure CI/CD pipelines and Observability settings (OpenTelemetry) within the Platform.

3. Refactor for Cloud-Native (Where Necessary):

   • Replace FT Group configurations with Kubernetes Deployment manifests.

   • Ensure Checkpoints and Shared Variables are configured to use an external Database rather than local storage.

   • Switch from TIBCO Rendezvous to TIBCO EMS or other modern protocols (Kafka/Pulsar) if communication needs to span across different pods.

4. Iterative Onboarding:

   • Deploy applications in "waves," starting with Priority 1 services.

   • Use the Control Plane to monitor performance and visualize process diagrams for troubleshooting.

5. Optimization:

   • Post-migration, optimize applications by leveraging Horizontal Pod Autoscaling (HPA) to handle peak loads dynamically.
     
     
     For more details refer TIBCO BusinessWorks 5 Containers: Strategy for Deployment

Resources

• TIBCO BusinessWorks 5 Containers: Foundations and Principles

• TIBCO BusinessWorks 5 Containers: Strategy for Deployment

• TIBCO BusinessWorks 5 Containers: Benefits and New Capabilities

• Product Docs

If there are any additional questions or queries, please reach out to the Integration Product Management Team at integration-pm@tibco.com.

Foundations and Deployment Strategy for TIBCO BusinessWorks™ 5 in Containers via TIBCO Platform – Control Plane

TIBCO BusinessWorks 5 (BW5) is now supported as a containerized runtime within the TIBCO Platform. This allows organizations to run existing BW5 applications on Kubernetes while managing them through the TIBCO Control Plane. By transitioning to a containerized model, BW5 applications benefit from cloud-native principles—such as self-healing, elastic scaling, and unified observability—without requiring a full rewrite of the integration logic.