Implementing Siebel Business Applications on DB2 UDB for z/OS > Security Concepts for z/OS > Data Transmission Security for Siebel Clients >

Roles and Permissions Used to Connect to DB2

The following roles and permissions are used to connect to DB2 and to install Siebel Business Applications on a DB2 database:

• SYSADM
• DBADM
• CREATEDBA

SYSADM Privileges Used for Connecting to DB2

A DB2 subsystem is a prerequisite for installing Siebel Business Applications. Although you do not need to use an ID with SYSADM privileges to install Siebel Business Applications, you might need such an ID to create underlying DB2 resources. For detailed information on setting up a DB2 subsystem for Siebel Business Applications, see Preparing for Implementation on the DB2 Host.

Functions that require SYSADM authority and that are necessary when you install Siebel Business Applications on DB2 for z/OS include:

• Allocating and accessing buffer pools
• Allocating and accessing storage groups
• Granting CREATEDBA or DBADM authority to the Siebel user ID used for the Siebel database installation
• Creating user-defined functions and stored procedures.

DBADM/CREATEDBA Privileges Used for Connecting to DB2

To install the Database Server requires access similar to that of DBADM; installers must be able to create Siebel objects and access the necessary utilities. Therefore, it is recommended that you grant CREATEDBA privileges to the primary or secondary authorization IDs that will be used to perform the database server installation.