+

Search Tips   |   Advanced Search

Default Provider queue connection factory settings



Overview

To set the configuration of a selected JMS queue connection factory used with the WAS JMS provider, pull up ACRCT, and click...

File | Open | EAR_file | Open | [Expand the selected JAR file] | Messaging Providers | Default Provider | Queue Connection Factories (right-click) | New
These configuration properties control how connections are created between the JMS provider and the service integration bus that it uses

The following fields appear on the General tab.

Settings that have a default value display the appropriate value. Any settings that have fixed values have a drop down menu.

Name

The name of the queue connection factory.

Data type String

Description

A description of this queue connection factory for administrative purposes within IBM WAS.

Data type String

JNDI Name

The JNDI name used to match this queue 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 queue connection factory connects.

Data type String

Client Identifier

The client identifier. 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.

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, Destination, 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 localhost:7777:BootstrapBasicMessaging

Where 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, Cluster, Server
Range Bus, Host

Temporary Queue Name Prefix

The prefix to apply to the names of temporary queues. This name is a maximum of 12 characters.

Data type String