Set WebSphere environment
variables to allow WebSphere Application Server to use optimized local adapters. The variables
are described in the topic, Optimized local adapters environment variables.
This is done once per stand-alone application server or WebSphere Application Server, Network Deployment cell.
Set the cell-wide variable WAS_DAEMON_ONLY_enable_adapter
to true to allow the cell's daemon(s) to process inbound
and outbound optimized local adapter calls. This variable must be
set in order to use the optimized local adapters.
Use the
cell-wide variables WAS_DAEMON_ONLY_adapter_max_conn, WAS_DAEMON_ONLY_adapter_max_serv,
and WAS_DAEMON_ONLY_adapter_max_shrmem to set the maximum number
of connections, maximum number of outbound services, and maximum amount
of shared memory allocated to optimized local adapter sessions by
the daemon.
Use the
ola_cicsuser_identity_propagate variable
to control propagation of security identities during registration.
This variable, which can be set at the cell or node level, must be
set to
1 to allow the optimized local adapters samples to
run.
Important: Read the information on the ola_cicsuser_identity_propagate
variable in the topic, Optimized local adapters environment variables,
to understand the security implications of setting this variable on
your server.
You can use the administrative console
or scripting to set these variables. The olaRar.py script
that is described in the next step sets the WAS_DAEMON_ONLY_enable_adapter
variable to true, but does not alter any other WebSphere Application Server environment
variables.
Install the resource adapter archive, ola.rar file,
and create a connection factory. For each application server
node that utilizes the optimized local adapters, you must also install
the resource adapter archive, ola.rar, and create a connection factory.
The olaInstall.sh script creates a symbolic link to this
archive file from each application server node's WAS_HOME/installableApps
directory. You can use either the administrative console or the olaRar.py script
to install the resource adapter and create the connection factory.
To use the olaRar.py script to install the resource adapter
and connection factory, see the topic, olaRar.py
script file. To use the administrative console to install the
resource adapter, read the topic Install the resource adapter archive
(RAR). You can create the connection factory in the administrative
console on the Resource Adapters panel. Click the name of your newly
created resource adapter and under Additional Properties, click J2C
connection factories > New. When creating the new connection
factory, the key field that needs to be completed is the JNDI name.
This
script also sets the cell-wide WAS_DAEMON_ONLY_enable_adapter variable
to true, but does not configure any other WebSphere environment variables for the
optimized local adapters. Make sure that you install the resource
adapter archive and create a connection factory on each application
server node that will handle incoming or outgoing optimized local
adapter connections.
For more information about connection factories,
see the topic Connection factory considerations for optimized local
adapters.