GroupsAdministrator Interface
The Administrator Home Page is divided into six main sections: Groups, Users, Files, LU/Device, Application and Log Out.
Within the Group section, you may configure sessions for the group and associate files with the various session types.
Within the User section, you may assign users to groups and modify each user's individual session configurations. Users will receive all sessions assigned to their group.
Within the File section, you may upload or delete files on the server.
Within the LU/Device section, you may add, remove or modify LU's, Devices and Answerbacks.
Within the Application section, you may modify global attributes of the Web Manager application.
Log Out
Use this link to Log out of the Administrator Interface. Sessions expire automatically after a set timeout period
Java Web Manager has a feature that will automatically lock the database when an Administrator is making changes. Get Lock can be used to manually turn on the database lock.
The following image illustrates the conceptual organization of the Java Web Manager.
Concept One: Sessions are assigned to Groups and only to Groups.
Sessions exist at the Group level, not the User level. If you wish for a user receive two Mainframe Display sessions and one Virtual Terminal session, then that user must belong to a group with those characteristics.
Concept Two: Every User is in a Group
Users do no exist outside of a Group.
Concept Three: Every user gets every Session assigned to the Group
Because sessions exist at the Group level, every user in the Group will "see" all the sessions. If you wish for one user to have three sessions and another to have four, then they must be in two different groups. However, you can share configuration files across Groups, so users in different groups can launch the same sessions.
Concept Four: Overriding Session settings at the User level affects only that User's session.
Session Overrides (or Switches) are a very powerful feature of the Java Web Manager. Using switches allows a fine granularity to the configuration of User sessions. You can imagine User switches as a layer of clear plastic that is laid over top of the Group session, resulting in a merged session with the User level preferences on top.
|
Group Preferences |
User Preferences |
Merged Preferences |
|
Red |
|
Red |
|
Green |
Orange |
Orange |
|
Blue |
|
Blue |
By logical extension, making changes to the User switches will have no effect on the underlying Group session.
To illustrate the power of overrides, let us assume the administrator has a configuration file that specifies a Mainframe Display session window. The window size and position are set, the keyboard mappings are set, and the color scheme is set to the administrator's liking. The administrator wishes to use these settings for every mainframe connection, but has ten different mainframes with ten distinct IP addresses/DNS names. Rather than creating ten different configuration files the administrator sets the host address in the configuration file to "hostOne.myDomain.com". Using the Session Override feature at the Group level the "Host Address" the administrator specifies "hostTwo.myDomain.com" as the main host for the group. Using the Session Override at the User level the "Host Address" is specified as "hostThree.myDomain.com". All three levels share the same configuration file specifying window size, location, color scheme, keyboard mappings, etc. but will connect to three different hosts on launch.
Related Topics:
