Configures communication through a message queue using BEA MessageQ as a client.

• RemoteConfig
• RemTrans

Optional description.

 Process priority for the transport process. For future use.

 My queue number that resides on the MQ server. If set to 0 (zero) the queue will
 be allocated dynamically and we will not know in advance what queue number we have (can be
 useful for one-way outgoing communication with no incoming messages). This attribute
 will in this case be updated with the attached queue number.

 MQ group for every outgoing message.
 Dynamic change is possible.

 MQ queue for every outgoing message.
 Dynamic change is possible.

 Scantime in seconds for outgoing RemTrans messages.
 Dynamic change is possible.

 When set, this attribute tells the remote handler not to start
 or restart the process that handles this remote node. If the transport process
 is running while the attribute is set it will terminate. This can be used to force
 a restart of the process.

 This attribute shows how many times the remote handler has restarted the
 transport process that handles this remnode.
 Dynamic change is possible and can be used in order to earn more restarts.

 The restart limit tells the remote handler how many times the transport process
 that handle this remnode can be restarted.
 Dynamic change is possible and can be used in order to earn more restarts.

 The restart time is set by the transport process at startup and therefore
 shows the latest (re)starttime.

 Error counter.

 Type of remnode. Used in the RemoteConfig classgraph.

 Contains the objid for the RemTrans objects for this remnode.
 The objid's are inserted by the remote process.