Rules for the Transformation Advisor tool
When you use the Transformation Advisor tool to analyze your deployed resources, different rules apply depending on whether you back up your resources to a backup file or a BAR file.
If you plan to move your architecture to adopt containers, you can run the Transformation Advisor tool to collect data about what is deployed to your IBM® Integration Bus 10.0 or IBM App Connect Enterprise 11.0 integration node. You can then analyze the collected data for potential issues before you migrate. For more information, see Running the Transformation Advisor tool.
The following table shows the rules that apply to the Transformation Advisor tool and whether they apply to a backup file, a BAR file, or both.
| ID | Title | Can be found in a backup file | Can be found in a BAR file | Solution for IBM App Connect EnterpriseContainers | Solution for IBM App Connect Enterprise12.0 | Solution for IBM App Connect Enterprise 11.0 |
|---|---|---|---|---|---|---|
| IIB01 | Consider a different transformation mechanism in place of .NET. | True | True |
The message flow contains an instance of a .NETInput or .NETCompute message flow node. While IBM App Connect Enterprise 13.0 software continues to support .NET, it does not support running the .NET CLR when it is deployed to Linux® Docker containers on App Connect Enterprise Certified Containers. Other message flow nodes are available for transformation such as Compute, JavaCompute, and Mapping nodes. |
Rule IIB01 applies only if you plan to move your architecture to adopt containers. |
Rule IIB01 applies only if you plan to move your architecture to adopt containers. |
| IIB02 | Consider a different transformation mechanism in place of PHP. | True | True | The message flow contains an instance of a PHPCompute message flow node. The PHPCompute node was deprecated in IBM Integration Bus 10.0 and it was removed from IBM App Connect Enterprise 11.0. Other message flow nodes are available for transformation, such as Compute, JavaCompute, and Mapping nodes. | The message flow contains an instance of a PHPCompute message flow node. The PHPCompute node was deprecated in IBM Integration Bus 10.0 and it was removed from IBM App Connect Enterprise 11.0. Other message flow nodes are available for transformation, such as Compute, JavaCompute, and Mapping nodes. | The message flow contains an instance of a PHPCompute message flow node. The PHPCompute node was deprecated in IBM Integration Bus 10.0 and it was removed from IBM App Connect Enterprise 11.0. Other message flow nodes are available for transformation, such as Compute, JavaCompute, and Mapping nodes. |
| IIB03 | Consider an alternative mechanism to SCA to communicate with WebSphere Process Server. | True | True | The message flow contains an instance of an SCA message flow node (SCAInput, SCAReply, SCARequest, SCAAsyncRequest, SCAAsyncResponse). IBM App Connect Enterprise 13.0does not support the SCA message flow nodes that were available in IBM Integration Bus 10.0. HTTP, IBM MQ, or JMS transport options are available for communication between message flows and SCA components in WebSphere® Process Server. | he message flow contains an instance of an SCA message flow node (SCAInput, SCAReply, SCARequest, SCAAsyncRequest, SCAAsyncResponse). IBM App Connect Enterprise 13.0 does not support the SCA message flow nodes that were available in IBM Integration Bus 10.0. HTTP, IBM MQ, or JMS transport options are available for communication between message flows and SCA components in WebSphere Process Server. | he message flow contains an instance of an SCA message flow node (SCAInput, SCAReply, SCARequest, SCAAsyncRequest, SCAAsyncResponse). IBM App Connect Enterprise 13.0 does not support the SCA message flow nodes that were available in IBM Integration Bus 10.0. HTTP, IBM MQ, or JMS transport options are available for communication between message flows and SCA components in WebSphere Process Server |
| IIB04 | Consider a different mechanism to run IBM Operational Decision Management Business Rules. | True | True | The message flow contains an instance of a DecisionService message flow node. IBM App Connect Enterprise 13.0 provides a replacement message flow node, the ODMRules node. The purpose of this node is to run ODM rules in the integration server. Alternatively, you can use the ODM SOAP or REST API to run business rules in the ODM engine. | The message flow contains an instance of a DecisionService message flow node. IBM App Connect Enterprise 13.0 provides a replacement message flow node, the ODMRules node. The purpose of this node is to run ODM rules in the integration server. Alternatively, you can use the ODM SOAP or REST API to run business rules in the ODM engine. | The message flow contains an instance of a DecisionService message flow node. IBM App Connect Enterprise 13.0 provides a replacement message flow node, the ODMRules node. The purpose of this node is to run ODM rules in the integration server. The new ODMRules node in IBM App Connect Enterprise 11.0.0.8 is classified as Technology Preview Code. Alternatively, you can use the ODM SOAP or REST API to start the execution of business rules in the ODM engine. |
| IIB05 | Consider a different protocol instead of relying on local file integration. | True | True | The message flow contains an instance of a message flow node that relies on local file interaction, and is not configured to use FTP. Although IBM App Connect Enterprise 13.0 continues to support local files with the FileInput node, if you want to use a container-based architecture, this choice has architectural drawbacks. Consider changing your configuration to use FTP or a more suitable messaging-based transport. | Rule IIB05 applies only if you plan to move your architecture to adopt containers. | Rule IIB05 applies only if you plan to move your architecture to adopt containers. |
| IIB06 | Consider your use of WebSphere Service Registry and Repository. | True | True |
Rule IIB06 does not apply if you are migrating to IBM App Connect Enterprise 13.0 or if you plan to move your architecture to adopt containers. Rule IIB06 applies only if you want to use releases before App Connect Enterprise 11.0.0.7. |
Rule IIB06 does not apply if you are migrating to IBM App Connect Enterprise 13.0 or if you plan to move your architecture to adopt containers. Rule IIB06 applies only if you want to use releases before App Connect Enterprise 11.0.0.7. |
The message flow contains an instance of a Registry Lookup or Endpoint Lookup message flow nodes that communicate with the WebSphere Service Registry and Repository. Releases before App Connect Enterprise do not support these message flow nodes. If you have an urgent need, or a simple use case, you can use SOAP nodes for communication with the WebSphere Service Registry and Repository. Alternatively, contact IBM to learn about plans in this area. |
| IIB07 | A MQPublication message flow node was found. You might want to consider altering your IBM MQ topology. | True | True | The message flow contains an instance of a MQPublication message flow node. In IBM Integration Bus 10.0, this message flow node requires a local server binding connection to an IBM MQ queue manager. IBM App Connect Enterprise 13.0 supports the Publication node by using a remote client connection to an IBM MQ queue manager. Consider altering your IBM MQ topology if you are moving your environment to a container-based architecture. | The message flow contains an instance of a MQPublication message flow node. In IBM Integration Bus 10.0, this message flow node requires a local server binding connection to an IBM MQ queue manager. IBM App Connect Enterprise 13.0 supports the Publication node by using a remote client connection to an IBM MQ queue manager. Consider altering your IBM MQ topology if you are migrating to IBM App Connect Enterprise 13.0 . |
The message flow contains an instance of a MQPublication message flow node. In IBM Integration Bus v10, and in IBM App Connect Enterprise before v11.0.0.6, this message flow node requires a local server binding connection to an IBM MQ Queue Manager. "IBM App Connect Enterprise v11.0.0.6 supports the Publication node by using a remote client connection to an IBM MQ Queue Manager. Consider altering your IBM MQ topology." |
| IIB08 | A Sequence or Resequence message flow node was found. Consider altering your IBM MQ topology. | True | True | The message flow contains an instance of a Sequence or Resequence message flow node. In versions of IBM App Connect Enterprise 11.0 before Fix Pack 7, this message flow node requires a local server binding connection to an IBM MQ queue manager. Consider altering your IBM MQ topology as part of your move to a container-based architecture. | Rule IIB08 applies only if you plan to move your architecture to adopt containers. | Rule IIB08 applies only if you plan to move your architecture to adopt containers. |
| IIB09 | A Collector message flow node was found. Consider altering your IBM MQ topology. | True | True | The message flow contains an instance of a Collector message flow node. In versions of IBM App Connect Enterprise 11.0 before Fix Pack 7, this message flow node requires a local server binding connection to an IBM MQ queue manager. Consider altering your IBM MQ topology as part of your move to a container-based architecture. | Rule IIB09 applies only if you plan to move your architecture to adopt containers. | Rule IIB09 applies only if you plan to move your architecture to adopt containers. |
| IIB10 | A TimeoutControl or TimeoutNotification message flow node was found. You might want to consider altering your IBM MQ topology. | True | True | The message flow contains an instance of a TimeoutControl or TimeoutNotification message flow node. In versions of IBM App Connect Enterprise 11.0 before Fix Pack 7, these message flow nodes require a local server binding connection to an IBM MQ Queue Manager. Consider altering your IBM MQ topology as part of your move to a container-based architecture. |
Rule IIB10 applies only if you plan to move your architecture to adopt containers. |
Rule IIB10 applies only if you plan to move your architecture to adopt containers. |
| IIB11 | An AggregateControl, AggregateRequest, or AggregateReply message flow node was found. You might want to consider altering your IBM MQ topology. | True | True | Rule IIB11 applies only if you plan to move your architecture to adopt containers. The message flow contains an instance of an AggregateControl, AggregateRequest, or AggregateReply message flow node. In versions of IBM App Connect Enterprise 11.0 before Fix Pack 7, these message flow nodes require a local server binding connection to an IBM MQ queue manager. Consider altering your IBM MQ topology as part of your move to a container-based architecture. In IBM App Connect Enterprise 13.0 the Group nodes are suitable for similar aggregation use-cases but they use in-memory queuing and have no IBM MQ dependency. |
Rule IIB11 applies only if you plan to move your architecture to adopt containers. | Rule IIB11 applies only if you plan to move your architecture to adopt containers. |
| IIB12 | A KafkaConsumer or KafkaProducer message flow node was found. You might want to consider changing the version of your Kafka broker. | True | True |
The message flow contains an instance of a KafkaConsumer or KafkaProducer message flow node. Different releases of IBM App Connect Enterprise (both IBM App Connect Enterprise 11.0 fix packs and IBM App Connect Enterprise 13.0 mod releases) contain different Kafka client versions. To ensure compatibility, you must consult the IBM App Connect Enterprise support pages to find out which Kafka client version is included. To find out the Kafka client version that is embedded in any particular IBM App Connect Enterprise release, the support page URL varies slightly but follows a common pattern such as https://www.ibm.com/support/pages/download-ibm-app-connect-enterprise-12010. On the support page, expand the section that is entitled "Embedded components and versions that are included in this release." |
The message flow contains an instance of a KafkaConsumer or KafkaProducer message flow node. Different releases of IBM App Connect Enterprise (both IBM App Connect Enterprise 11.0 fix packs and IBM App Connect Enterprise 13.0 mod releases) contain different Kafka client versions. To ensure compatibility, you must consult the IBM App Connect Enterprise support pages to find out which Kafka client version is included. To find out the Kafka client version that is embedded in any particular IBM App Connect Enterprise release, the support page URL varies slightly but follows a common pattern such as https://www.ibm.com/support/pages/download-ibm-app-connect-enterprise-12010. On the support page, expand the section that is entitled "Embedded components and versions that are included in this release." |
The message flow contains an instance of a KafkaConsumer or KafkaProducer message flow node. Different releases of IBM App Connect Enterprise (both IBM App Connect Enterprise 11.0 fix packs and IBM App Connect Enterprise 13.0 mod releases) contain different Kafka client versions. To ensure compatibility, you must consult the IBM App Connect Enterprise support pages to find out which Kafka client version is included. To find out the Kafka client version that is embedded in any particular IBM App Connect Enterprise release, the support page URL varies slightly but follows a common pattern such as https://www.ibm.com/support/pages/download-ibm-app-connect-enterprise-12010. On the support page, expand the section that is entitled "Embedded components and versions that are included in this release." |
| IIB13 | A JDEdwardsInput, JDEdwardsRequest, PeopleSoftInput, PeopleSoftRequest, SiebelInput, or SiebelRequest message flow node was found. You might want to consider the version of your App Connect Enterprise installation. | True | True | The message flow contains an instance of a JDEdwardsInput, JDEdwardsRequest, PeopleSoftInput, PeopleSoftRequest, SiebelInput, or SiebelRequest message flow node. These message flow nodes are also supported in IBM App Connect Enterprise 13.0. If you used configurable service definitions with these message flow nodes in IBM Integration Bus 10.0, you might want to consider the introduction of JDEdwards, PeopleSoft, and Siebel policy types in IBM App Connect Enterprise 13.0. | The message flow contains an instance of a JDEdwardsInput, JDEdwardsRequest, PeopleSoftInput, PeopleSoftRequest, SiebelInput, or SiebelRequest message flow node. These message flow nodes are also supported in IBM App Connect Enterprise 13.0. If you used configurable service definitions with these message flow nodes in IBM Integration Bus 10.0, you might want to consider the introduction of JDEdwards, PeopleSoft, and Siebel policy types in IBM App Connect Enterprise 13.0. | The message flow contains an instance of a JDEdwardsInput, JDEdwardsRequest, PeopleSoftInput, PeopleSoftRequest, SiebelInput, or SiebelRequest message flow node. These message flow nodes are also supported in IBM App Connect Enterprise 11.0. If you used configurable service definitions with these message flow nodes in IBM Integration Bus 10.0, you might want to consider the introduction of JDEdwards, PeopleSoft, and Siebel policy types in IBM App Connect Enterprise 11.0.0.6. |
| IIB14 | An SAPInput or SAPRequest message flow node was found. You might want to consider changing the configuration of your App Connect Enterprise installation. | True | True | The message flow contains an instance of an SAPInput or SAPRequest message flow node. These message flow nodes are also supported in IBM App Connect Enterprise 13.0, but the concept of IBM Integration Bus configurable services are replaced with IBM App Connect Enterprise policies. When you move to a container-based architecture, consider how to make the SAP JCo libraries available to your containers and the settings in the server.conf.yaml configuration file. | The message flow contains an instance of an SAPInput or SAPRequest message flow node. These message flow nodes are also supported in IBM App Connect Enterprise 13.0, but the concept of IBM Integration Bus configurable services are replaced with IBM App Connect Enterprise policies. When you move to IBM App Connect Enterprise 13.0, consider the differences between configurable services and policies. | The message flow contains an instance of an SAPInput or SAPRequest message flow node. These message flow nodes are also supported in IBM App Connect Enterprise 11.0, but the concept of IBM Integration Bus configurable services are replaced with IBM App Connect Enterprise policies. When you move to IBM App Connect Enterprise 11.0, consider the differences between configurable services and policies. |
| IIB15 | A deprecated graphical mapping message flow node was found. You must convert this node to the newer style of Mapping node. | True | True | The message flow contains an instance of the old graphical mapping message flow node. This type of message flow node is no longer supported. From WebSphere Message Broker Version 8.0 onwards, you must convert message maps to graphical data maps. The Toolkit provides a conversion tool for this purpose. | The message flow contains an instance of the old graphical mapping message flow node. This type of message flow node is no longer supported. From WebSphere Message Broker Version 8.0 onwards, you must convert message maps to graphical data maps. The Toolkit provides a conversion tool for this purpose. | The message flow contains an instance of the old graphical mapping message flow node. This type of message flow node is no longer supported. From WebSphere Message Broker Version 8.0 onwards, you must convert message maps to graphical data maps. The Toolkit provides a conversion tool for this purpose. |
| IIB16 | A TCPIPServer message flow node was found. Consider altering the configuration of your containers to open the TCPIP port. | True | True | The message flow contains an instance of a TCPIPServer message flow node. If you intend to use a non-default TCPIP port in your containers, consider changing your IntegrationServer custom resource values for spec.service.ports to include your TCP/IP Ports. |
Rule IIB16 applies only if you plan to move your architecture to adopt containers. |
Rule IIB16 applies only if you plan to move your architecture to adopt containers. |
| IIB17 | A LoopBackRequest message flow node was found. Consider altering the configuration of your containers to support this node. | True | True | The message flow contains an instance of a LoopBackRequest message flow node. Your IBM App Connect Enterprise 13.0 installation provides Node Package Manager (npm) to configure the Loopback Java™ script modules to support this node. When you move to a container-based architecture, consider your build pipeline, and its abilities to configure these supporting files in your container. |
Rule IIB17 applies only if you plan to move your architecture to adopt containers. |
Rule IIB17 applies only if you plan to move your architecture to adopt containers. |
| IIB18 | A WebSphere Transformation Extender or IBM Transformation Extender message flow node was found. Consider changing the configuration of your containers to support this node. | True | True | The message flow contains an instance of a WebSphere Transformation Extender or IBM
Transformation Extender message flow node. IBM Transformation Extender 10.1.0.1 can be combined with
IBM App Connect Enterprise 12.0.1.0 (or later
releases). Consider the compatible versions of these two products. |
The message flow contains an instance of a WebSphere Transformation Extender or IBM
Transformation Extender message flow node. IBM Transformation Extender 10.1.0.1 can be combined with
IBM App Connect Enterprise 12.0.1.0 (or later
releases). Consider the compatible versions of these two products. |
The message flow contains an instance of a WebSphere Transformation Extender or IBM Transformation Extender message flow node. Consider the compatible versions of these two products., IBM Transformation Extender 10.0.0.0 can be combined with IBM App Connect Enterprise 11.0.0.4 or above, IBM Transformation Extender 10.1.0.0 can be combined with IBM App Connect Enterprise11.0.0.10 or above. |
| IIB19 | An MQInput, MQOutput, or MQGet message flow node that uses server bindings to a queue manager was found. You might want to consider changing the node to use IBM MQ Client bindings when you move to containers. | True | True | You might want to consider changing to use IBM MQ client bindings when you move to containers so that you can use smaller containers. Independently scaling the integration servers in your architecture from your queue managers is simpler to achieve if you use client bindings rather than server bindings. |
Rule IIB19 applies only if you plan to move your architecture to adopt containers. |
Rule IIB19 applies only if you plan to move your architecture to adopt containers. |
| IIB20 | A Healthcare Pack artifact is deployed to this server. | True | True | A Healthcare Pack artifact is deployed to this server. The IBM Integration Bus Healthcare Pack is not supported in IBM App Connect Enterprise 13.0. Support is provided for applications in healthcare environments through IBM App Connect for Healthcare 6.0.0.0. Consider investigating the features that are provided by IBM App Connect for Healthcare 6.0.0.0 as a replacement for IBM Integration Bus Healthcare Pack. | A Healthcare Pack artifact is deployed to this server. The IBM Integration Bus Healthcare Pack is not supported in IBM App Connect Enterprise 13.0. Support is provided for applications in healthcare environments through IBM App Connect for Healthcare 6.0.0.0. Consider investigating the features that are provided by IBM App Connect for Healthcare 6.0.0.0 as a replacement for IBM Integration Bus Healthcare Pack. | A Healthcare Pack artifact is deployed to this server. The IBM Integration Bus Healthcare Pack is not supported in IBM App Connect Enterprise 13.0. In App Connect Enterprise v11.0.0.8 (and later), support is provided for applications in healthcare environments through IBM App Connect for Healthcare v5.0.0.0. Consider upgrading to App Connect Enterprise v11.0.0.8 or later and investigate the features that are provided by App Connect for Healthcare V5.0.0.0. |
| IIB21 | A top-level message flow was found that originates in an integration project. These artifacts must be moved to the default application in IBM App Connect Enterprise 13.0. | True | True | A top-level message flow was found that originates in an integration project. When top-level resources are migrated by using the mqsiextractcomponents command, they are moved to the default application in IBM App Connect Enterprise 13.0. Ensure that you consider the groupings that you require for all top-level resources. The groupings are likely to involve the adoption of application projects instead of integration projects. Applications and libraries (which were first introduced in WebSphere Message Broker Version 8.0) provide a more efficient way to isolate and group message flows and their associated artifacts. Although BAR files that contain top-level message flows can still be deployed to IBM App Connect Enterprise 13.0, these artifacts replace previously deployed default application content on each deployment. Given this change in iterative deployment behavior, proper consideration of the required groupings of message flows is encouraged. | A top-level message flow was found that originates in an integration project. When top-level resources are migrated by using the mqsiextractcomponents command, they are moved to the default application in IBM App Connect Enterprise 13.0. Ensure that you consider the groupings that you require for all top-level resources. The groupings are likely to involve the adoption of application projects instead of integration projects. Applications and libraries (which were first introduced in WebSphere Message Broker Version 8.0) provide a more efficient way to isolate and group message flows and their associated artifacts. Although BAR files that contain top-level message flows can still be deployed to IBM App Connect Enterprise 13.0, these artifacts replace previously deployed default application content on each deployment. Given this change in iterative deployment behavior, proper consideration of the required groupings of message flows is encouraged. | A top-level message flow was found that originates in an integration project. When top-level resources are migrated by using the mqsiextractcomponents command, they are moved to the default application in IBM App Connect Enterprise 11.0, ensure that you consider the groupings that you require for all top-level resources. The groupings are likely to involve the adoption of application projects instead of integration projects. Applications and libraries (which were first introduced in WebSphere Message Broker Version 8.0) provide a more efficient way to isolate and group message flows and their associated artifacts. Although BAR files that contain top-level message flows can still be deployed to IBM App Connect Enterprise 11.0 , these artifacts replace previously deployed default application content on each deployment. Given this change in iterative deployment behavior, proper consideration of the required groupings of message flows is encouraged. |
| IIB22 | A top-level resource was found that originates in an integration project. These artifacts are moved to the default application in IBM App Connect Enterprise 13.0. | True | True | A top-level resource was found. Top-level resources are moved to the default application when they are migrated to IBM App Connect Enterprise 13.0 by using the mqsiextractcomponents command. When you migrate to IBM App Connect Enterprise 13.0, consider your groupings for all top-level resources. The top-level resource that this rule detected is likely to be a dependency of a top-level message flow. Consider which message flows depend on this resource. Group the resource so that it continues to be available to the message flow when the flow is moved from its integration project to an application project. You can look for instances of rule IIB21, which detects top-level message flows that might have a dependency on the top-level resource that is highlighted by this rule. | A top-level resource was found. Top-level resources are moved to the default application when they are migrated to IBM App Connect Enterprise 13.0 by using the mqsiextractcomponents command. When you migrate to IBM App Connect Enterprise 13.0, consider your groupings for all top-level resources. The top-level resource that this rule detected is likely to be a dependency of a top-level message flow. Consider which message flows depend on this resource. Group the resource so that it continues to be available to the message flow when the flow is moved from its integration project to an application project. You can look for instances of rule IIB21, which detects top-level message flows that might have a dependency on the top-level resource that is highlighted by this rule. | A top-level resource was found. Top-level resources are moved to the default application when they are migrated to IBM App Connect Enterprise 11.0 by using the mqsiextractcomponents command. When you migrate to IBM App Connect Enterprise 11.0, consider your groupings for all top-level resources. The top-level resource that this rule detected is likely to be a dependency of a top-level message flow. Consider which message flows depend on this resource. Group the resource so that it continues to be available to the message flow when the flow is moved from its integration project to an application project. You can look for instances of rule IIB21, which detects top-level message flows that might have a dependency on the top-level resource that is highlighted by this rule... |
| IIB23 | A SOAPInput or HTTPInput message flow node was found that is using the integration node listener. | True | False | The message flow contains an instance of a SOAPInput or HTTPInput message flow node that is using the integration node listener. When you run App Connect Enterprise in a container architecture, you do not use an integration node or the integration node listener. Instead, you use an independent integration server with its own embedded HTTP listener. |
Rule IIB23 applies only if you plan to move your architecture to adopt containers. |
Rule IIB23 applies only if you plan to move your architecture to adopt containers. |
| IIB24 | Configuration indicates the use of the Record and Replay feature. | True | False |
Rule IIB24 applies only if you plan to move your architecture to adopt containers. Record and Replay can be used in a container-based architecture. However its dependence on a relational database and IBM MQ publications might be a cause for consideration. |
Rule IIB24 applies only if you plan to move your architecture to adopt containers. |
Rule IIB24 applies only if you plan to move your architecture to adopt containers. |
| IIB25 | A SOAPInput or HTTPInput message flow node that uses HTTPS was found. | True | True | The message flow contains an instance of a SOAPInput or HTTPInput message flow node that is using HTTPS. IBM App Connect Enterprise 13.0 uses TLSv1.2, and can also use TLSv1.3 for inbound HTTPS communications. Ensure that TLSv1.2, or TLSv1.3, are acceptable to your Business Partner applications. | The message flow contains an instance of a SOAPInput or HTTPInput message flow node that is using HTTPS. IBM App Connect Enterprise 13.0 uses TLSv1.2, and can also use TLSv1.3 for inbound HTTPS communications. Ensure that TLSv1.2, or TLSv1.3, are acceptable to your Business Partner applications. | The message flow contains an instance of a SOAPInput or HTTPInput message flow node that is using HTTPS. IBM App Connect Enterprise11.0 uses TLSv1.2, and cIBM App Connect Enterprise 2.0.0.5 or later can also use TLSv1.3 for inbound HTTPS communications. Ensure that TLSv1.2, or TLSv1.3, are acceptable to your Business Partner applications. |
| IIB26 | A globally coordinated message flow was found. | True | True | Rule IIB26 applies only if you plan to move your architecture to adopt containers. A globally coordinated message flow was detected. When you adopt a container-based architecture, you are unlikely to want to use globally coordinated message flows in your containers. You might want to reconsider your architecture to avoid global coordination, or to enable these flows to keep running outside containers. |
Rule IIB26 applies only if you plan to move your architecture to adopt containers. |
Rule IIB26 applies only if you plan to move your architecture to adopt containers. |
| IIB27 | The configuration indicates the use of the embedded global cache feature. | True | False | It is not advisable to use this capability to share information between integration servers in a container-based architecture. If you do use this capability, consider the placement and persistence of your catalog servers. |
Rule IIB27 applies only if you plan to move your architecture to adopt containers. |
Rule IIB27 applies only if you plan to move your architecture to adopt containers. |
| IIB28 | Configuration indicates the use of the multi-instance high availability feature. | True | False | You are unlikely to use this model to achieve high availability if you move to a container-based architecture. If you do use this model, consider the persistence and disk requirements. |
Rule IIB28 applies only if you plan to move your architecture to adopt containers. |
Rule IIB28 applies only if you plan to move your architecture to adopt containers. |
| IIB29 | An MRM message set dictionary was detected. | True | True | An MRM message set dictionary was detected. These artifacts are supported for use in IBM App Connect Enterprise 13.0, but you are advised to consider converting to use the superior DFDL message modeling technology. | An MRM message set dictionary was detected. These artifacts are supported for use in IBM App Connect Enterprise 13.0, but you are advised to consider converting to use the superior DFDL message modeling technology. | An MRM message set dictionary was detected. These artifacts are supported for use in IBM App Connect Enterprise 11.0, but you are advised to consider converting to use the superior DFDL message modeling technology. |
| IIB30 | A message flow with user-defined properties was found. | True | True | A message flow with user-defined properties was detected. Message flows can continue to use user-defined properties when deployed to IBM App Connect Enterprise 13.0, so this message is for information only. If you are moving to a container architecture, you will probably not want to dynamically change the value of user-defined properties after deployment. Instead, when you change configuration data, you are likely to stop your container and restart it with the new configuration applied. In the unlikely event that you want to dynamically update message flow user-defined properties after deployment, an administrative API function is available in IBM App Connect Enterprise 13.0. In general, when you use container-based architectures, other methods for providing configuration to an independent integration server might be preferable, such as a user-defined policy. |
Rule IIB30 applies only if you plan to move your architecture to adopt containers. |
Rule IIB30 applies only if you plan to move your architecture to adopt containers. |
| IIB31 | An IBM Integration Bus Activity Log configurable service was detected, which wrote to local files. | True | False | When you migrate to IBM App Connect Enterprise 13.0, IBM Integration Bus Activity Log configurable services are converted into Activity Log policy documents. When you move to a container-based architecture, you might want to reconsider your chosen output format for Activity Logging. |
Rule IIB31 applies only if you plan to move your architecture to adopt containers. |
Rule IIB31 applies only if you plan to move your architecture to adopt containers. |
| IIB32 | An integration server was associated with an integration node that specified a product edition (that uses the mqsimode command) that is no longer available. | True | False | Artifacts can be carried forward but due to changes in licensing, not all IBM Integration Bus software editions have direct IBM App Connect Enterprise 13.0 equivalents. Check with your IBM representative to ensure that you move to the appropriate App Connect Enterprise edition and remain correctly licensed in the future. | Artifacts can be carried forward but due to changes in licensing, not all IBM Integration Bus software editions have direct IBM App Connect Enterprise 13.0 equivalents. Check with your IBM representative to ensure that you move to the appropriate App Connect Enterprise edition and remain correctly licensed in the future. | Artifacts can be carried forward but due to changes in licensing, not all IBM Integration Bus software editions have direct IBM App Connect Enterprise 11.0 equivalents . Check with your IBM representative to ensure that you move to the appropriate App Connect Enterprise edition and remain correctly licensed in the future. |
| IIB33 | An IBM Integration Bus configurable service was detected that cannot be updated dynamically when it is converted to a policy in IBM App Connect Enterprise 13.0. | True | False | When you migrate to IBM App Connect Enterprise 13.0, IBM Integration Bus configurable services are converted into policy documents. Policy documents have several advantages, such as they can be created by using Toolkit templates and deployed in a BAR file. Some policies cannot be updated dynamically without the need to restart an integration server. This requirement does not typically apply in container-based architectures. However, depending on your use cases, you might want to consider this requirement when you migrate to IBM App Connect Enterprise 13.0. | When you migrate to IBM App Connect Enterprise 13.0, IBM Integration Bus configurable services are converted into policy documents. Policy documents have several advantages, such as they can be created by using Toolkit templates and deployed in a BAR file. Some policies cannot be updated dynamically without the need to restart an integration server. However, depending on your use cases, you might want to consider this requirement when you migrate to IBM App Connect Enterprise 13.0 | When you migrate to IBM App Connect Enterprise 11.0, IBM Integration Bus configurable services are converted into policy documents. Policy documents have several advantages, such as they can be created by using Toolkit templates and deployed in a BAR file. Some policies cannot be updated dynamically without the need to restart an integration server. However, depending on your use cases, you might want to consider this requirement when you migrate to IBM App Connect Enterprise 11.0 |
| IIB34 | A message flow that uses an MQTT Server was found. | True | True | Rule IIB34 applies only if you plan to move your architecture to adopt containers. A message flow uses an MQTT Server because it contains either an MQTTPublish or MQTTSubscribe message flow node. The built-in MQTT Server that is provided by IBM App Connect Enterprise 13.0 is not turned on by default in a container. |
Rule IIB34 applies only if you plan to move your architecture to adopt containers. |
Rule IIB34 applies only if you plan to move your architecture to adopt containers. |
| IIB35 | A message flow that uses an MQTTSubscribe node to monitor IBM Integration Bus events was found. | True | True | A message flow contains an MQTTSubscribe message flow node with a topic root of IBM/IntegrationBus. The presence of this node might mean that you have a message flow that is designed to monitor the product itself, and to take further action when data is received. You might want to review this design pattern when you move to a container-based architecture. IBM Integration Bus 10.0 can be configured to publish the following types of information to MQTT: operational events, admin events, business events, flow statistics, and resource statistics. IBM App Connect Enterprise 13.0 can be configured to publish the following types of information to MQTT: business events, flow statistics, and resource statistics. The App Connect Enterprise REST Administration API provides methods that can be called to provide operational and administration information. | A message flow contains an MQTTSubscribe message flow node with a topic root of IBM/IntegrationBus. The presence of this node might mean that you have a message flow that is designed to monitor the product itself, and to take further action when data is received. IBM Integration Bus 10.0 can be configured to publish the following types of information to MQTT: operational events, admin events, business events, flow statistics, and resource statistics. IBM App Connect Enterprise 13.0 can be configured to publish the following types of information to MQTT: business events, flow statistics, and resource statistics. The App Connect Enterprise REST Administration API provides methods that can be called to provide operational and administration information. | A message flow contains an MQTTSubscribe message flow node with a topic root of IBM/IntegrationBus. The presence of this node might mean that you have a message flow that is designed to monitor the product itself, and to take further action when data is received. You might want to review this design pattern when you move to a container-based architecture. IBM Integration Bus 10.0 can be configured to publish the following types of information to MQTT: operational events, admin events, business events, flow statistics, and resource statistics.IBM App Connect Enterprise 11.0 can be configured to publish the following types of information to MQTT: business events, flow statistics, and resource statistics. The App Connect Enterprise REST Administration API provides methods that can be called to provide operational and administration information. In addition, with IBM App Connect Enterprise11.0.0.10 or later, the Web UI also provides a dedicated administration log to display this information, which can also be written to a file for audit purposes. |