GreyTower Connector Parameters
Posted by William Brant on Mon, Apr 18, 2011 @ 07:45 PM
Module Options
GreyTower Module Options
| Options/Parameters | Description |
| Driver Module Name: |
com.novell.nds.dirxml.driver.JMS.JMSDirXMLDriverShim |
| Authentication |
Authentication ID The user name to authenticate against the JMS provider installation. |
| Authentication Context |
An optional directory context of the authentication object. |
| Application Password |
The password used in conjunction with the Authentication ID. |
Driver Settings
| Options/Parameters | Description |
| Queue Manager |
The name of a queue manager (Specific to IBMS WebsphereMQ Product). |
| Message Broker |
The name of message broker (Specific to IBMS WebsphereMQ Product). this field must be filled in with the element Message Broker if you want to send or receive using topics. |
| Port |
This element is used only for connecting to JMS Server Installation on non standard/ Non-default ports. |
| Oracle SID |
Used only when connecting to Oracle Advanced Queuing. The element represents the Oracle SID Identifier.. |
| Oracle-Schema |
Used only when connecting to Oracle Advanced Queuing. This element is used to specify the schema tag the queues reside under. |
| OracleQueueTable |
Used only when connecting to Oracle Advanced Queuing. This element represents the actual queue table name that will hold the JMS messages. |
| JMS Client ID |
The JMS Client identifier used to connect to a queue or topic. If left blank, the shim generates a random JMS Client ID. |
| Vendor |
The JMS Vendor Implementation.
|
Publisher Channel Options
| Options/Parameters | Description |
| Topic Receiver |
A JMS queue to receive XML formatted DirXML commands. |
| Queue Receiver |
The name of message broker (Specific to IBMS WebsphereMQ Product). this field must be filled in with the element Message Broker if you want to send or receive using topics. |
| Query Queue |
The queue to be used to query the remote application via JMS. |
| Query Reply Queue |
The queue to be used receive the reply message from the remote application. |
| Query Reply Queue TimeOut |
The number of seconds the Subscriber channel waits for the query reply message from the Remote application. The only valid value is an integer value for seconds. Otherwise, leave it empty for the default value of 10 seconds |
| Audit Queue |
JMS queue to use if the submitted DirXML transaction returned
an error..
|
| Tracking Queue |
JMS queue in which to place a copy of the message that was successfully processed by the DirXML engine. |
| Use Correlation IDs |
Whether to append a correlation identifier to both the trackingand audit queue Messages. |
| Performance Queue |
A JMS queue in which to place the Performance XML document |
| Reflexive Acknowledgement Queue |
The JMS queue in which to place the reflexive acknowledgement
messages
|
| Reflexive Acknowledgement Header |
The header to retrieve from the originally submitted message to place in the CorrelationID property of the reflexive acknowledgement message |
| Message Selectors |
A message selector uses message properties and headers as criteria in conditional expressions. These expressions use boolean logic to declare which messages should be delivered to a clientto retrieve from the originally submitted message to place in the CorrelationID property of the reflexive acknowledgement message |
Subscriber Channel Options
| Options/Parameters | Description |
| Queue Sender |
The name of the queue to send DirXML messages |
| Query Queue |
The queue used to query the remote application via JMS |
| Query Reply Queue |
The queue used to receive the reply message from the remote applicationS |
| Query Reply Queue Timeout |
The number of seconds the Subscriber channel waits for the query reply message from the JMS application. This value has no effect when enabled with pub/sub messaging. The only valid value is an integer value for seconds. Otherwise, leave it empty for the default value of 10 seconds |
| Topic Sender |
The topic to publish NDS event information to |
| Client Mode |
The mode or style to use in placing messages on a queue or topic. The valid styles are WebSphere MQ native message or JMS Messages (The only valid values are blank or MQ) |
| Byte Messaging |
Used to send a message containing a stream of uninterrupted bytes. The receiver of the message is responsible for the interpretation of the bytes. This should only be used if DirXML needs to exchange non-text messages with your application. Input True for sending a byte stream, or leave blank for the default (text ) option |
| JMS Time To Live |
The maximum lifetime for a message. The input is expected to be in milliseconds. If the element is blank, the message has an unlimited lifetime |
| JMS Priority |
The priority of the message. Valid values are from 0 through 9. If the element is left blank, the message priority defaults to 4. |
| Message Persistence |
The priority of the message. Valid values are from 0 through 9. If the element is left blank, the message priority defaults to 4. |
