Foundation Admin
Foundation Admin
Foundation
Administrator Guide
Software Version 3.0
LCquan, Watson LIMS, and Web Access are trademarks, and Thermo Scientific, LCQ, and Xcalibur are
registered trademarks of Thermo Fisher Scientific Inc. in the United States.
The following are registered trademarks in the United States and other countries:
Access, Excel, Microsoft, and Windows are registered trademarks of Microsoft Corporation. Oracle is a
registered trademark of Oracle Corporation and/or its affiliates.
All other trademarks are the property of Thermo Fisher Scientific Inc. and its subsidiaries.
Thermo Fisher Scientific Inc. provides this document to its customers with a product purchase to use in the
product operation. This document is copyright protected and any reproduction of the whole or any part of this
document is strictly prohibited, except with the written authorization of Thermo Fisher Scientific Inc.
The contents of this document are subject to change without notice. All technical information in this
document is for reference purposes only. System configurations and specifications in this document supersede
all previous information received by the purchaser.
Thermo Fisher Scientific Inc. makes no representations that this document is complete, accurate or error-
free and assumes no responsibility and will not be liable for any errors, omissions, damage or loss that might
result from any use of this document, even if the information in the document is followed properly.
This document is not part of any sales contract between Thermo Fisher Scientific Inc. and a purchaser. This
document shall in no way govern or modify any Terms and Conditions of Sale, which Terms and Conditions of
Sale shall govern all conflicting information between the two documents.
Software version: (Thermo) Foundation 3.0 and later, Xcalibur 3.0 and later, LCquan 2.7 SP1 and later,
LC Devices 2.8 and later, Q Exactive 2.0 and later, Exactive 1.1 SP4 and later, TSQ 2.3 SP3 and later;
TSQ Quantum 2.3 SP3 and later; (Microsoft) Windows 7 Professional SP1 32-bit and Windows 7
Professional 64-bit systems, and Office 2010
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii
Safety and Special Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii
Contacting Us . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ix
Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
System Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Configuration Tasks of the Laboratory Manager and IT Professional . . . . . . . . . 2
Prerequisites to Configuring the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
How Users Perform Sample Acquisition and Store Data . . . . . . . . . . . . . . . . . 6
Secure User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Configuring Software Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Defining User Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Protecting Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Setting Up User Access Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147
Preface
This administrator guide describes how to configure instruments and the Xcalibur™ and
LCquan™ applications for security and compliance. The intended audience includes both
laboratory administrators and local IT professionals who have administrative privileges for the
system.
Contents
• Related Documentation
• Safety and Special Notices
• Contacting Us
Related Documentation
You can also find the information covered in this user guide in the Help system that comes
with the Thermo Foundation™ platform.
The Foundation platform includes Help and the Thermo Foundation Administrator Guide as a
PDF file.
Contacting Us
There are several ways to contact Thermo Fisher Scientific for the information you need.
Phone 800-532-4752
Fax 561-688-8736
E-mail [email protected]
Knowledge base www.thermokb.com
Phone 800-532-4752
Fax 561-688-8731
E-mail [email protected]
Web site www.thermo.com/ms
Go to www.thermoscientific.com/wps/portal/ts/contactus.
Introduction
You can use Thermo Scientific™ applications to develop methods, create or import sequences,
acquire, process, and review data, and create reports, all within a secure environment. This
chapter provides an overview of security and compliance considerations and describes how to
use the Foundation platform, and the Xcalibur and LCquan applications to address them.
Contents
• System Security
• Configuration Tasks of the Laboratory Manager and IT Professional
• Prerequisites to Configuring the System
• Configuring Software Applications
System Security
To prevent unauthorized access to data, most organizations implement strict security
procedures for their computer networks. In this context, unauthorized access means:
• Access by an individual (external or internal to the organization) who has not been
granted the authority to use, manipulate, or interact with the system
• Access by using the identity of another individual—for example, by using a colleague’s
user name and password
The Xcalibur data system and the LCquan application directly implement some of these
controls and rely on the security functions in the Microsoft Windows 7 Professional operating
system for other controls:
• The Thermo Foundation Security Service controls secure file operations.
• The laboratory administrator restricts user software access through Thermo Foundation
Authorization Manager (an administrative utility), which relies on Windows user groups.
The Authorization Manager does not configure user access to the workstation. However,
it can define application roles and feature access for the users.
• Windows security functions handle user authentication.
• Windows security functions maintain electronic record security and, in particular, the
NTFS permission rights.
IMPORTANT The local IT administrator must configure the security features and
settings for Windows.
Figure 1 and Figure 2 show flowcharts of the configuration process for domain users and local
users, respectively.
Figure 1. Configuration tasks of the laboratory administrator and IT professional for domain users
No
Configure the LIMS. Refer to the LIMS documentation.
For Watson LIMS™, refer to Installing and Using the Peak View
Is system Yes Gateway Between Watson and LCquan for information about digital
part of LIMS? exchange of data between these applications.
No
Configure the database (Microsoft Access™ or Oracle).
Figure 2. Configuration tasks of the laboratory administrator and IT professional for local users
Configure the application secure root folder on - Ensure the Thermo Foundation Security Service is properly set up
the workstation. and running.
- Identify a folder to use as the application - Specify how users log on and off.
secure root folder
(by default, \Xcalibur\QuanRoot).
- Restrict access and ensure application users
and groups have proper folder permissions
(read, write, but not delete).
Some applications support the Thermo Scientific Web Access Server environment for
workstations that are for data review only. Web Access can provide application virtualization
to manage configuration and maintenance. You cannot use an instance of the application
running on a Web Access server for acquisition. The IT professional is responsible for
installing Thermo software on the Web Access server.
Some applications support remote acquisition. During remote acquisition, you can have the
application time-stamp raw files created by the Xcalibur application during acquisition and
create a time-stamped folder:
• Remotely stored raw files are time-stamped with the submission time.
• Pausing during acquisition does not change the time stamp.
• The time stamp for the raw files folder and the time stamp for the raw files are not
necessarily the same.
Or, you can prevent the application from time-stamping the raw files during a remote
acquisition by setting the permission from the Expand Tree list if the application permits this
activity. Refer to your application user guide for more information.
IMPORTANT An application might be able to overwrite a raw file of the same name if you
turn off time-stamping.
IMPORTANT Each Windows user account must be associated with a user ID, a
password, and a full description. These items are required for the system to store the
auditing information in the designated database.
As the laboratory administrator, you must define the following before asking your IT
professional to configure Windows user groups for domain users or before configuring private
groups in the Foundation Authorization Manager:
• Types of user roles, for example, administrator, supervisor, scientist, technician, auditor,
or quality assurance
• Individuals assigned to each user role and their projects
• Permissions for a given user role, such as the authority to create methods and acquire data,
signature authority, or read-only access to workbooks
For example, a laboratory might have standard operating procedures that prohibit technicians
from performing certain operations with the software. But the same laboratory might not
have any restrictions on software operations that the scientists can perform. In this case, you
must define at least two user groups—one for scientists and one for technicians.
To view and save the version information for your installed software
To view version information about all installed Thermo Scientific applications, see “Viewing
and Saving System Version Information” on page 123.
To fully implement the security features for applications, the laboratory administrator must
work with the IT professional to achieve the proper data system configuration. Configuring
applications for security and compliance requires three steps:
• Defining User Requirements
• Protecting Records
• Setting Up User Access Controls
If you do not plan to use the system in a regulated environment, define how the system should
be used. This might include the following elements that will help you to conduct the system
configuration steps throughout this document:
• Define authorized user groups on the system, categorized by user type, which defines the
level of access to the system functionality as well as access to data.
• Create a detailed process workflow showing how each user type uses the system to control
instruments and to perform sample acquisition, analysis, and reporting.
• Create a list of all discrete software functionality of the system, organized according to the
applications list in the Authorization Manager module.
Protecting Records
To establish secure file operations, as the laboratory administrator, you or an assistant
laboratory administrator must restrict access permissions for specific folders and files. Set
permissions so that only you or an assistant administrator can delete or alter records. The use
of protected folders and files ensures that unauthorized users cannot obscure previous records
by using a utility such as Windows Explorer.
After you define the security settings for at least one group, the application automatically
denies access to user that are not in that group.
IMPORTANT If no secure groups are defined, users have access to all features of the
application.
Contents
• Using Microsoft and Oracle Databases
• Configuring Your Auditing Database
• Auditing Database Configuration Manager Parameters
Note The LCquan application uses a Microsoft Access database to store each LCquan
Workbook Audit Trail.
If Watson LIMS is part of the workflow, refer to the Watson documentation for database
setup instructions that are specific to Watson LIMS.
Use the Thermo Foundation Auditing Database Configuration Manager to configure either a
Microsoft Access database on your local computer or an Oracle database on a remote
computer.
For information about installing and configuring the Oracle Server and Client software,
version 11g or later, refer to the Oracle manuals. Consult with your Oracle database
administrator and your Thermo Fisher Scientific service representative for advice and
instructions about how to install this software for your application.
To use an Oracle database, make sure that you complete the following tasks:
1. If the site does not have an Oracle server, version 11g or later, install an Oracle database
on an accessible remote server. For more information, consult your Oracle database
administrator.
2. Install the Oracle client software on your local system. For more information, consult
your Oracle database administrator.
3. If you do not know the user name, password, and Oracle Net Service Name of your
Oracle database, obtain this information from your Oracle database administrator.
IMPORTANT Ensure that no other Xcalibur applications are running at the same time
as the Database Configuration Manager. Auditing of Xcalibur applications cannot take
place while running the Database Configuration Manager.
For information about the parameters in the Thermo Foundation Auditing Database
Configuration Manager wizard, see “Auditing Database Configuration Manager Parameters”
on page 15.
1. From the Windows taskbar, choose Start > Programs (or All Programs) > Thermo
Foundation x.x > Database Configuration, where x.x is the version.
IMPORTANT If you are using Oracle version 11 or later, you might need to
contact Technical Support for information about configuring your database. See
“Contacting Us” on page ix for contact information.
Note Be sure to use the Oracle user name and password provided by your Oracle
database administrator.
4. Click Next.
The Thermo Foundation Database Configuration Manager dialog box opens.
5. Confirm that the settings in the Thermo Foundation Auditing Database Configuration
Manager dialog box are correct and click OK.
The next page of the Thermo Foundation Auditing Database Configuration Manager
opens.
Note The changes made in the Auditing Database Configuration Manager take effect
after restarting the computer.
7. Click Finish to save your settings and close the Auditing Database Configuration
Manager.
For more information about setting up your database, see “Configuring Your Auditing
Database” on page 12. Not all of the parameters are displayed at every step in the
configuration process.
Note If you are using Oracle as the database back end, install at least one relational
database on an accessible server and install the Oracle client on the system computer
before using the Auditing Database Configuration Manager.
For a brief explanation on how to install an Oracle database, see “Installing an Oracle
Database” on page 133.
Table 2 describes the parameters for the Auditing Database Configuration Manager.
Table 2. Auditing Database Configuration Manager parameters (Sheet 1 of 2)
Parameter Description
Read-only information
Database Name View the currently configured database.
This line does not appear if this is the first time that you are running the Auditing
Database Configuration Manager.
Database Type View the database type. The database must be an Oracle database on a remote server or
a Microsoft Access database on a local computer.
This line does not appear if this is the first time that you are running the Auditing
Database Configuration Manager.
Database Is Installed On View where the Oracle database is installed on the host computer. (When using a
Host Microsoft Access database, this line is blank.)
This line does not appear if this is the first time that you are running the Auditing
Database Configuration Manager.
Security Name View the Oracle database service name. (When using a Microsoft Access database, this
line is blank.)
This line does not appear if this is the first time that you are running the Auditing
Database Configuration Manager.
User Name View the logon name for the Oracle database. (When using a Microsoft Access
database, this line is blank.)
This line does not appear if this is the first time that you are running the Auditing
Database Configuration Manager.
Select Database Type area
Oracle On Network Server Select to use a remote server to run the Oracle database. You must enter a valid user
name and password to access the database.
When you select this option, the Oracle Net Service Name list appears below the
Password box.
Microsoft Access Select to use a local database based on Microsoft Access.
(When using a Microsoft Access database, this list does not appear.)
Final wizard page parameters
Restart Computer Now Restart the computer automatically when you click Finish.
I Will Restart Later End the database configuration without restarting the computer when you click Finish.
If you selected the Restart Computer Now option, save and close all other applications
before clicking this button.
Contents
• Confirming the Properties of Thermo Foundation Database Service
• Configuring the Properties of Thermo Foundation Security Service
• Configuring Security Settings for Folders and Files
• Configuring Security Settings for the Database Registry Key
• Specifying the Way Users Log On and Off
• Removing and Archiving Files
Note For information about Thermo Foundation Security Service, refer to the
Thermo Xcalibur Getting Started Guide.
Layered applications use the Thermo Foundation Database Service to access the auditing
database and make auditing entries.
To confirm the properties of Thermo Foundation Database Service are set correctly
Tip If you do not see the System and Security category on the Control Panel,
select Category in the View By List in the upper right side of the window.
b. Double-click Services.
The Services window opens.
5. Click the Log On tab to display the Log On page (Figure 4).
Figure 4. Database Service Properties Log On page
The Security Service installs and starts automatically when you install a Thermo layered
application. It is configured to start every time you restart the workstation computer.
IMPORTANT You must prevent unauthorized users from stopping the Security Service.
If the Security Service is stopped, the security features in the application do not function
properly.
Only the system administrator who installed the application software and the Security
Service, or someone who has administrative rights, can stop the service.
Service status
Note Once you set the properties of the Thermo Foundation Security Service, various
actions can change the properties, such as IT policies that generally are passed down to
computers. Review properties regularly to avoid changes that interfere with expected
auditing behavior.
Note The folder that contains the configuration files is hidden by default in Windows.
To make the INI folder appear, from the Windows 7 taskbar, choose Start >
Control Panel > Appearance and Personalization > Folder Options > View >
Hidden Files and Folders, and select Show Hidden Files and Folders. If you do not see
the Appearance and Personalization category, select Category in the View By list to the
right.
To add an administrative user (or administrative group) to the Security page Group, or to add
a specific group or groups to the User Names list and grant the administrator full access to the
security folder and read-only access to everyone else, follow these procedures:
1. Configuring Security Settings for the Root Folder
2. Working with Accounts Set Up by the Foundation Platform
3. Adding and Removing Users (within Folders)
4. Setting Folder Permissions for Users and Groups
Tip When you require more restricted access to folders and files, grant access only to
specific user groups. To set up appropriate user groups, see “Using the Authorization
Manager” on page 51.
In the procedures that follow, add an administrative user (or administrative group) and a
group or groups to the Permission Entries list. Then, grant the administrator full access to the
folder and grant limited access to everyone else.
Tip To further restrict access to folders and files, you can grant access to specific user
groups only. To do this, first set up appropriate user groups, as described in “Adding and
Removing Users (within Folders)” on page 33, and then perform the procedures that
follow, using your specific user groups.
To prepare a root folder, first turn off Use Sharing Wizard in the Folder Options dialog box.
You can then create a root folder for storing all your projects.
4. In the Advanced Settings list, at the bottom, clear the Use Sharing Wizard check box.
Clear this
check box.
5. Click OK to save the change and close the Folder Options dialog box.
To create or locate a folder to use as the root folder for storing all projects
IMPORTANT Do not use the Xcalibur folder as your root folder. If you change the
permission settings for this folder, Xcalibur applications will not run correctly.
Instead, create a new folder or use another existing folder as your root folder.
2. Right-click the folder and choose Properties from the shortcut menu.
The Properties dialog box for the folder opens.
3. Click the Security tab.
4. Click Advanced.
The Permissions page of the Advanced Security Settings for Study dialog box opens.
When you create a new root folder, the permissions from the parent folder automatically
propagate to the new folder, indicated by shaded check boxes in the Permissions list.
In the Advanced Security Settings dialog box, the check box labeled “Include inheritable
permissions from this object’s parent” is automatically selected and grayed out. For a root
folder, you must change this option.
IMPORTANT Normally, you do not want to allow your secure root folder to inherit
permissions from the parent folder. If someone changes the permission settings of the
parent folder, the permission settings of the new root folder do not change if you
select the Inherit From Parent… option.
Prevent this inheritance by clearing the Inherit From Parent… check box in the next
steps. Then correct the permissions in the section “Setting Folder Permissions for
Users and Groups” on page 37.
Subfolders created under the new root folder still inherit the permissions from the
root folder.
IMPORTANT Each Windows user account must be associated with a user ID, password,
and full description. These items are required for the system to store the auditing
information in the designated database.
Note By default, the Foundation and INI folders are in these directories.
• For Windows 7 (32 bit), the Foundation folder is located in the following
directory:
drive:\Program Files\Thermo\
• For Windows 7 (64 bit), the Foundation folder is located in the following
directory:
drive:\Program Files (x86)\Thermo
• For Windows 7, the INI folder is located in the following directory:
drive:\ProgramData\Thermo Scientific\
2. Right-click the folder and choose Properties from the shortcut menu.
The Folder Name Properties dialog box opens.
3. If the Security page is unavailable, do the following:
a. Choose Start > Control Panel.
b. Choose Appearance and Personalization > Folder Options.
The Folder Options dialog box opens.
c. Click the View tab.
d. In the Advanced Settings box, clear the Use Sharing Wizard check box, and then
click OK to accept the setting and close the Folder Options dialog box.
e. Close the Control Panel.
5. Click Edit.
The Permissions for Folder Name dialog box opens.
7. Confirm that the Select This Object Type box contains the object types that you require
(Users, Groups, or Built-in security principals).
To change the list of objects, click Object Types. In the Object Types dialog box, edit the
list of objects (for example, Users and Administrator) and click OK.
8. Confirm that the From This Location box lists the root location that contains your users
and groups.
To change the location, click Locations. In the Locations dialog box, specify a new
location and click OK.
9. In the Enter the Object Names to Select box, enter the new users or groups:
• If the name of a specific user group was missing from the Group or User Names list
on the Security page, type the name of the group.
• If the user name of the administrator (or the name of the administrator group) was
missing from the Group or User Names list on the Security page, type the user name
or group name.
Tip To enter multiple object names at the same time, separate the names with a
semicolon.
10. To verify that the new user or group name is now in the list, do the following:
a. Click Check Names to search for users or groups with the names that you specified
in the Enter the Object Names to Select box.
All similar or matching object names that were found appear underlined in the box.
b. Confirm that only the correct object name or names are listed in the box.
Then click OK to close the Select Users or Groups dialog box and return to the
Permissions for Folder Name dialog box.
11. Examine the Group or User Names list again.
The user groups and the name of the administrator are now available in the list.
• When additional groups or users appear in the Group or User Names list, go to
“Removing Unnecessary Users from Folders.”
• If no additional groups or users appear, go to “Setting Folder Permissions for Users
and Groups” on page 37.
1. If it is not already open, open the Permissions for Folder Name dialog box (see step 1
through step 5 of “To add users and groups to a folder” on page 33).
2. For each user of group that you want to remove, do the following:
a. Select the name of the user or group.
b. Click Remove to remove the selected user or group.
You are now ready to set the permission levels for your users and groups.
1. Open the Security page for the folder (see step 1 through step 4 of “Adding Users to
Folders” on page 33).
2. Set up the permission levels for the administrator as follows:
a. In the Group or User Names list, select the administrator (or the administrator
group) and click Edit.
The Permissions for Foundation dialog box opens.
b. In the Permissions for Folder Name dialog box, select the Allow check box for the Full
Control option.
All of the other check boxes in the Allow column are automatically selected.
Note Groups or users granted Full Control for a folder can delete files and
subfolders within that folder regardless of the permissions protecting the files and
subfolders.
Note Setting these permissions confirms that you cannot delete any of the files in
the folder using Windows Explorer.
4. Click OK to close the Permissions for Foundation dialog box and return to the Security
page of the Foundation Properties dialog box.
c. Clear the Include Inheritable Permissions from This Object’s Parent check box.
The Windows Security dialog box opens.
d. Click Add and then OK to close the dialog box and return to the Permissions page.
e. Click OK to return to the Security page.
6. Click OK to close the Folder Name Properties dialog box and save the permission
assignments.
For additional information about any step, see “Configuring Security Settings for the Root
Folder” on page 26.
6. Clear the Include Inheritable Permissions from This Object’s Parent check box.
7. When the Windows Security dialog box opens, click Add.
8. Confirm that the Permission Entries box contains only your administrator name (or the
administrator group) and the groups you want to add.
• If Administrator (or the Administrator group) does not appear in the list, add it.
• If a group does not appear in the list, add it.
• If any other users or groups appear in the list, select and remove them.
9. Set the permissions for the folder:
a. In the Permission Entries box, select Administrator.
b. Click Edit.
c. In the Permissions list, select the Allow check box for Full Control.
All the other Allow check boxes are automatically selected.
d. Click OK.
e. In the Permission Entries box, select the group name.
f. Click Edit.
g. In the Permissions list, select the Allow check box for Read and clear the Allow check
box for all the other options to prevent removal of information.
You have configured the security settings for the Security folder.
Note You must configure the database registry key whenever you create a new global
database.
1. From the Windows taskbar, choose Start > Run to open the Run dialog box.
2. Type regedit and click OK.
The Registry Editor window opens.
3. In the left pane of the Registry Editor dialog box, locate the folder:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE
\Thermo Scientific\Foundation\Auditing\CFR_Database
4. Right-click the CFR_Database folder and choose Permissions from the shortcut menu
to open the Permissions dialog box for this registry key.
5. Click Advanced.
The Advanced Security Settings dialog box opens.
6. Clear the Include Inheritable Permissions from This Object’s Parent check box.
The Windows Security dialog box opens.
7. Click Add to copy the inherited parent permissions to the CFR_Database registry key.
8. Click OK to close the Advanced Security Settings dialog box.
9. On the Security page of the Permissions dialog box, examine what groups or users appear
in the Group_or_User_Names box.
You want only your administrator name (or the administrator group) and your selected
group or groups to appear in this box.
• If your administrator name (or the administrator group) does not appear in the box,
add it. (See “Adding Users to Folders” on page 33.)
• If the group you want to use does not appear in the box, add it.
(See “Adding Users to Folders” on page 33.)
• If other users or groups appear in the box, remove them.
(See “Removing Unnecessary Users from Folders” on page 37.)
10. Set the permissions for the registry key:
a. In the Group or User Names box, select your administrator name (or the
administrator group).
b. In the Permissions list, select the Allow check box for Full Control.
The Read check box in the Allow column is automatically selected.
Starting with Windows 7, you can switch between users without actually logging off from the
computer. You can turn off this feature, called Fast User Switching, so that the current user
must log off before another user logs on.
If you do not turn off Fast User Switching when it is allowed, two users could log on at the
same time, which can cause strange behavior when they try to control their mass spectrometer.
The acquisition service can only handle one user logged in at a time. Thermo Fisher Scientific
recommends that all labs turn off Fast User Switching, regardless of whether secure file
operations is important to the user or not.
4. In the Local Computer Policy pane, choose Computer Configuration > Administrative
Templates > System > Logon to display the Logon options.
5. Double-click Hide Entry Points for Fast User Switching.
The Hide Entry Points for Fast User Switching dialog box opens.
Automatic logoff cannot occur if a password-protected screen saver precedes it. Automatic
logoff can occur if the screen saver is not password-protected, but you are not notified when it
occurs.
IMPORTANT Thermo Fisher Scientific recommends that you enable automatic logoff
to help ensure file integrity and access controls.
1. Choose Start > Programs (or All Programs) > Thermo Foundation x.x > AutoLogoff,
where x.x is the version.
The Thermo Foundation Automatic Logoff Setup dialog box opens.
For the Foundation platform running on the Windows 7 operating system, provide
users with the following instruction as part of your standard operating procedure after
you turn on AutoLogoff:
Each time you log on, the Windows 7 operating system prompts you for
permission to run AutoLogoff in the background. Choose Allow every time.
3. Click OK.
When a user logs out, the computer automatically shuts down any programs that are running.
If the Windows screen saver is set to appear on the computer at an earlier time than the Auto
Logoff time, the automatic logoff still occurs at the specified time, even though the user
cannot see evidence of the logoff because the screen saver is active.
IMPORTANT Shut down all applications before running the Authorization Manager.
Otherwise, if you make changes to permissions for an application when the application is
open, the changes might not take effect until you exit and restart the program.
Follow these procedures to use the Foundation Authorization Manager to configure secure
groups and set permissions for controlled features in the application data system.
Contents
• Planning User Groups
• Using the Authorization Manager
• Setting Up Secure User Groups
• Setting Permissions
• Setting Up Secure Reports
• Viewing the Authorization Manager History Log
• Working with Security Settings
• Permission Level Settings for an Application
• Authorization Manager Parameters
There is no limit to the number of user groups defined. For simplicity, if all users are to have
the same privileges, define a single user group.
IMPORTANT As a precaution, define at least one user group. If no user groups are
configured in the Authorization Manager, access to controlled features is unrestricted.
A user group can be either a preexisting Windows domain logon group or a private group:
• The domain administrator must create and manage Windows domain logon groups. For
help with domain logon groups, contact your domain administrator.
• The workstation administrator can create and manage private groups. However, before
the administrator can add a user to a private group, the user must be a member of a
domain group. If an intended user is not a user on the domain, grant a domain account
for that person. Contact your domain administrator for help in completing this task.
A single user can belong to more than one user group. If the groups have different permission
levels, the most lenient permission level applies to the user.
From the Windows taskbar, choose Start > Programs (or All Programs) > Thermo
Foundation x.x > Authorization Manager, where x.x is the version.
From the Windows taskbar, choose Start > All Programs >Thermo Foundation x.x >
Authorization Manager.
The Thermo Foundation Authorization Manager window opens. For information about
the parameters in this window, see “Authorization Manager Parameters” on page 79.
The application places no limit on the number of user groups you can define. For simplicity, if
all users are to have the same privileges, you can define a single user group.
IMPORTANT
• You must define secure user groups; otherwise, the system is not secure and all users
can access all features of the software.
• A single user can belong to more than one user group. If the groups have different
permission levels, the most lenient permission level applies to the user.
1. If it is not already open, open the Authorization Manager (see “Using the Authorization
Manager” on page 51).
2. Select only one of the Available Groups options to specify the type of user group:
• To use preexisting Windows user groups, select the Domain/Workstation option.
Contact your domain administrator to create or change logon groups.
Continue to step 3.
• To use (or create) a local user group, select the Private option. The lab administrator
can create private groups (see To define secure private groups).
3. To select the secure domain/workstation logon groups, do the following:
a. Select a group in the Available Groups list and click .
The group appears in the Secure Groups box.
b. When you have selected all of the needed groups, go to “Editing User Groups” on
page 56.
Note Private groups are necessary only if the required groups are not available as
Windows users or Domain user groups.
1. Right-click the user group in the Secure Groups box and choose Members from the
shortcut menu.
If the group is a private group, the Edit User List of Private Group dialog box opens
(Table 5).
2. To add or remove names from the user group, click Add or Delete.
3. For each user that you want to remove from the private group, select the user in the Users
in Private Group box, and then click Delete.
4. For each user you want to add to the private group, do the following:
a. In the System Group list, select the group that contains the new user.
A list of users in the selected group appears in the Users in System Group box.
b. In the Users in System Group box, select the user you want to add.
c. Click Add.
5. After you finish editing the user list, set the permission levels for each user.
For descriptions of the parameters in the Users in Group dialog box, see Edit Users In
Group dialog box parameters.
Right-click the user group in the Secure Groups box and choose Members from the
shortcut menu.
The Modify Users in Group dialog box opens. Because the domain administrator controls
membership in these groups, the lists in the Modify Users in Group dialog box are
read-only. To make changes to domain/workstation logon groups, see your domain
administrator.
1. In the Authorization manager window, in the Global Security Features group box, select
the Predefined Comments check box.
2. Click Edit.
Setting Permissions
For each secure user group, set the permission levels in the Permission Level area for certain
features of the CRC Validator and Instrument Configuration applications, the Xcalibur data
system, and the LCquan application (if installed).
The following table lists the available permission levels. All new secure user groups, whether
domain/workstation groups or private groups, have all features set to Disallowed.
Table 6. Permission levels
Permission Level Description
Disallowed Not permitted. You can specify whether the user interface control
for the disallowed operation is hidden or grayed out.
Signature List Enter the names and passwords of everyone on the required
signature list to perform the authorized action. To approximate an
electronic signature, set the Signature List feature to Allowed,
Password Required, and Comments Required. Anyone in a group
with the Allowed/Password/Comment combination for the given
feature must enter both a password and a comment, which is the
approximation of an electronic signature.
If you have already set up the permission levels for one secure user group and you want to set
the same permission levels for other secure user groups, go to “Inheriting Permissions” on
page 64.
If you have already set up the permissions levels for all your secure user groups and you want
to transfer these settings to another workstation, go to “Exporting and Importing
Permissions” on page 65.
1. If you have not already done so, open the Authorization Manager and create the
appropriate secure user groups (see “Defining User Groups” on page 54).
2. In the Authorization Manager, select a user group from the Secure Groups box.
3. Click Expand Tree to show the entire list of controlled features for the application.
4. From the list of controlled features, select the feature whose permission level you want to
change.
Note You can set permissions only for individual features, not subgroups. After
selecting a feature, the Permission Level options are active. If they are unavailable, you
might have selected a subgroup, not a feature.
5. In the controlled features list to the lower left of the Authorization Manager, select the
name of the application.
6. To show the entire list of controlled features for the unit, click Expand Tree.
7. From the list, select a feature and select one of the following Permission Level options:
• Disallowed
• Signature List
• Supervisor Password
• Password Required
• Allowed
Note You can set permissions only for individual features, such as Allow New
Dataset. set permissions for groups, such as Dataset Selection. When you select a
feature, the Permission Level options for that feature are available.
Tip Right-click a feature to choose the permission level from the shortcut menu.
8. If you selected Permission Level: Disallowed, select how the user interface appears for the
disallowed state.
9. If you set the permission level to Signature List, use the Available Groups area under
Signature List Groups to define the signature list groups.
a. In the Available Groups box, select a user group and click the right arrow. The group
appears in the Signatures Required box.
Being a part of the signature list requires that someone from the specified group be
present to perform the signing activity that permits the feature to be performed. The
signature is specifically for the feature selected.
To approximate an electronic signature, set a name or group to Allowed, Password
Required, and Comments Required. For instructions about defining the Comments
feature, see “Requiring User Comments” on page 67.
b. To add other groups to the Signatures Required list, repeat step a.
c. To require that the current user of the application be placed on the signature list,
select the Current User Must Sign check box.
d. To rearrange the order of the groups in the Signatures Required box, select a group
and click the Move Group buttons: Up or Down.
Note When a user uses a feature with the Signature List permission level, a series of
password dialog boxes appears, one dialog box for each signature (name and password
of a member of the designated group).
For instructions about defining the Comments feature, see “Requiring User
Comments” on page 67.
The order of the groups in the Available Groups box defines the display order of the
password dialog boxes.
10. If you want the users to enter a comment when they perform an action, select the
Comments check box in the Other Requirements area.
This option is available for all permission settings except Disallowed. When a user enters
a comment, it appears in the audit log for the software.
11. Set the permission levels for any or all remaining features as follows:
• To set the permission level of an individual feature, repeat steps 7 through 10.
• To set the permission levels of the other features in the currently selected application
to the same permission level you just set, select the This Application option and
click Set To Same.
• If you want to set the permission levels of all the features in all the applications to the
same permission level you just set, select the All Applications option and click
Set To Same.
The Permission Level setting, the Disallow State setting (if applicable), and the
Comments setting are copied to all the other features.
12. To set the permission levels for other user groups in the Secure Groups box, repeat
steps 1 through 11.
Note The Authorization Manager retains permission level settings if you move a user
group out of the Secure Groups box and into the Available Groups box. If you move
the group back into the Secure Groups box, the permission settings remain intact;
however, if you delete a user group from the Secure Groups box, all permission
settings are lost.
The Permission Level setting, the Disallowed state setting (if applicable), and the
Comment setting are copied to all of the other features for the currently selected
application.
– To set all other features for all applications to the permission level that you just
set, select the All applications option and click Set To Same.
The software copies the Permission Level setting, the Disallowed state setting
(if applicable), and the Comment setting to all other features for all applications.
–or–
• Right-click the user group name in the Secure Groups box, and choose
Globally Set To > Permission Level from the shortcut menu.
Inheriting Permissions
You can copy a complete set of permission levels from one secure user group to another secure
user group.
To copy permission levels from one secure user group to another secure user group
1. Set up the permissions for a secure user group. For setting up permissions in the LCquan
application see “LCquan Folder Structure” on page 129.
2. In the Secure Groups box, select the user group to receive the set of permission levels.
For descriptions of parameters in the Choose Secure Group dialog box, see Table 3 on
page 53.
3. Right-click the selected group and choose Inherit From from the shortcut menu to open
the Choose Secure Group dialog box and display a list of the secure groups (minus the
currently selected group).
4. Select the group whose permission levels you want to copy and click OK.
Both user groups now have the same set of permission levels.
Note To maintain the security of the permission list, you must export it to a secure
location. The Security folder (with proper security settings) on the current computer is an
ideal location.
1. On the system where the correct users and permission levels are set, start the Foundation
Authorization Manager.
2. In the Foundation Authorization Manager, click Export.
The button is located at the bottom of the window. The Save As dialog box opens.
3. Save the permission list in the Security folder as a file with an .eperm file extension.
The Windows 7 default location is drive:\ProgramData\Thermo Scientific\.
The default file name is permissions.eperm.
4. Copy the file to the Security folder on the new system.
5. On the new system, start Thermo Foundation Authorization Manager and click Import.
The Open dialog box opens.
6. Select the permission list file (filename.eperm) and click Open.
The user groups and permission levels appear in the Foundation Authorization Manager.
7. Confirm that the user groups and permissions are correct and click OK to save the
settings and close Thermo Foundation Authorization Manager.
IMPORTANT If you have not configured the security settings to protect your root folders,
do so before setting the root folder feature permissions. See Chapter 3, “Establishing
Secure File Operations.”
The Foundation Authorization Manager list of controlled features includes the following two
features for each application:
• Allow Arbitrary Selection of Root Folder—Allows users to change the root folder to any
folder that they choose. You must ensure that the Allow Arbitrary Selection of Root
Folder feature is set to Disallowed.
• Allow Change of Root Folder—Allows users to change the root folder to another secure
folder. You can set the Allow Change of Root Folder feature to any permission level. If
you set the permission level to anything other than Disallowed, you must define a list of
secure folders from which the user can select a new root folder.
Tip To display these two features in the Foundation Authorization Manager, double-click
the application name in the controlled features list and double-click Root Folder.
IMPORTANT Define secure folders by using fully qualified path names. Use of
mapped drive paths might result in network disconnection upon auto-logoff.
2. Select the secure folder that you want to add to the Secure Folders box and click OK to
close the dialog box.
The folder appears in the list in the Secure Folders box.
3. Repeat steps 1 and 2 for each folder that you want to add to the Secure Folders box.
After the permission levels and the Secure Folders box have been correctly set up, a user
cannot change the root folder to a folder that is not secure. The user must select the new
folder from the Secure Folders box from within the application. The secure folders
information is saved as part of the configuration in a protected folder. For more information,
see “Saving the Security Settings” on page 74.
1. If it is not already open, open the Authorization Manager by choosing Start >
Programs or (All Programs) > Thermo Foundation x.x > Authorization Manager,
where x.x is the version.
2. In the Global Security Features area, select the Predefined Comments check box.
3. Click OK to accept the setting and close the Authorization Manager window.
When predefined comments are active, a dialog box opens whenever a user performs an
action that requires a comment. The user must select a comment from a list before
proceeding.
1. If it is not already open, open the Authorization Manager by choosing Start >
Programs or (All Programs) > Thermo Foundation x.x > Authorization Manager,
where x.x is the version.
2. Select the Predefined Comments check box in the Global Security Features area and
click Edit.
The Comment List dialog box opens. For descriptions of these parameters, see Table 7.
3. Click Add New Comment.
The New Comment dialog box opens. For descriptions of these parameters, see Table 8.
The serial number increments for each report generated from a given application experiment.
If user groups with different security privileges create reports from the same experiment, both
the secure and non-secure reports are included in the total count of reports when assigning the
serial number.
1. In the Foundation Authorization Manager, select a user group from the Secure Groups
area.
2. In the list of controlled features (lower left side), select the application name and click
Expand Tree.
6. In the Browse for Folder dialog box, select the folder that contains the secure templates
and click OK.
1. Choose Start > All Programs > Thermo Foundation > Authorization Manager to open
the Authorization Manager.
2. In the Authorization Manager, do the following:
a. Select a user group in the Secure Groups box.
b. Click Expand Tree to show the entire list of controlled features for the application.
c. From the list, click the plus sign before the LCquan folder.
d. Click the plus sign before the Quantitate Section folder.
e. Select Automatically Lock Workbook after Creating Reports.
The Permission Level options become available.
f. Select the Allowed option, and click OK.
Each entry in the history log contains the time and date, and the user ID and full name.
You can sort and filter the entries in the history log by field (for example, you can sort and
filter by date and time). You can also print the log.
The controlled features information is saved in a configuration file in the following folder:
C:\ProgramData\Thermo Scientific\INI
You must properly set the security for this folder to prohibit access by non-administrators. If
you have not already done this, go to Chapter 3, “Establishing Secure File Operations.”
Certain permission level settings override other settings. In addition, some features are
unavailable—regardless of their permission level settings—if you have locked specific features
in the application.
When using the Oracle Server and Client software, version 11g or later, refer to the Oracle
manuals. Consult with your Oracle database administrator and your Thermo Fisher Scientific
service representative for advice and instructions about how to set permissions for your
application when using this version of the software.
The Permission Level Settings table lists the application features that you can configure in the
Foundation Authorization Manager.
Table 9. Permission Level Settings (Sheet 1 of 5)
Application feature Description
Run Application
Operator Use Allowed If you set this feature to Disallowed, the user cannot open the application. As a
result, the permission level settings for the other features are irrelevant.
If a user whose permission is set to Disallowed tries to access the system, the
application makes an entry in the Global Auditing Database history log.
Root Folder
Allow Change of Root Folder If you enable this feature (set it to Signature List, Supervisor Password,
Password Required, or Allowed), define a list of secure folders where the user can
select a new root folder.
Allow Arbitrary Selection of If you set this feature to Allowed, the user can select any folder to be the root folder
Root Folder of the workbook.
(For more information about file tracking, see “File Tracking Page of the Audit Viewer” on page 114.)
Allow Opening of Workbooks If you set this feature to Allowed, the user can open workbooks with file errors, such
with Filetracking Errors as workbooks with missing files or files that were modified outside of the LCquan
application.
(LCquan only)
Allow Opening of Workbooks If you set this permission to Allowed, the user can open workbooks that the
Already Marked as Opened application flags as opened.
(LCquan only) When a user opens an LCquan workbook, the application flags the workbook as
opened to prevent the workbook from being opened by multiple instances of the
application. If the application is forced to close abnormally, the flag might not be
removed even though the workbook is no longer open. To open the workbook, set
this permission to Allow. The next time the workbook is closed, the open flag is
removed.
File
Save If you set this permission to Disallowed, the user can lock the workbook only if it
has not been changed. If it has been changed, the user cannot lock the workbook.
Save As If you set this permission to Disallowed, the user cannot use the Save As command.
Create New Workbook (No special information or interactions.)
(LCquan only)
Create Locked Version of If you set this permission to Disallowed, the user does not have the option to lock a
Workbook (LCquan only) workbook.
Section Configuration
Show Instrument Setup Section If you set this permission to Disallowed, the user cannot display the Instrument
Setup Section nor can the user make changes to the Instrument Methods.
Show Acquisition Section If you set this permission to Disallowed, the user cannot create or modify an
acquisition sequence nor can the user acquire data.
Show Explore Section If you set this permission to Disallowed, the user cannot explore new quantitation
methods.
Show Quantitate Section If you set this permission to Disallowed, the user cannot:
• Create or change a processing method.
• Create or modify processing sequences.
• Survey and review all the results.
• Create reports from this section and process the data to produce quantitative
results.
The Allowed setting changes the behavior in the Column Arrangement dialog box
for Excel reports, preventing the user from changing the precision. Any previous
value settings are overridden with a restricted number of decimals and the values are
not editable. The Allow setting does not affect the behavior of the grid views, the
exported results, or the reports generated using XReport.
IMPORTANT Before the Excel rounding feature takes effect for Watson LIMS
digital interface, you must start and exit the application at least one time. See
“Recommended Settings for Excel Reports” on page 143.
Automatically Lock Workbook The Allowed setting automatically locks the workbook (not a copy of
After Creating Reports the workbook) after you create a report.
(LCquan only) A locked workbook (and its associated files) is a workbook that cannot be
overwritten. You cannot save any changes made to a locked workbook, and you
cannot acquire data in a locked workbook. You can create new reports, but the
LCquan application does not save the report selections. When you open a locked
workbook, it displays [Locked] in the title bar next to the workbook name and in
the status bar.
When using the Oracle Server and Client software, version 11g or later, see “Using Microsoft
and Oracle Databases” on page 11.
For more information about using the Authorization Manager to define user groups and set
permission levels, see “Setting Up Secure User Groups” on page 53.
These tables describe the parameters in the Authorization Manager window and the features
that you can configure from this window:
• Table 10 describes the parameters in the Authorization Manager window.
• Table 11 on page 84 describes the application features that you can configure from the
Authorization Manager window.
Table 10. Foundation Authorization Manager parameters (Sheet 1 of 6)
Parameter Description
Available Groups
Domain/Workstation Use preexisting Windows logon groups. Contact your network administrator to create
or change logon groups.
Private Use or create a private (local) user group. The administrator of the workstation can
create private groups.
Available Groups View the available Windows logon groups (Domain/Workstation option) or private
(local) groups (Private option).
To move a group into the Secure Groups box, select the group in the Available Groups
list and click >>. To move a group out of the Secure Groups box, select the group in the
Secure Groups box and click <<, or double-click the group.
Select the Private (Available Groups) option to enable the Create button.
Delete Select a private group in the Secure Groups box and click Delete to delete the group.
Secure Groups View the Windows logon groups (Domain/Workstation option) or private (local)
groups (Private option) whose permission levels you have set.
To move a group into the Secure Groups box, select the group in the Available Groups
list and click >>. To move a group out of the Secure Groups box, select the group in the
Secure Groups box and click <<, or double-click the group. To delete a secure group,
select the group in the Secure Groups box and click Delete. Right-click a group in the
Secure Groups box to display a shortcut menu with the following commands:
Members: Opens the Edit User List Of Private Group dialog box (for private groups) or
the Users In Group dialog box (for domain groups). For parameter information for
these dialog boxes, see Table 4 on page 56 and Table 5 on page 57, respectively.
Globally Set To: Sets all software features in all applications to the same permission
level: Disallowed, Signature List, Supervisor Password, Password, or Allowed.
Inherit From: Opens the Choose Secure Group dialog box (Table 3 on page 53).
Create Group: Opens the Create Private Group dialog box (Table 4 on page 56). (Only
for private groups)
Global Security Features
Predefined Comments Require the user to select from a list of predefined comments instead of typing in a
comment for features that require comments.
When you select this check box, the Edit button becomes active. Click Edit to open the
Edit Comment List dialog box and define a list of comments (Table 7 on page 68).
Edit For certain features that require comments, define a list of comments that a user must
choose from.
Secure folders are used only in the LCquan application. This box is grayed out unless
LCquan is selected in the Permission Level pane.
Add Locate the folder that you want to add to the Secure Folders list.
Secure folders are used only in the LCquan application. This button is grayed out unless
LCquan is selected in the Permission Level pane.
Delete Select and remove a folder from the Secure Folders list.
Secure folders are used only in the LCquan application. This button is grayed out unless
LCquan is selected in the Permission Level pane.
If Disallowed and Allowed are the only options available (all of the other options are
grayed out), then these options do not indicate permission levels, but instead indicate
configuration settings. Disallowed means that the selection in the Permission Levels
pane is not displayed by the application and Allowed means that the selection is
displayed.
For example, if you select Xcalibur Configuration | Allow To Access | Dataset List page
in the Permission Levels pane, only the Disallowed and Allowed settings are available. If
you select Disallowed, the Dataset List page is not displayed in the Xcalibur
Configuration dialog box. If you select Allowed, the Dataset List page is displayed in
the Xcalibur Configuration dialog box.
Signature List Require that the names and passwords of everyone on the signature list be entered to
perform the action that you selected in the Permission Levels pane. When an action
with a permission level of Signature List is chosen, a series of password dialog boxes
appear, one for each signature (name and password of a member of a designated
signature group). The order of the groups shown in the Signature List Groups:
Signature Required list defines the order in which the password dialog boxes appear.
Supervisor Password Require that the name and password of the supervisor be entered to perform the action
that you selected in the Permission Levels pane. In this context, a supervisor is any
person who has permission to do this operation—that is, the person’s permission level
for this operation is either Allowed or Password Required.
Password Required Require that the password of the user be entered to perform the action that you selected
in the Permission Levels pane.
Allowed No restrictions. Allows the user to perform the action that you selected in the
Permission Levels pane without restriction.
If Disallowed and Allowed are the only options available (all of the other options are
grayed out), then these options do not indicate permission levels, but instead indicate
configuration settings. Disallowed means that the selection in the Permission Levels
pane is not displayed by the application and Allowed means that the selection is
displayed.
For example, if you select Xcalibur Configuration | Allow To Access | Dataset List page
in the Permission Levels pane, only the Disallowed and Allowed settings are available. If
you select Disallowed, the Dataset List page is not displayed in the Xcalibur
Configuration dialog box. If you select Allowed, the Dataset List page is displayed in
the Xcalibur Configuration dialog box.
To move a group into the Signature Required list, select the group in the Available
Groups list and click >>. To move a group from the Signature Required list, select the
group in the Signature Required list and click << or double-click the group. The only
groups that can be in the Signature Required list are those groups that have permission
(Allowed or Password Required) to do the operation.
Select Permission Level: Signature List to activate the Available Groups list.
Signature Required Require a signature from a specified group. When an action with a permission level of
Signature List is chosen, a series of password dialog boxes appear, one for each signature
(name and password of a member of a designated signature group). The order of the
groups shown in the Signatures Required list defines the order in which the password
dialog boxes appear.
To move a group into the Signature Required list, select the group in the Available
Groups list and click >>. To move a group from the Signature Required list, select the
group in the Signature Required list and click <<. The only groups that can be in the
Signature Required list are those groups that have permission (Allowed or Password
Required) to do the operation.
Select Permission Level: Signature List to activate the Signatures Required list.
Current User Must Sign Add the current user to the Signatures Required list.
Select Permission Level: Signature List to activate the Current User Must Sign check
box.
Move Group Up Move the group that you selected in the Signatures Required list up one spot in the list.
Select Permission Level: Signature List to activate the Move Group Up button.
Move Group Down Move the group that you selected in the Signatures Required list down one spot in the
list.
Select Permission Level: Signature List to activate the Move Group Down button.
Other Requirements
Comment Require the user to enter a comment that appears in the Audit Log when performing an
action. Features in the LCquan application report auditing to the Workbook. Features
in Xcalibur applications report to the Global log.
Use the Authorization Manager to set permissions for the Foundation platform and the
Xcalibur data system features. You can set them for individuals or for groups. Certain
permission level settings override other settings.
Table 11. Authorization Manager application features (Sheet 1 of 8)
Features Description
CRC Validator
Run Application If you set this feature to Disallow, then the user cannot open the CRC Validator
window. In this case, the application ignores the permission level settings for other
features.
If a user whose permission is set to Disallow tries to access the system, an entry is made
in the Global Auditing Database history log.
If a user whose permission is set to Disallow tries to access the system, an entry is made
in the Global Auditing Database history log.
For the Homepage window, you can allow or disallow the following actions.
Dataset Selection • Dataset Selection Displayed at Startup
• Dataset Selection Allowed in Menu
• Allow New Dataset
Analysis • Start Analysis
• Stop Analysis
• Pause Analysis
Devices • Devices On
• Devices Standby
• Devices Off
• Automatic Devices On
Sequence Operations • Run Sequence
• Batch Sequence
• Import Sequence
• Export Sequence
• Run This Sample
File File Save
Print Print Sequence
Instrument Configuration
Run Application If you set this feature to Disallow, then the user cannot open the Thermo Foundation
Instrument Configuration window. In this case, the application ignores the permission
level settings for other features.
If a user whose permission is set to Disallow tries to access the system, an entry is made
in the Global Auditing Database history log.
For the Instrument Configuration window, you can allow or disallow the following actions.
Instrument Operations • Add Instrument
• Remove Instrument
• Configure Instrument
If a user whose permission is set to Disallow tries to access the system, an entry is made
in the Global Auditing Database history log.
For the Instrument Setup window, you can allow or disallow access to the following actions.
Dataset Application • Dataset Selection Displayed at Startup
• Dataset Selection Allowed in Menu
• Allow New Dataset
File File Save
Print Print Instrument Method
LCquan
For information about the LCquan features, see Appendix A, “LCquan Folder Structure and Security Features.”
If a user whose permission is set to Disallow tries to access the system, an entry is made
in the Global Auditing Database history log.
For the Library Manager dialog box, you can allow or disallow the following actions.
Dataset Application • Dataset Selection Displayed at Startup
• Allow New Dataset
Manage Libraries • Add Library
• Delete Library
• Archive Library
Convert Libraries Convert Library
Processing Setup
Run Application If you set this feature to Disallow, then the user cannot open the Processing Setup
window. In this case, the application ignores the permission level settings for other
features.
If a user whose permission is set to Disallow tries to access the system, an entry is made
in the Global Auditing Database history log.
For the Processing Setup window, you can allow or disallow the following actions.
Dataset Application • Dataset Selection Displayed at Startup
• Dataset Selection Allowed in Menu
• Allow New Dataset
File File Save
Print Print Processing Method
Options • Change Chromatography Type
• Calibration Options
• Delete Selected Component
Programs Program Changes
If a user whose permission is set to Disallow tries to access the system, an entry is made
in the Global Auditing Database history log.
For the Qual Browser window, you can allow or disallow the following actions.
Dataset Application • Dataset Selection Displayed at Startup
• Dataset Selection Allowed in Menu
• Allow New Dataset
Layout Usage • Apply Layout
• Apply Default Layout
• Save Layout
• Save Layout as Default
• Restore Factory Default
Tools Add Tools
Edit • Copy View to Clipboard.
• Copy Special to Clipboard
• Copy Cell to Clipboard
Print Print Cells
If a user whose permission is set to Disallow tries to access the system, an entry is made
in the Global Auditing Database history log.
For the Quan Browser window, you can allow or disallow the following actions.
Dataset Application • Dataset Selection Displayed at Startup
• Dataset Selection Allowed in Menu
• Allow New Dataset
Export Export Processing Method
Export Data to Excel • Export Short Excel Report
• Export Long Excel Report
View All Samples • Show All Samples
• Show Standard and QC Sample Types
Options Delete Selected Component
Results Grid • Delete Selected Samples
• Add Samples
• Copy Row
File File Save
Save All Save All Result Files
Print Print Reports
If a user whose permission is set to Disallow tries to access the system, an entry is made
in the Global Auditing Database history log.
Selecting the Disallow check box hides access to the following features.
Dataset Application • Dataset Selection Displayed at Startup
• Dataset Selection Allowed in Menu
• Allow New Dataset
Queue • Pause Queue
• Resume Queue
• Purge Queue
Analysis Remove From Queue
Subtract Background
Run Application If you set this feature to Disallow, then the user cannot open the software application.
In this case, the application ignores the permission level settings for other features.
If a user whose permission is set to Disallow tries to access the system, an entry is made
in the Global Auditing Database history log.
Selecting the Disallow check box hides access to the following features.
Dataset Application • Dataset Selection Displayed at Startup
• Allow New Dataset
Operation Proceed
If a user whose permission is set to Disallow tries to access the system, an entry is made
in the Global Auditing Database history log.
Selecting the Disallow check box hides access to the following features:
Customer Info Print User Info
Allow Access to Tabs • Folders
• Customer Info
• Fonts
• Peak Detection
• Mass Options
• Labeling and Scaling
• Intelligent Shutdown
• Dataset List
Reset Reset Allowed
File Converter
Run Application If you set this feature to Disallow, then the user cannot open the File Converter
application. In this case, the application ignores the permission level settings for other
features.
If a user whose permission is set to Disallow tries to open the File Converter
application, an entry is made in the Global Auditing Database history log.
Selecting the Disallow check box hides access to the following features.
Dataset Application • Dataset Selection Displayed at Startup
• Allow New Dataset
Convert Button Convert Button Check
XReport
Run Application If you set this feature to Disallow, then the user cannot open the Xreport application. In
this case, the application ignores the permission level settings for other features.
If a user whose permission is set to Disallow tries to access the system, an entry is made
in the Global Auditing Database history log.
Contents
• Checking Files with the Foundation CRC Validator
• Selecting Files Using Database Filters
• Selecting Files Using a Pattern
• CRC Validator Parameters
Note Close any open layered applications before running the Foundation CRC Validator.
1. From the Windows taskbar, choose Start > Programs (or All Programs) > Thermo
Foundation x.x > CRC Validation, where x.x is the version.
The Foundation CRC Validator window opens. For information about the parameters in
this window, see “CRC Validator Parameters” on page 99.
When you select files using database filters, select files for validation or viewing on the basis of
information about those files that is stored in the auditing database. For example, select files
created by a particular layered application or select files created or modified at certain times.
Create two types of filters: non-date filters and date filters. Non-date filters are based on fields
from the auditing database. Use them to select files based on characteristics, such as the
application used to create the file or the name of the user who created the file. Use date filters
to select files on the basis of the date when they were created or last modified.
Combine multiple non-date filters using the AND and OR operators. The default filter is the
most recently selected dataset name.
2. For each non-date filter that you want to add, do the following in the Add Non-Date
Filter area:
a. In the first list, select AND or OR.
b. In the second list, select the database key to filter on.
c. In the Equals box, type the value for the database key. For example, if you selected
Application Name in the second list, you might enter Home Page or Qual Browser in
the Equals box.
d. Click Add to add this filter to the list of current filters.
3. For each date filter that you want to add, do the following in the Add Date Filter area:
a. In the From box, enter the starting date and time for the filter.
b. In the To box, enter the ending date and time for the filter.
c. Click Add to add this filter to the list of current filters.
4. To remove unwanted filters from the filter list, click the filter name in the list and click
Remove Filter.
5. When you have made all needed changes, click OK to save your changes and close the
dialog box.
1. In the File Selection area of the CRC Validator window, select the Files Matching
Pattern option.
2. In the File Path list, select the path to the folder containing the files to check or click
Browse to find the folder.
3. In the File Name list, select the file extension of the files to check.
4. Select the Include Subfolders check box to have the CRC Validator check files in
subfolders of the selected folder.
5. Click OK to save your changes and close the dialog box.
From the Windows taskbar, choose Start > Programs (or All Programs) >
Thermo Foundation x.x > CRC Validator, where x.x is the version.
For information about the Filter Entries dialog box, see Table 13 on page 97.
Database Filter View the current database filter. This box is read-only.
The default filter is the last selected dataset name. To change the filter, click Edit Filter.
Files Matching Pattern Select files matching the file pattern listed in the File Path and File Name lists.
File Path The path to files to be checked. You can enter the path manually or click Browse to
select the path.
File Name The name of the file to check. You can use a wildcard character to represent one or more
characters in the file name. Use an asterisk (*) as a substitute for zero or more characters.
Use a question mark (?) as a substitute for a single character in the file name. You can
also select a common file extension from the list.
Include Subfolders To include all subfolders in the search for matching files.
CRCs Match: The CRC stored in the database matches the CRC just calculated for the
file.
CRCs Do Not Match: The CRC stored in the database does not match the CRC just
calculated for the file. Most likely, the file has been modified since the tracking record
was created.
File Not In Database: The file was found on the hard disk but was not found in the
database. It might not be a tracked file.
File Not On Disk: The file was found in the database but was not found on the hard
drive. The file might have been deleted or archived.
Folder Name View the full path to the file.
Files Tested View the total number of files tested.
Not In Database View the number of files that were not found in the database.
Not On Disc View the number of files that are in the database but could not be found on the disk.
CRCs Match View the number of files where the CRC value stored in the database matches the CRC
just calculated for the file.
CRCs Differ View the number of files where the CRC value stored in the database does not match
the CRC just calculated for the file.
Buttons
Check Start the comparison of the CRC value stored in the database with the one calculated
for the specified file or files on the hard disk.
Print Print the CRC validation report. The report contains which filter or file mask was used
and the time and date when the report was produced.
Auditing
This chapter describes how to use the Audit Viewer utility for auditing functions. You can
perform these auditing functions:
• Display all auditable events and changes made to files created or managed by various
Thermo Scientific applications.
• View a history of what has been done during data acquisition and data processing.
• Get information about all auditable events that have occurred within the application.
When you open the Audit Trail from within the Xcalibur data system, you can view the same
information that is provided in the Audit Viewer utility; however, you cannot print reports.
Contents
• Viewing Audit Viewer Databases
• Viewing Audit Viewer Pages
• Filtering Audit Viewer Entries
• Sorting Audit Viewer Entries
• Printing Audit Viewer Entries
• Audit Viewer Parameters
You can access either of the following types of databases using Audit Viewer:
• The Global Auditing database keeps a log of auditable events for all the Xcalibur-related
data files and applications it recognizes. The Xcalibur-related data files include the raw
files that you acquire in the LCquan application.
• The local application database keeps a log of auditable events associated with the current
application, including the entries that have not been saved to the database. Each
application database also includes a log about the raw files that are acquired as part of
the application. For the LCquan application, the audit database is the LCquan Workbook
Audit Trail.
IMPORTANT Each Windows user account must be associated with a user ID, password,
and full description. The system requires these items to store the auditing information in
the designated database.
IMPORTANT You must configure the database in the Thermo Foundation Auditing
Database Configuration Manager before you can access the Global Auditing database. See
“Configuring Your Auditing Database” on page 12.
Choose Start > Programs (or All Programs) > Thermo Foundation x.x > Audit Viewer,
where x.x is the version.
The Audit Viewer window opens. The window title bar shows the location of the
database being viewed.
Each LCquan workbook and each Xcalibur window has its own database. When you start
Audit Viewer from a study or workbook, the viewer displays the saved and unsaved entries for
the current study or workbook. The unsaved entries are highlighted in yellow in the viewer
window.
– Local application database: Lists the changes made within the application or to any
application-owned files in the LCquan workbook or Xcalibur window, including the
LCquan workbook file (.lqn), processing method (.pmd), instrument method
(.meth), sequence (.sld), and any imported sample data files (.raw). The File Tracking
page does not include the data files (.raw) acquired from within the application that
are tracked in the Global Auditing database.
For any files that are modified outside of the application, the Foundation platform
displays a file-tracking error message.
Note The LCquan application does not save entries to the database until you save the
workbook. The Audit Viewer headlights the unsaved entries in yellow.
• The Instrument Error page (see “Instrument Error Page of the Audit Viewer” on
page 115) lists events that occur to instruments that the Xcalibur data system creates or
manages.
2. In the Add Non-Date Filter area, select AND or OR from the first list.
• AND filters for entries that match ALL the specified criteria.
• OR filters for entries that match ANY of the criteria.
3. Specify a filter in the form of Column Name equals string.
a. From the drop-down list, select a column to filter on.
b. In the adjacent box, type the text string to match.
c. Click Add.
The filter criteria appear in the space below.
4. To add additional filters, repeat steps 2 and 3.
If you select an OR filter, records must match only one of the filters. If you selected an
AND match, records must match ALL the specified filters.
Note The non-date filter accepts partial matches. For example, if you have a user
name of john.doe, then a filter string of john or doe will match entries for that user
name.
1. In the Add Date Filter area, select or type the beginning date and time in the From box.
2. Enter the ending date and time in the To box.
3. Click Add.
To remove a filter
When you have defined all your filters, click OK in the Filter Entries dialog box.
The Audit Viewer window displays the results on the All page. For more information
about this page, see “All Page of the Audit Viewer” on page 111.
1. In the Audit Viewer window, click the tab of the page you want to view.
2. Click Sort.
The Sort Entries dialog box opens.
3. In the 1st Sort Field list, select a column heading and select the Ascending or
Descending option.
4. Repeat this step for the 2nd Sort Field and 3rd Sort Field.
5. Click OK.
The Audit Viewer page displays the entries in the specified sort order.
1. From the Windows taskbar, choose Start > Programs (or All Programs) > Thermo
Foundation x.x > Audit Viewer, where x.x is the version.
The Audit Viewer window opens.
2. Click the tab of the page you want to print.
3. Click Print.
The Print Options dialog box opens. For descriptions of these parameters, see Table 16.
4. Select the printing options (see Print Options Dialog Box) and then click OK.
Note If you select the Don't Tell Me About This Again check box, the Foundation
platform automatically applies the last requested behavior (Save or Not Save) each
time you start Audit Viewer when the application contains unsaved entries. To restore
the message, choose Options > Enable Warnings.
2. In the Audit Viewer window, click the tab of the page that you want to print.
3. Make sure the displayed page contains only saved entries. Yellow highlights appear on the
rows of any unsaved entries.
If you have a mix of saved and unsaved entries, you can do one of the following:
• In the application window, choose File > Save to save the application study. In the
Audit Viewer window, click Refresh.
• In the Audit Viewer window, click Filter, and then add filter rules so that only the
saved records appear on the page you want to print. See “Filtering Audit Viewer
Entries” on page 105 for details.
4. Click Print.
5. In the Print Options dialog box, select printing options, and then click OK.
When you double-click a log item on the All page, the Audit Viewer displays the page
associated with the log item and highlights the item on that page. The History page provides a
chronological listing of all of the changes made to method files, result lists, or both. The Event
page lists auditable software application events that the user initiated. The File Tracking page
lists all changes made to data files.
The Audit Viewer has slightly different capabilities when run as a stand-alone application
than when run from within a Thermo Scientific application.
• When you run the Audit Viewer as a stand-alone application (by choosing
Start > Programs (or All Programs) > Thermo Foundation x.x > Audit Viewer, where
x.x is the version), the Audit Viewer displays all items in the database (excluding any
uncommitted items or unsaved changes), and you can print the data.
• When you open the Audit Viewer from within most applications (by choosing
File > Audit Trail), the Audit Viewer displays only the items associated with the current
application, including uncommitted items and you cannot print the data.
• When you open Audit Viewer from within the LCquan application (by choosing
File > Audit Trail), the Audit Viewer window displays both committed and
uncommitted items and you can print the committed items.
File is created
File was copied
File was moved
File was deleted
File was modified
File was renamed
Result of rename
Old folder name
New folder name
Result of file move
Comment View the comment associated with the log entry.
Buttons
Sort Specify how you want to sort the entries in the Audit Viewer.
Filter Specify how you want to filter the entries in the Audit Viewer.
Auto Width View the longest entry in that column.
Print Print an active file or document.
Refresh Update the log.
The Audit Viewer has slightly different capabilities when run as a stand-alone application
than when run from within a Thermo Scientific application. When you run the Audit Viewer
as a stand-alone application (by choosing Start > All Programs > Thermo Foundation x.x >
Audit Viewer, where x.x is the version), you can view and print all items in the database
(excluding any uncommitted items or unsaved changes). When you open the Audit Viewer
from within an application (by choosing File > Audit Trail), the Audit Viewer window
displays only the items associated with the current application, including uncommitted items.
However, you cannot print the data.
Table 21. Instrument Error page parameters
Parameter Description
Date/Time View when the log entry occurred.
Computer Name View the name of the workstation performing the change.
User Name View the logon name of the user who made the change that caused the error notification.
The administrator of the network assigns logon names for each user.
Full Name View the descriptive name of the user who made the change that caused the error
notification. Often, this is the first and last name of the user. The administrator of the
network assigns a full name to the logon name for each user.
Application Name View the name of the software application that was used to change the instrument.
Dataset Name View the data set that contains the affected instrument.
Instrument Error Code View the code that the application produced when it received information about the
instrument error.
Instrument Error View the severity error level for the incident.
Severity
Instrument Error View the instrument error string that was produced.
String
Device VI State View the status of the device at the time the log event occurred.
Time Offset If an acquisition was in progress when the log event occurred, view the acquisition time. If
no acquisition was in progress, this field reads zero.
Buttons
Sort Specify how you want to sort the entries in the Audit Viewer.
Filter Specify how you want to filter the entries in the Audit Viewer.
Auto Width View the longest entry in that column.
Print Print an active file or document.
Refresh Update the log.
Contents
• Adding Instrument Drivers to the Instrument Configuration
• Setting Up the Configuration Options for Each Configured Device
1. Choose Start > Programs > Thermo Foundation x.x > Instrument Configuration,
where x.x is the version.
The Thermo Foundation Instrument Configuration window opens.
2. To choose the type of hardware devices to add, select a device type in the Device Types
list. The selections include the following: All, Autosampler, Gas Chromatograph, Liquid
Chromatograph, Mass Spectrometer, Detector, or Other.
Selecting All displays all of the installed device drivers in the Available Devices list.
Note If you do not see the device you want to add, you might need to install the
device driver.
3. For each device that you want to add to the instrument configuration, in the Available
Devices list do the following:
• Select the device icon, and then click Add.
–or–
• Double-click the device icon.
A copy of the device icon appears in the Configured Devices list.
To specify the configuration options for each configured device, go to the next topic, “Setting
Up the Configuration Options for Each Configured Device.”
Thermo Scientific Foundation Administrator Guide 117
7 Configuring Instruments
Setting Up the Configuration Options for Each Configured Device
For most Thermo Scientific mass spectrometers, the data system does automatically recognize
the ion source.
Each configured device of the LC/MS instrument appears as an icon on the View bar of the
Instrument Setup window.
• To open the Device view, click the Device icon.
• To open the Help for the device, choose Device Help. This Device Help is independent
of the application Help.
• To open the Help topic for the current page of the Device view, choose Help > Current
View Help (see Figure 7) or press F1.
Figure 7. Help for instrument devices
1. Add the devices that make up the instrument to the instrument configuration (see
“Adding Instrument Drivers to the Instrument Configuration” on page 117).
2. In the Configured Devices list, do the following:
• Select the device icon for the device that you want to configure and click Configure.
–or–
• Double-click the device icon.
The Device Name Configuration dialog box opens.
3. Enter all required configuration information for the device. Complete entries and options
for all pages.
4. To save settings and close the Device Name Configuration dialog box, click OK.
The Thermo Foundation Instrument Configuration window reappears.
5. To save the configuration settings and close the window, click Done.
Choose Start > Programs > Thermo Foundation x.x > Instrument Configuration,
where x.x is the version.
Table 22. Instrument Configuration window parameters (Sheet 1 of 2)
Parameter Description
Device Types
View or change the category of device types currently displayed in the Available Devices area. The default option
is All. The other options allow you to select a subset of all of the devices as follows:
A device must be present in the Configured Devices area to begin the process of configuring the device.
Remove Remove the device you have selected from the Configured Devices area.
Each button displayed in the Configured Devices area represents an instrument that has
been selected for configuration as an Xcalibur device but might or might not have been
configured.
Configure To configure a device listed in the Configured Devices area, click the button of the device to
be configured, and then click Configure to open the appropriate configuration dialog box.
For example, to configure an LCQ™ MS detector, click LCQ in the Configured Devices
area, and then click Configure. The LCQ Configuration dialog box opens.
Other Parameters
Done Close the Instrument Configuration window after you have configured Xcalibur devices.
If this dialog box appears, install the latest software for the instruments listed.
Note Follow the installation instructions provided with the data system and instrument
control software DVDs.
1. From the Windows taskbar, choose Start > Programs (or All Programs) > Thermo
Foundation x.x > Version Info, where x.x is the version.
The Version Info dialog box opens.
2. To view the complete version information for each installed application or instrument,
click the Expand/Collapse icon.
1. Click Save.
The following message appears.
• Click OK to save the version information to a text file and close the box.
IT Considerations
To ensure that both the Xcalibur and LCquan applications work properly, review these
IT issues.
Contents
• Avoid Antivirus Scanning During Data Acquisition
• Do Not Delete the Xcalibur System Account
• Ensure that a Firewall Exception Exists for the Instrument
• Ensure Your Computer Stays Active
1. Choose Start > Control Panel > System and Security > Power Options.
2. Select Create a Power Plan.
4. Click Next to open the Change Settings for the Plan dialog box.
Contents
• LCquan Folder Structure
• Security Features Within LCquan
For each new project, the LCquan application creates the following hierarchical folder
structure within the designated root folder.
• Study folder—Top-level folder within the root folder. Each study folder contains one or
more workbook folders. The study folder can contain any number of workbook folders,
but each workbook must have a unique name.
• Workbook folder—Contains all the information that the LCquan application uses for an
individual quantitative analysis project. The workbook folder contains the LCquan file
(.lqn), the instrument method file (.meth), and an audit database (.mdb). The workbook
folder also contains the following:
– Exports folder—Stores copies of all files that the application exports, such as report
files.
– Imports folder—Stores a copy of legacy files that you import into the workbook, such
as instrument method files, processing method files, or sequence files.
– Rawfiles folder—Contains acquired data files (.raw) and any imported raw data files.
– Temp folder—Contains temporary files used by the LCquan application.
The application performs Cyclic Redundancy Checks (CRCs) to protect against malicious
changes to data files. A CRC can detect file corruption and attempted changes to data files
outside the application. The CRC calculates checksums for sets of data, using mathematical
formulas, and embeds the value within the file. Each time you open the file, the CRC
recalculates the checksums and compares them with the stored values. When you modify or
process data within the application, the CRC recalculates and stores new checksums.
In addition, the application includes a file tracking system that maintains a database of the
files created in or used by the application. When you open an existing project, the application
displays a warning if files within that project have been moved or modified (as determined
from the CRC value). The Audit Trail ensures that you can generate all electronic records
from the raw data.
2. Select the type of audit from the tabs at the top of the display.
The Audit Trail is comprised of four parts: the History log, the Event log, the File
Tracking log, and the Instrument Error log. The History log contains information about
every parameter change a user has made within an application experiment. The Event log
contains information about all the events that have occurred within the application and
the File Tracking log tracks changes made to files contained within an application. The
Instrument Error log lists instrument errors.
The installation information in this chapter supplements the documentation that Oracle
provides and does not replace it. Refer to your Oracle manuals for installation and
configuration details.
Note The procedures contained in this chapter describe how to install the Oracle9i
Client. The installation procedures for other versions or releases of the database might
differ from those described here.
1. Insert the Oracle Database Client compact disc. The Autorun installation program starts
automatically. If it does not, find and double-click the setup.exe file.
2. Click Install/Deinstall Products in the installation program. The Welcome page opens.
IMPORTANT Do not install the Oracle Server if a previous version of the software
is already installed. Remove previous versions before installing the new version. Refer
to your Oracle documentation for more information.
3. To remove a previous version of the Oracle client software before proceeding with this
installation, click Deinstall Products. The Inventory dialog box opens. Select the
previous version from the list, and click Remove.
4. Click Next on the Welcome page. The File Locations page opens.
IMPORTANT The Source Path box automatically fills with the location of the
installation files. Do not change the path.
5. In the Name box under Destination, type or select a name for the Oracle Home.
6. In the Path box, type or select the location for the Oracle components. Or click Browse
to search for a different location.
7. Click Next.
The Installation Types page opens.
9. Click Next.
The Summary page opens.
• If the Oracle Net Configuration Assistant does not run, click Next on the
Configuration Tools page.
When the installation is complete, the Configuration Tools page opens. A series of tools
automatically starts creating and configuring your database and Oracle Net Services
environments. The Configuration Tools page displays the results of running these tools.
11. Select the No, I Will Create Net Service Names Myself option.
12. Click Next.
The Net Service Name Configuration, Database Version page opens.
15. Enter the global database name in the Service name field.
16. Click Next.
The Net Service Name Configuration, Select Protocols page opens.
17. Select the protocol used for the database, and click Next.
The page that opens depends on the selected protocol.
For example, when you select the TCP protocol, the Net Service Name Configuration,
TCP/IP Protocol page opens.
Based on your choice of protocol, the software requests protocol parameter information.
18. Complete the specification for the selected protocol and click Next.
For example, on the Net Service Name Configuration, TCP/IP Protocol page, type the
host name for the computer where the database is located and select the Use the Standard
Port Number of 1521 option.
19. Click Next.
The Net Service Name Configuration test page opens.
20. On the Net Service Name Configuration, Test page, select the Yes, Perform a Test option
and click Next.
The Net Service Name Configuration, Connecting page opens and the Oracle Net
Configuration Assistant performs a connection test.
• If the test fails, click Back to review the information that you entered. Make any
necessary changes and try the test again.
21. On the Net Service Name Configuration, Net Service Name page, accept the default net
service name or type another net service name that is unique to the client.
22. Click Next.
The Net Service Name Configuration, Another Net Service Name? page opens.
23. On the Another Net Service Name? page, specify whether or not to configure another net
service name for this client.
• When you select Yes and click Next, the Oracle Net Configuration Assistant leads
you through the process of configuring another net service name.
• When you select No and click Next, the Net Service Name Configuration Done page
opens. Click Next again and click Finish to complete the Oracle Net Configuration
Assistant and return to the Configuration Tools page.
24. On the Configuration Tools page, click Next.
The installation is complete.
Watson Interface
This appendix describes Thermo Foundation Authorization Manager settings for the
Watson file interface.
Note To use the digital gateways, you must install the Xcalibur and LCquan XDK
components.
Contents
• Recommended Settings for Excel Reports
• About the Watson Digital Interface
If you specify Excel rounding, the exported values are restricted to three decimal places
consistently in the Excel reports. However, if you use this feature, the Excel reports do not
include a full precision value.
To use the Excel rounding feature, set the permission level to Allowed in the Foundation
Authorization Manager (see Setting the Excel Features). Before the Excel rounding feature
takes effect for the Watson digital interface, you must start and exit the application.
1. From the Windows taskbar, choose Start > All Programs >
Thermo Foundation x.x > Authorization Manager.
Thermo Foundation Authorization Manager opens.
3. In the controlled features list (lower left side), select the application, and click Expand
Tree.
The list of controlled features appears.
4. Under Quantitate Section, right-click the feature and choose Allow from the shortcut
menu for each of the following:
• Remove signature line from Excel report
• Allow Watson file interface Excel format
• Allow Excel Rounding
To use the digital interface with Watson 7.2 or later, refer to Installing and Using the Peak View
Gateway Between Watson and LCquan for instructions.
Index
A Automatic Logoff feature
about 47
access
password-protected screen saver restriction 47
restricting to folders and files 25
unauthorized
definition 1 C
prevention of, overview 9 chromatogram peaks
accessing the auditing database 20 normalizing detected peak to 100% 77
acquiring data normalizing highest peak to 100% 77
remote acquisition 6 comments about actions, requiring 62
time-stamping raw files during remote acquisition comments, setting predetermined list 67
always time-stamp 6 configuration file 74
never time-stamp 6
configuring instruments 117
Acquisition run dialog, setting permissions 76
configuring software applications
Acquisition section, configuration 75 checklist 2
Acquisition section, setting permissions 76 overview of 8
adding users 33 controlled feature settings, saving 74
antivirus scanning 125 controlling user access, overview of 9
archiving files 48 CRC Validator, checking files with 94
audit log, requiring comments for 62 CRCs
Audit Trail, definition 130 See cyclic redundancy check
Audit Viewer creating private groups 55
filtering entries 105 cyclic redundancy check (CRC)
Instrument Error Page 115 security 130
printing entries 108 using 93
sorting entries 107
starting from Windows desktop 102
tabs 104 D
use for auditing 101 data
auditing databases loss due to auto logoff, prevention of 47
accessing 102 time-stamp raw files during remote acquisition
configuring 11–14 always time-stamp 6
auditing databases, accessing 102 never time-stamp 6
Authorization Manager Database Configuration Manager 11
history log for 72 database filters, selecting files using 95
printing security settings in 73 database service
saving controlled feature settings in 74 See Thermo Foundation Database Service
databases G
Global Auditing database, accessing 101
Global Auditing database 102
workbook database, accessing 101
decimal place rounding 143
defining as secure, private groups 55 H
defining user requirements 8 history log
definition for Authorization Manager 72
private groups 7 for software applications 131
user groups 7 History page, Audit Viewer 104
device drivers, incompatible 121
documentation survey ix I
domain logon groups
importing permissions 65
defining as secure 54
incompatible device drivers 121
definition 50
inheriting permissions 64
drivers, adding for instruments 117
Instrument Configuration window 117
Instrument Error page, Audit Viewer 105, 115
E Instrument Setup section
event log 131 configuration 75
Event page, Audit Viewer 104 setting permissions 75
Excel
recommended settings 143 L
rounding decimal places in 78
layered applications
Explore section, configuration 75
auditing 20
Explore section, setting permissions 76
database properties 20
exporting permissions 65
LCquan feature permissions 74–78
locking the workbook 71
F locking workbook automatically after creating report 71
Fast User Switching feature 45 logging in and out 47
features, setting for LCquan 74–78
file tracking log 131 M
File Tracking page, Audit Viewer 104
Microsoft Access database, configuring 11
files
multi-user logon 47
configuring security settings for 25
permissions, setting 75
removing and archiving 48 N
tracking 130 normalization
filters, selecting files using 95 of detected chromatogram peak to 100% 77
firewall exception 126 of highest chromatogram peak to 100% 77
folder structure 129
folders O
configuring security settings for 25
permissions Operator Use Allowed 74
setting for root 26 Oracle database, configuring 11
setting for security 40 Out Of Date Instrument Drivers Detected dialog box 121
P S
patterns, using to select files 98 saving system information 123
peaks secure reporting 77
normalizing detected chromatogram peak to 100% 77 security features, within software applications 130
normalizing highest chromatogram peak to 100% 77 security folder
permission level Signature List 61 configuration file and 74
permission levels configuring security settings for 40
about setting 58 security server
definition 58 See Thermo Foundation Security Service
exporting and importing 65 Security Service
inheriting 64 See Thermo Foundation Security Service
setting 58 security settings
setting all 63 folders and files 25
setting all features to same 63 printing from Authorization Manager 73
settings 74–78 security, system 1
permissions setting for folders and files 37 selecting files
printing security settings 73 using a pattern 98
private groups using database filters 95
creating 55 Set To Same button 63
defining as secure 55 setting permission levels 58
definition 7, 50
signature list definition 61
editing 56
Status values for CRC Validation 95
protecting records, overview of 9
study description 130
survey link ix
Q system information
Quantitate section displaying 123
configuration 75 saving 123
setting permissions 76 system security 1
R T
raw files Thermo Foundation Database Service
time-stamping during remote acquisition confirming properties of 20
always time-stamp 6 functions 20
never time-stamp 6 Thermo Foundation Database Service Properties dialog box
records, protecting 9 Log On page 22
registry key, Windows 42 Thermo Foundation Security Service
remote acquisition confirming properties of 20
always time-stamp 6 functions 22
prevent time-stamping 6 properties of
removing files 48 secure file operations 22
removing users 33 user authentication 22
reports verifying properties of 22
lock workbook after creating report 71 Thermo Foundation Security Service Properties dialog box
permissions for creating 77 Log On page 20
rounding decimal places in Excel 78 time stamps
setting up secure reporting 77 about 6
root folder time-stamping raw files during remote acquisition
allowing change 74 always time-stamp 6
configuring security settings for 26 never time-stamp 6
tracking, files 130
troubleshooting
IT considerations 125
out-of-date drivers 121
version information 123
U
unauthorized access
definition 1
prevention of, overview 9
user access, controlling 9
user authentication 20
user groups
definition 7
editing 56
single user belonging to multiple 53
user groups, Authorization Manager
planning 50
single user belonging to multiple 50
user requirements, defining 8
V
Version Info dialog box 123
viewing system information 123
W
Watson interface, setting features for 143
Watson LIMS, Oracle database 11
Windows Active Directory Domain groups 51
workbooks
already marked as opened 75
databases, auditing 102
description 130
locking 71
locking automatically after creating reports 71
setting permissions 75
X
Xcalibur system account 126
XReport templates, secure 77