Release 1.6

This readme includes improvements, usage notes, and known and resolved issues that have been implemented for the IBM webMethods B2B 1.6 release.

Highlights

Component	Description
IBM webMethods B2B Runtime Options	You can now configure runtime options for three categories: EDI, AS2, and general. These options enable you to control the runtime behavior of the system. For more information, see Runtime Options.
Support for triggering a processing rule when there are errors in AS2 messages	You can configure processing rule to trigger an email notification if there are AS2 errors based on the user status. For more information, see Adding a Processing Rule.
Support for more EDI connector operations	The following new operations are added in the EDI in IBM webMethods Integration formatDate formatTime formatNumber formatDecimal generateFunctionalAcknowledgement getDelimiter getFirstKey getEDIString nullifyIfBlank For more information, see webMethods.io EDI Connector.
Support for more B2B connector operations	The following new operations are added in the B2B Connectors in IBM webMethods Integration setXpathForDocAttribute getTransactionSenderReceiver getPartnerID addTransanctionContentPart relateTransactions getRelatedTransactions getTaskInfo updateAttribute restartTask For more information, see webMethods.io B2B Connector.
Support for handling duplicate MDNs	When IBM webMethods B2B receives a duplicate MDN for the original request, the status of the original request gets updated to indicate the correct status, and all the related messages are grouped together. For more information, see the options for AS2 in Runtime Options.
Support for configuring sender and receiver values of processing rules during queue creation	You can directly configure the partner-specific details for processing rules during queue creation. For more information, see Creating a Partner-Specific Queue.
Control number validation support for inbound EDI payload	The inbound payload can now be validated for duplication, or out-of-sequence control numbers by setting the options in the EDITPA template. For more information, see Working with EDITPA.
Support for bulk resubmit and reprocess actions	You can now resubmit or reprocess multiple transactions. For more information, see Viewing and Downloading Transactions
Enhanced transaction filters and transaction monitoring	You can bookmark your filters and can easily navigate through the transactions. For more information, see Viewing and Downloading Transactions.
Support for triggering a processing rule in case of errors for AS2 messages	You can configure processing rule to trigger an email notification for any AS2 errors based on the user status. For more information, see Runtime Options.
Support to migrate on-premises services to cloud using IBM webMethods Cloud Container	IBM webMethods B2B now supports two-way communication with IBM webMethods Cloud Container, if you have a Cloud Container subscription enabled in your IBM webMethods iPaaS account. You can now: Migrate select flow services, transformations services, and so on, using Trading Networks and/or EDI Modules. For more information, see Running On-Premises Service Orchestrations Using IBM webMethods B2B. Refer to a document type or a service residing on IBM webMethods Cloud Container in Trading Partner Agreements and processing rules, respectively. For more information see, Working with IBM webMethods Cloud Container.
Task management	You can now restart outbound transactions. And can start, stop, restart, or delete tasks. For more information, see Managing Tasks.
Managing Notifications	You can now subscribe to activities or events occurring in the system. This enables you to be aware of the key events happening in the system. You can subscribe to desired events and control the notifications frequency. Click on the bell icon on the right top corner to see all the notifications. For more information, see Managing Notifications.
Channel-based partner identification	You can now identify the partner who sent the business document using channel-IDs. You can make channels partner-specific so you can track the source of the inbound document. For more information, see Channels.
Document Delivery Rate	If your partner systems need to receive and process documents at a specific speed, you can control the pace at which the outbound documents are sent to your partner systems. For more information, see Supported Channel Types.
Terminology change	The asset migration feature that helps you import, export, and deploy assets is now renamed asset movement both in the product and documentation. For more information, see Asset Movement.

Usage Notes

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 secure exchange of business documents.
While synchronizing partner profiles as part of partner onboarding, if duplicate partner profiles are found, then those duplicate partners will not be created. Additionally, a message about the duplicate occurrence is logged in the Activity logs under the General category.
IBM 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 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[].
The publishing of assets from one environment (the origin) to other environment which has inherited users is not supported in IBM webMethods B2B.
- IBM webMethods B2B is supported on the latest version of Google Chrome and Mozilla Firefox web browsers.

Known Issues

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

BOC-11533
When IBM webMethods Cloud Container is down, the functionalities might take more than 60 seconds to respond.
BOC - 8265
The time stamp that is rendered in Full Message in the log entries in the Course of transactions are based on UTC and not current timezone.
BOC-12747
An unsupported RNIF transport 1.1 version appears as a dropdown option for transport version field in the TPA data section of the Trading partner agreement.
FLOW - 1912
Flow services using the webMethods.io B2B Connector fail with an error message indicating that the IBM webMethods B2B connection is disabled.
Workaround: Update the IBM webMethods B2B account, this refreshes the account and enables it.
BOC-10263
During the product upgrade window, you might notice a few failed transactions that involve execution of an operation in webMethods.io B2B Connector on IBM webMethods Integration.
Workaround: You can resubmit the failed transactions after the upgrade window.
BOC-12768
wm.tn.task:removeTask and wm.tn.task:getTaskStatus in WmTNStub do not work as expected in a clustered environment when the request goes to a node where the task is not available. These services work as expected in a non-clustered environment. There is no workaround currently for this issue.
BOC-12853
Although tenants with custom domain names can deploy on-premises assets to the cloud, certain configurations involving cross-applications and runtime invocations thereafter, do not work. There is no workaround for this issue.
BOC-13112
The Validate document structure option for XML documents does not work.
Workaround: Disable the Validate document structure option for the transactions to succeed.

Resolved Issues

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

BOC-11496
IBM webMethods B2B did not receive any asynchronous MDNs from the partner when AS2 out channel was updated with an asynchronous MDN URL.
The issue is resolved.
BOC-11042
UNA segment was missing in CONTROL documents of UNEDIFACT message when UNB01 field contains B to F character set.
This issue is resolved.
BOC-10620
If both IBM webMethods Integration and IBM webMethods B2B are open in two tabs of a web browser, request for authorization appears often.
This issue is resolved.
BOC-10528
The proper partner ID value does not get mapped with the conversation ID while sending a document to a partner, resulting in failed grouping receipt acknowledgment with the related transaction.
BOC-10524
The submitted payload was rendered in an improper format (by removing necessary whitespaces) in the Content page section of transaction.
This issue is resolved now.
BOC-10651
If you had earlier configured external URLs having wrong host names (bad SSL certificates), ensure that you either update those URLs, or use proper SSL certificates.
BOC-12894
Description: Transaction monitoring screen crashed frequently under heavy load.
Solution: Transactions generated for 30 days were being loaded by default, even for tenants with a large data set. The default value is now modified to 24 hours.
This issue is resolved.
BOC-12932
Service invocations between IBM webMethods B2B and IBM webMethods Integration are not processed successfully.
The communication mechanisms are now optimized.
This issue is resolved.