Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

QAnywhere new features

• Failover servers  The QAnywhere agent now can take a list of MobiLink server connection protocol options rather than just one.

  See Setting up a failover mechanism.

• Emulator support  QAnywhere client applications on the Pocket PC 2002 and Pocket PC 2003 now support x86 emulators. Only "scheduled" policy for the QAnywhere Agent is supported on these emulators.

• New RDBMSs supported as server message stores  All supported MobiLink consolidated databases can now be used in QAnywhere applications as server message stores: Adaptive Server Anywhere, Adaptive Server Enterprise, Microsoft SQL Server, Oracle, and DB2.

• QAnywhere .NET client library for the .NET Compact Framework now supports message listeners.   QAnywhere .NET client library for the .NET Compact Framework now supports message listeners.

• Remote message store properties now synchronized  When you set remote message store properties, those properties are now synchronized to the server message store so that they can be used in transmission rules.

• Enhanced message store properties  The ias_Network property now contains fields you can use to access detailed network information.

  See Client message store properties.
  In addition, you can now create customized message store properties.

• Rules for deleting messages  You can now specify transmission rules for the persistence of messages in the message stores. You can delete messages on the client side and server side.

  See Message transmission rules.

• Connection string  To start the local message store, you can now specify a connection string with the qaagent -c option. This allows you to use Adaptive Server Anywhere connection string parameters.

  See -c option.

• Quiet mode  The QAnywhere Agent now supports two flavors of quiet mode, which can avoid problems on some Windows CE devices.

  See -q option and -qi option.

• QAstop utility  When you start the QAnywhere Agent in quiet mode with the -qi option, you must use the new qastop utility to stop it.

  See -qi option.

• Enhanced verbosity  You can now specify output log file names with the -o or -ot option, and regulate the size of the output files with the -os and -ot options. In addition, the -v option replaces the old -verbose option. With -v, you have greater control over logging output.

  See:
  • -o option
  • -ot option
  • -on option
  • -os option
  • -v option

• Initialize database for use as a remote message store  You can use the new qaagent -si option to set up a remote message store. See -si option.

• Upgrade from version 9.0.1  The QAnywhere Agent has a new option, -su, that upgrades a remote message store from version 9.0.1 to 9.0.2.

  See -su option.

All QAnywhere MobiLink system tables are now owned by ml_qa_user_group. Previously, they were owned by DBO.

Two new MobiLink system tables have been added. See:

• ml_qa_delivery

• ml_qa_delivery_client

There are changes to the schema of several MobiLink system tables. See:

• ml_qa_global_props

• ml_qa_global_props_client

• ml_qa_repository

• ml_qa_repository_client

• ml_qa_repository_props

• ml_qa_repository_client

The following MobiLink system tables are not generated for 9.0.2 clients:

• ml_qa_repository_staging_client

• ml_qa_status_staging_client

The following MobiLink system table is not generated for 9.0.2 servers:

• ml_qa_repository_content