ConnectionFactory


Class

Declaration

class ConnectionFactory 

Purpose

Administered object for creating server connections.

Remarks

Connection factories are administered objects. They support concurrent use.

Administrators define connection factories in a repository. Each connection factory has administrative parameters that guide the creation of server connections. Usage follows either of two models:

EMS Server

You can use the EMS server as a name service provider—one tibemsd process provides both the name repository and the message service. Administrators define factories in the name repository. Client programs create connection factory objects with the URL of the repository, and call the ConnectionFactory.CreateConnection method. This method automatically accesses the corresponding factory in the repository, and uses it to create a connection to the message service.

Separate JNDI Repository

Administrators define factories in a JNDI repository. Client programs call LookupContext.Lookup to retrieve factories, and use them to create connections to the server.

 

Member
Description
Properties
Metric
FactoryLoadBalanceMetric Metric {get; set;}
When the connection factory balances the client load among several servers, it uses this metric to determine the least loaded server, so the connection factory can create a connection to it. For values, see FactoryLoadBalanceMetric .

 

Method
Description
Page
Constructor.
134
135

Administered Objects

Administered objects let administrators configure EMS behavior at the enterprise level. Administrators define these objects, and client programs use them. This arrangement relieves program developers and end users of the responsibility for correct configuration.

Subclasses

QueueConnectionFactory

TopicConnectionFactory

See Also

LookupContext


TIBCO Enterprise Message Service™ .NET Reference
System Release 4.3, February 2006
Copyright © TIBCO Software Inc. All rights reserved
www.tibco.com