|
QAnywhere Agent options The following QAnywhere Agent (qaagent) options have been deprecated and replaced.
| Deprecated qaagent option... | Replaced with qaagent option... |
|---|---|
| -agent_id id | -id id |
| -dbauser user | -c "UID=user" |
| -dbeng name | -c "ENG=name" |
| -dbfile filename | -c "DBF=filename" |
| -dbname name | -c "DBN=name" |
| -ek key | -c "DBKEY=key" |
| -password password | -c "PWD=password" |
| -sv | -c "Start={ dbeng9 | dbsrv9 }" |
| -verbose | -v[levels] |
QAnywhere Agent no longer creates the client message store You must now create the message store database yourself before running qaagent. There is a new option, -si, that initializes the database with system objects that are required by QAnywhere.
See Setting up the client message store.QAnywhere messages with an InReplyToID The QAnywhere built-in header InReplyToID is no longer mapped to the JMS property ias_ReplyToAddress. This means that it is no longer copied to JMSCorrelationID.
See Mapping QAnywhere messages on to JMS messages.QAnywhere client library message overhead is reduced The ias_MessageType property is no longer set for regular messages. It is still set for network status and other system messages that are sent to the system queue.