In today’s fast-moving, API-driven world, the ability to connect business processes seamlessly across internal and external systems is a game-changer. Many organisations rely on webMethods Integration to design, orchestrate, and automate their workflows. But what if those workflows could be instantly triggered through a secure, well-governed API? 

With IBM API Connect, enterprises can transform their webMethods Integration workflows into reusable, easily managed, and even monetizable APIs. This powerful combination extends integration capabilities, accelerates innovation, and opens the door to new business opportunities. 

Realising the full potential with IBM webMethods Hybrid Integration (IWHI) 

IBM webMethods Hybrid Integration (IWHI) is an AI-powered platform built for the complexity of modern enterprise IT. It takes the combination of IBM API Connect and webMethods Integration to the next level, while also offering many additional capabilities through a unified, end-to-end integration experience.

Within IWHI, organisations can select the capabilities that best match their integration needs—APIs, applications, events, files, and more. The platform also includes tools like End-to-End monitoring, giving enterprises enhanced visibility into transactions and integrations across these capabilities.

The Integration Flow

Here’s how it works at a high level: 

1. Add the required capabilities within the IWHI platform—for this example, select API Connect and webMethods Integration. 
2. Create a workflow in webMethods Integration—this could be anything from handling customer onboarding to orchestrating complex, multi-system processes. Then export the OpenAPI specification of the integration. 
3. Import the OpenAPI specification into API Connect to expose an API that serves as the secure entry point. 
4. Invoke the API—when called, it triggers the workflow in webMethods Integration. 

API Connect handles security, governance, and monitoring of API access, while webMethods Integration executes the underlying business logic. 

Business Benefits for Enterprises 

• Faster Time to Market – Expose existing workflows as APIs quickly. 
• High Reusability – Apply the same integration logic across different applications, channels, and business scenarios. 
• New Revenue Opportunities – Monetize select workflows by offering them as premium or paid APIs. 
• Robust Security and Governance – Safeguard workflows with enterprise-grade security, authentication, and policy enforcement. 
• Actionable Insights – Monitor usage patterns and performance to optimize workflows and API delivery. 
• Stronger Partner Collaboration – Give trusted partners secure, controlled access to critical business processes. 

Detailed steps

Configure webMethods Integration  

1. Provision and open the capability 
   • Provision webMethods Integration from the Manage Capabilities section in IWHI. Once provisioned, select it to start using the capability. 
2. Create a sample workflow 
   • For illustration purposes, let’s create a simple workflow that logs a message. More details on creating workflows can be found here.
   • Create a project in webMethods Integration called LoggerDemo. 
   • Inside the project, create a new workflow. 
   • From Developer Tools, drag the Logger action into the workflow steps. 
   • Open the gear icon on the Logger action and configure the details (e.g., add a log message). 
3. Configure the workflow trigger
   • Change the workflow trigger to Webhook. 
   • Set authentication to None. 
   • Turn on Autoconnect Return Sync on Webhook. 
   • Open the gear icon for the Autoconnect Return Sync on Webhook action and fill in the necessary details. 
   • Connect the Logger action with the Autoconnect Return Sync on Webhook action. 
4. Test the workflow 
   • Run the workflow by clicking the Play icon. 
   • Check the status of the workflow from the Monitoring tab. 
5. Create an API for the workflow 
   • In the LoggerDemo project, click on APIs and create a new API. 
   • Add a REST resource by clicking Add Resource and select an HTTP method. 
   • Choose Logger as the service and save. 
6. Export the OpenAPI specification 
   • Go to the API details page. 
   • Click the Download icon next to Documentation Public URL (JSON). This will download the OpenAPI specification for the API. 

Configure APIConnect Integration

1. Provision and open the capability 
   • Provision API Connect from the Manage Capabilities section in IWHI. Once provisioned, select it to start using the capability. 
2. Create a new API 
   • From the left vertical menu, click Develop (pencil icon). 
   • Press Add, then select API. 
   • Keep the default as OpenAPI 2.0 and choose From existing OpenAPI service. 
   • Click Next, then upload the OpenAPI specification exported from webMethods Integration. 
   • Click Next again, optionally update the API details, and proceed. 
   • On the Secure screen, leave everything checked. 
   • Click Next, then choose Edit API. 
3. Remove the security with _apiKeyAuth (We will be setting this up to call the webMethods integration API in step 5): 
   • Navigate to Paths > /latest > Operations > GET > Security. 
   • Delete _apiKeyAuth and confirm. 
   • Go to Security Schemes, delete _apiKeyAuth, and confirm. 
   • Save the changes. 
4. Set up application identification using Client ID/Secret
   • Add a new Security Scheme for Client ID
     • Go to Security Schemes and click on +  
     • Select Security definition type as apikey
     • Select Key type as client id
     • Select Located in as header 
   • Add another Security Scheme for Client Secret 
     • Go to Security Schemes and click on + 
     • Select Security definition type as apikey 
     • Select Key type as client secret 
     • Select Located in as header
   • Return to Paths > /latest > Operations > GET > Security and associate the operation with the new Client ID and Client Secret security schemes.

   • Save the changes.

5. Set up API key to call webMethods integration
   • Navigate to Gateway > Policies 
   • Click Add Action and leave the action as Set. 
   • Configure the variables: 
     • Variable name: message.headers.X-INSTANCE-API-KEY 
     • Type: String 
     • Value: Your API Key
   • Save the configuration. 

Note: The API key can be obtained from the IBM SaaS Console. Navigate to Subscriptions > IBM webMethods Hybrid Integration > Instance, then create a Service ID with the Integration Admin role. Next, generate an API key by specifying this Service ID. 

The API can now be invoked by passing the Client ID and Client Secret in headers. Client ID and Client secret can be obtained when the consumer subscribes to the API Developer Portal in APIConnect. Invoking the API via API Connect securely triggers the webMethods Integration workflow within a governed environment.

Gain Full Visibility with End-to-End Monitoring in IWHI 

One of the most powerful features of IBM webMethods Hybrid Integration (IWHI) is its ability to provide End-to-End monitoring. By combining IBM API Connect and webMethods Integration within IWHI, organizations gain deep insights into business transactions and integration flows—all from a single, unified dashboard. 

Once inside, we can view the example we created in the End-to-End Monitoring dashboard. This provides a clear view of the transaction flow across IBM API Connect and webMethods Integration—all in one place.