Using Secondary ehealth Consoles

Transcription

1 Using Secondary ehealth Consoles If you have several ehealth administrators at your site, each administrator can use an ehealth console to perform administrative tasks. The primary ehealth console and any of the secondary consoles can run at local or remote workstations. Through the primary console, administrators can perform all administrative- and user-level ehealth tasks. Administrators can use secondary consoles to perform a subset of the primary console tasks. This chapter provides detailed guidelines and best practices for operating multiple ehealth consoles (these guidelines do not apply to the use of the OneClick for ehealth Console). Performing Tasks Using Multiple Consoles When multiple consoles are in use, the first administrator who attempts to perform a task obtains read-write access for that task. Subsequent admins who attempt to perform the same task (regardless of which console the administrator is using) is given read-only access or is prevented from accessing a dialog that is being used by another administrator. You can allow administrators who might have responsibility for specific users (such as customers) to perform the following tasks for those users from secondary consoles: Discover resources within your network infrastructure. Edit or delete elements. Schedule jobs. Schedule, customize, and run reports. View license information. From the secondary console, an administrator can access some dialogs with restrictions. Table 1 describes the restrictions that apply to the use of the Discover and Poller Configuration (Poller Config) dialogs. Table 1. Restrictions on the Use of the Discover and Poller Configuration Dialogs Administrative Action Administrator opens Discover dialog from the primary console or a secondary console Administrator opens Poller Configuration dialog from the primary console or a secondary console Restrictions Discover dialog and the Poller Config dialog are not accessible from the other console. Poller Config dialog is accessible in read-only mode from a secondary console. Discover dialog is not accessible from both consoles. Poller Config dialog is accessible in read-only mode from the other console, unless you have filtered both consoles to show different groups. If you have specified different element filters for both consoles from the console that you are using you can access the Poller Config in read-write mode for the group that is not appearing in the other console. It displays the elements for the group on which you are filtering only. If you have specified a filter on only one of the consoles or the same filter on both consoles, you can access the Poller Config for the other in read-only mode only. ehealth Release 6.0 October 2006

2 Using Secondary ehealth Consoles Table 2 explains how an open Discover or Poller Config dialog affects your ability to view or modify element information from the other dialogs on the primary and secondary consoles. Table 2. Discover and Poller Configuration Dialog Restrictions with Secondary Consoles Primary Console Discover Dialog Primary Console Filter Primary Console Poller Config Dialog Secondary Console Discover Dialog Secondary Console Filter Secondary Console Poller Config Dialog Open N/A Inaccessible Inaccessible N/A Read-only mode Inaccessible N/A Read-only mode Open N/A Inaccessible Inaccessible None Open Inaccessible None Read-only Inaccessible None Read-only Inaccessible None Open Inaccessible Group A Open Inaccessible None Read-only Inaccessible Group A Open Inaccessible Group A Read-only Inaccessible Group A Open Inaccessible Group B Read-write Inaccessible Group A Read-write Inaccessible Group B Open Inaccessible None Read-only Inaccessible Group B Open Inaccessible Group B Read-only Inaccessible Group B Open ehealth displays messages to indicate whether you have read-only access, or to indicate that you cannot open a dialog. It also displays messages in each console about changes that all administrators are making. Discovering Elements ehealth permits a discover process to run from only one console at one time. When several ehealth administrators are logged into the ehealth system, the first administrator to open the Discover dialog can run the discover, and the other administrators receive a message that they cannot run a discover process. They will have read-only access to the Poller Configuration, Poller Controls, and Options dialogs. Managing the Poller Configuration Only one ehealth administrator at a time can open the Poller Configuration dialog for editing, unless each console has specified the name of a group on which to filter. For both consoles to have read-write access, the group filters specified in the Set Element Filter field in the Options dialog must be unique. If element filters are not set, and a secondary administrator attempts to open the Poller Configuration dialog while an administrator is editing it, ehealth notifies the secondary administrator that the dialog can be opened in read-only mode only. The secondary administrator can then view it, but cannot modify it. If each console has a unique group specified in the Set Element Filter field, administrators can open their Poller Configuration dialogs to edit the elements in the groups they specified in the Set Element Filter field, even if other administrators are simultaneously modifying other groups of elements. 2

3 Using ehealth Secondary Consoles The first administrator to open the Poller Configuration dialog automatically receives read-write access. Other administrators who attempt to open the dialog while it is open are granted read-only access. Two administrators cannot work on the same group of elements or reports simultaneously. Administrators can, however, use element filters to display only the groups for which they are responsible in the Poller Configuration dialog, thus ensuring that they can modify the elements for which they are responsible while other administrators modify their own elements. NOTE: Element filtering enables administrators to edit different groups at the same time. Because ehealth permits the same element to exist in more than one group, one administrator could overwrite changes made concurrently by another administrator. Therefore, take precautions to prevent two administrators from modifying the same elements at the same time. Setting Other Global Options. You can set global console options to show alias names instead of element names and specify report time zones. When you change the settings for the time zone and alias name fields in a secondary ehealth console, the settings are not preserved for any subsequent console sessions. The global settings only apply to the console in which you apply them; that is, if you set an option in the primary console, it is not automatically enabled in the secondary console. Scheduling Jobs An ehealth administrator who uses a secondary console cannot modify scheduled system jobs. The primary ehealth administrator is responsible for managing the database and performing these functions. If two ehealth administrators modify the same scheduled job at the same time, ehealth saves only the changes that were saved last. It overwrites the changes that were saved first. Configuring Secondary Consoles on UNIX Systems Before allowing other administrators to run ehealth at a secondary console, note the following restrictions. If you have installed ehealth on a UNIX system and you allow remote administrators access using secondary consoles, you must grant write permission to those other users. You must add the secondary console administrators to the UNIX user group to which the primary ehealth user account belongs. Specify group write permissions for the following directories (and their subdirectories) in your ehealth installation: help log output poller reports tmp web/output ehealth/extensions/auto To run a secondary console, each administrator must do the following: Log in as a different user (each ehealth administrator must use a unique user name). Obtain read and write access permissions on ehealth directories to create, read, or modify a report or temporary file. 3

4 Using Secondary ehealth Consoles To register another administrator as a database user: 1. Log in as the ehealth user (the name by which you or other administrators access ehealth) on the ehealth system. 2. Do one of the following: If your shell is sh or ksh, source the nethealthrc.sh file. If your shell is csh, source the nethealthrc.csh file. 3. Enter the following command to specify administrator privileges for the new user, where username is the name of an existing UNIX account: nhmanageusers -add -user username -priv admin To run a secondary console at a remote UNIX workstation: 1. Issue the following command to allow an X server to access your display, where ehealthhost is the name of the ehealth system: xhost +ehealthhost 2. Log in to the ehealth system remotely by entering the following command: rlogin ehealthhost 3. Set the display to appear on your workstation by entering the following, where systemname is the name of the workstation on which you want to display the console: setenv DISPLAY systemname: Do one of the following: If your shell is sh or ksh, source the nethealthrc.sh file. If your shell is csh, source the nethealthrc.csh file. 5. Enter the following command, where ehealth is the full pathname of the ehealth installation directory: ehealth/bin/ehealth -2nd Configuring Secondary Consoles on Windows Systems You must create a new user to run the secondary console. (The same user cannot run both the primary and secondary consoles simultaneously.) If you want to restrict access to these users, you can use Windows access control lists to allow individual or group access. To register an administrator as a database user: 1. Log in as the ehealth user on the ehealth system. 2. Enter the following command to specify administrator privileges for the new user, where username is the user name of the secondary console administrator (the user name must be the name of an existing Windows user account): nhmanageusers -add -user username -priv admin 4

5 Using ehealth Secondary Consoles If you run a secondary console on a Windows system, do not output on-demand or scheduled reports to the screen. If you have installed ehealth on a Windows system, you can obtain and install a Telnet server or Citrix Terminal Services on the ehealth system to support secondary consoles. Using Terminal Services. Terminal servers are systems that run application server software that enables you to deploy and maintain a business-critical application on one server machine (or several servers), while multiple users access and use the application from end-user systems. If you plan to use Terminal Services, you must purchase and install the Exceed X server software. You cannot use XVision, the X server that is installed with ehealth, with Terminal Services. To run a secondary console with Terminal Services: 1. Confirm that Exceed and Terminal Services are installed on the terminal server on which ehealth resides. 2. Through the Control Panel, verify that the Administrative Tools directory includes shortcuts for the following: Terminal Services Client Creator Terminal Services Configuration Terminal Services Licensing Terminal Services Manager 3. Verify that Exceed appears in your list of programs. 4. Confirm that the Terminal Services client is running on the system that you are going to use as a secondary console. 5. Verify that XVision is not running on the Terminal Services server or client systems. If it is, stop the XVision Server. You cannot use it with Terminal Services. 6. Create user accounts for the system and for ehealth on the terminal server. Terminal Services supports a maximum of three users for secondary consoles. 7. Start the Exceed server on the terminal server. 8. Start the primary ehealth console; then start the Terminal Services server. 9. Log in to the remote system (Terminal Services client) and start Exceed in the Terminal Services window. 10.Select Start Run, enter cmd in the Open field, and click OK. 11.Enter the following at the command prompt, where x.x is the value that appeared in the Exceed window: set DISPLAY=:x.x 12.Start the secondary console on this system by entering the following command: ehealth -2nd 5

6 Using ehealth Secondary Consoles Using Telnet. If you are using a Telnet server and the client system (the system on which you want the secondary console to run) is running Windows, you must have an X server running. ehealth Windows installations provide XVision as the X server. To run a secondary console through telnet at a remote Windows workstation: 1. Confirm that the telnet server is installed. 2. Start the XVision server by selecting Start Programs Vision XVision Server, or start the primary ehealth console. 3. Log in to the ehealth system remotely by entering the following command: telnet ehealthhost 4. Set the display to appear on your workstation by entering the following command, where systemname is the name of the workstation on which you want the console to appear: set DISPLAY=systemName: Reset your TMPDIR environment variable by entering the following command, where directoryname is the name of the directory in which you want to create your tmp directory: set TMPDIR=directoryName/eHealth/tmp 6. Enter the following command: ehealth -2nd Copyright 2006 CA. All rights reserved. 6