The following options are available on qconnector operations:
Mandatory. This specifies the name of the QueueConnectionFactory class in the JNDI namespace.
Queue connections are not instantiated directly but are instead created by connection factories. The connection factories are stored in the JNDI namespace of the application server.
Mandatory. This specifies the JNDI name of the queue onto which outgoing messages are placed.
This is only relevant for operations that have a return value. The return value is obtained by receiving a response JMS message from the recipient and this timeout value is used to ensure that the application does not wait indefinitely for the response.
Default value: 30 seconds.
This is only relevant for operations that have a return value. Specifies the JNDI name of the queue from which the response message should be taken.
BytesMessage or TextMessage. This allows you to specify whether a JMS BytesMessage or TextMessage is sent/received by the connector. By default the JMS connectors send and receive a JMS BytesMessage containing the bytes of a string representation of the struct parameters. If the system(s) being communicated with use a different character encoding, then these bytes may not be correctly translated by the other systems. In this case - provided the message doesn't contain any binary data - a JMS TextMessage can be used to ensure that the message is correctly translated by the other systems.
Specifies the name of the character encoding to use when converting the string representation of a struct to a JMS BytesMessage, and vice versa. If this option is not specified then the default local system character encoding is used. (Usually 'Cp1252' for Microsoft Windows, 'Cp1046' for EBCDIC on IBM® z/OS® , etc.) This enables you to ensure that the character encoding used for the message matches the character encoding of the other system being communicated with.
This option is not relevant if TextMessage is used.