I am trying to find out the bridge status using the below wlst script. But failed to execute it.
Please help me.
servers = domainRuntimeService.getServerRuntimes();
if (len(servers) > 0):
for server in servers:
messagingBridgeRuntime = server.getMessagingBridgeRuntime;
messageBridges = messageBrigdeRuntime.getMessageBridges();
for messageBridge in messageBridges:
destinations = messageBridges.getDestinations();
for destination in destinations:
print ' BridgeName ' , destination.getName()
print ' State ' , destination.getState()
Thanks for your response. As you said the state of a bridge instance is on the bridge runtime not the destination. I agreed with that and change the script as follows.
rt = cmo.getMessagingBridgeRuntime();
When i execute the above script got the error message as
Connecting to t3://localhost:7001 with userid system ...
Successfully connected to Admin Server 'router_server' that belongs to domain 'r
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Location changed to serverRuntime tree. This is a read-only tree with ServerRunt
imeMBean as the root.
For more help, use help(serverRuntime)
Problem invoking WLST - Traceback (innermost last):
File "D:\scripts\abc.py", line 8, in ?
Still i am unable to get the bridge status. please let me know is there any problem with the script.
Edited by: Siva Praasd Reddy G on Jul 17, 2012 8:27 PM
Edited by: Siva Praasd Reddy G on Jul 17, 2012 8:36 PM
I am able to view the state of a messaging bridge using online WLST.
connect() -> serverRuntime()->cd('MessagingBridgeRuntime')->cd(Bridge-instance-name)->ls().
But I am also having problem doing the same via WLST script yet. It seems to me that the runtime mbean tree hierarchy is incorrect for messaging bridges, and as a result, it is not easy (if possible at all) to access messaging bridge runtime mbean instances from serverRuntime. You may have to file a service request to get this fixed.
The "state" of a bridge instance is on the runtime mbean not the config mbean.
I am able to access a messaging bridge instance (and its state) using WLST. Here is the output.
-r-- Description Stopped by the administrator.
-r-- Name Bridge-0
-r-- State Inactive
-r-- Type MessagingBridgeRuntime
-r-x preDeregister Void :
-r-x start Void :
-r-x stop Void :
But I am using a recent WebLogic release (10.3.5). You may want to contact Oracle Support to get a patch for this on 9.2.3 if you are not able to upgrade to 10.3.5 or later release.