![]() ![]() ![]() ![]() ![]() Since there aren’t queue consumers active, the message will be persisted in the queue on the EMS server, showing as pending message. The aim of this step is to show the message configuration and the bridging mechanism working properly. The tool used to build the client is TIBCO Designer. In order to proceed with the steps it’s required to have a client in order to send a message to the topic and test the bridge mechanism with the selector. Using the TIBCO EMS administrator tool or the GEMS tool it’s possible to see the queues and the topics created. Open a command line and go to the “ %TIBCO_HOME%/ems/8.1/bin ” and run the following command:Ĭ:TIBCOems8.1bin>tibemsadmin -server “tcp://localhost:7222” -user your_admin_user -password your_admin_password -script E:ScriptNameSavedAtStep1.script Start the TIBCO EMS server either from the service list or from the TIBCO EMS Administration Tool. Note: when the retry mechanism is in place it’s advisable to set the prefetch value to 0, in order do not experience unexpected behaviors. Open a text editor in order to create the “.script” file to be executed in the TIBCO EMS server type the following commands and save the file on the disk. The steps are described taking in account a TIBCO installation on a Windows machine. Copy messages from the $sys.undelivered queue and publish them to a destination queue.Configure the queue’s properties to receive the message automatically for a specific number of time at specified intervals in case of errors.Set the bridge property between a topic and a queue based on a selector.Create topics and queues through scripts.This is a technical post that wants to achieve the following goals regarding TIBCO EMS bridging: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |