Supported resources in BAR files

You can use the following resources in your IBM® Integration Bus on Cloud integrations.

To add an integration to IBM Integration Bus on Cloud, you can upload a BAR file that contains message flows in the following container projects: One integration 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 are not supported

You cannot use standalone static libraries or message flows in an integration. To convert static libraries to shared libraries, see Converting a static library to a shared library in the IBM Integration Bus product documentation.

You must not include compiled message flow (.cmf) files in your BAR files. When you create a BAR file, on the Prepare tab of the BAR File editor, ensure that Compile and in-line resources is cleared.

Configurable services are not supported in IBM Integration Bus on Cloud.

You cannot use BAR files that contain patterns or message flow nodes from any of the following products:
  • IBM WebSphere Message Broker Connectivity Pack for Healthcare
  • IBM Integration Bus Healthcare Pack
  • IBM Integration Bus Retail Pack
  • IBM Integration Bus Manufacturing Pack

A message flow that is deployed to IBM Integration Bus on Cloud cannot coordinate XA transactions because no queue manager is coupled to the IBM Integration Bus servers in the cloud.

Message flow nodes that are supported (with restrictions)

Currently, you can use the following message flow nodes in your IBM Integration Bus on Cloud integrations.
  • CallableFlowAsyncInvoke
  • CallableFlowAsyncResponse
  • CallableFlowInvoke
  • CallableInput
  • CallableReply
  • Compute
  • Database
  • DatabaseInput
  • FileInput
  • FileOutput
  • Filter
  • FlowOrder
  • HTTPAsyncRequest
  • HTTPAsyncResponse
  • HTTPHeader
  • HTTPInput1
  • HTTPReply
  • HTTPRequest
  • Input
  • JavaCompute2
  • KafkaConsumer
  • KafkaProducer
  • Label
  • Mapping2
  • MQGet
  • MQInput
  • MQOutput
  • MQReply
  • Output
  • Passthrough
  • ResetContentDescriptor
  • RESTAsyncRequest
  • RESTAsyncResponse
  • RESTRequest
  • Route
  • RouteToLabel
  • SOAPAsyncRequest
  • SOAPAsyncResponse
  • SOAPEnvelope
  • SOAPExtract
  • SOAPInput1
  • SOAPReply
  • SOAPRequest
  • TCPIPClientInput
  • TCPIPClientOutput
  • Throw
  • Trace
  • TryCatch
  • Validate
  • XSLTransform
Notes:
  1. In IBM Integration Bus on Cloud, all HTTPInput and 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.
  2. In IBM Integration Bus on Cloud, you cannot access databases or the global cache from the JavaCompute or Mapping nodes.

To find out how to create a BAR file, see Creating a BAR file for IBM Integration Bus on Cloud.

Related tasks:
Exploring IBM Integration Bus on Cloud by using a sample
Getting support for IBM Integration Bus on Cloud
cl00007_.htm | Last updated 2018-12-15 07:47:00