Configuring user access for the stand-alone database logger
In a test environment, you can add any new privileges needed to your normal user account. In a production environment, you are recommended to create a new user with the minimum permissions required to do the job.
Before you begin
- If you are using DB2® on Windows ensure that the MUSR_MQADMIN user is in the DB2USERS group.
About this task
The number and type of user accounts you need to run the
database logger depend on the number of systems you use. You can install
the database logger, WebSphere MQ
and your database on a single system, or across two systems. The database
logger must be on the same system as WebSphere MQ. The components can be installed
in the following topologies:
- Database logger, WebSphere MQ and the database all on the same system
- You can define a single operating system user for use with all three components. This is a suitable configuration for the stand-alone database logger. The database logger uses Bindings mode to connect to WebSphere MQ and a native connection to connect to the database.
- Database logger and WebSphere MQ on one system, the database on a separate system
- You create two users for this configuration: an operating system user on the system running the database logger, and a operating system user with remote access to the database on the database server. This is a suitable configuration for the stand-alone database logger using a remote database. The database logger uses Bindings mode to connect to WebSphere MQ and a client connection to access the database.
As an example, the rest of these instructions assume that the user is called ftelog, but you can use any user name. Configure the user's permissions as follows: