[TIBCO.EMS .NET client library 8.1 documentation]

Administered object for creating server connections.

Namespace:  TIBCO.EMS
Assembly:  TIBCO.EMS (in TIBCO.EMS.dll)

Syntax

[SerializableAttribute]
public class ConnectionFactory : CFImpl, 
	ISerializable, ICloneable
<SerializableAttribute> _
Public Class ConnectionFactory _
	Inherits CFImpl _
	Implements ISerializable, ICloneable
[SerializableAttribute]
public ref class ConnectionFactory : public CFImpl, 
	ISerializable, ICloneable

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 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.

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.

Inheritance Hierarchy

See Also