Account prerequisites for custom installations

Before you begin a custom installation, you must have certain account prerequisites in place.

• You must be logged on with an account that owns the IBM® WebSphere® Application Server directories and binary files. The database JDBC drivers must be accessible by this account. The instructions in the preparation topics assume that you are doing the installation locally on the server.
• Install InfoSphere® MDM as a non-root user:
  • For IBM WebSphere Application Server, use the wasadmin ID.

    This ID must own a DB2® client or a DB2 instance and be a member of the mqm management group.

  • For DB2:
    • The suggested installation method is to set up one or more restricted users on a system for database schema users. Because DB2 uses the operating system to authenticate to a new user, a user ID such as mdmdb1 with a restricted shell is the best choice. This user is not required to be a member of any of the DB2 groups.
    • You can also do a simple installation by using a single ID for both the DB2 installation ID and the schema ID. The default ID is db2inst1. For more information about IBM DB2, see the product documentation.
  • A different database user and schema must exist for each deployment of InfoSphere MDM. Different databases for each deployment are not required.
  • When you install on IBM WebSphere Application Server, ensure that no server named server or cluster named cluster is being used on IBM WebSphere Application Server. The names server and cluster are used by the InfoSphere MDM installation.