This readme includes improvements, usage notes, and known and resolved issues that have been implemented for the webMethods.io B2B 10.12 release.
|Business Documents||The enhancements are as follows:
|Channels||The enhancements are as follows:
|Partner onboarding||Experience a cohesive partner onboarding flow on the user interface.
See Partner Onboarding.
|Cloud Container||New services help you migrate and deploy your on-premises use cases. A few services are improved to support cloud use cases.
The new services are listed as follows:
|Reliability and monitoring improvements||The performance enhancements are as follows:
|Enhancements to webMethods.io B2B app on webMethods.io Integration||A new operation named constructSubmitInput is added in webMethods.io Integration for you to prepare the necessary input for submitting the business documents to webMethods.io B2B.
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 secure exchange of business documents.
While synchronizing partner profiles as part of partner onboarding, webMethods.io B2B ignores all new partner profiles, retaining only the pre-existing profiles. Additionally, a message about the duplicate occurrence is logged in the Activity logs under the General category.
Software AG recommends that you do not create, update, or delete any B2B assets during the upgrade window.
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. For information on the underlying infrastructure provider in each region and the available products, click here.
Mapping of webMethods.io B2B production URLs with the Software AG Cloud Region 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:
In a clustered or multipod tenant, asynchronous request and response messages can get processed on different nodes resulting in processing errors. The grouping fails for such asynchronous request/response messages as they do not get related to each other across pods in a cluster.
There is no workaround.
TRADACOMS transactions do not split and therefore do not show the transaction document when submitted in webMethods.io B2B.
There is no workaround.
Functional Acknowledgment delivery fails with an with internal server error when you set Generate control number to Random in the Control number table of the EDITPA.
There is no workaround.
In the Full Message log entries for Course of transactions, webMethods.io B2B renders the timestamp in Universal Time Coordinated (UTC) rather than the current time zone.
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.
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.
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).
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.
Occasionally, an “Authorization Required” error occurs while reprocessing a transaction when the following sequence of actions are performed:
- Add a user in MyCloud.
- In webmethods.io B2B, select this new username in the processing rule action to call an integration.
Workaround: Ensure that the user with that username logs in to webMethods.io B2B at least once.
This section lists any issues that were resolved as part of this release:
When you edit the partner name, description, or status, the default values in the delivery settings take precedence over user-defined values. This issue is resolved. Now, when the partner has no user-defined values, the default values are assigned.