Release 11.0.10

What's New

Built-In-Services added for Flow services

New services are added for the JWT, SMIME, Security, Keystore, pkcs7, Document, String, and MIME under the Built-in Services section in the following categories:

• JWT: extractClaimsFromJWT, generateSignedJWT AND verifyJWT
  
• SMIME:createCertsOnlyData, createEncryptedData, processCertsOnlyData, processSignedData, createSignedData and processEncryptedData
  
• Security:generateHashValue, generateSalt, decrypt, encrypt, sign, decryptAndVerify, signAndEncrypt, verify, createMessageDigest, getCertificateInfo, loadPKCS7CertChain, decryptXML, encryptXML, signXML and getKeyAndChain
  
• Keystore: getCertificate and getTrustedCertificates
  
• pkcs7: sign and verify
  
• Document: documentToXMLValues and XMLValuesToDocument
  
• String: isNullEmptyOrWhitespace and lookupTable
  
• Mime: releaseBodyPartReferenceInTSpace
  

Read More

Enhancement in Flow Service Utility: logCustomMessage

Starting from IBM webMethods Integration 11.0.10 release, new tenants are subject to the maximum size limit of 1 MB for custom log messages.

Read More

Enhancement for Set Value Updates through JSON Configuration

Users can now add new data to a JSON file, which automatically updates the user interface, eliminating the need for code changes for each new value.

Previously, users had to set values for the fields in the pipeline editor by selecting the values from a predefined list that required code changes for each new value.

Skip Dependencies during Flow Service Export and Import

Users can select Skip dependencies while exporting or importing a flow service. This option allows exporting only the parent flow service, excluding its associated dependent services, packages, or configurations.
Read More

New Scheduler Feature in Events page

The newly added unified Scheduler functionality in IBM webMethods Integration, provides a consolidated view of all existing scheduled services within a specific project. This allows users to manage multiple schedules simultaneously.

Read More

Manage Message Destinations

A new field, Capacity, has been added and is now available when creating and editing messaging destinations, queues and topics. Users can configure the Capacity field to configure the limit on the maximum number of messages an individual queue or topic can hold while waiting for subscribers to consume the pending messages.

Read More

Enhancement in Subscriber Error Handling Mechanisms

A new Resource monitoring service field is added in the Transient error handling section that monitors resource availability for subscribers at regular intervals until it confirms resource availability and re-enables subscribers suspended due to transient errors.

Read More

Two-Way SSL Support in Database Connector

The Database connector has been enhanced to support Two-Way SSL. For Two-Way SSL authentication, users must configure the Keystore Alias and Truststore Alias.

Read More

Update in Project Deletion Process

The project deletion process has been updated to allow users to forcefully delete projects in a single step, without the need to manually remove associated assets such as workflows, flow services, and other assets. Previously, projects could only be deleted after manually removing all related assets. This enhancement streamlines the process, improving efficiency and reducing overhead.

Read More

API Enhancements

The following changes have been made to the API domains listed below:

• All Public APIs: When a request to any public API fails, the error source is now included in the response. This update applies to all public APIs, providing more detailed information about the cause of the failure.

  Read More

• Project API:

  • Users can now forcefully delete a project and all its assets by sending a request with the following body, along with the authentication details for the tenant linked to the project:

    Headers: 
    {             
        Authorization: BasicAuth
    }
    Body: 
    {
        "force_delete": true,
        "confirm_project_name": "Delete <project_name>"
    }

    Previously, projects could only be deleted after manually removing all related assets.

  • When deploying or importing a project, if the request fails, the error details are included in the output under the message key. For example,

    {
    "error": 
    {
        "status": "IMPORT_FAIL",
        "message": "Failed to fetch the deployment data.",
        "errorSource": 
        {
            "errorCode": "API_000",
            "requestID": "API-6d72b18c-5c30-4626-97ea-56ea1e9269d8"
        }
    }
    }

  Read More

Enhanced Preferences for Improved Usability

The Preferences section has been enhanced to improve usability:

• Global Preferences now include options like Autocommit and Re-use account that apply across the entire tenant and impact all users within that tenant. These preferences are configured at the administrative level and are typically controlled by the tenant administrators.

• User-Specific Preferences that apply to individual users and affect only their personal environment or interface. This allows customization of the application’s behavior or appearance to suit each user’s needs.
  Read More

New Add-ons Tab for Enhanced Capabilities

A new tab, Add-ons, has been added under Settings allowing users to include powerful enhancements to extend the application’s capabilities:

• Smart Mapping is now available, leveraging the collective intelligence of the IBM webMethods Integration community to recommend optimal field mappings from source to target. By enabling this feature, you provide your consent for IBM webMethods Integration to collect certain mapping information to improve recommendations.
  Read More

Support for New External Git Repositories

Users can now store their integration projects in GitLab and Bitbucket, as well as GitHub.

Read More

Private Runtime Ownership Transfer and Sharing

• Transfer Private Runtimes Ownership

  • Users can now transfer ownership of a private runtime to another user, if they wish to give primary responsibility for the project to someone else.

  • To avoid orphaned runtimes administrators can transfer the ownership of any runtime to another user within the organization.

• Sharing Private Runtimes

  • Users can share their private runtimes with other users, enabling collaborative work on the same runtime.

  • The owner has control over the individual users who can access and work on the private runtime, ensuring flexible and secure collaboration.

New options, Transfer Ownership, Share, and Collaborators are provided in the vertical ellipsis menu of the runtime card for transferring and sharing runtimes.
Read More

Restrictions for Runtime Instance Deletion

On the Runtime Instance Listing page, users are not allowed to delete the last remaining instance as there must always be at least one instance. Note that the Runtime Instance Listing page is not displayed if users revisit the Runtime Instance Listing page after switching to a single instance.

Read More

Runtime Card Status Changes

The status on the runtime card now reflects based on the instance’s status instead of the runtime alone.

Read More

Runtime Management APIs

New APIs have been added to allow users to create and manage runtimes.

Read More

Integration Runtime Dashboard Enhancements

• Integration Runtime Security Vulnerabilities: The Integration Runtimes Dashboard has been enhanced to provide an overview of potential security risks, including misconfigurations, exposed services, insufficient access controls, and insecure APIs within your runtime environment. The vulnerabilities across your runtime are grouped and displayed under various sections as follows:
  • About
  • Ports
  • APIs
  • Ports
  • Allowed services
  • Key/Certificate stores

These insights allow users to prioritize and address critical issues quickly, improving the overall security of their runtime.

• Integration Runtimes Dashboard Page Layout: A new left navigation pane has been added allowing users to easily navigate across the dashboard instead of the horizontal tabbed approach. This new layout provides quicker, more efficient access to key areas of the dashboard.

• Adapter Connections: A new column, Status, has been added to indicate the enabled and suspended connections.

Read More

Support to View Global Variables in Custom Packages

Users can now view the variables for custom packages imported into their projects. These package-specific variables are accessible at the project level. This enhancement provides a unified interface, ensuring that all relevant variables, whether from the project or imported packages, are easily accessible in one place, streamlining the workflow and improving usability.

The package-level variables can now be viewed under the respective packages in Project > Configurations > General > Variables.

Previously, users had no way to know what variables if any the package referenced.

Read More

New Package Services Icon and Enhanced Deploy Anywhere Flow Services Listing in Workflows

The Package Services icon () has been updated under Workflows. Additionally, deploy anywhere flow services are now correctly listed under Services in Workflows.

Enhanced Packages View

The Packages view is updated to provide a comprehensive view of all packages associated with the project. Previously, system package entries were not displayed.

Sync Report Download

Users can download a Sync report in JSON format to view the latest synchronization details for a specific runtime. Ensure the runtime is Running, as the sync report is unavailable if the runtime is disabled or offline.
Read More

Support for Accessing Deploy Anywhere Flow Services in Flow Services

Users can now use deploy anywhere flow services within a flow service, enabling seamless deployment of services in various environments directly from the flow.

Read More

Cleanup of Stopped Edge Runtime Instances

Edge runtime instances that are stopped (shut down) are now automatically cleaned up, that is, removed from the Runtime Instances list. This ensures that environment-related instances can scale up and down as required, removing the need to manually delete references to instances that are no longer running.

This does not apply to instances in the Unknown state, where communication has been lost but the instance may still be running.

Improved Access to Package Registry

Users no longer need to link package registry to a tenant using Empower credentials, as this process is now handled through SAML-based Single Sign-On (SSO) authentication.

New Connectors for Develop Anywhere, Deploy Anywhere

The following connectors are now supported in Develop Anywhere, Deploy Anywhere:

• AS/400
• HDFS
• Sharepoint
• Peoplesoft

New and Updated Connectors

Explore new and updated connectors released recently in IBM webMethods Integration.

Read More

Kafka Connector

Kafka connector is now available for IBM webMethods Integration.

Kafka connector enables seamless data exchange with both Apache Kafka and Confluent Kafka, which are distributed publish-subscribe messaging systems. The connector provides a unified, high-throughput, and low-latency platform for managing real-time data streams effectively. Using the Kafka connector, you can create actions and perform various operations, such as retrieving data from or inserting data into Kafka topics.

Read More

Fixes

See the Fixes section for information.

Customer Actions

This section provides information on the actions you need to perform before or after upgrading to IBM webMethods Integration v11.0.10 and the subsequent release patches or fixes.

Notice: Disruption of Services

• Containers Portal: Starting February 20, 2025, the authentication will be exclusively IBM ID. Previously generated registry tokens will be removed. After the transition, users may notice token authentication errors while pulling or refreshing Edge Runtime images from the portal. The digital signature for some container images may be temporarily unavailable.
  
  Customer Action Required: Create an IBM ID and generate new tokens using the IBM ID authentication method. Use the new tokens in your docker commands and scripts. For more information on how to create the IBM ID, see Containers Portal.

• IBM webMethods Package Registry: On February 20, 2025, the service may be temporarily unavailable due to a subscription change in the infrastructure.
  
  Customer Action Required: No action required. Retry the operation after a few minutes if any failure is observed.

Edge Runtime Sync Request Timeout

Sometimes, users may encounter errors during sync requests on existing Edge Runtimes if the sync process takes too long. In such cases, if there is no warning sign on the Sync icon, users can do one of the following actions:

• Ignore the errors and proceed with the service executions as this indicates that the sync has been completed successfully.

• Create a new Edge Runtime or a new instance with the latest Edge Runtime image.

Fixes

This section provides information on the fixes for IBM webMethods Integration version 11.0.10 and the subsequent release patches.

Known Issues

This section provides information on known issues for IBM webMethods Integration v11.0.10 and the subsequent release patches.

Events

WACN-168
Polling notifications are not being enabled when database objects already exist and the following error message appears:
Error: The database objects for “xxx” notification already exist. You can delete the objects and try enabling the notification again. To delete the existing database objects use the “pub.pollingNotificationUtils:dropDatabaseObjects” service.

Workaround: Either delete or drop related database objects.

WACN-161
Ordered Notification is not being enabled when multiple conditions are added for multi-table selection and the following error message appears:
Error: Cannot enable Polling Notifications : “xxx”. Cause: Execution of DDL query of Notification failed during enable/disable. Please check the datatypes of columns selected in notification. ORA-00907: missing right parenthesis

Workaround: Specify query conditions using only a single table for notifications.

Events

WACN-168
Polling notifications are not being enabled when database objects already exist and the following error message appears:
Error: The database objects for “xxx” notification already exist. You can delete the objects and try enabling the notification again. To delete the existing database objects use the “pub.pollingNotificationUtils:dropDatabaseObjects” service.

Workaround: Either delete or drop related database objects.

WACN-161
Ordered Notification is not being enabled when multiple conditions are added for multi-table selection and the following error message appears:
Error: Cannot enable Polling Notifications : “xxx”. Cause: Execution of DDL query of Notification failed during enable/disable. Please check the datatypes of columns selected in notification. ORA-00907: missing right parenthesis

Workaround: Specify query conditions using only a single table for notifications.

Workflows

WFL-7337
Test button fails for workflow actions containing a filepath field.
Workaround: If the Test button does not work as expected for a workflow action, manually run the workflow. Then, use the execution log data from the relevant action to map and configure the rest of the workflow.

WFL-4488
When users send bursts of sync workflow execution requests over the rate limit to IBM webMethods Integration, sometimes they receive “System: The requested operation cannot be performed at the moment. Please try again after some time.” error.
Workaround: Send sync workflow execution requests in smaller batches.

WFL-2759
When you create a custom Node.js connector with label (name) as test and test it, the output shows error.
Workarounds:

• Avoid using test label for custom Node.js connectors.
• Do not test a custom Node.js connector labelled as test. You can instead directly execute it.

BIC-5324
After logging out from IBM webMethods iPaaS, when a user logs in again using a different username and then navigates to IBM webMethods Integration using the App Switcher, the user sees that the earlier user’s session has still not been logged out.
Workaround: Log out from IBM webMethods Integration instead of from IBM webMethods iPaaS.

Flow Services

FLOW-6776
Keystore and truststore aliases from the source tenant remain in the target tenant after flow services are published, deployed, or imported, but are not visible there.
Workaround: Users must reconfigure the keystore and truststore aliases as per the target tenant to avoid any discrepancies.

FLOW-2575
In a transform pipeline, when both direct mappings and prediction mappings are present and you try to scroll the pipelineInput or pipelineOutput columns, the mapping lines are broken.
Workaround: Collapse and expand the direct mappings. The mapping lines will be repainted properly. This issue exists only when the scroll bar exists and you scroll either horizontally or vertically.

FLOW-2215
The icon position for adding a new Flow service step is not proper when the Expand All and the Collapse All buttons are used.
Workaround: Toggle the expanded state of the step on which the icon appears. This corrects the icon position when adding a new step.

Flow-4355
Ensure that you provide correct values for the input fields in the Set Value or Run dialog boxes when running a Flow service. This is because the input values are not validated according to their data types by the system and you may encounter errors.

Connectors

WACN-300
In Kafka connector, the consumer action fails to run correctly when offset and partition values are provided at runtime, resulting in an error.
Workaround: Specify the partition value at design time to avoid the error.

WACN-307
In Kafka connector, when you select Avro as a key or a value serializer or deserializer, the connection cannot be established or tested resulting in the following error:
Missing required configuration “schema.registry.url”.
Support for configuring schema registry and Avro serializer or deserializer is not included in the 11.0.10 release.

WACN-326
When the Kafka connector is disabled in IBM webMethods Integration, the connector is not listed on the connector’s page as expected. However, it is still visible on the flow service’s page, which is not as expected because the connector should be completely hidden when it is disabled.

WFL-7078
When a user updates a SOAP connector with another WSDL file having different port bindings, the new connector URL and port binding value do not get updated in the existing account of that SOAP connector.
Workaround: Create a new account for that SOAP connector instead of updating the existing account.

JDB-3597
When a Database service is edited, a side panel appears by default, which hides the delete or edit button.
Workaround: Minimize the overlay or side panel.

JDB-3602
When the Firefox web browser is used to add or edit the Database Account, port number validation fails.

WSP-1999
SAP® ERP metadata lookup for a business object intermittently returns empty data.

WSP-1573
Unable to edit imported action with created account.
An account name is associated with each SAP® ERP action. If the account with associated account name is not enabled in the project, the SAP® ERP action cannot be edited.
When an export/import function is used, the SAP® ERP action in the target project contains the associated account name.
However, the SAP® ERP account is not created in the target project.
Workaround: To edit the SAP® ERP action in the target project, do the following:
- If an SAP® ERP account with an associated account name exists in the target project, enable the SAP® ERP account in the target project and disable it in all other projects.
- If an SAP® ERP account with an associated account name does not exist in the target project, create and enable the SAP® ERP account in the target project.

JDB-2977
In the Database connector, updating an Update operation leads to incorrect output.
Workaround: Once you add or delete the table columns or data fields, verify the input/output names and update the proper input/output names if they are not correct.

JDB-3112
Editing an imported workflow or flow service having database connector operations displays an error.
When a workflow or a flow service is exported using the IBM webMethods Integration export functionality, the connection name is not saved in the exported workflow or flow service. On editing the database operation in the imported workflow or flow service, the connection associated with the action is not found.
Workaround: The imported workflow or flow service having database operations can be executed with a valid connection.

JDB-3106
The SQL query in CustomSQL is parsed by the system using a third-party SQL query parser (FoundationDB SQL Parser) to populate the input and output. When the SQL query parser is unable to parse, the error Failed to fetch Database Metadata appears.
Workaround: If the input and output for CustomSQL operation is not populated, ignore the error and configure the input and output explicitly.

WACN-81
The database connection gets disabled whenever the edge runtime container restarts.
Workaround: You can resync the edge runtime from the Flow Editor page or, do the following:
1. Go to Integration Runtimes > Connections page of the corresponding edge runtime.
2. Click the Restart option for the relevant database connection to initiate the restart of the connection.

Listeners

WSP-1758
Contact Support error observed while deploying a project having an SAP® ERP listener. This issue occurs while deploying a project having SAP® ERP listener notifications.
When you deploy a project containing SAP® ERP listener notifications, the deploy wizard provides you with an option to either create a new listener or select an existing listener. This listener is associated with the listener notification being deployed.
When you select a listener from the drop-down list, which is in disabled mode or enable pending mode, the listener notification deployment fails with an error related to enabling the listener. If you continue with the deployment even after the error, An error occurred while processing your request. Contact support. error message appears.
Workaround: Always select an enabled listener while deploying a project having SAP® ERP listener notifications.

Monitor

BIC-8481
Users are unable to update the custom time field under the Monitor tab with a simple click in Firefox browser.
Workaround: In Firefox, users can clear the time field value they want to update and re-enter the required value. Alternatively they can use any other browser to update the custom time field value with a simple click.

Monitor in Deploy Anywhere, Develop Anywhere

WFL-2715
In the Monitor page, if you select multiple projects in the Filters field, then the Executions list displays each project as a separate entry in the list. This is applicable for projects having Develop anywhere, deploy anywhere assets.

WIE-347
The Download logs option is not be available for the cloud and edge runtime transactions on the Monitor > Flow service execution page.

Projects in Deploy Anywhere, Develop Anywhere

WIE-739
The access control permissions are not supported for IBM webMethods Integration Projects.

WS-91736
You cannot work on projects and assets created by other users.

WIE-1393
Projects prefixed with the WM word are currently designated exclusively for product packages within edge runtimes. Any develop anywhere, deploy anywhere assets generated within these projects are not deployed to the edge runtime.

Integration Runtimes User Interface

WIE-348
The mouse pointer does not respond when you hover on the button corners.

Cloud Runtime

WF-30013
Occasionally, project dependency packages may not be automatically restored after the cloud runtime restarts.
Workaround: The recommended approach is to manually add those packages again in such cases.

Edge Runtime

An edge runtime running in a Virtual Private Cloud (VPC) connects to IBM webMethods Integration through an outbound internet connection rather than through any private link.

Connectors in Deploy Anywhere, Develop Anywhere

PIE-82107
The Database connector icon is not displayed in the Flow service Listing view for deploy anywhere flow services.

JDB-3597
The Delete button is not visible while editing a custom action for the Database connector. The Delete button is hidden under the Overview page.
Workaround: You must toggle the Overview page to perform the Delete action.

JDB-3846
You cannot deploy a deploy anywhere flow service from an edge runtime to cloud runtime. A connection not available error appears. This error occurs as the database account in the cloud runtime is in the disabled state.
Workaround:
1. Navigate to Integration Runtimes.
2. Select Cloud Runtime.
3. Go to the Connections tab.
4. Enable the connection.
5. Run the deploy anywhere flow service.

JDB-3602
The port numbers are not validated in the Database connector’s Add account dialog box.

JDB-3851
If the Firefox web browser is used to add or edit the database account, port number validation fails.

JDB-3858
The Driver Group and DataSource Class fields are displayed as text fields instead of drop-down lists when editing connections.

PIE-85083
The disabled database connection in an edge runtime is enabled automatically after syncing the deploy anywhere flow services.

PIE-87599
The database connection gets disabled whenever the edge runtime container restarts. Workaround: You can resync the edge runtime from the Flow Editor page or, do the following:
1. Go to Integration Runtimes > Connections page of the corresponding edge runtime.
2. Click the Restart option for the relevant database connection to initiate the restart of the connection.

WPS-5
Date type values retrieved in the IBM Power connector displays as one day old when the IBM Power server and the connector operate in different time zones. This discrepancy affects date values in operations such as Write DataQueue, Read DataQueue, and Call Program services. This issue does not occur if the server and connector time zones are the same.

WPS-12
The Call Command Service’s Command Name drop-down field lists both the non-interactive and interactive command names. It is important to note that this service is designed specifically for the execution of non-interactive batch commands. Workaround: Users must select only non-interactive commands for the service to provide the desired results. Selection of interactive commands may not provide the expected results.

WIE-1798
You cannot sync your package while creating an action in the Database connector in Flow Editor.
Workaround: To sync a package while creating an action in the Database connector, you need to do the following:
1. Go to Integration Runtimes and select the Edge Runtime. The Edge Runtime dashboard appears.
2. Go to Projects.
3. Click Sync. The package gets refreshed with the latest changes.

Workflows in Develop Anywhere, Deploy Anywhere

Deploy Anywhere Flow Services

WIE-1012
The Sync button is in disabled mode by default. It is enabled after you save the service.

WIE-361, WIE-400
The Sync In Progress dialog box does not respond when you try to run a deploy anywhere flow service with errors.

WIE-343
The error message, The Edge Runtime Default is unavailable appears when you try to run a deploy anywhere flow service that is having a flow step without any action.

PIE-84576
Deploy anywhere flow service fails with a b2b exception. This is due to an expired or unpaired Empower token. If any of the project in edge runtime has the Database account created using this token will pose issue.
Workaround: Create a database account with a valid token and run the services.

WIE-354
The cloned deploy anywhere flow services are not listed in the warning message when you try to delete any custom operations.

WIE-1302
Deploy anywhere flow service invocations have the default timeout set to one minute. Due to this, the deploy anywhere flow services that have larger processing times, higher payloads, or complex steps might take more than a minute, causing the service to fail with a timeout error. Currently, this value is not configurable.

Packages

PIE-93487
In the Security feature, enabling Java services from Allowed to Denied throws an error.

PIE-83907
The REST and SOAP resources for dependent packages are not displayed in the Assets page.

PIE-84029
The asset details displayed in the Assets Page do not include nested packages imported from GitHub.
Workaround: You must manually install packages.

PIE-83193
Deploy anywhere flow services using dependent custom packages might encounter errors if the dependent custom packages are deleted. This issue is observed in scenarios where the custom packages were added as dependents to other projects in the same tenant.
Workaround: Recommendation is not to add custom packages as dependents to the projects that are in the same tenant.