For optimized local adapters to make an outbound call to
your local daemon group or an inbound call to a WebSphere® Application Server cell, you must
bind the current address space to the WebSphere Application Server daemon group
and establish connection attributes.
Before you begin
The
WebSphere Application Server
daemon group must be active on the same z/OS
® image
that the register request originates from. If you are using the Customer
Information Control System (CICS
®),
the task-related user exit (TRUE) program must be activated before
a connection is made between CICS and
WebSphere Application Server.
If
you are using the Information Management System (IMS), the optimized local adapter external subsystem
interface must be installed and activated before applications begin
calling the optimized local adapter APIs.
Procedure
- Define the parameters to use in the connection. When
you are using CICS, the reg_flag_trans
flag is set to 1 to indicate that the connections created
under this register name are to be attached to RRS and joined with
the work done in a WebSphere Application Server
global transaction. Setting this flag to 0 (zero) indicates
that there are not connections created under this register name that
are to be attached to RRS and joined with the work done in a WebSphere Application Server
global transaction.
For inbound calls, a security context is always
propagated to WebSphere Application Server
and it contains the user ID of the address space making the request.
For CICS, the reg_flag_C2Wprop
flag propagates the user ID that the CICS task
is currently using, rather than the user ID from the address space.
For
outbound calls, the reg_flag_W2Cprop flag tells WebSphere Application Server to propagate
the user ID to CICS. CICS then attempts to start the
target program with that user ID.
To read more about using
security, see the topics, Securing optimized local adapters for inbound
support and Securing optimized local adapters for outbound support.
- Verify that the register name is not already used in another
cell that this address space is connected to. An address
space verification is done to ensure that the register name is not
already in use by another cell. If the register name is used by another
cell, an error return code is passed back and the register request
fails.
- Set up the client address space native language application
to call the BBOA1REG API. The daemon group and server
name are passed, and an input string that represents the name, or
register name that is used by the WebSphere Application Server daemon.
A
0 (zero) return and reason code indicates that the client address
space is now bound to the WebSphere Application Server
daemon group and server that you selected. Future calls that interact
with this WebSphere Application Server must
either have the supplied register name or a specific connection handle
that was created using that register name accompanying them.
Results
After completing this task, the passed register name string
is reserved in the current address space. No other register calls
can be made with this token until an unregister call is received for
it.
Important: If you use the minimum connections setting
on this call, the result is a pool of connections that are pre-established
with the target server and waiting for requests.
Also, a registration
entry context or control block is created and associated with the
register name string. Each unique register name has a register context.
Multiple register names with the same address space and thread can
bind with one or more
WebSphere Application Server
daemon groups.
What to do next
To read more about the BBOA1REG API, see the topic Optimized
local adapters for z/OS native
APIs.