Setting up the client message store

 To create a client message store
  1. Create a SQL Anywhere or UltraLite database.

    See Creating a SQL Anywhere database.

  2. Initialize each client message store by running the QAnywhere Agent or the QAnywhere UltraLite Agent with the following options:

    • -c option   to specify a connection string to the database you just created.

      See -c qaagent option.

    • -si option   to initialize the database. The -si option creates a default database user and password. The agent shuts down after initializing the database.

      When you initialize QAnywhere by running qaagent with the -si option, the QAnywhere Agent creates client system tables that are required for QAnywhere messaging. QAnywhere also uses server system tables. These are created when you install MobiLink setup. All QAnywhere system table names begin ml_qa_ and cannot be altered.

      See -si qaagent option.

    • -id option   optionally, if you want to pre-assign a client message store ID.

      See Creating client message store IDs and -id qaagent option.

    • -mu option   optionally, if you want to create a user name to use for authentication with the MobiLink server. If you do not use -mu at this point, you can specify it any time you start the QAnywhere Agent and the name is created if it does not already exist.

  3. If you used the -mu option to create a user name, you need to add the name to the server message store. This can be done automatically using the mlsrv12 -zu+ option, or can be done in other ways.

    See Registering QAnywhere client user names.

  4. Change the default passwords and take other steps to ensure that the client message store is secure.

    See Creating a secure client message store.

You can also upgrade a client message store that was created in a previous version of QAnywhere.

See -su qaagent option and -sur qaagent option.

Note

The easiest way to create and maintain your client message store is in Sybase Central. From the QAnywhere 12 plug-in task pane, choose Client Message Store.

 Creating client message store IDs
 Transaction logs
 Protecting your client message stores
 Example of creating a client message store