All Products

WebSphere Developer Debugger for System z provided a graphical interface for the Debug Tool for z/OS, enabling developers to debug applications running on z/OS. Key components included the Debugger client, the Debug Tool engine on z/OS, and the communication layer. The Debugger client, running on a workstation, connected to the Debug Tool engine on the mainframe. Communication occurred over TCP/IP....

WebSphere Developer for System z was an Eclipse-based IDE designed to streamline z/OS application development. It provided a PC-based environment for developers to create, edit, compile, and debug mainframe applications. The IDE connected to the z/OS host via the Remote Systems Explorer (RSE), enabling access to datasets, members, and other resources. Key features included support for COBOL, PL/I, and C/C++,...

Websphere Enterprise Service Bus (WESB) was an IBM product designed to integrate applications using a Service Integration Bus (SIB). It offered features for message routing, transformation, and security. Key components included mediation flows for message processing and support for standards like SOAP and REST APIs. WESB supported authentication methods such as user ID/password and X.509 certificates. The administrative console provided...

WebSphere Event Broker provided a publish-subscribe messaging infrastructure, enabling asynchronous communication between applications. Key components included the broker itself and the WebSphere Event Broker Explorer GUI. The broker used MQ messaging for communication, and configuration was managed through configuration files and the GUI. The product is not supported. Users should migrate to a supported platform such as IBM MQ or...

WebSphere Extended Deployment (WXD) provided enhanced capabilities for WebSphere Application Server, including in-memory data grids (eXtreme Scale), parallel processing (Compute Grid), and dynamic workload management (Virtual Enterprise). These features aimed to improve application performance, scalability, and resource utilization. Key components included the WebSphere Application Server, eXtreme Scale data grid, Compute Grid runtime, and Virtual Enterprise management tools. Administrative interfaces included...

WebSphere Extended Deployment Compute Grid provided a batch processing environment built on WebSphere Application Server. Key components included the Job Scheduler, Job Manager, and Execution Nodes. The Job Scheduler managed job submissions and schedules, while the Job Manager controlled job execution and monitored status. Execution Nodes ran the batch jobs. The system supported job scheduling, history tracking, and integration with...

WebSphere eXtreme Scale (WXS) is a distributed in-memory data grid designed for high-volume transaction processing. Key components include the ObjectGrid, Catalog Service, and Container Servers. WXS uses Java and REST APIs for data access, with operations like `put`, `get`, and `remove`. It supports RBAC for security and communicates via TCP/IP. WXS provides high availability through data replication and failover. Compared...

WebSphere Host Publisher provided a means to modernize access to legacy 3270 applications by creating a web-based interface. The architecture comprised Host Publisher Studio for development and Host Publisher Server for runtime. APIs, likely using HTTP, facilitated communication. Authentication was likely handled through user ID/password and LDAP integration. Key benefits included extending the life of legacy systems and simplifying user...

Websphere ILOG Decision Validation Services for z/OS was designed to enhance the testing and validation of business rules within the ILOG Rule Team Server environment. The product's architecture comprised key components such as the Rule Execution Server and the Decision Validation component, which communicated to facilitate rule validation and execution. The product offered APIs, including SOAP, for integration with other...

Websphere ILOG JRules for z/OS is a runtime component for executing business rules on the z/OS platform. It integrates with Websphere Application Server and is designed to automate decision-making processes. Key components include the rule execution engine and integration modules for the application server. The product provides APIs for rule execution and management. The administrative interface is the Websphere Application...

Websphere ILOG Rule Team Server for z/OS provided a comprehensive environment for managing business rules. The system comprised several key components, including the Rule Team Server for rule authoring and management, the Rule Execution Server for rule execution, and DB2 for persistent storage. The Rule Team Server offered a web-based console for administration, user management, and configuration. Authentication was handled...

Websphere ILOG Rules for COBOL, a runtime component for COBOL applications on z/OS, enabled the implementation of business rules within CICS and batch environments. The product, originally from ILOG and later part of IBM's portfolio, generated COBOL code from business rules defined using the ILOG Business Rule Management System. Key components included the Rule Engine, Rule Repository, and Rule Designer....

Websphere Information Integrator Classic Event Publisher for CA-IDMS provided a solution for real-time data integration by capturing and publishing CA IDMS database changes. Key components included the Event Capture Service, which monitored the CA IDMS database for changes; the Event Processing Engine, which transformed and filtered events; and the Event Publication Service, which delivered events to destinations via Websphere MQ....

WebSphere Information Integrator Classic Event Publisher for IMS provides a mechanism to capture and publish IMS database changes in real-time. The system comprises components such as the Event Capture component, the Event Processing Engine, and the WebSphere MQ Publisher. The Event Capture component monitors IMS logs for changes. The Event Processing Engine transforms and filters events. The WebSphere MQ Publisher...

WebSphere Information Integrator Classic Event Publisher for VSAM provided real-time data integration by capturing and publishing VSAM file changes to WebSphere MQ. Key components included the VSAM Event Capture component, the Event Processing Engine, and the WebSphere MQ Publisher. The product used configuration files to define VSAM files to monitor and event handling. It integrated with z/OS security for authentication...

Websphere Information Integrator Replication (WIIR) provided data replication capabilities between DB2 databases using a publish-and-subscribe model. Key components included the Capture and Apply components, which worked with Websphere MQ for asynchronous data transfer. The CLI was the primary administrative interface. WIIR supported data transformations using SQL-based expressions. The product's main use cases included data warehousing and disaster recovery. WIIR is...

WebSphere Message Administration Facility (WMAF) was a web-based application designed for managing SWIFTNet FIN messages on z/OS. It provided a centralized interface for creating, editing, and routing messages. The system comprised the WebSphere Portal server for the user interface and a DB2 database for data storage. Key features included message creation, modification, and backout capabilities. WMAF supported user authentication through...

Websphere MQ Advanced Message Security (AMS) provided message-level security features for IBM MQ. Key capabilities included encryption, digital signatures, and access control, ensuring confidentiality, integrity, and authentication of messages. AMS used X.509 certificates for authentication and supported various encryption algorithms like AES. The core components were the AMS agent, policy repository, and keystore. The AMS agent intercepted messages, applied security...

WebSphere MQ File Transfer Edition (FTE) provided a solution for secure and reliable file transfers within an MQ environment. It supported various transfer scenarios, including point-to-point and scheduled transfers. Key components included agents, which facilitated file movement, and MQ channels, which handled communication. FTE used MQ's security features for authentication and access control. The primary administrative interface was the command-line...