Supported resources in imported BAR files

When you deploy an integration solution that you developed in IBM® App Connect Enterprise Toolkit, ensure that the resources and message flow nodes in your integration are supported in App Connect Enterprise as a Service.

For current known limitations in App Connect Enterprise as a Service, see Known limitations.

Supported features

  • A BAR file that you deploy to App Connect Enterprise as a Service can contain message flows in the following container projects.
    • Applications
    • Integration services
    • REST APIs
    • Applications, integration services, or REST APIs that reference shared libraries
    • Applications, integration services, or REST APIs that include static libraries
  • All discovery connectors in the IBM App Connect Enterprise Toolkit are supported in App Connect Enterprise as a Service.
  • Most message flow nodes are supported. For a list of nodes that aren't supported, see Resources that are not supported in imported BAR files. For a list of nodes that have restrictions, see Message flow nodes with restrictions.
  • BAR files that you deploy to App Connect Enterprise as a Service must be self-contained, and can't reference libraries in other BAR files. Therefore, when you create your BAR file, you must add referenced shared libraries to the BAR file.
  • You can deploy subflow user-defined nodes from App Connect Enterprise 12.0.2.0 and later by adding the node to a shared library in the BAR file.
  • BAR files that you deploy to App Connect Enterprise as a Service can be a maximum of 50 MB.
  • If message flows interact with on-premises systems like databases or IBM MQ, you provide details to access your on-premises systems by configuring a private network connection and adding configurations when you deploy your BAR file. For more information, see Connecting to a private network.
  • If you use callable flows to share flow processing between App Connect Enterprise as a Service and App Connect Enterprise on premises, you must configure secure connectivity between them.

Resources that are not supported in imported BAR files

You can't include the following resources in a BAR file that you import to App Connect Enterprise as a Service.

  • A message flow in a BAR file that is imported to App Connect Enterprise as a Service can't coordinate XA transactions because no queue manager is associated with the integration runtime in App Connect Enterprise as a Service.
  • The following nodes.
    • .NETCompute

      The .NETCompute node is available on Windows only.

    • CDInput
    • CDOutput

      IBM Sterling C:D nodes require a local queue manager.

    • SAPInput
    • SAPReply
    • SAPRequest

      SAP nodes use SAP Java™ Connector (JCo) JAR files that must be used on the same network as SAP.

    • TCPIPServerInput
    • TCPIPServerOutput
    • TCPIPServerReceive

Message flow nodes with restrictions

Most of the remaining message flow nodes in the IBM App Connect Enterprise Toolkit are supported in |App Connect Enterprise as a Service. Restrictions apply to the following nodes.
File nodes
When you use local files in App Connect Enterprise as a Service, and don't use FTP or SFTP, only a File node can create and read the local files. In this situation, an external system can't create or read the local files. The following limitations also apply.
  • The file system can't be shared between replicas of the integration runtime.
  • The file system doesn't persist when you restart the integration runtime. If you restart the integration runtime manually, the integration runtime stops unexpectedly, or IBM restarts it for operational reasons, the file system and its contents are lost. Configure the application that uses the integration to account for this behavior.

HTTPInput node
In App Connect Enterprise as a Service, 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 service, your client must connect by using HTTPS.

JavaCompute node
In App Connect Enterprise as a Service, you can't access the global cache from JavaCompute nodes.

Mapping node
In App Connect Enterprise as a Service, you can't access databases or the global cache from Mapping nodes.

SOAPInput node
In App Connect Enterprise as a Service, 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 service, your client must connect by using HTTPS.

Nodes that need an IBM MQ queue manager
You can use event-driven message processing to control the flow of messages through your message flows by using aggregation, message collections, message sequences, and timeout nodes. These nodes need a default IBM MQ queue manager to control the system queues. (For more information, see Processing events in the IBM App Connect Enterprise documentation.)
For the following nodes that need to use a default queue manager, you can configure a remote default queue manager to control the system queues.
  • AggregateControl, AggregateReply, and AggregateRequest nodes
  • Collector nodes
  • FTEInput and FTEOutput nodes
  • Sequence and Resequence nodes
  • TimeoutNotification nodes when used in Controlled operation mode with TimeoutControl nodes
For more information, see Using a remote default queue manager in the IBM App Connect Enterprise documentation.