Limitations for JRE versions in IBM App Connect Enterprise

By default, integration servers use Java 8, which is provided with IBM App Connect Enterprise. Java 11 is also supplied with IBM App Connect Enterprise 12.0.10 and later versions. You can configure each of your integration servers to use either of the supplied versions by using the ibmint specify jre command. Before you proceed, check whether any limitations apply to the message flow nodes in your deployed message flows or to the type of security that you configure:

• The Change Data Capture node is not enabled for use with Java 8 in IBM App Connect Enterprise 12.0.10.0 or later versions.
• The JavaCompute node is enabled for use with Java 11 in IBM App Connect Enterprise 12.0.10.0 and later versions, but you must test each node instance to confirm that it works before you use it in production.
• The following message flow nodes are enabled for use with Java 11 in IBM App Connect Enterprise 12.0.12.0 and later versions:
  • CICSRequest node
  • IMSRequest node
  • Mapping node
• The following message flow nodes and capabilities are not enabled for use with Java 11 in IBM App Connect Enterprise 12.0.10 or later versions:
  • CORBARequest node
  • ODMRules node
  • WebSphere Adapters nodes
  • XSLTransform node
  • WebSphere Registry and Repository
• SOAP nodes are not enabled for use with Java 11 in IBM App Connect Enterprise 12.0.10.0 or later versions.
• The global cache is not enabled for use with Java 11 in IBM App Connect Enterprise 12.0.10.0 or later versions.
• The following security methods are not enabled for use with Java 11 in IBM App Connect Enterprise 12.0.10.0 or later versions:
  • Creating a security profile for LDAP
  • Authentication, mapping, and authorization with TFIM V6.1 and TAM
  • Creating a security profile for WS-Trust V1.3 (TFIM V6.2)