Release 10.16
This readme includes improvements, usage notes, known and resolved issues implemented for the webMethods.io B2B 10.16 release.
This readme includes improvements, usage notes, known and resolved issues implemented for the webMethods.io B2B 10.16 release.
webMethods.io Integration allows you to retrieve the transactions with asset information through the queryTransactions operation.
Important: This feature works only with webMethods.io Integration 10.16.1 version.
Read more
You can resubmit and reprocess a maximum of 10000 transactions on webMethods.io B2B.
Read more about reprocess and resubmit
You can download the transactions after customizing the columns on the transaction monitoring page.
Read more
You can send an email to your business partners with a custom domain email address while onboarding them.
Read more
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 webMethods.io Integration is on version 10.16.0 and webMethods.io B2B is on version 10.16.3.
When you are tracking a webMethods.io B2B transaction on End-To-End monitoring, you will be redirected to view the transaction on webMethods.io B2B transactions page.
Read more
Support for UNEDIFACT D95B business document type
You can now transact using UNEDIFACT D95B business document type.
Read more
Self-service Partner Portal (Beta)
A new single web-based self-service interface enables faster onboarding, transaction monitoring, and configuring communication details between you and your partners.
Warning: Partner Portal is a beta feature. The contents of this feature are preliminary and may be changed or discontinued without prior notice. Any changes may impact the feature’s operation with the webMethods.io family of products. webMethods warranties and product service levels shall not apply to the feature or the impact of the feature on other portions of the webMethods.io family of products. webMethods.io may review and monitor the performance and use of this feature. The documentation for this feature is also considered a beta version and is subject to revision. To enable the feature in your tenant, write to support@softwareag.com.
Customize the columns on the transaction monitoring page
You can personalise the Transactions page by selecting the columns of your interest.
Read more
Enhancements to checking duplicate business documents
Addition of four new operations
Flat file batching for large documents
A new output parameter hasMore is added in the convertFlatFileToDocument to process large Flat file documents in batches.
Read more
SSL/TLS certificates for webMethods.io Integration and webMethods.io B2B will expire on the date mentioned in the webMethods.io iPaaS Service Status page. If you are currently using SSL/TLS certificates with webMethods.io Integration and webMethods.io 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.
The following functionalities have certain restrictions in webMethods.io B2B system:
Partner certificate automatically gets associated with the new partner created with the same details as the deleted one. Also, the certificate is not listed in the certificate monitoring page.
To use 2-Way SSL/TLS functionality, business documents must be sent to a channel URL with the port 8443 appended to the hostname. The 2-Way SSL/TLS functionality is an additional-level of validation and security. This along with the partner-user credential-based authentication ensures that business documents are exchanged securely.
While synchronizing partner profiles as part of partner onboarding, webMethods.io B2B ignores all new partner profiles, and retains only the pre-existing profiles. Additionally, a message about the duplicate occurrence is logged in the Activity logs under the General category.
If you are not able to map multiple documents to a document array based on indexing in a Flow service, create a document array that holds all the required documents using the “insertDocument” operation of the “Document” service.
For example, if you want to map three documents (D1, D2, and D3) to a document array (DA1[]), add the “insertDocument” operation thrice: once for each document, and insert D1, D2, and D3 into the “documents” array. You can also use loops to run the “insertDocument” operation thrice. Finally, map the “documents[]” array, which holds all the three documents, to DA1[].
Publishing of assets from one environment (the origin) to another environment (the target) with inherited users is not supported.
It is recommended that you do not create, update, or delete any B2B assets during the upgrade window. For information on major releases, hotfixes, and patch releases including the latest statistics on the availability of cloud environments, incident history, and planned maintenance events, see webMethods.io iPaaS Service Status page.
Software AG Cloud products are available in several geographical regions, operated by different infrastructure providers. Go to the Software AG Cloud Regions website for information on the available products and also the underlying infrastructure provider in each region. For allowed IPs, see webMethods.io IP addresses for the cloud products.
Mapping of webMethods.io B2B production URLs with the Software AG Cloud Regions are listed as follows:
Software AG Cloud 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 |
This section lists any issues for the current release that were known when this readme was published:
BOC-18184
On the Transactions page, when you select the dateTime or number attribute (only for decimal values), transactions cannot be downloaded.
BOC-17241
When a Partner Portal user tries to upload a P7b certificate for both sign-verify and encrypt-decrypt authentication options, the certificate chain for either one of the authentication options goes missing. Subsequently, this missing certificate chain does not appear on the webMethods.io B2B user interface.
Workaround:
BOC-10263
During the product upgrade window, you might notice a few failed transactions when it involves running operations using webMethods.io B2B connector on webMethods.io Integration.
Workaround: You can resubmit the failed transactions after the upgrade window.
BOC-12853
Although tenants with custom domain names can deploy on-premises assets to the cloud, thereafter, certain configurations involving cross-applications and runtime invocations do not work.
Workaround: There is no workaround for this issue.
BOC-13902
webMethods.io B2B does not support two-way SSL communication with webMethods Cloud Container.
If two-way SSL is configured in Cloud Container, executions in webMethods.io B2B that invoke Cloud Container services fail.
Workaround: Change the authentication mode in Cloud Container to allow one-way and two-way SSL API execution calls (credentials and certificate).
BOC-14028
If you create a tenant user in Software AG Cloud with a username that is identical to an existing partner user in webMethods.io B2B, an Internal Server error appears when the tenant user attempts to log in to webMethods.io B2B.
Workaround: Delete the partner user and create another partner user with a unique username that does not match any of the existing tenant usernames. However, if you do not want to delete the partner user, delete the tenant user and create a tenant with a unique username that does not match any existing partner users. You can do this on the Software AG Cloud > Administration > Users page.
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 webMethods.io 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:
|
This section provides information on the fixes for webMethods.io B2B v10.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 |
webMethods.io 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 |
webMethods.io 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 webMethods.io B2B correspond to the timezone from where you are accessing the instance. If you do not configure a timezone, then webMethods.io B2B displays the browser’s timezone. If you configure a timezone on Software AG Cloud, then timestamps on the Monitoring screens correspond to that. If you do not configure a date-time format on Software AG Cloud, 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 webMethods.io 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 |
webMethods.io 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 webmethods.io B2B, format configuration was not being retained. |