Release 11.0.0

What's New

Release 11.0.35

Security updates with no new features to existing user-facing functionalities.

Release 11.0.26

Fixed minor internal issues in this version.

Release 11.0.25

IBM webMethods B2B user interface enhancements

Support for handling large documents

IBM webMethods B2B now supports processing of the large documents.

Read more

User-interface for monitoring all the identities

Monitor all the custom ID types in IBM webMethods B2B through a single user interface.

Read more

Capability to refresh datasets in externalized archived transactions

Refresh the datasets in archived transactions, tasks, and FA reconciliation.

Read more Archived transactions, Tasks, FA reconciliation

Download archived transactions

You can now download the archived transactions in the externalized archival enabled enterprise production tenants by applying the appropriate filters.

Read more

Validation for custom EDI document structure

IBM webMethods B2B now supports the validation of custom EDI document structure.

Read more

Support for custom headers for inbound RNIF messages

The IBM webMethods B2B creates a document attribute for custom headers for inbound RNIF messages.

Read more

webMethods.io B2B Connector Enhancements on IBM webMethods Integration

Support for IBM webMethods B2B Utils in IBM webMethods Integration

The IBM webMethods B2B Utils services generateResponse, constructSubmitInput , and parseContent have been implemented in IBM webMethods Integration to enhance the performance.

Read more

Support for custom headers for RNIF messages

The new input parameter header is added for RNIF messages in the constructSubmitInput operation.

Read more

Release 11.0.20

Security updates with no new features or modifications to existing user-facing functionalities.

Release 11.0.19

No new features.

Fixes included in the 11.0.19 release

See the Fixes section for information on the 11.0.19 fixes.

Release 11.0.18

Infrastructure updates with no new features or modifications to existing user-facing functionalities.

Release 11.0.16

Support for New EDI Business Document Types

Exchange X12 7020 EDI business document type with your business partners.

Read more

Fixes included in the 11.0.16 release

See the Fixes section for information on the 11.0.16 fixes.

Release 11.0.10

The current IBM webMethods B2B UI-serving component is replaced with another component that possesses equivalent functionality. This change is intended to enhance engineering and operational efficiencies, and customers are not required to take any specific actions in response to this change.

Release 11.0

IBM webMethods B2B user interface enhancements

Support to exchange cXML Business Documents

Exchange cXML documents with your business partners using cXML-IN and cXML-OUT channels in both test and production modes.

Read more

Support for New EDI Business Document Types

Exchange X12 2002 and UNEDIFACT 2017-2022 EDI business document types with your business partners.
Read more

Support for Customizing EDI Document on IBM webMethods B2B

Customize EDI documents, allowing partner-specific customizations for EDI documents.
Read more

Support for Functional Acknowledgment filters

Apply various attribute filters in the Functional acknowledgment page.
Read more

Support for custom ID type in both IBM webMethods Integration and IBM webMethods B2B products

Define and process custom ID types for EDI documents in IBM webMethods B2B and IBM webMethods Integration.
Read more

Enhancements to Partner Onboarding - Questionnaire support

Create and add a custom questionnaire in the partner onboarding form, which allows your enterprise to include custom questions along with the standard questions.
Read more

Secure Password Policy for Partner users in B2B

Configure a password policy for partner users.
Read more

Functional Acknowledgement (FA) transaction groups with the actual transaction

When you send a document through an outbound channel and receive an FA, it automatically groups it with the original document.

Grouping of Related Transactions

On expanding a transaction group, you can view up to five related transactions. The pagination option allows you to view more related transactions.
Read more

Enhancements to Archival Capability

IBM webMethods B2B displays current and past schedules only for externalized archival enabled enterprise production tenants.
Read more

Partner Portal Enhancements

• You can now view details of various partners using a multi-partner view. Enterprise IBM webMethods B2B tenant users can link multiple contacts to partners in IBM webMethods B2B and invite them to access Partner Portal. The contact that is added will have access to monitor different partners in Partner Portal. As an administrator of IBM webMethods B2B, you can also delete contacts which in turn deletes the Partner Portal user.
  Read more
  

• Partner Portal has attained the required stability and acceptance, and hence it is no more a beta feature.
  

webMethods.io B2B Connector Enhancements on IBM webMethods Integration

The following updates are made to the B2B operation on IBM webMethods Integration

• queryTransactions: The fieldCriteria operators are now categorized as: no-value operators, single-value operators, and multi-value operators.
  Read More
• constructSubmitInput: The cXML input parameter is added to support exchange of cXML documents.
  Read More
• addGroupEnvelope: The x12/ucs/vics input parameter is added to support different time formats for GS05 field in EDI messages.
  Read More
• getIDtype: A new operation to retrieve the list of ID types from IBM webMethods B2B.
  Read More

Customer Actions

To view the content of a large document in IBM webMethods Integration

When you call an integration from IBM webMethods B2B to IBM webMethods Integration, the content for the large document is null.
To fetch the content of the large document, you must write a logic for largeDoc input request as true and call getTransactionContentParts from IBM webMethods B2B operations in IBM webMethods Integration.

AS2 Connector Update

In IBM webMethods Integration, if the payload fails to reach the recipient when you resend the payload after a specific period (approximately 10 minutes), delete the existing account and create a new one. For more information, see AS2 Connector.

Fixes

This section provides information on the fixes for IBM webMethods B2B 11.0

Release 11.0.19

Release 11.0.16

Release 11.0.10

Known Issues

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

Release 11.0.35

• BOC-30030

  When an AS4 document is received and IBM webMethods B2B attempts to send an asynchronous receipt signal to the sender, the sender fails to process the receipt signal message due to an authentication issue. The activity log of the receiver shows an error in processing the document, but the processing status remains Done.

• BOC-30023

  When you receive a file in an SFTP inbound channel, IBM webMethods B2B must move it to the configured folder path after processing. If a file with the same name already exists in the folder path, a few cloud platforms do not permit overwriting the existing file with the new one. Consequently, the file gets picked up during file polling and processed multiple times.

  Now, when IBM webMethods B2B receives a file with the same name, it appends the timestamp in the format YYYYMMDDhhmmssSSS to the filename and saves it in the folder path.

Release 11.0.25

• BOC-30424

  IBM webMethods B2B fails to process an RNIF PIP inbound document (for example, 2A9) synchronously, if the HTTP header of the document is empty.

• BOC-30425

  The code list validator is available only when you select the Identifier for the Data type property. The code list validator still appears, even if you modify the Data type property.

• BOC-30228

  When large document handling support is enabled and a cXML payload larger than the value configured in the Large document threshold is submitted, the document is not processed.

  Workaround: Change the value configured in the Large document threshold field as per the cXML payload size or higher, and submit the document.

• BOC-29973

  The All tab on the Identities page displays only the identities of the Standard type.

  Workaround: To view the Custom and Standard identities, use the search box to search for the identity.

Release 11.0.20

• BOC-23792

  When IBM webMethods B2B processes UNEDIFACT, EANCOM, and ODETTE large documents and generates Functional Acknowledgement (FA), the FA transaction and the original transactions do not group on the Transactions page.

  Workaround: To group the original and FA transactions, modify the field value of documentPersistOrder to EnvelopeFirst in EDIPTPA.

Release 11.0.16

• BOC-23592
  IBM webMethods B2B processes the X12 7020 EDI business document with an error “No matching choice value” in an envelope which is added in Course of transaction. This error does not have any functional impact on the processing of the document, and you can ignore this error message.

Release 11

• BOC-22263
  The addTransactionContentPart operation in webMethods.io B2B Connector within IBM webMethods Integration always adds the content parts with partIndex as 0. This results in having all content parts with the same partIndex, and IBM webMethods B2B does not ensure the sequence of retrieved content parts from the getTransactionContentParts operation.
  Workaround: IBM recommends that you validate the sequence of the partName before you map the content parts from getTransactionContentParts operation in the flow service pipeline.
  

• BOC-22185
  Customization of any EDI schema that has a duplicate node is not allowed. For example, UNEDIFACT ORDERS document.
  This issue will be addressed in an upcoming release.
  

• BOC-22188
  An internal check written specifically to address the EDI customization capability was triggered on unsaved updates that were in an inconsistent state, causing a warning message to appear after extracting the document attributes.
  Workaround: Refresh or reload the Document attribute page before you extract a document attribute in the document structure.
  

• BOC-22084
  When you send a cXML document through a cXML-out channel and enable message signing in channel configuration, the validation of the signature on the document fails at the receivers end.
  

• BOC-22186
  The code list validator is not supported for newly created fields in custom X12 EDI business documents.
  

• BOC-22149
  EDI Batch documents do not support Custom ID types.
  

• BIC-23347
  When a tenant has more than one backend server instances, and when the user updates any schema in IBM webMethods B2B, the schema gets updated in one of the IBM webMethods Integration instance simultaneously. These changes sync with other instances within a maximum of ten minutes while the in-flight items allowed to reach the completion state, before it forces the sync.
  IBM recommends that you make design-time activity in production tenants when there is less execution traffic, or when you are aware that no long runs are to happen during the chosen duration. This reduces the chances of retrieving data from a stale node.
  

• BOC-21945
  The custom ID types in a partner profile do not appear on Partner onboarding page because of internal dependencies.
  
  

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

Resolved Issues

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

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.

• 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 assets from one environment (the origin) to another environment (the target) with inherited users is not supported.

• IBM recommends that you should 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 underlying infrastructure provider in each region and the available products, 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: