Release 10.16

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

What's New

Release 10.16.3

Ability to retrieve the transactions with asset information

IBM webMethods Integration allows you to retrieve the transactions with asset information through the queryTransactions operation.
Important This feature works only with IBM webMethods Integration 10.16.1 version.
Read more

Ability to resubmit and reprocess all transactions

You can resubmit and reprocess a maximum of 10000 transactions on IBM webMethods B2B.
Read more about reprocess and resubmit

Download the customized columns on the transaction monitoring page

You can download the transactions after customizing the columns on the transaction monitoring page.
Read more

Configure the SMTP server to send an email through custom domain

You can send an email to your business partners with a custom domain email address while onboarding them.
Read more

Ability to supply different AS2 addresses when sending message to AS2 Partner

You can choose a specific AS2 address when there are multiple addresses defined for an enterprise.
For more information, see constructSubmitInput and Creating a General Queue

Note You cannot customize AS2 addresses in constructSubmitInput when IBM webMethods Integration is on version 10.16.0 and IBM webMethods B2B is on version 10.16.3.

Ability to track IBM webMethods B2B transactions through End-To-End monitoring

When you are tracking a IBM webMethods B2B transaction on End-To-End monitoring, you will be redirected to view the transaction on IBM webMethods B2B transactions page.
Read more

Release 10.16.0

IBM webMethods B2B user interface enhancements

webMethods.io B2B Connector enhancements on IBM webMethods Integration

Customer Actions Required

SSL/TLS Certificate Update

SSL/TLS certificates for IBM webMethods Integration and IBM webMethods B2B will expire on the date mentioned in the IBM webMethods iPaaS Service Status page. If you are currently using SSL/TLS certificates with IBM webMethods Integration and IBM webMethods B2B, download the updated certificates from the specified location below and replace your existing certificates.

Azure cloud regions US2, EU3, AU1: Download certificates

AWS cloud regions US1, EU2, AU2: Download certificates

If you do not update your certificates, your 2-way SSL transactions will fail and you might experience an SSL handshake error.
Root and intermediate certificates remain unchanged.

Usage Notes

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

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

Known Issues

This section lists any issues for the current release that were known when this readme was published:

Release 10.16.2

Release 10.16.0

Resolved Issues

This section lists any issues that were resolved as part of this release:

Resolved Issue Description
BOC-15682 The user interface turns unresponsive when a partner-specific certificate is added from the partner-360 page.
BOC-16945 When the service execution on webMethods.io B2B Connector app on IBM webMethods Integration fails, a generic message to contact support appeared on the Monitoring log. The generic message made it difficult to identify the cause and fix the issue. Now, an actual error message appears upon failure.
BOC-15660 When a Flat File connector is defined with below mentioned definition and convertDocumentToFlatFile operation is run, the output of the operation is incorrect.
Flat File Connectors with below definition in the schema have the issue:
  • Record Identifier Position is set to Starts at position with a value 0.
  • First field definition under any record definition using Extractor Type as Nth Field.

Fixes

This section provides information on the fixes for IBM webMethods B2B v10.16.3.

Release 10.16.3


Issue ID Release Date Region Description
BOC-19097 May 27, 2023

May 28, 2023
June 03, 2023

June 04, 2023
June 10,2023
EU2 Frankfurt AWS
AU2 Sydney AWS
US1 Oregon AWS
US2 East Azure
EU3 West Azure
AU1 Australia East Azure
EU2 Frankfurt AWS
IBM webMethods B2B version 10.16.3 includes security updates for the key lengths of DES and Triple DES. The system will utilize a Triple DES key length of 128 and a DES key length of 64.
BOC-18372 May 27, 2023

May 28, 2023
June 03, 2023

June 04, 2023
June 10,2023
EU2 Frankfurt AWS
AU2 Sydney AWS
US1 Oregon AWS
US2 East Azure
EU3 West Azure
AU1 Australia East Azure
EU2 Frankfurt AWS
IBM webMethods B2B supports only the open SSH format to generate the public and private key pair. There is no support for the SSH2 format for both public and private key pairs.
BOC-18064 May 27, 2023

May 28, 2023
June 03, 2023

June 04, 2023
June 10,2023
EU2 Frankfurt AWS
AU2 Sydney AWS
US1 Oregon AWS
US2 East Azure
EU3 West Azure
AU1 Australia East Azure
EU2 Frankfurt AWS
A widget on the Monitoring page displays the total transaction count when they are 20K or less in an hour. When the number of transactions surpasses 20K in an hour, the widget displays 20K+.
BOC-17268 May 27, 2023

May 28, 2023
June 03, 2023

June 04, 2023
June 10,2023
EU2 Frankfurt AWS
AU2 Sydney AWS
US1 Oregon AWS
US2 East Azure
EU3 West Azure
AU1 Australia East Azure
EU2 Frankfurt AWS
When executing a bulk action (stopping or restarting) on more than 41 tasks, the system successfully processes only the first 41 tasks, and any remaining task encounters an error.
BOC-17041 May 27, 2023

May 28, 2023
June 03, 2023

June 04, 2023
June 10,2023
EU2 Frankfurt AWS
AU2 Sydney AWS
US1 Oregon AWS
US2 East Azure
EU3 West Azure
AU1 Australia East Azure
EU2 Frankfurt AWS
The timestamps that appear on IBM webMethods B2B correspond to the timezone from where you are accessing the instance. If you do not configure a timezone, then IBM webMethods B2B displays the browser’s timezone. If you configure a timezone on IBM webMethods iPaaS, then timestamps on the Monitoring screens correspond to that. If you do not configure a date-time format on IBM webMethods iPaaS, then the following default format appears for all the timestamps: Jan 4, 2023, 2:09:54 PM. 
BOC-17628 May 27, 2023

May 28, 2023
June 03, 2023

June 04, 2023
June 10,2023
EU2 Frankfurt AWS
AU2 Sydney AWS
US1 Oregon AWS
US2 East Azure
EU3 West Azure
AU1 Australia East Azure
EU2 Frankfurt AWS
When you submit UNEDIFACT documents to IBM webMethods B2B, and if the UNZ segment control number is different from the one specified in the UNB segment, the corresponding payload where the UNZ control number appears, gets modified.
Now the payload of the transaction remains the same as the one that is submitted.
BOC-17505 May 27, 2023

May 28, 2023
June 03, 2023

June 04, 2023
June 10,2023
EU2 Frankfurt AWS
AU2 Sydney AWS
US1 Oregon AWS
US2 East Azure
EU3 West Azure
AU1 Australia East Azure
EU2 Frankfurt AWS
FAGeneration/autoGenerateFA and ControlNumberManagement property values were reset in the default EDITPA.
BOC-17491 May 27, 2023

May 28, 2023
June 03, 2023

June 04, 2023
June 10,2023
EU2 Frankfurt AWS
AU2 Sydney AWS
US1 Oregon AWS
US2 East Azure
EU3 West Azure
AU1 Australia East Azure
EU2 Frankfurt AWS
IBM webMethods B2B has a new ReadOnly User role to view only the assets without any functional privileges. This role has read-only access to the assets and runtime data. For details, see User Roles and Permissions.
BOC-17240 May 27, 2023

May 28, 2023
June 03, 2023

June 04, 2023
June 10,2023
EU2 Frankfurt AWS
AU2 Sydney AWS
US1 Oregon AWS
US2 East Azure
EU3 West Azure
AU1 Australia East Azure
EU2 Frankfurt AWS
Enhancements are made to the TPA cache to avoid the application from becoming unresponsive during read and write operations.
BOC-17168 May 27, 2023

May 28, 2023
June 03, 2023

June 04, 2023
June 10,2023
EU2 Frankfurt AWS
AU2 Sydney AWS
US1 Oregon AWS
US2 East Azure
EU3 West Azure
AU1 Australia East Azure
EU2 Frankfurt AWS
When the TPA status is not as AGREED and/or the data status is IMMUTABLE, several transactions failed while attempting to obtain the TPA information. The transactions failed due to a problem in MySQL that causes deadlocks when a database lock is acquired or released in an application.
BOC-17172 May 27, 2023

May 28, 2023
June 03, 2023

June 04, 2023
June 10,2023
EU2 Frankfurt AWS
AU2 Sydney AWS
US1 Oregon AWS
US2 East Azure
EU3 West Azure
AU1 Australia East Azure
EU2 Frankfurt AWS
On importing EDI document to IBM webMethods B2B, format configuration was not being retained.