web server - Borland Technical Publications

OpenJMS
Table 24.1
Property Name Description Default Value
openjms.database.softcommit
This property is only applicable
when JDataStore is used to persist
JMS messages. This property
provides improved performance
during commit process, but with lack
of recoverability in some rare failure
scenarios. See JDataStore
documentation for more details.
true
openjms.database
Partition level porperties for OpenJMS (continued)
openjms.use_bes_transactions
OpenJMS Topologies
This property only applies to JDS
and is used to specify the name of
the JDS database.
OpenJMS starts a transaction
before it dispatches messages. It
uses the transaction service that is
part of the partition which contains
OpenJMS. If no transaction service
is available in the partition, one from
the Smart Agent domain is selected.
Use this property when you use
OpenJMS during transactions. This
property does not affect the
messaging applications that don’t
involve transactions. However, to
avoid an extra cost of transaction
startup and propagation turn this
property off.
openjms.jds
true
Important
Note
If you have two OpenJMS services with both of them using the TCP connector, make
sure you have different port numbers specified for them in the openjms.xml file. To open
this file, right-click on the OpenJMS service in the Borland Management Console and
select Properties from the drop down menu. Click on the openjms.xml tab in the right
pane.
OpenJMS can be configured to run in the following two topologies:
■
Server shared mode - where the OpenJMS service is hosted in a dedicated
partition with other services in that partition disabled. It is available as a shared
service to all partitions that are in the same osagent domain as the configuration in
which OpenJMS partition resides. The remote clients can access OpenJMS via an
RMI or TCP connector. Since OpenJMS needs a naming service to bind the JNDI
objects that are specified in its configuration file, the Transaction and Naming
services must be enabled in the partition that hosts OpenJMS or they should be
available in the SmartAgent domain.
■
Embedded Service mode - where OpenJMS is run as an embedded service in
each of the partitions in the configuration. Each partition uses the embedded (intravirtual
machine) connector of OpenJMS instead of the TCP or RMI connector. The
JMS clients use the embedded queue/topic connection factories. These factories
provide optimal ways to avoid the cost of TCP/IP. Even though JMS clients can use
the RMI connector in this mode, to achieve maximum performance it must use the
local (embedded) connector.
If multiple OpenJMS service instances are running in a single SmartAgent domain of
BES, there will be no database sharability or automatic failover to a running instance.
This is because there is no support for clustering for OpenJMS.
236 BES Developer’s Guide