Activation Configuration for TIBCO ActiveMatrix BusinessWorks (Container Deployment) Applications

TIBCO ActiveMatrix BusinessWorks (Container Deployment) requires activation via a license in order to start. Licenses can be generated in the TIBCO Software Downloads site at https://www.tibco.com/downloads. For complete details on activating TIBCO products, see the TIBCO Activation Service documentation at https://docs.tibco.com/products/tibco-activation-service.

Important: TIBCO ActiveMatrix BusinessWorks (Container Deployment) applications will shut down when you reach the end date of your entitlement to the product, and will not restart until you replace your license file with one that contains a new entitlement end date. It is recommended that you do so well in advance of your entitlement end date to avoid business disruption.

There are two options for activating this product: In-Product Activation (local activation) and TIBCO Activation Service.

  • In-Product Activation

    There are two options for configuring In-Product Activation for containers.

      Note: For the versions prior to TIBCO ActiveMatrix BusinessWorks™ 6.12.0 HF-001, use the Environment Variable LICENSE_SOURCE instead of TIB_ACTIVATION as shown in the examples given below.

    • Volume Mounting

      • Docker: Create the baseimage and application image, and keep your license file on the local system.
        docker run -it -v <local_license_folder>:<container_location> -e TIB_ACTIVATION=<container_location> <application_image>

        Note: The default location for the license file is /home/<user>/license. If the license file is found in this location, we don't need to provide TIB_ACTIVATION. For any other location, we need to provide TIB_ACTIVATION.

      • Kubernetes: Mount your license file to deploy the BWCE application on Kubernetes.

        Note: NFS volume mounting can be used to mount the license file to deploy the application on PCF.
  • Direct Embedding

    Place the license file inside <TIBCO_HOME>/bw/<version>/docker folder, for example:
    /resources/addons/license
    While running the container (on Docker or Kubernetes), pass this location as the license source, for example:
    docker run -it -e TIB_ACTIVATION=/resources/addons/license <application_image>
    The same can be passed in the yaml file when deploying the application on Kubernetes.

TIBCO Activation Service

Note: For the versions prior to TIBCO ActiveMatrix BusinessWorks™ 6.12.0 HF-001, use the Environment Variable LICENSE_SOURCE instead of TIB_ACTIVATION as shown in the examples given below.

Install TIBCO Activation Service software and upload your license file to the running instance. Consult the TIBCO Activation Service documentation for installation instructions and to determine the URL for your running TIBCO Activation Service instance. Pass the URL as an environment variable in the form TIB_ACTIVATION=<TIBCO ACTIVATION SERVICE URL>

For example:

docker run -it -e TIB_ACTIVATION=https://gasdiproradb01.internal:7070/?fp=92cff2ad79a4b12c4078b88ad38b6be8093df2254adb40d71fc1578df28aab4e <application_image>

The URL can also be passed in the yaml file when deploying the application on Kubernetes.