Broker 10.15 | webMethods Broker Documentation | Administering webMethods Broker | Using My webMethods with JMS | Managing Cluster Connection Factories | Viewing Detailed Information About Cluster Connection Factories
 
Viewing Detailed Information About Cluster Connection Factories
Use the following procedure to view detailed information about a cluster connection factory.
*To view detailed information about a cluster connection factory
1. Perform the steps listed in Viewing a List of Cluster Connection Factories.
2. Under Lookup Name, click the cluster connection factory whose information you want to view.
The Connection Factory Detail page displays the following information:
Field
Description
Lookup Name
Name of the JNDI directory with which this cluster connection factory is bound.
Provider
Name of the JNDI provider supporting this cluster connection factory.
Connection Factory Type
For descriptions of each cluster connection factory type, see Viewing the Detailed Information About Connection Factories.
Connection Factory
Client ID
The base client ID for connections created by this factory.
*If a client ID is specified, the connection factory derives a client ID from this value each time a connection is established.
*If a client ID is not specified, the connection factory assigns a unique client ID when a connection is established.
Cluster Name
The name of the cluster with which this cluster connection factory is associated.
Cluster Policy
The load-balancing policy governing the cluster, namely:
*Round Robin
*Sticky
*Random
*Weighted Round Robin
*Multisend Guaranteed
*Multisend Best Effort
For more information about the load-balancing policies, see Load-Balancing Policies for Clusters.
Number Of Broker s
The maximum number of recipient Brokers in a cluster.
This field is displayed only if you have selected Multisend Best Effort cluster policy. For more information, see Editing Cluster Configuration.
Cluster Broker s
List of Broker addresses bound with this cluster connection factory. JMS applications publishing to (or retrieving) documents from JNDI will use these Brokers for failover and load balancing.
Refresh Interval (minutes)
Default: 1440 minutes. After the specified minutes elapse, client applications refresh all connections to update changes made to the connection factory.
Client Group
Client group through which this cluster connection factory connects. The default is "JMSClient."
Use SSL Encryption
Whether traffic to connections made from this connection factory will be encrypted. The default is Yes.
*If set to Yes, all traffic to the Broker on this connection will be encrypted.
*If set to No, the connection will be authenticated but no data will be encrypted.
Use Remote SSL Files
Use the file paths for certificates as specified.
If this setting is not selected, My webMethods uses the local, uploaded keystore and trust store names and converts them to file paths.
SSL Keystore
Absolute path and file name of the client keystore file that contains the certificate information for SSL connections.
For more information about SSL keystores, see Keystore File.
SSL Keystore Type
File type of the client keystore, which is PKCS12.
SSL Truststore
Absolute path and file name of the truststore file containing the trusted root for the SSL certificate stored in the specified keystore.
For more information about SSL truststores, see Truststore File.
SSL Truststore Type
File type of the truststore certificate file, which is JKS.
Marshall In Class Name
Fully qualified Java class name of the inbound marshaller if the JMS marshalling feature was used.
Note:
Marshalling is an advanced feature that is used to connect to versions of Broker/JMS clients earlier than 6.5. For more information, see the "JMS Marshalling" appendix in the webMethods Broker Messaging Programmer’s Guide.
Marshall Out Class Name
Fully qualified Java class name of the outbound marshaller if the JMS marshalling feature was used.
Marshalling is an advanced feature that is used to connect to versions of Broker/JMS clients earlier than 6.5. For more information, see the "JMS Marshalling" appendix in the webMethods Broker Messaging Programmer’s Guide.