webMethods.io Integration v11.0 Release Announcement

Software AG is pleased to announce the release of webMethods.io Integration 11.0

Highlights of the release:

  • image

  • Develop anywhere: Develop integrations using either web tooling or Service Designer (offline).

  • Deploy anywhere: Deploy integrations to any environment of your choice.

  • Bring your own packages: Leverage existing webMethods integrations and services in a new unified integration platform.

  • Hybrid connectivity: Orchestrate across cloud providers, on-premises, and between regions while maintaining a single point of control.

  • Control plane: Unified view for all runtime environments whether they are in the cloud, private cloud, or on-premises data centers.

  • Lightweight execution: Provision new runtimes, as and when needed with a single-click deployment.

  • Self-register: Register a runtime and connect to a webMethods.io Integration tenant securely to ensure zero local configuration.

  • Self-provision: Facilitate runtimes dynamically as required to accommodate changes in integration and connectivity.

  • Orchestration: Build integrations on the fly with zero code and deploy and run services on any available webMethods.io Edge Runtime using workflows.

  • Connectivity: Deploy adapters and CloudStreams connectors to any runtime, using workflow orchestration to automate and streamline the deployment process.

  • Monitor: Track and manage the integration performance from beginning to end, regardless of their network topology, using webMethods.io End-to-End Monitoring.

Note: These capabilities are not available by default. Contact your sales representative for more information.

Custom Polling Intervals for Triggers

You can now customize the polling interval of a trigger by selecting the relevant interval from the Polling interval field. In the previous release, the polling interval was 5 minutes with no support for interval customization.

Managing Private APIs, Webhooks, and Services

You can now flag APIs, webhooks, and service invocation as private, that is, these can be used only from other webMethods components running inside your tenant’s network. For instance, API Gateway can be used to secure access to any of these assets without exposing them over the internet.

APIs: REST and SOAP APIs can be marked as private by enabling the Access option during the creation or modification of APIs. Once the API is marked as private, the external API invocation URL is modified to incorporate the private label. Read More

Flow Services: An individual Flow service can be marked as private by enabling the Enable private invocation option.
Read More

Webhook: A webhook can be marked as private by enabling the Private Webhook option during webhook creation or modification. Once a webhook is marked as private, it can be accessed only by API Gateway. This feature is available only for tenants with a paid plan.
Read More

Reorganization of Listeners and Webhooks

From release 11.0, you can access the Listeners and Webhooks functionality through Events under the Projects section.

Enhancements in Insights

You can now access and download the transactions and execution count reports for a specified timeframe using the newly added Reports section in the Insights feature of both Workflows and Flow services.

Enhancements in Queues and Topics in Messaging Service

You can now publish and consume messages from queues and topics created across projects by marking them as shared. This allows collaboration between projects without tight coupling.

Enhancements in Monitor Page

Workflows can now be filtered based on a custom context ID. These identifiers can be set from within the workflow using Set Context Id and assigned any value, such as order ID, customer name, and so on.

OAuth 2.0 (JWT Client Assertion Flow) for REST Connectors

A new authentication method named OAuth 2.0 (JWT Client Assertion Flow) is introduced to connect to REST endpoints in a secure way. This method enables you to generate access tokens for backends that utilize OAuth 2.0 by allowing clients to create digitally signed JWT assertions.

Additionally, you can include custom fields by clicking the Add field button, which appears when you select the OAuth 2.0 (JWT Client Assertion Flow) authentication method. These custom fields are then displayed on the Add Account window when creating an account for the REST connector.

Note: Currently, webMethods.io Integration supports this authentication method exclusively for Microsoft endpoints.

New Project APIs

The following new APIs have been introduced in the Project APIs domain:

Export: Allows you to export a project along with its valid assets into a zip file.

Import: Allows you to import a project exported by another tenant to your tenant.

Changes in the Token Management Page

The Token Management page in Settings > OAuth2.0 has been modified to address security vulnerabilities. The Access Token and Refresh Token columns are now hidden, preventing other users from accessing or viewing your tokens.

Send email action will be removed from new Free Forever tenants.