This tab allows you to create new connections, to review existing ones and to browse the list of available connectors.
This tab allows you to import new API definitions, both OpenAPI (Swagger, REST) or WSDL (Web Services). This is where you define APIs that you want to call from your flows.
You can also see all of your existing connector accounts and APIs.
Note that your connector accounts and APIs are per IBM App Connect instance. If you have more than one instance, you will need to manage your connections in each instance.
If you build flows which use the Notification capability to alert a user of something or that an action needs to be taken, this tab allows access to the current notifications.
These allow you to search your flows and also allow you to order their appearance on the dashboard
This allows you to create a new integration flow. You can do this using one of the following options:
This is where you create a new flow which is started from a connector, a callable flow (being called from another App Connect flow) or by a scheduler (timer)
This creates a new flow which is exposed as an API. Note that this is where you expose APIs that you create i.e. APIs that you want to allow other flows and applications to call. To add an API that you wish one of your flows to call, use the ‘APIs’ tab in the ‘Catalog’ tab.
If you have a flow which has been created by someone else, or you have exported the flow from this or another IBM App Connect instance, you can import it into this instance here. Note that if you already have a flow with the same definition/name another new flow will be created. These flows are imported from .yaml files which have been exported from IBM App Connect designer
This allows you to import a .bar file which has been created using the IBM App Connect Toolkit and run it in your IBM App Connect on Cloud instance. If you have a ‘Toolkit’ ‘IBM Integration Bus’ or ‘Broker’ .bar file, this is where you upload it to run it ‘on the cloud’
You can run integrations created using the IBM App Connect Toolkit on the IBM Cloud using your App Connect on Cloud instance. When you upload a .bar file using the New+ button, a new integration server is created which runs the .bar file. There is no concept of creating an integration server and adding .bar files to it – a new integration server (and tile) is created for each .bar file.
For more information see: TODO add link to ‘ACE’ section
When you create an integration flow using the IBM App Connect designer (via the New+ button), the integration flow will appear here as a tile. Each integration flow has its own tile.
Each tile indicates if a flow is running or not (stopped or started), if it has errors, whether the flow is complete and if it has had a successful run.
TODO: Add images of flow statuses.
The options are mainly self-explanatory but the following may need further discussion:
If the flow has had an error when it has run, then this will allow you to view the runtime errors. This is NOT the same as if the flow has a design/build-time error where the flow will show as ‘incomplete’ and will not be able to be started.
If your flow contains batch processing (discussed here TODO add batch link) then this allows you to see the progress of the batches and any errors within the batches.
If you wish to debug you flows by writing out logs using the log node, then you will need to enable debug logging for the debug messages to be written to the log. Enabling the debug will mean you need to restart your flow.
This allows you to export your flow definition as a text file. You can then view or store the file in a version control system or asset repository or you can import it into another IBM App Connect Instance using the ‘New+’ button on that instance.