web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Enabling the JMS services security Enabling the JMS services security Refer to Chapter 24, “JMS provider pluggability” for vendor-specific information on JMS services such as security. Advanced Concepts for Configuring JMS Connection Factories and Destinations All resource objects, JDBC Datasources, JMS Connection Factories and JMS Destinations, are defined in a DAR module using a jndi-definitions.xml descriptor. Module default-resources.dar, predeployed in all BES partitions, contains some default Connection Factories, Topics and Queues, defined for the bundled JMS service. You can edit these existing definitions to suit your environment or create new definitions using the DDEditor. JMS connection factories, similar to JDBC datasources, are classes that wrap the connection factory classes provided by JMS vendors. If you want to use a JMS vendor not bundled or certified to work with BES, you need to deploy that vendor's connection factory classes to your Partition. The jndi-definitions.xml descriptor DTD shows the relevant element, in bold: The element can be used to define a JMS connection factory or a JMS destination for deployment under JNDI. In this element, you specify the following: ■ ■ ■ jndi-name: this is the name that will be looked up under JNDI and from which a JMS connection factory or JMS destination is resolved. class-name: this is the vendor specific connection factory or destination class name. The class should be deployed as a library archive in your Partition only if a deployed component performs JNDI lookups for JMS resource objects of this vendor. properties: these are properties specific to BES and the JMS provider required to construct actual JMS resource object. Refer to Chapter 24, “JMS provider pluggability” for vendor-specific information on JMS queues. Chapter 23: Using JMS 219
220 BES Developer’s Guide
- Page 179 and 180: Transaction manager services Consis
- Page 181 and 182: Transaction manager services When t
- Page 183 and 184: Transaction manager services Follow
- Page 185 and 186: Declarative transaction management
- Page 187 and 188: Declarative transaction management
- Page 189 and 190: JDBC API Modifications JDBC API Mod
- Page 191 and 192: Handling of EJB exceptions Applicat
- 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: JMS and Transactions For instance:
- 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 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
220 BES Developer’s Guide
Change language