How to browse message in TIBCO EMS?
There was API available which can help in browsing data on EMS destinations but there was out of box tools also available in market which provide easy way to browse messages/data on EMS destinations. One of widely used tools that I personally use is GEMS. You can download the tool .Its open source
Connect to the desired EMS instance with credentials ..You can check credentials in users.conf file
Click on Queues on left hand side of the GEMS tools.
Right Click on the queue/topic which you want to browse. You should get option to browse. There is browse option in main menu option also. Note that for topic, you will get Monitor Topic option, for queue it will be Browse Queue
After clicking on browse queue, you will get below window. By default it will list down only 10 messages, by checking on ‘No limit’ option, you can get all the messages sitting on the queue.
Browse Result
You can double click on any message to see it content.
Message Compression , JMS_TIBCO_COMPRESS property- usage
Message compression is especially useful when messages will be stored on the server (persistent queue messages, or topics with durable subscribers). Setting compression ensures that messages will take less memory space in storage. When messages will not be stored, compression is not as useful. Another advantage of using the compression is when you have to transmit the messages on slower networks like WAN.
The compression option only compresses the body of a message. Headers and properties are never compressed. It is best to use compression when the message bodies will be large and the messages will be stored on a server. JMS_TIBCO_COMPRESS Allows messages to be compressed for more efficient storage.
To use the JMS_TIBCO_COMPRESS property,
1)create a “JMS Application Properties” object, where you add a boolean property “JMS_TIBCO_COMPRESS”.
2)In the Reply task, in the “Advanced” page, in the “JMS Application Properties” field, select the “JMS Properties” object you created.
3) Now, in the “Input” of the task, you can see the field “OtherProperties/JMS_TIBCO_COMPRESS”.
4)Put “true” in its value.
We can do BW performance tuning by setting these properties as per our hosts capacity.
- Max jobs
- Flow limit
- Activation Limit
- Java heap size
We can do EMS performance tuning at server and admin tool level as below.
performance tuning at Server level: This can be done using prefetch mechanism,thereby regulating the consumption of messages. The prefetch mechanism is avialable in both queues and topics.
performance tuning at Admin level: In Administrator, It’s done by adjusting the count of the threads, by setting the flowControl, maxbytes, maxmsgs etc.
In Adapters we can do by using polling and aleter
Suspending, resuming an EMS route
We have 2 ems servers – one within the firewall & one outside – connected by a route
Here is the command to suspend and resume
Suspend will suspend messages sending on routes. PFA
We have 2 ems servers – one within the firewall & one outside – connected by a route
Here is the command to suspend and resume
Suspend will suspend messages sending on routes. PFA
Example:
suspend route routername
TIBCO RV/RVRD Http Interface
We can check RVS status and each tibco rvd is running expose on HTTP interface , with this we can get many useful information about RVD /RVRD.
E.g:-
- General information(version,host name,store file,process id, ip add..)
- client details
- services has been subscribed by rvd
- XML Configuration- it gives subject a particular service is using and what are those etc.
- Current Log
- Which services has been subscribed by rvd
to check on which Http port your rvd is publishing information do this in your linux/windows host where rvd/rvrd is running
In UNIX :–> ps -ef | grep ‘rvd|rvrd’ | grep -v grep
this will show rvd/rvrd process with parameters used for starting “-http 7580″ shows that http interface is on port 7582
now just type this in your browser.
now just type this in your browser.
Show queues Table Information(SNFGXIBCT )
SNFGXIBCT : –> Prints information on the topic properties in the order
(S)ecure(N)sender_name or sender_name_enforced(F)ailsafe(G)lobale E(X)clusive (I)mport (B)ridge (C)flowControl(T)raceThe characters in the value section show:– Property not present
+ Property is present, and was set on the topic itself* Property is present, and was inherited from another queue
Note that inherited properties cannot be removed.
SNFGXIBCT : –> Prints information on the topic properties in the order
(S)ecure(N)sender_name or sender_name_enforced(F)ailsafe(G)lobale E(X)clusive (I)mport (B)ridge (C)flowControl(T)raceThe characters in the value section show:– Property not present
+ Property is present, and was set on the topic itself* Property is present, and was inherited from another queue
Note that inherited properties cannot be removed.
Root cause : Issue with EMS broker-. This broker does not start up after the server reboot. It fails because the data-store file gets locked
Root cause Error :
2011-06-13 00:00:28 ERROR: Unable to open metadata file ‘datastore/meta.db’, file may be locked.
2011-06-13 00:00:28 FATAL: Exception in startup, exiting.
2011-06-13 00:00:28 FATAL: Exception in startup, exiting.
Resolution :•
1) Try to run flock -u ../datastore/async-msgs.db and flock -u ../datastore/sync-msgs.db?
This should release all the locks on the file.
2) Or Delete the datastore files and then resatrt the EMS server then everything will be back on track!!
No comments:
Post a Comment