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] |
In addition, the following qaagent options are no longer required and have been deprecated:
See qaagent utility.
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.
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 Sending a message from a JMS connector to a QAnywhere client.
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.
Discuss this page in DocCommentXchange. Send feedback about this page using email. |
Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1 |