z/Web-Server Modernization Guide

z/Web-Server is a web server designed for z/VM and z/VSE operating systems. It enables the creation and deployment of web applications directly on these mainframe environments, supporting CGI programming using Assembler or REXX with CMS pipelines.

z/Web-Server is primarily a system and a tool set. It provides the core web server functionality and includes tools to aid in the development and deployment of CGI applications.

Organizations that rely on z/VM or z/VSE for their core business applications and want to provide web-based access to these applications would benefit from z/Web-Server. This includes enterprises in sectors like finance, insurance, and government that utilize mainframe systems.

A company should consider using z/Web-Server when they need to expose existing z/VM or z/VSE applications to web users, or when they want to develop new web applications that leverage the capabilities of these mainframe environments. It is particularly useful when integration with existing CMS pipelines is required.

Alternatives to z/Web-Server include other web servers that might be ported to or compatible with z/VM and z/VSE, or developing custom solutions using Java or other languages. However, these alternatives may not offer the same level of integration with CMS pipelines or the same ease of development for CGI programs in Assembler or REXX.

z/Web-Server requires a running instance of z/VM or z/VSE. It leverages the existing CMS pipelines for CGI program execution. A Java SDK may be needed for certain functionalities or extensions.

z/Web-Server runs within an LPAR on the mainframe. It is not directly z/OS dependent but integrates with z/VM and z/VSE subsystems.

z/Web-Server extends the capabilities of z/VM and z/VSE by providing web server functionality. It relies on these operating systems for its core services.

The main components include the web server core, CGI processing modules, and potentially a Java runtime environment if Java-based extensions are used. These components communicate through standard operating system interfaces and network protocols.

z/Web-Server likely uses standard ports such as 80 for HTTP and 443 for HTTPS. Specific network requirements depend on the configuration and the applications being served.

z/Web-Server allows organizations to provide web-based access to mainframe applications, improving user experience and accessibility. It enables integration with modern web technologies while leveraging the reliability and security of the mainframe.

Without z/Web-Server, organizations would need to find alternative ways to provide web access to their z/VM and z/VSE applications, potentially involving more complex and less integrated solutions. This could lead to increased development costs and reduced efficiency.

z/Web-Server can integrate with enterprise ecosystems by providing web services that can be consumed by other applications. It can also integrate with security systems for authentication and authorization.

z/Web-Server likely supports standard authentication methods such as basic authentication, as well as integration with mainframe security systems like RACF or ACF2. Specific methods depend on the configuration.

The access control model likely integrates with the mainframe's security system, potentially using Role-Based Access Control (RBAC) to manage user permissions.

Encryption, such as TLS/SSL, is used to secure communication between the web server and clients. Data at rest on the mainframe is protected by the mainframe's security features.

z/Web-Server likely provides audit logging capabilities to track user access and system events. These logs can be integrated with security information and event management (SIEM) systems.

z/Web-Server is typically deployed on-premise, within the organization's mainframe environment. It requires technical expertise in z/VM or z/VSE systems administration and web server configuration.

Ongoing operational requirements include monitoring server performance, managing security updates, and maintaining the web applications. Staffing requires personnel with mainframe and web server expertise.

Common implementation challenges include configuring the web server to integrate with existing mainframe security systems, ensuring compatibility with existing applications, and optimizing performance.

Administrative interfaces likely include a command-line interface (CLI) and potentially a web-based console for configuration and monitoring. User management is typically handled through the mainframe's security system.