| nTouch Documentation | ||||||||||||
|
Introduction The nTouch asset tracking system allows you to monitor and control assets in real-time via the intranet . The system uses a variety of network technologies to interface with end items so that you can be sure to always be in command. A thorough understanding of these technologies will assist you in managing items. Please review this document along with the on-line help files in order to better enjoy your experience with the system. |
||||||||||||
|
Assets
nTouch refers to any monitored and managed item as an asset. Therefore assets are any equipment that you have attached an nTouch tracking and control device to. All nTouch devices support GPS geo-position information along with movement detection and time and date stamps on selected events. Some devices allow you to monitor the speed and heading of mobile devices. Each installed nTouch device will be displayed under your account as an asset. You will use the functionality of this program to monitor and control your assets. Click on the links below to view the files that implement the standard "out of the box" modules. Note that the portal framework is not limited to supporting only the built-in modules. It is easy for developers to develop and integrate their own custom modules into the portal as well. Click here to discover how.
|
||||||||||||
|
Tracking System All configuration settings for the portal are stored within an XML configuration file -- enabling web administrators to easily deploy an instance of the portal accross multiple front-end web servers (each pulling the appropriate configuration data out of the same version of the portal configuration file). In a web farm environment care needs to be taken to replicate the latest configuration file across servers. In the method saveSiteSettings() the PortalCFG.xml file is updated making this a natural area to add replication code. The Portal Framework code listed below uses this configuration data to control the portal's content layout (ie: what portal tabs are displayed -- and what portal modules live on each tab) and security settings (ie: user roles, access permissions, etc). Configuration is loaded on each request from within the Portal Application's Global.asax file using the Configuration business component. It is then used from within either the Portal's DesktopDefault.aspx page (if the accessing browser is an HTML desktop device -- IE, Netscape, Opera, etc) or within the Portal's MobileDefault.aspx (if the accessing computer is a mobile device) to correctly render a tab view of the portal. |
||||||||||||
The portal framework logic is encapsulated within 5 pages, 4 user
controls, 5 class files, 2 stored procedures, the global.asax file and an
XML configuration file. Click on the links below to view the files that make up
the portal framework:
|
||||||||||||
|
Asset Administration
The Portal Starter Kit provides an online Admin tool that permits users in the "Admins" role to manage the content, layout and security of the portal. For information about how to use the Admin tool, see the "About the Portal" tab. The Portal Admin Tool updates the portal configuration using a Configuration component, and updates User Roles using the RolesDB component. The Portal Configuration elements, such as Tab names and layout, Module definitions and settings, and Portal display name, are stored in an XML file and retrieved into a cached DataSet. The Roles, User, and Security information, as well as the individual module data, are stored in the database.
|
||||||||||||
|
The nTouch application is a service provided solely to the customers of
nTouch LLC and PS Energy Group Inc.
The nTouch web application was developed by PS Energy Corporation in partnership with Microsoft Software, Inc Copyright (c) 2006 PS Energy Group Inc. Portions Copyrighted by Microsoft Corporation |
||||||||||||