IBM App Connect Enterprise 12.0 release notes

• Fractional truncation error is received when using an ESQL SELECT against a PostgreSQL database table using the TIME datatype with a precision (#97005)

  App Connect Enterprose 12.0.10.0 provides an ODBC, driver which can be used by ESQL based message flow nodes to communicate with a PostgreSQL database. When interacting with a table that has columns of the TIME datatype, and which also include a precision, then a fractional truncation error is returned to the message flow. To workaround the problem, users can set a parameter (FetchTWFSasTime=1) in the odbc.ini file which will stop the PostgreSQL ODBC driver from attempting to return the fractional seconds part of the time.
• Connecting more than one Change Data Capture message flow node to the same PostgreSQL database attempts to create separate connections (#96970)
  The Change Data Capture message flow node takes its connection properties from a Change Data Capture policy. Multiple Change Data Capture message flow nodes can be configured to reuse the same policy, but at runtime each node will create its own connection. In some circumstances this can lead to behaviour which the user may not expect: For example, when connecting to PostgreSQL there is a limit of one connection allowed and when this is exceeded further connections will be denied.
• Problem with Connector Discovery for Jira and Microsoft Sharepoint input nodes (#95916)

  When you Launch Connector Discovery from a Jira or Microsoft Sharepoint message flow input node, if you have not previously provided account credentials, then the discovery process will display a page describing the endpoint system as "Not connected". You will not see a connect button, nor will you see a list of potential actions to choose from. There is no obvious way forward in the discovery process and you need to close the window and return to your Toolkit workspace. There are two alternative workarounds for the problem:
  1. Before you launch connector discovery, use the mqsicredentials command to define your Jira or Microsoft Sharepoint credentials to your vault, and create a policy that links to those credentials. When you launch connector discovery, the defined credentials and policy will be used and the list of available actions you can choose from will be displayed.
  2. Before launching connector discovery, provide the credentials and policy information by launching from the menu File > New > Discovery Connector policies and credentials. You can then return to Launch Connector Discovery from the message flow input node and progress as normal.This issue is fixed in IBM App Connect Enterprise 12.0.10.0
• The integration node vault does not allow credentials to be updated while the integration node is running. (#95848)
  In App Connect Enterprise 12.0.9.0, the credentials in an integration node's vault are shared between the integration node, the node-wide HTTP Listener, and the integration servers that are owned by the node. If you update a credential by using the mqsicredential command, then the request is rejected, even though the vault technology is capable of allowing the vault to be locked for access while the update is happening. To work around this issue, stop the integration node, make the update to the credential, and restart the integration node.This issue is fixed in IBM App Connect Enterprise 12.0.10.0
• For integration servers that use an External Directory Vault, discovery connector nodes do not persist OAuth token updates to disk (#96120)
  In App Connect Enterprise 12.0.9.0, message flows that contain discovery connectors that use OAuth when they communicate with endpoint systems, incorrectly just store the updates in memory and do not persist the updated OAuth tokens to disk. If the integration server is subsquently restarted, and if the refresh token is still valid, then a new access token is generated. If the integration server is restarted and the refresh token is no longer valid, a new access token will not be generated, and connections will fail. Users can work around this problem by setting an environment variable MQSI_FORCE_TOKEN_STORE to the value "vault" before starting the integration server.  The list of connectors potentially affected by this behavior is:  anaplan, azuread, dropbox, kronos, maximo, mondaydotcom, msdynamicscrmrest, msexcel, msonedrive, msteams, mssharepoint, salesforcemc, sapariba, amazonkinesis, box, calendly, msexchange, servicenow, snowflake.This issue is fixed in IBM App Connect Enterprise 12.0.10.0
• Occasionally on Linux x86-64 the Toolkit can become unresponsive when you click a message flow node in a .msgflow file (#93923)
  When you edit a message flow, immediately after you click a message flow node on the flow canvas the Toolkit can become unresponsive. We suspect this issue is due to a race condition related to displaying hover help. The unresponsiveness occurs more regularly on heavily loaded machines, or where multiple separate Toolkit sessions are running. A work-around for this issue is not to click the message flow node immediately, but pause briefly until the hover help appears, and then click.
  This issue is fixed in IBM App Connect Enterprise 12.0.9.0
• Uninstalling App Connect Enterprise on Windows (due to long file path configuration) can result in files being left behind (#94655)

  Installations of App Connect Enterprise 12.0.8.0 that include the Discovery Connectors feature take advantage of longer file paths than previous versions of the product. Because of the longer file paths, when the product installation uses a location with a deep folder path, some files can be left behind when the product is uninstalled. This problem can occur on older versions of Windows (for example Server 2012 R2, Windows 8/8.1 and early Windows 10). These versions of Windows pre-date Windows operating system support for long file paths. The problem can also occur where long path support is deliberately switched off. You can work around this issue by manually deleting the left over files after the uninstallation completes. As this problem is outside the scope of the App Connect Enterprise product, behavior is unlikely to change in future releases but is noted here with the workaround for the benefit of our users.
• Optional filters selected during connector discovery are not persisted in the message flow for the monday.com input node (#94675)

  When you Launch Connector Discovery from a monday.com message flow input node, after you connect to the monday.com instance and after you select the trigger event and data object, you can define filters. These filters are intended to let the user control the circumstances that cause the input node to be triggered. When you use data objects named Item and Subitem, filtering options can be defined by using User IDs, Group IDs, and Subitem IDs. Although defined in the wizard these options are not being correctly saved to the message flow. As a result of not being saved, when the flow is deployed these filtering options have no effect on the monday.com events that trigger the flow.

  This issue is fixed in IBM App Connect Enterprise 12.0.9.0
• In rare circumstances, message flows with a Salesforce Input node can cause an integration server abend on Windows (#93210)

  Testing highlighted an intermittent situation where the integration server process can abend. This problem is consistently recreatable only when you use a message flow containing the Salesforce Input message flow node, on the Windows platform, and when the product is installed into the default path location. You can work around the problem by using one of the following solutions:
  1. Install the product in a slightly longer or shorter path than the default location.
  2. Specify that flows containing the Salesforce Input node are deployed in start mode manual.
  3. Disable the REST admin port of the server. 

  This issue is fixed in IBM App Connect Enterprise 12.0.6.0
• Toolkit is unable to edit an OpenAPI document and a Discovery Connector session at the same time (#492)

  In an App Connect Enterprise 12.0.5.0 Toolkit, it is possible to concurrently work on an OpenAPI document and a Discovery Connector session. This behavior regressed in App Connect Enterprise 12.0.6.0 causing a blank page to be displayed or a message stating "An error has occurred".  You can work around this issue by closing the open session and editing either the Discovery Connector settings, or the OpenAPI, one at a time.  This issue is fixed in IBM App Connect Enterprise 12.0.7.0 (concurrent editing sessions are not allowed and an error message explains what to do next.)
• Runtime reports an internal error (BIP2111E) from a message flow that contains a Discovery Connector message flow node (#91636)
  In an App Connect Enterprise 12.0.5.0 message flow, when a Discovery Connector message flow node is wired directly to an MQOutput or MQReply node, the runtime might report an internal error (BIP2111E) when it attempts to 'refreshBitStreamFromElements'. You can work around this error by wiring a Compute node into the flow after the Discovery Connector message flow node and before the IBM MQ message flow node. This wiring serves the purpose of preparing a writeBuffer ready to be used when the output message is serialized.  This issue is fixed in IBM App Connect Enterprise 12.0.6.0
• Docker Windows Silent Install options (#91571)
  When you use Docker Windows with the App Connect Enterprise 12.0.5.0 silent installation mechanism, you cannot select the installer options for Toolkit, WebSphere Service Registry and Repository nodes, Open API Editor, or Connector Discovery. These options are available with the silent installer when you are operating within traditional on-metal and VM environments (this note just applies to Docker Windows).  This issue is fixed in IBM App Connect Enterprise 12.0.6.0
• It is not possible to use Discovery Connector message flow nodes in an Integration Service subflow (#91641)
  When you use message flow nodes that rely on Connector Discovery (introduced in App Connect Enterprise 12.0.5.0), there is a problem running these nodes in the subflow of an Integration Service. You can work around this issue by using an Application with a SOAPInput node-driven message flow, and associated subflows instead.  This issue is fixed in IBM App Connect Enterprise 12.0.6.0
• With Discovery Connectors, the JSON schema files saved to the Toolkit workspace are not versioned (#368)
  When you run Connector Discovery (introduced in App Connect Enterprise 12.0.5.0), the JSON schema files that are saved to the Toolkit workspace by the discovery process contain the declaration "$schema": "http://json-schema.org/schema#", which does not declare a specific version of the specification. This lack of declaration causes the schema to not be usable when you use JSON schema validation in a message flow. You can work around this issue by changing the declaration to be "$schema": "http://json-schema.org/draft-04/schema#". This declaration can be used with JSON schema validation as normal.  This issue is fixed in IBM App Connect Enterprise 12.0.6.0
• With Discovery Connectors, if you click Back in the Connector discovery process when you create a policy or credentials for the first time, the account (policy or credentials) are not shown (#349)
  When you run Connector Discovery (introduced in App Connect Enterprise 12.0.5.0), and you create a new policy or credential for the first time, when you click Back the information is not displayed. To see the information, close the connector discovery process and open it from the message flow node's properties page.  This issue is fixed in IBM App Connect Enterprise 12.0.9.0
• With Discovery Connectors, do not attempt to use more than one policy of the same connector type in a single policy project (#301)
  When you run Connector Discovery (introduced in App Connect Enterprise 12.0.5.0), do not attempt to use more than one policy of the same Connector type within a single policy project. Using multiple policies can lead to indeterminate results. If multiple policies are used, when you run the Connector Discovery process (started from the message flow node's properties page) the selected Object and Action are not displayed on the last page of the process.  This issue is fixed in IBM App Connect Enterprise 12.0.9.0
• Connector Discovery offers JSONata expressions (#285)
  When you run Connector Discovery (introduced in App Connect Enterprise 12.0.5.0), and insert values for a field (for example a field in a 'where' filter), you might see a window offering the use of a JSONata function. JSONata functions that are displayed start with the $ symbol (for example '$isUndefined') and if they are selected they are displayed within curly braces {{}}. If you select these functions, the Runtime behavior is undefined and reserved for future use. This issue is fixed in IBM App Connect Enterprise 12.0.10.0 which introduces support for JSONata functions for mapping in the Discovery Connector nodes.
• Fractional seconds are ignored when you filter with Business Transaction Monitoring queries against a Db2 database (#88972)
  App Connect Enterprise 12.0.3.0 introduces a new filtering capability for the Business Transaction Monitoring feature in the web UI. If you use Db2 for your Business Transaction Monitoring database, and the filter query you supply in the web UI includes fractional seconds, then the fractional seconds are currently ignored. For example, if you have a transaction with a duration of 1.600 seconds and you filter with "durationAtLeast=1.1" then the transaction is not show in the results. The transaction is not shown because "1.600" is treated as "1", which is less than "1.1". This issue is fixed in IBM App Connect Enterprise 12.0.4.0
• New style subflow user-defined node properties cannot be contributed to template flows used in Pattern Authoring projects (#89025)

  When you use a Pattern Authoring project to create a pattern, you cannot use message flow templates that include properties of subflow user-defined nodes. Typically when you edit a message flow, there is right-click option on a node called "Pattern" that has one child "Select target properties". A dialog opens, showing a list of all the node's properties, by group, with a checkbox alongside each one. Ticking a property makes it visible to the pattern authoring configuration tab, allowing it to be set from pattern properties. However, with the current restriction, for subflow user-defined nodes no properties are shown and the dialog reports "No available node properties".  This issue is fixed in IBM App Connect Enterprise 12.0.7.0
• Contributing the same monitoring event to more than one business transaction definition on the same integration server creates duplication (#88007)

  When a single integration server hosts more than one business transaction definition, and the business transaction definitions use the same monitoring events, the monitoring events subscriptions are registered against all the business transaction definitions. This registering of events can lead to an incorrect business transaction status being reported. For example, if two start events are involved, the transaction status is shown as inconsistent.  You can work around this issue by defining each business transaction definition on a different integration server.  This issue is fixed in IBM App Connect Enterprise 12.0.3.0

• The command ibmint generate tests does not support relative paths on windows (#86166)

  You can work around this issue by using an absolute path when you pass in the value for the recorded-messages parameter on the ibmint generate tests command.  This issue is fixed in IBM App Connect Enterprise 12.0.2.0

• IBM App Connect Enterprise 12.0.1.0 Linux on Z for IBM zCX Multilingual (G01T5ML) contains an incorrect FMID, which prevents support cases being raised.
  You can work around this issue by installing an updated version of IBM App Connect Enterprise. This issue is fixed in IBM App Connect Enterprise 12.0.2.0

Copyright and trademark information

For more information about this topic, see the IBM Copyright and trademark information web page.

This information was developed for products and services offered in the US.

IBM might not offer the products, services, or features discussed in this information in other countries. For more information about the products and services currently available in your area, Consult your local IBM representative. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service can be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right can be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM might have patents or pending patent applications covering subject matter described in this information. The furnishing of this information does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Corporation
1 New Orchard Road
Armonk
New York
10504-1722
United States

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM Japan Ltd
IP Licensing
19 - 21 Nihonbashi Hakozaki-cho
Chuo-ku 
Tokyo 103-8510
Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. This statement might not apply to you because some states do not allow disclaimer of express or implied warranties in certain transactions.

This information might include technical inaccuracies or typographical errors. Changes are periodically made to this information; these changes are incorporated in new editions of the information. IBM can make improvements to the products and programs described in this information, changes in the products and programs described in this information, or both, at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.

IBM can use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who want to have information about it for enabling: (i) the exchange of information between independently created programs and other programs (including this program) and (ii) the mutual use of the information that is exchanged, can contact:

IBM App Connect
IBM United Kingdom Laboratories
Hursley Park
Winchester
Hampshire
England
SO21 2JN

Such information might be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Programming License Agreement, or any equivalent agreement between us.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements, or other publicly available sources. IBM did not test those products and cannot confirm the accuracy of performance, compatibility, or any other claims related to non-IBM products. Address any questions on the capabilities of non-IBM products to the suppliers of those products.

This information includes examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

Copyright license:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You can copy, modify, and distribute these sample programs in any form without payment to IBM in the following circumstances: For the purposes of developing, using, marketing, or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples are not thoroughly tested under all conditions. Therefore, IBM cannot guarantee or imply reliability, serviceability, or function of these programs. You can copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle, its affiliates, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

The registered trademark Linux® is used in accordance with a sublicense from the Linux Foundation, the exclusive licensee of Linus Torvalds, owner of the mark on a world­wide basis.

Other company, product, or service names might be trademarks or service marks of others.

Useful websites

IBM App Connect Enterprise product documentation
https://www.ibm.com/docs/app-connect/12.0

IBM Integration Community
https://developer.ibm.com/integration/

IBM App Connect Enterprise Requirements
https://www.ibm.com/support/pages/node/6456781/

IBM Db2
https://www.ibm.com/analytics/db2

© Copyright IBM Corporation 2023.