Open topic with navigation

TIBCO® Control Plane 1.0.0

# Creating and Deploying a new App Build

Follow the steps to create and deploy a new application.

By default, the apps are configured with 0.5 CPU and 1 GB of memory.

Before you begin

You need to provision a TIBCO Flogo version capability before you can create an app. For more information, see Provisioning TIBCO Flogo.

Procedure

1. Go to the Data Plane of your choice.

2. Click Deploy an App.

   Note: Alternatively, you can click the Flogo icon on the Data Plane card. Now you can skip step 3 and follow the instructions from Step 4.

3. Click Start in the Deploy Flogo tab.

4. In the Upload Files tab, drag the `.json` or `.flogo` file into the box or click browse to upload to upload a file from your system. Then, click Next.

   Note: If you want to deploy an app created locally in Visual Studio Code, upload the `.flogo` or `.json` file available in your workspace.

5. In the Select Versions window, specify the values for the following fields:

   Field name | Description
   --- | ---
   Application Name | Fill in the name of the application. Default: The name of the app is picked from the uploaded JSON file.
   Flogo Version | Select the version of Flogo that you want to work with. Default: The latest version or provisioned version.
   Application Build Name | Displays the name of the app builds created from the application. Default: The name of the application build is picked from the uploaded JSON file.
   NameSpace | Ensure that you create a namespace before specifying it in the text box. As you type the namespace, TIBCO Flogo will autosuggest a list of existing namespaces when the app is being deployed. If you type a non existing namespace, it will suggest the commands to create it in your data plane. If the namespace is not mentioned, it chooses the default value. Default: Default namespace of the Data Plane. Note: A Data Plane can have multiple namespaces, which are linked to a service account of the respective Data Plane. To create a namespace other than the default Data Plane namespace, see Deploying App Outside Data Plane Namespace.
   Application Tags | Tag your applications to enhance searchability and categorization.
   Connectors/Custom Extensions Version | Select the version of the connector/custom extension of your choice. Default: provisioned version. Note: If no connector has been provisioned, you can use the link to provision the connector in other tab.

6. Select the End User Agreement (EUA) checkbox and click Next.

7. In the Resource Configuration window, specify the values for the following fields:

   Field name | Description
   --- | ---
   CPU Requests | An indicative integer value specifying the minimum amount of CPU resources a container requires to function optimally. CPU resources are measured in `CPU` units (Kubernetes defines 1 CPU unit as equivalent to 1 physical CPU core or 1 virtual core depending on the node type). Default: 250 m
   CPU Limits | The maximum integer amount of CPU power a container can utilize within a Pod. It acts as a hard cap, preventing the container from exceeding its designated resources and potentially impacting the performance of other Pods on the same node. CPU resources are measured in `CPU` units (Kubernetes defines 1 CPU unit as equivalent to 1 physical CPU core or 1 virtual core depending on the node type). Default: 500 m
   Memory Requests | An indicative value specifying the minimum amount of memory a container requires to function properly. Kubernetes prioritizes scheduling Pods onto nodes that have enough available memory to fulfill these requests. Fill in an integer value. Measured in memory units (commonly denoted as MiB, GiB, or TiB). Default: 512 Mi
   Memory Limits | The maximum amount of memory a container can utilize within a Pod. Fill in an integer value. Measured in memory units (commonly denoted as MiB, GiB, or TiB). Default: 1024 Mi

8. Click Deploy App.

ResultOnce the app build is created and the Flogo application is deployed on the data plane, you can click the respective boxes to view app details, view app builds, or view deployed apps.
Note: You can notice the vscode app tag for apps deployed from Visual Studio Code using the TIBCO Platform runtime.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO® Control Plane

Copyright © 2023-2024. Cloud Software Group, Inc. All Rights Reserved.