Configuration of DB2 for z/OS servers for client reroute
If Sysplex routing is disabled on a DB2 for z/OS server, and a data sharing group
is set up for member-specific access, you can use IBM Data Server Driver for JDBC
and SQLJ client reroute support.
If Sysplex routing is enabled for a DB2 data sharing group, work is distributed
among all members of a data sharing group by the DB2 for z/OS server and
Workload Manager for z/OS (WLM). If one of the members of a DB2 data sharing
group fails, work is automatically transferred to other members. In this case, IBM
Data Server Driver for JDBC and SQLJ client reroute support is not needed.
Setting up member-specific access includes setting up a location alias that
represents one or more members of the data sharing group. Before a JDBC or SQLJ
client application can use the client reroute facility, a location alias needs to exist
that represents at least two members of the data sharing group. The client
application connects to those members using the location alias, instead of using the
location name to connect to the entire group. If one member fails, connections are
attempted to other members of the data sharing group, based on their priority
(WLM server weight information).
IBM Data Server Driver for JDBC and SQLJ client reroute support works only for
member-specific access. It does not work for group access. Therefore, only a
member dynamic virtual IP address (DVIPA) should be defined. A group DVIPA
should not be defined.
To set up the data sharing group so that JDBC and SQLJ client applications can
take advantage of client reroute support, the database administrator needs to
perform these steps:
1. Specify the DRDA port number on which all members listen for incoming SQL
requests.
2. Specify a unique resynchronization port number for each member.
3. Designate subsets of members to which DRDA requesters can connect.
4. Specify a generic LU name for the data sharing group, if RACF PassTickets are
used.
See the topic ″Configuring data sharing groups as TCP/IP servers″ for details.
Enabling IBM Data Server Driver for JDBC and SQLJ client
reroute for connections to DB2 servers
To enable client reroute for IBM Data Server Driver for JDBC and SQLJ
applications that connect to DB2 Database for Linux, UNIX, and Windows or DB2
for z/OS servers, you need to set properties to indicate to the driver which servers
are the primary and alternate servers.
Before you can enable IBM Data Server Driver for JDBC and SQLJ client reroute
for connections to DB2 Database for Linux, UNIX, and Windows or DB2 for z/OS,
your installation must have a primary server and an alternate server.
After the primary and alternate servers are set up, follow these steps:
1. Set the appropriate properties to specify the primary and alternate server
addresses.
v If your application is using the DriverManager interface for connections:
Chapter 3. JDBC application programming 85
|
|
|
|
|
|
|
|
|
|
|
|
|
To Next Page
Loading...
Need help?
General