Required roles and permissions for installation
The TrueSight Middleware and Transaction Monitor (TMTM) installation requires that user accounts be set up on the database, services, and agent servers. These user credentials are used throughout the installation process and should be created before you start the installation itself.
Note that agent server user accounts need not be set up until you are ready to distribute and install the agent and extensions.
Required permissions on the TMTM database
TMTM requires the following permissions to be granted to the TMTM database:
- SYSMAINT instance level authority to allow:
- SELECT ON sysibmadm.bp_hitratio
- SELECT ON sysibmadm.applications
- SELECT ON sysibmadm.dbcfg
- SELECT ON syscat.tables
- Authority to execute (on all tables within the TMTM schema)
- TRUNCATE TABLE IMMEDIATE
- ALTER TABLE
- In addition, functions and procedures for reporting are created in the schema by the create script which must be executable by the TMTM database user.
- If history table partitioning is required, authority to manage partitions is necessary:
- ALTER TABLE ATTACH PARTITION
- ALTER TABLE ADD PARTITON
- ALTER TABLE DETACH PARTITION
- SET INTEGRITY
- DROP TABLE
- Role 'select_catalog_role'
- SELECT ANY DICTIONARY
- VIEW SERVER STATE
- VIEW DATABASE STATE
Consult your DBA to grant these authorities. Contact BMC Support for a DB2 authority verification script if you require authority verification before installing the product.
Changes to apply to the TMTM database
The following changes need to be made to the TMTM database. This applies to DB2 for LUW users only. The requirements are:
- A system temporary tablespace with a page size of 16K or greater must exist. This requires a buffer pool of the same page size to support it.
- Command examples:
CREATE BUFFERPOOL QPTEMP32BP PAGESIZE 32K;
CREATE SYSTEM TEMPORARY TABLESPACE QPTEMP32 PAGESIZE 32K BUFFERPOOL QPTEMP32BP;
ALTER BUFFERPOOL QPTEMP32BP IMMEDIATE SIZE 1000;
- Command examples:
- The Database configuration parameter "currently committed" (cur_commit) must be set to DISABLED/OFF.
- Command example:
db2 update db cfg for <db_alias> using cur_commit off immediate
- The status of curr_commit can be known by issuing a "db2 get db cfg" command when connected to the database.
- Command example:
Consult your DBA to ensure these requirements are met; contact BMC Support with any concerns.
Database user accounts
|DB2||Because DB2 uses operating system authentication, create an operating system user account on the database server through which DB2 is accessed by TMTM. |
This information applies equally to DB2 on Windows, UNIX, and z/OS.
The user is an operating system user and should be identical to the database schema name under which the product objects are created. If this is not possible, aliasing can be used, as long as the user has the ability to perform all actions as indicated in the previous section. If your installation requires access through aliasing, contact BMC Support.
Create an Oracle user under which the TMTM objects are created.
An Oracle schema is a collection of database objects, including logical structures such as tables, views, stored procedures, indexes, and PL/SQL packages. The oracle user id must match the schema name. Use of synonyms to provide access to database objects is not supported.
|Microsoft SQL Server|
TMTM services and clients (the Management Console) must have access to the database using the account you create in this step.
Both Windows Authentication and SQL Server Authentication are supported. If SQL Server Authentication is chosen, then a SQL Server login must be created; create a SQL Server login and database user for use by TMTM, and then map the login to the database user. To set up Windows Authentication, see Connecting services and agents with a secure tunnel.
Use of aliases is not supported.