I was in the process of putting the v4.1.1.2 kit out and I hit a bump with the GT.M submission. The next thing I was going to do was completely document security, however, didn't get that far. Here is a short piece from the existing docs (needs to be updated).
EsiObjects offers simple user name and password security. The usernames and passwords reside on the server. They can be created and maintained through the VESOTCMN routine or via the Management|Security command of the development UI.
Creating and Maintaining Users using VESOTCMN.
To set up users on the server using the VESOTCMN routine, you must have access to the MUMPS programming prompt within the ESI namespace that the VESOTCMN routine resides within.
Once you have logged into the area as a programmer, invoke the VESOTCMN routine.
> Do ^VESOTCMN
Select Option 5 from the menu.
At this point, you may enter a ? in response to each prompt for information on how to answer.
First, select the Enable. This will enable security for your system. This will enable the ZV $ENV browser command.
Managing Users from the Developers UI
If the developer starts up the EsiObjects Development UI on a client PC with the /Admin (or /ESI) command line qualifiers and has system level Security enabled, access to management functions are permitted through the Management main menu option. The Management menu option is an add-in and will only appear if these two conditions are present. There are two commands supported at this level.
Version, which simply displays the current version of EsiObjects.
Security, which provides a command path to system and user level security commands. You can use these dialog boxes to set up users or you can use VESOTCMN.
I will get the real docs completed and put out to SF.
Terry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To get the object browser to work, please try the following.
1) Disconnect form the EsiObjects Server.
2) Open the Session Control Window
3) Select the Session to the server in Question
4) Right click and open the properties windows
5) Select the "User" Table
6) Make sure that in the requested privledges section that the Programmer & Debugging options are checked.
7) Select OK
8) Now reconnect and you should be able to Browse object.
Please let me know is this solves your problem.
Jerry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's a few years since I worked with EO, so I've just updated to the latest builds.
I tried "ZV $ENV" in the Xecute Shell in EO Client 4.1.1.2 on Win2k while connected to a Cache server. Nothing appears.
"W $ZV" from the Xecute Shell reports:
Cache for Windows NT (Intel) 4.1.6 (Build 184) Tue May 14 2002 13:50:43 EDT
Ideas?
John
John,
Starting with Verison 4.1 access to ZView has become controlled by the security layers. is security enabled on your EsiObjects server?
Jerry
John,
Welcome back :-)
I was in the process of putting the v4.1.1.2 kit out and I hit a bump with the GT.M submission. The next thing I was going to do was completely document security, however, didn't get that far. Here is a short piece from the existing docs (needs to be updated).
EsiObjects offers simple user name and password security. The usernames and passwords reside on the server. They can be created and maintained through the VESOTCMN routine or via the Management|Security command of the development UI.
Creating and Maintaining Users using VESOTCMN.
To set up users on the server using the VESOTCMN routine, you must have access to the MUMPS programming prompt within the ESI namespace that the VESOTCMN routine resides within.
Once you have logged into the area as a programmer, invoke the VESOTCMN routine.
> Do ^VESOTCMN
Select Option 5 from the menu.
At this point, you may enter a ? in response to each prompt for information on how to answer.
First, select the Enable. This will enable security for your system. This will enable the ZV $ENV browser command.
Managing Users from the Developers UI
If the developer starts up the EsiObjects Development UI on a client PC with the /Admin (or /ESI) command line qualifiers and has system level Security enabled, access to management functions are permitted through the Management main menu option. The Management menu option is an add-in and will only appear if these two conditions are present. There are two commands supported at this level.
I will get the real docs completed and put out to SF.
Terry
To get the object browser to work, please try the following.
1) Disconnect form the EsiObjects Server.
2) Open the Session Control Window
3) Select the Session to the server in Question
4) Right click and open the properties windows
5) Select the "User" Table
6) Make sure that in the requested privledges section that the Programmer & Debugging options are checked.
7) Select OK
8) Now reconnect and you should be able to Browse object.
Please let me know is this solves your problem.
Jerry