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.
Before you begin
For more information about optimized local adapters in development
mode, read the Optimized local adapters deployment in development
mode topic.
About this task
The optimized local adapters proxy EAR file can be found
in the
installableApps directory of the WebSphere
® Application Server
for z/OS installation. The
name of the EAR file is
ola_proxy.ear. The EAR
file can be installed using the administrative console or wsadmin
scripting. An example install command using jython is shown below:
AdminApp.install('/WebSphere/ND/AppServer/installableApps/ola_proxy.ear',
'[ -nopreCompileJSPs -distributeApp -nouseMetaDataFromBinary
-nodeployejb -appname ola_proxy -createMBeansForResources
-noreloadEnabled -nodeployws -validateinstall warn
-noprocessEmbeddedConfig -filepermission
.*\.dll=755#.*\.so=755#.*\.a=755#.*\.sl=755
-noallowDispatchRemoteInclude -noallowServiceRemoteInclude
-asyncRequestDispatchType DISABLED -nouseAutoLink
-noenableClientModule -clientMode isolated -MapResRefToEJB [[
OLAProxyEJB.jar ProxyEJB OLAProxyEJB.jar,META-INF/ejb-jar.xml
eis/ola javax.resource.cci.ConnectionFactory eis/ola "" "" "" ]]
-MapModulesToServers [[ OLAProxyEJB.jar
OLAProxyEJB.jar,META-INF/ejb-jar.xml
WebSphere:cell=PLEX1Network,node=PLEX1Node,server=server1 ]]]' )
Procedure
- The optimized local adapters connection factory on the
remote z/OS node is configured
in the same way that a normal optimized local adapters connection
factory would be configured. Each of the properties on
the optimized local adapters connection factory can be overridden
by the caller if the caller specified a value on the local node.
For example, if the optimized local adapters connection factory on
the remote z/OS node was configured
to use the OTMAServerName 'IMS1', but the OLA connection factory on
the local node specified OTMAServerName 'IMS2', the local node's specification
would be used.
- Security settings on the remote z/OS node can have an impact on which actions
the local node is allowed to perform on the remote node. The
user on the local node can specify a user ID and password to allow
work on the remote node to run using that identity. Currently, this
is only useful for running work in CICS® using
the optimized local adapters link server, where the user is logged
into CICS and the target transaction
is started using that user ID. Additionally, since the local node
uses Remote Method Invocation over Internet Inter-ORB Protocol (RMI-IIOP)
to communicate with the optimized local adapters proxy EJB, transport
security settings can be used to prevent unauthorized users from using
optimized local adapters in development mode.