z/Web-Host Modernization Guide

z/Web-Host provided web-based access to mainframe applications by translating 3270 terminal screens into web pages. It acted as middleware, allowing users to interact with legacy systems through a standard web browser. Without it, organizations would need to rely on traditional terminal emulators or invest in more complex application modernization projects.

z/Web-Host was middleware that sat between the mainframe and the user's web browser. It did not replace the underlying mainframe applications but provided a more user-friendly interface. It was suitable for organizations needing a quick and relatively inexpensive way to provide web access to existing 3270 applications.

Organizations with existing mainframe applications and a need to provide web-based access to those applications used z/Web-Host. These were often larger enterprises in industries like banking, insurance, and government. Companies needing to modernize their mainframe applications without extensive code changes found it useful.

Companies considered z/Web-Host when they needed to provide web access to existing 3270 applications quickly and with minimal changes to the underlying mainframe systems. It was a good fit when a full-scale application rewrite was not feasible or cost-effective. However, it was not suitable for organizations seeking a more modern, feature-rich user experience.

Alternatives to z/Web-Host include other screen scraping tools, terminal emulators with web integration capabilities, and full application modernization platforms. Examples include Virtel Web Modernization, IPBridge/Host, and z/Ware. These alternatives offer varying levels of functionality and integration with modern web technologies.

z/Web-Host required a mainframe environment running z/OS or zVSE/VSEn. It needed access to the 3270 data streams generated by the mainframe applications. On the web server side, it required a Java runtime environment to host the web application components. Network connectivity between the mainframe and the web server was also essential.

z/Web-Host typically ran on a dedicated LPAR (Logical Partition) on the mainframe. It intercepted 3270 data streams from mainframe applications and transformed them into HTML for display in a web browser. It did not directly depend on specific z/OS subsystems but required network access to the web server.

The core component was the screen scraper, which intercepted and translated 3270 data streams. A Java-based web server component handled the presentation of the web interface. Configuration files defined the mapping between 3270 screens and web pages. These components communicated via TCP/IP.

z/Web-Host exposed APIs for customizing the web interface and integrating with other systems. These APIs typically used HTTP and could be accessed using standard web development tools and languages. Specific API endpoint patterns would depend on the version and configuration of z/Web-Host.

z/Web-Host provided a cost-effective way to extend the life of existing mainframe applications by providing web access. It allowed organizations to avoid the expense and risk of a full-scale application rewrite. The business value came from improved user accessibility and reduced training costs.

Without z/Web-Host, organizations would need to rely on traditional terminal emulators, which can be difficult to use and maintain. Alternatively, they could invest in a full application modernization project, which can be expensive and time-consuming. z/Web-Host offered a middle ground.

The licensing model for z/Web-Host was typically perpetual, with ongoing maintenance fees. The total cost of ownership included the initial license fee, maintenance fees, and the cost of hardware and software required to run the product. Vendor lock-in was a consideration, as migrating to a different solution could require significant effort.

z/Web-Host integrated with enterprise ecosystems by providing web access to mainframe applications. This allowed users to access mainframe data and functionality through standard web browsers, which could be integrated with other web-based applications and services. It also supported integration with security systems for authentication and authorization.

z/Web-Host supported various authentication methods, including integration with existing mainframe security systems like RACF, ACF2, and Top Secret. It also supported web-based authentication methods like LDAP. The access control model was typically based on user roles and permissions defined within the mainframe security system.

z/Web-Host controlled access to mainframe applications and data by integrating with the mainframe security system. It enforced access controls based on user roles and permissions defined within the mainframe security system. This ensured that only authorized users could access sensitive data and functionality.

z/Web-Host used encryption to protect sensitive data transmitted between the mainframe and the web browser. It supported SSL/TLS encryption for web traffic. It also provided audit logging capabilities to track user access and activity. These logs could be used to monitor security and compliance.

z/Web-Host required ongoing monitoring to ensure that it was functioning correctly and that the web interface was available to users. It also required regular maintenance to apply security patches and bug fixes. Staffing requirements included mainframe system administrators and web developers.

Common implementation challenges included configuring the network connectivity between the mainframe and the web server, mapping 3270 screens to web pages, and integrating with existing security systems. Performance tuning was also important to ensure that the web interface was responsive.

Administrative interfaces included a command-line interface (CLI) and a web-based console. The CLI was used for configuring the product and managing users. The web-based console provided a graphical interface for monitoring the system and viewing logs. User management was handled through the CLI or the mainframe security system.