SOLA Modernization Guide

SOLA enables access to CICS and IMS applications as web services. It also allows CICS and batch applications to access external web services. SOLA uses analyzers to create WSDLs from COMMAREAs and 3270 screens, and it can import existing WSDLs to generate COBOL and PL/I copybooks.

SOLA supports HTTP and WebSphere MQ for transport. It uses WSDLs to define the service interfaces and COBOL or PL/I copybooks for data structures.

The COMMAREA Analyzer creates WSDLs from COMMAREAs. The 3270 Analyzer creates WSDLs from screen-scraping. The Outbound Analyzer imports existing WSDLs and converts them to COBOL and PL/I copybooks.

SOLA includes testing facilities for newly created web services. It also provides monitoring capabilities for HTTP and WebSphere MQ transports.

SOLA exposes SOAP-based web services. Specific API endpoint patterns depend on the configuration and the underlying CICS or IMS applications.

SOLA supports integration with COBOL and PL/I. The Outbound Analyzer generates COBOL and PL/I copybooks from WSDLs.

SOLA uses configuration files to define the mapping between web services and CICS or IMS transactions. These files specify the COMMAREA structure, screen layouts, and transport details.

SOLA uses HTTP and WebSphere MQ for communication. The choice depends on the configuration and the requirements of the target environment.

SOLA enables organizations to expose legacy CICS and IMS applications as web services, allowing them to be integrated with modern applications and platforms. This can extend the life and value of existing systems.

By exposing legacy applications as web services, SOLA allows organizations to reuse existing functionality and data in new applications, reducing development costs and time to market.

SOLA provides monitoring capabilities for HTTP and WebSphere MQ transports, allowing organizations to track the performance and availability of web services.

SOLA leverages the security features of the underlying CICS, IMS, and WebSphere MQ environments. Specific authentication methods depend on the configuration of these systems.

SOLA relies on the access control mechanisms of CICS and IMS. These systems typically use role-based access control (RBAC) to manage user permissions.

Encryption is typically handled by the underlying transport protocols (HTTPS, MQ security). SOLA itself does not provide specific encryption mechanisms.

SOLA integrates with the audit and logging capabilities of CICS, IMS, and WebSphere MQ. Audit trails can be used to track access to web services and data.

SOLA provides monitoring facilities for HTTP and WebSphere MQ transports. These facilities allow administrators to track the performance and availability of web services.

SOLA integrates with the logging capabilities of CICS, IMS, and WebSphere MQ. Logs can be used to troubleshoot issues and track system activity.

SOLA uses configuration files to define the mapping between web services and CICS or IMS transactions. These files can be managed using a text editor or a dedicated configuration tool.