zVWS Modernization Guide
zVWS is a java and web product by Velocity Software. Explore technical details, modernization strategies, and migration paths below.
Product Overview
zVWS is an HTTP server designed specifically for the z/VM operating system.
It is a good fit for organizations that rely on z/VM for their mainframe infrastructure and need to serve web content.
Modernization Strategies
Rehost
- Timeline:
- 6-12 months
Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.
Refactor (Recommended)
- Timeline:
- 18-24 months
Optimize application architecture for cloud while preserving business logic. Best ROI long-term.
Replatform
- Timeline:
- 3-5 years
Complete rewrite to cloud-native architecture with microservices and modern tech stack.
Frequently Asked Questions
General
What does zVWS do?
zVWS is an HTTP server designed for the z/VM operating system. It allows you to serve static HTML content and execute CGI scripts, enabling web-based applications on the mainframe.
Is this a system, application, or tool?
zVWS is a system that provides web server capabilities on z/VM. It is not merely an application, but a foundational component for serving web content.
What types of organizations use this?
Organizations that rely on z/VM for their mainframe infrastructure and need to serve web content or run web applications would use zVWS. This includes businesses in finance, insurance, and government.
When should we consider zVWS?
Consider using zVWS when you need to provide web access to applications or data residing on your z/VM system. It is particularly useful when migrating from older web serving solutions like VM:Webgateway.
What are the alternatives to zVWS?
Alternatives to zVWS include other web servers that can run on z/VM or solutions that involve offloading web serving to other platforms. z/Web-Server is another option.
Technical
What infrastructure is required?
zVWS requires a z/VM environment. It operates within the z/VM LPAR and does not have dependencies on z/OS. It needs TCP/IP connectivity to serve web requests.
For mainframe products: Does this run in an LPAR?
zVWS runs on the z/VM operating system. It is not dependent on z/OS or specific subsystems beyond the base z/VM environment and TCP/IP stack.
How does zVWS handle dynamic content?
zVWS supports serving static HTML content directly. For dynamic content, it uses the CGI (Common Gateway Interface) standard to execute external programs and scripts.
Does zVWS provide migration tools?
zVWS includes tools to assist in migrating configurations and applications from VM:Webgateway, simplifying the transition to the new server.
Business Value
What is the business value of zVWS?
zVWS allows organizations to modernize their z/VM applications by providing a modern web interface. This can improve user experience and enable integration with other web-based systems.
How does zVWS improve performance?
By providing a web server directly on z/VM, zVWS can reduce the need to transfer data to other platforms for web serving, potentially improving performance and security.
How can zVWS extend existing applications?
zVWS can be used to create web-based interfaces for existing mainframe applications, extending their functionality and making them accessible to a wider range of users.
Security
What authentication methods are supported?
zVWS supports standard authentication methods. Specific methods are configured within the server's configuration files.
How does zVWS control access to resources?
zVWS provides access control mechanisms to restrict access to specific web resources. The access control model is likely based on ACLs (Access Control Lists) defined in the server configuration.
What encryption is used and where?
zVWS uses encryption to protect sensitive data transmitted over the network. The specific encryption protocols used depend on the configuration, but TLS/SSL is commonly supported.
What audit/logging capabilities exist?
zVWS provides logging capabilities to track web server activity. These logs can be used for auditing and security analysis.
Operations
How is zVWS typically deployed?
zVWS is typically deployed on-premise within a z/VM environment. It requires configuration and ongoing maintenance by system administrators familiar with z/VM and web server technologies.
What level of technical expertise is required to implement it?
Implementing zVWS requires technical expertise in z/VM, TCP/IP networking, and web server configuration. Familiarity with CGI scripting is also beneficial.
What ongoing operational requirements exist?
Ongoing operational requirements include monitoring server performance, reviewing logs for security issues, and applying updates and patches as needed.
Ready to Start Your Migration?
Download our comprehensive migration guide for zVWS or calculate your ROI.