Field | Description |
Name | Required. Unique name of the new connection factory, for example, connectionfactory1. You cannot edit the name after you create the connection factory. |
Type | Type of the connection factory. You cannot edit this field. |
Connection URL | Required. Universal Messaging server URL for binding the connection factory, for example, nsp://localhost:9000. To specify a cluster of server instances, use a comma-separated list of connection URLs, for example, nsp://localhost:9000,nsp://localhost:9010. You can use a horizontal scalability connection factory to specify several connection URLs, where each connection URL can point to a standalone realm or a cluster. Horizontal scalability connection factories enable clients to publish messages to a set of servers or consume messages from a set of servers in a round-robin manner: For round-robin publishing, one message or transaction gets published to the first realm node or cluster, the next message to the next realm node or cluster, and so on. For round-robin consuming, there is no guarantee about the order in which the events are delivered. For a horizontal scalability connection factory, you specify several connection URLs, using the horizontal scalability URL syntax. For information about the syntax, see
URL Syntax for Horizontal Scalability. Consider the following example: (UM1,UM2)(UM3,UM4) - Indicates 2 clusters, one consisting of UM1 and UM2 and the other consisting of UM3 and UM4, so only two connections are constructed here. Note: Round-robin delivery is not supported for XA Connection Factory. |
Durable type | Select the durable type for Connection Factory and Topic Connection Factory. The default type is Named. |