...
Property name | Description | Required | Default Value | ||
|---|---|---|---|---|---|
| TransportLayer.TransportAdapters | Comma delimited list of TA. Separate configuration section for each listed client should be specified. JMSTA should be specified here. | Y | |||
| TransportLayer.JMSTA.Description | TA Description | Y | JMS Transport Adaptor | ||
| TransportLayer.JMSTA.DllName | TA library file name. In case this parameter is not specified, the TransportLayer.JMSTA.AdapterId is applied to define the adapter's library by ID | Y | |||
| TransportLayer.JMSTA.AdapterId | The parameter to define the adapter's library by ID. In case this parameter is not specified, or TransportLayer.JMSTA.DllName parameter is specified too, the TransportLayer.JMSTA.DllName is applied
Required value: JMS | N | |||
| TransportLayer.JMSTA.JVMOptionsFile | TA configuration file name | Y | |||
| TransportLayer.JMSTA.AllowRejectMessages | When option is true, JMS rejects messages if unable to send to the MQ or error was fired. False by default. | N | false | ||
| TransportLayer.JMSTA.AllowRepeatedStatusNotification | When option is true, JMS allows to call onLogout() callback if no onLogon() callback was called. False by default. | N | false | ||
| TransportLayer.JMSTA.ConnectionNames | Comma delimited list of TA connections. Separate configuration section for each listed connection should be specified | Y | |||
| TransportLayer.JMSTA.ClientNames | Comma delimited list of TA clients. Separate configuration section for each listed client should be specified | Y | |||
| TransportLayer.JMSTA.FIXVersion | In every session, FIX messages use a particular version of the FIX protocol. Use this parameter to set the version of the FIX protocol for a given session. Acceptable values: FIX40, FIX41, FIX42, FIX43, FIX44, FIX50, FIX50SP1, FIX50SP2. | N | FIX44 | ||
| Connections parameters | |||||
| TransportLayer.JMSTA.Connection.[ConnectionName].InitialContextFactory | JNDI option. The fully qualified class name of the factory class that will create the initial context. An initial context is the starting point for naming operations. | C, required if JNDI mechanism is used | |||
| TransportLayer.JMSTA.Connection.[ConnectionName].ProviderURI | JMS provider URI that defines where the Connection that is created is to connect to as well as the protocol that should be used, for example TCP/IP. Additionally configuration information can be encoded in the URI. | Y | |||
| TransportLayer.JMSTA.Connection.[ConnectionName].User | User name | Y | |||
| TransportLayer.JMSTA.Connection.[ConnectionName].Password | User Password | Y | |||
| TransportLayer.JMSTA.Connection.[ConnectionName].ConnectionFactory | JNDI option. Connection factory object name in the JNDI object store. | C, required if JNDI mechanism is used | |||
| TransportLayer.JMSTA.Connection.[ConnectionName].Reconnect | Enables or disables reconnect procedure for connection restore | N | false | ||
| TransportLayer.JMSTA.Connection.[ConnectionName].ReconnectTries | Number of reconnect tries or -1 for an infinite number of attempts | N | 3 | ||
| TransportLayer.JMSTA.Connection.[ConnectionName].ReconnectInterval | Fixed interval in milliseconds between reconnection attempts | N | 2000 | ||
| Clients parameters | |||||
| TransportLayer.JMSTA.Client.[ClientName].ConnectionName | Name of primary connection used by client. Connection should be registered in ConnectionNames enumeration and has all required parameters | Y | |||
| TransportLayer.JMSTA.Client.[ClientName].StorageDir | Directory where persistence file is stored in case the communication problem | Y, if persistent mode is enabled | |||
| TransportLayer.JMSTA.Client.[ClientName].SessionType | Session type:
| Y | |||
| TransportLayer.JMSTA.Client.[ClientName].MessagingMode | Session messaging mode: Queue - Point-To-Point. Each message is addressed to a specific queue, and receiving clients extract messages from the queue(s) established to hold their messages. Queues retain all messages sent to them until the messages are consumed or until the messages expire. Topic - Publish/Subscribe. In a pub/sub product or application, clients address messages to a topic. Publishers and subscribers are generally anonymous and may dynamically publish or subscribe to the content hierarchy. The system takes care of distributing the messages arriving from a topic’s multiple publishers to its multiple subscribers. Topics retain messages only as long as it takes to distribute them to current subscribers. | Y | |||
| TransportLayer.JMSTA.Client.[ClientName].DestinationURI | URI of session destination (Queue name) | Y | |||
| TransportLayer.JMSTA.Client.[ClientName].DeliveryMode | Specifies whether sent messages are lost if the JMS provider fails. Persist - instructs the JMS provider to take extra care to ensure that a message is not lost in transit in case of a JMS provider failure. A message sent with this delivery mode is logged to stable storage when it is sent. NoPersist - does not require the JMS provider to store the message or otherwise guarantee that it is not lost if the provider fails. NOTE: used only for Producer sessions. | N | Persist | ||
| TransportLayer.JMSTA.Client.[ClientName].TimeToLive | This value defines a message expiration time (in milliseconds) that is the sum of the message's time-to-live and the GMT when it is sent (for transacted sends, this is the time the client sends the message, not the time the transaction is committed). Setting parameter value to "0" will lead to infinite TTL. | Y | 3000 | ||
| TransportLayer.JMSTA.Client.[ClientName].SessionAckMode | Defines mode in which the Session will acknowledge the messages that it receives and dispatches. Auto - With this acknowledgement mode, the session automatically acknowledges a client's receipt of a message either when the session has successfully returned from a call to receive or when the message listener the session has called to process the message successfully returns. Client - With this acknowledgement mode, the client acknowledges a consumed message by calling the message's acknowledge method. Acknowledging a consumed message acknowledges all messages that the session has consumed. When client acknowledgement mode is used, a client may build up a large number of unacknowledged messages while attempting to process them. DupsOk - This acknowledgement mode instructs the session to lazily acknowledge the delivery of messages. This is likely to result in the delivery of some duplicate messages if the JMS provider fails, so it should only be used by consumers that can tolerate duplicate messages. Use of this mode can reduce session overhead by minimizing the work the session does to prevent duplicates. | N | Auto | ||
| TransportLayer.JMSTA.Client.[ClientName].MessageType | JMS Message type used for this session. Bytes - A stream of interpreted bytes. This message type is for literally encoding a body to match an existing message format. Text - Data is stored as a string. This message type is useful for exchanging simple text messages and for more complex character data, such as XML documents. Custom - The ability to use your own message type. This message type is useful for adaptation to already existing systems. For this message type property TransportLayer.JMSTA.Client.[ClientName].CustomMessageType is required. | Y | |||
| TransportLayer.JMSTA.Client.[ClientName].CustomMessageType | Class of custom message type implementation. This should be the implementation of one of the interfaces: NOTE: used only for Custom message type. | Y, if MessageType is Custom | |||
| TransportLayer.JMSTA.Client.[ClientName].Transacted | Sending/consuming of messages in the session is transacted. true - transacted. false - not transacted. The value is used by default. | N | false | ||
| TransportLayer.JMSTA.Client.[ClientName].TransactionBatchSize | Max number of message for one transaction. Take from queue the available number of message but no more than that specified in this property. NOTE: used only if transacted is enabled. | N | 20 | ||
| TransportLayer.JMSTA.Client.[ClientName].QueueSize | Max number of messages in queue. Message is queued until successfully sent. Waiting for space to become available if the queue is full. | N | 100 | ||
| TransportLayer.JMSTA.Client.[ClientName].QueuePersistent | Store messages in the file until they are committed which allows restoring and sending messages after a sudden application shutdown. true – to save messages in the file storage (persistent queue) with parallel saving in memory. false – to save messages in the in-memory queue. This approach is faster but less safe since some messages may be lost after restart.
| N | false | ||
| TransportLayer.JMSTA.Client.[ClientName].QueueNormalFileSize | After reaching this size, adapter waits when the queue will be empty for to truncate file. File size in Mbytes. NOTE: used only for persistent queue. | N | 10 | ||
| TransportLayer.JMSTA.Client.[ClientName].QueueMaxFileSize | After reaching this size, adapter truncate the file and overwrites the messages that are queued. File size in Mbytes. NOTE: used only for persistent queue. | N | 50 | ||
| TransportLayer.JMSTA.Client.[ClientName].DurableSubscription | Durable topic subscriptions allows receiving messages published while the subscriber is not active. Durable subscriptions offer the reliability of queues to the publish/subscribe message domain. true - Subscription is durable. false - Subscription is not durable. NOTE:
| N | false | ||
| TransportLayer.JMSTA.Client.[ClientName].DurableSubscriptionName | Durable subscription name. | Y, required if DurableSubscription set to true. | |||
| TransportLayer.JMSTA.Client.[ClientName].ConnectionsCount | Number of JMS connections. Adaptor will open given amount of connections to JMS server for given session to send simultaneously. NOTE:Please pay attention that if a number of connection is greater then 1 that there is no guaranty that messages will be placed to JMS in the same order they were received by adapter. | N | 1 | ||
| TransportLayer.JMSTA.Client.[ClientName].ThreadsPerConnection | Number of threads per one JMS connection. Adaptor will open given amount of JMS sessions for each JMS connection to send simultaneously. NOTE: Please pay attention that if a number of thread per connection is greater then 1 that there is no guaranty that messages will be placed to JMS in the same order they were received by adapter. | N | 1 | ||
...
FIXEdge C++ provides Start operation for Disconnected JMS TA sessions and Stop operation for Connecting and Running JMS TA sessions on request from the subscribed monitoring application.
Please refer to the Transport adaptor operations for FIXEdge C++ page for additional details about Start and Stop operations.
...