Release 10.15

Highlights

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

• IBM recommends that you do not create, update, or delete any B2B assets during the upgrade window.

• If you cannot 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 webMethods iPaaS 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, see Regions.

  Mapping of IBM webMethods B2B production URLs with the IBM webMethods iPaaS Regions are listed as follows:
  
  

Known Issues

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

• BOC-15915
  For an inbound XML business document, if you select the Validate document structure option in the Options page of the XML business document, the XML validation fails, and this is logged in the Transaction activity log.
  Workaround: Avoid this issue by disabling the Validate document structure option.
  

• BOC-15598
  When the addTransactionContentPart service has a dot (.) in partName parameter, the user interface does not render the content for the transaction.
  Workaround: Avoid using a dot character (.) or any other special character in the partName parameter.
  

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

  • Record Identifier Position is set to Starts at position with a value 0.
  • First field definition under any record definition using Extractor Type as Nth Field.
    

• BOC-8265
  In the Full Message log entries for Course of transactions, IBM webMethods B2B renders the timestamp in Universal Time Coordinated (UTC) rather than the current time zone.

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

Resolved Issues

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

None

Fixes

This section provides information on the fixes for IBM webMethods B2B v10.15.