Release 10.17
This readme includes improvements, usage notes, known and resolved issues implemented for the IBM webMethods B2B 10.17 release.
This readme includes improvements, usage notes, known and resolved issues implemented for the IBM webMethods B2B 10.17 release.
All AS4 communication is Drummond TM certified starting IBM webMethods B2B version 10.17 and higher.
Read more
The reconciliation of FA status is available for both EDI batch and non-batch documents.
Read more
In an SFTP-OUT-CLIENT channel, the following filename options are available:
And the filename prefix option is enhanced.
The limit for Field values in the Field criteria input parameter has increased from 5 to 20.
Read more
Important This requires IBM webMethods Integration with Connector Monthly Releases (CMR) 31.
To retain the same name for a document both in IBM webMethods B2B and IBM webMethods Integration, you must define an input parameter named fileName in IBM webMethods Integration. You can do this by defining an I/O parameter in the pipeline of the Flow service. You must then map the fileName to the input parameter called params.
Read more
Important This requires IBM webMethods Integration with Connector Monthly Releases (CMR) 31.
Retrieves the profile ID types from IBM webMethods B2B.
Read more
Important This requires IBM webMethods Integration with Connector Monthly Releases (CMR) 31.
The new user interface theme enhances your runtime transaction tracking experience significantly.
Important While the old user interface remains stable as before, the new user interface will be frequently updated.
Here are the key enhancements:
View transactions in multi-view mode
If you notice specific patterns in transactions that warrant further examination, you have the option to now select up to four transactions for detailed viewing across different pages. This allows you to thoroughly analyze their details and gain deeper insights.
Read more
Compare transactions
Select two transactions and compare their details.
Read more
Use quick filters on transactions
The quick filters feature allows you to swiftly create filters based on specific transactions of interest, helping you focus on the relevant data. Additionally, it aids in locating a list of transactions within a given time period, streamlining your search process.
Read more
Note Any modifications made to the new theme for IBM webMethods B2B reflects on the old theme for IBM webMethods B2B, leveraging a shared database to ensure continuous synchronization.
A separate archival mechanism enables you to retain and access archived data for years. The archival data is stored on an S3/Blob in a standard format that enables you to run queries. This was not possible earlier because multi-layered data persisted on the transaction store.
Limited Availability: Support for Externalized Archival of Transactions (Preview) is now enabled with Limited Availability. This is currently a beta feature. The contents of this feature are preliminary and may change without prior notice. Any changes may impact the feature’s operation with the IBM webMethods 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 IBM webMethods family of products. The documentation for this feature is also considered a beta version and is subject to revision.
You can now download archived transactions. The download limit for both live and archived transactions is 20,000 transactions.
Read more
The enhancements in Partner Portal are:
Hide contents, attributes, and document types on Partner Portal.
Read more
View the transaction-related comments as feeds on Partner Portal.
Delete assets.
Configure a custom format service in the EDI document structure.
Read more
Configure the advanced scheduling options for SFTP inbound channels.
Read more
Create, modify, associate inbound or outbound channels, along with creating or modifying Trading Partner Agreements (TPAs) on the Partner 360 Degree page.
Read more
Configure VDA control numbers on the Control Numbers page for inbound and outbound EDI transactions.
Read more
Configure the maximum file transfer size over SFTP in settings.
Read more
Select multiple hours, minutes and seconds while scheduling queues.
Read more
Two new services namely convertHIPAAMessageToDocument and convertDocumentToHIPAAMessage are added to the B2B connectors on IBM webMethods Integration.
Important This requires IBM webMethods Integration to be on the 10.16.3 version with Connector Monthly Releases (CMR) 29 version.
AS4 PEPPOL is adopted in many countries for e-invoicing. Two new services namely addOrUpdatePeppolPartner and retrievePeppolParticipant are added. In addition, a new input parameter named endpointUrl is added under the Configuring AS4 param section in the constructSubmitInput operation.
Important This requires IBM webMethods Integration to be on the 10.16.3 version with Connector Monthly Releases (CMR) 29 version.
Read more about addOrUpdatePeppolPartner
Read more about retrievePeppolParticipant
A new HIPAA connector is available on the Flow services page of IBM webMethods Integration.
Important This requires IBM webMethods Integration to be on the 10.16.3 version with Connector Monthly Releases (CMR) 29 version.
queryTransactions operation on the webMethods.io B2B Connector app on IBM webMethods Integration supports custom attributes as a filter criteria in the input. Also, in the output, you can view the attributes (up to 5 based on the attribute names specified in the includeAttributes input field), for the transaction in addition to the basic transaction details.
Important This requires IBM webMethods Integration to be on the 10.16.3 version with Connector Monthly Releases (CMR) 29 version.
None
The following functionalities have certain restrictions in IBM webMethods 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, IBM webMethods 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.
IBM recommends 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 IBM webMethods iPaaS Service Status page.
IBM webMethods iPaaS products are available in several geographical regions, operated by different infrastructure providers. For information on the available products and also the underlying infrastructure provider in each region, see Regions. See the IBM webMethods iPaaS page for IP addresses for the cloud products.
Mapping of IBM webMethods B2B production URLs with the IBM webMethods iPaaS Regions are listed as follows:
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-19788
When the Validate ebms header option is set to true for the receiver in the AS4 runtime options on the Runtime Options page, and the sender sends the AS4 Peppol message, then the sender receives a SOAP fault from the receiver with the following error message: “Invalid ebMS Header error. Error Message: cvc-minLength-valid: Value “ with length = ‘0’ is not facet-valid with respect to minLength ‘1’ for type ‘non-empty-string’.”
Workaround: The receiver must set the Validate ebms header option to false in the AS4 Runtime options on the Runtime Options page to receive the AS4 Peppol message.
BOC-19771
When you reset the Peppol test certificate chain and Peppol production certificate chain in the AS4 Runtime options to default and save, IBM webMethods B2B deletes the certificates associated with the Access Point profile. The following error message appears “Unable to update the runtime configuration for AS4. Error - An invalid certificate has been uploaded. Error details: Certificate chain bytes cannot be null or zero length.”
Workaround: You must add a certificate to save the AS4 Runtime options.
PIE-83308
The File name filter field is not supported for SFTP V2 version of the client for SFTP-IN channels.
BOC-19502
Users in IBM webMethods B2B with only Developer role assigned to them are unable to create the partner users.
Workaround: Ensure that you have the Administrator role assigned to you in addition to the Developer role.
BOC-19438
When the certificates associated with the partner profile are deleted or changed, or the Peppol configurations are incorrect, the following error appears in the Course of transaction - “Cannot create Crypto instance.”
Workaround: Delete the receiver profile which gets created dynamically.
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 IBM webMethods 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
IBM webMethods B2B does not support two-way SSL communication with IBM webMethods Cloud Container.
If two-way SSL is configured in Cloud Container, executions in IBM webMethods 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 IBM webMethods iPaaS with a username that is identical to an existing partner user in IBM webMethods B2B, an Internal Server error appears when the tenant user attempts to log in to IBM webMethods 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 IBM webMethods iPaaS > Administration > Users page.
This section lists any issues that were resolved as part of this release:
Resolved Issue | Description |
---|---|
BOC-19094 | The FA group and envelope control number for X12 documents is not same. |
BOC-18921 | When IBM webMethods B2B processed an inbound document of X12 or UNEDIFACT business document types, it modified the group and transaction content by changing the data in the GE (Functional Group Trailer) and IEA (Interchange Control Trailer) segments for X12, and the UNE (Functional Group Trailer) and UNZ (Interchange Trailer) segments in UNEDIFACT. |
This section provides information on the fixes for IBM webMethods B2B v10.17.20.
Issue ID | Release Date | Region | Description |
---|---|---|---|
BOC-20325 | Oct 10, 2023 Oct 10, 2023 Oct 10, 2023 Oct 10, 2023 Oct 11, 2023 Oct 11, 2023 Oct 11, 2023 |
EU2 Frankfurt AWS AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure EU3 West Azure AU1 Australia East Azure |
In IBM webMethods B2B, processing of EDI documents fails if the documents contain backslash() and ? as segment delimiters. |
BOC-19750 | Oct 10, 2023 Oct 10, 2023 Oct 10, 2023 Oct 10, 2023 Oct 11, 2023 Oct 11, 2023 Oct 11, 2023 |
EU2 Frankfurt AWS AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure EU3 West Azure AU1 Australia East Azure |
The reconciliation of FA status is available for both EDI batch and non-batch documents. |
BOC-20243 | Oct 10, 2023 Oct 10, 2023 Oct 10, 2023 Oct 10, 2023 Oct 11, 2023 Oct 11, 2023 Oct 11, 2023 |
EU2 Frankfurt AWS AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure EU3 West Azure AU1 Australia East Azure |
In IBM webMethods B2B, if EDI documents contain a few characters such as backslash(), ? as segment delimiters, then the processing of such a document fails. IBM webMethods B2B corrects the group and envelope control number for inbound documents of X12 or UNEDIFACT business document types. This fix reverts the issue resolved in BOC-18921 |
BOC-20193 | Oct 10, 2023 Oct 10, 2023 Oct 10, 2023 Oct 10, 2023 Oct 11, 2023 Oct 11, 2023 Oct 11, 2023 |
EU2 Frankfurt AWS AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure EU3 West Azure AU1 Australia East Azure |
When the UNEDIFACT payload does not have the group segment (UNG and UNE), and if the UNZ control number is incorrectly specified, the payload is processed successfully in IBM webMethods B2B. But, the extracted transaction content is modified where the UNZ control number is auto-corrected. |
BOC-20669 | Oct 10, 2023 Oct 10, 2023 Oct 10, 2023 Oct 10, 2023 Oct 11, 2023 Oct 11, 2023 Oct 11, 2023 |
EU2 Frankfurt AWS AU2 Sydney AWS US1 Oregon AWS EU2 Frankfurt AWS US2 East Azure EU3 West Azure AU1 Australia East Azure |
When an inbound EDI/AS2 message contains a new line at the end, the segment delimiter is added to the transaction content. Now, a segment delimiter is not added to the content. |