Databases Reference
In-Depth Information
How it works...
One message bridge per queue member must be created when using a distributed destination
like the
JMSAppQueue
queue to guarantee every message from every member is forwarded.
The target destination,
BridgeTarget
, uses a remote connection factory,
jms.
remoteappcf
, to connect to the remote queue. Since the remote queue
jms.remotequeue
is also distributed, disable the server affinity option of the remote connection factory
jms.
remoteappcf
so the messages are load-balanced to all members of the distributed queue
jms.remotequeue
.
Depending on the number of bridges created in the WebLogic domain, you should tune the
max connections settings of the resource adapter. The recommendation is to set the max
connections value as 2 times the number of bridges. If you have 20 bridges, change the max
connections to at least 40.
If the resource adapter deployment plan is changed, copy the updated
file to every machine of the cluster. In this case, copy the
/oracle/
Middleware/user_projects/domains/PROD_DOMAIN/plans/
jms-notran-adp-Plan.xml
file to every machine in the same path.
Using a shared folder to host the file is also a valid option.
There's more...
The message bridge can be configured using WLST.
Configuring the message bridge using WLST:
This change can be made using WLST.
1. Log in as a
wls
user to the shell and start WLST.
[wls@prod01]$ $WL_HOME/common/bin/wlst.sh
2. Connect to the Administration Server using
wlsadmin
as user,
<pwd>
as the
password, and
t3://adminhost.domain.local:7001
as the server URL:
wls:/offline>connect("wlsadmin","<pwd>","t3://adminhost.domain.
local:7001")
3. Run the following WLST commands to create the bridge sources:
edit()
startEdit()
cd('/')
cmo.createJMSBridgeDestination('BridgeSource_01')
Search WWH ::
Custom Search