CMS ODBC

[Stinney]

Sorry for the long post, but this is an area of CMS that I am really lost.

We have CMS ODBC Connectivity set up in our CMS. One of our groups uses it to access the Informix tables directly. I also verified it's running on our CMS.

I don't understand how they access it though. They have a login, but it never shows as logged in. I've been told it's because it logs in differently and can be found in a different system log. Where is this log and what are they logging into?

I have another user who would like to access these tables, he can get logged in, but he's denied the ability to look at the tables. I don't know why, or where permissions would have to change. He has rights in CMS to view just about everything report and dictionary related.

I've read the Database Connectivity documents but I'm not completely clear as to how the tables are accessed. I assume they are using a program that can perform SQL queries (like MS Access) and have the ODBC drivers necessary. Reading the documentation it looks like they would need the appropriate DSN for our system (which I don't know what it would be), a user name and password. I attempted the test that the Database Connectivity documentation provides, but I can't get past the DSN entry.


SO, with all that said:

1. What log would show users logging in and accessing the Informix tables?

2. Are there permissions to the tables that have to be given?

3. How do I determine the DSN?

4. How are the tables accessed?


- Stinney

Favorite all too common vendor responses: "We've never seen this issue before." AND "No one's ever wanted to use it like that before.

 

[Coineandude]

1. no idea here
2. i usually have our people use their regular cms user login and i have not needed to add any special permissions beyond what they already have fo cv supervisor.
3. the DSN could have been named anything but we generally call it CMS. depending on your cms version, it will be using some flavor of the openlink generic 32 bit driver.
4. you can use anything that speaks odbc to retrieve data from the tables - crystal reports, excel, access etc etc etc

 

[multibus2]

1. ODBC does use Solaris logins and password however as they are accessing the CMS via the ODBC broker they will not show up with the standard who command, however if you increase the odbc_init log level to 7 you will she who are are loging in warned the odbc logs are rolling if there is a lot of ODBC activity they will wrap as for seening what tables they access, this is quite limited.
The logs are in /cms/dc/odbc and to increase the loging level this command must be entered
/cms/dc/odbc/odbc_init -l 7

2. Using a standard CMS supervisor login they will gave select only access to all the tables listed in the CMS's ODBC manual. They cannot change anything however ODBC is not subject to the CMS applications permissions so they will be able to see all the available data.

3. As per shaneymc

4. As per shaneymc. The installed broker is not multitiered so you only have the basic windows or Solaris odbc connection, i.e. no jdbc or MS SQL openlink conectors.

"Been there, done that and got the teeshirt

 

[multibus2]

Pleaes pardon the bad english...

you will she who are are loging in

should read

you will see who is logging in,



"Been there, done that and got the teeshirt

 

[VoipMenace]

Hi
if you are using ODBC my advice would be to get a nightly copy on a SQL server to remove the risk and workload from the CMS server. One of the place i worked had a shadow reporting server where the reporting dept could work off, leaving the cms server alone

D.

 

[ramjef97]

These documents on Avaya's support site may be helpful.

http://support.avaya.com/elmodocs2/cms_r13/07-300330_cms_db_items.pdf

http://support.avaya.com/elmodocs2/cms_r13/780701_2.pdf