DB2 users for each CLM application
CLM 5.0.2/Tomcat/DB2
From the manual:
Important: If you install Jazz Team Server with the Change and Configuration Management, Quality Management, or Requirements Management applications on either the same computer or distributed platforms, a separate database and a DB user who is associated with that database must be created for each application. In addition, you must create a separate database for data warehouse.
The manual specifies how to create the databases for each appliction, but no specification on how to create the users.
Does the users created on the operating system level? How do I grant them db2 privileges?
Should I create each database with its corresponding users or I can great all of them with db2inst1?
Thanks,
Liora
Accepted answer
Hi Liora,
For DB2 you'll use operating system users added to the db2 users group. You can use db2inst1 if this is not a production environment, but is typically not a best practice to do so. Hope it helps,
For DB2 you'll use operating system users added to the db2 users group. You can use db2inst1 if this is not a production environment, but is typically not a best practice to do so. Hope it helps,
Comments
Hi Benjamin,
Thanks. I am preparing a demo environment, but still, would prefer to follow best practices.
So, I've created a user for each application. Which db2 user group should I add them to: db2iadm1 dasadm1
One more question: Should I create the specific db with the corresponding user?
You only need one common database user for all applications. There are no real advantages to having a unique database user per application. While you might be able to reduce permissions later, in order to provision the database, your user must be a member of the db2iadm1 group. If you find a way around that, please let me know! The product seems to do a lot of configuration checking during setup and can't seem to properly work unless you are an administrator.
1 vote
One other answer
You only need one common database user for all applications. There are no real advantages to having a unique database user per application. While you *might* be able to reduce permissions later, in order to setup the CLM applications, your database user must be a member of the db2iadm1 group. If you find a way around that, please let me know! The product seems to do a lot of configuration checking during setup and doesn't work unless you are an administrator (as of CLM 5.x).