eManager User Manual

 

Contents

What is eManager?

Getting Started

Folders/Items View Panel

General

Menus

            File

            Nodes

            Updates

            Distributions

            Pulse

            Tools

            View

Reports

            Options

            Help

Product Node Management

Adding a Node

Viewing a Node

Editing a Node

List Group Affiliation

Adding a Group

Adding Product Nodes to a Group

Deleting Nodes and Groups

Collecting Data from Nodes

Backups

Retrieving Vital Product Data

Retrieving the Update Log

Telnet to a Node

VNC Connection

Phindows to a Node

Buttons

Node Viewer Screen

Node Editor Screen

AutoLocate Screen

Collect Node Data Screen

Change Password Screen

How to Update a Remote Node

            1683/1783 Updates

            1883 Updates

            eTerm 350 Updates

            LINCS Updates

Code Update Screen

Configuration Update Screen

Pull Update Screen

Configuration Editor Screen

Distribution Plan Editor Screen

Distribution Monitor Screen

Code Update Matrix Screen

Job Creator Screen

Node Backup Jobs

eManager Database Backup Job

LINCS Library Backup Job

Important Messages Screen

Generating Reports

eManager Configuration Screen

LINCS Server Support

            eManager Licensing for LINCS

            LINCS Utilities

                        Diagnostic Utilities

                                    Dumps

                                    Event Logs

                                    ESCON Traces

                        Backups

                        Configuration Panels

                        Hardware View

            LINCS Patch Manager

LINCS Configuration Panels Viewer

Pulse Network Monitor

Appendix A - Installation

Appendix B - Troubleshooting

 

What is eManager?

eManager is an advanced software tool used to manage and maintain Visara products remotely. eManager allows you to make software updates and configuration changes to the products from a remote workstation. Some of the functions supported by eManager include:

·         Store specific product information in the eManager database on all Visara products installed

·         Automatically locate and enter Visara products into the database

·         Create and store update objects for configurations and code

·         Create and execute distribution plans for the update objects

·         Backup configurations for all Visara products onto the centrally located eManager platform

·         Shadow remote users on select desktop products

·         Monitor network availability of defined nodes

eManager uses standard IP protocols to communicate with the individual product nodes through available network connections. A complete Visara network can be managed easily and efficiently from a central location using eManager. eManager works with the following Visara products:

·         1683, 1783Network Computing Terminals

·         1883, 300LX, 400LX, 500LX, 500LXe, 600LX, 600LXe Linux Thin Clients

·         eTerm 300, 350, 360, 760 Windows Based Terminal (WBT)

·         LINCS Communication Servers (1174 and SCON models)

·         Linux Servers (SSL1000 and ICON)

 

 

Getting Started

If you have not installed eManager, refer to Appendix A for installation instructions, and for a list of requirements.

Once installed, you can start eManager from the Start menu, generally located at the bottom of your screen on the left side. Click Start, Program Files, Visara eManager, eManager. When eManager loads, a password prompt is displayed. You must key in the correct password to start eManager. The initial password for a new install is ‘eman’. Key ‘eman’ and click OK to finish loading. When loading finishes, product node, configuration and code update names, and distributions are loaded from the database if they exist. See the discussion on the Folders/Items screen for details. Once loaded, it is recommended that you change the password to something more secure. See the eManager Configuration Panel for instructions on changing your password.

To use eManager for code or configuration management, the following steps are generally required:

Add Product Nodes to the Database (use AutoLocate or add the nodes manually)

·         Create optional Distribution Groups if desired

·         Create Code and Configuration Updates as needed

·         Create a Distribution Plan to distribute Updates to the necessary targets

There are instructions in the Folders/Items panel discussion to accomplish each of these steps.

 

Folders/Items View Panel

General

The Folders/Items View Panel is the initial panel displayed and is used to launch most eManager functions. The Folders View on the panel’s left side displays a tree structure with three primary branches: Network Nodes, Update Files, and Distribution Plans. Each branch of the tree can be expanded or collapsed by clicking the + or – respectively. The Items View on the right side displays a view of items that can be node information, update or configuration files, or distribution plan information, depending upon what has been clicked in Folders view. This operation is quite similar to Window Explorer except for the type of information displayed. Information displayed in the Items View can be printed as a report by selecting Reports/Item View Report from the menu at the top of the panel.

A sample structure of the Folders tree is shown below with a description of each branch.

Network Nodes

\__Product - Product model e.g. 1783. Clicking a product branch displays all product nodes for the product type in Items View. Expanding the product branch displays the groups defined for that product type.

\__Group Name – Group Name. Clicking a group branch displays all product nodes assigned to the group in Items View. Expanding the group branch lists the members of the group in Folders View.

\__Group Node – Node that are members of this group

Updates

\__Product – Product model e.g. 1783

\__Code – All code updates for parent product are under this branch

\__ Code Object Name – Name of a code revision. Clicking a code object name displays the code object's files in Item View.

\__File Name – Names of all files in code revision

\__Config – All configuration updates for parent product are under this branch

\__ Configuration Object Name – Name of a configuration change. Clicking a configuration object name displays the configuration object's files in Item View

\__Pull – All pull updates for parent product are under this branch

\__ Pull Object Name – Name of a Pull update change. Clicking a pull update object name displays the pull object's files in Item View

Distributions

\__Product – Product model e.g. 1783. Clicking on a product branch displays the distribution plans saved for this product

\__Name – Name of distribution plan.

The information displayed in the Item View can be displayed in various formats including Icon View, Small Icon View, List View and Report View. In Report View, data is displayed in tabular columns each with a column title. Clicking the column title causes a sort to occur using data in that column. For example, clicking the Name title would sort entries in alphabetical order according to the name. Clicking again will sort in reverse alphabetical order. Another example is clicking the IL title will sort node entries by code Integration Level.

The Folders/Items panel contains a menu bar, buttons, and drop down menus to perform various functions as described below. In general, many of the buttons and menus expect you to select a branch in Folders View or the item in Item View before clicking the menu or button. Also, in some cases you may need to collapse, then expand a branch in Folders View or click on a branch to refresh the screen with changes made by the function just performed. In some cases, e.g. after an AutoLocate, you will need to click the File/Reset Menu to update the information on this screen, or just click the product type in the Folders View section.

Product Node Management

Adding Product Nodes to the Database

Nodes can be added to the database by manually entering a minimal amount of node data, by using the AutoLocate function, or by importing an existing eManager database. The AutoLocate function provides the easiest way to add product node information in most cases, if a structured naming scheme is to be used.

Manual Method

Click on the desire product branch in Folders View, then right mouse click and select Add Nodes. This displays the Node Viewer Screen, which contains fields where node parameters can be entered. See the Node Viewer Screen discussion for details. Once you enter the basic information required for your node definitions (name for the node and IP address, in most cases), you can use the "Collect Data from Nodes" function to gather the remaining information from the nodes themselves. You can also click Nodes on the menu bar and Add Node to display the Node Viewer screen.

 

Using AutoLocate

Click on the <AutoLocate> button to display the AutoLocate Screen which can be set up to search a range of addresses and store any Visara product nodes found. See the AutoLocate Screen discussion for details. You can also bring up the AutoLocate screen by clicking on any product branch in Folders View, then right mouse click to display the dropdown menu and select AutoLocate. You can also click Nodes/AutoLocate on the menu bar to display the AutoLocate screen.

 

Editing Product Nodes

Click on the desired product branch in Folders View to display the desired product node in Item View, then right mouse click it and select Edit Nodes. This displays the Node Edit Screen, which contains fields where node parameters can be edited. Editing node parameters does not change anything configured at the node itself, only the information stored in the eManager database. See the Node Viewer Panel discussion for details. You can also highlight the node in Items View and click Nodes / Edit Node from the menu to display the Node Viewer panel.

 

Viewing Product Nodes

Click on the desired product branch in Folders View to display the desired product node in Item View, then right mouse click it and select View Node Info. This displays the Node Information Panel, which contains information specific to the selected node, as stored in the eManager database. You can also double click the node in Item View to bring up the same information.

 

List Group Affiliation

Click on the desired product branch in Folders View to display the desired product node in Item View, then right mouse click it and select List Group Affiliation. A message box will appear listing all of the groups that the selected node is part of.

 

Adding a Group

You may decide to create a group when you have product nodes in a department or location that you desire to view, update, monitor, and/or create backups as a group. To add a group name, click on the desired product branch in Folders View, then right mouse click to display the dropdown menu and select Add Group. At the prompt, enter a group name and click OK. The group name you entered is added under the selected product. You can also click Nodes on the menu bar and Add Group to display the prompt. Collapse, then expand the product branch to show the new group.

Adding Product Nodes to a Group

Product nodes can be added to a group by editing the node using the Node Viewer Panel or with a drag drop operation. See the Node Viewer Panel discussion for details on this method. To drag and drop, click on the desired product branch in Folders view to display its product nodes in Item view. Then select the desired nodes in Item view. Multiple selections are possible by holding down the <Ctrl> key as nodes are clicked to add one at a time or holding down the <Shift> key to select a range. Double click, but stop with the mouse button down and drag the nodes to the desired group. As the mouse pointer moves over the branches in Folders view, they are highlighted so you can see the target selected. When the desired group is highlighted, release the mouse button and the nodes are added to the group. Note that product nodes can not be copied to a group in another product type. Also, if the selected target is not a group, nothing happens.

You can also add product nodes to a group as part of the AutoLocate function, by specifying which group the nodes are to be added to when detected.

Deleting Nodes and Groups

You can delete a node(s) from the database, delete a node(s) from a group, or delete a group. In each case the first step is to highlight the desired selection.

To delete a node from the database, click on a product in Folders View to display its product nodes in Item View. In Item view, click on the desired node or nodes to select them, then right-click the mouse to display the dropdown menu and select delete node, or just press the delete key. After confirming the action, the node or nodes are completely removed from the database.

To delete a node from a group, click on the group in Folders View to display its product nodes in Item View. In Item View, click on the desired node to select it, then right click the mouse to display the dropdown menu and select delete node. The node is removed from this group but remains in the database.

Multiple product node selections are possible by holding down the <Ctrl> key as nodes are clicked to add one at a time or holding down the <Shift> key to select a range.

To delete a group, click on the group in Folders view, then right click the mouse to display the dropdown menu and select delete group. The group is removed from the database; however product nodes that were in the group remain in the database.

You can also click Nodes on the menu bar and the appropriate delete function.

 

 Renaming a Group

You can rename a group by highlighting the name of the group in Folders View and right-mouse-clicking to display the pop down menu. Select Rename Group from the menu. A box with an edit field will appear to allow you to change the name. Note that the underscore character “_” is not allowed as part of the name.

 

Updating Node Information

If your network information is current within eManager, the simplest way to update the node information in the database is to use the Collect Node Data function. eManager connects to each node selected for updating, downloads the latest information and updates the database. See the Collect Node Data Screen discussion for details.

For networks where DHCP is used, and IP addresses are constantly changing, the preferred method of updating information in the database uses the AutoLocate function to update the database. A 'Minimal Information' option on the AutoLocate panel can be used to keep the process short. See the AutoLocate Screen discussion for details.

 

Backups

eManager allows you to create and restore configuration backups of your network nodes, for disaster recovery situations. The backup is intended to retrieve and store only the configuration information from a node, and not the complete binary image. The backup is stored in a subdirectory of the …eman3000\backups directory.

Backups can be performed on an individual basis or you can create a Backup Job to backup multiple nodes of the same node type, and schedule it to run at some convenient time. When running Backup Jobs, you may indicate the number of backups to be kept for each node, and schedule the job to repeat on a regular basis.

Some care is required to insure that the proper code level is restored or installed on a unit prior to restoring the configuration. Information about the code level that was installed on the node should be available in the eManager database.

Create Backup: Selecting this menu entry creates a copy of the selected product’s configuration files, and stores them in a subdirectory associated with the selected node. If a backup is already stored for the selected node, it will be overwritten by the new backup.

Restore Backup: You may select to restore the configuration backup previously created by eManager. If multiple backups have been created for a specific node, then you can select to restore the last backup or one of the previous backups by selecting which one from the menu (previous backups are identified by their date and time). In order to restore the configuration, the target node should be loaded with a stable copy of its operating system at the same code level that the backup was saved from. One exception to requiring the same code level is the LINCS server platforms. The LINCS platform only needs to be at the same or higher code level than the backup files.

Additional Backup functions are available for the LINCS Server platforms.

Create Backup Job: You can create a Backup Job capable of making backups of multiple nodes of the same type at the same time. The Backup Job is scheduled to execute on the Scheduler tab of the eManager Options panel.

 

Retrieving Vital Product Data

Another way to retrieve and optionally store current information on a node is to use the Retrieve Vital Product Data function. To retrieve and display vital product data from a node, click on its name in Items View, right click to display the dropdown menu and select the Retrieve Vital Product Data menu. eManager connects to the selected node, downloads the parameters and displays them on the Node Viewer Panel. Information retrieved using this function is not automatically stored to the eManager database. The Node Viewer Panel permits saving the information to the existing database entry or creating a new one.

 

Retrieving the Update Log

Some of the products supported by eManager keep an Update Log, giving information on the last update(s) that occurred to that device. This log is typically a log from the node's perspective as to whether an upgrade was successful or not, and what took place. Selecting this function retrieves the log from the node, stores it into the backup directory for that node, and displays it. From the viewing screen, you can print a copy of the contents of the file, save the contents to another file, or copy the contents to the clipboard for pasting into another application.

 

Telnet to a Node

To establish a Telnet session with a product node, click on a product branch in Folders View to display its product nodes in Item View. In Item View, click on the desired node to select it, then right click the mouse to display the dropdown menu and select Telnet To Node. The Telnet connection is then made. For security reasons, in most cases, you will be prompted to enter ID and password when connecting to a node via Telnet. Not all product node types support the Telnet function. For node types that do not support Telnet, the 'Telnet to Node' option will be grayed out on the menu.

The eManager product currently supports a single Telnet connection at one time. An icon in the status bar will display any time that the Telnet client is in use.

 

Wake Sleeping Node

eManager allows you to wake nodes that support Wake On LAN. To wake a node or nodes, click on a product branch in Folders View to display its product nodes in Item View. In Item View, click on the desired node(s). Right-mouse-click to display the dropdown menu and select 'Wake Sleeping Node'. If the 'Wake Sleeping Node' option is grayed out, the node type that you have selected does not support WOL. A WOL Icon should appear in the status line to indicate that the WOL process has been started. If some of the nodes that have been selected do not support Wake On LAN, they will be deselected (for example eTerm 360 and 760 models).

While the WOL icon is displayed, you can click on the icon to display the 'Wake On LAN Status' panel for the node(s) that were selected. A 'View' button on the resulting panel allows you to alternate between displaying the information in 'Icon' mode and 'Report' mode. Pressing the 'Exit' button closes the Wake On LAN Status panel.

You can Wake non-Visara products that support Wake On LAN by selecting 'Wake On LAN' from the Tools menu. A dialog box is presented, requesting the hardware or MAC address of the node, and if entered a second dialog box asks for the IP address. If both addresses are provided, eManager will attempt to wake the node up.

Pinging A Node

To Ping a product node, click on a product branch in Folders View to display its product nodes in Item View. In Item View, click on the desired node to select it, then right click the mouse to display the dropdown menu and select 'Ping Node'. A prompt displays with the product node’s IP address. If no node was selected the address is blank. You may edit or add an address or DNS name if desired. The Ping Screen displays and attempts to Ping the node. You may also Ping any IP address that you desire, by pressing the <Ping> button on the main eManager panel, filling in the IP Address or DNS name that you want to Ping, and press <OK>.

 

Reset a Node

You may reset a product node (force a power on reset) using eManager on an individual or multiple node basis. If the network interface is working, and a reset is initiated with eManager, the node will immediately, and without warning to the user commence to perform a power on reset. Because of the potentially disruptive nature of this function, the eManager administrator is required to enter the eManager password at the time the request is made.

To reset one or more nodes, highlight the desired nodes in Item View and right-mouse-click to display the popup menu, and select Reset Node. A small box will appear that allows you to enter the eManager security password or to cancel the reset operation. A 'Reset' icon appears in the status line when a reset is occurring. Pressing the Reset icon, displays a list of the nodes being reset and allows you to monitor the progress.

For LINCS platforms, there are a number of additional options for the type of reset that is desired, such as whether to do a fast reboot, normal reboot, and whether to boot on the default configuration. Once the desired options have been selected proceed to do the reset or cancel the operation.

 

VNC Connection

VNC, as it applies to eManager, is a product of AT&T Laboratories, designed to provide a shadowing capability to desktops running a suitable VNC server application. Screen data from the target platform is presented to the eManager platform, and keyboard and mouse input on the eManager platform is directed to the target platform as if you were directly attached. VNC is distributed and installed by eManager under the terms of the 'GNU General Public License'. You may also obtain a free copy of the VNC product, as well as the source code for VNC, by going to the AT&T Laboratories website at: http://www.uk.research.att.com/vnc/. The application reference for VNC is automatically configured for eManager, and may be reconfigured to a different location if desired on the eManager's Options panel. If properly installed and configured within eManager, you may kick off a VNC connection to a Visara 1883 from eManager. VNC connections to the eTerm 300, 360, and 760 products is supported if they are running Windows CE 4.2 Build 4026 or higher.

To accept a VNC connection on the 1883, the VNC application on the 1883 must be running. eManager will start the VNC application at the 1883 through a Telnet connection, then start the VNC connection. The Telnet session is closed as soon as the application has been started.

VNC connections can be password protected on most products. If a password is required, you will be prompted for that password when you attempt the connection.

Configuration of the VNC application path within eManager is on the Applications tab of the Options panel.

To establish a VNC connection to an 1883, click the 1883 nodes entry in the Folders View, then right-mouse-click on the desired 1883 target listed in the Item View. Next, select '1883 Utilities/VNC Connection/Start'.

Closing the VNC application window, only stops the current VNC session to the client, but does not shut the client application down on the 1883. To stop the client application as well, select the desired 1883 target in the Item View, then select '1883 Utilities/VNC Connection/Stop'. If the VNC application is still open on the eManager platform, it will close itself when the application at the client stops.

The VNC daemon is always running on the eTerm products, so eManager just kicks off the VNC application to connect to it.

 

Shut Down Node

Initiating this operation will cause a node to power down. For some nodes supporting Wake On LAN, the node will power down, but can be brought back to normal operation by performing the Wake On LAN function.

Because of the potential to cause a problem for a user, the Shut Down Node function is password protected (eManager Password). To cause a node to shut down, right-mouse-click on the node in Item View, and select 'Shut Down Node'. You will be prompted for the eManager password, and upon successfully giving this password the node will be remotely shut down. Only nodes supporting the Shutdown function will have a menu entry.

 

Phindows to a Node

Phindows provides a shadowing function to the 1683 and 1783 products. The path and command line parameters are configured during installation of eManager. If you change the default location of where the Phindows product gets installed, you would need to configure this new path to use it from eManager. See the eManager Configuration Screen discussion for details.

To establish a Phindows session with a product node, click on a product branch in Folders View to display its product nodes in Item View. In Item View, click on the desired node to select it, then right click the mouse to display the dropdown menu and select Phindows To Node. A prompt displays with the product node’s IP address. If no node was selected the address is blank. You may edit or add an address if desired. The Phindows session then automatically connects to the node. If you get a connection 89 error, the node number configured at the product node is not the default. In this case, enter a space N after the IP address in the prompt. eManager will automatically determine the node number. If you know the node number, key space N and the node number after the IP address to connect more quickly. General connection information can be entered on the eManager Configuration Screen.

If the password option has been set at the target product node, Phindows will require that you enter the node's connection password (not the administrator's password).

Phindows comes standard with licensed copies of eManager on the eManager CD and is installed as part of the eManager setup. There is a separate setup program for the Phindows program, which can be found in the Phindows directory on the CD, if you wish to install it elsewhere.

Viewing the Master Node

One product node database entry can be designated as a master for that node type using the Node Viewer Screen. The Configuration Update Screen uses Files located on the master to create configuration updates. To view parameters for the master, Click on any branch under Network Nodes in Folders View so the node information is displayed, then right click the mouse to display the dropdown menu and select View Master Node. eManager displays the master node information in the Node Viewer Screen. Not all product types support a master node function.

eManager’s Main Menu Items

File

Import Database - allows you to merge the contents of another eManager database into your database.

Refresh View – eManager refreshes the data displayed in the Folders/Item View Screen.

Reset View – eManager resets the data displayed in the Folders/Item View Screen, by collapsing and rebuilding the Folders View tree structure and clearing the Item View. This may be used in some cases where a change does not occur as you would expect in the tree structure.

Exit – Exits eManager

 

Nodes

AutoLocate – Displays the AutoLocate Screen

Add Node - See Adding Product Nodes To The Database

Group Definitions

New Group - See Adding A Group

Delete Group - See Deleting Nodes Or Groups

Rename Group – See Renaming a Group

Change Connection Password – Displays the Password Change Screen

Collect Data From Node – See Collect Node Data Screen

View Master Node – See Viewing The Master Node

Broadcast Message - Displays the Broadcast Message Screen

View Device VPD - Displays the contents of the VPD database, displaying VPD on devices attached to LINCS platforms.

Patch Manager - Brings up the patch manager panel for LINCS platforms.

LINCS Configuration Library - LINCS Central Site Library utilities (See also the LINCS Library Backup Job.)

View Library – Provides an interface into the LINCS Central Site Library

Backup Library - Backs up the LINCS Central Site Library

Restore Library - Restores the LINCS Central Site Library

LINCS Event Code Lookup - Allows you to look up LINCS error codes online

Communicate With Node

Node Definitions

Delete Node - See Deleting Nodes Or Groups

View Node Info - See Viewing Product Nodes

Edit Node - See Editing Product Node

Designate as Remote Library – Allows you to assign one of your LINCS platforms as the LINCS Library

List Group Affiliation - See List Group Affiliation

Retrieve Vital Product Data – See Retrieving Node Configuration

Backups – See Backups

Create Backup – See Create Backup

Restore Backup – See Restore Backup

Create Backup Jog - See Backup Jobs

Retrieve Update Log - See Retrieving the Update Log

Ping Node – See Pinging A Node

Wake Sleeping Node - See Wake Sleeping Node

Telnet to Node – See Telneting To A Node

Reset Node – See Reset a Node

Product Specific Utilities - An additional menu item is displayed specific to the product type selected. See Product Specific Utilities.

Product Specific Utilities

            1683/1783 Utilities

Phindows to Node - See Phindows to a Node

            1883 Utilities

VNC Connection - See VNC Connection

Edit Configuration - See 1883 Configuration Updates

            eTerm 350 Utilities

                        Shut Down Node - See Shut Down Node

            eTerm 360 Utilities

Change Terminal Properties - See Change Terminal Properties

Change Host Connections - See Change Host Connections

Set Password to Factory Default – Allows you to reset the passwords on an individual node back to the factory defaults (includes separate control of Terminal Properties password, Administrator password, and VNC password).

VNC Connection - See VNC Connection

Send Message to Screen – Prompts you to input a message that is then sent to an individual node’s screen.

Shut Down Node - See Shut Down Node

LINCS Utilities

Diagnostic Utilities - See Diagnostic Utilities

Force Dump - See Force Dump

Retrieve Dump - See Retrieve Dump

Delete Remote Dump - See Delete Remote Dump

Retrieve Event Log - See Retrieve Event Log

Retrieve Box Fail File - See Retrieve Box Fail File

Retrieve Existing ESCON Trace – Retrieves trace file previously created, that is on the LINCS hard drive

Stop and Retrieve ESCON Trace – Stops the ESCON trace facility, saves the trace, and retrieves it

View ESCON Trace – Allows you to view an ESCON trace that was previously retrieved

Backups - See Backups

Create Backup - See Create Backup

Restore Backup - See Restore Backup

Backup File List - See Backup File List

View Event Log - See View Event Log

View Box Fail Log - See View Box Fail Log

Configuration Panels - See Configuration Panels

Retrieve Panels - See Retrieve Panels

View Panels - See View Panels

Hardware View – Provides a number of interactive utilities. See Hardware View

Device VPD

View Device VPD

Delete Device VPD

            SSL1000 Utilities

                        HTTP Connection – initiates a secure browser connection to the SSL1000

                        Reset SSL Server – resets the SSL1000 server software (does not reboot the hardware)

                        SSL Server Log

                                    Retrieve SSL Log – retrieves the SSL1000 log and displays it in the eManager viewer

                                    View SSL Log – allows you to view a previously retrieved SSL1000 log

                                    Delete SSL Log – deletes the SSL1000 log at the SSL1000

                        Hardware View – See SSL1000 Hardware View

            ICON Utilities

                        HTTP Connection - initiates a secure browser connection to the ICON

                        ICON Server Log

                                    Retrieve ICON Log – retrieves the ICON log and displays it in the eManager viewer

                                    View ICON Log – allows you to view a previously retrieved ICON log

                                    Delete ICON Log – deletes the ICON log at the ICON

                        Hardware View – See ICON Hardware View

 

Updates

Code Updates

Add Code Updates – Displays the Code Update Screen

Edit Code Updates – Displays the Code Update Screen, listing the files in the selected code update

Delete Code Updates – Deletes the selected code update directory and its contents

Create/Edit Update Matrix - See Code Update Matrix Screen

Rename Update – Renames a code update

View Instruction File - Brings up the instruction file associated with the Code Update into the eManager Viewer. No editing capability of the file is provided. This option applies to 1883 nodes only.

Make Floppy Disks - Allows you to create floppy disks from the Code Update (LINCS product line only)

Configuration Updates

New Configuration Update – Displays the Configuration Update Screen allowing you to create a new one

Edit Configuration Update – Displays the Configuration Editor Screen allowing you to change editable items

Delete Configuration Update – Deletes the selected configuration update

View Configuration Update – Displays the Configuration Update Screen showing the selected configuration options

Rename Update – Renames a configuration update

Pull Updates - See Pull Update Screen

New Pull Update - Displays the Pull Update Screen

Edit Pull Update - Displays the selected pull update on the  Pull Update Screen

Delete Pull Update - Deletes the selected pull update

Rename Update  – Renames a pull update

 

Distributions

New Distribution – Displays the Distribution Plan Screen

Edit Distribution – Displays the Distribution Plan Screen showing the selected distribution plan

Delete Distribution – Deletes the selected distribution plan

Rename Distribution - Allows you to change the name of your distribution plan

Submit Distribution – Causes the selected distribution plan to be queued for execution. Execution starts when the start date and time is reached. If the start date and time is past, but the stop date and time has not, the execution will begin immediately.

Terminate Distribution – Clicking this menu submits a request to terminate this distribution. The distribution will not initiate further product node updates but will finish its current tasks prior to terminating.

Verify Distribution – Making this request will generate a Verify Distribution job for the Distribution Plan that is highlighted, and submit it for immediate operation. Each node in the original distribution list, will be checked to see if the distribution completed successfully or not.

View Distribution Status – Displays the Distribution Monitor Screen

 

 Pulse (Network Monitor)

Start Network Monitor – Starts the Pulse Network Monitor, monitoring all nodes specified by the Pulse configuration. The black on yellow Pulse symbol should appear in the status line of the main menu to indicate when the network monitor is running.

Stop Network Monitor - Stops the Pulse Network Monitor. The black on yellow Pulse symbol should disappear from the status line to indicate that the network monitor is not running.

View Network Monitor - Displays a set of icons representing the groups or subnets being monitored by Pulse. The choice of groups or subnets is determined by the Pulse configuration.

Report Generation

View Report Data - Displays the collected network monitor data, in a panel, where you can scroll through the data and perform searches.

Save Report Data - You will be prompted for a file name to save the report data to. Two file extensions are supported, '.txt' and '.csv'. The file created will be compatible to the extension that is selected. Files with '.txt' extensions are made to be viewed with a text editor. Files with '.csv' extensions are saved with comma separated fields and CR/LF separated records and may be imported into a spreadsheet.

Clear Report Data - Deletes the pulse.log file that contains the network monitor data. A message box allowing you to change your mind is displayed. If you proceed to clear the report data, the file is deleted. Individual node history information is not deleted. That information can be viewed on a node by node basis.

Clear Monitor History - Deletes the individual monitor history information that is normally collected and saved for nodes being monitored by Pulse. Clearing the individual monitor information does not affect the pulse.log file.

 

Tools

Job Creator - See Job Creator Panel

Telnet Application – See Telneting To A Node

Ping Application – See Pinging A Node

VNC Application - See VNC Connection

Phindows Application – See Phindow To A Node

Wake On LAN - See Wake Sleeping Node

 

View

This menu contains four selections that let you choose how data is displayed in the Item View section. They are Icon View, Small Icon View, List View and Report View

Reports

The 'Reports' menu allows you to select from two types of report generation. Selecting the 'Item View Report' will allow you to print whatever is displayed in the 'Item View' control of the main eManager panel (printable space must fit within page width). Display whatever information you wish to print, adjust column widths or even collapse columns, sort on any field that you need to then select 'Reports/Item View Report'. You will be allowed to edit the name of the report, or use the default name based on the contents that are currently displayed. Upon approving the report name, the contents of the Item View will be displayed as a report.  You can then choose to review the appearance of the report, print the report, or export the report as a file.

Selecting the 'Special Reports' option takes you to the eManager Report Generator panel, from where you can choose to generate a report based on several predefined report options.

Options

This menu item displays the eManager Configuration Panel

Help

Contents – Loads the help file with the cursor pointing in the table of contents

Folders/Items View – Loads the help file with the cursor pointing to the Folders/Items View Screen discussion

About – gives information about your copy of eManager (serial number, version, and license information)

Buttons

AutoLocate – Displays the AutoLocate Panel

Distr. Monitor – Displays the Distribution Monitor Panel and shows the selected distribution plan

Broadcast - Displays the Broadcast Message Panel

Telnet – Uses the internal Telnet client of eManager. See Telneting To A Node

Ping – See Pinging A Node

Shadow – Used to connect to a 1683/1783 with Phindows or to an 1883, e300, e360, or e760 with VNC. See Phindows To A Node (button appears if Phindows is configured) or VNC Connection (button appears if a path to the VNC application is configured).

Options – Displays the eManager Configuration Panel

Exit – Exits eManager

 

Node Information Panel

The Node Information Panel permits viewing details of the product node parameters for the selected node. You can bring up the viewer by two different methods. The easiest method is to double-mouse-click the node displayed in the Item View list. You may also right-mouse-click the node and select View Node Info from the list of options displayed. A small panel containing a product image and a description of the node's vital product data will be displayed. The panel is removed by pressing OK.

 

Node Viewer Panel

The Node Viewer Screen permits viewing details of the product node parameters for the selected node. The parameters displayed in color (or grayed) are parameters collected from the node or are system parameters that can not be edited. It is a multifunction screen used to add new product nodes to the database, edit existing product node entries, or view the configuration retrieved from product nodes during the Retrieve Vital Data function. Not all parameters will appear for every node type. The following sections describe the parameters displayed on the screen and how they are used, in addition to the menu items and button functions.

Product Node Parameters

Time Zone - Allows you to specify the time zone that the node resides in, for distribution and informational purposes. This field will display the time zone configured for eManager (on the eManager Options panel) by default, when you are adding new nodes.

Node Type - The type of product node is displayed here. This field is a drop down list that displays the node types currently enabled for eManager. (The Options panel is used to enable/disable product node types) It is convenient to change this value when manually adding new nodes of different product types or correcting a database entry that was saved under the wrong product type.

Group - This field is a drop down list of group names associated with the currently selected Node Type. Selecting a group name and saving will add this entry to the group. (Note that you can also add product nodes to a group with drag and drop from the Folders/Items View Panel.)

Name - This is an arbitrary name you can assign to the database entry for this product node. This name is displayed in other screens to make node selections for various functions, so it is recommended that you choose names that you can relate to the product node. See the "AutoLocate Screen" for a discussion of how names are assigned when AutoLocate adds database entries.

Model - Provides Model Number information for node types that come in various models.

DNS Name - This is the full DNS address, if there is one, for the product node. The eManager configuration choices determine if this address will be used to contact the product node. See the eManager Options Screen. Note: Either the DNS Name field or the IP Address field must contain an address.

IP Address - This is the full IP address for the product node in the format NNN.NNN.NNN.NNN where NNN is a number from 1 to 255. The eManager configuration choices determine if this address will be used to contact the product node. See the "Option Panel" for details. Note: Either the DNS Name field or the IP Address field must contain an address.

FTP Password - This password is used by eManager, to access the product node when using FTP. If you are adding a new entry, eManager inserts the default password for the selected node type. If the password at the product node has been changed, you will need to edit this field with the correct password. If the password field is changed, you will be prompted when saving to reenter the password for verification.

Desired Password - The field is used in conjunction with the Password Change Screen. If you need to change a product node password, you can enter the new password here. There is an option on the Password Change Screen that compares the FTP Password with the Desired Password and, if they differ, changes the product node password to the desired password. Note also that the Password Change Screen also writes the desired password to this field during a password change task.

Master - A number 1 or letter Y in this field designates this node as the Master product node. The 'Master' selection can be used by the "Configuration Update Screen", as the source for files when creating a configuration object.

Telnet Password - This password entry field is for products that require the use of a separate password from that used for FTP connections.

Telnet Port - This entry is a 5-digit field used for numerical entry of the Telnet port to be used for communication by eManager. This field will only be displayed for node types that allow you to define the Telnet port that will be used.

The remaining fields that are displayed are parameters collected from the product node or are system parameters, and are not editable.

Buttons

Previous - Clicking the Previous button displays the previous product node entry from the database.

Next - Clicking the Next button displays the next product node entry from the database.

Copy - Clicking the Copy button writes the displayed product node parameters to the Windows clipboard. This enables you to paste it into any other application for editing and/or printing.

Save - Selecting this button saves any changes made on the panel to the database.

Exit - Exits the Node Viewer Screen

 

Menus

File

Save To Database - This saves the displayed data to the database. Existing fields in the database entry are overwritten with the new data.

Save As New Record - The menu save the data as a new product node database entry.

Exit - Exits the Node Viewer Screen

 

Edit

Copy Node Data - Copies just the node data to the Windows clipboard

Copy Log - Copies just the log data to the Windows clipboard

Copy All - Copies all data displayed to the Windows clipboard

 

Help

Contents - Displays the eManager Help file indexed at the table of contents

Node Viewer Panel - Displays the eManager Help file starting at the Node Viewer Panel discussion.

 

AutoLocate Screen

The AutoLocate screen permits you to perform an automatic network search for product nodes using a range of IP addresses, then creates or updates database entries for these nodes. This function provides for the creation of the product node database with minimal effort. This function can also be used to update the current information kept in the database or find new nodes that are not currently stored in the database.

The AutoLocate function criteria are defined as a job, that once created can be executed immediately, or can be scheduled to execute later. A name must be assigned to the job, to distinguish it from other jobs. Once saved you can make changes to the jobs execution start time, cancel the start time, delete the job, or make the job recursive on the eManager Options panel Scheduler tab. You can also select the job from a list of saved jobs for immediate or later execution from the 'Stored AutoLocate Jobs' dropdown list.

To launch an immediate search, just enter the information on the panel as desired and click <Submit> (the Immediate box is checked by default). By pressing the <Submit> button, the job is queued for immediate execution, and will begin to execute, as long as there is not already an AutoLocate job executing and Pulse is not running. AutoLocate uses a combination of SNMP, PINGs, FTP, and proprietary socket connections to locate, identify, and retrieve information from the selected address range, dependent upon the types of devices that you have elected to search for, and the type of search you are performing. Information for all selected product node types is stored when found. You may view the progress of the AutoLocate function graphically by pressing the <View> button. The <View> button is grayed out for the first few seconds when the AutoLocate job starts while the job is being loaded for execution.

The following sections describe the information you need to enter and the choices you can make in more detail. AutoLocate creates a log in the bottom portion of the screen showing the progress of the search. You can use the <Display Log In Viewer> button to display the log in the larger viewer provided by eManager for easier viewing. The <Cancel> button issues a request to cancel the AutoLocate tasks that is currently executing. As soon as AutoLocate finishes with the current task(s), it terminates. The <Save> button allows you to save an AutoLocate job without executing it immediately.

Start Time Options

All jobs may be saved for future action or submitted for execution. The eManager Options Scheduler tab provides a means to reschedule, submit, cancel, or delete the job later. A description of the Start Time Option controls follows.

Immediately – When selected, the <Submit> button will be available to start an AutoLocate job immediately.

Do Not Schedule - If the 'Immediately' option is not selected, the 'Do Not Schedule' option becomes available to allow you to create an AutoLocate job that is not scheduled to execute. Selecting this option will cause the <Save> button to be available, and pressing the Save button will save this job. You can later schedule the job to execute if desired on the eManager Options Scheduler tab, or by selecting the job from the list on this panel at a later time and submit it.

Start Date - Indicates the date when you want this AutoLocate job to next execute. You must press <Submit> button to save the job and submit it for execution.

Start Time - The time selected indicates at what time you want this AutoLocate job to next execute. You must press the <Submit> button to save the job and submit it for execution.

Email Notification When Done - Entering an email address into this field (Alert Email Message Option must be enabled), will cause eManager to generate an Alert message when the AutoLocate job is complete, and send the Log as an attachment.

Three tabs contain the AutoLocate job options.

Locate Criteria Tab

The 'Starting IP Address' and 'Number of Increments to Start Address' fields are required fields to let eManager know what address range you are searching. The remaining parameters are optional, and should be selected according to what you are trying to accomplish (search for new nodes or update existing node information). A description of the tab options are described below.

Starting IP Address – A standard IP address in the format NNN.NNN.NNN.NNN where NNN is a number in a range of 1 to 255

Increments To Starting Address – The number of additional addresses to search. AutoLocate begins the search with the starting address and increments it by this quantity or until the '.255' address is reached.

Subnet Mask to Use - Informs eManager what subnet mask to use for SNMP broadcasts within the address range selected.

LINCS Telnet Port Number - Indicates which Telnet port to use on target LINCS platforms. If LINCS nodes are not part of the selection, this option does not appear.

Locate Options – Determines which nodes are to receive new records in the database.

Locate All – AutoLocate searches the network for all addresses in the specified range.

Locate Undefined Only - AutoLocate searches for only addresses in the range that are not already listed in the database.

Create Record of Non-Visara Nodes - Determines whether eManager will create a record into the database for Non-Visara nodes that are located ('Other SNMP-Capable' and 'Non-SNMP Capable' nodes are listed into the 'Unknown' node type category when found).

Device Types to Locate - Determines which device types eManager is supposed to locate. Node types that are not selected will be ignored when located by eManager. Normally by default, eManager will select the node types for which you have indicated you want support for on the eManager Options panel. Two other entries are provided in addition to Visara node types. These are, 'Other SNMP Capable' - devices that respond to SNMP broadcasts, and 'Non-SNMP Capable' - nodes that respond to an FTP connection attempt. The SNMP response, and the FTP connection string response can be used to help identify what node type is out there. If the 'Create Record of Non-Visara Nodes' option has been selected, a database record of the detected nodes will be created and stored under the 'Unknown' node type category by eManager, otherwise the node types will appear in the log and on the AutoLocate view, but will not be stored. It is possible to create an Alias for the connection strings and associate an icon to be displayed for these 'Unknown' device types when detected, by customizing the eManager Options Node Types panel. Note that the name of the 'Unknown' category can be changed to something more suitable to your application, by editing the name on the main eManager panel.

 

Successful Contact Options Tab

Record Action

Update Existing Record – AutoLocate searches the database for a match of the selected Record Match Option as described below and, if found, updates this record with the information downloaded from the product node; otherwise, a new record entry is created.

Always Add New Record – AutoLocate creates a new database entry for each product node found, even if there is an existing entry for the same device.

Record Match Options

Match Serial Number – AutoLocate checks the database for an entry with a serial number that matches the serial number downloaded from a responding product node.

Match IP Address – AutoLocate checks the database for an entry with an IP address that matches the IP address of a responding product node.

Match Node Name – AutoLocate checks the database for an entry whose name matches the node name downloaded from a responding node.

Match Hardware Address - The network MAC address of the node will be compared to the MAC addresses stored in the database for a match.

Information Gathering

Minimal - eManager will use only the minimum contact criteria to match the node to existing nodes in the database, based on the Record Match Options and the node types being searched for. This can be used to speed up the search process, when you are just trying to identify the new IP Address assignments in a DHCP environment, for example. Not all database information is collected from the node for this selection.

Full - eManager will attempt to collect all information normally collected for the type of nodes that are being searched for.

Default Time Zone Assignment - This field indicates which time zone will be assigned to a detected node when it is placed into the database. By default, the time zone displayed will be the same as eManager's time zone. You can select a different time zone by selecting a different one from the drop down box.

Naming Convention – These choices determine the name that will be used for the database entry, i.e. the name written to the Name field in the database.

Use Existing Database Name – AutoLocate keeps the existing name of a database entry when updating existing records. This option is not available if the Locate Criteria specifies Locate Undefined Only or the option to always add a new record is selected. This selection takes priority over other selections in this group if a match is made to an existing record.

Assign Name Stored At Node – AutoLocate uses the "node name" downloaded from the product node as the name for the database entry. This information may not be unique or configured depending on the node type, and how they are configured.

Use Serial Number - This option will cause eManager to enter the serial number information collected from the remote node as the eManager name for this device.

Use Base Name – For each product node that responds, AutoLocate appends a suffix to this name and uses it for the database entry name. See Name Suffix Options below for choices on how this numeric suffix is generated.

Name Suffix Options

Increment – AutoLocate creates a suffix for the base name starting at 1 and incrementing 1 for each node found. eManager searches the database for the base name assignments and determines the highest number assigned, then uses the next number to begin incrementing from if new nodes are found.

Use Last Octet In Address – AutoLocate appends the digits in the last octet of the IP address to the base name. This method should not be used if the same base name is to be used for multiple subnets, or if you are using DHCP, where the IP addresses will change periodically.

 

Advanced Contact Options Tab

Group Assignments

Assign To Group- When this box is checked, eManager puts each node located into the specified group. A group name is specified, by clicking the drop down arrow for the desired product type, then clicking the name. If a name is typed into the field, a new Group will be created by that name and the located nodes will be stored into it, as long as the name has not already been used. You can define one group for each node type that is being searched for, for any particular job.

Password

Stored Default (Checkbox) - Indicates that you want to used the stored default connection password for each node type selected. If a password other than the default is to be used, it must be configured in the Connect Password fields provided for the various node types.

Factory Defaults Button – Resets the connection passwords in the Connect Password fields back to the factory defaults for all node types.

Stored Defaults Button – Resets the connection passwords in the Connect Password fields back to the values entered and saved on the eManager Options panel for each node type.

Connect Password Fields - Fields contain the password that is to be used when attempting to locate and download node information from selected node types. Node types that do not have a corresponding Connect Password field, will always use the factory default, as no other option is allowed. The LINCS nodes use both an FTP and Telnet password to connect into the node with.

Distribute to New Nodes

Distribution Plan - Allows you to select a Distribution Plan from those that you have created, from a pull down list. If a new node is detected on the network (or if you have selected to generate a new database entry), if a Distribution Plan is listed for that node type, eManager will queue a Distribution Job to be sent to that node immediately upon completion of the AutoLocate job execution. Note that the target list of the Distribution Plan will be modified by the AutoLocate process each time it is run and the original target list will not be restored afterwards.

 AutoLocate Button Options

Submit - Saves and submits the AutoLocate job for execution. All parameters should be set to the desired values prior to submitting the AutoLocate job.

View - Provides a graphical representation of the progress of the AutoLocate job. A series of symbols representing each address, and eventually each node that has been detected and identified, will appear on the graphical representation. You can double-click on the icons to get more information about the progress of the AutoLocate procedure, or the devices that have been identified.

Save - Saves the job, without submitting it for execution. This option is available if you have deselected the Immediate checkbox and selected the 'Do Not Schedule' checkbox.

Cancel - Terminates the current AutoLocate job, when the currently running task completes. A message will be placed in the log, to indicate that a request to cancel has been made. Another message will be entered into the log when the AutoLocate has actually terminated.

Exit - Provides an exit from the AutoLocate panel.

Help - Pressing the help button brings up the eManager documentation.

 

AutoLocate Viewer Panel

The AutoLocate Viewer panel provides a means to visually display the progress of an AutoLocate job executing. Nodes are graphically displayed as icons on the panel. Information provided in the status bar at the bottom of the panel, give the elapsed time, number of addresses attempted, number of nodes contacted, and the number of nodes identified.

The AutoLocate Viewer panel is displayed by pressing the <View> button during an AutoLocate immediate execution.

Double-clicking an icon displays information gathered about the node at that address. If the device is a Visara node, the information displayed is a reflection of the information known about that node. If the AutoLocate being performed is for 'Minimal' information, then eManager will attempt to match a node in the database with the basic information pulled from the unit. The information displayed will be information from the database. If the option for 'Full' information has been selected, the information displayed will be information pulled from the device itself.

Right-mouse-clicking on a non-Visara node allows you to assign an alias name to the response that was received from that node. Once an alias name has been assigned to a particular response, eManager will identify nodes that respond in the same fashion by using the same alias. You can also assign an icon to be used with that alias on the eManager Options Node Types tab.

 

Broadcast Message Panel

Messages that need to be conveyed to remote stations can be written using eManager and then transmitted so they display at remote 1683,  1783, or select Windows CE platform stations. You can display this screen by clicking the Broadcast button or Broadcast menu on the Folders/Items View Screen. To broadcast a message, enter the information on the panel as described below and click <Submit>. The broadcast process connects to each selected product node, uploads the message and causes the remote product node to display a window containing your message. You can also specify the window's title. The following sections describe the information you need to enter and the choices you can make in more detail. The Broadcast Message Screen displays a log in the bottom portion of the screen showing progress. You can use the copy button to copy this log to the clipboard. Once in the clipboard, you can paste the information to any other application for editing or printing. The Cancel button issues a request to cancel the broadcast process. As soon as the current task is finished, it terminates.

Node Target Options

All Nodes - The broadcast function tries to contact every product node in the database, of the node type selected. Note that that the list is grayed out when this selection is made.

Individual Nodes – Clicking Individual Nodes causes the node names to display in the list. The broadcast function tries to contact each node selected.

Groups - Clicking Groups causes the group names defined for this product type to display in the list. The broadcast function tries to contact each node in every group selected.

A node (or group) is selected if it is highlighted. To select a single node (or group), click it. To select a range of nodes (or groups), click on the first node (or group), hold the shift key down, then click the last node (or group) in the desired range. To select nodes (or groups) that are not adjacent, hold the CTL key down while clicking the desired nodes (or groups). To deselect a node (or group), click it again.

Title - Enter text that you want displayed as the window title when the message is displayed at the remote product node.

Message - Enter the text for the message you want to display at the remote product node.

Start Date/Start Time – These entries determine when this task starts. It starts on or after the date and time specified. Note that information and selections for this task are not stored to disk or database, so if eManager is closed down for any reason, the task will not be completed.

Collect Data from Nodes Panel

This screen automates updating the database with the latest information collected from product nodes listed in the database. To launch the collection process, enter the information on the panel as described below and click submit. The collection process connects to each selected product node, downloads the node parameters, and updates the corresponding fields in the database. The following sections describe the information you need to enter and the choices you can make in more detail. The Collection Screen displays a log in the bottom portion of the screen showing progress. You can use the copy button to copy this log to the clipboard. Once in the clipboard, you can paste the information to any other application for editing or printing. The Cancel button issues a request to cancel the collection process. As soon as the current task is finished, it terminates.

Node Target Options

All Nodes - The collection process tries to contact every product node, of the type selected, in the database. Note that that the list is grayed out when this selection is made.

Individual Nodes – Clicking Individual Nodes causes the node names to display in the list. The collection process tries to contact each node selected.

Groups - Clicking Groups causes the group names defined for this product type to display in the list. The collection process tries to contact each node in every group selected.

A node (or group) is selected if it is highlighted. To select a single node (or group), click it. To select a range of nodes (or groups), click on the first node (or group), hold the shift key down, then click the last node (or group) in the desired range. To select nodes (or groups) that are not adjacent, hold the CTL key down while clicking the desired nodes (or groups). To deselect a node (or group), click it again.

Naming Options

Use Existing Database Name - When updates are made to the database entry, the name is not changed.

Assign Name Stored At Node - The node name downloaded from the product node is written to the name field.

Delete Record If No Ping Response – The database entry is deleted if the product node does not respond to a ping. This can be used in DHCP environments to eliminate old node definitions from the database.

Start Date/Start Time – These entries determine when this task starts. It starts on or after the date and time specified. Note that information and selections for this task are not stored to disk or database, so if eManager is closed down for any reason, the task will not be completed.

 

Password Change Screen

This screen automates changing the password at targeted product nodes. Not all node types support the changing of this password. To launch the password changes, enter the information on the panel as described below and click submit. The password change task connects to each selected product node, makes the password change, and updates the corresponding fields in the database. The following sections describe the information you need to enter and the choices you can make in more detail. The Password Change Screen displays a log in the bottom portion of the screen showing progress. You can use the copy button to copy this log to the clipboard. Once in the clipboard, you can paste the information to any other application for editing or printing. The Cancel button issues a request to cancel the password change task. As soon as the current task is finished, it terminates.

Node Target Options

All NCT Nodes - The password change task tries to contact every 1683, 1783 or 1883 product node in the database. Note that that the list is grayed out when this selection is made.

Individual Nodes – Clicking Individual Nodes causes the node names to display in the list. The password change task tries to contact each node selected.

Groups - Clicking Groups causes the group names defined for this product type to display in the list. The password change task tries to contact each node in every group selected.

A node (or group) is selected if it is highlighted. To select a single node (or group), click it. To select a range of nodes (or groups), click on the first node (or group), hold the shift key down, then click the last node (or group) in the desired range. To select nodes (or groups) that are not adjacent, hold the CTL key down while clicking the desired nodes (or groups). To deselect a node (or group), click it again.

All NCT Nodes Where Database Fields Differ – Desired vs Current – Clicking this selection causes eManager to compare the desired password field and the FTP password field for each NCT record in the database and, if they differ, attempt to change the product node’s password to the desired password.

Desired Password

Enter the password you want to change to. It must be entered twice for verification

Current Password

Use Database Password

When connecting to the product node, use the FTP password stored in the database record.

Use Nodes Default Password

When connecting to the product node, use the default password assigned for this node.

Use This Password

When connecting to the product node, use the password entered in the edit box. The password must be entered twice for verification.

 

Start Date/Start Time

These entries determine when this task starts. It starts on or after the date and time specified. Note that information and selections for this task are not stored to disk or database, so if eManager is closed down for any reason, the task will not be.

 

How to Update a Remote Node

Updating the code or configuration of a remote node with eManager is accomplished through the creation and execution of an update distribution. Requirements for the different products that are supported by eManager are different, but the overall process can be summarized. This process can be broken down into the following components that should be performed in the order listed:

1.       The creation of an update object that includes all the necessary files or information to make the change

2.       The creation of a distribution plan that references or uses the objects, and references the nodes that the plan affects.

3.       The submission of the distribution plan for execution.

4.       Verify that the distribution was successful. (Check the 'Verify' box at time of Distribution Plan creation, or manually initiating it later.)

 

1683/1783 Updates

Updates sent to a 1683 or 1783 will be detected by the update daemon in the 1683 or 1783. An information screen will appear on the display of the unit, and give the user the options to do nothing (update starts in 60 seconds), postpone the update (for 5 minutes) to allow time to close down what they are working on, or start the update immediately. If the user powers down their unit while this screen is displayed, the update which is stored in nonvolatile memory will be lost and the unit will not be updated, even though eManager will log the distribution to that device as a success. Running the 'verify' option should detect most instances of a unit that does not actually get upgraded.

Once the update actually begins, another panel will be displayed warning the user not to power off the display. A log appears on the screen indicating the success or failure of the update to install. This log can be retrieved and displayed by eManager.

1683/1783 Configuration Updates

The remote configuration of the 1683 and 1783 product is accomplished by making configuration changes to one unit, pulling the configuration from it, then distribute that configuration to any number of other units. A Configuration Update panel allows you to specify which configuration options you wish to pull from a unit to put into your configuration update object. To reduce the size of the files that are moved across the network, most of the configuration information can be compressed into one or more files prior to retrieval. When compression is selected, you are restricted from deselecting configuration components from the update later.

Most configuration options in the configuration update object cannot be edited once you have retrieved them due to the compression, so it is important to pull only the information needed, and to make sure that you have correctly configured the information prior to pulling it. Those options that may be edited, are available for changing by performing the Edit Configuration Update function from the Updates menu item on the main eManager panel. Although many of the configuration options are the same between the 1683 and 1783, some are different, so eManager handles the two products separately.

1683/1783 Code Updates

Code updates for the 1683 and 1783 products are in the form of code files and instruction files. You typically will have at least one code file (new code level or hot flash) and one instruction file associated with each change released for the product. eManager allows you to include one code level change and multiple hot flash changes into the same code object. eManager will determine the default order in which the changes will be installed at the remote unit.

1683/1783 Pull Updates

Pull updates can be initiated on a group of 1683/1783 products by creating a Pull Update Template within eManager, then distributing this template to the target products. The targets will process the Template in the immediate mode, and pull the update from the FTP Server location indicated in the template. You can establish an interval between 1683/1783 template loads, to provide more control over FTP Server access, by configuring a Pull Interval on the Distribution Plan Editor panel. You can also configure whether the units are to IML when the Pull is complete.

Using the Code Update Matrix

You can create a Code Update Matrix for use with the Code and Pull Updates that you have created for use with the 1683/1783. In the matrix you can specify IL (code) level and a particular Update that you want to be sent to any device detected with that IL level during execution of the distribution plan. By using the Code Update Matrix you can create a path by which down level units can be stepped up to the latest code level in an orderly fashion.

 

1883 Updates

For older levels of 1883 code (IL 003 and earlier), the configuration and application code is stored in a portion of memory that eManager can push changes to. The Linux kernel however, is stored in a protected area of memory that eManager cannot write to. Code changes to the kernel require that eManager push instructions to the 1883 that result in the 1883 pulling its update from an FTP server (Pull Update). Beginning with IL 004, all of the code files including the kernel can be written to directly by eManager, and can be handled as Code Updates unless they are too large (larger than 7.5 MB). Note that you cannot directly upgrade an 1883 from pre IL 004 levels to IL 004 and higher. (A Disk On Chip - DOC - replacement is required.)

1883 Configuration Updates

Remote configuration of the 1883 can be performed by using one of the methods described below:

Direct configuration of the 1883 can be achieved using the VNC product. The VNC product allows configuration of the 1883 in real time, by providing a shadow connection where the screen, keyboard and mouse can be controlled from a remote platform such as eManager. One drawback to this type of control is that you must make a separate connection to each 1883, one at a time to perform changes. A second drawback is dealing with network delays that are inherent within VNC and slower networks.

A second method entails creating a Configuration Update with eManager, using eManager panels to generate a configuration. Once created, this Configuration Update may be distributed to multiple 1883s using a distribution plan. Not all features can be configured using eManager panels.

A third option involves selecting an individual node from the list and selecting to 'Edit Configuration' from the menu. This option pulls the editable files from the node, and displays the configurable options in a tabbed configuration format. You can make changes, then press the <Save> button, which will cause the changes to be written back to the node. Not all features can be configured using this method, but you will not have the delays inherent to VNC while you are making the changes.

A fourth method is achieved by making configuration changes to one unit, pulling the configuration from it, then distribute that configuration to any number of other units. A Configuration Update panel allows you to specify which configuration options you wish to pull from a unit to put into your configuration update object. Although the configuration files are retrieved individually, most configuration options in the configuration update object cannot be edited once you have retrieved them. It is important then, to pull only the information needed, and to make sure that you have correctly configured the information prior to pulling it. Those options that can be edited, are available for changing by performing the Edit Configuration Update function from the Updates menu item on the main eManager panel.

1883 Code Updates

New application update code is distributed to the 1883 through a Code Update. Code updates for the 1883 products are usually in the form of tar files accompanied with an instruction file, but other individual files can be distributed as well in a code object. eManager should know what to do with most tar files through instructions included in the instruction file. In some cases you may also include other code files if necessary, and most individual application code files will be recognized by eManager. If a file is included with the object that eManager is not familiar with, you will be prompted to provide the path information for the unknown file. Some care should be taken not to attempt to push downlevel code to a unit, and you should also not attempt to push code levels 004 and higher to an older version (003 and before).

Code update information is kept in a history file at the node, when eManager is used to update the nodes. This information is reflected in the eManager database, when information is collected from the 1883 nodes.  Code updates are limited in size to 7.5 MB, by eManager, because of the size of the cache memory used on the 1883. A warning will be presented if a larger Code update is attempted. You will need to send larger updates using the Pull update method.

 

1883 Pull Updates

Making changes to the Linux kernel on the 1883 (at IL 003 and before) is performed through the use of a Pull Update. The pull update provides a means to distribute the necessary information in the form of a template that the 1883 needs to pull its update from an FTP server. Distributing an 1883 Pull Update sends the template to the 1883 and instructs the 1883 to update itself. You can also pull updates on 1883s that are at IL 006 and higher (IL 004 and 005 do not support Pull updates), and may need to do so if the update exceeds 7.5 MB in size.

Using the Code Update Matrix

You can create a Code Update Matrix for use with the Code and Pull Updates that you have created for use with the 1883. In the matrix you can specify IL (code) level and a particular Update that you want to be sent to any device detected with that IL level during execution of the distribution plan. By using the Code Update Matrix you can create a path by which down level units can be stepped up to the latest code level in an orderly fashion.

 

eTerm 350 Updates

All code changes to the 350 using eManager are performed as a pull update, using FTP (TFTP code changes must be performed directly from the unit). Configurations are pushed to the 350.

350 Configuration Updates

The remote configuration of the 350 product can be achieved in a couple of ways. You can make configuration changes to one unit, pull the configuration from it, and distribute that configuration to any number of other units. A Configuration Update panel allows you to specify which configuration options you wish to pull from a unit to put into your configuration update object. Most configuration information can be edited within eManager, so it is possible to pull the configuration from a unit, make changes, then push the configuration back to the unit. Those options that can be edited, are available for changing by performing the Edit Configuration Update function from the Updates menu item on the main eManager panel. You can also create a configuration from scratch from eManager, then push it to a unit. eManager keeps track of the options selected, and determines which levels of code, memory, and loader are required at the node, and provides a visual display of this in the Edit Configuration Update panel. You can use the Edit function to "dumb down" a configuration to allow you to push it to a downlevel client.

350 Pull Updates

New code is installed on the 350 through use of a Pull Update. A Pull Update template must be created in eManager then, distributed to the 350. Each 350 will then use the template instructions to make contact with an FTP server and pull, then process the file specified. The file must be placed on the FTP server prior to executing the distribution plan. You can control the number of 350s that will attempt to pull their updates from the FTP server by setting the Pull Interval on the Distribution Plan Editor panel when creating the Distribution Plan.

eTerm 300/360/400/760 Updates

Code changes to the e300/360/760 products using eManager consists of replacing the complete binary (typically 12-15 MB) and can be performed as either a push operation or pull operation. A push operation involves moving the binary file residing in the eManager directory structure, to the client. The pull operation requires that you position the update on a Windows platform available to the nodes that you are attempting to update, and pointing the nodes to the binary file through means of a pull update template. It should be mentioned that prior to code version WinCE 4.2 Build 4021, the portions of the existing configuration of the device may not be saved through a binary code update. At older levels, eManager strives to copy configuration information from the device prior to the binary code update, and restores what it can afterwards. However, if specific IP addresses were assigned in configuration of the devices, restoring of configuration information is not possible as part of the update process. A backup of the nodes configuration is made during the Distribution Plan for a Code Update and much of the configuration can be restored once the node is assigned the correct IP address again. Configuration changes can be handled several different ways, on the e300/360/760 family, allowing for changes to be made to one node, or multiple nodes, in real time or after a reboot.

eTerm 300/360/400/760 Configuration Updates

Configuration changes can be made to a single node, by using the Change Terminal Properties utility. This utility establishes contact with the node and presents a user interface dialog similar to Windows Control Panel, allowing you to make changes to the configuration in real time. A similar utility is available for making changes to Host Connections. In both cases, the changes take immediate affect, but affect only one node, so if the same changes need to be made to several nodes, you must repeat the process several times. Not every feature configuration is accessible through these utilities. To access these utilities display the list of e300/360/400/760 nodes on the main eManager panel, and select the node that you want to modify. Right-mouse-click the node and select 'eTerm 360 Utilities'. The resulting submenu displayed will include the 'Change Terminal Properties' and 'Change Host Connections' utilities.

Another option is to create a Configuration Update with eManager. The Configuration Update is made by either pulling an existing Configuration from a node that has already been configured, or by using the eManager panels to create a configuration from scratch. When creating a Configuration Update with eManager, you can specify which configuration options are to be changed or configured, and with the intent not to change other options. A feature checklist is provided when pulling a configuration from a unit, to indicate which feature configurations to pull. A similar check off list is used when making configuration changes, allowing you to modify your original feature selection. When pushing the resulting configuration to a remote node, only the options that were selected are modified on the remote device. Configuration Updates can be sent to one or multiple units by way of a Distribution Plan that you create. Not every feature can be configured through this utility. Using this process, it is possible to duplicate configuration options across the different models.

VNC is yet another option to allow you to reconfigure an individual remote node. VNC allows you to shadow the operations of the remote device, including the ability to make configuration changes in real time. Additional information on VNC operations in general is described under VNC Connection.

eTerm 300/360/400/760 Code Updates

Using a Code Update you can update the binary code on one or more eTerm 300/360/760 nodes at one time. Separate code binaries are used on the individual models. The remote nodes should have the intelligence to only accept the correct code updates for their model type, but it is still good practice to group the nodes by model type, to streamline the update process. To create a Code Update, expand the Folders View tree, Update Files branch to display the eTerm 300/360/400/760 category, and further expand to reveal the Code category. Right-mouse-click the Code entry, and select 'Add Code Update'. You will be required to name the Code Update and browse for the binary file that will be included in the update, from the Code Update panel. Once the Code Update has been saved, you will use a Distribution Plan to send the Code Update to the node(s) that you wish to update.

eTerm 300/360/760 Pull Updates

Update a remote node with a Pull update involves positioning the correct binary file onto a Windows platform, typically on the same subnet as the remote node that you want to update. You then create a Pull Update template by expanding the Folders View tree to display the 'Update Files/eTerm 300/360/760/pull' path and select it with a right-mouse-click. From the resulting menu, select 'New Pull Update'. Fill in the template with the correct information and save it. Once saved, you can call out the template as part of a Distribution Plan, and send it to one or more remote nodes.

 

LINCS Updates

A code update to a LINCS platform requires replacement of all code files (over 200) at one time. Code upgrades can normally be performed from any Integration Level to a higher level. If you are attempting to take a platform to a lower code level, you should also send a corresponding lower level of configuration for that unit with it. (The older code level is normally incapable of using the configuration files that reside on the node.)

Configuration is concentrated into just a few files, one containing the main configuration, and a few specialized files. The main configuration file is typically created on a specific LINCS platform and used only with that platform. This file contains all of the network and host connection information, as well as information that is specific to a particular combination of hardware, making each LINCS platform's configuration unique. The other specialty configuration files, may contain information that can be globally used by multiple platforms.

Configuration files have a code level associated with them, and can be used on LINCS platforms that are at the same code level or higher. A lower code level can not read the configuration created at a higher code level.

LINCS Configuration Updates

A configuration update is first created on a LINCS platform and then pulled off with eManager. You can pull any of the configuration files from a platform and store them in the update. You can select which of the configuration files are to be retrieved and added into the update. This update can then be distributed to another LINCS platform. Note that the main configuration file should not be pulled from one unit and sent to another unless you are attempting to duplicate the configuration complete with network connections and hardware configurations (replacing the original unit). You also have the option of creating a System 1 floppy with the desired configuration files with eManager from the Edit Configuration Update panel, by pressing the <Disk> button and following instructions.

LINCS Code Updates

Code updates are normally distributed from Visara in the form of 4 self-extracting zipped files. Code objects created for LINCS code can be made directly from the zipped files or from the unzipped files. Selecting the correct extension when attempting to add files to the code update will automatically trigger the proper response from eManager (add all discreet unzipped files, or unzip the file and add the discreet files). Each of these 4 files can be unzipped onto a floppy. The floppies can be manually loaded onto a LINCS platform as part of a "merge" process. You can also load these floppies into eManager as part of a Code Update. When loaded into eManager from 4 floppies, from 4 different subdirectories on a hard drive, or from 4 zipped files,  eManager will remember which files are contained on each floppy for recreating floppies later if desired (for manual distribution and installation if needed). Once a Code Update has been created in eManager, you can distribute the code across the network to one or more LINCS platforms as part of a distribution plan. If all 4 zipped files are unzipped into a single directory, eManager can still create a Code Update, but the ability to reconstruct floppies from the Code Update has been lost.

 

SSL1000 Updates

The SSL1000 is designed to update its code through an internet connection back to a Visara FTP site. Alternately, you can update the SSL1000 from a local FTP site. There are provisions in eManager to allow eManager to update (or downgrade) the SSL1000 server code to a code level. Configuration of the SSL1000 is intended to be performed through a browser connection into the SSL1000. eManager can provide initiate this browser connection if desired. eManager will also let you pull the configuration from the SSL1000 and provides the means to let you make changes to the configuration within eManager. You can also create a new configuration from a collected backup.

            SSL1000 Configuration Updates

From eManager, you can initiate a browser connection to the SSL1000 by selecting the SSL1000 product category, highlighting the specific SSL1000 node from the resulting list, right-click with the mouse and select ‘SSL1000 Utilities/HTTP Connection’ from the menu. From the browser session, you should be able to make most any configuration change that you need to. If you want to make changes offline or want to make the same changes to multiple SSL1000 platforms you could do that using the facilities of eManager. With eManager, you can retrieve the portions of the configuration that you wish to modify (such as the connection mappings), make the desired changes, then send the changes to all relevant SSL1000s.

SSL Code Updates

Code updates can be created in eManager by selecting ‘Update Files/SSL1000/Code’ in Folders View then right-mouse-click to bring up the menu. Select ‘Add Code Update’. SSL1000 code updates consist of a couple of files typically, a TAR file, which is the update itself, and an HTML file that describes what the update is for. Add only the TAR file into the code object. Create a Distribution Plan that references the Code Update, and the nodes to which it is to be sent. Distributing this code update will cause eManager to send the update file to the SSL1000, stop the SSL server, unTAR the update file and restart the SSL1000 server.

 

Code Update Panel

The Code Update Panel is used to create software updates that can be distributed to the product nodes. For the 1683 and 1783, a software update can be an integration level change, a hot flash update or a combination of the two. For the 1883 the code update can be a combination of tar files and regular files as well as hot flash updates. Code updates on the eTerm 300/360/760 products consists of a single binary file. The LINCS code update consists of over 200 files. The SSL1000 typically contains a single tar file.

As this screen is launched, you are prompted to enter a name for this update. A directory with this name is created within the eManager directory structure. The Code Update Screen then provides for adding and deleting files via the Add A File and Delete File buttons, respectively. You should use these functions to copy the files required by the update into the new directory. eManager also adds an object.txt file to the directory containing a list of the files that are included in the code update.

Note that the Distribution Plan Screen handles any situations where the installation order of the files needs to be specified.

Code updates are contained within the eManager directory structure in the following way:

<eManager Directory>/Updates/<Product Type>/Code/<New Directory>

Where,

<eManager Directory> is the directory where eManager files were installed

<Product Type> is the Name of the target product Type. eManager has already created this branch of the directory. Be sure to select the one that matches your target product.

<New Directory> is the name of the directory that will contain the update files.

For example a directory for integration level 47 for a 1783 might be:

C:\program files\eman3000\updates\1783\code\IL47

In the case of adding LINCS files to a code update, eManager looks for a specific file associated with each of the 4 disks, either the name of a self-extracting zip file or one of the file names representing the unzipped files. Upon selecting that file, eManager unzips the file if it is zipped, then pulls the files over for that disk. If all files associated with that update are located in one directory, eManager will pull all of the files in the directory over, and recognize that all 4 disks are accounted for. Configuration files are not allowed in a code update, and must be handled with a configuration update.

Note that when adding a file, eManager will start you in the current directory, unless you have configured a default directory in the eManager Options. Configuring a default directory can save a lot of time if you normally download updates to the same location.

 

Configuration Update Screen

The Configuration Update Screen is used to create configuration updates that can be distributed to the product nodes. Included on the screen is an array of configuration options that you can select from. Only the selected options will be included as part of the update when you create it and when you distribute it. This allows you to copy and change only the options that you desire, leaving other options untouched on the nodes that you are updating.

In some instances, a configuration update can include code for an application, e.g. 1480 client, TN3270 client, etc., but in most instances,   consists of one or more configuration files used by the client node type. By default, eManager does not allow you to select the application code files, and will leave the checkboxes for application code grayed out. You can change this on the eManager Options panel.

A dropdown control is used to specify the Configuration Source. Sources vary from one node type to another, but typically selections include the ability to pull a configuration from a node that has already been configured, create the configuration from panels within eManager, or copy existing configurations stored on the eManager platform (such as from a backup taken of a node).

If copying a configuration from a node, you have the option to specify the node from a list, or simply pointing to a node's IP address, if the node is not known to eManager.

Optionally, for some node types, you can choose the Master Node as the source. See the Node Viewer Panel on how to designate a product node as NCT Master.

Each Configuration Update is stored in a separate directory within the eManager directory structure. The directory location is as follows:

<eManager Directory>/Updates/<Product Type>/Config/<New Directory>

For example, a configuration change named TN3270 for the TN3270 Client in a 1783 might be:

C:\program files\eman3000\updates\1783\config\Tn3270

When creating the Configuration Update from eManager panels, you will be presented with the Configuration Editor Panel, containing a set of tabs labeled by configuration category. On each of the tabs, a box entitled 'Options Enabled' gives a list of features that may be configured on that panel. Only options checked may be configured on that panel. An unchecked option indicates that you do not wish to include the configuration of that feature in your update, and nodes to which your update is sent will not change the options that have not been checked.

Before exiting the configuration panels, you must perform a save using the <Save> button. If you do not save the configuration, eManager will not save what you have when you exit the configuration panels. Not all features may be configured directly from eManager panels. If you need configurations not included in the eManager panels, you must pull them from an appropriately configured node. Exiting the configuration panels takes you back to the Configuration Update Screen.

There is a scratchpad at the bottom of the screen where comments or notes about this configuration can be stored. This is for documentation purposes only. This area also serves as a log. As the configuration is created, progress is displayed in the scratchpad area. (To switch between the two, click the View Log or View Comments button.)

At this point you could click the Distribute button to display the Distribution Plan Screen and create a distribution plan to transmit this configuration to the product nodes.

 

Pull Update Screen

The Pull Update Screen provides a means to specify information that can be loaded into a node to allow the node to update itself from an FTP server. The specified information can be thought of as a Pull Update Template, that can be sent to a node or group of nodes that will update themselves from the same FTP server. The Pull Update is distributed as part of a Distribution Plan. You can set additional distribution options for the Pull updates on the Distribution Plan Editor panel.

It is important to remember to load the update files onto the FTP server, prior to executing the Pull Update distribution. Not all node types support the Pull function.

 

Configuration Editor Panel

The Configuration Editor Panel permits changing specific node configuration items as part of the creation process for a Configuration Update, or once a Configuration Update has been created. Not all configuration items can be changed in the editor. A set of checkboxes are provided under the heading of "Options Enabled", to indicate which configuration options are included in the update (and which options can be changed). Options can be added or deleted from the update by changing the status of the checkboxes. Once deleted from the update, most options will default back to a "factory default", if enabled once again. When editing an existing Configuration Update, if you exit the Configuration Editor Panel without saving the edits, the changes will be lost, and the Configuration Update will remain unchanged.

When an option group is disabled, it is usually grayed out. When enabled, you can make selections within that group. Pressing the <Save> button writes the current changes to the Configuration Update.

 

Distribution Plan Editor Panel

The Distribution Plan Editor is used to schedule transmission of a code and/or configuration and/or pull update to targeted product nodes. The screen permits selection of a code update, a configuration update, or pull update, or a combination from dropdown lists; the target product nodes or groups, and other miscellaneous choices as described below. For some product types, you can also select a Code Update Matrix. When selections have been made, click File/Save and enter a name at the prompt to save the plan to the database. No further action is taken until you submit it for distribution. To submit it, click the Action/Submit menu or from the Folders/Items View Screen by select the named plan, right click it, and click the Submit menu. Once submitted, eManager starts the plan, i.e. starts sending the update to target product nodes, according to the Start/Stop Date/Time as explained below and maintain a log so success or failure can be determined.

When a code update or configuration update is selected, files contained in the update directory are listed on the right side of the screen. eManager provides a verify function that checks these files for potential errors according to the following rules and node type and displays results in the verify log at the bottom of the screen.

1683/1783 Nodes

·         All files in the directory must be targeted for the same integration level.

·         If the directory contains a code update file, ilNN.car, it must also contain a corresponding ilNNupdY.XX instruction file where NN is the new code integration level and XX is the lowest integration level to which the update can be applied (file type XX is optional) and Y is the target product type, i.e. Y=t implies either 1683 or 1783, Y=6 implies 1683, Y=7 implies 1783

·         The Y parameter must match the target product node type for which this distribution is created.

·         Each hot flash instruction file, HFNN.LL (or HFNN.L), generally has a corresponding code file, HFNNLL.car, where NN is the code integration level and LL is the hot flash number.

·         As a minimum for code updates, the directory must contain one code update file and instruction or one hot flash update file and instruction.

·         Each file specified for expansion or copy in the code update instruction or in a hot flash instruction must be present in the directory. All files in the directory must be at the same integration level.

If errors are detected, the plan will not be saved. Note that these are basic, high level checks and obviously do not cover all possible errors. In some cases a warning in lieu of an error is issued and save is permitted. The prudent user will double-check each update for accuracy. In some cases you may need to change the installation order of the instruction files. See the Menu Items discussion below for details on how to do this.

Similar revision level checks and instruction file checks are done for the configuration update.

If an integration level update matrix has been created, "Matrix" can be selected as the code update. See Code Update Matrix panel for information on how the update matrix is used.

No error checking is done when "Matrix" is selected. However, unless Ignore All Errors has been check, the distribution manager will check for errors when an update specified by the matrix is processed.

When a Pull Update is selected for distribution, an additional Pull Interval parameter is displayed and is available for setting. The Pull Interval defines the amount of time that eManager will wait between attempting to load each node with a template, to prevent large number of nodes from attempting to download their updates from an FTP server all at once.

The following paragraphs describe the menu items, target node selection and other choices available in more detail.

Menu Items

File

Save – Saves the plan to the database. If this is a new plan, you are prompted for a name.

Save As – Saves the plan as a new plan.

Exit – Exits the Distribution Plan Screen

Edit

Copy Plan - Clicking the Copy Plan menu writes the plan information to the Windows clipboard. This enables you to paste it into any other application for editing and/or printing. Right clicking the file list can also access this menu.

Change Installation Order - The update may require instruction files to be implemented in an order other than the default. The default order generated by eManager orders the integration level update file first, followed by any hot flash instruction files ordered by the hot flash number. To change the installation order of a file, right-mouse-click the file list to display the dropdown menu and select the Change Installation Order menu. At the prompt, enter the desired position number for the file.

Return To Default Order – Clicking this menu item returns the installation order of the instruction file to the default.

Add A File – Clicking the menu displays a screen that permits browsing to a file and adding it to the update directory. Right clicking the file list can also access this menu.

Delete A File – To delete a file, click it to select it, then click this menu item

Target

Workstation Nodes – Clicking this menu item causes workstation node names to display in the list.

Workstation Groups – Clicking this menu item causes workstation Group names to display in the list.

FTP Server Nodes – Clicking this menu item causes FTP server node names to display in the list.

FTP Server Groups – Clicking this menu item causes FTP Server Group names to display in the list.

Action

Submit – Clicking this menu added this plan to the queue for distribution. Distribution will start according to the start/stop parameters as described below.

Terminate – Clicking this menu submits a request to terminate this distribution. The distribution will not initiate further product node updates but will finish its current tasks prior to terminating.

Monitor – Clicking this menu item displays the Distribution Monitor Screen.

View

View Distribution Log – If you are editing an existing plan, you can display the distribution plan log by clicking this menu. The scratchpad area at the bottom of the screen is shared by the distribution log and the verify log.

View Verify Log – Clicking this menu item displays the verify log.

Help

Contents – Clicking this menu item displays this document.

Distribution Editor Screen – Clicking this menu item displays the Distribution Plan Editor portion of this document.

Buttons

Save – see save menu item

Nodes – displays workstation nodes

Groups – displays workstation groups

Submit – see Action/Submit menu

Exit – Exits the Distribution Plan Screen

 

Other Choices

Send Configuration Update First

eManager orders the configuration instruction file first followed by any code and hot flash instruction files; otherwise, the code and hot flash instruction files are ordered first. This option is not allowed for all product types.

IML After Distribution

It is generally recommended that you IML most products after the update has taken place. This ensures that the changes made are put into effect. It also clears out the memory area used to push updates to some products, and that is also used for supporting various other applications. This area may not be cleared otherwise until the next IML.

LINCS updates do not have any affect until an IML occurs. Because of the nature of the product, this may be desired.

Advanced Button

These items are included under the advanced button to convey that caution should be used when selecting these items.

Override Level Checks

eManager checks the level of code on the target NCT before pushing an update to it. For a new IL level, eManager only verifies that the new code level is the same level or higher than the target, and if so, pushes the update to the NCT. The NCT also contains logic to determine whether the update will be accepted or not. Usually, if the NCT already has the code level that you are trying to push, it will not install the update.

For Hot Flashes, eManager checks the level of the target NCT, and will only push Hot Flashes created for that level of code to the NCT.

If you select to override the checks, eManager will push the new level of code or the Hot Flashes to the target NCT regardless of the level of the NCT. It is not recommended to select to override level checks without recommendation from Visara authorized support personnel. Installing a Hot Flash improperly, can cause problems on the target NCT in many instances.

            Delete Old Files From Remote Directory

Prior to uploading any files, eManager will delete all files in the target directory when this choice is made. The target directory for a 1683 or 1783 is the /tmp directory; for an FTP server it is the start directory specified for the FTP node.

Ignore All Errors And Warnings

eManager incorporates error checking when integration levels and/or configuration updates are selected. There are advanced cases where you may need to create an update that does not conform to the error checking rules. When the choice is made to ignore all errors and warnings, eManager will attempt to build and save the distribution while ignoring any reported errors. It is not recommended that you use this option unless you are confident that you know what you are doing.

Pull Interval

Two fields are available for entering minutes and seconds, representing the amount of time eManager should wait between attempting to load the download templates into multiple nodes. Using the default values of 0 will result in eManager attempting to load the templates into the target nodes as quickly as possible.

Verify After Distribution

You may choose to verify a distribution after the distribution has been completed. Checking the Verify checkbox indicates that you want the verification to take place. If the Verify checkbox has been selected, you may enter a value from 0-20 minutes to indicate how much time between when the distribution plan has completed until the verification process is to begin. The delay is to allow for the update processing time and IML time when distributing to a small number of nodes. For larger distributions involving several nodes, no delay time should be needed.

Verification is performed as a separate 'distribution' job. The title for the verification job is created by concatenating the word 'Verify ' along with the original job name. The verification job is submitted automatically. If you do not choose to verify the job automatically, you can choose to verify the job at a later time by selecting the Distribution Plan from the list on the main eManager panel, and selecting to verify it.

eManager typically checks for code version or the presence of a hot flash on nodes updated with a code update, or will pull the configuration options and compare them to the configuration options sent to verify the job. In some cases, eManager will pull an update log from the client that will identify whether the update was successful or not (from the node’s perspective).

A log is created for the verification by eManager, similar to the log created for the original distribution, and you can view the progress of the verification by viewing the Distribution Monitor. As nodes are verified to have had either a successful or failed distribution, the information is updated in eManager’s node database. You can view this information by selecting the node list on the main eManager panel and viewing the 'Dist Status' field.

 

Distribution Monitor Panel

The Distribution Monitor Panel displays details of the distribution plans including a scratchpad area that displays the log. An arrow control at the bottom of the screen permits viewing the next (or previous) plan. Since updates to the log are frequent during the execution of the plan, you can freeze the information being written to the plan temporarily by clicking the Lock/Unlock button to allow you to scroll through the existing information. A message next to the button indicates whether the log information is currently locked or unlocked. The plan continues to execute while you have the log locked, and the log information will resume updating in real time when you unlock the log.

The Targets field contains a list of the targets for the currently displayed plan. The displayable portion of the field is very small however compared to the size of the list that may be contained in the field. Clicking on the Targets field will display a list of all targets for the currently displayed plan.

 

Code Update Matrix Panel

This panel is used to create a table of Integration Levels and matching code updates. A distribution plan that selects "Matrix" as the code update can interrogate a node, obtain its revision level and use this table to determine which update if any should be sent to the node.

Buttons

Add Entry - This button adds the Integration Level as entered in the IL field and corresponding code update as selected in the Update dropdown box to the table. If the IL has already been added, an error prompt is displayed.

Delete Entry - This button is used to delete an entry from the table. Click the desired entry to highlight it, and click the Delete Entry button.

Delete All Entries - This button clears all entries from the table.

Save - Clicking this button saves the table as the matrix file.

Exit - Unloads the Code Update Matrix screen.

 

eManager Report Generator Panel

The eManager Report Generator Screen provides a means to generate a variety of reports based on the contents of the eManager node database. Various options allow you to select the type of report to be generated, which type of node the report is for, and allows you to sort the order of entries in the report based on a variety of fields. Once the report has been generated, you can print the report or export the report to a file.

To generate one of the predefined reports, select "Report/Special Reports" from the menu selection at the top of the main eManager panel, to bring up the eManager Report Generator screen. Make your selections for Node Type, Report Type, and Sort Options. Optionally, you can select a name for your report different than the default. Once you have made your selections, press the <Create> button. A report based on your selections will be displayed. From the report window, you may select the <Print> button to print the report or the <Export to File> button. If you select the <Print> button, a standard Windows Print box will be displayed allowing you to select additional print options.

Buttons

Create - Generates the report based on options selected

Exit - Returns you to the main eManager panel

 

eManager Configuration Panel

The Configuration Panel provides a means to setup and customize eManager. You can bring up the eManager Configuration Panel by pressing the <Options> button on the main eManager panel. It is organized into tabbed panels as described below.

 

Node Types Tab

This panel permits selection of product node types that will be displayed and supported by this copy of eManager in addition to various options related to specific node types.

 

Enabled Node Types

When a checkbox under Enabled Node Types is checked eManager displays this type in the Folders/Items View Screen and enables all eManager functions that apply to it. If a box is not checked, this node type is not displayed or supported. (Note: The current level of eManager supports a wide variety of product Node types.)

In some cases, several node models are classified into a single handling category, because of the common utilities and/or code that they share (usually using the same operating system such as Linux, or Windows CE).

A <Edit Labels> button is provided to allow you to change the name given to a category of nodes in the eManager panels. Pressing this button will take you to a Label edit panel where you can implement changes to the labels used by eManager for these categories.

Unknown is a special category, used primarily for defining nodes that are unfamiliar to eManager for the purposes of monitoring them with the Pulse Network Monitor. In addition to monitoring, eManager provides a simple interface to allow you to PING, perform Wake-On-LAN, Telnet, Browse, and VNC to the nodes. The node must support the function attempted in order to perform these utilities. The name of the Unknown category can be changed by selecting the Unknown category in Folders View and editing the name.

 

Model Identification

Because of name changes to some of the products in the Visara thin client line, certain products may be known by two different product numbers, although the products themselves are identical. It is possible to tell eManager which model to refer to the products as, when they are found on the network.

 

Default Communication Passwords

Some Visara products are shipped with a default connection password that permits eManager access. Some of these products allow you to change the password for improved security. You may need to enter the password information, for use by eManager when attempting to manage those nodes. You will be prompted to enter a password a second time if you attempt to make changes to one of them.

The assigned default password is automatically entered in the Node Viewer FTP Password edit box when adding a new node. Other eManager functions such as AutoLocate also permit use of this password.

Important Note: Changing the password on this panel does not change the password on the nodes themselves. You must use the Change Password function to make changes at the nodes with eManager.

 

Alias Editor

The Alias Editor provides a means to assign an icon to non-Visara nodes that are detected during an AutoLocate job. Alias names are initially assigned during an AutoLocate job, by right-mouse clicking on a detected node (that is not a Visara node) and selecting to assign an alias to the response string.

To change an alias name string, select the string that you wish to edit from the dropdown control. The name will appear in the edit box. Next, click the Change Image button, and browse for the icon that you wish to associate with the alias. The icon should appear in the square image box to the left of the button.

 

Distributions Tab

This group of choices affects the execution of distribution plans, and allows you to establish the value of certain defaults related to the distribution process.

Allow Integration Level Override - When this box is checked, the Distribution Plan Screen provides an option that, when checked, tells eManager to disregard mismatched integration levels when comparing the integration level of a code or configuration to that of the target product node. CAUTION should be used in selecting this option.

Permit Code in Config Objects - Selecting this option enables the checkboxes on the Configuration Update panel for code objects. Normally these options are disabled (grayed out) since distribution of application code is not normally performed. (Application code is normally distributed as part of Code Objects.)

Wait Time For Busy Node - If a node is flagged as being busy i.e. due to some other distribution or activity, the current distribution plan will wait this number of seconds before giving up.

Wait Time For FTP Slot - When multiple distribution plans are executing or other processes are actively using an FTP connection, the plans must wait for an available FTP slot. The current distribution waits this number of seconds for a slot to become available before giving up.

Wait Time For Distribution Shutdown - When the distribution plan launches the process to update the last node in the list, it goes into a loop waiting for all update processes to finish. The plan will wait this number of seconds before giving up and quitting anyway.

Wait Time for Telnet Client - The eManager Telnet client is used for distributions to 1883 clients. The value set for this parameter indicates how long eManager will wait for access to the Telnet client to complete the distribution, before going on to the next target.

eManager Time Zone - You can select the Time Zone that eManager resides in. Setting the value here affects the default time zone that appears on the AutoLocate and Node Viewer panels.

Default Code Update Source Directory - A default directory can be established where eManager will look when you select to add files to a Code Update. Configuring this option can save time if you are accustomed to copying files into a particular directory, or a series of directories associated with a particular directory. A browse button allows you to browse for the directory instead of typing the path. When browsing, find the directory you wish to make the default, then select any file in that directory. The path will be entered into the edit box.

 

Applications Tab

This group configures the executable path and parameters for various external applications used by eManager. The path to the applications executable must be entered in the location field. Some of this information may be filled in automatically when eManager is installed, if the install process is capable of detecting the locations of the applications. A Browse button is provided for each application to aid in finding the file path information if you need to provide new path information.

Browser refers to your web browser of choice. During installation of eManager, the path to Internet Explorer will automatically be configured if eManager detects IE to be present on your PC. You can put in the path for a different browser if you wish. The browser is used by eManager to view the help documentation provided (this document).

Phindows provides a shadowing function for use with 1783 and 1683 products. The Phindows software product is included on serialized copies of eManager and is installed as part of the eManager installation procedure. The installation program for Phindows can be found on the eManager CD in the \Phindows directory if you wish to install it elsewhere. The command line field contains parameters that control how Phindows behaves when launched. A default set of command line options are defined at eManager install time automatically. Additional information can be found in the section titled Phindows to a Node.

VNC is an option available for use with the 1883, 600/610XPe, and e300/360/400/760 products to allow shadowing of those nodes. VNC can also be used to shadow a variety of non-Visara platforms if a VNC server agent is running on those products. The VNC product is provided as shareware with eManager and is part of the normal installation. Additional information on the use of VNC can be found under the title VNC Connection.

 

Diagnostic Tab

These boxes can be checked for diagnostic purposes when troubleshooting a problem. When checked, a window is displayed for each instance and a log or screen showing progress and activity for the selected client is displayed.

FTP Trace - The FTP Trace allows eManager to trace an FTP connection when performing a Distribution Plan or other FTP activity. Once enabled, window will display each time a new FTP session is launched. You can copy this log to the Windows clipboard and paste it into any other application for editing and printing. The trace facility remains enabled, until you turn it off. Note that during large distributions, numerous FTP windows will be opened (perhaps too many) and it is normally recommended that you only use this option when you are dealing with a single FTP connection for best results.

Telnet Trace - Causes the eManager Telnet Client window to display when in use, even for operations that normally occur in the background. With the Telnet Trace option selected, the Telnet window will be displayed normally whenever the Telnet icon displays in the status line.

Ping Trace - Causes the eManager Ping window to display when a ping operation is launched.

Advanced Button - Behind the Advanced button you will find a way to reset the Telnet Semaphore. The Telnet Semaphore is used by eManager to allocate the Telnet resource, and in some error situations the semaphore could remain allocated to a failed process (the Telnet Icon remains on in the status row) after a failed process has been concluded. If this occurs, please take note of which operation was being attempted and report this information back to Visara so that we can correct the situation.

 

Administrator Tab

Display Secure Options Button – Prompts you for the eManager password to allow you to gain access to the Secure Options tab.

Assume Serial Number from CD – Pressing this button starts a process that lets you browse to a serialized eManager CD, and read the serial number from it. Doing so, serializes the installed copy of eManager. The primary reason for this function is to take an evaluation copy, and change it to a serialized copy, without having to go through the more lengthy installation process.

Choose working Icon - Allows you to select the animated Icon used by eManager to show activity during certain functions.

LINCS License Management – Provides buttons that can be used to view the current list of LINCS serial numbers that eManager is keeping track of, remove a particular serial number from the list, and add to the LINCS license. To increase the LINCS license, you must first purchase the additional license (disk/file). You may then insert the file where you can browse to find it, and use the button provided to initiate the browse and read activity that is needed to update the LINCS license online. Once you have upgraded your license, you may want to click on the Help/About function from the main eManager panel to confirm that the license has been upgraded correctly. A copy of the license file should be kept in a safe place in case you ever need to reinstall eManager onto a different platform or reinstall it from scratch (such as if you have a hard drive failure).

 

Network Tab

The network tab contains the configuration for some of the eManager networking resources.

FTP Options

Use Passive Mode - Check this box if you need to cross firewalls to manage some of the network nodes, and the firewalls do not permit Active FTP connections (blocking TCP port 21). Setting this option for an internal network when not needed can affect FTP transfer speeds significantly, and would not be recommended.

Maximum Concurrent FTP Sessions - Indicates how many FTP sessions eManager is allowed to establish concurrently when performing AutoLocate and Distribution functions. If slow dialup links are used, or if the PC that you are running eManager on is a slow PC (under 200 MHz), or if there are several other processes running on the same PC at the same time as eManager, you may want to keep the number of concurrent FTP sessions low. Values between 1-10 are allowed.

FTP Connection Timeout (Seconds) - This timeout is used by several processes, to prevent hanging a process when the node that eManager is attempting to FTP to does not complete the connection successfully.

PING Options

Maximum Concurrent PINGs Used During AutoLocate - Determines the maximum PINGs connections that eManager will attempt to open at one time. The number of sockets that Microsoft's Winsock allows open varies from one Windows platform to another. This option allows you to decrease the number used by eManager to make things run more smoothly in some environments.

Minimum Times to PING a Node During AutoLocate - Some networks throw away some of the PING packets generated by eManager to identify availability, making it necessary for eManager to send multiple PINGs to those devices. You can increase the incidence of contact by increasing the number of PINGs that eManager will send during the AutoLocate process. Only addresses that did not respond to a previous PING will be PINGed again. Information is written into the AutoLocate log to identify how many PINGs and how many PING responses were received during AutoLocate. If the second and subsequent PINGs never result in a response, then you can probably set this option back to 1 for your network. The more times that eManager is required to PING devices during AutoLocate increases the time to complete an AutoLocation significantly.

PING Before Telnet/FTP Connection - This option, when checked will cause eManager to PING a node before attempting to Telnet or FTP to it when running certain procedures. A PING timeout is much shorter than a Telnet or FTP timeout. If there is no response to the PING, eManager will not attempt to continue with the procedure. This can save a lot of time when performing certain functions such as backup jobs, where devices might be powered off. Some networks however, will block PINGs from passing to a node, so sometimes it is necessary to turn off this option in order to establish a connection to the remote nodes.

SNMP Options

Community Name for AutoLocate - This provides a means to customize the community name used by eManager when performing AutoLocate operations. The default name is 'public' which is the default supported by a wide variety of networked products. Some products can be customized to require a different name for security reasons. The value configured for eManager should be the same as what is configured on the products that eManager is expected to AutoLocate.

All 1883s are SNMP Capable - This option when checked will assume that all 1883s that eManager is to support are at IL 10 or higher, meaning that they are all SNMP capable. This can greatly reduce AutoLocate time, if eManager knows that all 1883s will respond to the SNMP (no need to PING and FTP to the nodes to locate them initially).

All 350s are SNMP Capable - This option, when checked, will assume that all 350s that eManager is to support are SNMP capable. This can greatly reduce AutoLocate time, if eManager knows that all 350s will respond to the SNMP (no need to PING and FTP to the nodes to locate them initially).

Default Subnet Mask - You can enter the subnet mask used on your network, to provide eManager with a default value to enter on your AutoLocate panels, for use when determining SNMP broadcast addresses. If no mask is configured, eManager will assume the mask 255.255.255.0 is to be used.

NCT Address Options

The choices in this group determine the IP address eManager will use when connecting to product nodes.

Use IP Address Always - The numeric address in database IP address fields (as displayed in the Folders/Items View Panel) is used for the connect address.

Use IP Address When DNS Name Is Blank - If the database DNS Name fields is blank, eManager uses the IP address field; otherwise the DNS name is used for the connect address.

Use DNS Name Always - The numeric address in database IP address fields (as displayed in the Folders/Items View Panel) is used for the connect address.

 

 

Pulse Tab

Pulse is the network monitor that is provided by eManager for the purpose of monitoring the Visara nodes on your network. Configuration of the options provided for Pulse is performed on the Pulse tab of the eManager Options panel.

Enable Network Monitoring - Enabling this option, results in the addition of the Pulse menu item on the main eManager panel.

Autostart Pulse on Boot Up - Selecting Autostart, will turn on the Pulse network monitor every time you boot the eManager application.

Display Status Colors on Node List - This option causes the network nodes to display the correct monitor color when you are on the main eManager panel and running Pulse. Only the name of each node displays the black (not monitored), green (communicating), yellow (did not respond to last query), or red (not communicating) indicators. Without this option enabled, you must use the Pulse 'View Network Monitor' option to view the node status.

Nodes to Monitor - You may select to monitor all nodes defined to eManager, or you can select specify individual groups. If you select to specify the groups to be monitored, you can check the group names in the list provided.

Check Frequency - A value in minutes determines how often eManager will attempt to contact the nodes to determine whether they are communicating on the network. PING is the tool used by eManager to determine whether a node is communicating or not. eManager limits the number of PINGs sent to a few hundred per minute maximum. A value of 5 minutes should allow eManager to make contact with about 1000 nodes on a local network during that interval.

Report Generation - Report generation options include the recording of Node Going Down events (no network response after interval where the node was responding), and Node Going Up events (good network response after interval where the node was not responding). A maximum file size can be established for the log to prevent the log from consuming your hard drive.

Scheduler Tab

The scheduler tab provides a means to display, change, and delete scheduled tasks. A dropdown list allows you to select the type of task that you want to view. The Report Box gives a list of Jobs that are in the schedule list, and the current status of those jobs. Currently, the types of jobs that can be affected by the scheduler are:

·         AutoLocate

·         Node Backups

·         Distributions

·         eManager Database Backup

·         LINCS Library Backup

You can affect an individual job, by selecting a job from the list, and right-mouse-click the job to get a dropdown list of actions that can be taken. Among these tasks are:

·         Delete Job

·         Edit Job

·         Cancel (Job) Execution

·         Change (Job) Schedule

·         View (Job) Log

Delete Job:  Selecting to delete the job will remove the job from the list and from the eManager database.

Edit Job:  Selecting to edit the job will cause the appropriate editor to appear for the job type that has been selected. Changes can be made to the job, and the changes saved. When exiting the edit panel, you will be returned to this panel.

Cancel Execution:  Selecting to cancel the execution, will not delete the job, but will prevent it from executing at the prescribed time if the job is scheduled to execute in the future. If the job is currently executing, execution of the job will be suspended at the next opportunity.

Change Schedule:  This will allow you to change the scheduling of the event, and change the interval if the event is repetitive.

View Log:  When selected, the appropriate log for the type of job selected, will display. 

Rescheduling Options - when you select 'Change Schedule', a set of rescheduling options appear. Included among the options are recursive options allowing the job to automatically reschedule itself on a daily or weekly or immediate basis. You can also set in a date and time for the next scheduled execution of the plan. Selecting the 'Pending' checkbox causes the job to be rescheduled. Deselecting the Pending checkbox will change the status of the job to 'Not Scheduled'.

Print Button -  The <Print> button allows you to print the contents the current job list.

 

Patch Manager Tab

The patch manager tab allows you to customize the LINCS Patch Manager utility.

Default Patch Source Directory - This entry identifies where eManager should look for new patches. If you do not configure a path, then the Patch Manager utility will start in the current directory.

 

Alert Messages Tab

The Alert Messages tab allows you to determine whether you want eManager to create and post a message when certain events occur, or to send an email to a specified person.

Display Message Icon in Status Line - Selecting this option will cause eManager to display a 'Message' icon in the status row, whenever an important message is generated by eManager to the eManager Administrator. Clicking the icon will cause the message to be displayed. This option is normally defaulted on.

Allow eManager to Send Alert Message Via Email - Selecting this option will cause eManager to generate an email message to a specified destination that has been associated with the job that generated the message. Logs generated as part of the job that generates the message, will be included as an attachment to the email. Enabling this option will activate the 'eManager's Identity' box, allowing you to configure the information necessary for eManager to connect up to the appropriate email identity.

Email User ID - Enter the User ID eManager is to use to access the local email system.

Password - Enter the User Password eManager is to use to access the local email system.

Email Alias - This field determines the source identity that will be displayed when an email message is sent to someone, to identify the sender (eManager).

Alert Message Destination - The Default Destination field indicates where eManager is to send most messages. The entry in this field will come up as the default destination for the alert message, for various jobs that generate a message. The value can normally be overridden on the other panels.

View Messages Button - Pressing this button will display any outstanding messages, beginning with the first of any unacknowledged messages.

 

Secure Options Tab

The Secure Options tab is disabled until you provide the eManager password from the Administrators tab. This is to prevent someone from walking up to a running copy of eManager and making changes that might compromise security. The Secure Options tab becomes disabled again when you leave the eManager Configuration panel.

eManager Password Change - Allows you to change the password used by eManager when eManager boots up or when certain operations are attempted, such as distributions.

Display <Password> Button on LINCS Telnet Interface – Checking this option causes a button to appear on the LINCS Telnet interface, with the label of ‘Password’. When the LINCS platform that you are communicating with challenges you for the Supervisor password, you may use this button to provide the necessary password. The actual password information is not displayed. This aid allows the administrator to enter the password without having to remember the password for that particular unit.

Require Password for Distributions and to Update Remote Node Options - Causes eManager to prompt for a valid (eManager) password prior to submitting a distribution plan for execution, or before allowing you to change node options on a node in real time (does not affect Shadowing connections).

Require Password to Reboot or Shutdown Node – Requires you to enter the eManager password prior to performing a node reboot or a node shutdown operation.

 

Job Creator Panel

The purpose of this panel is to allow you to create jobs, which once created, can be scheduled for execution on the Scheduler tab of the Options panel. To bring up the Job Creator panel, select 'Tools' from the menu and select 'Job Creator' from the drop down menu. You can also access the panel by selecting the path 'Backups/Create Backup Job' from the right-mouse-click menu displayed when selecting a node from Items View.

Controls on the Job Creator panel are as follows:

Node Type - This is a dropdown list that determines which node type is to be associated with this job. The 'eManager' selection in the list allows you to create a job that backs up the eManager database.

Job Name - This is a data entry field where you enter the name of the job you wish to create. If you select an existing job from the Job List dropdown, it will appear here.

Job Type - This dropdown list, allows you to select the job type that you want to define. The types of jobs available can differ from one node type to another. Among the job types supported are:

·         Backup Nodes – Provides a backup of the configuration for the nodes selected. Only the configuration (not the operating system) on the node is backed up. You may indicate at the time the job is created how many backups of a particular node are to be kept. When the job executes, if the indicated number of backups are already stored, the oldest backup will be deleted. Individual backups may be restored using the Backups/Restore Backup utility.

·         Backup eManager's Database – Provides a means to backup the main eManager node database on a scheduled basis. Note that the directory structure, code updates, and configuration updates are not included in this backup.

·         Backup LINCS Library – Provides a mechanism that will backup the LINCS Library from the LINCS platform that is currently assigned to have the LINCS Library, into the directory structure of eManager.

Job List - This is a list of jobs that already exist, for the job type and node type that have been selected.

Node Selection Options - You may choose between All (Nodes), (Individual) Nodes, and Groups (of Nodes), for your job. If you select Nodes or Groups, you must select from the lists which nodes or groups of nodes the job applies to. Selecting ‘All’ will cause the list of nodes to be selected with all nodes selected.

Email Option - Allows you to enter an eMail address to where an email will be sent when the job has completed, provided that you have the option enabled to allow email messages to be generated by eManager.

Job Options - Different jobs permit different options to be selected. These options will appear in the central area of the panel.

Button Definitions:

Save - Saves the job as defined by the selections on the panel. Saving the job does not schedule it for execution. You must schedule job executions on the eManager Options panel, Scheduler tab.

Delete - Deletes the job that is currently selected.

Exit - Exits you from the Job Creator panel.

 

Import Database Panel

The Import Database panel can be used to import other eManager database files into the current eManager database. This includes older versions of eManager such as eManager 2000 or other copies of the current eManager. Evaluation copies of eManager will limit the total number of desktop nodes to 50, and will limit the number of nodes that can be imported so that this maximum number is not exceeded.

It is recommended that you run the Collect Node Data function on nodes that have been imported from older versions of eManager so that any additional information gathered and stored at the current version will be retrieved and updated.

The fields on this panel are organized as follows:

Import File Type - This allows you to select from eManager 2000 files (version 1.1.6) or eManager version 1.5.0 or higher.

Browse Button - Allows you to browse for the file. Note that only files of the types needed by eManager, will be displayed. These were typically called emanager.csv for eManager 2000, and emanager.mdb for eManager version 1.5.0 and higher.

Include Group Info Checkbox - This option only applies to the eManager 1.5.0 and higher files. Selecting this option will import group definitions in addition to node definitions from the other database. If group definitions were used in eManager 2000, you will need to redefine the groups after you import the node information.

Start Import Button - Pressing this button initiates the import function. A message will be displayed at the completion of the import and indicate success or failure, and how many nodes were imported.

Return Button - Pressing the <Return> button causes this panel to be taken down, and return given to the main eManager panel. This button can be pressed prior to the database import or after.

 

Important Message Panel

If the Messaging option is enabled on eManager, a message icon will be displayed in the status line, whenever an important message has been generated by eManager. Pressing the 'Message' icon, results in the display of the first Important Message that remains unacknowledged, displayed on this panel. When multiple messages exist, they will be displayed in the order in which they were generated, beginning with the first unacknowledged message. Configuration for the generation of Important Messages is made in the eManager Options panel. In addition to the displayed message, there are five buttons displayed.

Close - Closes the Important Message panel. Messages that have not been deleted will still be available for viewing later.

Acknowledge - Acknowledges the message to eManager. If no other messages remain unacknowledged, then the 'Message' icon will go away. Pressing the Acknowledge button does not remove the message. The message can be viewed again later if desired.

Delete - Pressing this button removes the message from the Important Message list. Once deleted, the message is no longer available for viewing.

View Log - For Important Messages that were generated as the result of a job execution, there will normally be a job log associated with the message that can be viewed.

Help - Displays the feature description that you are reading now.

The Message Icon

The Message Icon will display in the status row of the main eManager panel, whenever an Important Message has been generated by eManager, and the message remains unacknowledged. Acknowledging or deleting all Important Messages, will cause the Message Icon to go away.

Viewing Old (Acknowledged) Messages

You must go to the eManager Options panel, Alert Messages tab, and press the <View Messages> button. This will allow you to view all outstanding messages, acknowledged or unacknowledged, and allow you to acknowledge or delete them as well.

 

Alert Message Email Support

Alert Messages can be generated by eManager and sent via email to configured destinations. Configuration of this feature is made on the eManager Options panel, Alert Messages tab. Individual operations can be configured in eManager to generate the alert messages (and the destination of the message is also defined). eManager makes use of existing email services configured on the PC that eManager is running on. A number of email services are compatible with eManager including Microsoft Exchange and Outlook or Outlook Express. Logs generated by operations that also generate the Alert Message will be sent in the email as attachments. eManager does not have the means to receive email, so there is no need to configure a mailbox for eManager.

 

LINCS Server Support

LINCS is the name given to the operating system used by Visara Communication Servers. This includes the line of 1174 Communication Servers and the SCON Console Concentrators. These communication servers are used to provide direct-attached and network-attached desktops and printers to communicate with the 3270 Mainframe environment.

eManager provides a number of management facilities to make working with the LINCS products easier, and provides a means to diagnose and recover from communication problems faster.

eManager Licensing for LINCS

The standard license for eManager includes a license for support of up to four LINCS servers. Additional licensing can be added to eManager to provide support for as many LINCS servers as needed. To increase your LINCS license for eManager, contact your local Visara sales representative.

LINCS license upgrades come in the form of a license file that can be integrated into eManager using a utility found on the eManager Configuration Panels.

eManager licensing for LINCS is implemented by allowing management of a limited number of LINCS servers, whatever your license permits. Establishing communications with a LINCS server for the first time initiates an exchange of information that causes eManager to register the LINCS platform to the eManager LINCS license. This registration remains in effect unless removed manually, as allowed by a utility found on the eManager Configuration Screen. Removing the registration of a LINCS platform causes all database entries for the device to be removed.

 

LINCS Utilities

Most of the same functions supported for Visara desktops are also provided for LINCS platforms. These include:

·         Node Definitions
      Add
      Edit
      Delete

·         Group Definitions
      Add
      Delete
      Rename

·         Collect Data From Nodes

·         Backups
      Create
      Restore

·         Communicate With Node
      Retrieve Vital Product Data
      Ping Node
      Telnet to Node
      Reset Node



Additionally, several other functions are unique to the LINCS platforms. These functions are described below.

View Device VPD

This selection allows you to display vital product data for all LINCS platforms that eManager has collected VPD information from. The information is displayed in Item View, where the information can be sorted by any field. You can also put the information in report form by selecting 'Reports/Item View Report'. This allows you to print or save the information to a file.

 

Patch Manager

The following functions are accessed by selecting the LINCS category in Folders View, then right-mouse-clicking:

Selecting this option brings up the LINCS Patch Manager panel. The purpose of this utility is to allow you to patch specific LINCS code levels with specific patches, as an alternative to installing a new integration level. The patch manager can identify which patches are installed a particular LINCS node, and can be used to install and remove patches from those nodes.

 

LINCS Configuration Library

The LINCS Configuration Library, also known as the Central Site Library in LINCS documentation is a library of configuration files that can be stored on a LINCS platform. Within that library can be stored the configurations for numerous LINCS platforms. Utilities on the LINCS platform can be used to edit, save, store, or create, configurations for any LINCS node. Only one LINCS node can be designated to contain the LINCS Configuration Library in eManager, at one time. To designate a LINCS node to have the remote library, select the LINCS node from the list in Item View and right-mouse-click, then select 'Node Definitions/Designate as Remote Library'. Note that the option to support the Central Site Configuration Utility must be enabled on the LINCS node configuration to make the library available on the LINCS node itself. The following utilities are provided by eManager to work with this library:

View Library – Displays the LINCS Library panel, by downloading the library catalog from the LINCS Central Site Library, and displaying the contents. From the LINCS Library panel, several actions can be taken with the contents of the library including:

            Edit Library Member – This utility connects to the library member via Telnet to allow editing of the member within the library.

Create Viewable Member – Panel snapshots are taken of the configuration to create an ASCII text file that can be viewed using the ‘View Library Member’ option. This viewable member can not be edited for use on a LINCS platform.

View Library Member – Viewing the ASCII text representation of the configuration provides the means to quickly search for information within the configuration, or to print a hard copy of the configuration.

Write Library Member to Disk – This option allows the library member to be copied to a drive accessible to the eManager PC. This can be a floppy drive, hard drive, or network drive. When written to a floppy, the proper LINCS System 1 disk label is also written to the floppy. This allows the floppy to be used to load the configuration directly into the appropriate LINCS platform.

Create Update from Member – Using this utility, you can create a Configuration Update that can be sent to the appropriate platform using a network connection.

Add Configuration to Library – Selecting this option will allow you to browse through the file system to select a LINCS fig$data.loa configuration file, which eManager will then load into the LINCS Library. This provides an easy means to store new configurations into the library. Note that the dod$cfg.loa file should also be present and will be copied into the library at the same time. (These two files together make up a library member.)

Print Current View – Makes a hard copy of the LINCS Library directory.

Backup Library - Backs up the entire contents of the LINCS Central Site Library from the LINCS node that has been designated to have the LINCS Configuration Library on it. The contents are stored in a directory within the eManager directory structure. The path to this library is: 

            …\eman3000\backup\lincs\lincs library

Restore Library - Restores the entire contents of the library back onto the LINCS node that is designated to have the LINCS Configuration Library.

 

LINCS Event Code Lookup

This utility allows you to enter an event/error code that has occurred or has been reported on a LINCS platform, and eManager will display information about the event or error. This function is also built into the eManager viewer used to display LINCS Event Logs and LINCS Box Failure files, so that you can simply highlight an event entry and display information about the code.

LINCS Utilities

The following utilities are additional utilities for LINCS platforms that can be accessed by selecting a LINCS node in the Item View list, and right-mouse-clicking, then select the LINCS Utilities:

Diagnostic Utilities

Force Dump: The Diagnostic Dump is a tool used by Visara engineers to diagnose software related problems. The process of dumping is disruptive to normal operations of the LINCS server, and should only be initiated under the direction of Visara support personnel with the approval of customer management. Diagnostic Dumps can be initiated on a remote LINCS node, by the eManager administrator. You will be advised by eManager whether the LINCS node is configured to automatically reboot itself (recover) upon the completion of the dump. Because this function is disruptive to users, the initiation process is password protected.

Retrieve Dump: This function allows the eManager administrator to retrieve a Diagnostic Dump from a network attached LINCS node. This dump can be retrieved during normal operation of the node, and is non-disruptive. The dump is written to a folder on the eManager platform, from where it can be copied or mailed to the appropriate support person. There is no practical information for the eManager administrator in the dump, and is intended for Visara engineering support personnel only.

Delete Remote Dump: You can delete a Diagnostic Dump from a remote LINCS platform with this utility. This is not normally a recommended procedure, since LINCS will store as many as 8 dumps at one time (the last 8 to occur), and it is normally better to leave the older dumps in place for possible problem determination.

Retrieve Event Log: You can retrieve and view the Event Log from a remote LINCS server with this utility. Once displayed, you can select individual lines in the Event Log for interpretation by eManager. Note that Event Logs are automatically included in any Backup of a LINCS node, performed by eManager. Viewing those Event Logs are accomplished as a selection from the Backup submenu.

Retrieve Box Fail Log: Every LINCS platform keeps a file associated with box failure occurrences. This file can be retrieved and viewed. Once displayed, you can select individual error events for interpretation by eManager. Note that Box Fail Logs are automatically included in any Backup of a LINCS node, performed by eManager. Viewing the Box Fail Log is accomplished as a selection from the Backup submenu.

ESCON Trace:  LINCS platforms that are host attached through an ESCON interface have a built-in trace facility that is normally running. In situations where Visara engineers request a copy of the ESCON trace to help diagnose a problem, you can use the ESCON Trace utilities to retrieve existing traces or to create a trace and then retrieve it. Additional controls over the ESCON trace facility are available through the Hardware View function.

Retrieve Existing ESCON Trace - This utility connects to the target node and retrieves an ESCON trace that has been saved previously, and displays it in the eManager Viewer. From the viewer you can make a hardcopy or save the trace to another file if desired.

Stop and Retrieve ESCON Trace - This utility will stop the ESCON trace facility, save the trace, then restart the trace facility. The trace will be retrieved and displayed in the eManager Viewer automatically.

View ESCON Trace - This option is to allow you to view a trace that was previously retrieved.

 

Backups

Create Backup: Selecting this menu entry creates a copy of the selected LINCS nodes configuration along with copies of the Event Log and Box Fail Log, and stores them in a subdirectory associated with the selected LINCS node.

Restore Backup: You may select to restore the configuration backup previously created by eManager. In order to restore the configuration, the LINCS platform must already be loaded with software and be available on the network.

Backup File List: Selecting this function will give a list of files contained in a LINCS configuration backup along with the time and date of when the backup was made (eManager time). If no backup has been performed, this utility has no effect.

View Event Log: This selection allows you to view the Event Log that was copied as part of a backup. Once displayed, you can select individual lines in the Event Log for interpretation by eManager. To view the current Event Log, refer to the Diagnostic Utilities discussion above.

View Box Fail Log: You can view the Box Fail Log that was copied as part of a backup, with this selection. Once displayed, you can select individual error events for interpretation by eManager. To view the current Box Fail Log, refer to the Diagnostic Utilities discussion above.

Configuration Panels

The utilities associated with the LINCS Configuration Panels retrieve an ASCII copy of the configuration panels stored on a LINCS platform for reference purposes only. You can not change a LINCS configuration with these utilities, or redistribute this configuration. If the configuration panels have been retrieved from a LINCS node and are available, eManager will mine the information from these panels to help with other functions and recommendations when working with that node. 

Retrieve Panels: This function retrieves a copy of the LINCS configuration panels, and stores it in the backup directory associated with the selected LINCS node. This file is kept in an ASCII text file that can be brought up in a text editor and printed or searched if desired.

This operation can take a few minutes, depending on the number of configuration panels associated with the selected node. An indication of the progress is displayed in the status bar at the bottom of the main eManager panel. When all panels have been collected, the panels will be displayed in the LINCS Configuration Panels viewer.

View Panels: You may use this selection to view panels previously retrieved from a LINCS server in the LINCS Configuration Panels Viewer. You can not edit the contents of configuration with this utility.

Hardware View

Selecting the 'Hardware View' utility while highlighting a LINCS node, will result in an attempt by eManager to graphically represent the hardware configuration of the node that you have selected, and an attempt to establish an interactive connection to the LINCS node. A drawing of what the controller should look like is presented complete with the correct card combination of what has been previously detected by eManager. Both a 'Front View' and 'Rear View' is available for all models except the 1174-15X (Front View only). The hardware information is gathered each time that the 'Collect Data from Nodes' or the 'Retrieve Vital Product Data' functions are run against the LINCS node.

If the hardware information has not been previously gathered for the selected node, you will be advised that the information is not available, and will be offered the opportunity to collect the necessary information.

Since this information is only as accurate as what has been collected from the LINCS node previously, an attempt to update this information should be made whenever hardware has been added or deleted from the node.

Once the hardware diagram has been displayed, you may click on various parts of the hardware diagram to bring up additional information, and initiate the collection of a variety of information.

Some utilities provided by Hardware View are aided by having collected the configuration panels prior to running this utility.

Follow is a list of utilities that can be run with a live connection to a LINCS platform. To initiate one of the utilities, left-mouse-click on the relevant hardware and select from the menu provided.

Base Hardware

·         Retrieve Coax Device Vital Product Data for the entire LINCS platform. The information is stored in a separate database and may be displayed using the View Device VPD menu option from the main eManager panel. You can view Device VPD for a specific LINCS node, or for all LINCS Nodes, depending on whether you initiate the action from selecting the LINCS node category or from selecting a specific LINCS node.

·         Session View - displays in tree form the Host interface adapters, host circuits and configured sessions, along with who owns the sessions currently. The session information is kept current (panel is updated every few seconds), for as long as the information is displayed.

·         Configuration Panels

·         Retrieve Configuration Panels - Retrieves the currently loaded configuration panels from the displayed LINCS platform.

·         View Configuration Panels - Views the currently stored configuration panels from the displayed LINCS platform.

·         Refresh Nickname File - Initiates the reading and implementation of a new Nickname file that has been sent to the LINCS platform as part of a Configuration Update.

·         Display LPD Print Queues - Allows you to display LPD Print Queues for LAN attached printers running the LPD protocol. Print Queue options/utilities include:

·         Release a job that has been put on hold

·         Delete a Job

·         PING remote printer to check network availability

·         Host Trace Facility – Brings up an interface to the Host Trace Facility of LINCS. From this interface you can perform the following:

·         Display the status of the configured Host Monitor traces.

·         Stop a monitor.

·         Clear a monitor.

·         Set filters for the monitor.

·         Start a monitor

·         Retrieve the trace associated with a monitor and display it. This operation allows you to save the trace to a file and to print it.

·         Date/Time Facility – Allows you to interact with the calendar function on the LINCS platform:

·         Get Date/Time – Displays the date and time of the LINCS platform. Note that there is no reference to time zone on the LINCS platform itself. The time zone information is displayed from what has been configured for the node in the eManager database.

·         Set Date/Time – Sets the date and time of the LINCS platform to match the date and time of eManager, corrected for the Time Zone as indicated in the eManager data base.

 

MCC/CDA

·         Display Current Coax Device Status - Provides a red/green/yellow graphic display of which ports have active devices on them. Initiate this function by left mouse clicking on the MCC or CDA card to bring up a menu.

·         View Device Information  - Display current information about individual ports, indicating such things as the type of device, power-on status, how many sessions are configured for the device and their status, whether any coax errors have been recorded for the device, and more.

·         View Device VPD (Vital Product Data) - Displays standard VPD information about the selected device, if the device support VPD or if the LINCS platform has been configured with device VPD.

 

FET/TRC/ETH

·         Display Network Adapter Statistics - for Ethernet and Token Ring cards.

 

ESC/ESX

·         ESCON Trace Facility – Provides an interface to the ESCON Trace Facility that runs on the LINCS platform. Controls provided allows you to set filters on CU and address that you want to trace, as well as provides you the ability to Start, Stop, Clear, Save, Retrieve, and View  the trace. These actions can be taken without affecting the operation of the LINCS node.

·         Retrieve Current ESCON Trace – Stops the ESCON trace and retrieves the trace from the LINCS node, then restarts the trace facility. This action can be taken without affecting the operation of the LINCS node.

 

Front View Touchpad Buttons

·         IML LINCS Platform - Initiates an IML of the LINCS platform. A warning is given prior to initiating the platform, to allow you to cancel the operation.

·         Create Dump - Initiates a Dump of the LINCS platform. A warning is given prior to initiating the platform, to allow you to cancel the operation.

 

LINCS Configuration Panels Viewer

The LINCS Configuration Panels Viewer allows you to view a LINCS configuration that has been previously retrieved, using the LINCS Utilities/Configuration Panels/Retrieve Panels function. This panel does not allow you to edit the contents. If you wish to edit the contents for some reason (creating documentation for example), you can view the configuration and save the file to a new location. Then use a text editor as needed.

To bring up the viewer, right-mouse-click on a LINCS node in the Item View, and select the View Panels option. You can also view the configuration from Hardware View. If a copy of the configuration has been retrieved, the viewer will be displayed, and a copy of the first configuration panel will be displayed. If the configuration has not been retrieved, then you will be allowed to initiate a retrieval of the configuration. When the configuration is being viewed, the buttons to the right of the panel information have the following functions:

·         Next: Displays the next configuration panel. If the last configuration panel is displayed, nothing happens.

·         Previous: Displays the previous configuration panel. If the first configuration panel is displayed, nothing happens.

·         First: Displays the first configuration panel.

·         Last: Displays the last configuration panel.

The edit field below the <Last> button allows you to type in a panel number. When a valid panel number has been entered and the <Enter> key is pressed, the panel indicated by the number will be displayed.

The date and time that the configuration panels were retrieved are displayed on the lower right hand side of the panel.

Search functions:

The edit field allows you to enter a text string. The search function is case sensitive, so be careful to select the specific string that you wish to find.

The <Next> button initiates a search forward through the information. The <Prev> button initiates a backward search through the information.

 

LINCS Patch Manager Panel

The LINCS Patch Manager Panel provides a set of tools that allows you to quickly determine the patch status of your LINCS platforms, install or remove patches from those units, and view patch information. LINCS patches are available for specific integration levels of LINCS code. The LINCS Patch Manager ensures that only levels of code designed to accept patches are updated with the patches. Additionally, the LINCS Patch Manager ensures that the integrity of the code is maintained when removing patches to ensure only the files that need to be removed are, based on whatever other patches are installed.

The prominent areas of the Patch Manager panel are as follows:

Patches Available - This is a tree structure displaying all of the patches that eManager has available to update LINCS platforms with. The patches are separated by integration level. When new patches are retrieved, eManager will unzip the patch and place it into the proper location within its file structure. If you select a patch in the tree structure, the patch information is positioned into the 'Patch' staging area, and a brief description appears in a note area below. Double-clicking on a patch in the structure opens a separate window with a fully detailed description of the patch.

Remote Node - The Remote Node area will display a list of patches installed on the remote node, if you select a remote node icon from the LINCS Nodes view, and press the <Installed Patches> button.  Selecting a patch in the list will display a brief description of the patch in the area below, and the patch information is positioned into the 'Patch' staging area.

LINCS Nodes/Code Update Selections and View Area - The view area will show LINCS Nodes icons or Code Update icons, depending on which control is selected. Expanding the size of the window will increase the icon viewing area accordingly. Selecting an icon in the view area will fill in the 'IP Address' and 'FTP Password' fields in the staging area.

Staging Area - The staging area consists of three fields entitled 'IP Address', 'FTP Password', and 'Patch'. When these three fields are filled in, the <Install New Patch> and <Remove Patch, buttons can be used to install or remove the indicated patch from the indicated LINCS platform.

Button Descriptions:

Installed Patches - Used to retrieve information about the patches installed on the LINCS platform that was last selected. Information retrieved will be displayed in the 'Remote Node' field.

Install New Patch - Used to initiate the installation of the last patch selected onto the last LINCS platform selected. The patch and LINCS platform information will be in the staging area.

Remove Patch - This button is used to initiate the removal of the selected patch from the selected LINCS platform.

Get Patch - Allows you to browse the file system to retrieve a patch that has been stored or downloaded. When you locate the patch that you want, eManager unzips the patch and sticks it into the eManager Patch Manager file structure.

Reboot Node - This option will initiate a reboot of the selected node. Since this action will take down the remote node briefly, the action is password protected.

Exit - Exits you from the Patch Manager panel.

 

SSL1000 Hardware View

Selecting the 'Hardware View' utility while highlighting an SSL1000 node, will result in an attempt by eManager to graphically represent the hardware configuration of the node that you have selected, and an attempt to establish an interactive connection to the SSL1000. A drawing of what the SSL1000 should look like is presented. Both a 'Front View' and 'Rear View' is available. From the displayed model several things can be done. By moving the mouse to point at various items in the diagram, eManager will attempt to identify many of those items.

Right-mouse-clicking the diagram will display a menu to provide access to several utilities. These include:

Rear View – Displays a rear view diagram of the SSL1000

Front View – Displays a front view diagram of the SSL1000

Show Connections – Displays a panel containing a list of the current connections through the SSL1000 platform. From this panel you can highlight a user and disconnect them. Information on the panel is updated every few seconds. Included with the information displayed is:

·         Session ID – A reference number assigned by the SSL1000 when a new connection is made

·         IP Address – The IP address of the user that is connected

·         Mapping Profile – The name of the profile as defined in the SSL1000 configuration, that is being used for the connection

·         Host IP/Port – The IP address and the TCP port that the user has been directed to on the upstream LINCS platform

·         SSL – Indicates whether SSL encryption is being used for the connection or not

·         Connected Since – Indicates how long the user has been connected through the SSL1000

Reboot Server Platform – Reboots the hardware platform that the SSL1000 is running on. Note that this operation will terminate all connections between the users and the upstream LINCS platform.

Reset SSL Server – This utility stops the SSL server software, but does not reboot the platform. Once stopped the SSL server is restarted. Note that this operation will terminate all connections between the users and the upstream LINCS platform.

Change SSL Administrator Password – Changing the password will affect access to the SSL server for management purposes. The new password will be entered into eManager’s database as encrypted information, and will be used by eManager for subsequent connections.

Date/Time – Two options are offered:

·         Get Time – Retrieves the current date, time, and time zone information from the SSL1000

·         Set Time – Sets the date and time to match that of eManager, taking in to account the current Time Zone information configured on the client

 

 

The LINCS Library interface provides a set of tools to help with managing the configuration files for the LINCS nodes in your network, through its connections to the LINCS Central Site Library utility configured on one of your LINCS nodes. The LINCS Central Site Library acts as a central repository for storing the configuration files for any or all of the LINCS nodes on your network. The main reason for setting up a Central Site Library is to provide backup redundancy of existing configurations with the necessary tools to allow them to be edited in a central location. (LINCS configuration files can not be directly edited on a PC in a text editor.) eManager provides the means to streamline the interface into this library. Among the tools provided by eManager are:

ICON Hardware View

Selecting the 'Hardware View' utility while highlighting an ICON node, will result in an attempt by eManager to graphically represent the hardware configuration of the node that you have selected, and an attempt to establish an interactive connection to the ICON. A drawing of what the ICON should look like is presented. Both a 'Front View' and 'Rear View' is available when displaying the ICON-20T. A single image that contains both the Front View and Rear View of the ICON-1T is displayed. From the displayed model several things can be done. By moving the mouse to point at various items in the diagram, eManager will attempt to identify many of those items.

Right-mouse-clicking the diagram will display a menu to provide access to several utilities. These include:

Rear View – Displays a rear view diagram of the ICON

Front View – Displays a front view diagram of the ICON

Show Connections – Displays a panel containing a list of the current connections through the ICON platform. From this panel you can highlight a user and disconnect them. Information on the panel is updated every few seconds. Included with the information displayed is:

·         Session ID – A reference number assigned by the ICON when a new connection is made

·         IP Address – The IP address of the user that is connected

·         Host – The Host connection name that the user has been directed to

·         User Name – Indicates which user name the user connected in on

Reboot Server Platform – Reboots the hardware platform that the ICON is running on. Note that this operation will terminate all connections between the users and their host connections.

Date/Time – Two options are offered:

·         Get Time – Retrieves the current date, time, and time zone information from the ICON

·         Set Time – Sets the date and time to match that of eManager, taking in to account the current Time Zone information configured on the client

LINCS Library Interface

The LINCS Library interface provides a set of tools to help with managing the configuration files for the LINCS nodes in your network, through its connections to the LINCS Central Site Library utility configured on one of your LINCS nodes. The LINCS Central Site Library acts as a central repository for storing the configuration files for any or all of the LINCS nodes on your network. The main reason for setting up a Central Site Library is to provide backup redundancy of existing configurations with the necessary tools to allow them to be edited in a central location. (LINCS configuration files can not be directly edited on a PC in a text editor.) eManager provides the means to streamline the interface into this library. Among the tools provided by eManager are:

  • Backup and Restore of the LINCS Central Site Library (these backups can be initiated in real time, or by scheduling a backup job)
  • A connection (via Telnet) to edit an existing Library Member without having to navigate the LINCS Central Site panels
  • A shortcut menu on the LINCS Telnet interface: to allow you to jump to specific locations in the configuration that you are editing, without having to navigate to those panels manually.
  • A utility to capture the current configuration panel information into a text file that can also be viewed from eManager or from a PC text editor (and printed).
  • The means to enter new library member directly from eManager, by browsing to the configuration file location, and checking it into the library.
  • Print the directory of the Library.
  • Copy a library member to a disk location.
  • Copy a library member into a Configuration Update.

Any LINCS node can house a Central Site Library for your network, in addition to its normal duties. To create a Central Site Library on a LINCS node, you must enable the Central Site Customization option in the configuration of that node. To put this option into affect after configuring for it, the LINCS node must be rebooted.

To provide eManager with the knowledge of which LINCS node it is to use as the LINCS Library, select the LINCS node from the list, right-mouse-click, and select the ‘Node Definitions/Designate as LINCS Library’ option from the menu. Only one LINCS node can be designated as the current LINCS Library at a time for eManager. You can however work with multiple libraries by changing which node is designated as the library.

You can also transfer a library from one LINCS node to another by first selecting the first node as the library and performing a backup. Then select the second LINCS node as the current library, and perform a restore of the library. Using this method you can back up the entire library onto a second platform.

 

 

ETerm 300, 360, and 760 Utilities

The following section describes utilities provided for the eTerm 300, 360, and 760 products. These utilities are run one-on-one with a terminal to provide a mechanism for making changes to that nodes configuration.

Change Terminal Properties

You can make changes to the configuration of an individual node, by right-mouse-clicking a node in the eTerm 360 category Item View list, and selecting eTerm 360 Utilities/Change Terminal Properties. Among the properties that can be reconfigured are:

·         Input and Volume

·         Time Zone

·         Network

·         Security

·         LPD Printer

·         Display

·         Internet Options

·         RDP Settings

·         SNMP

·         Thin Print

·         Desktop Options

·         Desktop Style

·         VNC Viewer Settings

·         FTP Update

Change Host Connections

Changes to the Host Connection settings can be affected on an individual node basis using this utility. To invoke this utility, select a node from Item View, and right-mouse-click to display the menu. Select eTerm 360 Utilities/Change Host Connections. RDP, ICA, TN3270, TN5250, and ASCII Host Connections can be changed in this manner.

 

Pulse Network Monitor

The Pulse Network Monitor is a function provided by eManager, that when configured, allows eManager to monitor the availability of nodes on the network by periodically sending a PING to each node configured to be monitored.

Nodes are selected for monitoring by customizing the eManager Options panel, found on the Pulse tab.

Pulse can be activated and deactivated from a menu selection on the main eManager panel. You can also configure Pulse to activate automatically when eManager is booted.

While Pulse is running, a log is kept of the results. What goes into the log is determined by the configuration of Pulse. In addition to providing an entry of when Pulse is activated and deactivated, you can configure two types of events to be logged.

·         Node Come Up Event - Node starts responding to Pulse after failing to respond to previous attempts at contact.

·         Node Go Down Event - Node stops responding to Pulse after events where a good response was received.

When Pulse is activated, initial node status events are logged for devices based on the setting of the Come Up Event or Go Down Event as if all devices just made a transition.

The log may be viewed, cleared, or written to either a text or CSV file. When viewed, the view represents a snapshot of the log at the time that the view was requested (it is not dynamically updated with new information).

The maximum size for this log can be determined by the Pulse configuration options, but is not to exceed 2 MB.

In addition to the log, a limited history (approximately 10-20 events logged) is kept for each node that is being monitored. You can view an individual nodes monitor history by first selecting View Network Monitor from the Pulse menu, finding the individual node in the monitor that you wish to view the history on, then right click the node to allow you to view the nodes monitor history. You can also clear the nodes monitor history without affecting the history of the other nodes, or the entries for that node in the Pulse log.

The frequency that Pulse will contact an individual node can be configured on the Pulse tab. Values from 1 minute to 120 minutes can be configured. Pulse makes contacts with the network nodes in cycles, based on the configured intervals. That is, at the beginning of each cycle a list of nodes that is to be monitored is created, and each node is contacted one time by Pulse. The result of the contact attempt is reviewed by Pulse and the log and history are updated as needed. When all nodes that are to be contacted have been attempted, the cycle is complete and Pulse will wait until the next scheduled cycle time to make another attempt. Determining the frequency value is partly a matter of judgement and partly a matter of the number of nodes to be monitored. For local networks 200-300 node contact attempts can be made by Pulse in a minute. If you have 1000 nodes to monitor, Pulse typically requires 4-5 minutes to complete a cycle. If the interval is set too short, the result is that Pulse will begin the new cycle immediately following the completion of the previous cycle. (Pulse does not abort a cycle to begin the next.)

 

Determining the Nodes to be Monitored

The nodes to be monitored are determined by the configuration of the Pulse monitor. You can elect to monitor all nodes, or groups of nodes. If there are duplicate node entries in the eManager database for a particular node, each entry will generate a contact attempt, and each entry will have its own icon representation when view monitor status.

When selecting to monitor all nodes, every node definition found in the eManager database will be monitored. When viewing the network monitor, the initial display panel will show an icon for each subnet that has nodes defined to them. You can double-click individual subnet icons to display the nodes being monitored on that subnet.

Selecting to monitor individual groups, allows you to limit the monitoring to fewer than all nodes. Groups can be created to include any selection of nodes desired. When monitoring groups, every node that is part of one of the groups being monitored will be compiled into the list of monitored nodes. Adding the same node definition to two or more groups does not result in Pulse contacting the node multiple times per cycle. Pulse contacts a single database entry one time only. When viewing the network monitor, the initial display panel will show an icon for each group, including groups that do not have any nodes defined to them. You can double-click on a group icon to display the individual members of that group.

Monitoring Nodes that are not Visara Products

You can define nodes to be monitored by Pulse that are not supported Visara products. This is accomplished by electing to allow support for the 'Unknown' category in the eManager Options panel, Node Types tab.

You can define nodes of device types unknown to eManager by highlighting the 'Unknown' category on the main eManager panel in the Network Node section of Folders View, then right-mouse-clicking the category to add a node definition. Unknown nodes are limited to supplying a name and address and adding some comments.

You can create groups under the Unknown category and drag Unknown nodes into those groups for monitoring purposes.

Monitoring Groups of Mixed Device Types in a Single Group

For distribution reasons, nodes of multiple varieties are not allowed to be included in any of the standard groups set up under the Node Types categories. However, if you establish the Unknown category and create a group within that category, you can drag devices defined to the various product categories into the Unknown groups for monitoring purposes.

Viewing the Status of the Monitor

The current status of the Pulse network monitor can be viewed at any time by selecting View Network Monitor from the Pulse menu item. The initial display will show icons representing either groups or subnets (see Determining Nodes to be Monitored). The icons on this panel will have a background color of red, yellow, green, or none, which represents the current status of the subnet or groups based on the last contact attempt by Pulse.

For subnet and group icons, the color represents:

·         Red - No response received from any of the nodes monitored that are part of the subnet or group

·         Yellow - Some nodes that are part of the group or subnet are responding and some are not

·         Green - All members of the group or subnet are responding

·         None - Contact to one or more members of the group or subnet has not occurred yet (initial state when Pulse is enabled)

Double-clicking the subnet or group, results in another panel appearing that displays the individual nodes that make up the subnet or group.

For individual node icons, the color represents:

·         Red - No response received from the last two contact attempts

·         Yellow - No response to the last contact attempt (previous attempt was successful)

·         Green - Successful response to the last contact attempt

·         None - No contact attempt has been made (initial status when monitor is started

Additional information can be displayed on individual nodes by right-mouse-clicking the node. You can view the nodes vital data, view the monitor history for that node, or select to clear the monitor history for that node.

Using the Pulse Log

The Pulse log is kept so that you can review the activity observed by the network monitor. The log itself is kept in a file, using a shorthand form for the raw data. Shutting down eManager, stops the network monitor if it is running, but does not delete the log. You can later start up eManager and work with the log, without having lost the contents of the log.

From the Pulse menu item on the main eManager menu, you can select to view the log, clear the log, or save the log to a file. Saving the log to a file you will be allowed to save the log as a text file for viewing with a text editor, or as a CSV file, that can be imported into a spreadsheet.

The log is maintained and appended to, through multiple starts and stops of Pulse. When the log becomes too large, old data is discarded from the file and the new data is added.

Viewing the Pulse Log

You can view the contents of the Pulse Log using the viewer provided with eManager. When viewing the log from eManager, the log file is massaged to create another file that is then opened by the viewer. The eManager log file for Pulse is left intact and will be appended to, with new data if the monitor is running.

The viewer allows for you to scroll through the contents of the log. You can page forward and backwards through the log, as well as jump to the beginning, last or a specific page within the log.

You can also search for text strings within the log using the search capability of the viewer. The search capability is case sensitive, so keep that in mind when you use it.

 

Backup Jobs

The purpose of Backup Jobs are to backup the configuration of nodes in your network to make it easier to restore their configuration at a later date if necessary. All Visara node types can have rather sophisticated configurations, and in some cases those configurations may vary considerably from one node to another. If a hardware failure occurs, or if a configuration is changed significantly, it may be desired to be able to restore a previously stored configuration in a timely fashion.

By scheduling backups of your nodes on a regular basis, it may be possible to have that previously stored configuration available without spending a great amount of time, personally gathering this information.

How to create a Backup Job

Backup Jobs are created on the Job Creator panel. Backup Jobs are dedicated to a particular node type, so if you have a variety of Visara node types in your network, you may need to create multiple jobs to backup everything that you need. You have an option to indicate the number of backups each node is allowed. If more backups already exist than you indicate with this job, the extra backups will be deleted as part of the job execution. Creating the job does not automatically schedule it. Scheduling the job is a separate operation.

How to Schedule a Backup Job

Backup Jobs are scheduled on the eManager Options panel, Scheduler tab, accessed by pressing the <Options> button on the main eManager panel. The Scheduler is used to schedule a variety of jobs, so you must select the 'Node Backups' Job Type from the drop down list. A list of all Node Backup jobs will be displayed, indicating status, scheduled execution date and time, and whether the job is recursively scheduled. Select the job from the list and right-mouse-click to bring up an activity menu. Select 'Change Schedule' from the menu, and fill in the desired date and time for the job. You can also indicate whether the job is to repeat and how often. Once these options have been set, check the 'Pending' checkbox. The status for your job in the list should change to Pending. If the date/time indicates the past, you will be warned when you check the Pending box that your job will commence immediately, giving you the opportunity to cancel the execution. Whenever a job is Pending or Executing, the 'Jobs' icon will appear on the main eManager panel. Clicking that Icon will bring you back to this panel.

How to Cancel a Backup Job

You can cancel a job by selecting the job from the list, and right-mouse-click to bring up the activity menu. Select 'Cancel Execution' from the menu. If the job is executing, it will terminate at the first convenience. If the job is pending, the job status will change to 'Not Scheduled'.

How to Restore a Backup

Backups are restored on an individual node basis. Depending on the situation, the task may be as simple as selecting the node in the Items View of the main eManager panel, right-mouse-click to bring up a menu, and select 'Backups\Restore Backup'. You will be given the choice of the existing backups for that node. The last backup taken from the node will be identified by the selection 'Restore Last Backup'. Other, older backups will be identified by date and time. If you wish to view the date and time of the current backup, you can double-click the node in Items View to display information about the node, which includes date of last backup. Most configurations are sensitive to the version of code running on the platform. If you are replacing an existing node with another, or if you have recently changed the level of code running on the node, you may not be able to restore the backup. If you are unsure, check with Visara support personnel prior to attempting the restore. Restoring a configuration to a node with the wrong code version could result in corrupting the nodes ability to function.

eManager Database Backup Job

The eManager Database Backup Job allows you to schedule the backing up of the main database used by eManager to a destination of your choice. The destination currently must be a location that you can browse to through Windows Explorer. You should take care to ensure that the destination is other than on the same hard drive that you are running eManager from. This can be on a separate platform available through the network.

It is recommended that you back the database up on a daily basis.

How to create an eManager Database Backup Job

Backup Jobs for the eManager database are created on the Job Creator panel. The 'eManager Database Backup Job' is created by selecting the 'eManager' node type from the dropdown list, then selecting the 'Backup Database' option under the Job Type. You have an option to indicate the number of backups of the database that are allowed. If more backups already exist than you indicate with this job, the extra backups will be deleted as part of the job execution. Creating the job does not automatically schedule it. Scheduling the job is a separate operation.

How to Schedule an eManager Database  Backup Job

The eManager Database Backup Job is scheduled on the eManager Options panel, Scheduler tab, accessed by pressing the <Options> button on the main eManager panel. The Scheduler is used to schedule a variety of jobs, so you must select the 'Backup Database' Job Type from the drop down list. A list of all eManager Database Backup jobs will be displayed (usually only one), indicating status, scheduled execution date and time, and whether the job is recursively scheduled. You can also view the last completion date and time. Select the job from the list and right-mouse-click to bring up an activity menu. Select 'Change Schedule' from the menu, and fill in the desired date and time for the job. You can also indicate whether the job is to repeat and how often. Once these options have been set, check the 'Pending' checkbox. The status for your job in the list should change to Pending. If the date/time indicates the past, you will be warned when you check the Pending box that your job will commence immediately, giving you the opportunity to cancel the execution. Whenever a job is Pending or Executing, the 'Jobs' icon will appear on the main eManager panel. Clicking that Icon will bring you back to this panel.

How to Cancel the eManager Database Backup Job

You can cancel a job by selecting the job from the list, and right-mouse-click to bring up the activity menu. Select 'Cancel Execution' from the menu. If the job is executing, it will terminate at the first convenience. If the job is pending, the job status will change to 'Not Scheduled'.

How to Restore a Backup

There is no utility currently for restoring a backed-up database. You can restore it rather easily by copying it to the 'eman3000' directory, usually found as a subdirectory to the 'Program Files' directory (depending on where you installed the eManager program initially). You may want to rename the current file name, unless you are sure that you will not need it. The name of the main eManager database is 'emanager.mdb'.

LINCS Library Backup Job

The LINCS Library is a repository of configuration files that can be created and edited on a LINCS platform. Within this library you can maintain a collection of all of the configurations for all of your LINCS platforms in a single, central location. The purpose of the LINCS Library Backup Job, is to schedule on a regular basis, the duplication of the LINCS Library, if you are using one, to a location other than on the LINCS node where the library normally exists, to prevent loss if the LINCS node's hard drive fails. The backup of this library is kept in the eManager directory structure, specifically in the '…\eman3000\backup\lincs\lincs library' directory.

Creating the LINCS Library Backup Job

The LINCS Library Backup Job is created on the Job Creator panel. Since this library is unique to LINCS platforms, you must first select LINCS as the node type, then select 'Backup LINCS Library' as the job type.

Scheduling the LINCS Library Backup Job

The LINCS Library Backup Job is scheduled on the eManager Options panel, Scheduler tab, accessed by pressing the <Options> button on the main eManager panel. The Scheduler is used to schedule a variety of jobs, so you must select the 'Backup LINCS Library' Job Type from the drop down list. A list of all LINCS Library Backup jobs will be displayed (usually only one), indicating status, scheduled execution date and time, and whether the job is recursively scheduled. You can also view the last completion date and time. Select the job from the list and right-mouse-click to bring up an activity menu. Select 'Change Schedule' from the menu, and fill in the desired date and time for the job. You can also indicate whether the job is to repeat and how often. Once these options have been set, check the 'Pending' checkbox. The status for your job in the list should change to Pending. If the date/time indicates the past, you will be warned when you check the Pending box that your job will commence immediately, giving you the opportunity to cancel the execution. Whenever a job is Pending or Executing, the 'Jobs' icon will appear on the main eManager panel. Clicking that Icon will bring you back to this panel.

Canceling the LINCS Library Backup Job

You can cancel a job by selecting the job from the list, and right-mouse-click to bring up the activity menu. Select 'Cancel Execution' from the menu. If the job is executing, it will terminate at the first convenience. If the job is pending, the job status will change to 'Not Scheduled'.

How to Restore a LINCS Library Backup

The most recently backed up Library can be restored to the node that is designated as the LINCS Library, by using the Restore LINCS Library function from the main eManager panel. Select the LINCS Node category from Folders View and right mouse click. Select 'LINCS Configuration Library/Restore Library'.

 

Appendix A – Installing And Removing

System Requirements

To install and use Visara eManager, you need:

·         Personal computer with a Pentium 75-megahertz (MHz) or higher processor. Faster processors in the 200 MHz range and higher are recommended, for better eManager performance.

·         Microsoft Windows® 95, Windows 98, Windows 2000, or Windows XP operating system, or Microsoft Windows NT Workstation operating system version 4.0 or later, with Service Pack 4 or later

·         For Windows 95 or Windows 98: 32 megabytes (MB) of RAM
(16 MB of RAM for the operating system, plus an additional 16 MB of RAM for eManager). You will need additional memory as required by other applications. More memory can help speed up operations.

·         For Windows 2000 or Windows NT Workstation version 4.0 or later with Service Pack 4 or later: 48 MB of RAM
(32 MB of RAM for the operating system, plus an additional 16 MB of RAM for eManager). You will need additional memory as required by other applications.

·         Additional memory beyond the minimums should improve performance and is recommended.

·         Available hard-disk space - For typical installation, 40 MB of available hard-disk space is required as a minimum. Because of the large binary image files required by some of the node types managed by eManager, a more practical requirement may be in the 150 MB-500 MB range.

·         CD-ROM drive

·         VGA or higher resolution monitor; Super VGA recommended

·         Most eManager panels are optimized to be used with an 800 x 600 screen resolution. Higher resolution may be desirable.

·         Microsoft Mouse or compatible pointing device

·         If Internet Explorer is used on the same platform that eManager is installed on, it is recommended to use IE5.5 or higher. Some of the functionality required by eManager makes it incompatible with levels of IE prior to IE5.0.

·         Winsock 2.0 or higher (comes standard on most Windows platforms). For Windows 95, you may need to upgrade Winsock to version 2.0. The upgrade is free from www.microsoft.com . Search for "winsock2" and follow the download and install instructions. This upgrade is not included with eManager, and there is no immediate warning if it is not installed. You will have problems when using eManager and PINGs are used. (eManager may PING a node before attempting contact in many instances.)

·         Windows 2000 systems do not allow the eManager installation program to update the wininet.dll file, used by eManager for its FTP interface. If you get an error attempting to install eManager onto a Windows 2000 system, referring to the wininet.dll file, you may need to put the latest service pack for Windows 2000 on that platform, prior to installing eManager.

·         When running on an OS where multiple user accounts are allowed (such as on Windows XP), you should be logged on with administrator privileges.

Ports and Protocols used by eManager

eManager uses a number of IP protocols to do its management work, so it may be necessary to implement certain changes on your network, in order to perform some functions. Some processes allow for PINGs to be blocked, but eManager must be configured to expect this. The following table shows which protocols are used to manage various products:

Node Type

Protocols

eTerm 350

SNMP – Port 161, 162
PING
FTP – Port 21

NCT 1683, NCT 1783

SNMP – Port 161, 162
PING
FTP – Port 21
Telnet - Port 23

Linux Nodes: 1883, 300LX, 400LX, 500LX, 600LXe,610LXe

SNMP – Port 161, 162
PING
FTP – Port 21
Telnet – Port 23
WOL – Port 1954
VNC – Port 590x

Win CE Nodes: e300, e360, e760, 300CE, 400CE

SNMP – Port 161, 162
PING
WOL – Port 1954
VNC – Port 590x

Win XPe Nodes: 600XPe, 610XPe

SNMP – Port 161, 162
PING
WOL – Port 1954
VNC – Port 590x

LINCS Nodes: 1174, SCON

SNMP – Port 161, 162
PING
FTP – Port 21
Telnet – Port of your choosing

 

Installing eManager

To install, run setup.exe from the eManager CD and follow the installation prompts.

If you already have a copy of eManager installed, you should uninstall the existing copy prior to installing the new copy if you are installing version 2.2.0 or previous versions. See Uninstalling eManager below.

If your system files are up to date, the installation process completes in one pass. However, if any files are down level, two installation passes are required. The first time you run setup.exe, the install routine updates the system files and requires the system to be rebooted. After the system has rebooted, you must run setup.exe again to install eManager.

If you encounter problems installing eManager on a Windows 2000 platform, you may have to upgrade your Windows 2000 platform with the latest service pack, prior to installing eManager.

Uninstalling eManager

When upgrading to eManager version 2.2.1 or higher, all you need to do is run the setup program that is part of the new version. For installing previous versions of eManager, you should first remove any existing version. See instructions that follow.

To Uninstall eManager, use the Add/Remove programs function provided in Windows Control Panel. To access Add/Remove programs, click Start on the Start Menu, then click settings. This displays the Control Panel. In Control Panel, double click Add/Remove programs. Scroll through the list of programs and select Visara eManager, then click the <add remove> button and follow the prompts.

Uninstall will not remove files that have been created or modified since the installation was done. For example, eManager creates the database file used to store node information in, and several directories. If files have changed, the eManager directory structure and these files are not deleted. This preserves the database when reinstalling eManager to the same directory. All relevant licensing information related to eManager is also maintained through a normal remove program operation.

In all cases, it is important to ensure that eManager is not running when attempting to remove the version, or install a new version.

Updating eManager

When upgrading to eManager version 2.2.1 or higher, you need only run setup on the new version. The install process will remove older versions installed in the same directory as the new install. Otherwise use the procedure that follows.

To update eManager from an older version to a higher version, it is recommended that you first uninstall the old version, then install the new version in the same location previously occupied by the old version. Your serial number, license, and data files will be maintained through the process. If you install a new version over top of an older version, you may get multiple entries for eManager appearing in the installed programs list. This should not affect the operation of eManager, but may add confusion when viewing installed programs information.

It is also recommended that you reboot your PC after you have installed an update. Sometimes the new install does not properly handle the installation of the PING client used by eManager. See the troubleshooting reference to this problem below.

 

Appendix B – Troubleshooting

1883 Pull Update Does Not Complete Without Manual IML

The 1883 is not capable of accessing files from an FTP server under some circumstances. Try putting the files required by the 1883 in a directory just off the root directory (do not put the files into a directory that is nested further down in the tree). It is also recommended to keep the filenames of the upgrades short.

 

Unable to Establish a Connection to a 1683, 1783, or 1883

The products listed above, will not allow a Telnet or FTP connection (used by eManager) to become established in a timely fashion if the DNS configuration of the nodes is not correct. Insure that the DNS information is correct, then try again.

Another possible cause for failure may occur if the connection password has been changed from the factory default. eManager keeps track of changes to the connection password, if the changes were implemented through eManager. If the passwords were changed through some other means, you will need to edit the node information for each node within eManager, to inform eManager of the change so that eManager can communicate with the nodes.

Unable to Upgrade a 1683

Versions of the 1683 prior to IL 42 were not compatible to eManager. You will need to upgrade the unit by some other means to a level of IL 42 or higher, prior to using eManager with it.

 

Unable to Establish Communications with an eTerm 350

The eTerm 350 has a configuration item associated with management from eManager. If this option has been disabled, the 350 will not communicate with eManager.

 

Error Trying to Make Phindows Connection to a 1683 or 1783

Check the eManager Options panel to make sure that the path to the Phindows application is correct and that the command line information is correct. You can press the default key for the Phindows command line information and save it if you have any doubts about the configured information being correct.

 

Unable to View Full Screen of 1683/1783 When Using Phindows

The only way to view the full screen of a target device using Phindows is if the monitor of the platform eManager is running on is at the same resolution or higher than the target node.

 

Unable to Type into a Host Session Through Phindows

A fix is required on the 1683/1783 to allow typing into the host session, and is not an eManager problem. This fix was initially released as Hot Flash 50.10.

 

Runtime Error Occurs During Distribution Plans or AutoLocation

You may have the number of concurrent FTP sessions set too high for your environment (PC/Server that eManager is running on or network speed/congestion levels). Check the number of concurrent FTP sessions that are allowed on the eManager Options Network tab, and reduce the number and retry the operation. Although effort has been put into avoiding runtime errors, if too many sessions are opened at once, timing/processor task situations may arise that can cause eManager to hang.

 

Runtime Error Occurs

A runtime error event should be reported to Visara for correction using normal problem reporting procedures. Please take note of as much detail as possible about what you were attempting to do at the time the error occurs.

 

Appearance of an Error Message Box Referencing the Multiping client of eManager After Upgrading the Version of eManager

This is a known problem in eManager, and sometimes occurs after the version of eManager has changed. Rebooting the PC that eManager is installed on one time should take care of this problem.

 

"Error Processing Ping Job" Message

This message occurs on Windows 95 PCs when Winsock 2.0 is not installed. You can get this update from the Microsoft web site. You can also encounter this problem if you are running on a Windows 2000 or Windows XP platform and do not have administrator rights.

 

"Please Check Network Speed Performance or Try Again" Message

This problem is typically related to managing certain Visara Windows CE thin clients. This problem can be corrected by upgrading to eManager version 2.2.1 or higher.

 

Not All Configuration Options are Backed Up from Certain Windows CE Platforms

This is a limitation of the Windows CE platform, not eManager. In this instance, not all options are being passed to eManager, so the missing options can not be restored to the node later. You may have to upgrade the Windows CE platform to a higher code version and reconfigure options as necessary. Using the FTP upgrade utility on the thin client platform may yield better results on older code levels.

 

Multiple Entries of the Visara eManager product in the Installed Software List

You did not run the Remove Software utility of Windows before installing a newer version of eManager. This problem should not occur normally when installing version 2.2.1 or higher. Having multiple entries in the list should not normally cause any problems, but the next time that you attempt to install a new version of eManager, remove each of the instances of the Visara eManager. The first one should remove itself without error. The subsequent removal(s) will give you an error message of missing files, because they were already removed, but the remove software function should eliminate the extra entries from the list.

Difficulty AutoLocating Nodes

Initial detection of nodes by eManager makes use of a combination of SNMP and PING frames. If both are being blocked on your network, then you will not be able to AutoLocate nodes. Depending on the node type, additional protocols may be used to gather additional information from the nodes. Protocols used include FTP, Telnet, and socket connections. A more complete list is available in the install section of this document. You may also need to ensure that you are using the right subnet mask for the network that you are attempting to AutoLocate on. A setting on the eManager Options panel allows you to define the default subnet mask that eManager is to use (but you can use whatever mask you want to for each AutoLocate job).
If you feel confident that you are not blocking the protocols that eManager uses, make sure that you are running eManager version 2.2.1 or higher. If you still are having problems, please contact Visara support representatives.

Unable to FTP Code and Configurations

If you get consistent failures when trying to Push or Pull code and configurations between eManager and the remote nodes, you may need to check the ‘Use Passive Mode’ option on the eManager Options panel, Network tab. Most firewalls block normal FTP operations but may allow Passive Mode FTP operations.

Appendix C – Using eManager in a DHCP Environment

Working in a DHCP environment with eManager adds a level of complexity to managing the code and configurations of your nodes, since the IP addresses of the nodes may change from time to time. The main tool provided by eManager for keeping track of your desktops when their IP addresses are changing is the AutoLocate feature. AutoLocate does more than just find your devices initially. As part of the AutoLocate process, information specific to the desktop is pulled from the node and stored in the database.

Using AutoLocate to Generate Your Initial Node List

You can locate powered on desktop nodes with eManager, using the AutoLocate utility. To create your list initially, you will want to select the option to Always Add New Record under the Successful Contact Options. You may want to create a useful base name for eManager to use when constructing the new records. These names can be edited later if needed. Since the address is not fixed, you will probably want to use the Increment option under Name Suffix Options.

If you know that all of the nodes associated with a subnet or range of IP addresses are to be part of the same department, and you will work with them as a group for configurations or code updates, you should consider assigning the nodes to a group when they are detected initially. This can be accomplished by selecting the Assign to Group checkbox and selecting the appropriate group name from the dropdown box.

Using AutoLocate to Update Your Existing Node List

Once you have defined the nodes on the network to eManager and have assigned them to their appropriate distribution groups, you can update the information gathered on the nodes, by running a new AutoLocate procedure. This time you will want to select the Update Existing Record option under Successful Contact Options, and select the appropriate Update Option (usually you will want to select Match Serial Number or Hardware Address). By using this method, eManager will simply update existing records in the database with any new information collected for the known nodes, and will add new records if a new node is found that is not currently identified in the database. AutoLocate jobs can be scheduled to run automatically using the Job Scheduler on the eManager Options panel.

Distributing to DHCP Clients

Prior to any distribution to your clients in a DHCP environment where DNS names are not used, you will need to run the AutoLocate function to identify the latest IP address for the nodes, since eManager will need this information to perform the distribution.

Working in DNS Environments

If DNS names are used for all of the desktop clients, and the names are automatically updated when DHCP assigns new addresses, you can create distributions where the DNS names are used for distribution purposes, rather than IP addresses. This allows you to perform distributions without having to perform the AutoLocate function.

 

Copyright © 2006 Visara International ..............................................................................    01/20/05