Pankaj Agrawal

Integration Server

The runtime engine for webMethods flow services, Java services, and adapters. Hosts the packages that implement business logic, connects to backend systems via adapters, and exposes services over HTTP/S, JMS, and SOAP.

BPM

webMethods Business Process Management models long-running, human- and system-driven processes as executable diagrams, coordinating tasks across systems and people with monitoring built in.

My webMethods Server

The web-based portal (MWS) for task inboxes, process monitoring dashboards, and administrative consoles used by business and operations teams to interact with running integrations.

Trading Networks

The B2B gateway for partner document exchange — EDI, XML, flat files — providing partner profiles, document routing rules, and processing rule chains with full audit trail.

Universal Messaging

Enterprise pub/sub and point-to-point messaging middleware providing guaranteed delivery, clustering, and multi-protocol support (JMS, AMQP) as the backbone between decoupled systems.

API Gateway

Manages the full API lifecycle — publishing, policy enforcement (throttling, auth, transformation), versioning, and analytics — as the governed front door to backend and Integration Server services.

MFT (Managed File Transfer)

Secure, monitored file transfer with delivery guarantees, encryption, and event notifications — used where B2B partners or legacy systems exchange data as files rather than API calls.

Java

Used for custom Java services within webMethods where flow services alone are impractical — complex parsing, performance-sensitive transforms, or integration with Java-only libraries.

REST

Primary protocol for modern service-to-service and partner integrations — resource-oriented APIs, typically JSON, exposed and consumed through webMethods REST descriptors and API Gateway.

SOAP

Contract-first XML messaging protocol still common with legacy enterprise systems (SAP, mainframes) where WSDL-defined contracts and WS-Security are required.

JSON / XML

The two dominant payload formats in integration work — JSON for modern REST APIs, XML for SOAP, EDI-adjacent, and many legacy enterprise interfaces.

Oracle / SQL

Relational database integration — reading from and writing to Oracle as a system of record via JDBC adapters, stored procedures, and batch loads.

AWS

Cloud infrastructure and managed services used when extending on-prem webMethods integrations to cloud-native workloads or hybrid deployments.

Git

Version control for flow service packages, configuration, and supporting code — essential for team-based webMethods development and CI/CD.

Postman / SoapUI

API testing tools used to validate REST and SOAP services independently of the integration platform, including contract, load, and regression testing.

Workato

Cloud-based iPaaS used for lighter-weight SaaS-to-SaaS integrations, complementing webMethods for scenarios where a full on-prem platform is unnecessary.