web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Other JMS providers Using Message Driven Beans (MDB) with OpenJMS Important For a BES partition to support MDBs, the MDB must be able to access a JMS server. To make the MDB access the OpenJMS server, make sure that: 1 OpenJMS is installed and enabled as an in-process service in your partition or available in the domain. Right-click on the OpenJMS service and select Start from the menu to enable the service. 2 The resource references are properly configured in the ejb-jar.xml file to point to the right type of connection factory. If your MDB needs transactional access, you must use Embedded or RMI connection factories with your MDB so as to support transaction propagation. Other JMS providers For other JMS providers to achieve a runtime level of pluggability, compliance with the J2EE specifications is necessary. BES requires that the JMS XA APIs support JTA integration. In addition, the JMS product should support the ConnectionConsumer interface. Refer to Sun's chapter on the JMS API for specific information on complying with the specification. Note Required client libraries for other JMS providers When trying to connect to another JMS provider the required libraries must first be deployed to the target Partition. The steps are: 1 Start your BES server and Management Console. 2 From the Console, open the Wizards menu and select the Deployment Wizard. The wizard allows you to deploy modules to a Partition. 3 “Add” the library file and check the option to restart the Partition on deploy. 4 Proceed to deploy to the chosen Partition(s). Close the wizard. You should see your libraries listed under the “Deployed Modules” folder of the Partition(s). The Borland Deployment Descriptor Editor panels do not provide as much custom help for other JMS vendor products as it does for JMS vendors certified to work with BES. Refer to the other JMS vendor's documentation to ascertain the correct name of the ConnectionFactory, Topic or Queue implementation class in order to create JNDI objects. All required libraries are already configured so nothing extra is needed if you are going to use JMS services bundled with BES. Configuring admin objects for other JMS providers BES provides configurations in the Borland Deployment Descriptor Editor for Tibco, Sonic and other JMS providers. However, there are required properties and classes for using other JMS providers with BES. These must be configured in the jms.properties file located in C:\Documents and Settings\username\.bmc60. Chapter 24: JMS provider pluggability 237
Other JMS providers The following are the required properties that must be configured in the jms.properties file: Tibco.QueueConnectionFactory.props=serverUrl,clientID,userName,userPassword Tibco.XAQueueConnectionFactory.props=serverUrl,clientID,userName,userPassword Tibco.TopicConnectionFactory.props=serverUrl,clientID,userName,userPassword Tibco.XATopicConnectionFactory.props=serverUrl,clientID,userName,userPassword Tibco.Queue.props=address Tibco.Topic.props=address Sonic.QueueConnectionFactory.props=connectionURLs,defaultUser,defaultPassword,c onnectID,clientID,sequential,loadBalancing Sonic.TopicConnectionFactory.props=connectionURLs,defaultUser,defaultPassword,c onnectID,clientID,sequential,loadBalancing Sonic.XAQueueConnectionFactory.props=connectionURLs,defaultUser,defaultPassword ,connectID,clientID,sequential,loadBalancing Sonic.XATopicConnectionFactory.props=connectionURLs,defaultUser,defaultPassword ,connectID,clientID,sequential,loadBalancing Sonic.Queue.props=queueName Sonic.Topic.props=topicName Other.QueueConnectionFactory.props= Other.TopicConnectionFactory.props= Other.XAQueueConnectionFactory.props= Other.XATopicConnectionFactory.props= Other.Queue.props= Other.Topic.props= Tibco.QueueConnectionFactory.class=com.tibco.tibjms.TibjmsQueueConnectionFactor y Tibco.TopicConnectionFactory.class=com.tibco.tibjms.TibjmsTopicConnectionFactor y Tibco.XAQueueConnectionFactory.class=com.tibco.tibjms.TibjmsXAQueueConnectionFa ctory Tibco.XATopicConnectionFactory.class=com.tibco.tibjms.TibjmsXATopicConnectionFa ctory Tibco.Queue.class=com.tibco.tibjms.TibjmsQueue Tibco.Topic.class=com.tibco.tibjms.TibjmsTopic Sonic.QueueConnectionFactory.class=progress.message.jclient.QueueConnectionFact ory Sonic.TopicConnectionFactory.class=progress.message.jclient.TopicConnectionFact ory Sonic.XAQueueConnectionFactory.class=progress.message.jclient.xa.XAQueueConnect ionFactory Sonic.XATopicConnectionFactory.class=progress.message.jclient.xa.XATopicConnect ionFactory Sonic.Queue.class=progress.message.jclient.Queue Sonic.Topic.class=progress.message.jclient.Topic Other.QueueConnectionFactory.class= Other.TopicConnectionFactory.class= Other.XAQueueConnectionFactory.class= Other.XATopicConnectionFactory.class= Other.Queue.class= Other.Topic.class= PropertyName=type, default type=QueueConnectionFactory|TopicConnectionFactory|XAQueueConnectionFactory| XATopicConnectionFactory|Queue|Topic connectionURLs=String,localhost:2506 defaultUser=String defaultPassword=String connectID=String clientID=String sequential=Boolean,false 238 BES Developer’s Guide
- 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 and 244: OpenJMS Important If you use OpenJM
- Page 245 and 246: OpenJMS openjms.clean_messages_on_s
- Page 247: OpenJMS Table 24.1 Property Name De
- 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
- Page 295 and 296: General syntax and usage General sy
- Page 297 and 298: Syntax and usage for iastool Table
Other JMS providers<br />
The following are the required properties that must be configured in the jms.properties<br />
file:<br />
Tibco.QueueConnectionFactory.props=<strong>server</strong>Url,clientID,userName,userPassword<br />
Tibco.XAQueueConnectionFactory.props=<strong>server</strong>Url,clientID,userName,userPassword<br />
Tibco.TopicConnectionFactory.props=<strong>server</strong>Url,clientID,userName,userPassword<br />
Tibco.XATopicConnectionFactory.props=<strong>server</strong>Url,clientID,userName,userPassword<br />
Tibco.Queue.props=address<br />
Tibco.Topic.props=address<br />
Sonic.QueueConnectionFactory.props=connectionURLs,defaultUser,defaultPassword,c<br />
onnectID,clientID,sequential,loadBalancing<br />
Sonic.TopicConnectionFactory.props=connectionURLs,defaultUser,defaultPassword,c<br />
onnectID,clientID,sequential,loadBalancing<br />
Sonic.XAQueueConnectionFactory.props=connectionURLs,defaultUser,defaultPassword<br />
,connectID,clientID,sequential,loadBalancing<br />
Sonic.XATopicConnectionFactory.props=connectionURLs,defaultUser,defaultPassword<br />
,connectID,clientID,sequential,loadBalancing<br />
Sonic.Queue.props=queueName<br />
Sonic.Topic.props=topicName<br />
Other.QueueConnectionFactory.props=<br />
Other.TopicConnectionFactory.props=<br />
Other.XAQueueConnectionFactory.props=<br />
Other.XATopicConnectionFactory.props=<br />
Other.Queue.props=<br />
Other.Topic.props=<br />
Tibco.QueueConnectionFactory.class=com.tibco.tibjms.TibjmsQueueConnectionFactor<br />
y<br />
Tibco.TopicConnectionFactory.class=com.tibco.tibjms.TibjmsTopicConnectionFactor<br />
y<br />
Tibco.XAQueueConnectionFactory.class=com.tibco.tibjms.TibjmsXAQueueConnectionFa<br />
ctory<br />
Tibco.XATopicConnectionFactory.class=com.tibco.tibjms.TibjmsXATopicConnectionFa<br />
ctory<br />
Tibco.Queue.class=com.tibco.tibjms.TibjmsQueue<br />
Tibco.Topic.class=com.tibco.tibjms.TibjmsTopic<br />
Sonic.QueueConnectionFactory.class=progress.message.jclient.QueueConnectionFact<br />
ory<br />
Sonic.TopicConnectionFactory.class=progress.message.jclient.TopicConnectionFact<br />
ory<br />
Sonic.XAQueueConnectionFactory.class=progress.message.jclient.xa.XAQueueConnect<br />
ionFactory<br />
Sonic.XATopicConnectionFactory.class=progress.message.jclient.xa.XATopicConnect<br />
ionFactory<br />
Sonic.Queue.class=progress.message.jclient.Queue<br />
Sonic.Topic.class=progress.message.jclient.Topic<br />
Other.QueueConnectionFactory.class=<br />
Other.TopicConnectionFactory.class=<br />
Other.XAQueueConnectionFactory.class=<br />
Other.XATopicConnectionFactory.class=<br />
Other.Queue.class=<br />
Other.Topic.class=<br />
PropertyName=type, default<br />
type=QueueConnectionFactory|TopicConnectionFactory|XAQueueConnectionFactory|<br />
XATopicConnectionFactory|Queue|Topic<br />
connectionURLs=String,localhost:2506<br />
defaultUser=String<br />
defaultPassword=String<br />
connectID=String<br />
clientID=String<br />
sequential=Boolean,false<br />
238 BES Developer’s Guide
Change language