XML Query for IDMS Modernization Guide
XML Query for IDMS is a legacy application/data access product by ObjEx. Explore technical details, modernization strategies, and migration paths below.
Product Overview
XML Query for IDMS is middleware designed to provide service-oriented architecture (SOA) access to CA IDMS databases.
The product exposes APIs that allow .NET and Java applications to send XML queries to the XML Query for IDMS server.
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 XML Query for IDMS do?
XML Query for IDMS provides service-oriented architecture (SOA) access to CA IDMS databases. It enables .NET and Java applications to interact with and retrieve data from IDMS systems.
Is this a system, application, or tool?
XML Query for IDMS is middleware that bridges the gap between modern application architectures and legacy CA IDMS databases. It provides a layer of abstraction, allowing applications to access IDMS data without needing to understand the complexities of the underlying database.
What types of organizations use this?
Organizations that rely on CA IDMS as a core database and need to integrate it with newer .NET or Java-based applications benefit from XML Query for IDMS. These organizations are often in industries like banking, finance, insurance, and government.
When should we consider XML Query for IDMS?
A company should consider using XML Query for IDMS when it needs to expose CA IDMS data as services for use by .NET or Java applications. This is especially relevant when modernizing applications or building new applications that need to interact with existing IDMS data.
What are the alternatives to XML Query for IDMS?
Alternatives include other middleware products that provide access to CA IDMS, such as those offering similar SOA capabilities or direct database connectivity. Some organizations might also consider migrating data from IDMS to a more modern database, although this is a more complex and costly undertaking.
Technical
What infrastructure is required?
XML Query for IDMS requires a z/OS environment where CA IDMS is running. It also needs a network connection to the systems hosting the .NET or Java applications that will be accessing the IDMS data.
For mainframe products: Does this run in an LPAR?
XML Query for IDMS typically runs in an LPAR within the z/OS environment. It is dependent on z/OS and requires the CA IDMS subsystem to be active and accessible.
How does XML Query for IDMS expose IDMS data?
XML Query for IDMS exposes APIs that allow .NET and Java applications to query and retrieve data from CA IDMS. These APIs typically use protocols like SOAP or REST to communicate over the network.
What is the syntax for basic operations?
The exact syntax for operations depends on the specific API being used. However, a typical operation involves sending an XML query to the XML Query for IDMS server, which then translates the query into an IDMS database request and returns the results in XML format.
Business Value
What is the business value of XML Query for IDMS?
XML Query for IDMS allows organizations to leverage their existing CA IDMS data in modern applications, extending the life and value of their legacy systems. This avoids costly and risky data migration projects.
How does this product integrate with enterprise ecosystems?
By providing a service-oriented interface to CA IDMS, XML Query for IDMS enables organizations to integrate IDMS data into enterprise ecosystems, allowing for better data sharing and application integration.
What would happen if an organization did not use this product?
Without XML Query for IDMS, organizations would need to develop custom solutions to access CA IDMS data from .NET or Java applications, which can be complex, time-consuming, and expensive. Alternatively, they might be forced to migrate data to a different database.
Security
What authentication methods are supported?
XML Query for IDMS supports various authentication methods to control access to IDMS data. Specific methods include standard z/OS security mechanisms and potentially integration with external authentication providers.
What access control model is used?
The access control model used by XML Query for IDMS typically involves defining roles and permissions that determine which users or applications can access specific IDMS data. This may be based on Role-Based Access Control (RBAC).
What encryption is used and where?
Encryption is used to protect data in transit between the .NET or Java applications and the XML Query for IDMS server. This typically involves using SSL/TLS to encrypt the communication channel.
What audit/logging capabilities exist?
XML Query for IDMS provides audit logging capabilities to track access to IDMS data and any modifications made. These logs can be used for security monitoring and compliance purposes.
Operations
What are common implementation challenges?
Implementing XML Query for IDMS requires expertise in CA IDMS, z/OS, and the .NET or Java environments that will be accessing the data. Common challenges include configuring the network connectivity, setting up security, and optimizing query performance.
What ongoing operational requirements exist?
Ongoing operational requirements include monitoring the performance of the XML Query for IDMS server, ensuring the availability of the CA IDMS database, and managing user access and security.
How is this product typically deployed?
XML Query for IDMS is typically deployed on-premise, within the organization's z/OS environment. This allows for direct access to the CA IDMS database and ensures data security and compliance.
Ready to Start Your Migration?
Download our comprehensive migration guide for XML Query for IDMS or calculate your ROI.