Broker 10.5 | webMethods Broker Documentation | Administering webMethods Broker | Using My webMethods with JMS | Managing Connection Factories | Viewing the Detailed Information About Connection Factories
 
Viewing the Detailed Information About Connection Factories
Use the following procedure to view detailed information about a connection factory.
*To view detailed information about a connection factory
1. Perform the steps listed in Viewing the List of Connection Factories.
Note:
The information for a cluster connection factory, used for the load balancing and client-side failover features, is different from that of non-cluster connection factories. For information about cluster connection factories, see Managing Cluster Connection Factories.
2. Under Lookup Name, click the 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 to which this connection factory is bound.
Provider
Name of the JNDI provider supporting this connection factory.
Connection Factory Type
For descriptions of each 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.
Broker Server
Name and port number of the controlling Broker Server.
Broker
Select a Broker address from the list.
This address is stored with the connection factory object so that JMS applications retrieving the object from JNDI connect to the correct Broker.
Client Group
The name of the client group through which this connection factory connects.
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. You use the local option only if the file path is accessible to the client applications while establishing the connection to JNDI.
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.
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.