VirtualSource Modernization Guide
VirtualSource is a help, documentation and training product by ADPAC Corporation. Explore technical details, modernization strategies, and migration paths below.
Product Overview
VirtualSource is an application designed to automate the creation and delivery of online documentation for mainframe applications.
This helps development and operations teams understand application functionality, data structures, and processing logic more efficiently.
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 VirtualSource do?
VirtualSource automates the creation and delivery of online documentation for mainframe applications. It helps users understand application functionality, data structures, and processing logic without needing to consult paper-based manuals or source code directly.
Is this a system, application, or tool?
VirtualSource is an application and toolset designed to improve understanding and maintainability of mainframe applications. It is not a system in itself, but rather a tool that works with existing systems.
What types of organizations use this?
Organizations that rely heavily on mainframe applications, particularly those with complex systems and a need for improved documentation, benefit most from VirtualSource. This includes companies in industries like banking, insurance, and government.
When should we consider VirtualSource?
A company should consider VirtualSource when they face challenges in maintaining and understanding their mainframe applications, when documentation is outdated or incomplete, or when they need to improve knowledge transfer among staff.
What are the alternatives to VirtualSource?
Alternatives to VirtualSource include manual documentation efforts, code analysis tools, and other documentation generators. However, VirtualSource is specifically designed for mainframe environments and offers automated features not always found in generic tools.
Technical
For mainframe products: Does this run in an LPAR?
VirtualSource runs on the z/OS platform and operates within an LPAR. It is dependent on the z/OS operating system and may require specific subsystems to be active.
What configuration files are used?
VirtualSource likely uses configuration files to define how it extracts and formats documentation. These files specify data sources, formatting rules, and output options.
Does VirtualSource have an API?
VirtualSource may integrate with other mainframe tools and systems through APIs or data exchange mechanisms. Specific API details would depend on the product's capabilities and available interfaces.
What are the main system components?
The specific components of VirtualSource would include modules for data extraction, documentation generation, and online presentation. These components communicate to process application metadata and create the final documentation.
Business Value
What is the business value of VirtualSource?
VirtualSource provides business value by reducing the time and effort required to document mainframe applications. This leads to improved understanding, faster problem resolution, and reduced maintenance costs.
What happens if we do not use VirtualSource?
Without VirtualSource, organizations may struggle with outdated or incomplete documentation, leading to increased support costs, longer development cycles, and higher risk of errors.
How does VirtualSource help with onboarding new team members?
VirtualSource helps integrate new team members by providing them with readily available and up-to-date documentation of mainframe applications. This reduces the learning curve and allows them to become productive faster.
Security
How does VirtualSource handle security?
VirtualSource likely uses z/OS security mechanisms, such as RACF, ACF2, or Top Secret, to control access to documentation and administrative functions. Specific authentication methods would depend on the z/OS configuration.
What access control model is used?
The access control model used by VirtualSource is likely Role-Based Access Control (RBAC), where users are assigned roles with specific permissions to access documentation and perform administrative tasks.
What encryption is used?
VirtualSource may encrypt sensitive data, such as passwords or configuration information, both in transit and at rest. The specific encryption algorithms used would depend on the product's security features.
Operations
How is VirtualSource typically deployed?
VirtualSource is typically deployed on-premise within the mainframe environment. This involves installing the software on z/OS and configuring it to access application metadata.
What level of technical expertise is required?
Implementing VirtualSource requires technical expertise in z/OS, mainframe applications, and documentation practices. Ongoing operational requirements include monitoring the system, maintaining configuration files, and updating documentation as applications change.
What are common implementation challenges?
Common implementation challenges include identifying and accessing relevant application metadata, configuring the system to extract and format documentation correctly, and ensuring that the documentation remains up-to-date.
What administrative interfaces are available?
Administrative interfaces for VirtualSource likely include a command-line interface (CLI) and potentially a web-based console. These interfaces are used to configure the system, manage users, and monitor its operation.
Ready to Start Your Migration?
Download our comprehensive migration guide for VirtualSource or calculate your ROI.