Exporting an App

Here are a few things to keep in mind before you export an app:
  • When you export an app, all the flows in your app get exported. You cannot choose the flows to export.
  • Passwords or connection details that are configured in any activities within any flow or connection in the app to be exported are removed in the exported app. Manually configure the credentials or VPN connections in the flows after importing such apps.
  • Some apps created in Project Flogo™ use the any data type. The any data type is not supported in Flogo. Such apps get imported successfully, but the element of type any gets converted into an empty object. Explicitly use the mapper to populate the empty object with member elements.
  • When an app is exported, the connections are also exported. Also, they retain the same visibility level (org level connection or user level connection).

To export an app:

    Procedure
  1. On the Apps page, click the app to open the app details page.
  2. Click the shortcut menu ().
  3. Click Export.

    Using the Export option dropdown menu, download the following:

    • App - exports a single <appname>.json file. You can use this option to download an app that you plan to import into TIBCO Cloud Integration using the drag-and-drop method.
    • TIBCO Cloud Integration artifacts - downloads two files, manifest.json, and flogo.json. The manifest.json contains the manifest details such as the endpoints, memory resource details. The flogo.json contains the app itself. These artifacts are needed to push the app directly using the TIBCO Cloud™ CLI. You must have the TIBCO Cloud™ CLI installed on your local machine to do so. Use this option to push a Flogo app to TIBCO Cloud Integration without having to import it into TIBCO Cloud Integration. See the section Pushing Apps to TIBCO Cloud for details on how to do this.