Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
WASOPSCTF.somecorp.com=
(description=
(load_balance=on)
(failover=on)
(address=
(protocol=tcp)
(host=idops1)
(port=1521))
(address=
(protocol=tcp)
(host=idops2)
(port=1521))
(connect_data=
(service_name=WASOPSCTF.somecorp.com))))
NONE
WASOPSTAF.somecorp.com=
(description=
(load_balance=on)
(failover=on)
(address=
(protocol=tcp)
(host=opshp1)
(port=1521)
(address=
(protocol=tcp)
(host=opshp2)
(port=1521)
(connect_data=
(service_name=WASOPSTAF.somecorp.com)
(failover_mode=
(type=session)
(method=preconnect)
(retries=0)
(delay=10))))
WASOPSTAF.somecorp.com=
(description=
(address=
(protocol=tcp)
(host=opshp1)
(port=1521))
(connect_data=
(service_name=WASOPSTAF.somecorp.com)
(failover_mode=
(backup=opshp2)
(type=session)
(method=preconnect)
(retries=0)
(delay=10))))
Install the Oracle client in the hosts where you plan to install
WebSphere. Install WebSphere® as described in the manual, using
the OCI driver to connect the WASs to the databases created. Since
we use the global net service name, which is independent of
individual nodes, the failover is transparent to WebSphere. For CTF,
WebSphere® receives a few StaleConnectionExceptions during an
OPS/RAC failover, and WebSphere® handles these exceptions
automatically. WebSphere® usually works automatically after an
OPS/RAC/TAF failover.
In summary, although OPS/RAC uses non-IP failover, it still needs
platform-specific cluster software to provide cluster management
and inter-process communication. OPS/RAC failover takes a very
short time. It is almost instantaneous failover, because non-IP
takeover is used and no restarting of the database instance is
needed. WebSphere® establishes connections immediately after a
failover, and clients observe very few failures.