What are the most common commands and their syntax?

Common commands include starting and stopping services, configuring connections, and managing security settings. The exact syntax varies depending on the specific operation and the chosen interface (CLI or GUI).

What types of APIs does Shadow z/Services for CICS expose?

The product exposes REST APIs for integration. These APIs use standard HTTP methods (GET, POST, PUT, DELETE) and JSON for data exchange. Specific endpoint patterns and method names depend on the CICS application being accessed.

What programming languages and protocols are supported for integration?

Supported programming languages and SDKs include Java and .NET. These SDKs provide libraries and tools to simplify the integration process. Communication protocols include HTTP and TCP/IP.

What are the main system components?

The main components are the z/Services Gateway, the CICS Connector, and the Windows Client. The z/Services Gateway handles incoming requests, the CICS Connector interacts with CICS, and the Windows Client provides the interface for Windows applications.

How does Shadow z/Services for CICS provide business value?

Shadow z/Services for CICS enables organizations to modernize their mainframe applications by integrating them with modern platforms. This integration can extend the lifespan of mainframe applications while leveraging new technologies.

How does Shadow z/Services for CICS facilitate application development?

By enabling integration between CICS and distributed systems, Shadow z/Services for CICS allows businesses to create new applications that leverage existing mainframe assets. This can reduce development costs and time to market.

How does Shadow z/Services for CICS improve operational efficiency?

The product allows organizations to extend the reach of their CICS applications to new users and systems. This can improve customer service and operational efficiency.

How does Shadow z/Services for CICS improve business agility?

By integrating CICS applications with modern platforms, Shadow z/Services for CICS can help organizations improve their agility and responsiveness to changing business needs.

What authentication methods are supported?

Shadow z/Services for CICS supports authentication via LDAP, SAML 2.0, and X.509 certificates. These methods ensure secure access to CICS applications.

What access control model is used?

The product uses an RBAC (Role-Based Access Control) model. This allows administrators to define roles and assign permissions to users based on their roles, ensuring that users only have access to the resources they need.

What encryption is used and where?

Encryption is used to protect sensitive data during transit. This includes encrypting data exchanged between the z/Services Gateway and the CICS Connector, as well as between the Gateway and the Windows Client.

What audit/logging capabilities exist?

Audit logging is available to track user activities and system events. These logs can be used to monitor system behavior and identify potential security threats. The logs record user actions, system events, and security-related incidents.

What administrative interfaces are available?

Administrative interfaces include a CLI (Command Line Interface) and a GUI (Graphical User Interface). The CLI allows for scripting and automation, while the GUI provides a visual interface for configuration and monitoring.

How is user management handled?

User management is handled through the administrative interfaces. Administrators can create, modify, and delete user accounts, as well as assign roles and permissions. Integration with external identity providers is also supported.

What are the main configuration parameters?

Main configuration parameters include connection settings, security configurations, and logging levels. These parameters can be adjusted through the administrative interfaces to customize the product's behavior.

What monitoring/logging capabilities exist?

Monitoring and logging capabilities include real-time monitoring of system performance and detailed logging of events. These features help administrators troubleshoot issues and ensure the system is running smoothly.

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

Shadow z/Services for CICS

Name: Shadow z/Services for CICS
Availability: InStock

Rocket Software Supported z/OS

UNIX and Windows Legacy Application/Data Access CICS

Vendor

Rocket Software

Product Overview

The architecture of Shadow z/Services for CICS is designed for robust and secure integration between CICS applications and distributed systems. The core components include the z/Services Gateway, the CICS Connector, and the Windows Client. The z/Services Gateway acts as the central point of contact, receiving requests from client applications and routing them to the appropriate CICS applications.

It supports REST APIs, enabling communication via HTTP and JSON. The CICS Connector resides on the z/OS platform and interacts directly with the CICS environment. It translates requests from the Gateway into CICS transactions and returns the results.

The Windows Client provides the interface for Windows-based applications, allowing them to access CICS resources. Communication between components is secured using encryption. 509 certificates, with RBAC for access control.

The system utilizes TCP/IP for network communication. The Gateway and Connector can be configured for high availability and scalability. Detailed logging and monitoring capabilities are available to ensure optimal performance and security.

Frequently Asked Questions

What is Shadow z/Services for CICS?

Shadow z/Services for CICS enables Windows Java and .NET applications to access CICS applications, and vice versa. It facilitates integration between distributed environments and mainframe CICS applications, allowing for the modernization of applications and data access.

What is the history of Shadow z/Services for CICS?

The product was created by merging Tanit Objects and Tanit Services, along with technology from ClientBuilder. It was acquired by Rocket Software from Progress Software.

What are the primary use cases for Shadow z/Services for CICS?

It allows access to CICS applications from Windows Java and .NET applications and enables CICS applications to access resources on Windows platforms. This bidirectional capability is a key feature.

What data formats and protocols does Shadow z/Services for CICS support?

Shadow z/Services for CICS supports various data formats and protocols, including those used by CICS and distributed systems. It provides a bridge for data exchange between different platforms.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now