Provisioning TIBCO BusinessWorks Container Edition Capability

You can provision the TIBCO BusinessWorks™ Container Edition capability from TIBCO Control Plane. To provision the TIBCO BusinessWorks Container Edition capability, ensure that you have a registered data plane in TIBCO Control Plane. For more information, see Registering a Data Plane.

TIBCO BusinessWorks Container Edition is an integration product suite for enterprise, web, and mobile applications. You can provision the TIBCO BusinessWorks Container Edition capability to deploy, manage, and monitor TIBCO BusinessWorks Container Edition applications by TIBCO Control Plane.

For more information on TIBCO BusinessWorks Container Edition, see TIBCO BusinessWorks Container Edition Documentation.

Before you begin
  • Ensure that the Nginx Ingress Controller is deployed with a valid domain name. For more information, see Ingress Controller.

  • Create a data plane by following the registration steps. For more information, see Registering a Data Plane.

    Procedure
  1. In the TIBCO Control Plane, click Data Planes from the left navigation.
  2. On the Data Plane card, click Go to Data Plane.
  3. Click Provision a Capability.
  4. On the Provision TIBCO BusinessWorks™ Container Edition card, click Start.
  5. Select the required Storage Class, Ingress Controller, and Database Resource to provision capability. If there is no existing resource, you can add a resource. For more information about resources, see Managing Resources.
  6. Click Next.
  7. Add the path prefix in the Path Prefix textbox for the ingress resource that is used for provisioning public APIs.
  8. To enable the Auto Discover BWCE Apps option, use the toggle button.
    Note: This is a Preview feature. By using the Auto Discovery feature, you can fetch your existing BWCE apps from the same K8s cluster deployed using the Helm chart and monitor those applications from TIBCO Control Plane UI. Application resources must have the following required labels:
    • deployment: app.kubernetes.io/instance=<app-name> and any labels used to configure discoverability
    • pod: app.kubernetes.io/instance=<app-name>
    • service: app.kubernetes.io/instance=<app-name>
    By default, the Auto Discover BWCE Apps option is disabled.
    Note: Only monitoring is supported for autodiscovered apps.
    On enabling this option, Namespace Label Selector Expressions option is activated. By default, the Engine Port is set to the value 8090. You can customize this value, as required.

    Also, you can add a new expression by specifying the Namespace and the Label Selector Expression. Execute the commands as shown in the UI to manage the Namespace.

  9. To disable the fluentbit sidecar deployment for TIBCO BusinessWorks Container Edition applications, toggle off the The Deployment of fluenbit sidecar for Application logs button. By default, this button is enabled.
  10. The Enable Execution History button is enabled only if the Data Resource is option is selected.
  11. Select the EULA checkbox to accept the End-User License Agreement.
  12. Click BWCE Provision Capability. It takes some time to provision the capability.
ResultYou can see that the Capability card is added on the Data Plane details page. If the capability provisioning is successful, you can see the status on the card as green.

What to do nextAfter the capability is provisioned, you can start deploying applications.