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.
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 (Beta) 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.
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.
SSL/TLS certificates for webMethods.io Integration and webMethods.io B2B will expire on March 29, 2023. 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 before March 29, 2023.
If you do not update your certificates before March 29, 2023, your 2-way SSL transactions will fail and you might experience an SSL handshake error.
Root and intermediate certificates remain unchanged.
Azure cloud regions US2, EU3, AU1: Download certificates
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 FlowService, 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.
Software AG Cloud products are available in several geographical regions, operated by different infrastructure providers. Click here for information on the underlying infrastructure provider in each region and the available products.
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 here.
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-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-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:
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 MyCloud 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 MyCloud > 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. |