web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
OpenJMS Important When there are multiple messaging applications in the partition, and each of them uses a distinct datasource for application data, the two-phase commit optimization is not possible for each of those applications. The two-phase commit optimization will work only with the one that has the same datasource as OpenJMS. OpenJMS can persist data in only one datasource for all applications in a partition, regardless of the number of applications in that partition. So, if a partition has multiple applications and each application stores its data in its own separate database, you can make OpenJMS datasource to point to only one of those databases. The application that stores its data in this database will achieve the 2PC optimization. Configuring Security with OpenJMS Note The authentication and security features that come with OpenJMS version 0.7.6. work with the following BES configurations: 1 OpenJMS authentication with TCP Connector 2 OpenJMS authentication with VBJ-based RMI Connector HTTPS and TCPS connections are not supported in BES 6.5 release. The following XML code in openjms.xml file shows an example of how to turn on security for configurations 1 and 2 above only. It provides a list of authenticated users: 3 OpenJMS authentication with VBJ-based RMI connector using BES security Refer to the /examples/security/Readme.html document on how to configure security for this configuration. Refer to the OpenJMS documentation in /jms/openjms/docs directory for details on how to use security in OpenJMS. Specifying Partition Level Properties for OpenJMS To integrate OpenJMS as a partition level service in BES, it is introduced as a new service in the partition's configuration. The following properties are for OpenJMS in the partition.xml file. This file is located in /var/domains/base/ configurations//mos//adm/properties directory. The following code in the partition.xml file (located in /var/domains/base/ configurations//mos//adm/properties directory) creates OpenJMS as a partition level service: -
OpenJMS openjms.clean_messages_on_startup="true" openjms.datasource="serial://datasources/OpenJmsDataSource" openjms.sql_file="adm/openjms/conf/openjms.sql" openjms.datasource_lookup_interval="1" openjms.max_datasource_lookup_retries="1" /> The properties are described in the table below: Table 24.1 Partition level porperties for OpenJMS Property Name Description Default Value lifecycle.class openjms.configfile openjms.home openjms.clean_messages_on_startup Used to add an inprocess JMS service. In case of OpenJMS this property has to have a value of com.borland.jms.JmsPartitionServic e. The reflection based code of the partition launcher dynamically detects if the class specified in this property is in the Java CLASSPATH. If it finds it, it tries to load and start the service. This property specifies the location of the configuration file. The location is relative to the current working directory of your partition. This file is the central place where configuration of OpenJMS is stored. This file is needed for the embedded OpenJMS service to come up with a BES partition. This file also contains the list of JNDI objects (Queues, and Topics) that need to be created as part of the OpenJMS service startup. This property specifies where OpenJMS is installed. OpenJMS uses the value specified here to locate various resources. This property indicates whether to clean up the database tables containing JMS messages across partition restart. Currently, this property is only available for JDataStore. For other databases, you must delete messages manually. com.borland.jm s.JmsPartition Service adm/openjms/ conf/ openjms.xml /jms/openjms true 234 BES Developer’s Guide
- Page 193 and 194: 182 BES Developer’s Guide
- Page 195 and 196: Client View of an MDB Client View o
- Page 197 and 198: Clustering of MDBs This is yet anot
- Page 199 and 200: Error Recovery Redelivered messages
- Page 201 and 202: 190 BES Developer’s Guide
- Page 203 and 204: JNDI Definitions Module Important s
- Page 205 and 206: Disabling and Enabling a Deployed D
- Page 207 and 208: Configuring JDBC Datasources In the
- Page 209 and 210: Configuring JDBC Datasources To add
- Page 211 and 212: Defining the Connection Pool Proper
- Page 213 and 214: Defining the Connection Pool Proper
- Page 215 and 216: Descriptions of Borland Enterprise
- Page 217 and 218: Advanced Topics for Defining JDBC D
- Page 219 and 220: Connecting to JDBC Resources from J
- Page 221 and 222: Configuring JMS Connection Factorie
- Page 223 and 224: Defining Connection Pool Properties
- Page 225 and 226: Obtaining JMS Connection Factories
- Page 227 and 228: JMS and Transactions and its accomp
- Page 229 and 230: JMS and Transactions For instance:
- Page 231 and 232: 220 BES Developer’s Guide
- Page 233 and 234: Configuring JMS administered object
- Page 235 and 236: Tibco Creating Clustered JMS Servic
- Page 237 and 238: Sonic serverUrl String localhost:72
- Page 239 and 240: Sonic Creating Clustered JMS Servic
- Page 241 and 242: OpenJMS Even though OpenJMS can be
- Page 243: OpenJMS Important If you use OpenJM
- Page 247 and 248: OpenJMS Table 24.1 Property Name De
- Page 249 and 250: Other JMS providers The following a
- Page 251 and 252: 240 BES Developer’s Guide
- Page 253 and 254: Creating the Interceptor Class For
- Page 255 and 256: Creating the JAR file Creating the
- Page 257 and 258: Components Components The Connector
- Page 259 and 260: System Contracts Connection Managem
- Page 261 and 262: System Contracts Security Managemen
- Page 263 and 264: Common Client Interface (CCI) Conne
- Page 265 and 266: Packaging and Deployment Figure 26.
- Page 267 and 268: Resource Adapters Resource Adapters
- Page 269 and 270: Connection management Connection ma
- Page 271 and 272: Security management with the Securi
- Page 273 and 274: Security management with the Securi
- Page 275 and 276: Resource Adapter overview Note Reso
- Page 277 and 278: Deployment Descriptors for the Reso
- Page 279 and 280: Developing the Resource Adapter Con
- Page 281 and 282: Deploying the Resource Adapter Pack
- Page 283 and 284: Application development overview 8
- Page 285 and 286: Application development overview //
- Page 287 and 288: Application development overview
- Page 289 and 290: Other Considerations Other Consider
- Page 291 and 292: Other Considerations To illustrate,
- Page 293 and 294: Other Considerations } } { cf = new
OpenJMS<br />
openjms.clean_messages_on_startup="true"<br />
openjms.datasource="serial://datasources/OpenJmsDataSource"<br />
openjms.sql_file="adm/openjms/conf/openjms.sql"<br />
openjms.datasource_lookup_interval="1"<br />
openjms.max_datasource_lookup_retries="1" /><br />
<br />
The properties are described in the table below:<br />
Table 24.1<br />
Partition level porperties for OpenJMS<br />
Property Name Description Default Value<br />
lifecycle.class<br />
openjms.configfile<br />
openjms.home<br />
openjms.clean_messages_on_startup<br />
Used to add an inprocess JMS<br />
service. In case of OpenJMS this<br />
property has to have a value of<br />
com.borland.jms.JmsPartitionServic<br />
e. The reflection based code of the<br />
partition launcher dynamically<br />
detects if the class specified in this<br />
property is in the Java<br />
CLASSPATH. If it finds it, it tries to<br />
load and start the service.<br />
This property specifies the location<br />
of the configuration file. The location<br />
is relative to the current working<br />
directory of your partition. This file is<br />
the central place where<br />
configuration of OpenJMS is stored.<br />
This file is needed for the embedded<br />
OpenJMS service to come up with a<br />
BES partition. This file also contains<br />
the list of JNDI objects (Queues,<br />
and Topics) that need to be created<br />
as part of the OpenJMS service<br />
startup.<br />
This property specifies where<br />
OpenJMS is installed. OpenJMS<br />
uses the value specified here to<br />
locate various resources.<br />
This property indicates whether to<br />
clean up the database tables<br />
containing JMS messages across<br />
partition restart. Currently, this<br />
property is only available for<br />
JDataStore. For other databases,<br />
you must delete messages<br />
manually.<br />
com.borland.jm<br />
s.JmsPartition<br />
Service<br />
adm/openjms/<br />
conf/<br />
openjms.xml<br />
/jms/openjms<br />
true<br />
234 BES Developer’s Guide
Change language