Step 9: Build the App Binary or Push the app to the TIBCO Cloud
After you have created your app, you can build it anytime. When you build the app, its deployable artifact gets created. You can download it to your local machine. Each operating system has its build target. Select the right target for your operating system when building the app. You can use the built artifact to run the app.
Building the app binary
Read the Considerations.
- Procedure
- Open the Apps page.
- Click the app for which you want to build an app executable. The page for the selected app opens.
- On the page that opens, click Validate and resolve errors if any.
- Open the shortcut
menu, click Build app, and select a build target option that is compatible with your operating system (such as Darwin/amd64 for Macintosh).
Note: If you have created or pushed an app using tibcli or platform API, the Build App option is not displayed as the apps are read-only.The following build target options are available:
- Macintosh: Darwin/amd64
- 64-bit Linux: Linux/amd64
- 32-bit Linux: Linux/x86
- Microsoft Windows: Windows/amd64
The app begins to build. When it is built, the deployable artifact is downloaded to your local machine. -
To confirm whether the app executable is built successfully, go to the History tab and check whether Action is displayed as APP BUILD.
Running the App
- Open a terminal.
- Run:
- Run:
chmod +x <app-file-name>
./<app-file-name>
On Microsoft Windows
At the command prompt, run:
app-file-name.exe
The other way to use the built app is to push it to TIBCO Cloud.
Pushing your app to TIBCO Cloud
Click the back arrow on the top-left corner or click the Apps tab to open the app details page and then, click Push.

After the app has finished deploying, you see the following status:

The app is in the stopped state as there are no instances of the app running. To run the app, hover over the zero to display the up and down arrows above and below it. Click the up arrow above the zero such that the zero turns to 1, and click Scale. You see the running status once the instance starts.
