LabLynx KB:SysAdmin - 1.0 intro
 |
This is an article specific to the Category:LabLynx knowledge base. Its context outside of LabLynx, Inc may not be apparent, thus why it appears inside the LabLynx KB namespace. |
Introduction
This document contains details associated with the usage of the LabLynx LIMS solution developed by LabLynx, Inc. This document contains general guidelines for the LIMS system administration module as well as the help file content, which is also available online while using the LIMS application.
The LABLynx LIMS Solution is an intranet-based application. An intranet application is an application that is accessed over a network and can be used by many individuals simultaneously. The LabLynx LIMS follows the client-server model in that the application processing occurs primarily on the application and database server(s), and the user's computer (client) provides a window in which the user can view or edit information.
While an intranet application is built on the client-server model, it has other characteristics related to Internet technology that provides significant advantages over both traditional client-server applications and distributed applications. Most laboratory personnel today have some degree of exposure to the Internet and the use of a Web browser application. An intranet application is an application that is located on a Web server and can be accessed by users via their Web browser application. This Web server can be integrated into an existing corporate local area network (LAN) or wide area network (WAN) and not be accessible to the public via the Internet. While the technology for providing access to the application is similar to accessing information via the Internet, the Web server in effect establishes a private model of the Internet accessible by the computers which are connected to the LAN or WAN.
Infrastructure connectivity
The server(s) on which the LIMS application and the central data storage facilities are installed will be connected to the existing network infrastructure. In order for a user to be able to access and interact with the LIMS application, the workstation must have connectivity with the existing network infrastructure.
LIMS security model
Before a user can access any of the screens of the LIMS application, they must log in to the application. The user's LIMS account information is contained in the LIMS database. By supplying a login and password, the LIMS application can verify the user as a valid account for accessing the LIMS. Once the user has logged in to the LIMS, they have begun a 'session' with the LIMS application. For the entire time they are logged in, certain information is carried with them as session variables. These variables identify the user's account and the profile to which the user is assigned. With this identifying information, the LIMS application can dynamically adjust lists of information and functions available within each page based on the user's identity. If a user does not interact with the LIMS application for a client-specified period of time (by accessing any page or function within a page), they will automatically be logged out of the application. Any data not saved when the LIMS automatically logs the user out will be lost. It is always imperative to save any pending data before leaving the workstation.
Upon successfully logging in to the LIMS, the application responds to the user by creating a system of menus for the user. This system of menus is dynamically built at the time of login based upon the user profile to which the user belongs.
A user profile is a list of defined rights. These rights include which screens the user can view and even what functions within each page the user can perform. If a user is authorized to view details but not edit these details, the screen will be listed on the menu, but when the user accesses the screen, the save button may be disabled (grayed-out) or may not appear at all.
