Planning to use optimized local adapters on Liberty for z/OS
Plan how to implement WebSphere optimized local adapters (WOLA) in your Liberty server environment.
Before you begin
For CICS® Transaction Server for z/OS® to communicate with optimized local adapters, the minimum required
version of CICS Transaction Server for z/OS is version
4.1.
About this task
If you have applications that are written in native languages, such as Cobol, PL/I, C/C++,
and high-level assembly languages, that run under z/OS batch,
Customer Information Control System (CICS), or UNIX System
Services environments, you can use optimized local adapters to directly call between the
native-language application and Java-based business logic on a Liberty server. You can use optimized local
adapters to make the following calls:
Inbound calls from an external address space to Enterprise JavaBeans (EJB) applications that are deployed on a local Liberty server
Outbound calls from an application that is running under the Liberty server on z/OS to a server program that is running in an external address space
If you have a large number of native-language applications that you want to use on Liberty, implementing optimized local adapters
provides the following benefits:
Performance improvement
Identity context propagation
Local binding support
Gateway or proxy for legacy assets on z/OS systems
Procedure
Review the existing business and middleware applications in your environment to determine
which application processes would benefit from using optimized local adapters.
Choose
processes that you can remove and replace with calls to the optimized local adapter native API
callable services.
If you plan to propagate a System Authorization Facility (SAF) user ID from Liberty for z/OS to the enterprise information system (EIS), verify that the Liberty server is using a SAF-based user
registry.