 |
 |
 |
|
 |
|
 |
|
 |
|
 |
|
 |
DataDirect Shadow z/Services For Screens
Shadow z/Services provides rapid transformation of mainframe screen-based processes into SOAP-based Web services. z/Service's unique Dynamic Introspection technology goes beyond the limitations of terminal emulation methods by exposing screen data as field names rather than as row/column coordinates. Dynamic Introspection provides a simple programming model which improves developer productivity, reduces application maintenance, and increases application reliability.
Broad Range of Support for Screen Environments
Supported screen-based applications include:
- CICS/TS
- IMS/TM
- IDMS
- ADS/O
Simplified Web Services Process
Shadow z/Services automatically exposes mainframe applications as ready-to-use Web services. A simple five-step process serves to publish any application as a Web service:
- Create a virtual directory (where you want the WS to be hosted)
- Create a target system (i.e. CICS, IDMS, Natural)
- Log onto the application/run the application
- Select screens for input and output
- Add alternate navigation for multiple screens
Unique Dynamic Introspection Technology Interacts Directly with Screen Metadata
Shadow z/Services uses an exclusive technology called Dynamic Introspection to locate the metadata associated with screen fields. This metadata-based approach allows Shadow to directly access the screen-based information based on the field names. Because Shadow z/Services interacts directly with the metadata, changes to screen layout and field size no longer require adjustments to the Web service code. This improves the reliability of the Web services.
Interaction with the created Web service is orchestrated by administrator-defined microflows, which are the logical aggregation of multiple screens. Microflows execute within Shadow on the mainframe, which improves performance by reducing 3270 traffic over the network, and allows the administrator to control the flow of the application based on the content of a particular field. Shadow z/Services also supports environments where there is no metadata for field names.
Key Features
Shadow z/Services' capabilities for screen-based applications complement other Shadow features that expose mainframe data and programmatic resources as Web services in support of mainframe SOA implementations. Key features include:
- Non-invasive development approach protects proven legacy screen logic
- Flexible choice in development environments supporting both the Eclipse framework and .NET
- Automated generation of web services from mainframe data sources
- Automated generation of starter programs, simplifying the testing of newly created services
- Microflows execute on the mainframe to improve performance through the elimination of network traffic
- Access to fields by name reduces maintenance when screen layout or field size changes occur on the mainframe
- Bi-directional web services support on mainframe, (publishing as well as allowing the mainframe to consume external web services)
- Exploits IBM's Unicode hardware assists - dramatically reduces the resource consumption required to support web services on the mainframe
- Full support for SOAP over HTTP and SOAP over MQ as transport options
Supports Transformation of CICS Screens
- Directly accesses the metadata from the application to publish screen information based on field names (BMS screen data in z/Services for CICS/TS); if there is no metadata available, field names are dynamically generated
- Access to screen names provides complete state information to the web services administrator, which improves reliability (BMS Maps in z/Services for CICS/TS)
- For CICS/TS Screen-Based Applications, Shadow supports the newest CICS technologies, including Channels and Containers, URIMAP, and FEPI/Linkable Bridge
- z/Services for CICS/TS deployment in the CICS option enables organizations to reuse their existing CICS infrastructure including CWS–CICS Web Support and CICS Web Services
Supports Tranformation of IDMS Screens
z/Services for IDMS and ADS/O Screen-Based Applications integrates directly into IDMS and ADS/O applications through the IDD (IDMS Dictionary) to access the metadata from the application.
z/Services has received the CA-Smart Certification for its capability to transform IDMS screens into industry standard web services.
Flexible Web Services Deployment Options
Shadow z/Services provides multiple options for deploying mainframe Web services in order to meet your unique infrastructure requirements. Runtime options for screen logic include:
- Shadow – A robust, multi-threaded, native runtime server that deploys within a started task on the mainframe. Shadow provides a real-time foundation architecture for standards-based mainframe integration in support of Web services/SOA, Real-time events, SQL and Web enablement.
- Distributed - A Windows-based, mid-tier solution requiring no installation of software on the mainframe, offering tn3270 or tn5250 API screen access
- CICS Region - A runtime server that deploys within a CICS region on the mainframe and offers four high-performance options for direct access to mainframe screen and business logic:
- COMMAREA
- OTMA
- 3270 Bridge/Linkable Bridge
- FEPI
Security Optimization Management
Shadow z/Services for screen-based applications leverages one of Shadow's advanced features for optimizing security and performance associated with mainframe Web services deployments. Shadow's Security Optimization and Management (SOM) increases the viability of mainframe Web services by reducing the overhead of authenticating loosely-coupled connections.
Intelligently Interface Your Screen-Based Applications with an SOA Environment
Shadow z/Services lets you leverage your investment in screen-based applications by providing flexible, intelligent interaction between screen-based applications and Web services - in support of SOA deployments or simply to increase the re-use of mainframe applications. The product's Dynamic Introspection technology simplifies development, improves reliability, and virtually eliminates much of the maintenance associated with older terminal emulation methods.
| More Information | |||||||||||||||||||
|
