ObjEx for z/OS Modernization Guide

ObjEx for z/OS connects CA IDMS databases to external applications using Websphere MQ. It provides interfaces to capture and publish database changes and to access IDMS data via MQ messaging. This allows for integration of legacy IDMS systems with modern, distributed applications.

ObjEx for z/OS is middleware. It facilitates communication between CA IDMS databases and external applications through Websphere MQ. It provides inbound and outbound interfaces to enable this integration.

Organizations that rely on CA IDMS for critical business data and need to integrate this data with other applications can benefit from ObjEx for z/OS. This includes enterprises in industries such as banking, finance, insurance, and government.

Consider ObjEx for z/OS when you need to expose CA IDMS data to external applications, participate in service-oriented architectures (SOA), or modernize legacy systems without extensive code changes. It is useful when real-time data replication or event-driven architectures are required.

Alternatives to ObjEx for z/OS include custom-built integration solutions, other middleware products that support CA IDMS integration, and data replication tools. Examples include IBM Integration Bus (IIB) and Informatica PowerCenter, although these may require more extensive configuration and development.

ObjEx for z/OS requires a z/OS environment, a running CA IDMS database, and a Websphere MQ infrastructure. The components are deployed within the z/OS LPAR and interact with IDMS and MQ subsystems.

ObjEx for z/OS runs on the z/OS platform. It is dependent on z/OS and requires specific subsystems such as CA IDMS and Websphere MQ to be present and configured.

The Outbound Interface captures database changes using IDMS logging or change data capture (CDC) mechanisms. It then publishes these changes as MQ messages. The Inbound Interface receives MQ messages and translates them into IDMS database operations.

ObjEx for z/OS uses configuration files to define the mapping between IDMS data structures and MQ message formats. These files specify the queues, topics, and data transformations required for integration.

ObjEx for z/OS enables integration of legacy CA IDMS systems with modern applications, allowing organizations to leverage existing data assets in new ways. This can improve business agility, reduce development costs, and extend the life of critical mainframe applications.

By integrating CA IDMS with Websphere MQ, ObjEx for z/OS allows organizations to participate in service-oriented architectures (SOA) and event-driven architectures. This enables real-time data sharing and improved responsiveness to business events.

ObjEx for z/OS can reduce the cost and complexity of integrating CA IDMS with other systems. It provides a standardized interface for accessing IDMS data, eliminating the need for custom-built integration solutions.

ObjEx for z/OS leverages the security features of both CA IDMS and Websphere MQ. Access to IDMS data is controlled through IDMS security mechanisms, while MQ message security is managed through MQ security policies. It supports authentication methods such as RACF and ACF2.

ObjEx for z/OS supports encryption of MQ messages to protect sensitive data in transit. This ensures that data is not exposed during transmission between systems.

ObjEx for z/OS provides audit logging capabilities to track access to IDMS data and MQ message activity. This allows organizations to monitor and audit data access for compliance purposes.

ObjEx for z/OS is typically deployed on-premise within the z/OS environment. It requires technical expertise in CA IDMS, Websphere MQ, and z/OS to implement and maintain.

Ongoing operational requirements include monitoring the health of the ObjEx for z/OS components, managing MQ queues and topics, and maintaining the configuration files. Staffing requirements include personnel with expertise in CA IDMS, Websphere MQ, and z/OS.

Common implementation challenges include configuring the mapping between IDMS data structures and MQ message formats, ensuring proper security settings, and troubleshooting connectivity issues between IDMS and MQ.