Release 1.5

Highlights

Usage Notes

The following functionalities have certain restrictions in IBM webMethods B2B system:

• Secondary certificates are not used for sign-verify, encrypt-decrypt, or SSL usages for any document received over any AS2 channel. To work around this issue, ensure that only valid certificates are set as primary certificates.

• Secondary certificates cannot be imported or exported.

• 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. And a message about the duplicate occurrence will be 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[].

• The IBM webMethods B2B User Interface may appear out of sync during an upgrade.
  Workaround: Retry after some time.
  

Known Issues

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

• BOC-6554
  When importing business documents from releases below IBM webMethods B2B 1.3, if the attributes configured for these business documents have transformation function set to EDIINT AS1, AS2, or AS3, then those attributes do not appear in the Attributes tab of that document.

• BOC - 10184
  TRADACOM document batch file does not give batch count, in addition, the sender and receiver tenants do not get extracted.

• 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.

• 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-10277
  When updating the Folder path in the an SFTP-IN channel under the Post-processing section by selecting the Move to Folder action, the Update button for the channel remains disabled.
  Workaround: Toggle Allow Folder Creation to the enable state.

• BOC-10264
  In a Custom TPA when the DeliverFA option is set to false, the setting is not honored.
  The Functional Acknowledgement(FA) is still delivered to the partner.
  Workaround: Either use default TPA Or create a custom rule above the “Deliver Functional Acknowledgement” system rule.
  

• 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 upgrate window.

• BOC-10424
  A few limitations are noted during the update and view actions for record or composite node (with conditional validators).
  The values you specify for the Conditional validator fields are not rendered on the UI. Each time you update the modification you make to the record or composite nodes, you must specify the values for the Conditional validator fields. Also the Add action for conditional validator copies the value you specify in one Conditional validator field to the rest of the Conditional validator field as well.
  Workaround: To update a record or composite node (with conditional validator), always re-type the values for the Conditional validator fields.

• BOC-10311
  When non-EDI or XML documents are sent over AS2 channels, the size of the payload increases before it is persisted.

Resolved Issues

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

• BOC-9540
  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-8882
  The Sender filter was auto-filled with a spurious value, and resetting the filter value did not fix the issue.
  This issue is resolved.
  
  
• BOC-8563
  ISA14 field value was always set to ‘0’ even when ackRequested field in EDI connectors AddInterchangeEnvelope operation was set to ‘true’.
  This issue resolved.
  
  
• BOC-10186
  Earlier IBM webMethods B2B searched for the AS2 ID of the sender profile requesting an FA, before sending the FA over the AS2 channel. Now, IBM webMethods B2B retrieves the value of the AS2 ID from the enterprise profile if an AS2 ID value is not set for the sender partner requesting an FA.
  This issue resolved.