Databases Reference
In-Depth Information
3.
In
the
Persistence
Stores
table,
click
on
the
UMSJMSFileStore_auto_<n>
persistence
store
that
targets
to
WLS_BAM1
.
4.
In the
Configuration
tab, enter the following URL in the
Directory
field:
ORACLE_BASE/admin/<domain_name>/<cluster_name>/jms
5.
Click on
Save and Activate
.
6.
Repeat the
steps 3
to
5
for
UMSJMSFileStore_auto_<n>
that targets to
WLS_BAM2
.
Configuring a persistence store for transaction recovery
The WebLogic Server uses transaction logs for recovery from system crashes
or network failures. To enable the Managed Servers within a WebLogic Server
cluster to recover JTA transactions, the
transaction
log must be stored in a
shared storage. Preferably, this location should be a dual-ported SCSI disk or on
a
Storage Area Network (SAN).
To configure a persistence store for transaction recovery, complete the following
steps:
1.
Log in to the WebLogic Server Administration Console.
2.
In the
Domain Structure
pane, navigate to
Environment | Servers
.
3.
Click on
WLS_BAM1
in the
Name
column of the table.
4.
In the
Configuration
tab, click on the
Services
tab.
5.
In the
Default Store
section of the page, enter the following path in the
Directory
field:
ORACLE_BASE/admin/<domain_name>/
<soa_cluster_name>/tlogs
6.
Click on
Save
.
7.
Repeat
steps 3
to
6
for
WLS_BAM2
.
Untargeting BAM Server components from WLS_BAM2
In the current release, BAM server components, such as ADC, Report Cache,
EMS, and so on, do not support active-active deployment in an HA environment.
Therefore, you must untarget these components from one of the Managed Serv-
