Configure... | Specify... |
Name | Required and unique. Name of the new connection factory. Once created, you cannot edit the JNDI connection factory name. For example, connectionfactory1. |
Type | Required. Type of connection factory selected when creating the connection factory. For example, XA Connection Factory. Note: This field cannot be edited. |
Connection URL | Required. Universal Messaging server URL for binding the connection factory. For example, nsp://umhostname:9000. A cluster of server instances is specified using 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 allow 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. See the section
URL Syntax for Horizontal Scalability for details of this syntax. Example: (UM1,UM2)(UM3,UM4) - Indicates 2 clusters, one consisting of UM1 and UM2 and the other consisting of UM3 and UM4, so only 2 connections will be constructed here. Note: Round-robin delivery is not supported for XA Connection Factory. |
Durable type | Select the durable type. The durable type Named is selected by default. Note: You can configure the durable type property only for Connection Factory and Topic Connection Factory. |