Rules for 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 backup file | Can be found in BAR file | Solution |
|---|---|---|---|---|
| IIB01 | Consider a different transformation mechanism in place of .NET. | True | True |
The message flow contains an instance of a .NETInput or a .NETCompute message flow node. While IBM® App Connect Enterprise v11 software continues to support .NET, there is no support for 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 nodes, JavaCompute nodes, and Mapping nodes. |
| 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 v10, and it was removed from IBM App Connect Enterprise v11. Other message flow nodes are available for transformation, such as Compute nodes, JavaCompute nodes, 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 v11 does not support the SCA message flow nodes that were available in IBM Integration Bus v10. HTTP, IBM MQ, or JMS are all still viable transport options 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 v11.0.0.8 provides a new replacement message flow node that is called the ODMRules node. The purpose of this message flow node is to run ODM rules within the integration server. 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 rather than relying on local file integration. | True | True | The message flow contains an instance of a FileInput message flow node that relies on local file interaction and is not configured to use FTP. Although IBM App Connect Enterprise v11 continues to support reading local files with the FileInput node, for users who embrace a container-based architecture, this choice has architectural drawbacks. Consider changing your configuration to use FTP, or a more suitable messaging-based transport. |
| IIB06 | Consider your use of WebSphere Service Registry and Repository. | True | True | The message flow contains an instance of a RegistryLookup or EndpointLookup message flow node that communicates with WebSphere Service Registry and Repository. Releases before IBM App Connect Enterprise v11.0.0.7 do not support these message flow nodes. If you have an urgent need, or a simple use case, you can use the SOAP nodes for communication with WebSphere Service Registry and Repository. Alternatively, contact IBM to learn more about future plans in this area. |
| IIB07 | A Publication 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 Publication message flow node. In IBM Integration Bus v10, and in IBM App Connect Enterprise v11.0 before Fix Pack 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 as part of your move to a container-based architecture. |
| 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 IBM App Connect Enterprise before v11.0.0.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. |
| 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 IBM App Connect Enterprise before v11.0.0.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. |
| 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 IBM App Connect Enterprise before v11.0.0.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. |
| IIB11 | An AggregateControl, AggregateRequest, or AggregateReply message flow node was found. You might want to consider altering your IBM MQ topology. | True | True | The message flow contains an instance of an AggregateControl, AggregateRequest, or AggregateReply message flow node. In IBM App Connect Enterprise before v11.0.0.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. IBM App Connect Enterprise v11 also provides the Group nodes, which cater for similar aggregation use-cases but use in-memory queuing and have no IBM MQ dependency. |
| 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. In IBM App Connect Enterprise v11.0.0.4 (and earlier fix packs), the product uses a Kafka client at version 0.10.0.1. In IBM App Connect Enterprise v11.0.0.5 (and later fix packs), the product uses a Kafka client at version 2.20. You might want to change to a different client version when you consider the compatibility of your Kafka broker. |
| 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 v11. If you used configurable service definitions with these message flow nodes, you might want to consider the introduction of JDEdwards, PeopleSoft, and Siebel policy types in IBM App Connect Enterprise v11.0.0.6. |
| IIB14 | An SAPInput or SAPRequest message flow node was found. You might want to consider changing the configuration of your IBM 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 v11, where the concept of an IBM Integration Bus configurable service is replaced with an IBM App Connect Enterprise policy. When you move to a container-based architecture, consider how to make the SAP JCo libraries available to your containers and the required settings in server.conf.yaml. |
| IIB15 | A deprecated graphical mapping message flow node was found. Convert this node to the newer 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 v8.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 required TCPIP port. | True | True | The message flow contains an instance of a TCPIPServer message flow node. Consider changing your values.yaml file if you intend to use a non-default TCPIP port in your 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 v11 installation provides Node Package Manager (npm) as a convenient means of configuring the required 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. |
| 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 App Connect Enterprise v11.0.0.4 (and later) supports the use of this type of message flow node, which is used with IBM Transformation Extender v10. When you move to a container-based architecture, consider this version information. |
| 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 more easily achieved if you use client bindings rather than server bindings. |
| 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 11.0. In IBM 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 IBM App Connect Enterprise v11.0.0.8 and investigate the features that are provided by App Connect for Healthcare V5.0.0.0, as a replacement for the IBM Integration Bus Healthcare Pack. |
| IIB21 | A top-level message flow (originating in an Integration project) was found. These artifacts must be moved to the Default Application in IBM App Connect Enterprise v11. | True | True | A top-level message flow (originating in an Integration project) was found. When they are migrated by using the mqsiextractcomponents command, all top-level artifacts are moved to the Default Application in IBM App Connect Enterprise v11. Ensure that you consider the groupings that you require for all top-level resources. The groupings are likely to involve adopting Application projects in preference to Integration projects. Applications and Libraries (which were first introduced in WebSphere Message Broker V8) are encouraged as the preferred 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 v11, 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 (originating in an Integration project) was found. These artifacts are moved to the Default Application in IBM App Connect Enterprise v11. | 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 v11 by using the mqsiextractcomponents command. When you adopt IBM App Connect Enterprise v11, carefully consider your required groupings for all top-level resources. It is likely that the top-level resource that this rule detected is 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 IIB21, which detect top-level message flows, which 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-wide listener. | True | False | The message flow contains an instance of a SOAPInput or HTTPInput message flow node that is using the integration node-wide listener. When you run App Connect Enterprise in a container architecture, you do not use an integration node or the integration node-wide listener. Instead you use an independent integration server with its own embedded HTTP listener. |
| IIB24 | Configuration indicates the use of the Record and Replay feature. | True | False | Record and Replay was added to IBM App Connect Enterprise v11 in Fix Pack 11.0.0.4, so it is available if you want to continue to use it. Although you can run this capability in a container-based architecture, its dependence on a relational database and IBM MQ publications might be cause for consideration. |
| 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 v11 uses TLSv1.2, and IBM App Connect Enterprise v11.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 | 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. |
| IIB27 | Configuration indicates the use of the embedded global cache feature. | True | False | The embedded global cache feature was added to IBM App Connect Enterprise in Fix Pack 11.0.0.4, so it is available if you want to continue to use it. It is not advisable to use this capability to share information between integration servers in a container-based architecture; if you do, carefully consider the placement and persistence of your catalog servers. |
| IIB28 | Configuration indicates the use of the multi-instance high availability feature. | True | False | The multi-instance high availability feature for integration nodes was added to IBM App Connect Enterprise v11 in Fix Pack 11.0.0.3, so it is available if you want to continue to use it. You are unlikely to use this model to achieve high availability if you move to a container-based architecture; if you do, carefully consider the persistence and disk requirements. |
| 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 v11, 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 v11, 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 UDPs after deployment. Instead, when you change configuration data, you are likely to prefer to tear down your container and restart it with the new configuration applied. In the unlikely event that you want to dynamically update message flow UDPs after deployment, an administrative API function is available in IBM App Connect Enterprise v11.0.0.6 or later. 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. |
| 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 v11, IBM Integration Bus Activity Log configurable services are converted into IBM App Connect Enterprise Activity Log policy documents. When you move to a container-based architecture, you might want to reconsider your chosen output format for IBM App Connect Enterprise Activity Logging. |
| 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 | Although artifacts can be carried forward, due to changes in licensing, not all IBM Integration Bus software editions have direct IBM App Connect Enterprise v11 equivalents. Check with your IBM representative to ensure that you move to the appropriate IBM App Connect Enterprise edition and remain licensed correctly in future. |
| IIB33 | An IBM Integration Bus configurable service was detected that cannot be dynamically updated when converted to a policy in IBM App Connect Enterprise v11. | True | False | When you migrate, IBM Integration Bus configurable services are converted into IBM App Connect Enterprise policy documents. IBM App Connect Enterprise policy documents have several advantages, including the fact that they can be created by using Toolkit templates and deployed in a BAR file. Some policies cannot be dynamically updated (without restarting an integration server). This requirement does not usually apply in container-based architectures. However, depending on your use cases, you might want to bear this requirement in mind when you migrate to IBM App Connect Enterprise v11. |
| IIB34 | A message flow that uses an MQTT Server was found. | True | True | A message flow uses an MQTT Server, as it contains either an MQTTSubscribe or MQTTPublish message flow node. The built-in MQTT Server that is provided by IBM App Connect Enterprise v11 is not turned on by default within a container. |
| 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 some further action when data is received. You might want to revisit this design pattern when you move to a container-based architecture. IBM Integration Bus v10 can be configured to publish to MQTT the following types of information: Operational Events, Admin Events, Business Events, Flow Statistics, and Resource Statistics. IBM App Connect Enterprise v11 can be configured to publish to MQTT the following types of information: BusinessEvents, Flow Statistics, and Resource Statistics. The IBM App Connect Enterprise REST Administration API provides methods that can be called to provide operational and administration information. |