Deploying an App using BW Provisioner

Using this method, you can deploy an application using an existing app build or newly created app build, with the Managed By BW Provisioner option from the Deploy App window, once the app build is created.

    Procedure
  1. In the App Resource Configuration window, specify the values for the following fields and click Next:
    • App Name: The default name of the application.
    • Note: The app name should not be more than 48 characters.
    • BW Profile: This displays all the profiles that are available for the application EAR file.
    • NameSpace: The target namespace where the application is deployed. If you want to use a namespace different from the default data plane namespace, see Deploying App Outside Data Plane Namespace.
    • Tags: The tags to categorize the application.
    • Execution History: Toggle the Execution History button to enable Execution History. This option is visible only when the Database Resource option is selected for the capability.
    • Service Mesh: Toggle the Service Mesh button to enable Service Mesh. This option is visible only when the Service Mesh capability is provisioned.
  2. Enable the Auto Scaling Configuration button to auto scale an application and specify the values for the following fields:  
    • Minimum Replica: The minimum number of replicas for the deployment. Hover over the number of instances. When the arrows display, change the required number of replicas.
    • Maximum Replica: The maximum number of replicas for the deployment. Hover over the number of instances. When the arrows display, change the required number of replicas.
    • Target CPU Utilization (%): The threshold for CPU Utilization of the application. By default, this variable is set to 70%. When the CPU utilization by an app running in a container exceeds the threshold that you specified, it automatically scales up or down the number of replicas. You can change the threshold values according to your app requirement.
    • Target Memory Utilization (%) The threshold for memory utilization. By default, this variable is set to 70%. When the memory utilization by an app running in a container exceeds the threshold that you specified, it automatically scales up or down the number of replicas. You can change the threshold values according to your app requirement.

      These options are available only when the Auto Scaling Configuration button is enabled.

  3. In the Resource Allocation section, specify the values for the following fields:
    • CPU Requests: The minimum guaranteed amount of CPU reserved for a container.
    • CPU Limits: The maximum guaranteed amount of CPU used by a container.
    • Memory Requests: The minimum guaranteed amount of CPU used by a container.
    • Memory Limits: The maximum guaranteed amount of memory used by a container.
      Note: Memory Requests and Memory Limits allow only integers with suffix such as Ei, Pi, Ti, Gi, Mi, Ki. For example: 1Gi
  4. Select the I have read and accepted the TIBCO End User Agreement (EUA) checkbox and click Deploy App.
ResultAfter the TIBCO BusinessWorks Container Edition application is successfully deployed on the data plane an app ID is generated. Click the respective boxes to either View Apps Details, or View App Builds, or View Deployed Apps.