WebTek Modernization Guide

WebTek aimed to provide a way to access and modernize legacy CICS (Customer Information Control System) applications through web interfaces, offering an alternative to traditional methods like screen scraping or using CICS Transaction Gateway. It acted as middleware, sitting between the mainframe CICS environment and web-based applications.

WebTek was middleware. It provided a bridge between mainframe-based CICS applications and modern web environments, allowing organizations to expose CICS functionality through web interfaces without requiring extensive changes to the underlying CICS applications.

Organizations with significant investments in CICS applications that wanted to provide web access to those applications were the target audience. These were often larger enterprises in industries like banking, insurance, and government. Companies needing to integrate mainframe data and processes with web-based systems would have considered WebTek.

WebTek would have been considered when an organization needed to provide web access to existing CICS applications without undertaking a complete rewrite or using screen scraping techniques. It offered a potential solution for integrating mainframe systems with web-based applications, but given its 'Not Supported' status, modern alternatives should be explored.

Alternatives to WebTek include CICS Transaction Gateway (CICS TG), which provides a standard interface for accessing CICS applications, and various application modernization platforms that offer broader capabilities for transforming legacy applications. Other options involve API enablement tools that expose CICS functionality as RESTful services.

WebTek required a z/OS mainframe environment with CICS. It would typically run within an LPAR (Logical Partition) on the mainframe. The product likely had specific dependencies on CICS system services and potentially other mainframe software components.

WebTek likely involved a server component running on z/OS that communicated with CICS regions. Web requests would be routed to this server, which would then interact with CICS transactions. The specific communication protocols and data formats would be defined in WebTek's configuration.

Without access to specific documentation, it is difficult to provide exact command syntax. However, typical operations would have included defining CICS transactions to be exposed, configuring web interfaces, and managing user access. Configuration files would likely have been used to define these settings.

WebTek likely exposed APIs to allow web applications to interact with CICS transactions. These APIs might have been based on protocols like HTTP or TCP/IP. The specific API endpoints and data formats would have been defined by WebTek's implementation.

The business value of WebTek was in enabling organizations to leverage their existing CICS applications in a modern web environment. This could extend the life of legacy systems, reduce development costs compared to rewriting applications, and improve user access to mainframe data.

Without WebTek (or a similar product), organizations would have needed to rely on older access methods like 3270 terminals or invest in more complex and costly application modernization projects. Screen scraping was another alternative, but it is generally less reliable and maintainable.

WebTek aimed to provide a more structured and maintainable approach to web-enabling CICS applications compared to screen scraping. It offered a potential alternative to CICS Transaction Gateway, but it is important to evaluate modern solutions given WebTek's 'Not Supported' status.

Security in WebTek would have involved controlling access to CICS transactions and data through web interfaces. This likely included authentication of users and authorization to specific functions. The product may have integrated with mainframe security systems like RACF, ACF2, or Top Secret.

WebTek's access control model likely involved defining roles or groups and assigning them permissions to access specific CICS transactions or data. This could have been implemented using a role-based access control (RBAC) model.

Encryption could have been used to protect data transmitted between the web server and the mainframe. This might have involved using SSL/TLS for web communication and potentially encryption of sensitive data within the CICS environment.

Ongoing operations for WebTek would have included monitoring the health and performance of the server components, managing user access, and troubleshooting any issues with CICS transactions. Mainframe systems programmers would likely be involved in supporting the product.

Implementation challenges could have included configuring WebTek to work with specific CICS applications, ensuring compatibility with existing security systems, and optimizing performance for web users. Expertise in both mainframe and web technologies would have been required.

Monitoring capabilities likely included logging web requests, tracking CICS transaction performance, and providing alerts for any errors or performance issues. These logs could be integrated with mainframe monitoring tools or SIEM systems.