web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Tibco Integrating clustered Tibco servers into BES The fault tolerant Tibco JMS server pair is represented in BES as a redundancy group Managed Object. Although there are two Tibco servers running, BES shows the pair of servers as a single Managed Object. The definition for the Redundancy Group Managed Object is shown below: Note The Tibco servers in the example above are running on different hosts. Configuring clients for fault tolerant Tibco connections To connect to a backup server in the event of failure of a primary server, a client application must specify multiple server URLs in the jndi-object XML for the connection factories as below: jms/XAQueueConnectionFactory com.tibco.tibjms.TibjmsXAQueueConnectionFactory serverUrl String localhost:7222,hnguyen:7222 jms/QueueConnectionFactory com.tibco.tibjms.TibjmsQueueConnectionFactory serverUrl String localhost:7222,hnguyen:7222 jms/XATopicConnectionFactory com.tibco.tibjms.TibjmsXATopicConnectionFactory serverUrl String localhost:7222,hnguyen:7222 jms/TopicConnectionFactory com.tibco.tibjms.TibjmsTopicConnectionFactory Chapter 24: JMS provider pluggability 225
Sonic serverUrl String localhost:7222,hnguyen:7222 Enabling Security for Tibco Note For information on SSL, please refer to the Tibco documentation. Tibco documentation is located in \jms\tibco\doc\html. To enable security for Tibco, you can either modify the tibjmsd.conf file located in: / /var/domains/base/configurations// mos/tibco/tibjmsd.conf, or you can set it using the Tibco Admin tool. 1 From the Tools menu in Borland Management Console launch the Tibco Admin Console tool. 2 Type connect. 3 Enter Login name and Password. 4 Once connected, type set server authorization=enabled. 5 Security is now enabled. For client authentication, users should be created and added to an authorization group. For instance, create a user using the command: create user [] [password=]. 6 Add a member, type add member [,,...]. Disabling security for Tibco Set the server authorization to disabled: set server authorization=disabled. Sonic Sonic has achieved the runtime level of pluggability which is determined by compliance to the J2EE specification. Configuring Admin Objects for Sonic Sonic'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. 226 BES Developer’s Guide
- 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 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: Tibco Creating Clustered JMS Servic
- 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
- Page 281 and 282: Deploying the Resource Adapter Pack
- Page 283 and 284: Application development overview 8
- Page 285 and 286: Application development overview //
Tibco<br />
Integrating clustered Tibco <strong>server</strong>s into BES<br />
The fault tolerant Tibco JMS <strong>server</strong> pair is represented in BES as a redundancy group<br />
Managed Object. Although there are two Tibco <strong>server</strong>s running, BES shows the pair of<br />
<strong>server</strong>s as a single Managed Object. The definition for the Redundancy Group<br />
Managed Object is shown below:<br />
<br />
<br />
Note<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
The Tibco <strong>server</strong>s in the example above are running on different hosts.<br />
Configuring clients for fault tolerant Tibco connections<br />
To connect to a backup <strong>server</strong> in the event of failure of a primary <strong>server</strong>, a client<br />
application must specify multiple <strong>server</strong> URLs in the jndi-object XML for the<br />
connection factories as below:<br />
<br />
jms/XAQueueConnectionFactory<br />
com.tibco.tibjms.TibjmsXAQueueConnectionFactory<br />
<br />
<strong>server</strong>Url<br />
String<br />
localhost:7222,hnguyen:7222<br />
<br />
<br />
<br />
jms/QueueConnectionFactory<br />
com.tibco.tibjms.TibjmsQueueConnectionFactory<br />
<br />
<strong>server</strong>Url<br />
String<br />
localhost:7222,hnguyen:7222<br />
<br />
<br />
<br />
jms/XATopicConnectionFactory<br />
com.tibco.tibjms.TibjmsXATopicConnectionFactory<br />
<br />
<strong>server</strong>Url<br />
String<br />
localhost:7222,hnguyen:7222<br />
<br />
<br />
jms/TopicConnectionFactory<br />
com.tibco.tibjms.TibjmsTopicConnectionFactory<br />
<br />
Chapter 24: JMS provider pluggability 225
Change language