Scribd
Upload
8 views2 pages

Using CMS dbaccess

Using CMS dbaccess

Uploaded by

Mohsin Habib
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
8 views2 pages

Using CMS dbaccess

Using CMS dbaccess

Uploaded by

Mohsin Habib
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

12/17/24, 2:21 PM Using dbaccess

Experience the refreshed Home page with efficient navigation and smarter content search. Log in to the site.

Click Here for details.

Maintaining and Troubleshooting Avaya Call Management System

Using dbaccess

Table of Content
Print

Using dbaccess

Last Updated Apr 30, 2024 3 minute read Avaya Call Management System 21.0 Administrator Expert Maintaining

Before you begin


Use dbaccess to limit which CMS logins have ODBC/JDBC access to the CMS database. The CMS database has open access permissions as a standard feature which
allows permission to any CMS login, connecting to CMS through ODBC/JDBC, to view any CMS table. No action is required if all CMS logins are allowed open access to
the CMS database.

The dbaccess utility does not provide the ability to control which tables the CMS login has access to, or which ACD data the CMS login can view. The process of setting
the secure database access is performed in two parts. First, all CMS login-ids that are allowed CMS database access must be members of the Linux group dbaccess.
Second, you must execute the dbaccess option under the CMSADM menu.

Note:
Adding a single CMS login to the dbaccess group disables open access permissions for all users who are not members of the dbaccess group.

Procedure
1. You need to add each CMS login, allowing ODBC/JDBC access to the CMS database, to the Linux group dbaccess. To add CMS logins to the dbaccess group,
enter: usermod -G dbaccess cmslogin . Where cmslogin is the user-id of the specific CMS login to be placed in the group. You must execute the usermod
command for each CMS login for which you want to provide CMS database access

2. To determine which logins are in the dbaccess group, enter: cat /etc/group | grep dbaccess .

3. Open the Avaya Call Management System Administration menu. Enter: cmsadm . The system displays the Avaya Call Management System Administration
menu. menu.

4. Select the dbaccess option. The system displays the following message:

Begin CMS DB Access Permissions changes


grant resource to "public";
Your CMS database currently has public access permissions to all resources. Do you
wish to revoke this access and only grant access to specific CMS users? [y,n,?]

5. Enter: Y . The process continues. The system displays the following messages:

Please wait while CMS Informix Database permissions are changed.


revoke resource from public;
revoke connect from public;
grant connect to cms;
grant connect to cmssvc;
Revoke resource from public on CMS database.
Please wait while connect permissions are granted for requested users
Feedback

grant connect to <cmslogin>;


grant connect to <cmslogin>;
...
Changes to CMS DB Access Permissions finished.

Note:
The output always displays one grant connect message per CMS login, including logins already in the dbaccess group with connect permissions.To remove
ODBC/JDBC access permissions for CMS logins, first remove them from the Linux dbaccess group then run dbaccess from theAvaya Call Management
System Administration menu. menu

After the changes are complete, you may use the CMS logins to run ODBC/JDBC clients and access the CMS database.

6. Remove ODBC/JDBC access permissions for CMS logins from the Linux dbaccess group. Enter: usermod –G “” cmslogin .

7. Open the Avaya Call Management System Administration. menu. Enter: cmsadm . The system displays the Avaya Call Management System Administration
menu. menu.

8. Select the dbaccess option. The system displays the following message:

Begin CMS DB Access Permissions changes


Please wait while connect permissions are granted for requested users
grant connect to <cmslogin>;
...
Changes to CMS DB Access Permissions finished.

https://documentation.avaya.com/bundle/MaintainingandTroubleshooting_r21/page/Using_dbaccess.html 1/2
12/17/24, 2:21 PM Using dbaccess

The Linux dbaccess group information is reset to only provide access permissions to members remaining in the Linux dbaccess group.

9. Run the usermod command for each CMS login in the dbaccess group. Enter:

usermod –G “” cmslogin1
usermod –G “” cmslogin2
usermod –G “” cmslogin3

10. Open the Avaya Call Management System Administration menu. Menu. Enter: cmsadm . The system displays the Avaya Call Management System
Administration menu..

11. Select the dbaccess option. The system displays the following message:

Begin CMS DB Access Permissions changes


No CMS user ids are in UNIX group dbaccess.
If you proceed, the CMS database will
be set to public permissions access for all resources.
Do you really want to do this? [y,n,?]

12. Enter: Y . The process restores public permissions to the CMS database. The system displays messages similar to the following:

Please wait while CMS Informix Database permissions are set to public.
grant resource to public;
revoke connect from cms;
revoke connect from cmssvc;
Grant resource to public on CMS database.
Changes to CMS DB Access Permissions finished.

Previous

Switching password aging on/off

Next

Using config_pkg

STAY CONNECTED

Sitemap | Terms of Use | Privacy | Customize Cookie Settings | Trademarks | Accessibility © 2024 Avaya LLC

Feedback

https://documentation.avaya.com/bundle/MaintainingandTroubleshooting_r21/page/Using_dbaccess.html 2/2

You might also like