If you want to deploy integration solutions that you’ve developed in IBM® App Connect Enterprise or IBM Integration Bus to the cloud, without the need to acquire and maintain an IT infrastructure, App Connect on IBM Cloud™ can help. You can import a BAR file that contains all the artifacts that make up your integration solution, then run the contents in an integration server in App Connect on IBM Cloud.

You can see your integration servers on the App Connect on IBM Cloud dashboard, alongside your event-driven flows and flows for APIs – all in one place. You can use the dashboard to view the contents of your integration servers, and you can start and stop them. A screenshot of the App Connect dashboard, showing 2 integration servers, an event-driven flow, and a flow for an API

To run your App Connect Enterprise or Integration Bus solutions in App Connect on IBM Cloud, you need to create an App Connect service in IBM Cloud (formerly Bluemix). (For more details, see https://console.bluemix.net/catalog/services/app-connect.) You also need to have App Connect Enterprise or Integration Bus installed on premises.

First, find or create everything you need:

  • An App Connect service in IBM Cloud.
  • App Connect Enterprise or Integration Bus 10.0.0.4 or later installed on premises.
  • A valid BAR file that you’ve created in the IBM App Connect Enterprise or Integration Toolkit. (See What makes a BAR file valid in App Connect on IBM Cloud?)

Next, run the contents of your BAR file in App Connect on IBM Cloud:

  1. Click New > Import a BAR file.
  2. Either click the “Import a BAR file” dialog box to select a BAR file from your file system, or drag a BAR file from your file system to the dialog box.

    If you see an authentication error, check that your BAR file is valid (See What makes a BAR file valid in App Connect on IBM Cloud?)

  3. Optional: You can edit the name if you want to (this will be the name of the integration server on the dashboard).
  4. Click Import.

    An integration server is created, and a tile is added to the dashboard to represent it. Initially, you’ll see the status as “Preparing”, which means that the contents of the BAR file are being unpacked onto the integration server. When preparation has finished, the status will show as “Stopped”, indicating that the integration server is ready to be configured and started. If you see a message saying that preparation failed, click Try again in the message to start preparation again. You can see a summary of the contents of the integration server by clicking the arrow The arrow icon that allows you to see a summary of the contents of an integration server on the tile.

  5. Open the integration server by clicking the tile, or expanding the tile menu () and then clicking Open.
  6. Configure the integration server:
  7. Optional: To split message flow processing between your on-premises environment and App Connect on IBM Cloud, configure callable flows by opening the hamburger menu Icon for hamburger menu, expanding Manage, and selecting Callable flows (see Sharing message flow processing between App Connect on IBM Cloud and App Connect Enterprise.)
  8. When you’ve completed configuration, return to the App Connect on IBM Cloud dashboard and start the integration server by opening the tile menu and then clicking Start.
  9. You can also use the tile menu to delete or update the BAR file. The “update” option allows you to upload a new version of a BAR file.
  10. When your integration server is running, you can view logs by opening the integration server and then clicking View logs. For more information, see Viewing logs for your integration servers.

If you can’t find what you want, or have comments about this tutorial, please either add comments to the bottom of this page or .

1 comment on"Running enterprise integration solutions in App Connect on IBM Cloud"

  1. Nii-Boi Kotei February 27, 2018

    We are currently at WMB V8.0.0.5 and looking into upgrading to the APP Connect or API Connect. We are looking into getting all the detail steps for migration for our review and hopefully to make a decision on which migration path to select.

Join The Discussion

Your email address will not be published. Required fields are marked *