When you import a BAR file into IBM® App Connect on IBM Cloud™, it’s validated to ensure that the contents can be run in the integration server. You can import a BAR file that contains message flows in the following container projects:

  • Applications
  • Integration services
  • Applications or integration services that reference shared libraries
  • Applications or integration services that include static libraries
  • REST APIs

One integration server contains the resources from a single BAR file. That BAR file must be self-contained, and cannot reference libraries in other BAR files. Therefore, when you create your BAR file, you must ensure that you add any referenced shared libraries to the BAR file. BAR files that you deploy to the cloud must be a maximum of 10 MB in size.

Resources that aren’t supported in BAR files on App Connect on IBM Cloud

You can’t include the following resources in a BAR file that you import to App Connect on IBM Cloud:

  • Standalone static libraries or message flows.
  • Compiled message flow (.cmf) files.

    When you create a BAR file in App Connect Enterprise, on the Prepare tab of the BAR File editor, ensure that Compile and in-line resources is cleared.

  • A message flow in a BAR file that’s imported to App Connect can’t coordinate XA transactions because no queue manager is associated with the integration server in App Connect.

Message flow nodes that are supported (with restrictions)

Currently, you can use the following message flow nodes in BAR files that you import to App Connect on IBM Cloud:

  • AppConnectRESTRequest
  • CallableFlowAsyncInvoke
  • CallableFlowAsyncResponse
  • CallableFlowInvoke
  • CallableInput
  • CallableReply
  • Compute
  • Database
  • DatabaseInput
  • EmailInput
  • EmailOutput
  • File

    (In App Connect on IBM Cloud, you can use file nodes when you use FTP or SFTP transport only.)

  • FileInput
  • FileOutput
  • Filter
  • FlowOrder
  • GroupComplete
  • GroupGather
  • GroupScatter
  • HTTPAsyncRequest
  • HTTPAsyncResponse
  • HTTPHeader
  • HTTPInput

    (In App Connect on IBM Cloud, HTTPInput nodes use HTTP over TLS (HTTPS), even if the Use HTTPS property on the node is cleared. Therefore, when you interact with these nodes in the cloud, your client must connect by using HTTPS.)

  • HTTPReply
  • HTTPRequest
  • Input
  • JavaCompute

    (In App Connect on IBM Cloud, you can’t access databases or the global cache from JavaCompute nodes.)

  • KafkaConsumer
  • KafkaProducer
  • Label
  • Mapping

    (In App Connect on IBM Cloud, you can’t access databases or the global cache from Mapping nodes.)

  • MQGet
  • MQInput
  • MQOutput
  • MQReply
  • MQTT
  • Output
  • Passthrough
  • ResetContentDescriptor
  • RESTAsyncRequest
  • RESTAsyncResponse
  • RESTRequest
  • Route
  • RouteToLabel
  • SOAPAsyncRequest
  • SOAPAsyncResponse
  • SOAPEnvelope
  • SOAPExtract
  • SOAPInput

    (In App Connect on IBM Cloud, SOAPInput nodes use HTTP over TLS (HTTPS), even if the Use HTTPS property on the node is cleared. Therefore, when you interact with these nodes in the cloud, your client must connect by using HTTPS.)

  • SOAPReply
  • SOAPRequest
  • TCPIPClientInput
  • TCPIPClientOutput
  • TCPIPClientRequest
  • Throw
  • Trace
  • TryCatch
  • Validate
  • XSLTransform

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

Join The Discussion

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