Broker 10.15 | webMethods Broker Documentation | Administering webMethods Broker | Using My webMethods with JMS | Managing Connection Factories | Adding Connection Factories
 
Adding Connection Factories
Use the following procedure to add a connection factory.
*To add a connection factory
1. In My webMethods: Messaging > Naming Directories > Connection Factories.
2. On the Connection Factories List tab, click Add Connection Factory.
3. Complete the settings for the following on the Add Connection Factory page:
In this field...
Select or type...
Lookup Name
The name of the JNDI directory in which to bind this connection factory.
Provider
The name of an existing JNDI naming directory from the list.
Connection Factory Type
Connection Factory Client ID
Optional. The base client ID for connections created by this connection factory.
*If you specify a client ID, the connection factory derives a client ID from this value each time a connection is established.
*If you do not specify a client ID, the connection factory assigns a unique client ID when a connection is established.
Broker Server
The 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 an existing client group or a new client group for this connection factory. If a new client group name is entered, that client group is created.
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
The fully qualified Java class name of the inbound marshaller if the JMS marshalling feature is used; otherwise, leave blank.
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
The fully qualified Java class name of the outbound marshaller if the JMS marshalling feature is used; otherwise, leave blank.
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.
4. Click OK.