Bind CompositeConnectionFactory
Adds a Composite ConnectionFactory definition into a JNDI context.
Syntax
bind { cm_cf | CompositeConnectionFactory } lookup-name [ with
clusterConnectionFactories=(connection-factory-name)+
[ clusterRefreshInterval=cluster-refresh-interval ]
[ clusterPolicy=cluster-policy-name ]
[ useXA={ true | false } ]
[ marshallInClassName=class-name ]
[ marshallOutClassName=class-name ] ]
The command syntax has these parts:
Part | Description |
lookup-name | Required. The name used to look up this connection factory in the JNDI directory. |
clusterConnectionFactories | Required.List of cluster connection factory names that are part of the composite connection factory. These cluster connection factories must be created prior to binding them to a composite connection factory. The list of cluster connection factory names is specified by separating the cluster connection factory names with a comma (,). For example, clusterConnectionFactories=clusterFactory_01,
clusterFactory_02 |
clusterRefreshInterval | Optional.The cluster refresh interval in minutes. JMS client applications can use this interval to refresh the cluster connection factory, and choose to reconnect if the connection factory has changed. The webMethods API for JMS will not automatically refresh the connection factories or Broker connections. The value of this property must be an integer greater than 0. The default value is 1440. |
clusterPolicy | Optional.The name of the composite cluster routing policy. Specify any of the following policies:  ROUND_ROBIN (the default value) STICKY RANDOM MULTISEND_BEST_EFFORT MULTISEND_GUARANTEED |
useXA | Optional. Whether XA transactions are allowed with this composite connection factory. The default value is true, which means XA transactions are allowed. If you are not using the specified composite connection factory with an application server, specifying false saves some of the overhead associated with support for composite XA connection factories. This parameter is for JMS only. If the connection factory is for a C# client, this parameter is ignored. |
marshalInClassName | Optional. Class name of the inbound marshaller (JMS clients only). |
marshalOutClassName | Optional. Class name of the outbound marshaller (JMS clients only). |
Remarks
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.
Example
bind CompositeConnectionFactory TEST_CONNECTION_FACTORY with
clusterConnectionFactories=clusterFactory_01,clusterFactory_02
clusterPolicy=ROUND_ROBIN
clusterRefreshInterval=640
useXA=false
show TEST_CONNECTION_FACTORY
TEST_CONNECTION_FACTORY : com.webmethods.jms.impl.WmConnectionFactoryImpl
clusterConnectionFactories: clusterFactory_01,clusterFactory_02
clusterRefreshInterval: 640
clusterPolicy: ROUND_ROBIN
useXA: false
marshalInClassName: <not specified>
marshalOutClassName: <not specified>
Cluster Factories: 2
Cluster Factory [0]: clusterFactory_01
clusterName: cluster_01
clusterBrokers: broker_01@hostname:port,broker_02@hostname:port
includeAllBrokers: false
clusterRefreshInterval: 144
clusterPolicy: ROUND_ROBIN
application: JMS
clientGroup: JMSClient
clientId: <not specified>
sslKeystore: <not specified>
sslTruststore: <not specified>
sslKeystoreType: <not specified>
sslTruststoreType: <not specified>
sslEncrypted: false
useXA: true
marshalInClassName: <not specified>
marshalOutClassName: <not specified>
Cluster Factory [1]: clusterFactory_02
clusterName: cluster_01
clusterBrokers: broker_03@hostname:port,broker_04@hostname:port
includeAllBrokers: false
clusterRefreshInterval: 144
clusterPolicy: ROUND_ROBIN
application: JMS
clientGroup: JMSClient
clientId: <not specified>
sslKeystore: <not specified>
sslTruststore: <not specified>
sslKeystoreType: <not specified>
sslTruststoreType: <not specified>
sslEncrypted: false
useXA: true
marshalInClassName: <not specified>
marshalOutClassName: <not specified>
Related Commands