The initiator-config element specifies the configuration info for a protocol-specific connection initiator. A connection initiator allows a Coherence*Extend client to connect to a cluster (via a connection acceptor) and use the clustered services offered by the cluster without having to first join the cluster.
The initiator-config element must contain exactly one protocol-specific connection initiator configuration element (either jms-initiator or tcp-initiator).
The following table describes the elements you can define within the initiator-config element.
|<jms-initiator>||Optional||Specifies the configuration info for a connection initiator that connects to the cluster over JMS.|
|<tcp-initiator>||Optional||Specifies the configuration info for a connection initiator that connects to the cluster over TCP/IP.|
|<outgoing-message-handler>||Optional||Specifies the configuration info used by the connection initiator to detect dropped client-to-cluster connections.|
|<use-filters>||Optional||Contains the list of filter
names to be used by this connection initiator.
For example, specifying use-filter as follows
will activate gzip compression for all network messages, which can help substantially with WAN and low-bandwidth networks.
|<serializer>||Optional||Specifies the class configuration info for a Serializer implementation used by the connection initiator to serialize and deserialize user types.
For example, the following configures a ConfigurablePofContext that uses the my-pof-types.xml POF type configuration file to deserialize user types to and from a POF stream: