Empower 3 Software Enterprise e PDF

Empower 3 Software Enterprise
System Administration and Maintenance

Empower 3 Software Enterprise
System Administration and Maintenance
Copyright Notice
2011 WATERS CORPORATION. PRINTED IN THE UNITED STATES OF

AMERICA AND EUROPE. ALL RIGHTS RESERVED. THIS DOCUMENT OR PARTS
THEREOF MAY NOT BE REPRODUCED IN ANY FORM WITHOUT THE WRITTEN
PERMISSION OF THE PUBLISHER.
The information in this document is subject to change without notice and should not
be construed as a commitment by Waters Corporation. Waters Corporation assumes
no responsibility for any errors that may appear in this document. This document is
believed to be complete and accurate at the time of publication. In no event shall
Waters Corporation be liable for incidental or consequential damages in connection
with, or arising from, its use.
Waters Corporation Registered Trademarks - symbolized by .

ACQUITY, ACQUITY UltraPerformance LC, ACQUITY UPLC, Alliance, Atlantis,
Bondapak, Bondapak, CapLC, CIA, CIA-Pak, Connections, Connections INSIGHT,
Durapak, ESCi, Integrity, Micromass, Millennium, nanoACQUITY UPLC, Nova-Pak,
NuGenesis, Oasis, PATROL UPLC, PIC, PicoTag, PowerStation, PrepPak, Q-Tof
Ultima, Quattro Ultima, Rheometrics, Rheometrics Inc, Sep-Pak, Spherisorb,
Styragel, Symmetry, SYNAPT, TA, Taper-Cell, Triwave, TRIZAIC UPLC,
UltraPerformance LC, UPLC, Viridis, Waters, Waters Quality Parts, Xevo, and XTerra.
Waters Corporation Unregistered Trademarks - symbolized by .

Accell, AccellPlus, AccQFluor, AccQTag, AccuPure, AccuSep, ACE, ACQUITY UPSFC,
ActION, ActiveWell, Alpha Bak, ALPS, Alliance Filtration System, ApexTrack, ASTRA,
AutoBlend, AutoBlend Plus, AutoLynx, AutoProbe, AutoPurification, AutoPurify,
AutoSpec, AutoSpec Premier, AutoTag, Baseline, BEH Technology, BioLynx,
BiopharmaLynx, BioSuite, Breeze, c.authorize, ChromaLynx, ChromPlot, CIMS, Clear-
100, c.news, Corasil, CSH, c.shop, DDA, DDTC, Delta-Pak, Delta-Prep, Dextro-Pak,
Dimension, DIOS-target, Discus, DisQuE, DriftScope, Dual Cell, DXC, eApplications,
eCord, ECP, eLab Notebook, Empower, e-MS, EnantioSelect, Engineered Simplicity,
E
Enhancer, Envirogel, EPCAS, e-QUILL, EQUILL, Everflow, ExpertEase, Expression
High Definition, Proteomics, Fam-Pak, FractionLynx, GCT, GCT Premier, Gen-Pak,
Glyco-Pak, Guard-Pak, HDMS, HEX, High Definition Mass Spectrometry, High
E
Definition MS, HSPgel, IC-Pak, Identity High Definition Proteomics, i-FIT, Intelink,
Intelligent Speed, IntelliStart, IonDRAG, IonSABRE, iRequest, IS, IsoPRIME, LAC/E,
Laser Probe, LC-DDA-MS, LC-MALDIprep, LCT, LCT Premier, LectraBond, LockSpray,
MagLift, M@LDI, M@LDI HT, M@LDI L, M@LDI LR, MALDI micro, MALDI micro MX,
MALDI SYNAPT, MarkerLynx, MassFRAGMENT, Mass-Informatics, Massive Inference,
MassLynx, MassPREP, MassSeq, MassSpec, MassTrak, MassTRANSIT, MaxEnt,
Maxima, MAXspec, MegaFlow, MetaboLynx, MicrobeLynx, MilliLab, MilliNet, MilliTrap,
MUX-ExactMass, MUX-technology, Nano LC, NanoEase, NanoFlow, NanoLockSpray,
nanoTile, NeoLynx, OBD, OpenLynx, OpenLynx Global SERVER, OpenQuan, Ostro,
pDRE, PepSeq, PerformancePLUS, Platform ICP, Platform ICP Life, Platform LC,
Platform LCZ, Porapak, Porasil, Posiive, PowerLine, Precursor Ion Discovery, Prep
Page 1 of 2 Rev. 27011
3000, PrepLC, ProfileLynx, ProSpec, PROtarget, ProteinLynx, ProteinLynx Global
SERVER, Protein-Pak, ProteinProbe, PSD MX, Purification Factory, Q-DIS/QM, Q-
DIS/R, Q-Tof, Q-Tof micro, Q-Tof Premier, Q-Tof Ultima, QA-1, QuanLynx,
QuanOptimize, QUANPEDIA, QuanTof, Quattro LC, Quattro micro, Quattro micro GC,
Quattro Premier, Quattro Ultima Pt, QuickBlot, RADAR, Radial-Pak, RapiGest, Real-
TIME LC, RPS, S2K, SAM, Sample Centric, SAT/IN, ScanWave, SDMS Vision
Publisher, Sentry, Silica-Pak, Sirocco, StepWave, Stratus, Sugar-Pak, SunFire,
SuperPremium, Symmetry300, SymmetryPrep, SymmetryShield, SystemsQT, T-
Wave, TaperBeam, TaperSlit, TargetLynx, The Science of Whats Possible,
ThermaBeam, Tiger, Transform, Trap-Pak, Ultrahydrogel, UltraLoop, Ultrastyragel,
UNIFI, UPSFC, Page, Porasil, Styragel, V-Optics, VanGuard, Visual Method
Builder, W-Optics, Waters Critical Clean, Waters Dimensions, WAVS, WebBrowser,
WHISPER, WISE, WISP, WorkFlow, XBridge, Xenon-Pulse, Xenor, XPoSure, XSelect,
Zeta-1, ZQ and ZSpray.
Additional trademarks
*GPEC - registered in foreign countries ONLY
CombiChrom, CombiPrep, and CombiScreen are trademarks of YMC, Co. Ltd.
YMC is a trademark of YMC Co. Ltd.
Other trademarks or registered trademarks are the sole property of their

respective owners.
Page 2 of 2 Rev. 27011

Table of Contents
1. Chapter 1 Enterprise Architecture
2. Chapter 2 Enterprise Installation (server)
3. Chapter 3 Node Installation
4. Chapter 4 Push Installation Automation
5. Chapter 5 Administrative and Management Tools
6. Chapter 6 Node and System Management
7. Chapter 7 User Management
8. Chapter 8 Project Management
9. Chapter 9 Operational Mechanisms
10. Chapter 10 Introduction to Oracle 11g
11. Chapter 11 Database Management using Web Console
12. Chapter 12 Server Backup Disaster Recovery

Enterprise Architecture
Rev. 30011 Chapter 1: Page 1 of 37

Waters Confidential and Proprietary Information

Typical Empower Network

This technology has been fully inspired by the idea of the
Chromatographic Intranet where anywhere on the network you
will have the feeling as if you were next to the instruments.
The use of dedicated Acquisition servers called LAC/E32 allow you
to acquire data remotely with full hard disk buffering capability in
case of a network interruption.
This can be fully adapted on all corporate networks regardless of
how big it is. Inter-Building, Inter-Site, Inter-country and even into
your home.

Empower Network Scalability

Ultimate flexibility and scalability allows you to make the
most of your chromatography software, without
compromising lab performance and data integrity.
The key to Empower Softwares scalability is that you have
the same software interface regardless of the configuration.
Laboratories have the ability to grow without requiring new
software.
Empower 3 Workgroup changes make a small network an
attractive solution
Removed the complexities of the Node Licenses
Small network for up to 10 user
Appropriate solution to support regulatory compliance
Cost effective solution for development and test servers

Parts of the Empower Enterprise Architecture

The following are the different parts of the Empower Enterprise
Architecture and their corresponding functions:
A - Acquisition and Control
Acquisition client - A client directly connected to analytical
instruments via an Ethernet card, COM port. Its capabilities
include controlling instruments, acquiring data and processing.
LAC/E32 Acquisition server, a computer directly connected
to analytical instruments via an Ethernet card, COM port. It
is primarily responsible for data acquisition and instrument
control.
D Database
Server - The repository unit and storage location of the
Oracle Database, its program files and raw data files.
P - Processing and Reporting
Client - A computer with the Empower program files
primarily used for processing and interfacing with
acquisition clients and LAC/E32 modules.
Note: The following slides use the following conventions, namely, A,

D and P.

The flexible architecture allows instruments to be connected to the

network however the customer requires. The Lace Acquisition
server takes care of all instrument communication, leaving your IT
to manage the clients, servers and storage
Empower can be deployed in many tested configurations
Traditional Client Server with Windows servers
Using Citrix Server Farms to deliver to client PCs
With Virtual Server configurations
With UNIX based servers

There are two advantages of this architecture: reduce software validation

and the ability to run the Citrix clients on different clients, e.g. apple,
handheld devices etc.
Since activity is occurring on Citrix server, bandwidth requirements are
reduced. The screen refreshes, key strokes and mouse clicks are the
only things that travel over the network between the Citrix client an
Citrix server.
Faster and simpler software deployment
Empower Client loaded on the Citrix Server and instantly available
Software deployment can be accommodated very quickly - usually in
hours or days rather than weeks or months.
Reduce the time required for validation
By consolidating a number of Empower clients into a single Citrix
server, software qualification is reduced to the Citrix server itself - the
clients do not require qualification.
The Citrix Clients use old hardware or OS not supported by Empower
Since the Empower client is only running on the Citrix server,
customers have the ability to leverage unsupported hardware such as
a Macintosh computers or Unix workstations and hardware running
operating systems not supported by Empower 3.
Simpler administration
Administration can be effectively limited to the Citrix server
Citrix is for the application, not the database


An Oracle RAC database is a clustered database. A cluster is a group of

independent servers that cooperate as a single system. Clusters provide
improved fault resilience and modular incremental system growth over
single symmetric multiprocessor (SMP) systems. In the event of a
system failure, clustering ensures high availability to users. Access to
mission critical data is not lost. Redundant hardware components, such
as additional nodes, interconnects, and disks, allow the cluster to provide
high availability. Such redundant hardware architectures avoid single
points-of-failure and provide exceptional fault resilience.
With Oracle Real Application Clusters, we de-couple the Oracle Instance
(the processes and memory structures running on a server to allow
access to the data) from the Oracle database (the physical structures
residing on storage which actually hold the data, commonly known as
datafiles). A clustered database is a single database that can be accessed
by multiple instances. Each instance runs on a separate server in the
cluster. When additional resources are required, additional nodes and
instances can be easily added to the cluster with no downtime. Once the
new instance is started, applications using services can immediately take
advantage of it with no changes to the application or application server.
Oracle Real Application Clusters is a shared everything architecture. All
servers in the cluster must share all storage used for an Oracle RAC
database. The type of disk storage used can be network attached storage
(NAS), storage area network (SAN), or SCSI disk.
Servers connected by a high speed connection, non-shared internal
storage, shared storage subsystem

Scalability- Just add servers as necessary rather than replace one server with a
larger server (traditionally done)-no outage required. Applications that have
traditionally run on large SMP servers can be migrated to run on clusters of small
servers.
Oracle Real Application Clusters architecture automatically accommodates rapidly
changing business requirements and the resulting workload changes. Oracle
automatically balances the user load among the multiple nodes in the cluster.
Administrators can painlessly add processing capacity as application requirements
grow. The Cache Fusion architecture of Oracle RAC immediately utilizes the CPU
and memory resources of the new node.
The Oracle RAC database can be installed, configured, and managed from a single
location.
Oracle Real Application Clusters has been designed for high availability and
scalability. By providing protection from hardware and software failures, Oracle
Real Application Clusters provides systems availability ensuring continuous data
access. Its scale out and scale up features offer a platform, which can grow in any
direction allowing enterprises to grow their businesses. Existing applications as
well as newly developed applications benefit from the transparency Oracle Real
Application Clusters provides. Application development as well as administration
and change management thus become much easier allowing reduction in total
cost of ownership. Oracle Real Application Clusters is unique to the market with
its offering and capabilities. Oracle RAC is used by thousands of customers
worldwide in all industries in mission critical and many other application
environments.
Chapter 1: Page 10 of 37





A virtual machine is a tightly isolated software container that can run its own operating systems and
applications as if it were a physical computer. A virtual machine behaves exactly like a physical computer and
contains it own virtual (i.e., software-based) CPU, RAM hard disk and network interface card (NIC).
Virtualization lets you run multiple virtual machines on a single physical server, sharing the resources of
that single computer across multiple environments. (consolidation)
An operating system cant tell the difference between a virtual machine and a physical machine, nor can
applications or other computers on a network. Even the virtual machine thinks it is a real computer.
Nevertheless, a virtual machine is composed entirely of software and contains no hardware components
whatsoever. As a result, virtual machines offer a number of distinct advantages over physical hardware.
Each virtual machine contains a complete system, eliminating potential conflicts
Run Empower2, Empower build 1154 and Breeze 2 on the same computer
All have different OS versions, Oracle versions, etc.
virtual machines are incredibly portable and easy to manage
You can move and copy a virtual machine from one location to another just like any other software file,
using any standard data storage medium from a USB flash memory card to an enterprise storage area
networks (SANs).
Benefits
Reduce capitol because: Increased energy efficiency
requires less hardware - Run multiple, conflicting operating systems and applications on a single
computer
Rapid deployment and disaster recovery
Virtual images are similar to computer images but are hardware independent and can be deployed on
dis-similar computers
Require less time to deploy than a conventional installation
Validation benefits
Changes to other environments on same computer do not affect the validation of the Empower
environment
High Availability, server consolidation, scalability and reduction in capital costs
Running a single OS and single application on a server leaves that server or client underutilized
A virtual machine lets you share the resources of a single physical computer across multiple virtual
machines for maximum efficiency.
requires less hardware reduces your physical infrastructure footprint by consolidating excess server
and desktop hardware
Clusters - you dont need to assign servers, storage, or network bandwidth permanently to each
application. Instead, your hardware resources are dynamically allocated when and where theyre needed.


A hosted approach provides partitioning services on top of a

standard operating system and supports the broadest range of
hardware configurations.
In contrast, a hypervisor architecture is the first layer of software
installed on a clean 64 bit-based system (hence it is often referred
to as a bare metal approach).
Since it has direct access to the hardware resources, a hypervisor
is more efficient than hosted architectures, enabling greater
scalability, robustness and performance.



Probably more important than controlling the multitude of

instrument types in the ability for the software to handle advanced
data processing of that data, permitting you to create meaningful
results, direct from the software of acquisition. We will touch on
just a few of these applications today.

Manages all dissolution result calculations eliminates transfer

to Excel get reports straight from Empower
The data processing capabilities automatically apply
appropriate correction factors and speed up calculation and
reporting of particular dissolution parameters.
Combining Empower Software with a Waters Alliance
Dissolution System sets the standard for automated
dissolution testing.
Combined software and hardware solution.

Before: Time consuming, repetitive tasks consisting of several

sequential steps
After: faster and Easier Method Validation
It automatically manages and documents the method
validation workflow in one software package
It displays the status of on-going validation studies This
allows you to see at what you have done and what you need
to do next for each validation test or validation characteristic
It determines all results and statistical calculations in
Empower which eliminates the data transfer step which we
have already discussed. eliminating time-consuming data
transfer to spreadsheets and the associated problems of
transcription errors and security concerns
And this processing step is done on all components at the
same time . The time that it takes to do this processing, by
the way is reduced from the time it currently takes you to
the time that it takes to click a button
The software determines if your results are out of
specification
It allows you to generate reports with standardized
templates
Estimate time saved between 50% 80% as compared to
the current process.

MVM automatically manages and documents the method

validation workflow in one software package
It displays the status of on-going validation studies This
allows you to see at what you have done and what you need
to do next for each validation test or validation characteristic
It determines all results and statistical calculations in
Empower which eliminates the data transfer step, eliminating
time-consuming data transfer to spreadsheets and the
associated problems of transcription errors and security
concerns
And this processing step is done on all components at the
same time. The time that it takes to do this processing, by
the way is reduced from the time it currently takes you to the
time that it takes to click a button

The software determines if your results are out of

specification compared with acceptance criteria
It allows you to generate reports with standardized templates

The Empower Softwares integrated Chemical Structures improves

data management and reporting all within the same software
interface. By associating chemical structures with the peak
component information, you can integrate chemical structures into
reports and improve search capabilities through structure search as
an alternative to a traditional text search.

If we look at how method development is traditionally done in labs.

The method is developed using a certain approach often One
Factor At a Time (OFAT) for performance. Possibly the
development is supplemented with simulation software. The
method is sent on for validation, and may or may not succeed. If it
does not, it is sent back for re-development.
This is a common cycle, its something we hear often as a
challenge facing our customers. The reason this is occurring is that
there is no consideration of robustness in the development stage
only in the validation stage.
The Quality by Design (QbD) is a systematic approach of
development with pre-defined objectives it incorporates risk
management. It is recommended by the FDA and ICH Q8R2.

Support for Fusion Method Development software (version 9.6) for

use with Empower 3 is available.
Fusions robustness simulator will exclude the settings that do not

meet method performance and method robustness requirements.

Theres a story behind the two chromatograms you see on the

screen, it is a real example. As Chemists, many of us have
struggled with a method.
This is the situation behind the picture on top.
A group worked to improve an HPLC method over a period of
about 45 days, with little success.
On the bottom is what was able to be accomplished for the same
sample in only 2 days using Fusion and ACQUITY UPLC.
In this example, the potential to resolve a challenging
separation more quickly is quite clear.
What other reasons interest Chemists in a Quality by Design-
based approach to method development using UPLC?
the need to increase efficiency (by speeding up method
development, reducing solvent usage).
increased confidence that a method can be validated or
successfully transferred between sites.
desire to modernize/standardize methodology, and align with
the latest regulatory guidance, for instance as part of a
global QbD initiative.

Waters Data Converter 2 will support Empower 3

Add-on, installed on Empower client PC
Supports Empower 2 Personal and Network
Empower 3
Based on SDMS data conversion technology
Manual import of raw data into Empower
Select data individually or whole directory structures
Individual mapping of data properties into fields and custom
fields
Group data into new sample sets or append to existing
Automated import of raw data into Empower
Configure multiple scan directories with individual parameters
Supports multiple converters
Supports data management
of imported data
Independent from Empower release cycle

Just a short impression, how the new software looks

To the left a Windows Explorer style tree view. Users can select
single or multiple data sets and folders with multiple data sets
(recurses into subfolders)
1) Transfer data into the processing table (right) via drag & drop (or
context menu)
Data will be checked, if they are fit to be imported relative to the
selected import filter (only those that are seen fit are imported into
the table)
2) (optional) Change import parameters
could be Sample set name policy (auto increment, use field
contents for name, set one sample set for all data in table, attach
data to existing sample set, make each data set a sample set)
could be field mapping from original data properties to Empower
fields or custom fields
3) Import set.
Status is shown in data row, plus status bar, Import report is

shown in log window (with channel new IDs), diverse file logging
options available.

Auto mode (running => config icons grey): Scan lines have
individual parameters (Empower project, import filter, field
mapping, sample set policy). Directories are scanned consecutively,
New data are added to the import table and
imported according to parameters (like in manual mode).
It is possible to log out and leave the auto mode running.

EDM is the SDMS based Empower option

Automatic project archive includes all kind of checksums and
security mechanisms to make sure data do not get lost or changed
on the way. A manual trigger from Empower is possible too.
After successful transfer to EDM projects can also be deleted from
Empower. Deletion is only done after all security checks are
successful.
Moving data to EDM provides searchability on project detail level -
if data are converted also on result down to custom field level
Beside the project archive (rawdata) , all reports may be printed
into EDM.
During this transfer the metadata are extracted which makes
finding the data in the EDM webclient easy. There is a full access
control allowing reviewers, approvers or auditors to look at the
data without Empower.

So lets look at data. Samples are analyzed by instruments that

produce two streams of data..FILES and PRINTED reports. The
underlying technology in the Waters NuGenesis SDMS captures
both data types and automatically extracts metadata (data about
the data) and populates an Oracle relational database.
The printed report is stored as an enhanced metafile and can be
viewed by anyone that has the security privilege to do so.
The files remain for a given time within the SDMS system then,
through our offline storage manager, the files are sent to a storage
device with a pointer so you can retrieve and restore the file at
some time in the future.
In this way the total data footprint is captured and cataloged. Key
using other programs is the re-use tools within the Waters
NuGenesis SDMS system

This slide shows screen shots of the electronic signature in EDM of

a captured Empower report.
Besides one common viewer for all different printed reports the
EDM technology has another key advantage. Printed data remain
live which means text, grapics and table content can be reused in a
select and send process. Tables even keep their structure which is
the first step of facilitating a data transfer process to other
systems.

SQT Productivity Kit for SDMS provides a global solution for all
instruments in the lab Empower and non Empower CDS controlled
systems.
Electronically capturing and cataloguing qualification
documentation from Empower CDS and other instruments into
SDMS, a secure compliant-ready repository
Extracts results of qualification tests, generates automatically
Qualification Summary. Review and Signoff through a web browser

Integration with LIMS, SAP, eLab Notebooks, Scientific Data

Management System (SDMS) databases etc
Using the robust Empower Toolkit interfacing tools Empower reads
the sample work list generated by a LIMS, configures the
appropriate instruments, process chromatograms and reports the
analytical results back to the LIMS.
More information on http://www.waters.com/SDMS

Enterprise Server Installation
Rev. 29011 Chapter 2 Page 1 of 70


The Server Hard Drives

The minimum configuration of the Empower server uses four hard
drives, partitioned into four or five logical drives.


The Empower 3 Raw Data Share as a Separate Server

If the Empower 3 Raw Data Share is on a separate physical server,
the archive logs and mirrored files that would normally reside with
the raw data should be located on the same physical server as the
database datafiles.






To optimize the performances of the server,

depending on the sever usage, the right registry
settings must be selected.
The table indicates the correspondence between the
previous option setting in Windows 2003 and the
registry values in Windows 2008

Registry Settings : Optimization for Network Application



Waters policy on Oracle Critical Patch Update Testing

Waters policy is not to test every Oracle Critical Patch Update
that may be released. Waters will review each Oracle Critical
Patch Update and, if critical to Empower 3, Waters will
perform a set of regression tests including, Data Acquisition,
Data Buffering in a network configuration, Benchmark
Calculations and Printing.
In an event that a problem arises with the loading of a
particular update, Waters is dedicated to delivering the
most effective and prompt resolution possible. Once
testing is complete, Waters will make the update available
for installation.
If it is determined, after reviewing the information
available from Oracle, that no testing is necessary, Waters
will publish that finding on the Waters Web Site.


Installing Empower on the Server

Insert the Empower DVD into the DVD-ROM.

Installing Empower on the Server

Even if you are an administrator the User Account Control requires
you Run the setup as Administrator

Installing Empower on the Server (continued)

Select the language then click OK.


At the Empower 3 Enterprise Software page, click Install
Empower Software


At the Empower 3 Product Type page, select the configuration for
your server Workgroup or Enterprise


At the Empower 3 Product Type page, select Server


At the Customer Information page, enter the appropriate user
name and organization. Enter your Total Assurance plan number in
the Serial Number box, then click Next.


At the License Agreement page, read the agreement, select I
accept the license agreement, then click Next.


If Oracle is not present, the user is given the following 3 choices:
1. Complete server installation . This is the standard installation on the server

which includes building the database.
2. Empower software only. In this case, Empower client stack and script are
installed without installing Oracle and without installing the database. This
installation is designed for when a customer has his own Oracle license and has
installed Oracle and built Empower database separately from the Empower
installation. (This can be performed on either the server or on a client)
3. Empower and Oracle software only. This installation is designed for an
installation on a custom database or for a RAC installation.
If Oracle < 11.2 is present, the installation stops

If Oracle 11.2 or higher is present, the user is given the following 2 choices:
1. Complete server installation. When the user chooses this option , they are
required to use the version of Oracle that is already installed.
2. Empower software only (same as above)
The option to install Empower and Oracle Software only is not given as the
correct Oracle version is already present.
Note: If the user has Oracle present but wants to install Oracle using the Empower
installer, they need to manually delete the existing Oracle install and then launch
the Empower installer again.


At the Import System Object page, tick off Import System Object
only during a migration, then click Next.
Only import an existing Millennium32 v4.0, Empower 1154 or
Empower 2154 database using the System Object Export utility
during migration. The System Object Export utility exports all
database object information with the exception of projects. To
complete the upgrade, projects and Libraries must be backed up
from the previous version of the software, and then restored to
Empower 3.


At the Destination Folder page, by changing the drive letter of the
provided paths, specify the drive locations then click Next.
Empower Application and Empower Oracle on Program Disk
Empower Projects on Raw Data Disk
Empower Database on Database Disk


At the Database Options page, specify the locations of the archive
and mirror directories by changing the drive letter of the provided
paths, then click Next.


At the Oracle Database Domain Name and SID page, enter the
Oracle System Identifier (SID) and the Oracle Domain name, then
click Next.
The database domain name typically consists of
computername.domain (for example,
BACKUPSERVER.CONNECTIONS.COM where the computer name is
BACKUPSERVER and the domain is CONNECTIONS.COM).
Note: The database SID can be any combination of alphanumeric

characters, up to 8 characters. However, it must start with WAT to
automatically populate the Empower 3 database field in the login
window. WAT10 is the default.


At the Ready to Install the Program page, click Next to start the
program file installation.


The Install page appears, indicating the progress of the
installation. By default, the Empower 3 installer installs both
Oracle 11g and Empower 3.
The Database Configuration Assistant page appears, indicating the
progress of the installation.


1. At the InstallShield Wizard Completed page, click Finish.
2. Then, select Yes, to restart the computer now.
Note: You must restart your system for the configuration changes
made to the Empower server to take effect.



Configuring the Database Service Name

Configure the server with a Database Service Name to allow the
server to be used as a client for troubleshooting purposes.
1. Click Start > Programs > Empower > Oracle Empower11g
> Net Configuration Assistant to run the Oracle Net
Configuration assistant.
Note: You must log in using an account that has administrators

privileges.

Configuring the Database Service Name (continued)

1. At the Net Configuration Assistant: Welcome page, select Local
Net Service Name Configuration, then click Next.
2. At the Net Service Name Configuration page, click Add, then click
Next.


At the Service Name page, enter the global database name, and
then click Next. The global database name is the combination of
the Oracle Service Identifier (SID) and the database domain name,
as supplied during installation.
For example, if you supplied an SID of WAT10 and a domain
name of BackupServer.Connections.com during installation
The global database name is WAT10.
BackupServer.Connections.com.

To see the Listener status: in command prompt type LSNRCTL

STATUS
The Global Database Service has 1 instance
The commands LSNRCTL START or LSNRCTL STOP can also be
used to start or stop the Listener.


At the Select Protocols page, ensure that TCP is selected,
1. Then click Next.
2. At the TCP/IP Protocol page, in the Host name field, enter either
the fully resolved host name (computername.domain.dns) or the
TCP/IP address of the server where the Empower database resides.
Leave the default port selection at 1521, and then click Next.
Note: Using the IP address of the server for the Host Name avoids
potential name resolution issues and improves performance.
Note: If you have configured multiple listeners and you want this
client to use one, click Use another port number and enter the
appropriate port number.


At the Test page, select Yes, perform a test, then click Next.
The test is automatically performed and will fail initially with the
ORA-01017 invalid username/password error due to having
the wrong default user name and password (hard coded by
Oracle) which must be changed.
Attention: If the test failed for any error other than ORA-01017,
contact Waters Technical Support.
1. Click Change Login.


1. Enter System as the Username and Empower as the Password,
then click OK to perform the test.
Note: Empower is the default password for the Oracle System
account.
The test should succeed. If not, review the entries, make
appropriate changes and test again.
2. Click Next.


1. At the Net Service Name page, enter a name in the Net Service
Name field, then click Next.
The name that you enter appears in the Database field of the
Empower Login dialog box. In general, this name can be any
alphanumeric string. However, when using a client in conjunction
with a LAC/E32 Acquisition Server, the client and the LAC/E32
Acquisition Server must use the same net service name.


1. At the Another Net Service name? Page, select No, then click
Next.
2. Click Next at the Net Service Name Configuration Done page.


1. Click Finish to exit the Welcome page of the Oracle Net
Configuration Assistant Wizard.
Note: The file modified using Oracle Net Configuration Assistant,

TNSNAMES.ORA, is very syntax-sensitive! You should only use
Oracle Net Configuration Assistant to modify the net service name
settings. If you modify the TNSNAMES.ORA file manually, then
Oracle Net Configuration Assistant may no longer work.

Configuring a Shared tnsnames.ora File

On the Empower Database Server, locate the drive installed
with the Oracle Program files and browse to the
\Empower\Oracle\Oracle10g\Network\Admin directory.
1. Locate the tnsnames.ora file, right-click the file
2. Click Copy.
Note: If you have more than one Empower Database Server,
add them to the tnsnames.ora file using the Net Configuration
Assistant prior to copying the tnsnames.ora file.
Browse to the drive installed with the raw data files, and
browse to the \Empower\Projects directory and paste the
tnsnames.ora file into the folder.
Note: Waters recommends that the share be placed in the same
directory that will hold Empower raw data files. Custom
directories may be used, but if so, the share permissions must
be set as described in the next page.

Configuring the Empower Projects Directory on Windows 2008

Server (continued)
1. Click Advanced Sharing
2. Select Share this Folder
3. Enter the Share name: Waters_Projects$


Server (continued)
1. On the Share Permissions click Add type SYSTEM
2. Allow Full Control Permission for SYSTEM


Server (continued)
1. Next, you need to set the security settings..
2. Click the Security tab.
3. Click Advanced


Server (continued)
1. On the Advanced Security settings page, click Change
Permissions
2. Remove the check mark beside Include inheritable
permissions from this objects parent, and in the Windows
security box
3. Click Add
4. Use Remove to remove all users except SYSTEM
5. Allow Full control permissions for SYSTEM


Server (continued)
1. Select Permissions tab
2. Select Permission Entries Everyone
3. Click Change Permissions
4. Click Add type Everyone
5. Click OK
6. Allow the following permissions for Everyone:
a. Traverse folder/execute file
b. List folder/read data
c. Read attributes
d. Read extended attributes
e. Read permissions
7. Click OK
8. Select Replace all child object permissions from this
object.
9. Click Apply
10.On the Windows Security message Click Yes
11.Click OK
12.On the Permission Tab, Click OK
13.Click Close

Installing Empower License and Options

1. From Start, click Start > All Programs > Empower >Waters
Licensing Wizard
a. See page 4-18 of the Empower 3 Installation and Configuration
Guide
2. Logon using the System account
3. Request software registration to create a Registration File. This
file stores your license information registration.
If your computer has Internet access, connect to the Waters

License Activation Web site
https://www.waters.com/activate/licenseintro.htm
If not, move the registration file you have just created to a
computer with Internet access and connect to the Waters License
Activation Web site.
Follow the instructions to obtain your license activation file. You
must have either your license and option serial numbers or the
order number(s) of the purchased licenses and options.
The Waters License Activation Web site will provide the license
activation file that you place in a file location accessible to your
Empower 3 computer.

Installing Empower License and Options (continued)
1. Log into the Waters Licensing Wizard and select Activate

Licenses.
Browse to select the license activation file you downloaded from
the Waters License Activation Web site.
You must process the activation on the same database on which
you initially created the registration file.
On the License Activation Complete page click Finish. A list of
successfully activated licenses and options appears.

Running Verify Files

To run verify files:
1. Select Start > Programs > Empower > Verify Files. The File
Verification utility compares the installed Empower files checksum
with a previously stored checksum, and then creates a File
Verification Result log. Review the contents of the file. You can
print or save a copy of the results.
2. Select File > Exit.

Registering Server Printers

To register printers:
1. Select Start > Programs > Empower > Register Empower
Node Printers.
2. Review the list of printers that are currently registered (if any).
If the printer you require is not on the list, click Get Printers,
select the printer, then click OK.
3. Click OK to save the changes and close the dialog box.
Note: Printers must be configured in the OS before they are
registered with Empower.




Note: For more information on Windows 2008 privileges, see the

Windows 2008 Help and User documentation.

Operating System Administrator Account Privileges

The system account and the administrator account
(Administrators group) have the same file privileges, but they
have different functions. The system account is used by the
operating system and by services that run under Windows.
There are many services and processes within Windows that
need the capability to log on internally (for example during a
Windows installation). The system account was designed for
that purpose; it is an internal account, does not show up in
User Manager, cannot be added to any groups, and cannot
have user rights assigned to it. On the other hand, the system
account does show up on an NTFS volume in File Manager in
the Permissions portion of the Security menu. By default, the
system account is granted full control to all files on an NTFS
volume. Here the system account has the same functional
privileges as the administrator account.
NOTE: Granting either account Administrators group file

permissions does not implicitly give permission to the system
account. The system account's permissions can be removed
from a file but it is not recommended.


Changing the Passwords of Empower System User Accounts

Change the Empower System user account password the first time
you log in and regularly thereafter to maintain system security.
To change the system account password:
1. In Configuration Manager, select the Users view.
2. Select the user System in the right pane and right-click.
3. From the menu, select Properties.
4. In the General page, enter the new password in the New
Password and Confirm New Password fields.
5. Click OK.
Note: You must be logged in to Empower as an administrator to
perform this procedure.

The Server Hard Drives

The minimum configuration of the Empower server uses four hard
drives, partitioned into four or five logical drives.


Server File Organization

Here is a look at the Empower Database directory on the
Database drive.


Server File Organization (continued)

Here is a look inside the Empower Projects directory on the
Raw Data drive. There is a folder for each project defined in
the Empower software.
In each project folder is a separate file for each channel of
data acquired (d*.dat). The number contained in the file
name is the Channel ID given to the data file by Oracle
and is used to link the data with the sample information
and results.

The files in the Script and Bin folders are very critical files. They
are tested during the Verify File process to verify if their checksum
was not modified during the installation.
The result is written in the Checksum.txt file stored in the Script
directory.


Disconnecting dead connections

You can configure Sqlnet.ora file to automatically disconnect dead
connections
Open the file with Notepad
Enter the following commands:
1. SQLNET.AUTHENTICATION_SERVICES = (NTS)
2. SQLNET.EXPIRE_TIME = X
Enables NT Security Authentication Service on the database server

The SQLNET.AUTHENTICATION_SERVICES is always NTS on the
Database Server and always NONE on the Client
Where X equals the number of minutes after which you want the
database to check for dead connections
For example every 10 minutes (X =10 )
Tip: if you set this parameter too small, such as 2 minutes, database
performance is sometimes slowed
Reboot the database sever after the modifications

Server File Organization (continued)

Here is a look at the Empower directory on the Program
drive. It shows the script, the database, the archive and
network directories.

Node Installation

Node Installation

Node Installation

Node Installation

Node Installation

Node Installation

Node Installation
On the Workstation, Client or LAC/E and Server the minimum

configuration is verified and if not reached then the installation will
stop.
The recommended configuration will ensure the best performances
For any new Empower 3 Feature Release or Service Pack read the
Release Notes before the installation

Node Installation
Adjust hardware on your needs:

A computer, running Empower on multiple system at the same
time, as well as running office and mail system may require more
power than a machine dedicated to Empower.

Node Installation
User Account Control (UAC)

A technology and security infrastructure introduced with Microsoft
Vista and Windows Server 2008 operating systems, with a more
relaxed version also present in Windows 7 and Windows Server
2008 R2. It aims to improve the security of Microsoft Windows by
limiting application software to standard user privileges until an
administrator authorizes an increase or elevation. In this way, only
applications trusted by the user may receive administrative
privileges, and malware should be kept from compromising the
operating system. In other words, a user account may have
administrator privileges assigned to it, but applications that the
user runs do not inherit those privileges unless they are approved
beforehand or the user explicitly authorizes it.
To reduce the possibility of lower-privilege applications
communicating with higher-privilege ones, another new
technology, User Interface Privilege Isolation is used in conjunction
with User Account Control to isolate these processes from each
other. One prominent use of this is Internet Explorer 7s "Protected
Mode".

Node Installation
In Windows XP select the network auto negotiation mode by

1. Selecting My network place > Right Click > properties
2. Select the network card to setup > configure >
3. The tab may be different based on the network card brand .
In Windows 7
1. Open the Network and Sharing Center > select change
adapter setting
2. Select the network card to setup > configure
3. The tab may be different base on the network card brand .

Node Installation
In Windows XP select the network auto negotiation mode by

1. Selecting My network place > Right Click > properties
2. Select the network card to setup > configure
In Windows 7
1. Open the Network and Sharing Center > select change
adapter setting
2. Select the network card to setup > configure.
Auto negotiation may slow down the network traffic by adjusting

continuously the Link speed.
Set a fixed Link speed accordingly with the speed of the network
switch.
To ensure the right speed has been selected, verify the transfer
duration of a 100Mb file before and after the change.

Node Installation
Same path as for accessing the network speed, and select the
power management tab.

Node Installation
Host and Lmhost file are located in \windows\system32\drivers\etc
WARNING : The host and lmhost must not have extension. (the default
lmhosts file is lmhosts.sam is a sample file provide as example.)
Hosts file
The hosts file is one of several system facilities to assist in addressing
network nodes in a computer network. It is a common part in an operating
system's Internet Protocol (IP) implementation, and serves the function of
translating human-friendly hostnames into numeric protocol addresses,
called IP addresses, that identify and locate a host in an IP network.
In some operating systems, the hosts file content is used preferentially over
other methods, such as the Domain Name System (DNS), but many
systems implement name service switches (e.g., nsswitch.conf) to provide
customization. Unlike the DNS, the hosts file is under the direct control of
the local computer's administrator.
LMHosts file
The LMHOSTS (LAN Manager Hosts) file is used to enable domain name
resolution under Windows when other methods, e.g. WINS, fail. It is used in
conjunction with workgroups and domains. If you are looking for a simple,
general mechanism for the local specification of IP addresses for specific
hostnames (server names), use the HOSTS file, not the LMHOSTS file.
The file, if it exists, is read as the LMHOSTS setting file. A sample file
(lmhosts.sam) is provided. It contains documentation for manually
configuring the file.

Node Installation
Disabling Windows XP Error Reporting

On Windows XP systems, a number of error messages might show
up if a window closes unexpectedly. To avoid seeing these
messages, disable Windows XP Error Reporting.
To disable Windows XP Error Reporting:
1. Access Control Panel.
2. Double-click the System applet.
3. Click the Advanced tab.
4. Click the Error Reporting button.
5. Click Disable error reporting, then click OK.
6. Click OK to exit the System Properties page.

Node Installation
Changing Paging File Size

To verify/change the paging file size (for a Windows XP client):
1. Click the Control Panel
2. Double-click the System applet.
3. Click the Advanced tab
4. Click the Settings button under Performance.
The performance options dialog box appears.
5. Click the Advanced tab
6. Click the Change button under Virtual memory.

Node Installation
Changing Paging File Size (continued)

The initial and maximum paging file size should be set twice the
physical memory (4096 MB).
If you change the paging file size, click the Set button to record
your changes.
Note: Verify that the paging file size you set is available as free space
in the hard drive accordingly.
If asked if you want to restart the computer, click Yes unless you
want to restart later. Rebooting will set new sizes.
Note: If the initial and maximum sizes are above 4096 MB, you can
decide not to change them accordingly. However, for best
performance (less fragmentation), set the paging file size such that
initial is the same as maximum size.

Node Installation
Setting the Properties of the Event Viewer Logs

1. Access Event Viewer from Start > Programs > Administrative
Tools > Event Viewer.
To change the properties of a each log
1. Right-click on a log and select Properties.
To prevent logs from being overfilled, select an appropriate
maximum log size
2. Select Overwrite events as needed in the General tab.
If the log settings are set to something other than Overwrite
events as needed, there is a potential for a recurrent error
message to completely fill up the event viewer log which could
result in a system failure. To prevent this, all logs in the Event
Viewer should be set to Overwrite events as needed.

Node Installation

Node Installation

Node Installation
Execute the Setup.exe from the media location
Note: You MUST be administrator.

Node Installation
Language option are:

English
Japanese
Chinese
Korean
1. Click install software to start the install Process

Node Installation
Select Enterprise for :

Server installation
Client
LAC/E32

Node Installation

Node Installation
At the Customer Information page, enter the appropriate user

name and organization.
1. Enter your Total Assurance plan number in the Serial Number box.
2. Click Next.

Node Installation

Node Installation
The TNS_ADMIN environmental variable setting adds an

environmental variable to the client that points to a pre-configured
tnsnames.ora file, which is located in a network-accessible share.
This allows large installations to maintain a single tnsnames.ora file
in a share instead of configuring a tnsnames.ora file on each client
and LAC/E32.
1. If you do not intend to use this configuration option, leave No
selected.
2. If you want to enable the TNS_ADMIN variable, select Yes.
3. Enter the network path to the share containing the pre-configured
tnsnames.ora file (for example, \\theservername\thesharename$).
4. Refer to the Installation and Configuration Guide for the
instructions on how to configure a shared tnsnames.ora file.
Note: Not recommended.

Node Installation
Click one of the following buttons at the Installation Type page:

1. To install the files on Drive C or default location, click Typical.
2. To install the files on a different drive, click Custom. (For Custom
Installation, follow the instructions in the Installation and
Configuration Guide or Upgrade and Configuration Guide).

Node Installation
1. Click Next to start the installation.

Node Installation
When installation is finish you have to restart the computer

Node Installation
After the first login in windows you may receive the following
popup.
1. Press Allow access
Automated QA is an external application use for the AVT software
(Automatic Validation Tool).

Node Installation

Node Installation

1. At the Select Protocols page, ensure that TCP is selected, then
click Next.
At the TCP/IP Protocol page, in the Host name field, enter either
the fully resolved host name (computername.domain.dns) or the
TCP/IP address of the server where the Empower database resides.
2. Leave the default port selection at 1521
3. Click Next.
Note: Using the IP address of the server for the Host Name avoids
potential name resolution issues and improves performance.
Note: If you have configured multiple listeners and you want this
client to use one, click Use another port number and enter the
appropriate port number.

Node Installation

1. At the Test page, select Yes > perform a test
2. Click Next.
a. The test is automatically performed and will fail initially with the
ORA-01017 invalid username/password error due to having
the wrong default user name and password (hard coded by
Oracle) which must be changed.
Attention: If the test failed for any error other than ORA-01017,
contact Waters Technical Support.
3. Click Change Login.

Node Installation

1. Enter System as the Username and Empower as the Password,
2. Click OK to perform the test.
Note: Empower is the default password for the Oracle System
account.
The test should succeed. If not, review the entries, make
appropriate changes and test again.
3. Click Next.

Node Installation

1. At the Net Service Name page, enter a name in the Net Service
Name field
2. Click Next.
a. The name that you enter appears in the Database field of the
Empower Login dialog box. In general, this name can be any
alphanumeric string. However, when using a client in
conjunction with a LAC/E32 Acquisition Server, the client and the
LAC/E32 Acquisition Server must use the same net service name.

Node Installation

1. At the Another Net Service name? Page, select No, then click
Next.
2. Click Next at the Net Service Name Configuration Done page.

Node Installation

1. Click Finish to exit the Welcome page of the Oracle Net
Configuration Assistant Wizard.
Note: The file modified using Oracle Net Configuration Assistant,

TNSNAMES.ORA, is very syntax-sensitive! You should only use
Oracle Net Configuration Assistant to modify the net service name
settings. If you modify the TNSNAMES.ORA file manually, then
Oracle Net Configuration Assistant may no longer work.

Node Installation
The TNSNAMES File

The file modified by Oracle Net Configuration Assistant is
tnsnames.ora. It is located in
<drive>:\Empower\Oracle\Oracle10g\network\admin.
Here is a view of the tnsnames.ora file with the entries made by
Oracle Net Configuration Assistant.

Node Installation
The TNSPing Utility

TNSPing is a diagnostic tool that checks TNS connectivity
between the LAC/E32 acquisition server or client to the server
using the entries in the TNSNAMES.ora file. This utility is the
same as testing the connection using Oracle Net Configuration
Assistant.
To use this utility, when using an Enterprise Client or LAC/E32
Acquisition Server
1. Go to the command prompt and enter the following:
2. C:\> tnsping databaseservicename

Node Installation

Node Installation
The Verify files contain different section :

Header with machine and install information
Icop installed
Database information and options installed.
All the empower file verification.
A Summary part with signature part.
Register Printer
Register printer - allows the printer to be registered so that it
can be used by the WatersService during process and printing
automation (batch processing/printing, run and report & run
and process, AQT & SQT process)

Node Installation

Install Automation
Rev. 30011 Chapter4: Page 1 of 14

Install Automation

Install Automation

Install Automation
The installation automation is the capability from a central location

to install automatically application on different computer.
The push installation allow the install automation for Client,
acquisition Client and LAC/E32 as well as install automation for
ICOP.
Installation can be performed simultaneously on multiple machine

Install Automation

Install Automation

Install Automation

Install Automation

Install Automation

Install Automation

Install Automation
PsExec executes a program on a remote system, where remotely executed console

applications execute interactively.
Usage: psexec [\\computer[,computer2[,...] | @file]][-u user [-p psswd][-n s][-l

][-s|-e][-x][-i [session]][-c [-f|-v]][-w directory][-d][-<priority>][-a n,n,...
] cmd [arguments]
-a Separate processors on which the application can run with
commas where 1 is the lowest numbered CPU. For example,
to run the application on CPU 2 and CPU 4, enter:
"-a 2,4"
-c Copy the specified program to the remote system for
execution. If you omit this option the application
must be in the system path on the remote system.
-d Don't wait for process to terminate (non-interactive).
-e Does not load the specified account's profile.
-f Copy the specified program even if the file already
exists on the remote system.
-i Run the program so that it interacts with the desktop of the
specified session on the remote system. If no session is
specified the process runs in the console session.
-h If the target system is Vista or higher, has the process
run with the account's elevated token, if available.
-l Run process as limited user (strips the Administrators group
and allows only privileges assigned to the Users group).
On Windows Vista the process runs with Low Integrity.
-n Specifies timeout in seconds connecting to remote computers.
-p Specifies optional password for user name. If you omit this
you will be prompted to enter a hidden password.
-s Run the remote process in the System account.
-u Specifies optional user name for login to remote
computer.
-v Copy the specified file only if it has a higher version number
or is newer on than the one on the remote system.
-w Set the working directory of the process (relative to
remote computer).
-x Display the UI on the Winlogon secure desktop (local system
only).
-priority Specifies -low, -belownormal, -abovenormal, -high or
-realtime to run the process at a different priority. Use
-background to run at low memory and I/O priority on Vista.
computer Direct PsExec to run the application on the remote
computer or computers specified. If you omit the computer
name PsExec runs the application on the local system,
and if you specify a wildcard (\\*), PsExec runs the
command on all computers in the current domain.
@file PsExec will execute the command on each of the computers listed
in the file.
program Name of application to execute.
arguments Arguments to pass (note that file paths must be
absolute paths on the target system).
You can enclose applications that have spaces in their name with
quotation marks e.g. psexec \\marklap "c:\long name app.exe".
Input is only passed to the remote system when you press the enter
key, and typing Ctrl-C terminates the remote process.
If you omit a user name the process will run in the context of your
account on the remote system, but will not have access to network
resources (because it is impersonating). Specify a valid user name
in the Domain\User syntax if the remote process requires access
to network resources or to run in a different account. Note that
the password is transmitted in clear text to the remote system.
Error codes returned by PsExec are specific to the applications you

execute, not PsExec.

Install Automation

Install Automation

Install Automation

Administrative and
Management Tools
Chapter 5
Administrative and
Management Tools
Overview of Empower Pro Window
Configuration Manager Administration Tools
Empower System Policies
Empower System Audit Trail

Administrative and
Management Tools
This Chapter Provides instruction these topics:
Login to Empower
Message Center
Help Menu
Configuration Manager
System policies
System monitor
Default Strings
Audit Trail
Empower software has three interfaces to access the

application:
Interfaces in QuickStart is a single-window access point for data

Empower collection, processing, and reporting. Use a wizard to
set up methods and run assays without confusion. You
can navigate the entire Empower environment from
one screen, including instrument control, a real-time
view of plotted data, and a work area to look at raw
data.
Pro is for system administrators or power CDS users
who need total control and compartmental access to all
Empower Software functions. You can configure for
regulatory compliance, customize application security
to define a complete audit trail for all software and
user activity, and use electronic records and
signatures.
Open Access gives the walk-up user who may not
be a trained chromatographer the ability to simply
select a method and number of samples, and start a
run with the click of a mouse. Results are automatically
sent to a printer or a specified email address.
Empower has a variety of administration management

features and tools for customizing how the software is used
in individualized environments. This chapter focuses on these
management features and tools to assist in the configuration
and administration of Empower.

Administrative and
Management Tools
Login to:
Empower
Software
Double click
the Icon

Administrative and
Management Tools
The Login Dialog
Type in User
Name and
Password
Select
Advanced>>
button
To use Empower, you must have a user name and password.

User name and password are not case sensitive. A system
administrator creates each user account.
On a client computer in a Workgroup or Enterprise

configuration, there is an additional drop down list to select
the database you want to access. Only the local database is
available on Empower Personal.
Note: System policies can be set so that the Global Default

User Interface is Quickstart, Pro or Open Access.
Note: The first time that you login to Empower the password
is the same as the user name, unless the system
administrator has assigned a different password.

Administrative and
Management Tools
Change your password at login (if required)
Type new
password (if
prompted)
Choose OK, and In the Select User Type and Interface Dialog box:
OK again and 1. Select the appropriate User Type from the drop down
the main Pro menu
window will 2. Select the appropriate interface from the Allowed
open. User Interfaces radio buttons.

Administrative and
Management Tools
You can assign individual users to more than one user type,
as some users often perform more than one job function. If,
for example, the Empower administrator is also a chemist,
you can assign them two user types: Administrator and
Chemist.
Users assigned to more than one user type can sign into the
system only as one user type at a time and perform only
those functions associated with that user type.
A users user type appears in the audit trail, message center
and in the title bar (at the top of the window).
Message Center Message Center window

Icon opens in
tray Message Center opens and minimizes to the Empower icon in
the Windows System tray when a user logs into Empower.
Double click the
Empower
Message
Center icon to
maximize
Message Center
window.
Message Center stores and displays the following types of

messages:
Informational, Warning and Error.

Administrative and
Management Tools
Informational - This is notification of an action within the

Empower system, for example, when a service pack is
installed.
Warning - This indicates that a system error may be
occurring or is about to occur. You can take corrective
action in response to a warning message.
Error - This indicates a detected failure, such as an
instrument setup failure or incorrect password used.
Informational and Warning messages are listed in normal,

black font. Error messages are listed in bold, red, italicized
font.
Empower sorts these messages into five categories that you

can access by selecting a tab at the bottom of the table: All,
Acquisition, Security, Processing and Email (on
Workgroup or Enterprise systems only).
When an Error message is generated in the Empower

System, the Empower Message Center icon in the Windows
System tray turns red alerting the user that the system has
encountered an error.
Message Center Table Save to file

Message center
Can be saved to From the File menu, the Message Center table can be saved
a text file as a text file that will be automatically named as Message
Center with current date. The table can also be output to a
printer for hard copy format.

Administrative and
Management Tools
Select File >

Save As File or
Print Table to
save Message
Center table as
text file
or print.
Select View > Message Center Properties allows configuration of the

Properties to Message Center window.
access Message
Center
Properties.
Note: Message Center messages are global for Enterprise

and Workgroup environments. Users can see their related
Empower system messages and Administrators can see all
user messages.
In addition, any user type can be given the privilege to view

all messages.

Administrative and
Management Tools
Set the number Message Center Properties is comprised of 3 tabs that allow
of messages to configuration of global settings for Message Center.
display in the
Message Center The General tab provides the ability to set the number of
table by setting messages displayed in the Message Center table. The
Number of messages can be scrolled through by using the Next Group
Messages to and Previous Group to Display buttons.
display.
Click Next
Group or
Previous
Group to
Display buttons
to scroll through
messages.
Manually purge
a category by The Purge tab allows purging of selected Message Center
selecting and categories by selecting the appropriate category and using
clicking Purge the Purge Selected Message Logs NOW button. The Auto-
Selected Purge feature allows the ability to automatically purge any
Message Logs message older than the number of days specified.
NOW.
To automatically
purge all
categories,
select Auto-
Purge
Messages
Older Than and
specify the
number of
Days.

Administrative and
Management Tools
The Passwords tab allows setting a password to access

Message Center Properties.
Note: Setting a Message Center Properties password is

important to allow access to only users authorized to perform
the functions in Message Center Properties.
Access to the Message Center Properties is not restricted

based on user type, only by access to the password set for
the Properties window.
The Message Center Properties password is not controlled by

the Accounts and Passwords policies set for user accounts in
Set Message System Policies.
Center
Properties
password by
selecting
Password
Protect
Properties,
then enter
Password and
Confirm
Password.

Administrative and
Management Tools
Empower Pro Window
Six Application
buttons
Run samples
Browse Project
and Configure
system most
used
Login session information Displays the name of the user

currently logged in and the source of the Empower
Six application buttons Access primary applications in

Empower software:
Run Samples - Acquire data

Browse Project - Opens the Project window
Configure system - Manage Empower system
administrative functions
Process data Generate results using batch process
Review data - Review or Preview (for printing) data
Print data Print reports

Administrative and
Management Tools
Overview of the Pro Interface
Login and
Logout buttons
are in the main
Pro window
Login and Logout buttons Log in to and log out of an

Empower session. If multiple logins are specified as part of
your Empower system policies, the Login button remains
enabled, allowing multiple users to log in as the current user
for multiple Empower sessions. The same user can log in to
another interface
About Empower
Select About to
view database
information
About Pro
displays your
Total
Assurance
Plan ID#
Installed
Service Packs,
and the
Installed
Options

Administrative and
Management Tools
This information Waters: 1-800-252-4752

will be helpful www.waters.com
when calling
Waters for
support.
Help: Empower Online Information System
Click Help
In Empower you can utilize Help from the menu bar. To

access Window level help in other Empower windows select
F1 on your keyboard.
Help button Opens the Empower Pro Window Help. You

can access and use the Empower Help system in several
ways:
Empower Context-Sensitive Help - Accessed by clicking

the tool in the title bar of a dialog box, property tab, or main
window. When activated, a question mark attaches to the
cursor, and when you click the item of interest, a brief
description of that item and its function appears.

Administrative and
Management Tools
Empower Window-Level Help - Accessed through the

Help menu where there is a menu bar (select the Empower
Help on option) or by pressing the F1 key in an application
window. The Help files display information about the
currently active window.
Empower Help Topics - Accessed by selecting Empower

Help Topics from the Help menu options in the menu bar.
This activates the Empower Help Topics Browser displaying
Contents, Search, and Glossary tabs. The Empower Help
Topics Browser allows you to display and navigate through
the Help topics. It also provides search and print
capabilities.
Help: Home
Home from the

Menu bar
provides an
interactive
selection.
You can interactively click on an item to get more

information, including Empower Online Information
System to get more details on searching, printing, copying,
etc.

Administrative and
Management Tools
Help: Searching
When
searching for a
topic, put it in
double quotation
marks.
example:
valley to
valley
Select List
Topics to find
all related items.

Administrative and
Management Tools
Help: Glossary
The Glossary will provide you a list of not only Empower

terms but also general chromatography terms.
Select the
Glossary tab,
choose the
Term to view its
corresponding
Definition.

Administrative and
Management Tools
Configuration Manager
The Configuration Manager window provides access to

administrative features and functions within Empower. The
Configuration Manager window allows configuration of
System Policies, Empower Nodes and Systems, and is used
to perform Project management, User management, System
Audit Trail auditing and other functions.
Click Configure
System

Administrative and
Management Tools
Configuration
Manager
Window
Components of the Configuration Manager include:
Menu bar - Displays File, Edit, View, Tools and Help

menu commands.
Toolbar - Displays tools that provide shortcuts to some
of the commonly used menu commands.
The Tree pane displays the configuration tree.
The View table displays information about the item
selected in the tree pane.
Note: Any action that can be performed in a particular

window can be easily accessed by right clicking in the
window to show the functions menu available for that
particular window.

Administrative and
Management Tools
System Monitor
System Monitor provides an overview of high level

information about the Empower system. System objects such
as projects, users and systems can be monitored to make
informed decisions about the status of the system at any
time.
Select View >

System
Monitor.
The top bar of the System Monitor window shows certain

important facts about your system:
Number of User Licenses Used / Available

Number of System Licenses Used / Available
Number of Agilent LC Licenses Used / Available
Number of Agilent GC Licenses Used / Available
Number of Computers Connected

Administrative and
Management Tools
There are four different tables available:

Users: Displays the users, computers, accessed
projects, and systems open in Run Samples.
Systems: Displays the acquisitions systems by
system name, the computer running the system, the
user for whom the system is running, the project into
which each system is acquiring data, the status, and
the other users connected to the same system.
Projects: Displays projects and their users, systems
acquiring data, the amount of free tablespace, and the
tablespace quota.
Processing: Displays system usage by computer,
users, active projects, and server status.
The System Monitor view table can be customized in the

Options Dialog box. Options you can set include:
Show All Objects: Displays a row for each known
object (user, system or project) in the System Monitor
table, whether or not the objects are active. Default:
Disabled.
Auto Update: Updates the System Monitor display
according to a user-specified time interval. If Auto
Update is disabled (system default), the System
Monitor is set to a value of 30 seconds.
Select View >

Options
Select Show All

Objects and
Auto Update
every X
seconds.
Click OK.

Administrative and
Management Tools
Database Properties
The Database Properties allows Administrators to change the

internal database password that Empower software uses to
login to the Oracle Database.
Select View >

Database
Properties.
Click to view
Change
Database
Password
Recommend:
DO NOT
CHANGE
Password
Waters strongly suggests that you DO NOT CHANGE THIS;

however, if your company policy demands that the password
needs to be changed, you need to supply the current
password. Only certain Waters personnel can provide this
password. Only these Waters personnel fixing your database
would know or need to use this account/password.

Administrative and
Management Tools
System Policies
System policies are global system settings that control the

behavior of several aspects of Empower software. For
example, you can enforce the periodic expiration of user
account passwords, limit the number of login attempts,
prohibit multiple logins, configure default full audit trail
settings, set signoff policies for results, and so on.
You can also use system policies to set up Empower

software for use with GXPs, electronic signatures and
electronic records.
Each tab of the system policies is described below.
Note: To modify system policies, you must log in to

Empower software using an account with the Alter System
Policies privilege.
Select View >

System
Policies.

Administrative and
Management Tools
User Account Policies
User accounts
tab
The User Account Policies tab defines configuration of the

Empower System within the following categories:
Accounts and Passwords

LDAP Domain Manager
Login Window Policies
Click F1 for Note: The help menu has extensive details for each policy
details of each
policy

Administrative and
Management Tools
LDAP Domain Manager:
When LDAP authentication is enabled, you can define

multiple domains.
Note: The Empower user who activates LDAP Authentication
To enable, must have the property Always local Login. Any existing
select LDAP local Empower users who dont have that property are
Authentication disabled when LDAP authentication is enabled.
and click New
Enter Domain
information in
the
Authentication
policies window

Administrative and
Management Tools
To edit domain
information,
Select LDAP
Domain
Manager and
click Edit.
To view domain
information,
select in LDAP
Domain Manager Tip: For information on domains, click Help on the
and click View. Authentication Policies page of the System Policies dialog
box.
Login Window policies:
Click F1 for
details of each
policy

Administrative and
Management Tools
New Project Policies
New Projects
tab
Define global
Project
Policies
The New Project Policies tab defines the global setting for
new project creation. Settings can be required for all new
projects or allowed to be changed by the project creator.
See Help menu for detailed descriptions of each policy.
Project Object indicates what category of entries will be

affected by this policy
Comment determines the type comment required, options
are:
Silent = no comments
Unrestricted provides a dialog box where users can
enter any comment, does require at least something is
entered
Restricted requires users to choose from a list of
predefined comments
Note: predefined list is created under Default Strings

Click F1 for
details of each
Exception: If you select Restricted comments and no
policy
default strings exist, users can enter any comment.

Administrative and
Management Tools
Confirm Identity when checked, password must be

reentered to complete task
System Audit Trail Policies
System Audit
Trail Policies tab
defines audit
trail comment
configuration for
the listed
categories
These categories affect the global or system audit trail not

the project audit trail.
System Object indicates what category of entries will be

affected by this policy
Comments types can be assigned as with Projects (see

above)
Confirm Identity same effect as project audit trail (see

above)

Administrative and
Management Tools
Data Processing Policies
Data
Processing tab
Data Processing Policies:
Controls the way Empower processes data by globally

allowing alternate ways of calculating data. See the help
menu for details of each policy.
Data Processing Technique:

Click F1 for Empower offers two data processing techniques, Traditional
details of each and ApexTrack integration. Each technique uses a unique
policy integration algorithm and, therefore, processes data
differently.
Traditional integration is always available, whereas, to use

ApexTrack, it must be enabled in three places (in this order):
the Empower database, the project, and the processing
method.

Administrative and
Management Tools
Other Policies
Other tab
The System Audit Trail Other Policies tab defines

configuration of the Empower System within the following
categories:
Application time out

Disallow use of annotation tools in
Preview/publisher
Date and time format
Number of default rows in tables
Click F1 for
details of each See the help menu for details of each policy.
policy

Administrative and
Management Tools
Result Sign Off Policies
Result Sign off

tab
The Result Sign Off Policies tab defines configuration of the

Empower System within the following categories:
Signoff of electronic reports
When using electronic signatures to sign off data, these

policies must be considered.
Click F1 for
details of each See the help menu for details of each policy.
policy

Administrative and
Management Tools
Email Policies
Set up Email
Policies to
determine which
message
center entries
to forward to
one or more
email account(s)
The Email Policies tab defines configuration of the Empower

System within the following categories:
Email Policies
By configuring email system policies, you determine which

messages from the Message Center are sent to an email
account. The email center facilitates troubleshooting because
it allows the recipient to quickly respond to an Empower
error without having to check the Message Center
throughout the day.

Administrative and
Management Tools
Requirements:
Empower Enterprise/Workgroup installed and you must

specify which Empower database will send the email
messages
Waters Email Center configured on either a client
computer or a server
Alter System Policies privilege
To configure email policies for your laboratory, you must

specify the category and type of error message that you
want to email, and configure the outgoing mail server
settings.
To configure the email policies for your database:
1. On the Email Policies tab, click Category in the first

row, and then select one of the following categories.
Select this category For these messages

Security Unsuccessful logon attempts, project
integrity errors, a user trying to log on
with an account that does not exist, and
so on.
Instrument Instrument failures, such as, leaks over
pressure, and other instrument issues.
Processing Failure to acquire data and/or process

data, such as, no results, processing
method errors, and so on.
General Changes to system objects that appear in
the system audit trail, such as project
version updates, changes in the project
directory, and so on.

Administrative and
Management Tools
2. For each category, specify the type of message that

the designated person should receive.
Select this type For these messages

Informational Database updates to projects, changes to
project directory, and so on.
Warning A somewhat serious error, but not a
security risk, such as instrument failure,
user aborting a run, and so on.
Error A serious error, such as unsuccessful
login attempts, project integrity errors,
and so on.
Restriction: For each row in the Email Policies table, you can
only choose one message type for each category (such as
Security and Error), but you can specify multiple email
addresses for each type and category. To specify multiple
message types for a category, you must use multiple rows.
3. For each category and message type, type the email

addresses of the person(s) that you want to receive an
email. Use a semicolon (;) and a space to separate
email addresses.
Example: John_Smith@waters.com;
Mark_Jones@waters.com
4. Specify the outgoing mail server.
Tip: This is the server that sends outgoing email for your
company. If you are not sure, check with your IT
department. If you change one of the mail server information
settings, such as the outgoing mail server or the default
email name, you must stop and restart Waters Email
Service.
On the desktop of the Email client, right-click My Computer,

and then select Manage. In the Computer Management
dialog box, click Services and Applications > Services,
right-click Waters Email Service, and then select Restart.
In the Default From Name field, specify the name of the
email account that will appear when the designated person
receives an email message.

Administrative and
Management Tools
Restriction: Do not enter any spaces or special characters.
5. In the Server Port Number field, enter the port number

for the SMTP server.
6. If your mail server requires authentication, select the
authentication check box, and then enter an account
name and password.
7. Click OK.
Result: If an audit trail is required, supply a comment and/or

password, and then click OK.
Note: Once changes are made to system policies, You must

log out and then log back in to Empower in order for the
changes to the System Policies to take effect.
Default Strings
Add custom
Default Strings A default string is text, up to 249 alphanumeric characters,
that can be created in advance, and then selected when
prompted to provide a reason for modifying Empower
objects, such as, methods, projects, users, and so on. A set
of predefined comments can be created for each category to
describe why a change was made to an object in Empower.
Comments are often required for audit trail purposes.
Default strings can save time by eliminating the need to type

recurring comments because once they are created; they can
be selected from a list. It also ensures that comments
recorded within audit trail records are consistent.
When System Administrators set up system policies for a

laboratory, they define whether comments are required to
describe reasons for changes to objects in Empower.
The creators of projects determine for each project whether

users must enter comments to describe changes to samples,
methods, or when results are created, modified, or deleted.
If a comment is required to describe a change to a system

or project object, a System Administrator or the person who
created the object can decide that the user must enter

Administrative and
Management Tools
"Restricted" comments. This means that a comment must be

chosen from a predefined list of comments (default strings).
If a default comment is required and none exist for a

category, free form comments must be entered until a
default comment is created.
Default Strings can be accessed through the Configuration

Manager window.
Select View >

Default
Strings.
Default strings can be added, modified or deleted from the

Default Strings dialog box by selecting the Category.

Administrative and
Management Tools
Select
Category.
Click Add
String,
Modify String
or Delete
String.
Click OK.
System Audit Trail
Empower automatically generates a secure and time-

stamped audit trail that tracks any change to system-level
activities.
The View System Audit Trail privilege allows viewing these

objects in the System Audit Trail.
The System Audit Trail can be accessed in the Configuration

Manager window.
Select System
Audit Trail in
Tree Pane.

Administrative and
Management Tools
The System Audit Trail keeps a record of actions performed

at the system level, such as successful/unsuccessful logon
attempts, creation of new projects, deletion of
chromatographic systems, and so on.
This audit trail enables retention of secure, time-and-date

stamped records of changes made to these objects.
Because this feature cannot be turned off, the System Audit

Trail can become quite large over time. These records can be
backed up as well as archived and removed to review them
at a later date.
Backup System Audit Trail
The System Audit Trail can be backed up as a binary or text

file from the Configuration Manager window.
Select Records
> System
Audit Trail >
Archive >
Binary or Text.
Note: Binary files are more secure than text files. Text files
can be easily modified and resaved with no record that the
file was altered. Be sure to save any System Audit Trail
backup in a secure location.
Text files are readable outside Empower; binary files must be

brought into the offline audit trail to be viewed.
Archive System Audit Trail

Administrative and
Management Tools
The System Audit Trail can be permanently archived as a

binary or text file with subsequent removal of audit trail
records from the System Audit Trail.
The System Audit Trail can be archived from the

Configuration Manager window.
Select Records
> System
Audit Trail >
Archive and
Remove
Enter
Administrator
1 and
Password 1
and
Administrator
2 and
Password 2.
Click OK.

Administrative and
Management Tools
Select Binary
File or Text
File.
Enter date in
Remove all
records dated
before box.
Click OK.
Select location
to save
archived
messages.
Archived
messages saved
with
System Audit
with Date and
Time as file All System Audit Trail messages before the date listed will be
name. archived to the file type selected and all corresponding
messages will be purged from the System Audit Trail.
Click Save.
Note: Only messages archived as binary files can be
imported back into the Empower system via the Offline
System Audit Trail.
Dialog box with

warning
appears, click
OK

Administrative and
Management Tools
Offline System Audit Trail
The Offline System Audit Trail can be used to restore

archived System Audit Trail messages. Only messages
archived as binary files can be restored in the Offline System
Audit Trail.
The Offline System Audit Trail can be accessed in the

Select Offline
System Audit
Trail in Tree
Pane.

Administrative and
Management Tools
Restoring Offline System Audit Trail
Select Records
> Offline
System Audit
Trail >
Restore
Select location
of Archive and
click Open.

Administrative and
Management Tools
View archived
messages in
Offline System
Audit Trail
table.
Clear Offline System Audit Trail
Select Records
> Offline
System Audit
Trail > Clear

Administrative and
Management Tools
Click Yes or No.
All messages
cleared from
Offline System
Audit Trail table.
Saved binary file

is still available
to import again
to Offline Audit
trail table at any
point.

Administrative and
Management Tools
Summary
Empower has 3 different hardware configurations: Personal,

Workgroup and Enterprise.
The Empower Pro window allows access to the following: Login/Logout,

About system information, Empower help, and 6 application buttons
(Run Samples, Browse Project, Configure System, Process Data,
Review Data and Print Data).
Message Center contains informational, warning and error messages

which provide system information during use of the software.
System Policies provide the ability to configure the global settings of

Empower software.
The System Audit Trail tracks information about system level changes
to the Empower system.
Review Questions
1. How many hardware configurations of Empower are there? What is the

difference between the different hardware configurations?
2. How many user interfaces are there in the Empower software?
3. Where do you select the user type and interface you want to use?
4. Which Empower window is used to access information about the Empower

system? How is this window accessed?
5. Which Empower window is used to perform administrative functions?
6. What types of file formats can be used to backup/archive the Empower

System Audit Trail? What is the difference between the different file
formats?

Configuring Empower 3
Nodes with Instruments



Supported Empower Configurations

Up to 4 instruments can be connected to one acquisition
server, with some limitations.
Current systems connect though Ethernet cards using a
direct connection from the instrument to the acquisition
server
Each instrument is assigned an IP address
Legacy systems can be connected through other interfaces:
busLAC/E32 (using IEEE)
8-port Equinox serial card
COM port.
Each of these have specific requirements for installation,
refer to system documentation.
Note: More than one interface type can be run

simultaneously.

A Chromatographic System
This example shows a typical LC chromatographic system. An LC
chromatographic system generally consists of a pump, an
autosampler and a detector.
If you are using Waters instrumentation, these components may
be connected to the acquisition server by IEEE cables or thru
Ethernet.
When using IEEE, the instruments are daisy-chained together
and connected to the IEEE port on the busLAC/E card in order
to allow communication between the computer and the
instrumentation.
When using Ethernet, instruments are connected to an
Ethernet switch using the RJ45 connection. This allows
communication from the computer to the switch then to the
instrumentation.
Note: Fourteen is the maximum number of total devices that you

can attach to an IEEE socket. To connect these devices, you can
use a maximum of twenty meters cable length.


To connect using a NIC (labeled Instrument LAN), you have

to set-up the Waters DHCP Service through the Acquisition
Server Properties.
Check the latest service packs for newest released
instruments available for connectivity

Supported IEEE 488 Devices via the BusLAC/E card
IEEE connections require a proprietary computer card (purchase from

Waters) in the acquisition server.
Legacy LAC/E boxes come with this card.
Each instrument connected to the acquisition server in the IEEE chain

is assigned a unique IEEE address (from 2 to 29). You can configure
these addresses through the front keypad on each instrument except
for the Waters 2996 PDA Detectors and the Waters Pump Control
Module (PCM). These devices have their addresses configured
through a series of dip switches on the back of the instrument.
Each instrument connected to the same acquisition server must have

a unique IEEE address to ensure proper communication.
Typical IEEE-488 Waters instruments are:

Alliance systems: 2695, 2795, 2695D
Detectors: 2487, 2996, 2410, 2414
Note: Refer to the Empower Software System Installation and

Configuration Guide for the complete list of supported systems and
their minimum firmware requirements.

IEEE Rules
The maximum total IEEE cable length is 20 meters (refer to table).
The maximum number of IEEE devices is 15 (fourteen instruments plus
the busLAC/E card).
The maximum length between IEEE devices is 4 meters (minimum is 1
meter).
Identify all attached IEEE devices with unique addresses (from 2
through 29). This is configured either through the front keypad of most
equipment or through a series of DIP switches on the back of the
instrument depending on the instrument model.
Make sure that the devices firmware meets the minimum firmware
required.
Keep data rates for devices within the specified data rates allowed
depending on the type of systems connected.
Power up all of the instruments and verify that they have completed
and passed their calibration and diagnostic routines.
Note: Refer to the Empower 3 Software System Installation and
Configuration Guide and the Empower 3 System Release Notes for the
system configurations supported.

Connection Through the busLAC/E Card Serial Port

In addition to the IEEE port, the busLAC/E card has a serial
port. The I/O Distribution box (called the harmonica) is
connected to the serial port of the busLAC/E card. The
harmonica has four ports, so that it is possible to connect
four devices. The following are examples of devices that you
can connect to the harmonica:
A busSAT/IN module is an analog to digital converter used to
acquire data from instruments that are not IEEE or ethernet
controlled.
A SAT/IN connected to the busLAC/E card through the
harmonica allows you to connect up to two chromatographic
systems (acquire data on two separate channels) on two
different time bases.
Devices attached to the harmonica must also have addresses
so that Empower can differentiate among them. The
harmonica addresses are assigned depending on the port to
which the instrument is connected: Port 1 - 1, 2; Port 2 - 3,
4; Port 3 - 5, 6; and Port 4 - 7, 8.
To avoid potential conflicts between harmonica and IEEE
addresses, do not use addresses 1 through 8 if you are
using both a harmonica and IEEE control.

Supported Serial Devices via the Equinox Card

The supported serial instruments connected through the
Equinox card are:
2475 Multi Fluorescence Detector (however, the Waters 2475
is better set-up using Ethernet connection)
Waters 2465 Electrochemical Detector
busSAT/IN Module
Agilent 5890S (Series II - attached to serial card), 6850,
6890, 6890+ and 6890N Gas Chromatographs
Agilent 7673S (attached to serial card), Agilent G1512A
AutoSampler Controller
Agilent 7694 Headspace Autosampler (G1290B),
Agilent 1100 Series Control Modules: isocratic, quaternary
and binary pump, autosampler, VWD, MWD(A), MWD(B),
RID

New Empower Nodes

New Empower Nodes automatically appear in the list of
Nodes in the Configuration Manager after the first time
Empower has been opened on that Node.
Different examples of Empower Nodes as shown above:
Empower servers such as:

Backup server (Empower Node Type: Server)
Clients or Acquisition servers such as:
Cetraining (Empower Node Type: Empower)
LAC/Es such as:
Waters-177 (Empower Node Type: LAC/E32)

Accessing the Properties of an Empower Node

Access the Node properties in order to:
Verify the connection of the acquisition server to the
instruments
Verify/change the information about the instruments
connected to the acquisition server
Verify/change the configuration of the serial ports
Verify/change the way different users access the server
To access the properties of the acquisition server:

1. Click Configure System in the Empower Login Window
2. Select Nodes on the tree on the left-hand side of the
window
3. Right-click the name of the Empower Node in the table
4. Select Properties.
Note: All connections to instruments, except for IEEE, must

be set in the acquisition server properties before you can
access chromatographic systems in Empower.

Empower Node Properties

The Empower Nodes Properties dialog box opens. The five
tabs are:
1. General
2. Instruments
3. Serial Ports
4. Configure DHCP
5. Access.
The General Tab
Use this tab to view the information about the Empower
node:
Verify that the Empower Node Name and Type are
correct.
Check BusLAC/E status and type (if applicable)
Check Serial Device status (if applicable)
Verify/change time zone for this node
Add comments

Empower Node Properties (continued)

The Instruments Tab
Use this tab to view details about the instruments connected to the selected
Empower Node. Empower software does not automatically fill in the values
in all columns. The columns are:
Type: Indicates the instrument type (i.e. 2695, Agilent 1100, and so
on).
Address: Indicates the IEEE address or address assigned to
instruments.
OK?: Indicates if the instrument is powered on and working properly.
Serial Number: Displays the instrument serial number. You enter
these values. There are some exceptions, for which Empower
automatically reads the serial number. (generally for newer systems)
Last Serviced: Indicates the last service date of the instrument, this is
manually entered.
Next Service Due: Indicates the notification date for the next service
message. You can still use the chromatographic system when you reach
or pass the service date providing that you have the Warn on Service
Limit privilege. This value is also manually entered.
PROM Version: Indicates the instrument PROM (firmware) version.
Comments: Displays any comments that are manually entered (for
example, located in QC lab).
Details: Displays information specific to an instrument (for example,
heater/cooler option installed).


The Serial Ports Tab
Use this tab to configure the serial ports. Click the
appropriate drop-down list and then select the instrument
you want to add.
The different ports are:
BusLAC/E Serial Ports: The instruments available to
be configured on these ports are: SAT/IN module
connected to a non-IEEE detector or injector, Agilent
5890 and Agilent 7673.
PC COM Serial Ports: Empower software supports the
use of one PC COM port. The instruments available to be
configured on a COM port are: SAT/IN 2 which can be
configured with one channel at a time and a 474
Fluorescence Detector.
8 Port Serial Card: The instruments that can be
configured on this card (also known as an Equinox card)
are: None, Agilent 6890, Agilent 5890S, Agilent 7673S,
SAT/IN 2, or a 474 Fluorescence Detector. Default:
None.
Note: these 8 ports are only available if an Equinox card is

installed.


The DHCP Service Tab
Use this tab to configure DHCP on Empower Nodes. Click
the Configure DHCP button to start setting up IP Addresses
for certain Ethernet based instruments based on their MAC
addresses.

Configuring Network Connections and IP Addresses

The Configuration Wizard sets an IP address for an instrument network card.
To set the IP address for an instrument network card:
1. Select Server > Configuration Wizard.
2. Select an instrument network card and click Next.
3. Click Default (192.168.0.1), then click Next.
4. Click Finish.
5. Click Yes. The acquisition server reboots. If the IP address for an acquisition
server is being set from a remote client, the acquisition server properties
window must be closed. Click OK on the message that appears.
Tip: If you click No in the Waters DHCP Server Configuration dialog box, a message
appears to remind you to reboot the computer.
After you set the IP address and the acquisition server has rebooted, restart the
Configuration wizard to verify the IP address information.
Tip: The second IP address is for Waters mass detectors and is automatically
assigned, regardless of whether or not the acquisition server controls a Waters
mass detector.
6. Click Cancel to exit the wizard.
Note: Please use Help for more information


The Access Tab
Use this tab to control user access to the selected Empower Node and the
Chromatographic Systems connected to it.
If you are on a client/server configuration, you must click in the Share
Instruments with Other Network User check box. This gives other users
on the network the ability to use this acquisition server and its associated
systems.
Allowed Access:
Owner Only-Specifies that only the owner of the Empower Node and
all users with administrator privileges can access the selected
acquisition server.
Owner and Group(s)-Specifies that only the owner of the Empower
Node, all members of the groups as specified in the Allow Access to
Groups list, and Administrators can access the selected acquisition
server. Group access allows a user to access and modify an acquisition
server.
Owner, Group and World-Specifies that all users in the database
can access and modify the selected acquisition server.
Owner: Specifies the owner of the acquisition server. This field is
enabled if you are the current owner of the selected acquisition server or
if you have Administrator privileges.
Password Protect Access
Password Required-Specifies that a user must have a password to
access the Acquisition Server from a different Empower database.
Click OK to apply any changes.

Empower Node Properties - Server

To view the Empower Node Properties of a server,
1. Select the server in the Empower Node page of
Configuration Manager.
2. Right-click on the server
3. Select Properties.
The Empower Node Properties page appears with two tabs,
General and Access tabs.
The General tab shows the Empower Node Name, Type
and Time Zone.
The Access tab contains the properties to specify who is
allowed access to the server.

Creating a New Chromatographic System

To create a new Chromatographic System
1. Click on the New System tool in Configuration Manager.
2. You can also select a right-click if Systems is viewed on the tree,
or use the Edit drop-down menu.

Creating a New Chromatographic System (continued)

The new Chromatographic System Wizard dialog box in now
available.
1. Select Create New System as the System Type to start the wizard.


In the New Chromatographic System Wizard Select Server page,
1. Select the Empower Node that is connected to the instruments that
is needed to be connected to create the chromatographic system.
2. Click Next.


In the New Chromatographic System Wizard System
Selection page
1. Select the systems with its appropriate address number
from the left tree and bring over to the right side under the
New Systems tree. Once all appropriate components are
assigned to be part of this New System,
2. Click Next.


In the New Chromatographic System Wizard Access Control page,
select the properties to control user access to the new system.
If you are on a client/server configuration, you must click in the Share
Instruments with Other Network User check box. This gives
other users on the network the ability to use this system.
Allowed Access:
Owner Only-Specifies that only the owner of the
Chromatographic System and all users with administrator
privileges can access the selected Chromatographic System.
Owner and Group(s)-Specifies that only the owner of the
Chromatographic System, all members of the groups as specified
in the Allow Access to Groups list, and Administrators can access
the selected Chromatographic System. Group access allows a
user to access and modify a Chromatographic System.
Owner, Group and World-Specifies that all users in the
database can access and modify the selected Chromatographic
System.
Owner: Specifies the owner of the Chromatographic System. This
field is enabled if you are the current owner of the selected
Chromatographic System or if you have Administrator privileges.
Password Protect Access
Password Required-Specifies that a user must have a
password to access the Chromatographic System from a
different Empower database.
Select appropriately and click Next.


In the New Chromatographic System Wizard Name
Selection page, identify the new System Name.
Check the Online box if the system is to be available for
immediate use.
Enter System Comments or select from the available Default
Comments drop-down menu. Once all appropriate entries
are specified,
1. Click Finish.
A message acknowledges the system to be Online if enabled.


The new system is now shown in the Systems tree of

Chromatographic System Properties

Each system has properties, where the settings chosen when
the system was added can be modified.
To access system properties, highlight the system, right click
and choose System Properties

General tab
In this tab you can change the system comments
On line or off line can also be changed from this window, to
take the system off line, uncheck the Online box
Note: this can also be done from the right click menu when the
system was highlighted in configuration manager

Configuration tab
In this tab you can change the components assigned to this
system
Note: ONLY change this when the system is not in use. This will
affect all instrument methods created for this system.

Access tab
As described during the system creation, this tab allows changes
to who has access to this system.
Choose OK to save any changes

User Management
Chapter 7
User Management
Overview of Empower User management
Create and modify Empower User Types
Create and manage Empower Users
Create and manage Empower User Groups

User Management
Empower User Management
How are Empower users are managed in three separate areas within
Empower users Empower: User Types, Users and User Groups.
managed in the
system? Empower User Types define the privilege level for all users
assigned to that User Type. Examples of User Types are
Administrator and Chemist.
Typically, configuring User Types is the first step to

implementing user management in an Empower system.
Empower comes with 4 default User Types that represent
common examples of configured User Types:
Administrator
Analyst
Chemist
Guest
These default User Types can be configured to meet the

needs of your individual system, or new User Types can be
created and configured to manage users.
Empower Users are individual user accounts created for

each user of the system. Users are created and assigned a
User Type to define their privilege level in the system. Each
named user requires a User license to access the system.
Note: User account and password management is defined in

the User Account Policies tab in System Policies.
Empower User Groups allow an administrator the ability to

control access to different Empower objects such as Projects
and Systems.
Once User Types and Users have been created, individual

users can be added to User Groups that not only allow them
access to certain Empower objects, but also designate their
User Type level when they access that object.

User Management
Empower User Types
Empower User Types define user privilege levels within the

Empower system. User Types are configured and managed
in the Configuration Manager window.
Click Configure
System to open
Configuration
Manager
window.
Select User
Types in the
Tree Pane.

User Management
Creating New User Types
New User Types can be created from the User Types table in
Right click User

Types table
and select New.
Enter new User

Type name.
Click OK.
The new User Type is defined by configuration of 3 tabs in

the User Type Properties:
Management
Methods
Data Acquisition
Note: User Type privileges should be defined by the

processes and procedures appropriate for each individual
systems intended environment. These should be based on
your company policies, procedures and any relevant
regulatory requirements.

User Management
User Type Properties: Management
Select
Management
tab
Select
appropriate
Privileges
Click F1 for Privileges are assigned by selecting the respective privileges

details of each being assigned to that User Type.
privilege
Note: The help menu has extensive details for each privilege

User Management
User Type Properties: Methods
Select Methods
tab
Select
appropriate
Privileges
Method privileges relate to any method. Including,

instrument methods, processing methods, report methods,
method sets, sample set methods and sample set method
templates.
Click F1 for Note: The help menu has extensive details for each privilege
details of each
privilege

User Management
User Type Properties: Data Acquisition
Select Data
Acquisition tab
Select
appropriate
Privileges.
Click OK.
Data acquisition privileges relate to acquiring data and the

run samples window.
Click F1 for Note: Refer to the Empower Help system for each individual
details of each User Type Properties tab for more information on the specific
privilege privileges for each tab.

User Management
Modifying User Types
User Types can be modified by accessing User Type

Properties in Configuration Manager.
Right click User

Type and select
Properties.
Select
Management
tab
Modify
Privileges.
Click OK.

User Management
Empower Users
Empower Users represent individual user accounts for each

user of the Empower system. Users are created and
managed in the Configuration Manager window.
Select Users in
Tree Pane.

User Management
Creating New Users
New Users can be created from the Users table in

Right click in
Users table and
select New
Enter User
Name, Full
Name, Allowed
User Types,
Default User
Type,
Default User
Interface and
Allowed
Interfaces.
Click OK.
(details next
page)

User Management
The Users Full Name is required in regulated environments

when using electronic signatures.
Password required forces the user to use a password when
logging in.
Always Local Login uses local user account and password
policies in the Empower system for authentication in lieu of
LDAP.
Note: The first time a user opens their user account, the
password is the same as the user name unless an
administrator changes the password.
Note: The Default User Interface is defined in the User

Account tab of System Policies.
Multiple User Types
Individual users can be assigned to more than one user type,

as some users often perform more than one job function. If,
for example, a chemist is also the System Administrator, you
can assign him or her two user types: Chemist and
Administrator.
Users assigned to more than one user type can sign onto the
system only as one user type at a time and perform only
those functions associated with that user type.
When logging on, a user can select the user type (privilege
role) for that account depending on what function the user
will be performing in the software.
Only configured user types will be available in Allowed User
Types and Default User Type.

User Management
Note: In order to use an assigned User Type other than the

Default User Type, the user has to select the Advanced
button on the Empower Login window during login to the
system.
Managing Users
User accounts can be managed after creation by accessing

User Properties.
Right click User

and select
Properties.

User Management
User Properties
Account
Status: Active,
Disabled,
Removed.
Enter New
Password and
Confirm
Password.
Select User
Must Change
Password at
Next Login (if
required).
There are three options available in Account Status:
Active: Specifies that the selected user account
is operating normally.
Disabled: Specifies that the selected user
account has been deactivated by the software
and cannot be used to login to Empower
software.
Removed: Specifies that the selected user
account has been deleted from the current
database and the account cannot be used to log
into Empower software. Removed user accounts
no longer use a named user license.
Note: When Enforce Unique User Account Name is enabled

in the System Policies, user accounts are automatically set to
the status of Removed when those user accounts are
deleted; however, the user account remains in the Users
table.
Note: Users can change their own password; however,

unless the users have management privileges, they must
enter their current password before Empower accepts the
new one.

User Management
User Types/Interfaces tab
Select Allowed
User Types
Select Allowed
Interfaces.
Click OK.
The User Types/Interface tab allows modification of the

Allowed User Types, Default User Type, Allowed
Interfaces and Default User Interface.

User Management
Empower User Groups
Empower User Groups allows an administrator to define

access to Empower system objects such as Projects,
Systems, etc. Empower User Groups are accessed from the
Select User
Groups in Tree
Pane

User Management
Creating New User Groups
New User Groups can be created from the User Groups table
in Configuration Manager.
Right click User

Groups table
and select New.
Enter Group
Name, assign
Group Admin
(if needed), and
assign Users to
User Group
Note: The group administrator can create and delete user

accounts in the specified user group without special
privileges. You do not have to select a group administrator.
Note: You must have user Create User Group privileges to

create user groups.

User Management
Modifying User Groups
User Groups can be modified by accessing User Group

Properties in Configuration Manager.
Right click User

Group and
select
Properties.
Select Group
Properties tab
Modify Group
Admin or Users
in Group.
Note: Only an administrator, the current group administrator

or a user with Alter User Group privilege may change the
Group Admin setting.

User Management
The Admin Properties tab allows the group administrator to

administrate the User Group.
Select Admin
Properties tab
Select Add
User, Delete
User, Modify
User or Copy
Preferences
Click OK.
From this tab, the group administrator can add users,

delete users (from the group) or modify users and copy user
preferences from one user to another.
Export to Text
An administrator can export all the user profiles to a text file

for documentation and records management.
This export to text file will work with all Configuration

Manager properties, including: Empower Nodes, Systems,
Users, User Types, User Groups, and Plate Types.
This will save time in documenting configuration manager

functions.
The Export to Text file can be generated from the right click
menu of the Empower Nodes, Systems, Users, User Types,
User Groups, and Plate Types.

User Management
Right click and

select Export to
Text.

User Management
Summary
Empower users are managed in three separate areas within Empower:

User Types, Users and User Groups.
Empower User Types define the privilege level for all users assigned
to that User Type.
Empower Users are individual user accounts created for each user of
the system.
Empower User Groups allow the ability to control access to different

Empower objects such as Projects, Systems, etc.
Review Questions
1. Which Empower window allows User Types, Users and User Groups to be
created, modified and managed?
2. What are the 3 types of Account Status available for User accounts?
3. Other than an Empower administrator, what user can administrate users

in a User Group?
4. What Empower feature can be used to obtain instant information to

Empower system objects such as Users, User Types and User Groups?

Project Management
Chapter 8
Project Management
Overview of Empower project management
Structure of Empower projects
Project organization and hierarchy
Create, clone and manage projects
Project data management, backup and restore

Project Management
Empower project management
What are A project is a user-defined collection of methods, results,

Empower peaks, sign-offs, audit trails, curves, custom fields, and raw
projects? data that resides in Empower. These methods, results etc.
are stored in a reserved area of tablespace within the
database. Raw data are stored separately and grouped by
project.
Tablespace is the portion of the Oracle database where all

the Empower metadata is stored, i.e. everything but the raw
How are projects data files. Examples: methods, sample information results
managed in the etc.
system?
Creating and administering projects
Projects are created and managed from Configuration

Manager, an Empower window through which most
administrative tasks are performed.
When creating a project, its properties can be defined such

as the project name, the amount of tablespace reserved for
the project, user access and more.
Once created, the left side of the Configuration manager

window lists all projects by name under the Projects folder in
a tree-like structure. A selected project appears under the
Project folder; its sub-projects appear in the table on the
right side of the Configuration Manager window.
There are three project types: standard, validation template,

and validation working. Most projects are considered
standard projects; validation template and validation
working are for use with the MVM option only.

Project Management
Working with project data
A project is used through the Project window, which provides

a centralized, functional (and visual) link between the
database and user interface. Projects can be utilized to
create methods, process data, generate and print reports,
and manage information using the menus, views, and tools
in the Project window.
Also, project views can be customized to suit individual

workflow and standard operating procedures.
Organizing projects
Projects and sub-projects can be created within a

hierarchical structure to manage them individually and/or as
a unit.
When creating a project, determine whether it should be

created at the project root directory (a top-level project) or
in a project hierarchy as a sub-project.
This hierarchical structure allows organization of multiple

projects into one common project structure.
Tips:
An Empower sub-project is functionally identical to an

Empower project; the only difference is that it has
another project as a parent. (similar to a subfolder in
Windows)
Sub-projects can also be parents and include other

sub-projects.
Projects within a hierarchy can have unique user

access privileges and other settings.
For example, user access can be granted to specific

sub-projects but not to the parent project.
When backing up a parent project and its sub-projects,

the hierarchical structure remains intact.

Project Management
When restoring a sub-project or hierarchy, the project

is restored to the parent project directory selected in
the Restore Project wizard.
Note: cloning projects maintains the original hierarchy.
Deleting a project with sub-projects deletes both the

parent project and sub-projects when you have the
appropriate user privileges to delete both.
Structure of the Empower project window

The Project
window
separates
information into
folder-like tabs
that organize
data by
category.
Each selected
tab, or category,
displays the
information in
the Project View
table. The Project Window includes the following components:
Menu bar Displays menus that execute the

commands used in this window.
Toolbar Displays shortcut buttons that provide quick
access to primary commands used in this window.
Just-In-Time dialog bar (Pro interface only)
Displays a check box and save tool to view and save
Just-In-Time view filters.
Filter by Displays the Filter By list to select a view
filter, the Edit View button to access the View Filter
Editor, and the Update button to apply the selected
view filter.
View table Displays information corresponding to
the selected view and view filter. View filters limit or
tailor the types of information displayed by the view.

Project Management
By applying different view filters, you determine what

information appears in the view table.
Project tree (Pro interface only) In Multi-Project

mode only, displays a branched list of open projects
and associated views.
A Global Projects branch displays combined views for

all open projects. Appears automatically when you
open multiple projects in Configuration Manager.
Multi-Project mode will be covered later in this
chapter.
Structure of Empower data
Empower projects consist of two separate components: the

metadata contained in the Empower Database associated
with the project (i.e. Sample Name, Injection #, Channel
ID, etc.) and the raw data flat files in the Raw Data drive
comprised of the raw signal generated from the instrument
(the channel of data).
The metadata stored in the database is assigned an Oracle

ID number starting at 1000, incremented by 1 as new
metadata objects are created irrespective of the type of
object (i.e. 1000, 1001, 1002, 1003, etc.)
For instance, a new project may assign the Oracle ID number

for an instrument method as 1000 and newly created Sample
Set would be assigned an Oracle ID of 1001. The Oracle ID
number for each metadata object is project specific. For
example, the Oracle ID 1000 may correspond to a processing
method in one project, but may correspond to a result in a
different project.

Project Management
Oracle ID
The Oracle ID is used to link information in the project. For

instance, the Sample Set, all methods and calibration
curve(s) used to generate a result can be traced back from
the Oracle ID, or Result ID, in that particular project. The
Channel ID identifies the raw data corresponding to the
result.

Project Management

Project Management
Raw Data Files
Raw data flat files are encrypted and protected with a CRC.
The raw data flat files are stored in the Projects folder of the
Raw Data drive on the Empower Database server (if using a
single server configuration) or in a network location where
the Raw Data files are configured to be stored (i.e. a SAN).
The raw data files can range in size from a few KB (i.e.
single wavelength UV data) to 100 MB or more (i.e. PDA
spectrum or MS).
Note: The number of injections acquired and ultimately the

number and size of channels acquired with each injection will
determine how large or full the Raw Data drive becomes.
Later in this chapter, it will be shown how to archive projects
to remove associated raw data files to free up space on the
Raw Data drive.

Project Management
Project Organization and Hierarchy
Organizing Empower projects is critical to ensure that

information can be quickly and easily located. This applies
not only to projects active in the Empower system, but
applies to projects archived outside of the system as well.
Here are some examples of how companies are organizing

their projects and sub-projects:
Product name
Method or Analysis Type
Chromatographic System
Empower User
Contract Customer (Contract Labs)
Research Project
Department
Combinations of the above
While its important to design a naming scheme to organize

projects, its also important to consider the following
information as well:
Time period project(s) used
Retention time of the project
User access to the project
For example, Quality Control laboratories typically use the

same project naming convention repeatedly over specified
time intervals.
The core project name can consist of the Method. If this
project is being constantly cloned or recreated with the same
core project name, it will be difficult to find data in the
projects from a specific time period as all archived projects
would have the identical name.
By adding a time period into the name of the project (or

parent project), this will help quickly locate archived data as
the project names will differentiated by the time period
i.e. consider the project name MethodXYZ vs. Method XYZ
Q1 2011.
Which do you think would be easier to locate data for

MethodXYZ that was acquired in the 1st quarter of 2011 from
all other projects named MethodXYZ?

Project Management
Project Organization (continued)
Below is an example of project hierarchy which allows the

use of a parent project / sub-project relationship. The ability
to create project naming hierarchies allows administrators to
easily manage project creation, backups, archiving and
access.

Project Management
Viewing Empower Projects
Empower projects are created in the Configuration Manager

window.
Click Configure
System to open
Configuration
Manager
Select Projects
in the Tree
Pane.

Project Management
Project Table
Statistical information about projects can be viewed from the

Project Table.
Right click
Project and
select Update
Statistics.
Project
Statistics are
displayed in
Projects table.

Project Management
Project Table (continued)
The columns in the project table are:

Name: project name
Owner: The current owner of the project. The project

owner defaults to the user that created the project or
restored it into the system.
Create Date: The date when the project was created.
Full Audit Trail: The check box indicates Full Audit

Trail support was enabled when the project was
created.
Locked: The selection indicates that the project is

locked as Read Only Lock, Process Only Lock or Full
Project Lock.
You must have the appropriate privileges to lock or
unlock projects.
Comments: Displays the comments entered when the

project was created.
Tablespace Quota: The total amount of tablespace

reserved for the project when it was first created or
last modified.
Tablespace Free: The amount of quota tablespace

that is currently available to the project.
File Space Used: The amount of disk space occupied

by the raw data in the project.
File Space Free: The amount of free disk space in the

Raw Data drive.

Project Management
Creating a New Project
New projects can be created from the Projects table in

Right click
Projects table
and select New.
Or select New
Project button
The New Project

Wizard opens.
Select the New
Parent Project
from the
Projects list.
Click Next >.

Project Management
Select the
amount of
Project
Tablespace.
Full Audit Trail

Support and
Project Audit
Trail Policies
can be enabled
(if required).
Select to enable
or disable
ApexTrack
Integration
and set Default
Algorithm.
Note: The ability to set Full Audit Trail Support and Full
Click Next >. Audit Trail Policies depends on how the New Project Policies
are set in System Policies. Refer to the chapter that covers
System Policies for more information. Once a project has
been created as a Full Audit Trail project, it cannot be
undone.
Select which
Options to
enable in the
project.
Click Next >.

Project Management
Note: If a particular option is not being used in the project,

Waters recommends disabling the option(s) since more
tablespace will be utilized even if option is not needed. Also,
disabling unnecessary options removes unnecessary menu
items and features from Run Samples and Review.
Set the Allowed

Access.
Set Group User

Type and Allow
Access to
Groups (if
applicable).
Set World User

Type (if
applicable).
Click Next >.
The Access Control window allows control over which users

have access to the project. The following is a guideline to set
up user access:
Allowed access
Owner only (default)
Owner of the project and users with Administrator privileges

can access the selected project.
Owner and group
Owner of the project, Administrators, and group members

specified in the Allow Access to Groups list can access the
selected project.
Owner, group, and world
All users in the Empower database can access the selected

project.

Project Management
Access Control Continued

Group user type
When Owner and Group, or Owner, Group, and World access

is allowed, a temporary user type can be assigned (which
can differ from the user type assigned to the individual user
accounts) to group members selected in the Allow Access to
Groups list. Select the appropriate group user type from the
list.
Choices: User types with the same or fewer privileges than

user assigning privileges.
Default: User's Own Type
Note: The Group User Type (and its associated privileges)

selected overrides a user's individual user type (and
associated privileges). To preserve a user's original user type
privileges for access to the selected project, select User's
Own Type from the list.
Allow access to groups
Specifies (from a list of all groups in the current Empower

database) the group(s) that will have access to the new
project .
Access privileges of users that belong to these groups

override access privileges of the selected world user type.
If Owner, Group and World is selected, users that do not

belong to any selected groups in the Allow Access to Groups
list are assigned the World User Type access.

Project Management
World user type
When Owner, Group and World access is allowed, a

temporary user type is assigned (which can differ from the
user type assigned in the individual user accounts) to all
users in the Empower database when they access the
selected project. Select the appropriate world user type from
the list.
Choices: User types with the same or fewer privileges than

user assigning privileges.
Default: User's Own Type
Note: The World User Type (and its associated privileges)

selected overrides a user's individual user type (and
associated privileges). To preserve a user's original user type
privileges for access to the selected project, select User's
Own Type from the list.
Select items to
copy from other
project.
Select a Project
from the list to
assign an
existing project
to copy items
from.
Click Next >.

Project Management
Enter Project
Name and
Project
Comments.
Enter Audit
Trail Comment
(if applicable).
Click Finish to
create project.
Note: The Project Name can be up to 30 alphanumeric

characters including underscores and spaces. Project
Comments are required for Full Audit Trail projects and can
be up to 250 characters.
New project
appears in the
Projects table
of Configuration
Manager.

Project Management
Project Cloning
Copies of one or more projects can be created to use the

information stored in these projects as a building block for
other projects. Cloned projects include the methods,
preferences, view filters, custom fields, audit trail settings,
and access settings that exist in the base project.
When a project is cloned, the project and its settings

are copied, including the system policies set for that
project (including GXP/ER/ES regulatory policies).
Empower does not copy the raw data or results to the
new projects. These can be copied separately, from
within a project.
A name prefix and/or suffix can be defined to automatically

assign to cloned projects created from the seed project (for
the parent project, not sub-projects). The prefix and suffix
can be incrementally changed with a number, or a letter, for
each subsequent project so that the user can quickly identify
a set of cloned projects generated from a particular base
project
Creating Multiple Copies of One Project
Multiple clones of a single project can be performed from the

Right click
project to be
cloned and
select Clone.

Project Management
Enter New
project name
seed.
Enter # of
copies to create
and Prefix or
Suffix with
Increment to
add to seed
name.
Select Perform
Shallow Copy
of Methods (if
required).
Select Set
Project
Comment and
enter Project
Comments (if
applicable).
Enter Audit
Trail Comment
(if applicable).
Click OK.
Cloned
project(s)
created with
seed name and
incrementing
prefix or suffix.

Project Management
Creating One Copy of Multiple Projects
A single clone of multiple projects can also be created using

the Configuration Manager window.
Select multiple
projects, right
click and select
Clone.

Project Management
Enter Prefix
and/or Suffix.
Select Perform
Shallow Copy
of Methods (if
applicable)
Set Project
Comments and
enter Project
Comments (if
applicable).
Enter Comment
(if applicable).
Click OK.
Cloned projects
created with
names of base
projects and
incrementing
prefix or suffix.

Project Management
Project Properties
The Project Properties allows changes to be made to existing

projects. Project Properties can be used to perform one or
more of these actions:
Change the project owner (if you are logged in using
an account with the Change Owner privilege)
Enable or disable available Empower software options
for the current project
Change tablespace quota (if you are logged in using an
account with the Change Quota privilege)
Create, edit, and delete custom fields and copy existing
custom fields to other projects
Change access to the selected projects
Project Properties are accessed in the Configuration Manager

window.
Select project,
right click and
select
Properties
The Project Properties dialog box consists of 5 different tabs:

General
Custom Fields
Access
Integrity
Processing

Project Management
Project Properties General tab
Select Owner.
Designate
Project Parent.
Select Enabled
Options.
Set project
Database
Tablespace.
Project Properties Custom Fields tab
Click New, Edit,

Delete,
Lock/Unlock
and Save to
Project to
work with
Custom Fields.

Project Management
Project Properties Access tab
Select Allowed
Access, Allow
Access to
Groups (if
applicable), and
Group/World
User Type (if
applicable)
Project Properties Integrity tab
When a project backup or restoration is run, integrity tests

are performed on the files. The tests determine whether all
of the project's data files have been backed up or restored
successfully.
For each raw data file Channel ID in a given project a Raw

Data File Integrity test determines whether the raw data file
can be read. It also determines whether the date, time, and
size information for each channel data file is correct.
During project backup, checksums of the *.EXP and *.INF

files are produced. They are verified when the project is
restored.
Note: the file Backup.log contains information about the

Oracle export process during project backup. This
information is stored in the project's backup location.

Project Management
Select Integrity
file and click
Details.
Project Integrity
file verifies raw
data files
associated with
the project.
Note: If any errors are detected, a message asks the user to

view the report via the project's Project Properties dialog
box. (Errors are also recorded in the Message Center and/or
the System Audit Trail.)

Project Management
Project Properties Processing tab
Select Enable
ApexTrack
Integration
and select
Default
Algorithm (if
applicable).
Set Number of
Digits of
Precision
Displayed for
Area and
Height.
Click OK.
Note: all data within Empower is automatically recorded to

14 decimal places. This just adjusts how many are shown.

Project Management
Locking Projects
Locking a project prevents users from accessing the project.

It is possible to set different types of project locks depending
on the purpose of locking the project.
Projects can be locked from the Configuration Manager

window.
Right click
project and
select Lock
Project >
Read Only
Lock, Process
Only Lock, or
Full Project
Lock.
Note: Recommendations on locking projects:
Ensure that no users need to access a project before

locking it.
If planning to delete a project, it is recommended to

first lock the project, and then back up the project,
before deleting it.
Locking or unlocking a project with sub-projects

displays a message asking to lock or unlock the sub-
projects as well.

Project Management
Types of project locks
Read Only Lock - Allows a project to be opened but

only allows data to be read. No data acquisition is
allowed.
Process Only Lock - Allows a project to be opened
and allows both the reading and processing of data. No
data acquisition is allowed.
Full Project - Fully locks a project. Projects with a full
lock cannot be opened.
The lock status of a project can be determined in

Configuration Manager:
If a project is locked, the project folder icon includes a

lock.
The lock status of a project can also be seen in the
Locked column.
Unlocking Projects
A project can be unlocked from the Configuration Manager

window.
Right click
project and
select Lock
Project >
Unlock Project.

Project Management
Database Management
The following diagram illustrates what will happen to a

database over time with no data management.
With no active Data Volume

database Size
management, Decreasing Backup
Performance
the performance
of the database
decreases over Not enough time
time. to backup
No space on
the backup
system
Not enough Time

space
With no data management over time, a database will

eventually run out of physical space.
As the size of the database grows, the performance of the

database decreases proportionally to the amount of data
contained in the database.
In addition, as the database grows in size, there is an
increased risk that the daily security backup system will run
out of space or not have enough time to complete a full
backup before the next backup begins.

Project Management
Proper Database Management
The following diagram illustrates an ideal profile of a

database over time with proper database management.
Proper database Size

management Stable
Performance
requires actively
managing the
size of the
database over
time allowing
the performance
to remain
Data Volume
stable.
Backup
Time
With proper database management, the size of the database
remains constant over time.
The amount of data being added to the system is offset by

data being archived and removed from the active database.
This allows the performance of the database to remain stable

over time.
Project Data Management
As Empower projects grow in size over time, it is imperative

to regularly backup and permanently archive project data to
ensure proper system performance.
Empower projects must be backed up within the Empower

application for proper data management.
Projects are backed up as flat files that include both exported

database metadata and the corresponding raw data files
from the Raw Data drive and then separately deleted out of
the Empower system.

Project Management
Both activities are performed in the Configuration Manager

window. Project backups can be backed up to most any type
of media: network drive, SAN, optical media, external hard
drive, etc.
Note: All backups of Empower projects must be

performed in Configuration Manager. NEVER
attempt to backup a project using the operating
system such as Windows Explorer.
Project Backup
Right click
project(s) and
select Backup
Project.
Confirm
project(s) to
backup.
Enter Backup
Comments (if
applicable).
Click Next >.

Project Management
Click Browse.
Select the
backup location.
Click OK.

Project Management
Verify backup
location.
Click Next >.
Allow backup to
complete and
click Next >.

Project Management
Verify project
backup
destination
directories.
Click Finish.
Backup of
project(s) can
be viewed
through the
operating
system file
directory.
Note: In addition to the Project_Integrity.txt file created to

verify project backup, a backup.log file is generated that
summarizes everything in the project that was backed up.

Project Management
Project Deletion
To complete archive of the project(s), manually delete the

project(s) from Empower using the Configuration Manager
window.
Note: Be sure that the project is backed up BEFORE deleting

any project in the system.
Once the project has been deleted from the system, the data
is permanently removed.
Deleted data can only be recovered from project backups or
restoring from a daily security backup of the Empower
server.
It is recommended to test restoring the project backup into
the system before permanently deleting it.
Right click on
the project(s)
and select
Delete.
Project(s) are
deleted from the
system.

Project Management
Project Restoration
Archived project(s) can be restored back into Empower. This

allows access to the database information as well as the raw
data files associated with the project.
Before restoring project information to the database, ensure

that these conditions are met:
The backup device is installed and powered on.
If restoring a project over the network, enter the exact

directory path in the path option (for example,
N:\UserA\Backup), or use the Browse button to browse
the network drives for the directory and subdirectory of
the backed up project.
Note: When backing up or restoring projects, do not use a

share name that contains spaces. However, you can backup
or restore from a mapped drive with a name that contains
spaces.
You have the appropriate user privileges for the

projects or sub-projects that you are restoring.

Project Management
Consider the following when performing project restoration:
If the directory contains single project backup files, the

project is restored.
If the directory contains multiple backed up project
files, the software give you the option to choose which
projects to restore from that directory.
When restoring projects created with previous versions
of Millennium or Empower, you need to select a time
zone for the project.
When restoring single projects, the software displays a
warning box whenever an error occurs. You must
respond to the warning before the restore operation
continues.
For batch restore operations, the software completes
the process without operator entry, generating a log
file that lists any integrity errors found during the
restore operation. This facilitates unattended restore
operations by ensuring that warning messages do not
stop the batch process.
The batch process is halted only when it encounters
errors that cause the project to be deleted or cause the
restore operation to fail.
Duplicate project names are not allowed unless the
projects have different parents.
Empower displays a warning message if you attempt to
restore to a duplicate name.
Project restoration considerations for Millennium

projects
To restore a Millennium 2.1x project, the Pre 3.0 Converter

utility tool is run on the selected project. Projects older than
version 2.1x must first be updated to version 2.1x before
upgrading to Empower.
Note: If you are restoring a project created in Millennium

version 3.0 or earlier, you need to perform a refresh in
Configuration Manager in order to see the restored projects.
After the Pre 3.0 Converter utility tool restoration process
ends, press F5 in the Configuration Manager tree to see
these projects.

Project Management
Project Restoration
Projects are restored from the Configuration Manager

window.
Right click
Projects table
and select
Restore
Project(s).
Enter Restore
location or click
Browse and
select Restore
location.
Click Next >.

Project Management
Click Yes to
restore entire
project hierarchy
or No to restore
selected project
only.
If entire project
hierarchy
selected, select
the new parent
project for
project(s).
Click OK.
If single project
selected for
restore, enter a
Project Name
and select
Project Parent.
Click Next >.

Project Management
If entire project
hierarchy
selected, select
project(s) to
restore.
Click Next >.
Allow project(s)
to restore and
click Finish.

Project Management
Restored
project(s)
available in
Configuration
Manager
Projects table

Project Management
Summary
Empower projects are comprised of two components: the metadata

information stored in the database and the raw data flat files stored in
the Raw Data directory.
Projects can be organized in a hierarchal structure including parent

projects and sub-projects.
It is critical to actively manage the Empower database to ensure that

the performance of the system remains consistent over time.
The Configuration Manager window allows following project

administration tasks: create, lock, backup, delete, restore and
manage.
Review Questions
1. Where are existing projects configured within Empower once they have
been created (i.e. increase project tablespace)?
2. Within Empower, what are the 2 activities that need to be performed on

projects to archive them?
3. Can more than one project be cloned at the same time? If yes, can those
projects all be renamed with a name different from the original
project(s)?
4. How many types of project locks are available in Empower and what do
they do?
5. What file can be used to verify the status of a project after backup or
restore?
6. Describe one of the benefits of organizing projects in a hierarchy.
7. Can a backup and restore of Empower data be performed using the

Operating System? Why or why not?

Operational Mechanisms



Database Name Resolution

Empower finds the database by resolving the database
service name to the server and the instance. A separate TNS
names file is set-up on each client.
The different ways to set up the TNS names files on the
clients are:
Manually configure the database service name on each
client or LAC/E32 using Oracle Net Configuration Assistant
Copy it down manually to each client from the server
Use the TNS_ADMIN environmental variable to centrally
use one tnsnames.ora file
Use directory replication
To minimize Empower name resolution issues, use the IP

address of the server instead of the host name in the
tnsnames.ora file

The Listener
When an instance starts, the listener opens and establishes a
communication pathway through which users connect to
Oracle.
The listener merely connects users to the database, it does
not check to see if the database is fully functional or not.
The command lsnrctl status can only be run on the Database
server.
Be sure you are in the right oracle home. The listener is
ready when the instance is ready. After stopping and
restarting the listener wait almost 1 min to see the
discovered instance.

Distributed Component Object Model

COM defines how components and their clients interact. If
the client and component are in the same process, then the
communication is direct (no need for intermediary);
however, if the processes are shielded from each other (as
they are in Windows NTFS based systems), the client cannot
contact the component directly. COM transparently
facilitates the inter-process communication.
In stand-alone Empower workstations, communication
between QuickSet.exe and the other processes is
facilitated by COM.
DCOM extends COM to support communication between
objects across a network and allows portions of an
application to be distributed so that the right components
can be run in the right place. DCOM uses remote procedure
calls (RPCs) and Windows NTFS security features
(permissions) to enable applications and processes to
communicate across networks using the same tools and
technologies of COM.

How DCOM is Used

When a run is started from a client, a process called
QuickSet.exe is started on the client.
Quickset.exe launches the process called
InstrumentServer.exe on the remote acquisition server via
DCOM.
The InstrumentServer process handles communication for
the active chromatographic systems on an acquisition
server.
For Empower Enterprise, DCOM is managed by the Waters
Service and does not have to be manually configured on
acquisition servers used for distributed (remote) acquisition.
Note: Only QuickSet.exe exists on the client. The other
process, InstrumentServer live and run on the acquisition
server.


User Login
User enters User Name and password. Oracle Net passes
the information to the Server for validation.
If the user name and password are validated, the
authentication is sent back via Oracle Net and the Login
window is enabled.
Optionally If LDAP authentication have been selected a
Domain Controller is contacted using the LDAP protocol.

Project Query
User double clicks a Sample Set in the Sample Sets tab of
the Project window. Oracle Net sends the query to the
server.
The server finds the information and sends it back via Oracle
Net. The Injections are displayed in the Injections tab of the
Project window.

Reviewing Data
From the Project window, the user selects a Channel to bring
into the Review window. A SQL query is sent to the server.
The Review window opens via COM.
The server sends the Channel information back via Oracle
Net.
The server sends the raw data information via TCP/IP.

Local Acquisition: Run Sample Set

The user queues up a Sample Set and clicks the Run button.
InstrumentServer is activated and sends an instrument
method request to the server.
The server sends the instrument method information back to
the InstrumentServer.
InstrumentServer communicates with the instrument via
Ethernet.

Local Acquisition: During Chromatographic Run

InstrumentServer communicates with the system during a
run via Ethernet.
The data is buffered locally on the Acquisition Servers hard
drive and incrementally uploaded to the server during
acquisition.
The Run Samples Real Time Plot is updated via COM.

Local Acquisition: Post Chromatographic Run

The buffered data is sent via TCP/IP to the raw data
directory on the server.
The sample information (channel update) is sent to the
server database.

Remote Acquisition: Chromatographic Run Start

The user clicks the run button in Run Samples on the client
and the sample set information is sent to the database
server.
The client computer sends information to the LAC/E32
InstrumentServer via DCOM.
The LAC/E32 InstrumentServer sends a method request to
the database server.
The database server sends back the method information.
The LAC/E32 InstrumentServer communicates the control
information to the instrument via Ethernet.

Local Acquisition: During Chromatographic Run

InstrumentServer communicates with the system during a
run via Ethernet.
The data is buffered locally on the Acquisition Servers hard
drive and incrementally uploaded to the server during
acquisition.
The Run Samples Real Time Plot is updated via COM.

Local Acquisition: Post Chromatographic Run

The buffered data is sent via TCP/IP to the raw data
directory on the server.
The sample information (channel update) is sent to the
server database.

Processing
InstrumentServer communicates with the Processing Server
via COM.
A request is made to the server database for method and
raw data.
The Method is sent via Oracle Net and the raw data is sent
via TCP/IP.
The Processing Server processes the data and sends the
results to the server database.

Reading Raw Data Files

The following occurs when reviewing a chromatogram or
during the processing of data. The raw data file is read from
the raw data share provided that the OS share has the
proper permissions. The Everyone group is the operating
system group account allowing the reading of the raw data
from the share. The Everyone group permission is set with
Read Only access.

Writing Raw Data Files

During acquisition, as the raw data is collected, the raw data file
is streamed into a file on the raw data share. At the end of each
chromatographic run, the raw data file is closed.
The transfer of the raw data file is initiated by WatersService
which is a DCOM service. WatersService is authorized to write
the file to the share because this service has the authority of
the local System OS account. The local System account has
Full Control permissions on the share.
The WatersService also creates a new directory in the raw
data share during the creation or cloning of projects.
The Watersservice can be host by a service account different
than system. Then the full control on the rawdata share has to
be set to full control for the owner of the Watersservice.











To disable WatersService on a Citrix Server

To disable the WatersService service on the Citrix Server:
1. Logon to the Citrix Server with an administrator group account.
2. Access Windows Services.
3. Right-click on the WatersService service and select Properties.
4. Change the Startup type to Disabled and then click OK.
5. Reboot the server. After the server restarts, each Citrix user will
automatically get their own copy of the processing server
(procserv.exe) running with their OS user.
The following should be considered when the WatersService is

disabled on the Citrix Server:
When qualifying the Citrix server, run Empower AQT utility from the
server itself or a Citrix client. Running the utility from a standard
client against the Citrix server will not work properly. Also, ensure
that the logged in OS user has the privilege to access the desired
printer.
In order to change the time zone for the Citrix server, access the
properties of the server in Configuration Manager from the Citrix
server or from a Citrix client. This action cannot be performed
from a standard client.



Intro to Oracle 11g

Intro to Oracle 11g

Intro to Oracle 11g
Benefits of Integrating Oracle with Empower

Since Oracle is built into Empower software, you can
organize data according to subject so that the data is easy
to:
Retrieve
Oracle stores information about how different samples
are related so that it is easy to bring related data
together.
Track and Verify
Oracle allows you to keep (and report) an extensive
audit trail that tracks changes made to the database.
Report
You can build customized, individual, and summary
report methods.
Recover
Oracle has the ability to recover from failed or aborted
transactions .
It also keeps a record of all changes made to the
database to enable recovery of data in the event of a
failure.

Intro to Oracle 11g
The built in database manages all raw data, methods and results
by permanently linking all aspects of the electronic record together.
Even if methods or sequences are subsequently updated, the
Empower database will always retrieve the actual version used for
any reported result.

Intro to Oracle 11g
Oracle Storage Structure

Logical and Physical Database Structures
The database has logical structures and physical structures.
Logical Components (=the instance)
Schema: A schema is a collection of database objects that are owned by a
database user. Schema objects are the logical structures that directly refer to
the databases data. Schema objects include such structures as tables, views,
sequences, stored procedures, synonyms, indexes, clusters, and database links.
In general, schema objects include everything that your application creates in
the database.
Tablespace: The Oracle database is logically grouped into storage areas called
tablespaces.
Each tablespace consists of one or more physical files called datafiles.
Segment: A segment is the largest unit of storage within a tablespace. For
example, all storage associated with a table is stored in a segment.
A tablespace may have one or more segments.
Each segment is made up of one or more extents.
Extents: An extent is a storage area made up of a contiguous group of Oracle
(data) blocks.
When a segment (also known as table) is created, it consists of at least one
extent.
A table grows by adding additional extents.
Oracle (data) blocks: This is the smallest unit of storage in an Oracle
database.
One Oracle block correlates to one or more operating system blocks
allocated from an existing physical data file.
The Oracle block size can be from 2 to 16 kbytes and is set at database
creation.

Intro to Oracle 11g
Oracle Storage Structure (continued)

Physical Components
Data files: The physical repository of all of the data in the
database.
Each tablespace may consist of one or more datafiles.
For Empower, there is a 1:1 ratio of data files to tablespaces
during creation .
The database administrator can change the size of a datafile
after its creation or can specify that a data file should grow
dynamically as objects in the tablespace grow.
In general, for Empower the data files set to grow as objects
in the tablespace grow.
The two types of data stored in the data files:
User data: Your stored information
System data: The information the database needs to manage
itself and your data (location of data files, user names, types
of fields, and so on.)
OS block: The smallest unit of physical storage space on a hard
drive
The OS block size is dependent on the file format used and
operating system installed.
Ideally, the Oracle block size should be equal to the OS block
size.

Intro to Oracle 11g
Oracle Architecture
Oracle is a relational database management system that provides a
comprehensive, integrated approach to data management. The Oracle
database consists of a physical structure (the database files) and a logical
structure (the instance).
Primary components of Oracle:
The database - the physical files accessed by the instance. The three file
types are:
data files: physical files that contain the actual data in the database
redo logs: physical files that contain a record of changes made to the
database to enable recovery of data in case of failure
control files: physical files that contain the information necessary to
maintain and verify database integrity. Contains a list of all other files
that make up database such as data files and redo logs.
The instance - the combination of background processes and memory
structures necessary for users to be able to access information in the
physical database. The part which provides access to information on the
database. Every time an instance is started, a shared memory area called
the System Global Area (SGA) is allocated and the background processes
are started.
When you open or shut down the database, you are really opening or
shutting down the instance.
When people refer to the Oracle database, they are referring to the
combination of the instance and the database physical files.

Intro to Oracle 11g
The Oracle Database Files

The database files are of three types:
1. Datafiles
2. Redo logs
3. Control files
There are also several key physical files that are not considered to
be part of the database.
1. The parameter file: Used to define/create the instance
2. The password file: Used to validate remote logins
3. Archived log files: Offline copies of the redo logs that may be
necessary for recovery

Intro to Oracle 11g

Intro to Oracle 11g

Intro to Oracle 11g

Intro to Oracle 11g
How Redo Logs Work

When transactions occur, they are first stored in two memory
areas: the data buffer cache and the redo log buffer.
Data in the data buffer cache is eventually written back to
the data files. The data in the redo buffer cache is written
to the redo log files.
Redo entries are written to a redo log file whenever one of
the following occurs:
A transaction commits
The redo log buffer is one-third full
There is more than a megabyte of changed records in
the redo log buffer
A timeout occurs (every three seconds)
Before the data in the database buffer cache is written
to the data files

Intro to Oracle 11g
How Redo Logs Work (continued)

Each redo log file can hold up to 250 MB of transactions. When a
redo log file is full, a log switch occurs and the transactions are
written to the next redo log file.
When a log switch occurs, an event called a checkpoint is
initiated.
During a checkpoint, a number of dirty database buffers
covered by the redo log being checkpointed are written to
the data files. The headers of all of the datafiles and control
files are then updated to reflect that the process has
successfully completed.
What happens after the last redo log file is filled depends on which
archive mode you are in.

Intro to Oracle 11g
ARCHIVELOG Mode vs. NOARCHIVELOG Mode

You can run in two archive modes: ARCHIVELOG mode and
NOARCHIVELOG mode.
NOARCHIVELOG mode: After all redo logs are filled, the existing
data is overwritten.
ARCHIVELOG mode: After each redo log is filled, a log switch
occurs, new data is written to the next redo log in line and the data
stored in the recently filled redo log is dumped to an archive log on
a separate drive.
This lets you recover almost to the point of failure. You may lose
up to 250 MB worth of transactions (whatever the amount was
in the current redo log). However, if the redo logs were
overwritten without archiving and the database fails, you would
not be able to recover any transactions completed since the last
backup.
With mirrored redo logs, you may be able to recover up to the
point of failure.
Empower Enterprise systems should always be in ARCHIVELOG mode,
which is enabled during installation.
Do NOT change this! Although you take a slight performance hit,
the protection ARCHIVELOG mode provides is far more valuable.
By default, stand-alone workstations are in NOARCHIVELOG mode.

Intro to Oracle 11g
Control Files
Before the database starts, it checks the control file to find out if
recovery is necessary. If there are any missing files or if anything was
changed while the database was not in use, the control file will then be
able to tell that recovery is required before the database can be started.
If the control file is not accessible for some reason, the database will not
start. To provide additional fault tolerance, the Empower Enterprise
server is set up with two mirrored control files on different physical
drives.
By default, one control file is written to the database drive and the
other to the raw data drive.
Control file contents include:
database name and identifier
data file and redo log locations
log history (recorded during log switches)
location and status of archive logs
current log sequence number
checkpoint information such as the current system change number
(transaction number)
Oracle updates the control files continuously during database use, so
these must be available for writing whenever the database is open.

Intro to Oracle 11g
The Oracle Instance

The Oracle instance consists of the memory structures and
background processes necessary to provide users with access to
the physical files. If the instance is not started, users will be unable
to access data in the database.
Whenever the instance is started, a memory structure known as
the system global area (SGA) is allocated and the Oracle
background processes are started.
The SGA is divided into four primary compartments:
The data buffer cache
The redo log buffer
The shared SQL pool
The data dictionary cache.
Each instance on a server has a unique system identifier (SID) that
was determined when the database was created.
For Empower 3, the default SID is WAT10. However, the SID
name can be WATxy where x y is 0 - 9 or A Z. It can also
start with any other characters as long as there is a total of 8
characters (without spaces) and it ends with WATxy.

Intro to Oracle 11g
The System Global Area

The System Global Area SGA is the memory area of the instance used
to cache database information used by the database processes.
SGA is shared by all Server and Background processes
It is made up of four memory structures:
1. Data Buffer Cache: Caches the most recently used Oracle block.
2. Redo Log Buffer: Caches the redo information; record changes
made to the database.
3. Shared SQL Pool: (Library Cache) Caches the most recently used SQL
statements.
4. Data Dictionary Cache (Row Cache): Caches the most recently used
definitions in the database
With Oracle11g you can change the size of the SGA, or its components,
while the instance is running.
The Program Global Area PGA is memory regions that contain data
and control information for a server or background process. A PGA is
nonshared memory created by Oracle Database when a server or
background process is started. Access to the PGA is exclusive to the
server process. Each server process and background process has its own
PGA.

Intro to Oracle 11g
The Data Buffer Cache

When information is put into the database, it is stored in data blocks. When a
database query is processed, the server process first looks in the data buffer
cache (where the most recently used blocks are stored) for any blocks it needs.
Data must be in the data buffer cache before a server process can use it. If a
server process needs data that is not currently in the data buffer cache, the
server process reads the block containing the data from the data file and places
a copy in the data buffer cache (a cache miss).
The data buffer cache is used so that subsequent requests for the same data
block may find the block already in memory (a cache hit) and not require
physical reads. The buffer cache hit ratio calculates how often a requested
block has been found in the buffer cache without requiring disk access. A hit
ratio greater than 90% will improve the performances
There is a physical limit to the size of the data buffer cache. As the cache is
filled, data blocks are removed using the least recently used (LRU) algorithm.
LRU algorithm means that information that has been in the cache unused for
the longest period of time is flushed first.
There are two ways to potentially improve database performance: increasing the
size of the data blocks so that each block can hold more data or increasing the
size of the data buffer cache so that it can hold more data blocks.
Data block size is determined when the database is created and can be
changed while the instance is running without stopping and restarting the
database. However, if you add additional RAM to the Empower server, you
may want to consider increasing the size of the SGA. Then consider
increasing the size of the data buffer cache by altering the db_block_buffers
parameter in the parameter file (SPFILE).

Intro to Oracle 11g
Redo Log Buffer

The redo log buffer records the data block that has been
changed, the location of the change and the new value in a
redo entry.
It is a circular buffer that is reused after it has been filled, but
only after all the old redo entries are written to the redo log
files.
Oracle blocks off the portion of the redo log buffer that is
being flushed to the redo log files to ensure that its
contents are not overwritten until the redo entries are
recorded to the redo log files.
New transactions can continue to write redo information to
the rest of the redo log buffer.
If the remaining space in the redo log buffer fills up before
the flushing of a portion of the redo log buffer is complete,
the database pauses until there is space in the redo buffer.
It is important to differentiate between redo information and
undo information.
Undo: Undo is the activity Oracle performs using the undo
information stored in the rollback segments to restore data
to its prior state.
Redo: Information stored in the redo logs is used to
reapply transactions that are committed but not yet
recorded in the database datafiles prior to some database
failure.

Intro to Oracle 11g
Shared SQL Pool

The most recently used SQL statements are stored in an
area of memory called the shared SQL pool so that they can
be reused if the same statement is submitted again.
Information stored in the shared SQL pool consists of:
The text of the SQL statement
A compiled version of the statement (parse tree)
The steps to be taken when executing the statement

Intro to Oracle 11g
The Data Dictionary

The information cached in the data dictionary cache is read
from the data dictionary, which is stored in the system
tablespace.
The data dictionary contains two parts:
Base tables - The first objects created in the Oracle
database. These tables are the underlying tables that store
the description of the database.
Because information in these tables is stored in a cryptic
format, they are not accessed by users looking for
information about the database.
Data dictionary views - Tables that summarize and
display information stored in the base tables
They decode the base table data into useful information.
Users can query these views to find information about
the database and its components.
Data in the base tables is necessary for Oracle to be able to
function properly. When the database is in use, Oracle reads
the data dictionary to determine the schema objects that exist
and the users that have access to them.
The data dictionary is continuously updated to reflect
changes in database structures, grants, and data
structures.

Intro to Oracle 11g
The Server Processes

Depending on how the database was built, an instance may have
several background processes, but every instance includes the
following five required server processes:
Database writer (DBWR)
Log writer (LGWR)
System monitor (SMON)
Process monitor (PMON)
Checkpoint (CKPT)
The Empower server will also have the server process Archiver
(ARCH), if it is in ARCHIVELOG mode.

Intro to Oracle 11g
The Background Processes

Database writer (DBWR)
Writes changed data blocks back to the data files.
Log writer (LGWR)
Writes the redo entries to the redo log files.
It is also the only process that writes to and reads from the
redo log files.
Checkpoint (CKPT)
Updates the database status after a checkpoint.
It notifies the control file of a redo log file switch and ensures
that dirty data blocks are written back to disk.
Dirty data block - Data sitting in memory that has been
changed but not yet written back to the database.
When a checkpoint occurs, any information in memory is written to
the database files. As this is happening, everything is synched
with the control file.

Intro to Oracle 11g
The Background Processes (continued)

Archiver (ARCH)
When running in ARCHIVELOG mode, it makes an archived copy
of the redo log files (when the log switch occurs).
System monitor (SMON)
It performs any recovery that is needed at startup.
For example, if the Oracle instance fails because the server
was powered off without closing the database, any
information in the SGA that has not been written to disk
(either to the redo log files or the data files) is lost. When
the database is next reopened, SMON automatically performs
instance recovery by rolling forward records in the online
redo log file to the data files and rolling back any
uncommitted transactions.
Process monitor (PMON)
It performs recovery for a failed user by taking the identity of
the failed user, releasing all the database resources that the
user was holding and rolls back the aborted transaction.

Intro to Oracle 11g
Understanding the Instance

Imagine yourself in a restaurant
You are the customer.
You give your order to the waiter/waitress.
That person takes your request to the kitchen.
The kitchen staff prepares the food, then notifies the
waiter/waitress when your order is ready and stock inventory.
The waiter/waitress brings the food to you.
The waiter/waitress is the user process.

The user processes are the tools used by you to interact with
the database.
The kitchen staff is the server process.
The server processes take the requests from the user processes
and fills them.
The kitchen is the system global area.

Intro to Oracle 11g
SQL Transaction Example: Update

The user execute an update command on a table.
1. A user starts a session from the client, connects to the server
through the Listener that assigns a server process. The server
process evaluates the syntax of the command, the object
(table) and privileges then returns the acknowledgement to the
user process.
2. The command is stored in the Library cache and Redo Log
Buffer. The server process execute the command, allocate
memory in the data buffer cache, read the rows of the table
from the data blocks in the data file.
3. The server process loads the data blocks from the Data file into
the data buffer cache.

Intro to Oracle 11g
SQL Transaction Example: Update

4. Copy the before image of data blocks that contain rows which are
updated into the rollback segments in the Undo Tablespace.
5. The transaction is applied, the rows are updated. The data blocks
in the Data Buffer cache contain the after image.
6. The Server Process copy the after image data blocks from the Data
Buffer Cache to the Redo Log Buffer.
7. The Server Process copy the before image data blocks from the
Undo TS to the Redo Log Buffer.
The Redo Log Buffer contain both transactions before update and
after update

Intro to Oracle 11g
SQL Transaction Example: Commit

8. The User Process is informed that the rows were updated
9. The User Process confirms the transaction. The Server Process
execute the commit command to complete the transaction
10.The commit command triggers the LGWR process that writes the
transactions in the Redo Log file

Intro to Oracle 11g
SQL Transaction Example: Commit

11. Confirm the successful commit
12. Trigger the DBWR process
13. (The DBWR process writes the after image (the modified block or
dirty block) from the Data Buffer Cache into the Data File
14. The before image is cleared from the Undo TS
15. The Check Point process (CKPT) generates a sequential number:
the system change number (#SCN) that is written in the Control
files in the Data File headers and Redo Log file. The SCN marks a
consistent point in time in the database.

Intro to Oracle 11g
Oracle Architecture: the Redo Log / Archive Files

When the Redo Log file is full:
1. A Switch Log is triggered that will overwrite the content of the next
Redo Log file.
2. The Check Point process (CKPT) generates a sequential number:
the system change number (#SCN) that is written in the Control
files, in all the Data File headers and in the Redo Log File. The SCN
marks a consistent point in time in the database. The SCN value
stored in the Control File ensures the consistency of the Database.
At startup the SMON process verifies every SCN in File headers are
the same as the one in the Control File, if not a recovery is
required.
3. The Archiver process (ARCH) copies the content of the current
Redo Log file into an Archive file. All the transactions in the Redo
Log are permanently stored in the Archive file.
4. The Database Writer process (DBWR) writes the after images (the
modified blocks or dirty blocks) from the Data Buffer Cache into
the Data File.
5. At every Log Switch ARCH process increments automatically the
Archive sequence number that identifies the new Archive file. It is
a cycling process that overwrites the first Redo Log when the last
one is full.

Intro to Oracle 11g

Oracle 11g Database Management
Rev 31011 Chapter 11: Page 1 of 37


OEM : Oracle Enterprise Management

If you use the web console on the server it may be useful to

remove the IE ESC.

Requirements for Database Startup and Shutdown

To Startup or shutdown the database, two user account credentials
are required
a local or domain Windows DBA User that is a member of the
local ORA_DBA group and an Oracle User with SYSDBA or
SYSOPER privileges.
If the user is already a member of a domain group, such as
Server Operators, the group can be added as a member of
the ORA_DBA group.
In Windows 2008 servers, local and domain administrators
are automatically added to the ORA_DBA group.
If you want to give a different user or group ORA_DBA privileges,
the procedure that follows differ depending if the Empower
database server is a Domain Server Member or a Domain
Controller.

Empower Database Server as Domain Member Server

To add a user group to the ORA_DBA group:
1. Go to Start > Programs > Administrative Tools > Computer Management.
2. In Computer Management, browse to System Tools > Local Users and
Groups > Groups.
3. In the right-hand pane, double-click ORA_DBA.
4. Take one of the following actions based on if the administrator account
you will be using to manage the database is listed as a member:
a. If it is a member, click Cancel.
b. If it is not a member, in the Select Users or Groups dialog box,
1) click Locations. In the Locations dialog box,
2) if you are adding a pre-configured local user to the group
3) select the Empower database server name.
4) If you are adding a domain user or group, select the appropriate
domain.
Note: To select a domain user or group, you must have access to the
domain administrator username/password.
If you want to select a user account on the local server
1. Click Cancel when prompted for domain credentials
2. Select the database server name from the Locations dialog box.
3. In the Select Users or Groups dialog box,
4. Enter the name for the user or group whose credentials will be used for
database management functions
5. Click OK.

Empower Database Server as Domain Controller

Note: By default, Empower Workgroup servers configured by Waters are
domain controllers.
To add a user group to the ORA_DBA group:
1. Go to Start > Programs > Administrative Tools > Active Directory
Users and Computers.
2. Click Users.
3. In Active Directory Users and Computers, click Users.
4. In the right-hand pane, double-click ORA_DBA.
5. In the ORA_DBA properties, click the Members tab.
6. Take one of the following actions based on if the administrator account
you will be using to manage the database is listed as a member:
a. If it is a member, click Cancel.
b. If it is not a member, in the Members tab, click Add.
7. In the Select User, Computers or Groups dialog box, verify that the
appropriate domain name displays in the Look in field.
8. Enter the name of the domain user or group whose credentials will be
used for database management functions, and then click OK.

sqlNet.ora
The oracle SQLNET.ORA is present on all the oracle home directory
(Client, Lace or Server).
Only the Database Server must be set to
SQLNET.AUTHENTICATION_SERVICES = (NTS)
Lace, Client must be set as per default to
SQLNET.AUTHENTICATION_SERVICES = (None)
The sqlnet is located in the [Oraclehome]\Network\Admin
The oracle Home 64bit on the server is located :

-D:\Empower\Oracle\Oracle11g\
The oracle Home 32bit on server, lace, client :
- X:\Empowe\Oracle\Oracle11gClient\ (where x correspond to
the Application drive installation.)

Setup the gLogin.sql on the database server

The file is located on the Oracle Home 64 bit on the Database
server in the following path:
D:\Empower\Oracle\Oracle11g\sqlplus\admin\glogin.sql
The glogin.sql file is used to customize the display of Sqlplus.
Sqlplus is used also internally by oracle for some database
connection.
As the query that customizes the prompt reports errors if the
database is down or in a Mount or NoMount. The database
console do not work for , starting the database or performing
recovery.
You can remark the line or simply remove them


Oracle Accounts used for login
User: sys
Password (default): oracle
Connect as: sysdba
Or
User: system
Password (default): empower
Connect as: normal


The console contains alerts and information on Oracle issues and

incidents.

Starting the Oracle Database

Unless the database is in need of recovery, it should start
automatically when the server is booted.
To start the Empower Database, use the Database Control Console.
Alternatively, OracleServiceWATn is the service used to start the
database. Its default setting is to start automatically.

Stopping the Oracle Database

Unless the database is in need of recovery or unless using a cold
backup, it should not naturally shutdown.
To stop the Empower Database, use the Database Control Console.
Alternatively, OracleServiceWATn is the service used to stop the
database. During a server reboot, the database will shutdown and
start automatically via the service.





Shutting down the Empower Database

You may need to shut down the Empower database for various
reasons, such as before performing a backup of the entire server
or before performing server maintenance. Before shutting down
the database, you might want to use System Monitor to confirm
that no users are currently connected to the database. To start
System Monitor, log in to Empower and select View > System
Monitor from the Configuration Manager window.
To manually shut down the Empower database:
1. Log in to the Database Control console as the Oracle sys user with
SYSDBA privileges.
2. Click Shutdown.

To shutdown the database two types of credential have to be

provided:
The OS credential (a user part of the Ora_dba group in windows)
An oracle sysdba Account.



To startup the database two types of credential have to be provided:

The OS credential (a user part of the Ora_dba group in windows)
An oracle sysdba Account.





Tablespace Status
Check that all the tablespace status is Online


Check the datafile status

The datafile status must be online except the System datafiles
are always SYSTEM.
Note: Status RECOVER means the datafile has to be

recovered.





Memory allocation
When you add memory on your server you should also change the
memory allocation in Oracle.
Oracle only uses the memory it is assigned.

Memory allocation
The SGA and PGA memory size has to be increased.

Server Backup
& Disaster Recovery

Server Backup
& Disaster Recovery

Server Backup
& Disaster Recovery

Server Backup
& Disaster Recovery

Server Backup
& Disaster Recovery

Server Backup
& Disaster Recovery
Common Causes For System Failure

Heres a chart based on data from Kroll Ontrack Data
International which can be found at:
www.krollontrackdata.com

Server Backup
& Disaster Recovery
Common Causes For System Failure

This chart, based on the same data from Kroll Ontrack
indicates that:
44% of failures are caused by hardware or system
malfunction.
3% is attributed to natural disaster such as flood or
earthquake.
7% is attributed to computer viruses although that
number may be higher when considering Exchange
environments with the recent rash of computer viruses
such as the Melissa virus.
14% is software corruption or program malfunction and
possibly
32% is human error, the most interesting statistic.

Server Backup
& Disaster Recovery

Server Backup
& Disaster Recovery
Disaster Recovery Planning

A Disaster Recovery Plan consists of the following activities:
Assess Hazards and Vulnerabilities
Determine Mitigation Strategies
Develop Planning Documents
Conduct Training and Exercises
Evaluate/Improve

Server Backup
& Disaster Recovery

Server Backup
& Disaster Recovery
Identifying Roles and Responsibilities

Clearly identify roles and responsibilities. Who will be responsible
for what? Who will reinstall the OS? Who can handle network
problems? Who can turn off the overhead sprinklers if they were to go
off? Who can open the door if the electronic lock doesnt accept your
password? Who will contact the help desk to keep them informed?
Whos on call at some remote site, possibly in another country?
The call list will be essential to your survival when you need to get in
contact with someone. Your call list should include not only people on
your team, but also people such as the maintenance or custodial staff,
security, or perhaps even people that dont work for your organization
directly such as police or the local fire department. These people might
have things such as master keys, knowledge about the electrical
systems, or anything that you take for granted. Does your machine
room have a punch combination lock on it? Do you know how to get in
the door when your combination doesnt work? If you needed to get
access to your off-site tapes, do you know how to do that at 2am?
The contact procedures are merely an agreed-upon protocol on how
to spread the word when something goes wrong. How long after
receiving an alarm does operations wait before they contact the person
on call? If that person doesnt reply, how long do they wait before they
call the backup person? When someone on the team replies to a pager
notification, do they call Operations to let them know that they can
dismiss the alarm going off? This communication procedure is
important. Without it we can get into trouble.

Server Backup
& Disaster Recovery

Server Backup
& Disaster Recovery

Server Backup
& Disaster Recovery
Backups
To protect Empower data, Waters recommends that you perform:
A cold backup of the database and Empower raw data files at
least once a week.
A hot backup of the database and the Empower raw data files at
least once a day.
The frequency of your backups should be based on the relative
importance of your data. If your users are working with critical
data, you may want to back up your files more than once a day, or
back up individual projects using the Empower software backup
tools.
Oracle provides various methods for backing up and restoring a
database, or for running scripts to back up and restore files (such
as incremental backups). You may want to use your own backup
variation.

Server Backup
& Disaster Recovery

Backing Up the Oracle Database Server Backup
& Disaster Recovery
Be careful with the oracle home , two oracle home exist

1. one for 32 bit client
2. one for 64 bit for database.

Server Backup
& Disaster Recovery
When lot of rawdata are present on the server the time to copy
them mat increase significantly the backup process time.
The copy of the rawdata as to be perform twice. One for the
temporary location then one on the external storage.
To save time we can only copy them to the final storage.
Important:
1. Copy the database to external storage
2. Copy the Rawdata to external storage
Note: You will have more rawdata than Channel entries in DB. In
case of restore additional rawdata have to be eliminated.

Server Backup
& Disaster Recovery

Backing Up the Oracle Database Server Backup
& Disaster Recovery

Server Backup
& Disaster Recovery

Server Backup
& Disaster Recovery
What to Backup
It is good to backup all Empower Files.
The System Files and Registry backup is optional.
As we know, however, the more backups we have, the better
prepared we are for any kind of disaster.
This is a balance that must be struck given the business
needs of your organization.

Server Backup
& Disaster Recovery

Server Backup
& Disaster Recovery
System Change Numbers (SCN numbers)

System change numbers are used in the following:
Transaction tables
Block headers
Control files
Data file headers
Redo logs
They tell Oracle the status of the database.
A number is assigned to a transaction and when a log
switch occurs, Oracle records the highest SCN in each
redo log as it is archived.

Server Backup
& Disaster Recovery

Server Backup
& Disaster Recovery

Server Backup
& Disaster Recovery

Server Backup
& Disaster Recovery
Complete Recovery from Backups

Complete recovery using a hot backup requires a current
copy of the online redo logs and control files from the time of
the database failure. Since redo logs are mirrored, a copy of
the online redo log is available in the event of a database
drive failure.

Server Backup
& Disaster Recovery

Technology
It has come to our attention that many of our customers and their IT organizations have
requested information on the internal licensing structures of our Data products. This
document discusses the Oracle licensing rules as they are applied internally to our Family
of software products that contain an Embedded Oracle database. These include our CDS
Chromatography products, Scientific Document Management System with Vision
Publisher ( SDMS 7.1 w/ VP) and our Analytical Workflow (AWM) product line.
Oracle offers several licensing models and Waters as a Certified Advantage

Technology Partner (CAP) has chosen the Embedded (ESL) Named User Plus
(NUP) model for all of their applications that contain Oracle Intellectual Property.
As a component of the Waters / Oracle distribution agreement, an Oracle sub-
license is required to be a component of each Waters Laboratory Informatics Suite
Application sale regardless of whether or not the end-user is currently covered
under a Oracle license which was obtained from Oracle or an alternate third party.
The Waters Data products that contain an Embedded Oracle database and are
licensed as such and from this point forward they will be called out collectively as
the Waters Laboratory Informatics Suite (WLIS)
Waters Laboratory Informatics Suite and Oracle

The family that makes up the WLIS applications contains an Oracle database, this
component of the application is licensed from Oracle Corporation. One of the terms of
the contract that Waters has with Oracle restricts Waters from selling their data products
without the Oracle license being included. This license was designed specifically for
Waters customers that wish to utilize a product that basically maintains itself and has a
known structural configuration, which can assist in their qualification and validation
efforts thus basically making the Oracle engine invisible to the customer.
This program allows Waters to offer customers a turnkey solution where the Oracle
technology is fully integrated into the application or device. Now Waters is able offer
customers the award-winning Oracle enterprise technology without them needing
additional IT resources to manage it. Oracle considers all of the Embedded Licensed
Applications to be designed such that the database is truly embedded into the application
and the customer or end user has little or no knowledge that the Oracle database exists in
the application. Waters does not grant or sell an Oracle license to its customers rather
Waters grants to users of the WLIS the use of its Oracle license under a sub-license
distribution agreement with Oracle (Waters / Oracle distribution agreement)
Business Rules applied to the Waters Embedded Oracle

License
The Oracle license that Waters distributes comes to Waters with a given set of business
rules applied to it. The Waters WLIS Application must by contract conform to these rules
and they are passed on to our customers as a component of the Waters terms and
conditions of sale. Below find a subset of the business rules that apply to this license:
and the WLIS family of applications.
Packaging / Media Kit
The Oracle components of each of the WLIS Applications must be packaged as

an integrated component on the WLIS application program's product media set.
The Oracle Universal Installer ("OUI") must be packaged as an independent of
the programs. When loading the software, the application software launches the
OUI in silent mode and then the customer must then be instructed to retrieve the
additional program software from another source.
(In the case of SDMS 7.1 there is a set of DVDs with all programs and an
additional Companion media as requirements demand)
Customers are not permitted to install Oracle component programs separately and
or independently from the WLIS Applications installation package
Installation
The Oracle components of the WLIS Applications must be installed and
configured as an integrated component by the WLIS Applications installation
routine. The customer is not permitted to configure the Oracle components
outside the WLIS Applications installation process. This includes but is not
limited to Patch Sets, Critical Patch Utilities or Security Alerts
The WLIS Application program is required to and does provide preconfigured
instance size configurations via Oracle template technology and the database
creation assistant. This is to minimize the initial program configuration and
ongoing program management.
Access
The customer is not permitted to access the Oracle components directly but rather
only through the WLIS Applications program. External access through
SQLPLUS or the connect statement is prohibited by this license.
The WLIS Applications have been designed and developed by Waters to
eliminate program administration tasks by the customer. This is done by enabling
centralized and remote administration through the Oracle Enterprise Management
utility (Grid Control) and by including built in program administration functions.
All administration scripts including startup, shutdown, and backup must be and
are provided by Waters and reside within the application program.
The customer has not been granted the right to navigate the underlying data
schema as Waters provides predefined data views within the application that
buffer the customer from the underlying data schema and SQL statements.
Accessing of information on an ad hoc basis is not permitted under this license.
If the WLIS Applications must interface with another application or external
database, the customer is not permitted to access any of the WLIS databases to
establish the transfer of data. One of the Waters WLIS Applications Tool Kit
which is a predefined APIs (Tool Kit) must be used to transfer data via the
application package. Management of the data transfer must be done through the
WLIS Applications and Tool Kit interface.
The customer may not use Oracle or third party tools or utilities that are not
supplied by Waters Corporation as part of the WLIS Application package to
access the Oracle programs or component structures. This includes third party
backup programs that have Oracle Agents. No license is granted for access to the
Oracle engine by WLIS Applications license; only tools supplied with the WLIS
Applications distribution may access the database or Oracle components.
Support / Services
Program updates (Oracle Patch Sets, Critical Patch Updates or Security Alerts)
must be certified and distributed as a component of the WLIS Applications
package. Media containing updates obtained from other sources including Oracle
may not be deployed under this license
The customer is not licensed to upgrade the database or other Oracle program
technology versions separately from the WLIS Applications media distribution set
or Waters WLIS Applications updates.
Waters is required to provide all customer service and education for all program
operations to the end user. There is no option for the customer to obtain Oracle
support (CSI Numbers) for the programs supplied by the WLIS Applications.
Only Waters Employees can access the Oracle programs directly for purposes of
technical assistance to the customer or end user and such access is limited to
providing technical assistance, including troubleshooting, problem resolution, and
support assistance. Waters is prohibited from providing remote or onsite program
administration tasks on behalf of the end user that are otherwise prohibited under
the terms of this agreement.
Additional Software License Practices

Waters is responsible for duplicating, manufacturing, and shipping all media and
documentation to the end-user. Waters bears all costs related to the above
responsibilities. The customer is not eligible to obtain Oracle Media or
Documentation from Oracle in conjunction with this license.
When Waters distributes the WLIS applications, under the ESL Waters business
rules supersede the current Oracle business practices. Should the ESL be
determined to be invalid for a particular deployment then the current Oracle
Price List must be used as the basis for determining user minimums which would
apply.
The Oracle Software Licenses which are a component of the WLIS Applications
are not upgradable to Oracle Full Use or Application Specific Full Use Licenses
nor are they eligible to be migrated to other licensing metrics or able to be used by
other applications.
The Oracle software components distributed with the Waters CDS package may
only be used in conjunction with the application that they were distributed with..
The Oracle programs supplied with WLIS Applications may not be used to add
any additional functionality or for the installation of any additional application
modules not included in the module list which defines the distribution agreement
with Oracle.
Alternative Licensing Schemas

If these conditions are determined not to be in compliance with the customers business
practices, or the customers business practices require additional Oracle Intellectual
Property or a customized deployment, an alternative licensing option is available. Waters
will on request supply a separate Oracle full use license and media distribution, including
an Oracle support contract either from Waters Corporation or directly from Oracle.
If the customer currently has a supported full use license that they would like to apply to
this applications operating environment, this would also address any business practices
compliance issues. This option allows the customer to apply almost any business rule or
to include any additional Oracle or third party maintenance / monitoring application that
they may wish to employ. This includes any additional Oracle product, application, tool
or feature that they may wish to license and deploy.
When employing this alternative licensing schema, the Waters Embedded Oracle License
becomes invalid and the ESL listed business rules no longer apply. Instead the Oracle
Standard License Agreement (OSLA) rules and Oracle licensing practices apply
Contact your Waters Network Data Sales specialist to get information on this option. It
should be noted that:
WLIS Application named user license are Application entitlements and the Oracle
named user licenses will have to be obtained separately.
A WLIS Applications Named User license is a license for access to the
application not to the database.
The Oracle license which is an embedded component of the WLIS Applications
Product offering is only valid when used in conjunction with the WLIS
Application Embedded Oracle license.
The possibility exists that in installing a custom Oracle operating environment,
additional qualification testing may be required. Consult Waters or your
corporate validation group for details.
Appendix A Push Directories Files Structures
\\MyServer\Empower3DVD
(Contains the copy of the Empower3 software

DVD )
\\MyServer\EMPOWER3ICOP
(Contains the copy of the Empower3 ICOP)
\\MyServer\PUSHFOLDER
(Contains response file, scripts, tnsname.ora)
Rev. 29011 Page 1 of 1

Appendix B Files Interaction & Dependencies
Run_ME_PushInstallEmpower3.bat
Psexec.exe Node_list.txt InstallEmpower3.bat
Setup.exe (From Empower3DVD) E3_Response.config
Oracle11g_Client_x32 Path
Log Path
Run_ME_PushTnsname.bat Psexec.exe Node_list.txt Tnsname.ora
Run_ME_PushInstallICOP.bat
Psexec.exe Node_list.txt InstallICOP.bat
Setup.exe (From ICOP DVD) ICS_Response_EN.rsp
ICS_List_EN.txt
WORKING_DIRECTORY Path
Log Path

Setup the WatersEmailService
in EMPOWER3
Empower3 provides connection to a standard email box to warn and
inform the user of messages from Empower. The process which
manages this function is the WatersEmailService.
The Email service scans the Message center periodically to identify if
messages have to be sent to email.
The setup of email function is divided in 3 steps:

- Service Creation
- Setup Email service database
- Setup Empower
2 Send existing message
1 Check every X minutes

1. Create the WatersEmailService
The service has to be created on only one machine (you can use
a LAC/E if you want)
a. From the command prompt type type:
i. X:\Empower\Bin\WatersEmailService.exe service
Where x is the drive where you install Empower.
b. Verify the service is registered in the windows services
c. Right click on the service

d. Click properties

1. Setup the startup type to Automatic
2. Press OK
3. Press Start to start the service

2. Set the database for WatersEmailService
a. On the empower\bin folder double click on the file

SetEmailDatabase
The following screen will be display
You can setup the database you want to scan for messages to
send by email, how often to check for email, and optionally you
can protect the windows to avoid change.

3. Set Empower email functionality
In the email policies you can setup the type of message

a. Enter the SMTP server name, Default From Name and
server port number used.
b. If your server requires authentication enter the name and
password.
c. Restart the WatersEmailService

Appendix C Node_list.Txt
Lace01
Lace02
Lace03
Client01
Client02
Client03
Client04

Appendix D ICS_List_EN.TXT
*Agilent LC Control Software

*Waters A6850
*Waters A7890 Software
*ACQUITY Binary Solvent Manager
ACQUITY Column Manager
*ACQUITY UPLC Columns Calculator
*Waters ELS Detector
*ACQUITY FLR Detector
*ACQUITY Sample Manager FTN
*ACQUITY PDA Detector
*ACQUITY Quaternary Solvent Manager
ACQUITY Sample Manager
*Waters SQ Detector
*Waters TQ Detector
*Waters 3100 Mass Detector
*ACQUITY TUV Detector
Waters EMD1000 Software
*Waters 2420 Software
*Waters 2489
*Waters 25X5 Quaternary Gradient Module
*Waters 2707 Autosampler
*Waters 2998 PDA Detector
*Waters ZQ2000 Software
*Waters ZQ4000 Software
*is used to remark (not install a icop)

Appendix E E3_Response.config
<?xml version="1.0" encoding="utf-8" ?>
<Configuration>
<Properties>


<USERNAME>waters</USERNAME>


<ORGANIZATION>waters</ORGANIZATION>


<PIDKEY>xxxxxxxxxx</PIDKEY>


<AGREETOLICENSE>Yes</AGREETOLICENSE>


<ORACLE_MEDIA>\\Myshare\EMPOWER3DVD\Oracle11g_Client_x32</ORACLE_MEDIA>

<INSTALL_TYPE>LACE32</INSTALL_TYPE>

<USE_TNS>false</USE_TNS>

<TNS_ADMIN_PROPERTY></TNS_ADMIN_PROPERTY>


<LANGID>English</LANGID>


<EMPOWER_APP_DIR>C:\</EMPOWER_APP_DIR>


<ORACLE_CLIENT_DIR>C:\</ORACLE_CLIENT_DIR>



<LOG_FILE_NETWORK_LOCATION>\\Myshare\Push\log</LOG_FILE_NETWORK_LOCATI
ON>
</Properties>
<CommandLine>

<ACTION>Install</ACTION>

<SkipRequirements>TRUE</SkipRequirements>

Appendix E E3_Response.config

<RESTART>TRUE</RESTART>
</CommandLine>
<Product>
</Product>
</Configuration>

Appendix F ICS_Response_EN.rsp
<?xml version="1.0" encoding="utf-8" ?>

<Configuration>

<ACTION>InstallAll</ACTION>



<LANGUAGE>English</LANGUAGE>


<ICS_LIST>\\MYSHARE\PUSH\ICS_List_EN.txt</ICS_LIST>

<LOG_FILE_NETWORK_LOCATION>\\MYSHARE\Push\log</LOG_FILE_N
ETWORK_LOCATION>



<MS_DETECTOR>Detector</MS_DETECTOR>

<RESTART>TRUE</RESTART>


<WORKING_DIRECTORY>\\MYSHARE\EMPOWER3ICOP
</WORKING_DIRECTORY>
</Configuration>

Appendix G Run_ME_PushTnsname.bat
Rem_____________________________________________________________________
Rem
Rem Name:Run_ME_PushTnsname.bat
Rem Version: 1.0.001
Rem Last modified: 01/06/2011
Rem Author: Gilles BASSARD Waters
Rem
Rem Script Requirement:
Rem PSexec.exe http://technet.microsoft.com/en-us/sysinternals/bb897553
Rem Node_List.txt
Rem Tnsname.ora
Rem_____________________________________________________________________
Rem
Rem - To simplify the usage of the scrip variable will be used

Rem - Replace location by your own location
Rem - the user that execute the script with available credential
Rem - must have admin rights on target machine
Set UserName=vdom\Training
Set UserPWD=password
Rem - location of the Node_List.txt file that contain the machine list to install
Set ComputerListpath=\\Myshare\Push
Rem - location of the TNSNAME.ORA file

Set TNSNAMEfilepath =\\myshare\Push
Rem the following line copy the tnsname.ora

Rem for helping debugging you can replace -d by -i and log in the taget computer with the
user and password.
psexec @%ComputerListpath%\Node_List.txt -d -h -u %username% -p %userpwd%
cmd /c copy /y \\%TNSNAMEfilepath%\tnsname.ora
C:\Empower\Oracle\Oracle11gClient\network\admin

Appendix H Run_ME_PushInstallEmpower3.bat
Rem ___________________________________________________________________________________
Rem
Rem Name: Run_ME_PushInstallEmpower3.bat
Rem
Rem PSexec.exe http://technet.microsoft.com/en-us/sysinternals/bb897553
Rem E3_Response.config
Rem Node_List.txt
Rem InstallEmpower3.bat
Rem ___________________________________________________________________________________
Rem

Rem - location of the empower3 dvd

set Empower3DVDpath=\\Myshare\EMPOWER3DVD
Set UserName=VDOM\training
Rem - location of the Response file for installation

Set E3Respfilepath=\\Myshare\Push
Rem - location of the push directory

Set pushfolder=\\Myshare\Push
Rem - display variables

@echo list of variable
@echo ----------------
@echo Empower3DVDpath=%Empower3DVDpath%
@echo E3Respfilepath=%E3Respfilepath%
@echo UserName=%UserName%
@echo UserPWD=%UserPWD%
@echo ComputerListpath=%ComputerListpath%
@echo pushfolder=%pushfolder%
Rem the following line install the empower3

Rem for helping debugging you can replace -d by -i and log in the taget computer with the user and password.
psexec @%ComputerListpath%\Node_List.txt -d -h -u %username% -p %userpwd% -c -f
"InstallEmpower3.bat" %Empower3DVDpath% %E3Respfilepath%
Rem Remove the Rem in next line to help you for troubleshooting
Rem Pause

Appendix I InstallEmpower3.Bat
Rem
________________________________________________________________________________________
Rem
Rem Name:InstallEmpower3.Bat
Rem
Rem E3_Response.config
Rem Setup.exe from empower3dvd
Rem
Rem
________________________________________________________________________________________
Rem

Rem The variables are passed to the batch

Rem
Rem %1 Empower3DVDpath
Rem %2 E3Respfilepath
rem - location of the empower3 dvd

set Empower3DVDpath=%1
rem - location of the Node_List.txt file that contain the machine list to install
rem - location of the Response file for installation

Set E3Respfilepath=%2
Rem For terminal server change the ts mode to installation

Change user /install
Rem the following line installs the empower3

%Empower3DVDpath%\setup.exe /responseFile %E3Respfilepath%\E3_Response.config
rem remove the rem in next line to help you for troubleshooting
rem Pause

Appendix J Run_ME_PushInstallICOP.bat
Rem
_______________________________________________________________
Rem
Rem Name:Run_ME_PushInstallICOP.bat
Rem
Rem Script RequiRement:
Rem PSexec.exe http://technet.microsoft.com/en-
us/sysinternals/bb897553
Rem ICS_Reponse_EN.RSP Template located in Empower3
DVD in the push folder
Rem Node_List.txt
Rem InstallICOP.bat script to execute the installation
Rem
Rem
_______________________________________________________________
Rem

Rem - location of the empower3 dvd

set ICOPpath=\\Myshare\EMPOWER3ICOP
Set UserName=VDOM\training

Set ICOPRespfilepath=\\Myshare\Push

Appendix J Run_ME_PushInstallICOP.bat
Rem - location of the push directory

Set pushfolder=\\Myshare\Push
Rem - display variable

@echo list of variable
@echo ----------------
@echo ICOPpath=%ICOPpath%
@echo UserName=%UserName%
@echo UserPWD=%UserPWD%
@echo ComputerListpath=%ComputerListpath%
@echo pushfolder=%pushfolder%
Rem the following line installs the empower3 ICOPs

Rem for helping debugging you can replace -d by -i and log in the target
computer with the user and password.
psexec @%ComputerListpath%\Node_List.txt -d -h -u %username% -p
%userpwd% cmd /c %pushfolder%\script\InstallICOP.bat %ICOPpath%
%pushfolder%
Rem Pause

Appendix K InstallICOP.bat
Rem
_________________________________________________________________________
Rem
Rem Name:InstallICOP.bat
Rem
Rem Script RequiRement:
Rem ICS_Response_EN.rsp
Rem Setup.exe from ICOP media
Rem
_________________________________________________________________________
Rem

Rem
Rem The variable are pass to the batch
Rem
Rem %1 ICOPpath
Rem %2 ICOPRespfilepath
Rem - location of ICOPs media

set ICOPpath=%1

Set ICOPRespfilepath=%2
Rem For terminal server change the ts mode to installation

Change user /install
Rem the following line install the empower3

%ICOPpath%\setup.exe /responseFile %ICOPRespfilepath%\ICS_Response_EN.rsp
Rem Pause

Exercises for Empower 3 Enterprise
System Administration
Lab 1: Installing an Empower Client
Estimated time to complete this lab: 30 minutes
Exercise 1 Installing Empower on the Client

In this exercise you will install Empower on the client.
1. To install Empower on the client, you will use a shared folder containing the Empower 3 DVD.
2. Map a drive or connect to the share: Training2\Empower3DVD
3. Find the correct directory for Empower Software installation.
4. Select the set-up file and the software installation will begin.
5. Select English in the Choose Setup Language page and select OK.
6. Click on the button Install Empower software.
7. Under the which product do you want to install? choose Enterprise. Then choose NEXT
8. Unser which installation do you want to perform? Choose Client. Then choose NEXT
3. In the Customer Information page, enter ClientX as the User name where X is your Client
Number. Enter Waters as the organization. Enter xxxxxxxxxx as the Serial Number.
4. In the License Agreement page, read the agreement, select I accept the license agreement,
then, click NEXT.
5. In the installation options page, select No to use TNS_ADMIN environmental variable, then,
click NEXT.
6. In the Setup Type page, select Typical as the installation type.
7. Click Install in the ready to install the Program page.
8. Click Finish once the installation is complete. Select Yes to restart the computer.
Exercise 2 Configuring the Database Service Name

In this exercise you will copy the tnsnames.ora file from a shared folder.
1. The TNSnames.ora file is located on the same share as the Empower DVD
2. Locate the file and chose copy.
3. In the client, explore to the directory c:\Empower\Oracle\Oracle11client\network\Admin
4. Copy the tnsnames.ora file to this location.
Exercise 3 Install Service Release

In this exercise you will install any service Release files.
1. From the same Shared Empower DVD folder, locate the set-up file for Service Release 1.
2. Double click on the file to start the installation.
3. Follow the directions to install.
Rev. 03509 Page 1 12/21/2011
4. When complete, you are ready to install the ICOPs. (drivers for instrument control)
Exercise 4 Installation of ICOPs (drivers for Instrument control)

In this exercise you will install drivers for control of instruments.
1. From the same Shared Empower DVD folder, locate the set-up file for ICOP installation.
2. Double click on the file to start the installation.
3. Follow the directions to install.
4. For this exercise select all the instruments. For a real installation, select any instruments you
want to control. In typical environment, all clients on the network need to have the same ICOPs
installed.
Exercise 5 Run Verify Files

In this exercise you will confirm the installation of Empower 3 was performed without errors.
1. From the Windows START menu, under programs\Empower, locate verify files.
2. Click on verify files and the script will run.
3. When complete, a file should appear on the screen. If not, go to Programs\Empower, View
Verify Files.
Exercise 6 Confirm Installation on the Client

In this exercise you will confirm the installation of Empower 3 by bringing a channel to Review.
1. Log in to Empower 3.
2. Identify the corresponding Time Zone.
3. Open a project (use Default_FAT)
4. Select a channel, right-click and select Review.
5. Make sure the channel has 2D Channel table information and a chromatogram in the view.
Rev. 03509 Page 2 12/21/2011

Lab 2: Administrating Empower 2
Exercise 1 Setting up system policies, users, user types, user groups, projects and
systems.
In this exercise you will learn how to plan on how to set-up system policies, users, user types, user
groups, projects and systems. You will perform this exercise on the client. The alternative is to have a
discussion on your company set-up.
Case Study: A local pharmaceutical company has purchased Empower 2 Enterprise

to be used by its major departments QC and R&D Department. Only one Empower
server will be used as a centralized chromatography data management system.
QC Department:
Manufacture generic drugs for regional market, but preparing for meeting US regulatory
compliance requirements. Need to meet GXP compliance.
Currently manufacturing 3 major products: Cabbage, Carrot, and Celery
Customers want to manage results from each drug separately
Customers want to keep each months analysis separately, so they can lock and review as needed
by auditors
QC Department has a total of 4 people:
o Linda QC Department Manager
o Karen Senior Chemist
o Duffy Chemist
o Micky Analyst
Linda wants only the chemists create projects, but only senior chemist can backup projects
She also does not want anyone to be able to delete any data, except herself
Linda wants to manage all administrative work for her group
Instead of paper signature, Linda wants to use Empowers electronic signature capabilities
o Karen as the first level review
o Linda as the second level review
Customer has 2 HPLCs. Customer want the HPLCs to be used only by each group. (set systems
offline)
o 2695/2487
o 2695/2996
R&D Department:
Responsible for method transfer and method development
Compliance not important
Currently studying 2 products: Orange and Apple
Customers want to manage results from each drug separately
Responsible for method transfer and method development
R& D department is managed by Kenneth
He has two staff: George and Amanda
He wants them to able to change methods and delete data since they dont need to meet any
regulatory compliance
Customer has 2 HPLCs. Customer want the HPLCs to be used only by each group. (set systems
offline)
Rev. 03509 Page 3 12/21/2011
o 2695/2996
o Non Waters Instrument using the SAT/IN A to D converter
QA Department:
Policies are based on QC Department
Robert is the QA manager
He does not perform any laboratory work, but wants to be able to access any results from both
R&D and QC lab
1. Based on the customer feedback, set system policies based on their products and requirements.
Which set-up of system policies would prevail QC or R&D? ____________________
Can you apply both sets of system policies? ____________________________________
2. Based on the customer feedback, create user types, users, and user groups to meet their
requirements.
1. Based on the customer feedback, create projects based on their products and requirements.
2. Based on the customer feedback, create dummy instruments with appropriate security. If no
dummy instruments are available, use Create new system wizard. Select No to the first question
(creating serial instruments) and select Yes on the second question (if no instruments are
available, do you want to create demo instruments?). Proceed with the wizard by selecting
appropriate instruments as part of the system being created.
Rev. 03509 Page 4 12/21/2011

Lab 3: Oracle
Exercise 1 Using the Oracle Management Console

In this exercise you will be using the Oracle Management Console.
1.. Open Internet Explorer and use the following URL to access the web console.
https://app1:1158/em
2. Log on as system account with the normal role using the password Empower
3. Navigate to the Home page.
What is your instance name? _________________________________________
What is your listener name? __________________________________________
What is your host name? ____________________________________________
4. Navigate to the appropriate page. Select Datafiles under Storage.
5. Select each datafile and select view to view its properties.
6. Fill the following table.
Datafile name Status File Size Increment Maximum

Size Size
_________ __________ __________ ___________
_____________ _________ __________ __________ ___________
_____________ _________ __________ __________ ___________
_____________ _________ __________ __________ ___________
_____________ _________ __________ __________ ___________
_____________ _________ __________ __________ ___________
_____________ _________ __________ __________ ___________
_____________ _________ __________ __________ ___________
7. Identify the sequence number of the last archive log either through the console window or through
windows explorer.
________________________________________________________________________________
Rev. 03509 Page 5 12/21/2011

8. Open Windows Explorer and navigate to the Database Drive.
E:\EmpowerDatabase\Oradata\WAT10\*.*
Identify the size in windows explorer for each of the files:
Datafile name Size

(Units: ______)
______________ ____________
______________ ____________
______________ ____________
______________ ____________
______________ ____________
______________ ____________
______________ ____________
Rev. 03509 Page 6 12/21/2011

2011 Waters Corporation. Printed in the U.S.A. XXXXXXXXXX Rev.X

Empower 3 Software Enterprise e PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Empower 3 Software Enterprise e PDF

Uploaded by

Copyright:

Available Formats

Empower 3 Software Enterprise

System Administration and Maintenance

2011 WATERS CORPORATION. PRINTED IN THE UNITED STATES OF

Waters Corporation Registered Trademarks - symbolized by .

Waters Corporation Unregistered Trademarks - symbolized by .

Other trademarks or registered trademarks are the sole property of their

Page 2 of 2 Rev. 27011

1. Chapter 1 Enterprise Architecture

2. Chapter 2 Enterprise Installation (server)

3. Chapter 3 Node Installation

4. Chapter 4 Push Installation Automation

5. Chapter 5 Administrative and Management Tools

6. Chapter 6 Node and System Management

7. Chapter 7 User Management

8. Chapter 8 Project Management

9. Chapter 9 Operational Mechanisms

10. Chapter 10 Introduction to Oracle 11g

11. Chapter 11 Database Management using Web Console

12. Chapter 12 Server Backup Disaster Recovery

Rev. 30011 Chapter 1: Page 1 of 37

Rev. 30011 Chapter 1: Page 2 of 37

Typical Empower Network

Rev. 30011 Chapter 1: Page 3 of 37

Empower Network Scalability

Rev. 30011 Chapter 1: Page 4 of 37

Parts of the Empower Enterprise Architecture

Note: The following slides use the following conventions, namely, A,

Rev. 30011 Chapter 1: Page 5 of 37

The flexible architecture allows instruments to be connected to the

Rev. 30011 Chapter 1: Page 6 of 37

There are two advantages of this architecture: reduce software validation

Rev. 30011 Chapter 1: Page 7 of 37

Rev. 30011 Chapter 1: Page 8 of 37

An Oracle RAC database is a clustered database. A cluster is a group of

Rev. 30011 Chapter 1: Page 9 of 37

Rev. 30011 Chapter 1: Page 11 of 37

Rev. 30011 Chapter 1: Page 12 of 37

Rev. 30011 Chapter 1: Page 13 of 37

Rev. 30011 Chapter 1: Page 14 of 37

Rev. 30011 Chapter 1: Page 15 of 37

Rev. 30011 Chapter 1: Page 16 of 37

Rev. 30011 Chapter 1: Page 17 of 37

A hosted approach provides partitioning services on top of a

Rev. 30011 Chapter 1: Page 18 of 37

Rev. 30011 Chapter 1: Page 19 of 37

Rev. 30011 Chapter 1: Page 20 of 37

Probably more important than controlling the multitude of

Rev. 30011 Chapter 1: Page 21 of 37

Manages all dissolution result calculations eliminates transfer

Rev. 30011 Chapter 1: Page 22 of 37

Before: Time consuming, repetitive tasks consisting of several

Rev. 30011 Chapter 1: Page 23 of 37

MVM automatically manages and documents the method

Rev. 30011 Chapter 1: Page 24 of 37

The software determines if your results are out of

Rev. 30011 Chapter 1: Page 25 of 37

The Empower Softwares integrated Chemical Structures improves

Rev. 30011 Chapter 1: Page 26 of 37

If we look at how method development is traditionally done in labs.

Rev. 30011 Chapter 1: Page 27 of 37

Support for Fusion Method Development software (version 9.6) for

Fusions robustness simulator will exclude the settings that do not

Rev. 30011 Chapter 1: Page 28 of 37