A JMS topic connection factory is used to create connections to the associated JMS provider of JMS topics, for publish/subscribe messaging. Use topic connection factory administrative objects to manage JMS topic connection factories for the default messaging provider.
To view this pane in the console, click the following path:
.
By default, connections created using this JMS connection factory in the server containers (for example, from an enterprise bean) are pooled using J2C connection pooling. You can modify the connection pool settings for this connection factory by selecting the Connection pool properties properties link in the Additional properties section of the administrative console panel.
The configuration of a container-managed authentication alias and mapping module on a connection factory are deprecated in release 6.0. You now set these properties in the bindings for the resource reference of the application. If you do not want to modify the bindings for an existing application, locate this connection factory in the J2C panels where you can still find these properties.
Configuration properties for this object. These property values are preserved even if the runtime environment is stopped then restarted. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.
Specifies the highest topological level at which application servers can use this resource object.
Required | No |
Data type | Text |
Specifies a JMS provider, which enables asynchronous messaging based on the Java Message Service (JMS). It provides J2EE connection factories to create connections for specific JMS queue or topic destinations. JMS provider administrative objects are used to manage JMS resources for the associated JMS provider.
Required | No |
Data type | Text |
The JNDI name for the resource.
As a convention, use a JNDI name of the form jms/Name, where Name is the logical name of the resource. For more information about the use of JNDI and its syntax, see JNDI support in WebSphere Application Server in the WebSphere Application Server information center.
Required | Yes |
Data type | Text |
The name of the service integration bus to connect to.
Required | Yes |
Data type | Custom |
The name of a target that identifies a group of messaging engines. Specify the type of target using the Target type property.
This indicates the name of a target that is to be used to determine one or more messaging engines to handle work. The type of target is indicated by the Target type property
Connections are load balanced across the available messaging engines that satisfy the selection criteria.
If you want applications to be able to connect to any messaging engine in the bus, do not set this property.
For more information about using this property with other connection factory properties for workload management of connections, see Administrative properties for JMS connections to a bus.
Required | No |
Data type | Text |
The type of target named in the Target property.
Required | No |
Data type | drop-down list |
Range |
|
This property specifies the significance of the target group.
For more information about using this property with other connection factory properties for workload management of connections, see Administrative properties for JMS connections to a bus.
Required | No |
Data type | drop-down list |
Range |
|
The name of the inbound transport chain that the application should target when connecting to a messaging engine in a separate process to the application. If a messaging engine in another process is chosen, a connection can be made only if the messaging engine is in a server that runs the specified inbound transport chain. Refer to the InfoCenter for more information.
If the selected messaging engine is in the same server as the application, a direct in-process connection is made and this transport chain property is ignored.
The transport chains represent network protocol stacks operating within a server. The name you specify must be one of the transport chains available in the server that hosts the messaging engine, as listed on the server_name panel. The following transport chains are provided, but you can define your own transport chains on that panel.
For more information about using this property with other connection factory properties for workload management of connections, see Administrative properties for JMS connections to a bus.
Required | No |
Data type | Text |
A comma-separated list of endpoint triplets, with the syntax hostName:portNumber:chainName, used to connect to a bootstrap server. For example Merlin:7276:BootstrapBasicMessaging,Gandalf:5557:BootstrapSecureMessaging.". If hostName is not specified, the default is localhost. If portNumber is not specified, the default is 7276. If chainName is not specified, the default is BootstrapBasicMessaging. Refer to the InfoCenter for more information.
You only need to modify this property if you have client applications running outside of an application server, or applications on a server in another cell, that want to use this connection factory to connect to the target service integration bus specified on the connection factory.
To use JMS destinations of the default messaging provider, an application connects to a messaging engine on the target service integration bus to which the destinations are assigned. For example, a JMS queue is assigned to a queue destination on a service integration bus.
Client applications running outside of an application server - for example, running in a client container or outside the WebSphere Application Server environment - cannot locate directly a suitable messaging engine to connect to in the target bus. Similarly, an application running on a server in one cell to connect to a target bus in another cell cannot locate directly a suitable messaging engine to connect to in the target bus.
In these scenarios, the clients (or servers in another bus) must complete a bootstrap process through a bootstrap server that is a member of the target bus. A bootstrap server is an application server running the SIB Service, but does not need to be running any messaging engines. The bootstrap server selects a messaging engine that is running in an application server that supports the desired target transport chain. For the bootstrap process to be possible, you must configure one or more provider end points in the connection factory used by the client.
A bootstrap server uses a specific port and bootstrap transport chain. The port is the SIB_ENDPOINT_ADDRESS (or SIB_ENDPOINT_SECURE_ADDRESS if security is enabled), of the messaging engine hosting the remote end of the link. Together with host name, these form the endpoint address of the bootstrap server.
If you want an application to use a bootstrap server with a different endpoint address, you need to specify the required endpoint address on the Provider endpoints property of the JMS connection factories that the client application uses. You can specify one or more endpoint addresses of bootstrap servers.
The endpoint addresses for bootstrap servers must be specified in every JMS connection factory that is used by applications outside of an application server. To avoid having to specify a long list of bootstrap servers, you can provide a few highly-available servers as dedicated bootstrap servers. Then you only need to specify a short list of bootstrap servers on each connection factory.
boothost1:7278:BootstrapBasicMessaging or boothost1:7278and for a server assigned secure port 7289, on host boothost2, and using the predefined transport chain BootstrapTunneledSecureMessaging:
boothost2:7289:BootstrapTunneledSecureMessaging
[ [host_name] [ ":" [port_number] [ ":" chain_name] ] ]where:
[2002:914:fc12:179:9:20:141:42]:7276:BootstrapBasicMessaging. If a value is not specified, the default is localhost.
If port_number is not specified, the default is 7276.
The following predefined bootstrap transport chains are provided:
Specifying host_name : chain_name instead of host_name : : chain_name (with two colons) is incorrect. It is valid to enter nothing, or to enter any of the following: "a, "a:", ":7276", "::chain", and so on. The default value applies if you do not specify a value, but you must separate the fields with ":"s.
boothost1:7278:BootstrapBasicMessaging, boothost2:7289:BootstrapTunneledSecureMessaging, [2002:914:fc12:179:9:20:141:42]:7276:BootstrapBasicMessaging
Required | No |
Data type | Text area |
The proximity of messaging engines that can accept connection requests, in relation to the bootstrap messaging engine.
For more information about using this property with other connection factory properties for workload management of connections, see Administrative properties for JMS connections to a bus.
Required | No |
Data type | drop-down list |
Range |
|
The reliability applied to nonpersistent JMS messages sent using this connection factory.
Required | No |
Data type | drop-down list |
Range |
|
The reliability applied to persistent JMS messages sent using this connection factory.
Required | No |
Data type | drop-down list |
Range |
|
Read ahead is an optimization that preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
You can override this property for individual JMS destinations by setting the Read ahead property on the JMS destination.
Required | No |
Data type | drop-down list |
Range |
|
This alias specifies a user ID and password to be used to authenticate connections to the JMS provider for application-managed authentication.
This property provides a list of the J2C authentication data entry aliases that have been defined to WebSphere Application Server. You can select a data entry alias to be used to authenticate the creation of a new connection to the JMS provider.
If you have enabled WebSphere Application Server security, select the alias that specifies the user ID and password used to authenticate the creation of a new connection to the JMS provider. The use of this alias depends on the resource authentication (res-auth) setting declared in the connection factory resource reference of an application component's deployment descriptors.
Required | No |
Data type | drop-down list |
Whether or not the container logs that there is a missing transaction context when a connection is obtained.
Select this property to log connections being created without a transaction context.
Required | No |
Data type | Check box |
Whether cached handles (handles held in instance variables in a bean) should be tracked by the container.
Required | No |
Data type | Check box |
The authentication alias used during XA recovery processing.
This property provides a list of the J2C authentication data entry aliases that have been defined to WebSphere Application Server. You can select a data entry alias to be used to authenticate during XA recovery processing.
If you have enabled security for the associated service integration bus, select the alias that specifies the user ID and password used for XA recovery which is valid in the user registry for WebSphere Application Server. This property must be set if bus security is enabled and XA transactions are to be used.
Required | No |
Data type | drop-down list |