User names and passwords Reference TCP/IP port considerations

You must set user names (sometimes referred to as user IDs) and passwords for Multiple Device Manager (MDM) and its components during installation and configuration. This topic describes various user names, when and how they are set, and when they are used.

Multiple Device Manager

The MDM and Performance Manager installation programs request that you enter this user name and password. The user name must be registered with the operating system. On Windows, the user name must be part of the DirAdmin and DirSystem groups, which are the IBM Director Group group names. On Linux, the user name must be part of the diradmin and dirsystem groups, which are the Linux IBM Director Group names. You can change the MDM user name after installation using the Configure MDM task in the IBM Director Console. The MDM user name must be treated as a universal user name to accomplish connectivity with MDM managed devices. You must put this same user name and password on your CIM Agents in your enterprise.

CIM Agent for IBM TotalStorage Enterprise Storage Server (ESS)

The CIM Agent for ESS provides MDM with access to the ESSs. You must customize the CIM Agents in your enterprise to accept the MDM user name and password. See the setuser command for CIM Agent for ESS.

CIM Agent for IBM TotalStorage SAN Volume Controller

The CIM Agent for SAN Volume Controller is part of the SAN Volume Controller Console and provides MDM with access to SAN Volume Controller clusters. You must customize the CIM Agents in your enterprise to accept the MDM user name and password. See the SAN Volume Controller Console user assistance to change passwords and create new user names for the SAN Volume Controller Console.

User that is installing MDM

The logged-on user that is performing the installation is the user account that is active during the installation of MDM and Performance Manager. This individual must have certain user rights that might not always be assigned to the administrators group. During MDM installation, MDM detects the missing user rights, and adds them to the account when the user accepts this option.

IBM DB2 Universal Database

When you install DB2 Universal Database, you provide a user name string and password. If the user name does not exist on the operating system, DB2 installation creates it for you. The DB2 services run under the log-on properties of the user name. If you change the password, you must correct the services log-on properties for DB2. You need the DB2 user name and password when you are installing the following products:

IBM Director

The IBM Director installation program requires that you enter the IBM Director user name and password. The IBM Director services run under the log-on properties of the user name that you provide. If you change the password, you must correct the services log-on properties for the IBM Director. The IBM Director user name and password are also used to log on to the IBM Director Console. For Windows, any valid user names that are defined within the DirAdmin or DirSuper groups on the system where the IBM Director server is installed have access to the IBM Director and MDM Console functionality. For Linux, any valid user names that are defined within the diradmin or dirsuper groups on the system where the IBM Director server is installed have access to the IBM Director and MDM Console functionality.

IBM WebSphere Application Server

For Windows, the WebSphere Application Server services run under the log-on properties of the user name that you provide. The MDM installation requests that you enter this user name. A new user name is created on the operating system if it does not exist. To avoid WebSphere Application Server user name restrictions, enter a user name with eight or less characters and avoid non-alphabetic characters and blanks. If you change the password, you must correct the services log-on properties for the WebSphere Application Server.

For Linux, the WebSphere Application Server services run under root.

If WebSphere Application Server was installed as part of your MDM installation, the WebSphere Application Server superuser user ID and password are the same as the MDM superuser ID and password. To stop WebSphere Application Server, you must include the superuser ID and password in the stopServer command. To log onto the WebSphere Application Server Administration Console, you must use the MDM superuser user ID and password.

Performance Manager

When you create a performance data-collection task for a storage device, some devices require a user name and password. User names and passwords are required for a SAN Volume Controller in the following situations:

(C) Copyright International Business Machines Corporation 2004