Background information
To monitor your environment, you must first
install the Performance Management server and
supporting components. Review the options and requirements
to help you plan your installation of the Performance Management server.
- What gets installed with the server
- The installation also installs a DB2® server, a Summarization and Pruning agent, and a MongoDB database on the same system as the Performance Management server. The DB2 database stores application definitions and relationship and metric data. The MongoDB database stores threshold event and transaction tracking data.
- Creating DB2 users before you install the Performance Management server
- The Performance Management installation creates a DB2 server on your local system. It creates the DB2 instance users dasusr1, db2apm, and db2fenc1, itmuser, and the groups dasadm1, db2iadm1, db2fadm1. The installation assigns users to groups as follows:
- The dasusr1 user is assigned to the dasadm1 group.
- The db2apm user is assigned to the db2iadm1 and dasadm1 groups.
- The db2fenc1 user is assigned to the db2fadm1 group.
- The itmuser user is assigned to the dasadm1 group.
To adhere to your organization's database server administration policies, you might want to create the DB2 instance users before the DB2 server is installed. When you create each user, you must assign the user to its primary group and update the default user password for each user in the install.properties file. During the Performance Management server installation, when are prompted to install the DB2 database or connect to an existing DB2, select install the DB2 database. For more information, see Creating DB2 users before you connect to a local DB2 server.
- Connecting to a remote DB2 server
- If you have a remote DB2 server, you can use it for the Performance Management server databases rather than installing a DB2 server with the Performance Management server.
The DB2 installer creates the dasuser1 user and the dasadm1 group and assigns the dasuser1 user to the dasadm1 group. You must manually create all other users and groups and assign the users to the appropriate groups. For more information, see Connecting to a remote DB2 server.
- Installing the Performance Management server on a computer system where LDAP authentication is used
- If the system where you plan to install the Performance Management server with a local DB2 server is using an external directory service with LDAP for user authentication, you must update itmuser and DB2 instance user passwords if they are configured in your directory service before you install the Performance Management server. After you install the Performance Management server, you must configure the LDAP security plug-in on the local DB2 server. For details, see Installing on a system using an external directory service.
- Installing MongoDB on a remote system
- For scalability purposes, you can install MongoDB on another system. For more information, see Installing a remote MongoDB.
- Requirements and supported platforms
- You must have root permissions to install and run the Performance Management server. Running the Performance Management server as a non-root user is not supported.
- Review the System requirements and Dependencies topics for the supported platforms and requirements for the Performance Management server.
- Configuring agent and Hybrid Gateway while installing the server
- Before the agents can be installed, the agent installation images must be configured to connect
to the server. If you plan to configure the agent images during installation of the server rather
than at a later time, download the agent images to the same system where the server will be
installed.
The agent images can be mounted on an NFS partition but the images must be accessible using the file system. Do not change the installation image file name for the agents during or after download. If the installation image file name is changed, it is not recognized by image configuration tools and configuration fails. For more information, see Download instructions. - As with agent images, if you plan to configure the Hybrid Gateway image during installation of the server rather than at a later time, you must first download the image to the same system where the server will be installed. For more information, see Download instructions.
- OIDC
- OpenID Connect (OIDC) is a simple identity protocol over OAuth 2.0. OIDC is enabled in Performance Management console. OIDC lets a client application request the identity of the user as an ID token in a standardized, REST-like manner. In addition, the client application can use access tokens to access REST-like Services. A self-signed certificate is created for OIDC during installation. You can configure a self-signed certificate or a CA signed certificate for OIDC, for more information, see Configuring a self-signed certificate for OIDC server, and Configuring a CA-signed certificate for OIDC server.