web server - Borland Technical Publications

Service Management for JMS Providers
Service Management for JMS Providers
Tibco
The BES service control infrastructure can manage the JMS service process (either a
JVM or native process, whatever form it takes in the JMS provider) as a first class
managed object. Operations like starting, stopping and server configuration is provided
for supported (Tibco, Sonic, and OpenJMS) providers out of the box. Extending this to
any JMS product is documented in “Service Management for other JMS providers” on
page 239.
The BES Management Console allows for template-based additions of any number of
JMS servers, of any vendor type, to the same BES configuration in a management
domain.
Tibco has achieved the runtime level of pluggability that is determined by the
compliance to the J2EE specification.
Added value for Tibco
Tibco provides this added value:
■
■
■
■
Transparent installation
No post installation configuration
Clustering of Tibco servers can be done visually using the BES Management
Console
Tibco Admin Console is available from BES Management Console Tools menu.
Configuring Admin Objects for Tibco
Tibco's admin object properties are defined in BES and can be configured graphically
using the Borland Deployment Descriptor Editor.
See “Setting Admin Objects Using Borland Deployment Descriptor” on page 222.
Auto Queue Creation Feature in Tibco
Tibco has an auto queue creation feature by which if a specified queue does not exist
in the server, the Tibco server will create the queue as necessary.
Tibco Admin Console
Note
You can launch the Tibco Admin Console from within BES only for the Windows
platform. For all other platforms, run the executable from directory to
launch the console.
BES includes the Tibco Admin Console for additional configuration. To launch the
Tibco Admin Console, select it from the Tools menu in the BES Management Console.
Chapter 24: JMS provider pluggability 223