ServEx Modernization Guide
ServEx is a legacy application/data access product by XPS Software. Explore technical details, modernization strategies, and migration paths below.
Product Overview
ServEx is a development and runtime system designed to create SOAP-based Java applications that connect to mainframe resources.
Consider using ServEx when you need to expose mainframe resources as web services or integrate mainframe data with Java applications.
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 ServEx do?
ServEx is a development and runtime system that enables the creation of SOAP-based Java applications that can connect to mainframe resources. It provides connectors for accessing IMS, CICS, CA Ideal screens, CICS temporary storage, VSAM datasets, and DB2 databases.
Is this a system, application, or tool?
ServEx is a middleware solution that provides connectivity between Java/web applications and mainframe systems. It offers a framework for building SOAP-based services that expose mainframe resources.
What types of organizations use this?
Organizations that rely on mainframe systems for core business functions and want to integrate these systems with modern Java and web applications can benefit from ServEx. This includes enterprises in industries such as banking, finance, insurance, and government.
When should we consider ServEx?
A company should consider ServEx when it needs to expose mainframe resources as web services, integrate mainframe data with Java applications, or modernize its mainframe applications without completely rewriting them. It is useful for organizations seeking to leverage existing mainframe investments while adopting modern technologies.
What are the alternatives to ServEx?
Alternatives to ServEx include z/OS Connect, OpenLegacy, and Ivory Service Architect. These products also provide connectivity between mainframe systems and modern platforms, but they may differ in terms of supported protocols, development approaches, and integration capabilities.
Technical
What infrastructure is required?
ServEx requires a mainframe environment running z/OS or zVSE/VSEn. It also requires a Java runtime environment for deploying and running the generated SOAP-based applications. Specific subsystems like CICS or IMS may be needed depending on the resources being accessed.
For mainframe products: Does this run in an LPAR?
ServEx typically runs in an LPAR (Logical Partition) on the mainframe. It is dependent on the z/OS or zVSE/VSEn operating system and may require specific subsystems like CICS or IMS to be active.
What types of APIs does ServEx expose?
ServEx exposes SOAP-based APIs for accessing mainframe resources. These APIs can be consumed by Java applications or other web service clients. The specific API endpoint patterns and method names depend on the configuration and the resources being accessed.
What mainframe resources can ServEx access?
ServEx supports integration with various mainframe resources, including IMS, CICS, CA Ideal screens, CICS temporary storage, VSAM datasets, and DB2 databases. It uses connectors to access these resources and expose them as SOAP-based services.
What are the main system components of ServEx?
The main system components of ServEx include the development environment, the runtime engine, and the connectors for accessing specific mainframe resources. These components communicate through internal APIs and protocols to process requests and return data.
Business Value
How does ServEx provide business value?
ServEx enables organizations to leverage their existing mainframe investments by exposing mainframe resources as web services. This allows them to integrate mainframe data and functionality with modern applications, extending the life of their mainframe systems and reducing the need for costly replacements.
How does ServEx reduce costs?
By using ServEx, organizations can avoid the cost and complexity of completely rewriting their mainframe applications. Instead, they can expose existing functionality as web services, allowing them to modernize their systems incrementally and at a lower cost.
How does ServEx integrate with enterprise ecosystems?
ServEx helps organizations integrate their mainframe systems with enterprise ecosystems by providing a standardized way to access mainframe resources. This allows them to connect mainframe data with other applications and systems, improving data sharing and collaboration.
What happens if an organization does not use ServEx?
Without ServEx, organizations may face challenges in integrating their mainframe systems with modern applications. They may need to rely on older technologies or develop custom solutions, which can be costly and time-consuming. ServEx provides a more efficient and standardized way to achieve this integration.
Security
What authentication methods are supported by ServEx?
ServEx supports various authentication methods for securing access to mainframe resources. Specific methods include basic authentication, LDAP authentication, and integration with security systems like RACF or ACF2.
What access control model is used by ServEx?
ServEx uses an access control model based on roles and permissions. This allows administrators to define roles with specific privileges and assign users to those roles, controlling their access to mainframe resources.
What encryption is used by ServEx?
ServEx uses encryption to protect sensitive data transmitted between the Java/web applications and the mainframe system. The specific encryption algorithms used may vary depending on the configuration and the communication protocols.
What audit/logging capabilities exist in ServEx?
ServEx provides audit and logging capabilities to track user activity and system events. This information can be used for security monitoring, compliance reporting, and troubleshooting.
Operations
What ongoing operational requirements exist for ServEx?
ServEx requires ongoing monitoring to ensure the availability and performance of the integration between Java/web applications and mainframe systems. This includes monitoring the runtime engine, connectors, and underlying mainframe resources.
What are common implementation challenges with ServEx?
Implementing ServEx may involve challenges such as configuring the connectors to access specific mainframe resources, ensuring compatibility between the Java/web applications and the mainframe system, and managing security and access control.
What administrative interfaces are available for ServEx?
ServEx provides administrative interfaces for managing users, configuring connectors, and monitoring system performance. These interfaces may include a command-line interface (CLI), a graphical user interface (GUI), or a web console.
How is user management handled in ServEx?
User management in ServEx involves creating user accounts, assigning roles, and defining access permissions. This can be done through the administrative interfaces or by integrating with existing user directories such as LDAP.
Ready to Start Your Migration?
Download our comprehensive migration guide for ServEx or calculate your ROI.