Release 11.1.0

This readme includes improvements, usage notes, known and resolved issues implemented for the IBM webMethods B2B 11.1.0 release.

What's New

Release 11.1.10

IBM webMethods B2B user interface enhancements

Support for Functional Acknowledgement split option

Generate the functional acknowledgement document at interchange, group, and transaction level for an EDI document.

Read more

webMethods.io B2B Connector and B2B Utils services Enhancements on IBM webMethods Integration

Support for getChannel operation in webMethods.io B2B Connector

A new operation getChannel to retrieve the channel details from IBM webMethods B2B is added.

Important
This requires IBM webMethods Integration with Connector Monthly Releases (CMR) 38.

Support for selecting a preferred channel for the document delivery

A new input parameter preferredOutboundChannelID is added in constructSubmitInput operation. You can now select a preferred outbound channel to send a document.

Important
This requires IBM webMethods Integration with Connector Monthly Releases (CMR) 38.

Support for auto generating a functional acknowledgement

A new input parameter autoGenerateFA is added in submit operation. You can now auto generate a functional acknowledgement in IBM webMethods B2B.

Important
This requires IBM webMethods Integration with Connector Monthly Releases (CMR) 38.

Fixes included in the 11.1.10 release

See the Fixes section for information on the 11.1.10 fixes.

Release 11.1.0

No new features to existing user-facing functionalities.

Customer Actions

To view the content of a large document in IBM webMethods Integration

When you call an integration from IBM webMethods B2B to IBM webMethods Integration, the content for the large document is null.
To fetch the content of the large document, you must write a logic for largeDoc input request as true and call getTransactionContentParts from IBM webMethods B2B operations in IBM webMethods Integration.

AS2 Connector Update

In IBM webMethods Integration, if the payload fails to reach the recipient when you resend the payload after a specific period (approximately 10 minutes), delete the existing account and create a new one. For more information, see AS2 Connector.

Fixes

This section provides information on the fixes for IBM webMethods B2B 11.1

Release 11.1.10


Issue ID Release Date Region Description
BOC-30865 24th October, 2024
25th October, 2024
25th October, 2024
Asia Pacific Sydney AWS AU2
Europe Frankfurt AWS EU2
US West Oregon AWS US1
In IBM webMethods B2B, the document fails to process when sent with the RNIF custom attribute in a different case.
The issue is resolved. Now, the RNIF custom attribute is made case-sensitive.
BOC-31149 24th October, 2024
25th October, 2024
25th October, 2024
Asia Pacific Sydney AWS AU2
Europe Frankfurt AWS EU2
US West Oregon AWS US1
When IBM webMethods B2B receives an XML document over an AS2 partner-specific channel and an MDN is requested, whether synchronous or asynchronous, if the sender and receiver details are not present in the XML, these details are not extracted from the EDIINT MDN and XML documents.
The issue is resolved.
BOC-30970 24th October, 2024
25th October, 2024
25th October, 2024
Asia Pacific Sydney AWS AU2
Europe Frankfurt AWS EU2
US West Oregon AWS US1
In IBM webMethods B2B, the outbound peppol messages failed at the receiving access point due to an unsupported encryption algorithm.
The issue is resolved. Now, the Advanced128SHA256GCM and Advanced256SHA256GCM algorithms are provided to support the specification.
BOC-29699 24th October, 2024
25th October, 2024
25th October, 2024
Asia Pacific Sydney AWS AU2
Europe Frankfurt AWS EU2
US West Oregon AWS US1
In the IBM webMethods B2B Peppol, the “ValueType” attribute in BinarySecurityToken for signature contains http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509PKIPathv1 for the outbound Peppol message.
This issue is resolved. The value for the “ValueType” attribute must be http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3 as per the Peppol specification version 2.0.3.
BOC-31317 24th October, 2024
25th October, 2024
25th October, 2024
Asia Pacific Sydney AWS AU2
Europe Frankfurt AWS EU2
US West Oregon AWS US1
In IBM webMethods Integration, when the user uses the getTransactionContentParts service to retrieve transaction content, the original encoding of the content gets ignored, and IBM webMethods B2B returns the content encoded in UTF-8, which resulted in a validation error in the customer’s custom validation logic.
This issue is now resolved. Now, IBM webMethods B2B returns the content encoded in original standard in which the content was sent.

Usage Notes

The following functionalities have certain restrictions in IBM webMethods B2B system:

Region Sample URL
US West Oregon AWS US1 https://tenantname.int-aws-us.webmethods.io/b2b
East US Virginia Azure US2 https://tenantname.int-az-us.webmethods.io/b2b
Europe Frankfurt AWS EU2 https://tenantname.int-aws-de.webmethods.io/b2b
West Europe Netherlands Azure EU3 https://tenantname.int-az-eu.webmethods.io/b2b
Australia East Azure AU1 https://tenantname.int-az-au.webmethods.io/b2b