Collection Contents Index CHAPTER 11.  Administering SQL Remote for Adaptive Server Anywhere Error reporting and handling pdf/chap11.pdf

Data Replication with SQL Remote
   PART 3. SQL Remote Administration
     CHAPTER 11. Administering SQL Remote for Adaptive Server Anywhere       

Running the Message Agent


This section describes how to run the Message Agent for Adaptive Server Anywhere.

For Info     For information on features of the Message Agent that are common to Adaptive Server Anywhere and Adaptive Server Enterprise, see SQL Remote Administration.

Top of page  Starting the Message Agent

The Message Agent has a set of command-line switches that control its behavior. The only command-line switch that is required for the Message Agent to run is the connection parameters switch (-c).

The connection parameters are described in the chapter "Connecting to a Database" in the Adaptive Server Anywhere User's Guide.

Verbose keyword

Short form

Argument

DatabaseFile

DBF

string

DatabaseName

DBN

string

DatabaseSwitches

DBS

string

EngineName

ENG

string

Password

PWD

string

Start

Start

string

Userid

UID

string

Top of page  Running the Message Agent as a service

If you are running the Message Agent in continuous mode (not batch mode), on Windows NT or Windows 95, you may wish to keep the Message Agent running all the time that the server is running.

You can do this by running the Message Agent as a service under Windows NT or Windows 95. A service for Windows NT can be configured to keep running even when the current user logs out, and to start as soon as the operating system is started.

For Info     For a full description of running programs as services, see the chapter "Running the Database Server" in the Adaptive Server Anywhere User's Guide.

Top of page  The Message Agent and replication security

In the tutorials in the previous chapter, the Message Agent was run using a user ID with DBA permissions. The operations in the messages are carried out from the user ID specified in the Message Agent connection string; by using the user ID DBA, you can be sure that the user has permissions to make all the changes.

In many situations, distributing the DBA user ID and password to all remote database users is an unacceptable practice for security and data privacy reasons. SQL Remote provides a solution that enables the Message Agent to have full access to the database in order to make any changes contained in the messages without creating security problems.

A special permission, REMOTE DBA, has the following properties:

Using REMOTE DBA permission 

A suggested practice is to grant REMOTE DBA authority at the consolidated database to the publisher and to each remote user. When the remote database is extracted, the remote user becomes the publisher of the remote database, and is granted the same permissions they were granted on the consolidated database, including the REMOTE DBA authority which enables them to use this user ID in the Message Agent connection string. Adopting this procedure means that there are no extra user IDs to administer, and each remote user needs to know only one user ID to connect to the database, whether from the Message Agent (which then has full DBA authority) or from any other client application (in which case the REMOTE DBA authority grants them no extra permissions).

Granting REMOTE DBA permission 

You can grant REMOTE DBA permissions to a user ID named dbremote as follows:

GRANT REMOTE DBA
TO dbremote
IDENTIFIED BY dbremote

In Adaptive Server Anywhere, you can add the REMOTE DBA authority to a remote user by checking the appropriate option in the New Remote User Wizard.

Top of page  

Collection Contents Index CHAPTER 11.  Administering SQL Remote for Adaptive Server Anywhere Error reporting and handling pdf/chap11.pdf