Default Provider topic connection factory settings
To set the configuration properties of the selected JMS topic connection factory for use with the internal product Java™ Message Service (JMS) provider that is installed with WAS. These configuration properties control how connections are created between the JMS provider and the service integration bus that it uses.
To view this ACRCT page, click File > Open. After you browse for an EAR file, click Open. Expand the selected JAR file > Messaging Providers > Default Provider. Right-click Topic Connection Factories and click New.
The following fields appear on the General tab.
Settings that have a default value display that appropriate value. Any settings that have fixed values have a drop down menu.
- Name
The name of the topic connection factory.
Data type String
- Description
A description of this topic connection factory for administrative purposes within IBM WAS.
Data type String
- JNDI Name
The JNDI name used to match this topic connection factory definition to the deployment descriptor. This entry is a resource-ref name.
Data type String
- User Name
The User Name used, with the property, for authentication if the calling application does not provide a userid and password explicitly. If this field is used, then the Properties field UserName is ignored.
If we specify a value for the User Name property, also specify a value for the property.
The connection factory User Name and properties are used if the calling application does not provide a userid and password explicitly. If a user name and password are specified, then an authentication alias is created for the factory where the password is encrypted.
Data type String
The password used to create an encrypted. If we complete this field, then the field in the Properties box is ignored.
If we specify a value for the User Name property, also specify a value for the property.
Data type String
- Re-Enter
Confirms the password.
- Bus Name
The name of the bus to which the topic connection factory connects.
Data type String
- Client Identifier
The name of the client. Required for durable topic subscriptions.
Data type String
- Nonpersistent Messaging Reliability
The reliability applied to nonpersistent JMS messages sent using this connection factory.
If we want different reliability delivery options for individual JMS destinations, we can set this property to As bus destination. The reliability is then defined by the Reliability property of the bus destination to which the JMS destination is assigned.
Default ReliablePersistent Range
- None
- There is no message reliability for nonpersistent messages. If a nonpersistent message cannot be delivered, it is discarded.
- Best effort nonpersistent
- Messages are never written to disk, and are thrown away if memory cache overruns.
- Express nonpersistent
- Messages are written asynchronously to persistent storage if memory cache overruns, but are not kept over server restarts.
- Reliable nonpersistent
- Messages can be lost if a messaging engine fails, and can be lost under normal operating conditions.
- Reliable persistent
- Messages can be lost if a messaging engine fails, but are not lost under normal operating conditions.
- Assured persistent
- Highest degree of reliability where assured message delivery is supported.
- As Bus destination
- Use the delivery option configured for the bus destination.
- Persistent Message Reliability
The reliability applied to persistent JMS messages sent using this connection factory.
If we want different reliability delivery options for individual JMS destinations, we can set this property to As bus destination. The reliability is then defined by the Reliability property of the bus destination to which the JMS destination is assigned.
Default ReliablePersistent Range
- None
- There is no message reliability for nonpersistent messages. If a nonpersistent message cannot be delivered, it is discarded.
- Best effort nonpersistent
- Messages are never written to disk, and are thrown away if memory cache overruns.
- Express nonpersistent
- Messages are written asynchronously to persistent storage if memory cache overruns, but are not kept over server restarts.
- Reliable nonpersistent
- Messages can be lost if a messaging engine fails, and can be lost under normal operating conditions.
- Reliable persistent
- Messages can be lost if a messaging engine fails, but are not lost under normal operating conditions.
- Assured persistent
- Highest degree of reliability where assured message delivery is supported.
- As Bus destination
- Use the delivery option configured for the bus destination.
- Durable Subscription Home
The name of the durable subscription home.
Data type String
- Share durable subscriptions
Controls whether or not durable subscriptions are shared across connections with members of a server cluster.
Normally, only one session at a time can have a TopicSubscriber for a particular durable subscription. This property enables you to override this behavior, to enable a durable subscription to have multiple simultaneous consumers.
Data type Selection list Default In cluster Range
- In cluster
- Allows sharing of durable subscriptions when connections are made from within a server cluster.
- Always shared
- Durable subscriptions can be shared across connections.
- Never shared
- Durable subscriptions are never shared across connections.
- Read Ahead
Controls the read-ahead optimization during message delivery.
Default Default Range Default, AlwaysOn and AlwaysOff
- Target
The name of the Workload Manager target group containing the messaging engine.
Data type String
- Target Type
The type of Workload Manager target group that contains the messaging engine.
Default BusMember Range BusMember, Custom, ME
- Target Significance
The priority of significance for the target specified.
Default Preferred Range Preferred, Required
- Target Inbound Transport Chain
The name of the protocol that resolves to a group of messaging engines.
Data type String
- Provider Endpoints
The list of comma separated endpoints used to connect to a bootstrap server.
Type a comma-separated list of endpoint triplets with the syntax: host:port:protocol.
Example BootstrapBasicMessaging corresponds to the remote protocol InboundBasicMessaging (JFAP-TCP/IP).
Default
- If the host name is not specified, then the default localhost is used as a default value.
- If the port number is not specified, then 7276 is used as a default value.
- If the chain name is not specified, a predefined chain, such as BootstrapBasicMessaging, is used as a default value.
- Connection Proximity
The proximity that the messaging engine should have to the requester.
Default Bus Range Bus, Host, Cluster, Server
- Temporary Topic Name Prefix
The prefix to apply to the names of temporary topics. This name is a maximum of 12 characters.
Data type String