In this step,
activate support for the optimized local adapters with the WebSphere environment variables
in the WebSphere Application Server daemon
group or cell. This prepares the WebSphere Application Server to receive inbound
requests.
Subtopics:
Enabling the server environment to use optimized local adapters
You must enable the application server to receive inbound
and outbound requests using the optimized local adapters support.
Optimized Local Adapters for z/OS is
a set of callable services (APIs) that give native z/OS applications the ability to make inbound
calls to application server enterprise beans, and enable native programs
to act as a server and accept requests from applications running in
the WebSphere Applications
Server.
Optimized local adapters deployment in development mode
Optimized local adapters can be used in development
mode, which enables application developers to test their optimized
local adapters enabled applications using a copy of WebSphere Application Server running on
an operating system other than z/OS.
Configuring optimized local adapters in development mode on the remote z/OS node
The optimized local adapters for z/OS proxy enterprise archive (EAR) file must
be installed on the remote z/OS node
to enable the local node to communicate with it. The EAR file has
a single resource reference, named eis/ola, which
must be resolved to an optimized local adapters connection factory
installed on the remote z/OS node.
Configuring optimized local adapters in development mode on the local node
The optimized local adapters for z/OS resource archive (RAR) file must be installed
on the local node. When running on a non-z/OS platform, the optimized
local adapters RAR file communicates with an instance of the optimized
local adapters proxy enterprise archive (EAR) file on a remote z/OS node using Remote Method Invocation
over Internet Inter-ORB Protocol (RMI-IIOP).
WebSphere Optimized Local Adapter (WOLA) remote work request on an Enterprise Java Bean target
This feature allows a client application such as batch, CICS, etc. to contact a remote WebSphere Application Server
server instance hosting an application whose business logic execution
and results are required by the client. The remote invocation is done
by leveraging the BBOA1INV/BBGA1INV and BBOA1SRQ/BBGA1SRQ APIs and
a proxy application (RemoteEJBProxy), which is shipped with WebSphere Application Server
for z/OS.
Starting an application server
When you start an application server, a new server process
starts. This new server process is based on the process definition
settings of the current server configuration.
Directory conventions
References in product information to app_server_root, profile_root,
and other directories imply specific default directory locations.
Become familiar with the conventions in use for WebSphere Application
Server.
Enabling the server environment to use optimized local adapters
You must enable the application server to receive inbound
and outbound requests using the optimized local adapters support.
Optimized Local Adapters for z/OS is
a set of callable services (APIs) that give native z/OS applications the ability to make inbound
calls to application server enterprise beans, and enable native programs
to act as a server and accept requests from applications running in
the WebSphere Applications
Server.
Optimized local adapters deployment in development mode
Optimized local adapters can be used in development
mode, which enables application developers to test their optimized
local adapters enabled applications using a copy of WebSphere Application Server running on
an operating system other than z/OS.
Configuring optimized local adapters in development mode on the remote z/OS node
The optimized local adapters for z/OS proxy enterprise archive (EAR) file must
be installed on the remote z/OS node
to enable the local node to communicate with it. The EAR file has
a single resource reference, named eis/ola, which
must be resolved to an optimized local adapters connection factory
installed on the remote z/OS node.
Configuring optimized local adapters in development mode on the local node
The optimized local adapters for z/OS resource archive (RAR) file must be installed
on the local node. When running on a non-z/OS platform, the optimized
local adapters RAR file communicates with an instance of the optimized
local adapters proxy enterprise archive (EAR) file on a remote z/OS node using Remote Method Invocation
over Internet Inter-ORB Protocol (RMI-IIOP).
WebSphere Optimized Local Adapter (WOLA) remote work request on an Enterprise Java Bean target
This feature allows a client application such as batch, CICS, etc. to contact a remote WebSphere Application Server
server instance hosting an application whose business logic execution
and results are required by the client. The remote invocation is done
by leveraging the BBOA1INV/BBGA1INV and BBOA1SRQ/BBGA1SRQ APIs and
a proxy application (RemoteEJBProxy), which is shipped with WebSphere Application Server
for z/OS.
Starting an application server
When you start an application server, a new server process
starts. This new server process is based on the process definition
settings of the current server configuration.
Directory conventions
References in product information to app_server_root, profile_root,
and other directories imply specific default directory locations.
Become familiar with the conventions in use for WebSphere Application
Server.