Prepare an existing application.
Enable the server environment.
Parent
Use optimized local adapters for outbound support
A resource adapter archive (RAR) file, ola.rar, is provided for applications to use the Java Connector Architecture (JCA) 1.5 programming model for connecting to and calling native language external server programs. Read the topic, Using the optimized local adapter to call an application in an external address space from a WebSphere application for more information about how to accomplish this.
If we are calling from a Cobol or C/C++ program, you might want to use the IBM Rational Application Developer assembly tools, such as Rational Application Developer, to create a Java class with getter and setter helper methods that correspond to the Cobol copybook or C/C++ structure. These methods help convert binary form to Java objects. The Java 2 Connector (J2C) tools in Rational Application Developer can be used to accomplish this conversion. Read about assembly tools for more information about tooling support for WebSphere Application Server applications.
Subtopics
- (zos) Use optimized local adapters to connect to an application in an external address space from a WebSphere application
Use this task when to use the outbound APIs to connect to an application in an external address space from an application that is deployed on WebSphere Application Server for z/OS.
- (zos) Use the outbound APIs with the external address space or subsystem
Use this task to create an interaction between the outbound APIs and the external address space or subsystem.
- Assemble applications
Application assembly consists of creating Java EE modules that can be deployed onto application servers. The modules are created from code artifacts such as WAR files, resource adapter archive (RAR) files, enterprise bean (EJB) JAR files, and application client archive (JAR) files. This packaging and configuring of code artifacts into EAR modules or stand-alone web modules is necessary for deploying the modules onto an application server.
What to do next
(Optional) Use the CICS environment.
Subtopics
- (zos) Use optimized local adapters to connect to an application in an external address space from a WebSphere application
Use this task when to use the outbound APIs to connect to an application in an external address space from an application that is deployed on WebSphere Application Server for z/OS.
- (zos) Use the outbound APIs with the external address space or subsystem
Use this task to create an interaction between the outbound APIs and the external address space or subsystem.
- Assemble applications
Application assembly consists of creating Java EE modules that can be deployed onto application servers. The modules are created from code artifacts such as WAR files, resource adapter archive (RAR) files, enterprise bean (EJB) JAR files, and application client archive (JAR) files. This packaging and configuring of code artifacts into EAR modules or stand-alone web modules is necessary for deploying the modules onto an application server.
Related tasks
Use optimized local adapters to connect to an application in an external address space from a WebSphere application Use the outbound APIs with the external address space or subsystem Assembling applications