Name: Shadow AutoHTML for CICS/TS
Availability: InStock

Question 1

What is Shadow AutoHTML for CICS/TS?

Accepted Answer

Shadow AutoHTML for CICS/TS automatically converts 3270 screens to HTML, enabling web access to CICS applications. It leverages the Shadow Data Mapping Facility (DMF) to map data fields. The product was originally released by Neon Systems and later integrated into the Shadow z/Enterprise Web Server.

Question 2

What is the core functionality of Shadow AutoHTML for CICS/TS?

Accepted Answer

The primary function is to transform 3270 screen data into HTML format for web browsers. This involves intercepting 3270 data streams, mapping the data using DMF, and generating HTML output. The product integrates with the Shadow z/Enterprise Web Server for deployment.

Question 3

What are the key components and dependencies of Shadow AutoHTML for CICS/TS?

Accepted Answer

Shadow AutoHTML for CICS/TS was designed to work with the Shadow z/Enterprise Web Server. The DMF is used for data mapping. Configuration typically involves defining mappings between 3270 screen fields and HTML elements. The product was originally released by Neon Systems.

Question 4

What are the primary use cases for Shadow AutoHTML for CICS/TS?

Accepted Answer

The product's main use case is to provide web-based access to existing CICS applications without requiring code changes to the CICS programs. This allows organizations to modernize their application access without rewriting their core business logic.

Question 5

What APIs does Shadow AutoHTML for CICS/TS expose?

Accepted Answer

The product exposes no direct APIs. It relies on intercepting and transforming 3270 data streams. The Shadow z/Enterprise Web Server handles the web interface and communication. Data mapping is managed through the DMF.

Question 6

What are the main architectural components of Shadow AutoHTML for CICS/TS?

Accepted Answer

The architecture includes the 3270 data stream interceptor, the DMF for data mapping, and the Shadow z/Enterprise Web Server for web presentation. Communication occurs between these components to convert 3270 data to HTML.

Question 7

How is Shadow AutoHTML for CICS/TS configured and administered?

Accepted Answer

Configuration is primarily managed through the DMF, where mappings between 3270 fields and HTML elements are defined. There is no CLI or GUI for direct configuration of AutoHTML itself. The Shadow z/Enterprise Web Server provides administrative interfaces.

Question 8

What are the network and system requirements for Shadow AutoHTML for CICS/TS?

Accepted Answer

The product relies on the Shadow z/Enterprise Web Server for web serving capabilities. The DMF is used for data mapping. The specific ports and network requirements are determined by the z/Enterprise Web Server configuration.

Question 9

What is the business value of using Shadow AutoHTML for CICS/TS?

Accepted Answer

Shadow AutoHTML for CICS/TS enables organizations to extend the life of their CICS applications by providing web access without requiring extensive code changes. This reduces the cost and risk associated with application modernization.

Question 10

How does Shadow AutoHTML for CICS/TS help with application modernization?

Accepted Answer

By providing web access to existing CICS applications, Shadow AutoHTML for CICS/TS helps organizations avoid the need to rewrite or re-architect their core business systems. This accelerates the modernization process.

Question 11

How does Shadow AutoHTML for CICS/TS impact the return on investment (ROI) of CICS applications?

Accepted Answer

The product allows organizations to leverage their existing investment in CICS applications by extending their reach to web users. This helps to maximize the return on investment in these legacy systems.

Question 12

How does Shadow AutoHTML for CICS/TS improve user productivity?

Accepted Answer

By providing a web interface, Shadow AutoHTML for CICS/TS improves user productivity by enabling access to CICS applications from any web browser. This enhances the user experience and streamlines workflows.

Question 13

What security features are provided by Shadow AutoHTML for CICS/TS?

Accepted Answer

Shadow AutoHTML for CICS/TS relies on the security features of the Shadow z/Enterprise Web Server. This includes authentication and access control mechanisms configured within the web server. The DMF does not provide security features.

Question 14

What authentication methods are supported?

Accepted Answer

The product does not directly handle authentication. Authentication is managed by the Shadow z/Enterprise Web Server. Supported methods depend on the web server configuration.

Question 15

What access control model is used?

Accepted Answer

Access control is managed through the Shadow z/Enterprise Web Server. The specific access control model (e.g., role-based access control) depends on the web server configuration. The DMF does not provide access control.

Question 16

What encryption is used?

Accepted Answer

The product does not provide encryption. Encryption is handled by the Shadow z/Enterprise Web Server, which may use HTTPS for secure communication. The DMF does not provide encryption.

Question 17

What are the key operational tasks for Shadow AutoHTML for CICS/TS?

Accepted Answer

The primary operational tasks involve monitoring the Shadow z/Enterprise Web Server, which hosts the HTML-converted CICS applications. Monitoring tools for the web server can be used to track performance and availability.

Question 18

What logging capabilities are available?

Accepted Answer

Logging is handled by the Shadow z/Enterprise Web Server. Administrators can review the web server logs to troubleshoot issues and monitor application activity. The DMF does not provide logging capabilities.

Question 19

How is performance monitored?

Accepted Answer

Performance monitoring is primarily focused on the Shadow z/Enterprise Web Server. Administrators should monitor the web server's resource usage (CPU, memory, etc.) to ensure optimal performance. The DMF does not provide performance monitoring.

Question 20

What are the backup and recovery procedures?

Accepted Answer

Backup and recovery procedures are managed through the Shadow z/Enterprise Web Server. The specific procedures depend on the web server configuration and the underlying z/OS environment. The DMF does not require separate backup and recovery.

Are You a Vendor? Claim Your Listing

Shadow AutoHTML for CICS/TS

Product Overview

Frequently Asked Questions

What is Shadow AutoHTML for CICS/TS?

What is the core functionality of Shadow AutoHTML for CICS/TS?

What are the key components and dependencies of Shadow AutoHTML for CICS/TS?

What are the primary use cases for Shadow AutoHTML for CICS/TS?

What APIs does Shadow AutoHTML for CICS/TS expose?

What are the main architectural components of Shadow AutoHTML for CICS/TS?

How is Shadow AutoHTML for CICS/TS configured and administered?

What are the network and system requirements for Shadow AutoHTML for CICS/TS?

What is the business value of using Shadow AutoHTML for CICS/TS?

How does Shadow AutoHTML for CICS/TS help with application modernization?

How does Shadow AutoHTML for CICS/TS impact the return on investment (ROI) of CICS applications?

How does Shadow AutoHTML for CICS/TS improve user productivity?

What security features are provided by Shadow AutoHTML for CICS/TS?

What authentication methods are supported?

What access control model is used?

What encryption is used?

What are the key operational tasks for Shadow AutoHTML for CICS/TS?

What logging capabilities are available?

How is performance monitored?

What are the backup and recovery procedures?

Related Products

More from Progress Software

Shadow AutoHTML for IMS/TM

Shadow z/SQL

Similar Products

3270 SUPEROPTIMIZER/CICS

Access Manager for CICS

ACCOLADE

ACI Host Link

Adabas SQL Gateway

ADS for CICS

Help Improve This Directory

Share Your Product Experience