Broker 10.5 | webMethods Broker Documentation | webMethods Broker Messaging Programmer's Guide | webMethods Messaging Administration | JMSAdmin Command Reference | JMSAdmin Command Descriptions | Bind TopicConnectionFactory
Bind TopicConnectionFactory
Adds a TopicConnectionFactory definition into a given context (JMS clients only).
bind { tcf | TopicConnectionFactory } lookup-name [ with ]
[ { brokerHost | bh }=host[:port] ]
[ { brokerName | bn }=broker-name ]
[ clientId=client-id ]
[ application=application-name ]
[ group=client-group-name ]
[ sslKeystore=filename ]
[ sslPassword=password ]
[ sslTruststore=filename ]
[ sslEncrypted={ true | false } ]
[ useXA={ true | false } ]
[ marshallInClassName=class-name ]
[ marshallOutClassName=class-name ] ]
The command syntax has these parts:
Required. The name used to look up this connection factory in the JNDI directory.
*Optional.The host part is the host name of the Broker Server on which the Broker resides. The default value is localhost.
*Optional.The port part is the port number of the Broker Server on which the Broker resides. The default value is 6849.
Optional. The name of the Broker. If you do not specify a Broker name, JMSAdmin uses the default Broker on the specified Broker Server.
Optional. The base client ID for connections created by this factory.
*If you specify a client ID, it must be unique. This ID is assigned to all the connections to the Brokers in the cluster.
*If you do not specify a client ID, the connection factory assigns a unique ID when a connection is established.
Optional. The name of the application stored as part of the application's Broker client state. The application is displayed by JMSAdmin.
Optional. The client group name that clients created from this connection factory will use. Note that the bind command does not create the client group; you must create a client group explicitly using the create group command. The default client-group-name is JMSClient.
Optional. The fully qualified path of the file containing the SSL certificate that JMSAdmin will use on SSL connections made from this connection factory.
Optional. The password for the keystore file that JMSAdmin is to use when connecting to the Broker using SSL.
Optional. The file that holds the trusted root (CA public key) that JMSAdmin will use to connect to an SSL-enabled Broker.
Optional. Whether traffic to the Broker on connections made from this connection factory will be encrypted.
*If set to true, all traffic to the Broker on this connection will be encrypted.
*If set to false, the connection will be authenticated but no data will be encrypted.
The default value is false.
Optional. Whether XA transactions are allowed with this connection factory. The default value is true, which means XA transactions are allowed. If you are not using the specified connection factory with an application server, specifying false saves some of the overhead associated with support for XA connection factories.
Optional. Class name of the inbound marshaller.
Optional. Class name of the outbound marshaller.
You can only use the marshalInClassName and marshalOutClassName parameters when implementing the marshalling feature when you use webMethods Broker as a JMS provider. For more information, see JMS Marshalling.
Related Commands
Bind ConnectionFactory
Bind Topic
Modify Topic
Modify TopicConnectionFactory