SampleManager Installation Guide
SampleManager Installation Guide
Installation Guide
Version 12.2
© 2019 Thermo Fisher Scientific Inc. All rights reserved.
Thermo Fisher Scientific Inc. provides this document to its customers with a product purchase to use in
the product operation. This document is copyright protected and any reproduction of the whole or any
part of this document is strictly prohibited, except with the written authorization of Thermo Fisher
Scientific Inc.
The contents of this document are subject to change without notice. All technical information in this
document is for reference purposes only. System configurations and specifications in this document
supersede all previous information received by the purchaser.
Thermo Fisher Scientific Inc. makes no representations that this document is complete, accurate, or
error-free and assumes no responsibility and will not be liable for any errors, omissions, damage, or
loss that might result from any use of this document, even if the information in the document is
followed properly.
This document is not part of any sales contract between Thermo Fisher Scientific Inc. and a purchaser.
This document shall in no way govern or modify any Terms and Conditions of Sale, which Terms and
Conditions of Sale shall govern all conflicting information between the two documents.
Contents
Preface ...................................................................................................................... ix
Related Documentation ................................................................................. ix
Special Notices................................................................................................ x
Contacting Us................................................................................................. x
Preface
Thermo Scientific™ SampleManager LIMS™ software can plan, manage, and maintain an
accurate record of work performed in a laboratory environment. The SampleManager
LIMS software incorporates Laboratory Information Management (LIMS), Data
Management (SDMS), and Process Execution and Procedural Electronic Lab Notebook
(LES) capabilities in a single solution.
Contents
• Related Documentation
• Special Notices
• Contacting Us
Related Documentation
SampleManager includes Help, manuals, and guides as PDF files.
With the SampleManager client running, you can access Help in the following ways:
• Press the F1 key.
• From the main menu bar at the top of the SampleManager window, choose Help
and then click Contents.
• Click a Help button.
Special Notices
Make sure that you follow the precautionary statements presented in this guide. The
special notices appear in boxes.
Contacting Us
There are several ways to contact Thermo Fisher Scientific for the information you need.
Email [email protected]
Web https://support.thermoinformatics.com/contacts
Introduction
This manual describes how to install and configure SampleManager, including:
• Introduction (this chapter) – SampleManager architecture, deployment, and general
information.
• Installing SampleManager Server for an Oracle Database (page 19) – How to set up
the server software and create a SampleManager server instance that uses an Oracle
database.
• Installing SampleManager Server for a SQL Server Database (page 59) – How to set
up the server software and create a SampleManager server instance that uses a SQL
Server database.
• Post-Installation Tasks (page 97) – How to install licenses and perform the initial
configuration of your SampleManager system.
• Installing SampleManager Client (page 115) – How to install the client software, set
up a connection to the server instance, and add licenses.
• Upgrading SampleManager (page 129) – How to upgrade the server and client.
• Installing LIMS Reporter (page 157) – How to install the reporting software and
configure it for your database.
• Installing Chromeleon Link Components (page 173) – How to install the
components that connect your SampleManager LIMS system to a Thermo Scientific
Dionex Chromeleon Chromatography Data System.
• Installing Data Manager Components (page 185) – How to install the components
that let your SampleManager LIMS system store, retrieve and view data created by
external applications, such as instrument control software.
• Oracle Setup (page 223) – An outline of how to set up Oracle Server and Oracle Net
Client for SampleManager.
• SQL Server Setup (page 233) – An outline of how to set up SQL Server for
SampleManager.
Contents
• Architecture
• Deployment
• System Requirements
• Overall Setup Procedure
Architecture
SampleManager systems use a three-tier architecture. The tiers are:
• Client – SampleManager supports two clients:
– SampleManager LIMS web client can be accessed from any supported web
browser. The web client connects to the SampleManager web server component.
For more information, see the SampleManager Web Client Installation and
Configuration Guide.
• Application server – The application server hosts the SampleManager Server
application and the SampleManager instance that connects to a specific database.
• Database server – The database server hosts the SampleManager database.
Messages that are transmitted between the SampleManager Client and SampleManager
Server are encrypted before they are sent, using unique encryption keys that are generated
for each session. The encryption algorithms and code constructs are FIPS-compliant.
The following diagram shows the architecture of a SampleManager system with a SQL
Server database. Client workstations can connect using both the SampleManager desktop
client and the SampleManager web client. The SampleManager Web Server component
is only required for systems where some clients connect using the SampleManager web
client. The SQL Server Connectivity Components are required when the
SampleManager Server and the database are hosted on separate servers.
Figure 1-1. SampleManager architecture with a SQL Server database
The SampleManager Web Client can be opened in a web browser, such as Google
Chrome. Most of the features of the SampleManager Client are available in the
SampleManager Web Client. For more information, see the SampleManager Web Client
User Guide and SampleManager Web Client Installation and Configuration Guide.
The database server, application server, and SampleManager Web Server can be hosted
on virtual servers in the cloud. SampleManager 12.2 has been validated on virtual
machines hosted by Amazon Web Services (AWS).
A single PC can host multiple tiers. Small systems can use one machine as a database
server, application server, and client PC. Larger systems typically use separate database
and application servers, with many client PCs. For more information, see Deployment
(page 5).
Deployment
SampleManager is designed for deployment as a distributed system, with many possible
configurations of the database, server, and client tiers. This section provides a basic
overview of the following possible configurations:
• Single-tier systems (page 6) suitable for demonstrations or development.
• Two-tier systems (page 7) suitable for testing, training, or other lower-usage
implementations.
• Three-tier systems (page 8) suitable for production systems. Complex three-tier
systems use technology such as high-availability databases and SampleManager
application server clusters to enhance performance and reliability for large
production implementations.
Single-Tier Systems
In a single-tier system, a single machine hosts the database, the SampleManager server,
and the SampleManager client. Single-tier systems are useful for purposes such as
demonstrations, or developing and testing of custom code.
Figure 1-3. Single-tier system
Two-Tier Systems
In a two-tier system, the database and application server are installed on one server, and
users connect to the system from client workstations.
The following example shows a two-tier system that is configured to support both the
SampleManager desktop client and the SampleManager web client.
A two-tier system is easy to set up, but installing the database and application server on
the same server is not optimal for performance. This configuration is best suited for
demonstration, development, or training systems.
Three-Tier Systems
In a three-tier system, the database, SampleManager server, and SampleManager client
are hosted on separate machines. The optional SampleManager web server lets users
connect with the SampleManager web client in a browser, without installing the
SampleManager desktop client on the client workstation.
Figure 1-4. Three-tier system
Large SampleManager systems that require high availability and performance can use
SampleManager application server clusters (page 10) for load balancing and high
availability database configurations to maximize performance and reliability. Each
component of the system can be tuned individually.
SampleManager LIMS does not maintain a central record of the instances that belong to
an application server cluster. For maintenance and upgrade purposes, we recommend
that you keep a record of your application server cluster architecture.
Figure 1-5. Complex three-tier system
SampleManager clients can be installed on a Citrix server farm to permit a high number
of clients and load balancing. The database server and application server can be hosted in
the Cloud to reduce management overheads.
If the lock daemon on the application server is the current cluster manager lock daemon,
the transaction requests and responses for each connected client are handled locally.
Figure 1-7. Handling a lock request from a client connected to the cluster manager
lock daemon
If the lock daemon on the application server is not the cluster manager lock daemon, the
transaction requests and responses for each connected client are passed to the cluster
manager lock daemon.
Figure 1-8. Handling a lock request from a client connected to a local lock daemon
If an application server that is not hosting the cluster manager lock daemon goes down,
the cluster manager lock daemon detects the failure and removes all locks associated with
the local lock daemon on that application server.
If the application server that is hosting the cluster manager lock daemon goes down, the
lock daemons on the remaining application servers reconfigure to continue operations.
The first local lock daemon that detects the failure of the cluster manager lock daemon
writes its connection details to the USER_SETTINGS table, becoming the new cluster
manager. The new cluster manager lock daemon re-establishes the lock transactions it has
handled with the database. The new cluster manager then accepts connections from the
other operational lock daemons in the cluster. Each of the other lock daemons passes its
list of active locks to the new cluster manager, and operations continue as normal.
If the use_cluster value is false, or use_cluster is not present in the Windows registry key,
the lock daemon cluster mechanism is not used.
System Requirements
This section provides a summary of the system requirements for a SampleManager
installation. For detailed information, see the SampleManager LIMS 12.2 Release Notes in
the installation kit.
For information about web browsers and other software supported for this release, see the
SampleManager LIMS 12.2 Release Notes in the installation kit.
Operating System
SampleManager is supported on the following operating systems:
Server
Microsoft Windows Server 2016
Client
Microsoft Windows 7 x64 Professional SP1
Notes Any combination of the server and client operating systems can be used. If the
database is installed on the same machine as the SampleManager server, the database
version must be compatible with the server operating system. For more information,
see the documentation for your chosen database.
Database
SampleManager supports the following database platforms:
• Oracle 12c
• SQL Server 2016 SP1
• SQL Server 2016 SP2
• SQL Server 2017
This section describes the overall setup procedure for the following databases:
• Oracle Database (page 15)
• SQL Server Database (page 16)
See the Installing SampleManager Server for an Oracle Database chapter (page 19).
4. If you want users to connect with the SampleManager web client, install and
configure the SampleManager Web Server.
See the Installing SampleManager Server for a SQL Server Database chapter (page
59).
Set up your client PCs by installing SampleManager client software and configuring
a connection to the SampleManager server instance.
4. If you want users to connect with the SampleManager web client, install and
configure the SampleManager Web Server.
See the SampleManager Web Client Installation and Configuration Guide.
6. If you want to use the Data Manager functionality to store and manage data created
by external applications, install the Data Manager components.
Contents
• Installation Procedure Summary
• Creating a SampleManager Instance
• Removing a SampleManager Instance
3. Make sure that the Oracle Net Listener for your database can connect to the
database.
4. Install and configure the 32-bit Oracle Net Client on the SampleManager Server
machine. See Configuring a Connection from the Oracle NET Client to the Oracle
Server (page 228).
5. Make sure that the Local Net Service Name for the 32-bit Oracle Net Client can
connect to your database through the Oracle Net Listener.
6. Install SampleManager Server (page 23).
If your instance will use the legacy LIMS Reporter tool (page 157) to generate reports,
install an Oracle ODBC driver (page 230) that LIMS Reporter can use to connect to the
database. LIMS Reporter is only available for existing SampleManager systems that have
custom InfoMaker reports.
Pre-Installation Checks
Before installing SampleManager server, perform the following tasks:
1. Make sure that the correct operating system is installed (page 14).
2. Back up your system as appropriate.
3. Make sure that your network is functioning correctly and uses the TCP/IP protocol.
4. Make a note of the full name of the computer on which you are installing
SampleManager server.
5. Make sure that the Microsoft .NET Framework 4.6.2 is installed on the server where
you will install SampleManager Server.
The installer for the required version of the Microsoft .NET Framework is included
in the following folder of the SampleManager installation kit:
..\SampleManager 12.2\Server\Redistributables
6. Make sure that the Microsoft Visual C++ 2017 Redistributable is installed on the
server where you will install SampleManager Server.
The installer for the Microsoft Visual C++ 2017 Redistributable is included in the
following folder of the SampleManager installation kit:
..\SampleManager 12.2\Server\Redistributables
Note This requirement applies if you want to install the website and SampleManager
Web Application supplied with SampleManager. The website and SampleManager
Web Application are optional features. For more information, see the SampleManager
LIMS Web Interface Configuration Guide.
If you want to use the standard SampleManager website, you must install the
SampleManager Web Application on a separate server that uses the Windows Server
2008 R2 SP1 operating system.
The SampleManager Web Application requires Microsoft .NET Framework version 1.1.
You can download all editions of the .NET Framework from:
http://www.microsoft.com
You must install the Microsoft .NET Framework version 1.1 before you install any later
version of the .NET Framework. It is not possible to install the .NET Framework
version 1.1 after a later version of the .NET Framework.
Windows Server operating systems later than Windows Server 2008 R2 SP1 do not
support Microsoft .NET Framework version 1.1.
For more information about installing and configuring the SampleManager Web
Application and website, see the SampleManager LIMS Web Interface Configuration
Guide.
Installing Oracle
Before installing SampleManager, install and configure Oracle on the database server and
application server machines:
3. Make sure that the Oracle Net Listener for your database can connect to the
database.
4. Create a tablespace (page 226) in your database for SampleManager server data.
If you supply the password for the Oracle SYS account when you create a
SampleManager instance, the SampleManager Add Server Instance Wizard can
create a tablespace for you.
5. Create a user (page 227) that the SampleManager instance will use to connect to
your Oracle database.
If you supply the password for the Oracle SYS account when you create a
SampleManager instance, the SampleManager Add Server Instance Wizard can
create a user account for you.
6. On your application server machine, install the 32-bit Oracle Net Client and
configure it to connect to your Oracle database (page 228).
Note If you install the SampleManager Server on the same computer as the Oracle
database, you must configure the 32-bit Oracle client to connect to the database
through a Net Service Name, in the same way as for a remote database server.
SampleManager Server cannot connect to the database using a 64-bit Oracle Client.
7. On the application server machine, run the Oracle Net Manager and make a note of
the exact Net Service Name that connects to your Oracle database.
By default, the Net Service Name is the same as the database name.
8. If your instance will use the legacy LIMS Reporter tool (page 157) to generate
reports, on the application server machine, install the Oracle ODBC driver (page
230). LIMS Reporter is only available for existing SampleManager systems that have
custom InfoMaker reports.
..\SampleManager 12.2\Server\en-US
4. If the Microsoft .NET Framework version 4.6.2 is not installed on your server, the
installation fails. To correct this problem:
a. Close the SampleManager Setup wizard and install Microsoft .NET Framework
version 4.6.2.
The installer for the required version of the Microsoft .NET Framework is
included in the following folder of the SampleManager installation kit:
..\SampleManager 12.2\Server\Redistributables
b. After the Microsoft .NET Framework version 4.6.2 is installed, repeat steps 1–2
to restart the installation of SampleManager Server.
If the Microsoft .NET Framework version 4.6.2 is installed on your server, you can
proceed with the installation.
5. If the Microsoft Visual C++ 2017 Redistributable is not installed on your server, the
installation fails. To correct this problem:
a. Close the SampleManager Setup wizard and install Microsoft Visual C++ 2017
Redistributable.
The installer for the Microsoft Visual C++ 2017 Redistributable is included in
the following folder of the SampleManager installation kit:
..\SampleManager 12.2\Server\Redistributables
b. After the Microsoft Visual C++ 2017 Redistributable is installed, repeat steps
1–2 to restart the installation of SampleManager Server.
If the Microsoft Visual C++ 2017 Redistributable is installed on your server, you can
proceed with the installation.
8. Custom Setup
Choose the SampleManager components to install:
a. In the tree, click the Client + Server > Oracle item and choose Will be
installed on local hard drive.
b. The Thermo Licensing Server item is selected by default. If you want to use a
Thermo Licensing Server installed elsewhere on your network, click the Thermo
Licensing Server item and choose Entire feature will be unavailable.
c. If you want to use the Service Monitor, click the Service Monitor item and
choose Will be installed on local hard drive. The Service Monitor tool lets you
manage the services associated with SampleManager instances on your server.
d. If you want to change the location where SampleManager will be installed, click
Browse and select the location.
e. Click Next to continue.
To use SampleManager, you must install the Thermo Licensing Server and then install
suitable licenses. If you want to host Thermo Licensing Server on your SampleManager
application server, you can include it in the SampleManager Server installation process.
If you want to host the Thermo Licensing Server on a remote machine, you can start the
installation wizard manually.
..\Server\en-US\PFiles\Thermo\SampleManager\12.2\License
Note When SampleManager Server is installed, the License folder is copied to the
root folder for the SampleManager Server installation. The default location for the
root folder is:
c:\Program Files (x86)\Thermo\SampleManager\12.2
2. Destination Folder
a. Either accept the default location for the installation, or browse for an
alternative.
b. Click Next to continue.
3. Network Share
SampleManager does not use the network share feature. Click Next to continue.
This Setup Wizard can create different types of SampleManager instance. The following
sections describe the settings required to create each type:
• Creating a New Instance (page 27)
This procedure creates a new standalone SampleManager instance with a database
that is populated with default SampleManager data.
• Creating a Cloned Instance (page 37)
This procedure creates a SampleManager instance that shares a database and files
with another instance. Application server instances are useful for large
SampleManager implementations that require load-balancing and sharing to enhance
performance.
• Creating a New Site Instance (page 47)
This procedure creates a SampleManager instance that shares files with another
instance, but has its own database that is populated with default SampleManager
data.
1. In Oracle (page 21), create an empty database ready for the SampleManager instance
data.
2. On the server that will host your instance, install SampleManager Server (page 23).
3. The instance will require a connection to a Thermo Licensing Server. Use one of the
following methods to provide the connection:
• Install the Thermo Licensing Server (page 25) on the server that will host your
new application server.
• Obtain the name of a remote server that hosts a Thermo Licensing Server and
the port number for the Thermo Licensing service on that server. Multiple
SampleManager instances can share a single Thermo Licensing Server.
4. From the Start menu, click Thermo SampleManager 12.2 > Add Oracle Instance.
8. Choose Location
a. Either accept the default location for the instance files, or browse for an
alternative.
b. If you want to use a remote Thermo Licensing Server, enter the connection
string for the machine that hosts the Thermo Licensing Server. The syntax for
the connection string is:
port@hostname
Where:
• port is the port number of the Thermo Licensing service on the remote
server
• hostname is the name of the remote server
c. Click Next to continue.
Figure 2-6. Setup Wizard – Choose Location
• Enter the name and password for an account that does not exist. The wizard
will create an account for SampleManager using the details you enter. The
default username and password are the same as the name of the instance.
If you did not supply the SYS account password, enter the username and
password of an existing account.
b. Click Next to continue.
The next page that appears depends on whether you supplied the SYS password
on the Choose Oracle Database page.
Figure 2-8. Setup Wizard – Choose Database Account
This step applies if you supplied the SYS password for your Oracle database on the
Choose Oracle Database page.
a. If you want to use an existing tablespace in your Oracle database for the
SampleManager data, select Use an existing tablespace and choose the
tablespace you want to use. The list contains all the tablespaces in the Oracle
database.
b. If you want the Add Instance Wizard to create a tablespace for your data, select
Create a new tablespace and enter the SQL command that you want the wizard
to use. For example:
CREATE TABLESPACE SMDB_DB DATAFILE
'D:\oracle\oradata\SMDB\SMDB_DB.DBF' SIZE 100M REUSE AUTOEXTEND
ON NEXT 50M MAXSIZE 500M
We recommend that you use '[instance name]_DB' as your tablespace name.
This option is only available if you supplied the SYS password for the Oracle
database.
c. If you have created a new version of structure.txt containing customized
tablespace information for any of the tables, clear Update oracle_location
details in Structure.txt. For more information, see the "Data Storage and
Handling in Oracle" chapter in the SampleManager LIMS System
Administration Guide.
If this check box is selected, the structure.txt file will be updated with details of
the specified tablespace before the instance is created.
d. Click Next to continue.
Figure 2-9. Setup Wizard – Choose Oracle Tablespace (SYS password supplied)
This step applies if you selected I don't know the SYS password. Please let me
continue on the Choose Oracle Database page.
a. Enter the name of the tablespace that has been created for SampleManager in
your Oracle database.
b. Click Next to continue.
Figure 2-10. Setup Wizard – Choose Oracle Tablespace (SYS password not
supplied)
If you have chosen to let the wizard create the Oracle user, click Next to continue. If
you test the connection, it will fail because the user account specified in the
connection string has not been created yet.
After you create the instance, you can set up your SampleManager licenses, and configure
your application server to allow client workstations to access the SampleManager
instance. For more information, see Post-Installation Tasks (page 97).
1. Use Oracle tools to create a copy of the SampleManager database that the instance
you want to clone connects to. See your Oracle documentation for more
information.
2. On the SampleManager application server, use the 32-bit Oracle Client tools to
create a local net service name (page 229) that connects to the copy of the database
that you created in step 1.
3. On the server that will host your instance, install SampleManager Server (page 23).
4. The instance will require a connection to a Thermo Licensing Server. Use one of the
following methods to provide the connection:
• Install the Thermo Licensing Server (page 25) on the server that will host your
new application server.
• Obtain the name of a remote server that hosts a Thermo Licensing Server and
the port number for the Thermo Licensing service on that server. Multiple
SampleManager instances can share a single Thermo Licensing Server.
5. From the Start menu, click Thermo SampleManager 12.2 > Add Oracle Instance.
9. Choose Location
a. Either accept the default location for the cloned instance files, or browse for an
alternative.
b. Specify the location of the root folder for the SampleManager instance that you
want to clone. For example:
C:\Thermo\SampleManager\Server\VGSM
c. If you want to use a remote Thermo Licensing Server, enter the connection
string for the machine that hosts the Thermo Licensing Server. The syntax for
the connection string is:
port@hostname
Where:
• port is the port number of the Thermo Licensing service on the remote
server
• hostname is the name of the remote server
d. Click Next to continue.
Figure 2-17. Setup Wizard – Choose Location
After you create the instance, you can set up your SampleManager licenses, and configure
your application server to allow client workstations to access the SampleManager
instance. For more information, see Post-Installation Tasks (page 97).
All the other files required for SampleManager operations, such as report designs and
VGL libraries, are obtained from a shared folder that is specified during the instance
creation process. All the application instances that connect to the shared database
should use the same shared folder.
• Windows services – The wizard creates Windows services associated with the
instance, such as the increment daemon and lock daemon. For a description of each
service, see the "Operating Environment" chapter in the SampleManager LIMS
System Administration Guide. The lock daemon for the application server operates as
one of the cluster of lock daemons associated with the applications servers that
connect to the shared database. For more information about lock daemon clustering,
see Lock Daemon Operation with SampleManager Application Server Clusters (page
10).
• Windows registry – The wizard creates Windows registry entries associated with the
instance.
Each application server instance in the cluster that connects to a single database must be
installed on a separate server.
SampleManager LIMS does not maintain a central record of the instances that belong to
an application server cluster. For maintenance and upgrade purposes, we recommend
that you keep a record of your application server cluster architecture.
To create the first instance in a planned cluster of application server instances, create a
new instance, as described in Creating a New Instance (page 27). When the new instance
is operating correctly, configure the Lock Daemon to operate as part of a cluster.
Note When you install an application server with the Setup Wizard, the installation
process configures the lock daemon to run in cluster mode. The lock daemon must be
configured manually for the first instance in an application server cluster.
1. On the server that hosts your new SampleManager instance, open the Registry
Editor.
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\
LabSystems\SampleManager Server\smplock<instance_name>
Where <instance_name> is the name of the instance.
1. On the server that will host your instance, install SampleManager Server (page 23).
2. The instance will require a connection to a Thermo Licensing Server. Use one of the
following methods to provide the connection:
• Install the Thermo Licensing Server (page 25) on the server that will host your
new application server.
• Obtain the name of a remote server that hosts a Thermo Licensing Server and
the port number for the Thermo Licensing service on that server. Multiple
SampleManager instances can share a single Thermo Licensing Server.
3. From the Start menu, click Thermo SampleManager 12.2 > Add Oracle Instance.
The Setup Wizard appears.
7. Choose Location
a. Either accept the default location for the instance files, or browse for an
alternative.
b. Specify the location of the SampleManager instance root folder that contains the
files you want this instance to share. The folder must be shared and accessible to
the user accounts that will be associated with the Windows services for your new
instance.
Specify the shared folder location as a UNC path, not a mapped drive.
c. If you want to use a remote Thermo Licensing Server, enter the connection
string for the machine that hosts the Thermo Licensing Server. The syntax for
the connection string is:
port@hostname
Where:
• port is the port number of the Thermo Licensing service on the remote
server
After you create the instance, you can set up your SampleManager licenses, and configure
your application server to allow client workstations to access the SampleManager
instance. For more information, see Post-Installation Tasks (page 97).
SampleManager LIMS does not maintain a central record of the site instances that share
files with another instance. For maintenance and upgrade purposes, we recommend that
you keep a record of your site instance architecture.
1. In Oracle (page 21), create an empty database ready for the SampleManager instance
data.
2. On the server that will host your instance, install the 32-bit Oracle Net Client, and
configure it to connect to your Oracle database (page 228).
3. On the server that will host your instance, install SampleManager Server (page 23).
4. The instance will require a connection to a Thermo Licensing Server. Use one of the
following methods to provide the connection:
• Install the Thermo Licensing Server (page 25) on the server that will host your
new application server.
• Obtain the name of a remote server that hosts a Thermo Licensing Server and
the port number for the Thermo Licensing service on that server. Multiple
SampleManager instances can share a single Thermo Licensing Server.
5. From the Start menu, click Thermo SampleManager 12.2 > Add Oracle Instance.
9. Choose Location
a. Either accept the default location for the cloned instance files, or browse for an
alternative.
b. Specify the location of the root folder for the SampleManager instance that you
want the site to share files with. For example:
C:\Thermo\SampleManager\Server\VGSM
c. If you want to use a remote Thermo Licensing Server, enter the connection
string for the machine that hosts the Thermo Licensing Server. The syntax for
the connection string is:
port@hostname
Where:
• port is the port number of the Thermo Licensing service on the remote
server
• hostname is the name of the remote server
d. Click Next to continue.
Figure 2-23. Setup Wizard – Choose Location
This step applies if you supplied the SYS password for your Oracle database on the
Choose Oracle Database page.
a. If you want to use an existing tablespace in your Oracle database for the
SampleManager data, select Use an existing tablespace and choose the
tablespace you want to use. The list contains all the tablespaces in the Oracle
database.
b. If you want the Add Instance Wizard to create a tablespace for your data, select
Create a new tablespace and enter the SQL command that you want the wizard
to use. For example:
CREATE TABLESPACE SMDB_DB DATAFILE
'D:\oracle\oradata\SMDB\SMDB_DB.DBF' SIZE 100M REUSE AUTOEXTEND
ON NEXT 50M MAXSIZE 500M
We recommend that you use '[instance name]_DB' as your tablespace name.
This option is only available if you supplied the SYS password for the Oracle
database.
c. If you have created a new version of structure.txt containing customized
tablespace information for any of the tables, clear Update oracle_location
details in Structure.txt. For more information, see the "Data Storage and
Handling in Oracle" chapter in the SampleManager LIMS System
Administration Guide.
If this check box is selected, the structure.txt file will be updated with details of
the specified tablespace before the instance is created.
d. Click Next to continue.
Figure 2-24. Setup Wizard – Choose Oracle Tablespace (SYS password supplied)
This step applies if you selected I don't know the SYS password. Please let me
continue on the Choose Oracle Database page.
a. Enter the name of the tablespace that has been created for SampleManager in
your Oracle database.
b. Click Next to continue.
Figure 2-25. Setup Wizard – Choose Oracle Tablespace (SYS password not
supplied)
If you have chosen to let the wizard create the Oracle user, click Next to continue. If
you test the connection, it will fail because the user account specified in the
connection string has not been created yet.
After you create the instance, you can set up your SampleManager licenses, and configure
your application server to allow client workstations to access the SampleManager
instance. For more information, see Post-Installation Tasks (page 97).
Note This wizard removes the SampleManager server instance and gives you the
option to remove the data associated with the instance. The underlying Oracle
database structure is left on your system. You can remove the database afterwards,
using standard Oracle tools.
1. From the Start menu, click Thermo SampleManager 12.2 > Remove Oracle
Instance.
3. Choose Instance
a. Select the instance that you want to delete
b. Click Next to continue.
Figure 2-27. Delete Server Instance wizard – Choose Instance
5. Confirm Details
Check the details shown and click Next to continue.
Figure 2-29. Delete Server Instance wizard – Confirm Details
Click Save Log to save a log file of the instance deletion. Click Next to continue.
Figure 2-30. Delete Server Instance Wizard – Instance Deletion in Progress
Contents
• Installation Procedure Summary
• Creating a SampleManager Instance
• Removing a SampleManager Instance
4. If you intend to install SampleManager Server and the SQL Server database on
separate machines, install and configure the SQL Server Client Tools Connectivity
feature on the SampleManager application server machine.
The Imprint reporting tool requires a SQL Server Native Client ODBC data source
to connect to the database.
Pre-Installation Checks
Before installing SampleManager server, perform the following tasks:
1. Make sure that the correct operating system is installed (page 14).
2. Back up your system as appropriate.
3. Make sure that your network is functioning correctly and uses the TCP/IP protocol.
4. Make a note of the full name of the computer on which you are installing
SampleManager server.
5. Make sure that the Microsoft .NET Framework 4.6.2 is installed on the server where
you will install SampleManager Server.
The installer for the required version of the Microsoft .NET Framework is included
in the following folder of the SampleManager installation kit:
..\SampleManager 12.2\Server\Redistributables
6. Make sure that the Microsoft Visual C++ 2017 Redistributable is installed on the
server where you will install SampleManager Server.
The installer for the Microsoft Visual C++ 2017 Redistributable is included in the
following folder of the SampleManager installation kit:
..\SampleManager 12.2\Server\Redistributables
Note This requirement applies if you want to install the website and SampleManager
Web Application supplied with SampleManager. The website and SampleManager
Web Application are optional features. For more information, see the SampleManager
LIMS Web Interface Configuration Guide.
If you want to use the standard SampleManager website, you must install the
SampleManager Web Application on a separate server that uses the Windows Server
2008 R2 SP1 operating system.
The SampleManager Web Application requires Microsoft .NET Framework version 1.1.
You can download all editions of the .NET Framework from:
http://www.microsoft.com
You must install the Microsoft .NET Framework version 1.1 before you install any later
version of the .NET Framework. It is not possible to install the .NET Framework
version 1.1 after a later version of the .NET Framework.
Windows Server operating systems later than Windows Server 2008 R2 SP1 do not
support Microsoft .NET Framework version 1.1.
For more information about installing and configuring the SampleManager Web
Application and website, see the SampleManager LIMS Web Interface Configuration
Guide.
See the SQL Server Setup chapter (page 233) for more details.
..\SampleManager 12.2\Server\en-US
4. If the Microsoft .NET Framework version 4.6.2 is not installed on your server, the
installation fails. To correct this problem:
a. Close the SampleManager Setup wizard and install Microsoft .NET Framework
version 4.6.2.
The installer for the required version of the Microsoft .NET Framework is
included in the following folder of the SampleManager installation kit:
..\SampleManager 12.2\Server\Redistributables
b. After the Microsoft .NET Framework version 4.6.2 is installed, repeat steps 1–2
to restart the installation of SampleManager Server.
If the Microsoft .NET Framework version 4.6.2 is installed on your server, you can
proceed with the installation.
5. If the Microsoft Visual C++ 2017 Redistributable is not installed on your server, the
installation fails. To correct this problem:
a. Close the SampleManager Setup wizard and install Microsoft Visual C++ 2017
Redistributable.
The installer for the Microsoft Visual C++ 2017 Redistributable is included in
the following folder of the SampleManager installation kit:
..\SampleManager 12.2\Server\Redistributables
b. After the Microsoft Visual C++ 2017 Redistributable is installed, repeat steps
1–2 to restart the installation of SampleManager Server.
If the Microsoft Visual C++ 2017 Redistributable is installed on your server, you can
proceed with the installation.
8. Custom Setup
Choose the SampleManager components to install:
a. In the tree, click the Client + Server > SQL item and choose Will be installed
on local hard drive.
b. The Thermo Licensing Server item is selected by default. If you want to use a
Thermo Licensing Server installed elsewhere on your network, click the Thermo
Licensing Server item and choose Entire feature will be unavailable.
c. If you want to use the Service Monitor, click the Service Monitor item and
choose Will be installed on local hard drive. The Service Monitor tool lets you
manage the services associated with SampleManager instances on your server.
d. If you want to change the location where SampleManager will be installed, click
Browse and select the location.
e. Click Next to continue.
If you did not choose to install the Thermo Licensing Server component, click
Finish to close the wizard.
To use SampleManager, you must install the Thermo Licensing Server and then install
suitable licenses. If you want to host Thermo Licensing Server on your SampleManager
application server, you can include it in the SampleManager Server installation process.
If you want to host the Thermo Licensing Server on a remote machine, you can start the
installation wizard manually.
..\Server\en-US\PFiles\Thermo\SampleManager\12.2\License
Note When SampleManager Server is installed, the License folder is copied to the
root folder for the SampleManager Server installation. The default location for the
root folder is:
c:\Program Files (x86)\Thermo\SampleManager\12.2
2. Destination Folder
a. Either accept the default location for the installation, or browse for an
alternative.
b. Click Next to continue.
3. Network Share
SampleManager does not use the network share feature. Click Next to continue.
This Setup Wizard can create different types of SampleManager instance. The following
sections describe the settings required to create each type:
• Creating a New Instance (page 67)
This procedure creates a SampleManager instance that shares files with another
instance, but has its own database that is populated with default SampleManager
data.
1. In SQL Server (page 62), create an empty database ready for the SampleManager
instance data.
2. On the server that will host your instance, install SampleManager Server (page 62).
3. The instance will require a connection to a Thermo Licensing Server. Do one of the
following:
• Install the Thermo Licensing Server (page 65) on the server that will host your
new application server.
• Obtain the name of a remote server that hosts a Thermo Licensing Server and
the port number for the Thermo Licensing service on that server. Multiple
SampleManager instances can share a single Thermo Licensing Server.
4. From the Start menu, click Thermo SampleManager 12.2 > Add SQL Instance.
8. Choose Location
a. Either accept the default location for the instance files, or browse for an
alternative.
b. If you want to use a remote Thermo Licensing Server, enter the connection
string for the machine that hosts the Thermo Licensing Server. The syntax for
the connection string is:
port@hostname
Where:
• port is the port number of the Thermo Licensing service on the remote
server
• hostname is the name of the remote server
c. Click Next to continue.
Figure 3-6. Setup Wizard – Choose Location
• This account – Enter the name and password of the account that the
services will use. This is the recommended option.
The account must have appropriate permissions for your SQL Server database
and the server that hosts the database. See SQL Server Setup (page 233) for
more information.
b. Click Next to continue.
Figure 3-10. Setup Wizard – Choose Service Account
After you create the instance, you can set up your SampleManager licenses, and configure
your application server to allow client workstations to access the SampleManager
instance. For more information, see Post-Installation Tasks (page 97).
1. Use SQL Server tools to create a copy of the database. See your SQL Server
documentation for more information.
2. On the server that will host your instance, install SampleManager Server (page 62).
3. The instance will require a connection to a Thermo Licensing Server. Do one of the
following:
• Install the Thermo Licensing Server (page 65) on the server that will host your
new application server.
• Obtain the name of a remote server that hosts a Thermo Licensing Server and
the port number for the Thermo Licensing service on that server. Multiple
SampleManager instances can share a single Thermo Licensing Server.
4. From the Start menu, click Thermo SampleManager 12.2 > Add SQL Instance.
8. Choose Location
a. Either accept the default location for the cloned instance files, or browse for an
alternative.
b. Specify the location of the root folder for the SampleManager instance that you
want to clone. For example:
C:\Thermo\SampleManager\Server\VGSM
c. If you want to use a remote Thermo Licensing Server, enter the connection
string for the machine that hosts the Thermo Licensing Server. The syntax for
the connection string is:
port@hostname
Where:
• port is the port number of the Thermo Licensing service on the remote
server
• This account – Enter the name and password of the account that the
services will use. This is the recommended option.
The account must have appropriate permissions for your SQL Server database
and the server that hosts the database. See SQL Server Setup (page 233) for
more information.
b. Click Next to continue.
After you create the instance, you can set up your SampleManager licenses, and configure
your application server to allow client workstations to access the SampleManager
instance. For more information, see Post-Installation Tasks (page 97).
All the other files required for SampleManager operations, such as report designs and
VGL libraries, are obtained from a shared folder that is specified during the instance
creation process. All the application instances that connect to the shared database
should use the same shared folder.
• Windows services – The wizard creates Windows services associated with the
instance, such as the increment daemon and lock daemon. For a description of each
service, see the "Operating Environment" chapter in the SampleManager LIMS
System Administration Guide. The lock daemon for the application server operates as
one of the cluster of lock daemons associated with the applications servers that
connect to the shared database. For more information about lock daemon clustering,
see Lock Daemon Operation with SampleManager Application Server Clusters (page
10).
• Windows registry – The wizard creates Windows registry entries associated with the
instance.
Each application server instance in the cluster that connects to a single database must be
installed on a separate server.
SampleManager LIMS does not maintain a central record of the instances that belong to
an application server cluster. For maintenance and upgrade purposes, we recommend
that you keep a record of your application server cluster architecture.
To create the first instance in a planned cluster of application server instances, create a
new instance, as described in Creating a New Instance (page 67). When the new instance
is operating correctly, configure the Lock Daemon to operate as part of a cluster.
Note When you install an application server with the Setup Wizard, the installation
process configures the lock daemon to run in cluster mode. The lock daemon must be
configured manually for the first instance in an application server cluster.
1. On the server that hosts your new SampleManager instance, open the Registry
Editor.
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\
LabSystems\SampleManager Server\smplock<instance_name>
Where <instance_name> is the name of the instance.
1. On the server that will host your instance, install SampleManager Server (page 62).
2. The instance will require a connection to a Thermo Licensing Server. Do one of the
following:
• Install the Thermo Licensing Server (page 65) on the server that will host your
new application server.
• Obtain the name of a remote server that hosts a Thermo Licensing Server and
the port number for the Thermo Licensing service on that server. Multiple
SampleManager instances can share a single Thermo Licensing Server.
3. From the Start menu, click Thermo SampleManager 12.2 > Add SQL Instance.
The Setup Wizard appears.
7. Choose Location
a. Either accept the default location for the instance files, or browse for an
alternative.
b. Specify the location of the SampleManager instance root folder that contains the
files you want this instance to share. The folder must be shared and accessible to
the user accounts that will be associated with the Windows services for your new
instance.
Specify the shared folder location as a UNC path, not a mapped drive.
c. If you want to use a remote Thermo Licensing Server, enter the connection
string for the machine that hosts the Thermo Licensing Server. The syntax for
the connection string is:
port@hostname
Where:
• port is the port number of the Thermo Licensing service on the remote
server
• This account – Enter the name and password of the account that the
services will use. This is the recommended option.
The account must have appropriate permissions for your SQL Server database
and the server that hosts the database. See SQL Server Setup (page 233) for
more information.
b. Click Next to continue.
After you create the instance, you can set up your SampleManager licenses, and configure
your application server to allow client workstations to access the SampleManager
instance. For more information, see Post-Installation Tasks (page 97).
SampleManager LIMS does not maintain a central record of the site instances that share
files with another instance. For maintenance and upgrade purposes, we recommend that
you keep a record of your site instance architecture.
1. In SQL Server, create an empty database ready for the SampleManager instance data.
2. On the server that will host your instance, install SampleManager Server (page 62).
3. The instance will require a connection to a Thermo Licensing Server. Do one of the
following:
• Install the Thermo Licensing Server (page 65) on the server that will host your
new application server.
• Obtain the name of a remote server that hosts a Thermo Licensing Server and
the port number for the Thermo Licensing service on that server. Multiple
SampleManager instances can share a single Thermo Licensing Server.
4. From the Start menu, click Thermo SampleManager 12.2 > Add SQL Instance.
8. Choose Location
a. Either accept the default location for the cloned instance files, or browse for an
alternative.
b. Specify the location of the root folder for the SampleManager instance that you
want the site to share files with. For example:
C:\Thermo\SampleManager\Server\VGSM
c. If you want to use a remote Thermo Licensing Server, enter the connection
string for the machine that hosts the Thermo Licensing Server. The syntax for
the connection string is:
port@hostname
Where:
• port is the port number of the Thermo Licensing service on the remote
server
• This account – Enter the name and password of the account that the
services will use. This is the recommended option.
The account must have appropriate permissions for your SQL Server database
and the server that hosts the database. See SQL Server Setup (page 233) for
more information.
b. Click Next to continue.
After you create the instance, you can set up your SampleManager licenses, and configure
your application server to allow client workstations to access the SampleManager
instance. For more information, see Post-Installation Tasks (page 97).
Note This wizard removes the SampleManager server instance and gives you the
option to remove the data associated with the instance. The underlying SQL Server
database structure is left on your system. You can remove the database afterwards,
using standard SQL Server tools.
1. From the Start menu, click Thermo SampleManager 12.2 > Remove SQL
Instance.
The Delete Server Instance Wizard appears.
3. Choose Instance
a. Select the instance that you want to delete
b. Click Next to continue.
Figure 3-25. Delete Server Instance wizard – Choose Instance
4. Database Cleanup
a. If you want to delete the data associated with the instance in the database, select
the Delete the SampleManager data and tables check box.
If the check box is not selected, SampleManager data and tables will be left in
the SQL Server database. Use this option if the underlying database cannot be
accessed, for example if it has been, or will be, deleted manually.
b. Click Next to continue.
CAUTION Selecting the check box results in the permanent deletion of
SampleManager data from the database. You will not be able to restore the database
or recover its data.
If the instance is an application server that shares its database with other <product
instances, selecting the check box deletes the data from the shared database.
5. Confirm Details
a. Check the details shown.
b. Click Next to delete the instance.
Figure 3-27. Delete Server Instance wizard – Confirm Details
Post-Installation Tasks
This chapter describes the tasks you must perform after you have installed
SampleManager on your application server.
Contents
• SampleManager Licenses
• Running SampleManager Client for the First Time
• Configuring the Application Server Firewall
• Setting the Server Timezone
• Configuring the Server Warm Start Feature
• Smart Client Deployment
• Encrypting the Database Connection String in the
Windows Registry
• Adding Dictionaries for the Spell Checking Feature
• Configuring ADO Cursor Locations and Cache Size
• Adding the ActiveRecord Task to the Watch Dog
Timer
• Add DLLs for Report Designer OLE Previews to Exe
Folder
SampleManager Licenses
SampleManager uses FlexNet licensing, which is implemented through the Thermo
Licensing Server. The Thermo Licensing Server is installed as part of the main
SampleManager installation process, in the following folder by default:
C:\Program Files (x86)\Thermo\Thermo Licensing Server
The SYSTEM user account can log in to SampleManager at any time without taking a
license from the Full license pool. SampleManager allows one license-free connection
with the SYSTEM account at any time. This feature lets you install and test your
SampleManager client before you obtain your licenses.
Read-Only licenses purchased. Any number of operators can have their License Type
set to Read-Only.
• Read-Only Named – A license that grants a specific user read-only access to all
SampleManager features. If an operator connects to SampleManager with a
Read-Only license, they can view data but not create or modify it. The only records
that are created in a Read-Only session are background system records such as access
logs and recently used items. Each Read-Only Named license is assigned to a specific
operator and is only available for use by that operator.
Each module you install also requires a license. You must add the license for a module
before you install the module. If a valid license is not present, the module installation
process can fail.
After you have finished installing your SampleManager server, you must obtain a license
file for the licenses you have purchased, by sending details of your installation to:
[email protected]
The license is associated with the server machine on which you have installed the
Thermo Licensing Server. If you move this software to a new server machine in the
future, contact Support to obtain a new license file.
The Save As dialog box appears, prompting you for a file name and location for the
installation details file.
5. Enter a suitable name and location for the file and click Save to create it.
2. Open the Windows Service panel and start the Thermo Licensing Server service.
Note If this service has already been started, stop and then start it again. Do not
use the Restart option.
3. You should now be able to run the SampleManager client and connect to your
SampleManager instance, as described in Running SampleManager Client for the
First Time (page 104).
4. If you purchased Full Named or Read-Only Named licenses, assign the licenses to
the corresponding users (page 102).
To open the License Group Editor, use one of the following methods:
• From the main menu, select Setup > System > Users > Named User License Setup.
• In Explorer, right-click an operator and select Operator > Modify. On the Definition
page of the Personnel Property sheet, click the ellipsis button in the License
Type prompt.
Figure 4-2. License Group Editor
The explorer grid shows the type of license assigned to each SampleManager operator.
The selection criteria for the list of operators that appear depends on the value of the
LOGIN_LDAP_NEEDSPASSWORD configuration item:
• Yes – The list contains records from the PERSONNEL table that are associated with
a record in the PASSWORD table and that have the remove_flag set to False.
• No – The list contains records from the PERSONNEL table that have the
remove_flag set to False.
The Pool Size prompts below the explorer grid show the number of each type of license
that is included in your SampleManager license file. The progress bar beside each license
type shows how many licenses of that type have been allocated to operators in the grid.
You can assign any number of operators to the Full and Read-Only license types, as these
types of license limit the number of concurrent sessions. The Full Named and
Read-Only Named license types show a validation error if the number of operators
assigned that type of license exceeds the Pool Size.
To select a continuous series of operators, select the first operator then hold down
the SHIFT key and select the last operator.
To select a series of operators that are not continuous, hold down the CTRL key and
select each operator.
2. Right-click and choose the type of license you want to apply to the selected
operators.
3. To save changes to the license type allocations, click OK. Your changes will take
effect after a 12-hour delay.
To implement the license type allocation changes immediately, stop and restart the
Thermo Licensing service. If you stop the Thermo Licensing service, all current
sessions are terminated.
This feature prevents the SYSTEM user from being locked out of SampleManager.
Because no SampleManager server connections have been set up, the Create a new
server item window appears.
Figure 4-3. Create a new server item window
4. Select the Remote Server option and enter the following values:
• Instance Name – The name of the instance. If this field is set to Default,
SampleManager will connect to the current Default Instance recorded in the
Windows registry on the remote server machine.
• Server Name – The name of the server where the instance is installed.
• Port Number – The port number for the instance.
6. Log in to SampleManager, using the username 'SYSTEM', with the Password field
left blank. If the ThermoLicensing Service has not started, you might see an error. In
this case, start the ThermoLicensing service using the Services tool in Windows
Administrative Tools.
You can now configure your SampleManager system using the SampleManager
client.
Note We recommend that you configure the security settings for the SYSTEM user
immediately. Change the default password to a new, secure value.
For more information, see the SampleManager LIMS System Administration Guide.
Note The SampleManager Debugger is used to debug VGL reports. You might not
need to use the Debugger on all your client machines.
For more information, see the "Security" chapter in the SampleManager LIMS System
Administration Guide.
If the Server Warm Start feature is enabled, the SMDaemon service operates as follows:
To configure the Server Warm Start feature for an instance, set the following application
settings in the SMDaemon.exe.config file:
• WarmStartInstance
• WarmStartInterval
The SMDaemon config file is found in the following folder on the SampleManager
server:
<SampleManager root>\Server\<instance>\Exe
Where <SampleManager root> is the root folder of the SampleManager installation and
<instance> is the name of the SampleManager instance.
For more information about the SampleManager config files, see the "Operating
Environment" chapter in the SampleManager LIMS System Administration Guide.
Note If the Server Warm Start feature is enabled and you add a new SampleManager
server to the Manage Servers window, the server will not appear in the Manage Servers
list the next time a SampleManager client connects to the SampleManager application
server. This effect occurs because the SampleManagerServerHost process for that client
session was started by the Server Warm Start feature before the new SampleManager
server was added. The new server will appear on the list in subsequent SampleManager
client sessions.
SampleManager 12.2\SmartClient
2. Extract the following .zip file to a location that will be accessible to your
SampleManager users:
SampleManager 12.2 SmartClient.zip
Note The Smart Client files can be placed in a shared folder or hosted on an IIS
server.
3. Send each user a link to the setup.exe file in the extracted folder.
4. When a user clicks the link for the first time, the SampleManager client is installed
using ClickOnce deployment. A SampleManager icon appears on the Windows
desktop. Whenever the user runs SampleManager by clicking the icon, the Smart
Client checks for updates and runs an installation if any changes are found.
Note The SampleManager Smart Client is installed on a workstation for the current
user only.
To prevent someone from gaining unauthorized access to the connection string through
the registry, you can use SampleManager to encrypt the registry value.
2. From the main menu, select Setup > System > Encrypt Connection String.
For more information, see the following chapters in the SampleManager LIMS System
Administration Guide:
• "Data Storage and Handling in Oracle"
• "Data Storage and Handling in SQL Server"
– Prompt
– Text Edit
– Rich Text Edit
• The SPELLCHECKING_ENABLED configuration item is set to Yes.
• Dictionary files exist in the Resource folder for the SampleManager instance.
The spell check feature compares text with entries in the SampleManager dictionary files
in the following order:
1. The custom dictionary maintained on the current workstation.
2. The company dictionary maintained on the server and synchronized when a client
workstation connects to the server.
3. The language-specific dictionary for the language associated with the current
operator. Language-specific dictionaries are maintained on the server and
synchronized when a client workstation connects to the server.
For detailed instructions about obtaining and installing dictionary files, see the "Spell
Checker" chapter in the SampleManager LIMS Form Designer Manual.
The ADO cursor location for an instance is obtained from the Windows registry on the
SampleManager application server machine when the instance first connects to the
database. The setting is stored in the smp$ado_cursor_location registry item in the
following registry key:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LabSystems\
SampleManager Server\<Instance_name>
The ADO cursor location value can be changed at runtime to optimize an individual
database operation. To change the value at runtime, set the value of the
ADO_CURSOR_LOCATION global to CLIENT or SERVER. For information about
setting global values, see the VGL Programmer's Guide Help and the SampleManager
Form Designer Help.
The ADO cache size property controls how many records the provider keeps in its buffer
and how many records are retrieved at one time into local memory. The setting is stored
in the smp$ado_cache_size registry item in the following registry key:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LabSystems\
SampleManager Server\<Instance_name>
The ADO cache size value can be changed at runtime to optimize an individual database
operation. To change the value at runtime, set the value of the ADO_CACHE_SIZE
global to the required integer. For information about setting global values, see the VGL
Programmer's Guide Help and the SampleManager Form Designer Help.
1. From the main menu, select Setup > Scheduling > Watch Dog Timer > List
Entries.
5. To run the ActiveRecord task for a specific table, enter the name of the table,
enclosed in double quotes, in the Task Parameters prompt. If the Task Parameters
prompt is left empty, the ActiveRecord task will run for all tables that have an Active
flag.
6. Set the Recurrence Pattern for the task. The task should run at least once per day, to
make sure that the active status values are kept up-to-date. See the "Background
Operations" chapter in the SampleManager LIMS System Administration Guide for
more information about setting the frequency pattern.
7. Set the Range of Recurrence for the task. In a production system, the No End Date
option should be selected. See the "Background Operations" chapter in the
SampleManager LIMS System Administration Guide for more information.
The spmtqinstance service processes the entries in the watch dog timer queue. Make sure
that the spmtqinstance service for your instance is running before you start to create and
update entities that use the version management feature. For more information about the
Windows services associated with SampleManager, see the "Operating Environment"
chapter in the SampleManager LIMS System Administration Guide.
To enable this feature, you must add the DLLs required for each attachment type to the
Exe folder of your SampleManager instance.
http://www.ghostscript.com/
To support Microsoft Office attachments, obtain the following Office primary interop
assemblies from Microsoft:
• Microsoft.Office.Interop.Excel.dll
• Microsoft.Office.Interop.Powerpoint.dll
• Microsoft.Office.Interop.Word.dll
• Office.dll
Note The SampleManager client can also be deployed to client workstations using
the Smart Client functionality (page 107).
Contents
• Prerequisites
• Installing SampleManager Client Software
• Connecting to a SampleManager Server Instance
• Managing Server Instance Connections
Prerequisites
Make sure that a printer has been set up on the workstation. The printer does not have
to be a physical printer, for example, Adobe PDF can be used.
In the SampleManager LIMS 12.2 installation kit, there are two folders that contain
installation files for the SampleManager client:
• Client – The client installer to use for new implementations.
• Client_Inc_Imprint – The client installer to use for upgraded systems that require
support for the InfoMaker reporting tool or combit List and Label label design tool.
These tools are not required for new instances.
2. Open the folder that contains the SampleManager client installer required for your
instance.
3. Double-click the SampleManagerInstaller.msi file.
To suppress the SampleManager splash screen when the client starts, add the following
parameter to the Target value in the SampleManager shortcut:
-NoSplash
1. Copy the following file from the SampleManager installation kit onto the target
machine:
..\Client\SampleManagerInstaller.msi
Where:
• <path to SampleManagerInstaller.msi> is the path and file name of the
SampleManagerInstaller.msi file on the target machine.
• <path to root folder> is the path of the root folder where the
SampleManager client will be installed.
• <path to exe folder> is the path of the exe folder of the SampleManager client
installation.
• <path to help folder> is the path of the help folder of the SampleManager
client installation.
• <path to logfile> is the path of a folder where you want to save a log file of
the installation.
On a 32-bit operating system, the default location of the Exe folder is:
C:\Program Files\Thermo\SampleManager\<version>\Exe
On a 64-bit operating system, the default location of the Exe folder is:
C:\Program Files (x86)\Thermo\SampleManager\<version>\Exe
Each user who will create csv or html tab reports must have Read/Write permissions on
the folder.
1. From the Windows Start menu, run the SampleManager client application.
By default, this option is found under Start > All Programs > Thermo
SampleManager > SampleManager.
Because no SampleManager server connections have been set up, the Create a new
server item window appears.
Figure 5-2. Create a new server item window
3. Select the Remote Server option and enter the following values:
• Instance Name – The name of the instance. If this field is set to Default,
SampleManager will connect to the current Default Instance recorded in the
Windows registry on the remote server machine.
• Server Name – The name of the server where the instance is installed.
• Port Number – The port number for the instance.
4. If the server is configured for proxy login, select the Use proxy login check box.
See the Proxy Login (page 121) section for more information.
5. Click OK to save changes and close the window.
Proxy Login
If your server is configured to use proxy login, the Use proxy login check box must be
selected in the server connection details on each client.
When a client is configured for proxy login, the SampleManager Login window does not
have Username and Password fields.
Figure 5-4. SampleManager Login window for proxy login
To log in to SampleManager, click Login. Your current Windows login details will be
authenticated by the server and, if successful, the SampleManager Explorer will appear.
If your SampleManager instance is configured to use proxy login, you can create a
desktop shortcut that bypasses the SampleManager login window.
3. In the Target box, add the name of the SampleManager server to the end of the
target path:
Where Your Server Name is the name given to the SampleManager server instance
in the Create a new server item window (page 119).
The Target value required to connect to a server instance called vgsm local is:
If the current user interface font does not contain all the characters required for your
preferred language, SampleManager will not render text correctly.
1. From the main menu, select View > Select Fonts. The Font Select dialog box
appears.
2. Change the SampleManager Font settings to one or more fonts that contain the
characters for your language.
Note SampleManager stores font settings on each workstation for the combination
of your Windows user account and the SampleManager server that you are currently
connected to.
1. From the Windows Start menu, run the SampleManager client application.
The SampleManager Login window appears.
Figure 5-5. SampleManager Login window
The Manage Servers window (page 124) appears, showing a list of configured server
items. Each server item is a set of connection details for a SampleManager server
instance.
4. Click the Close Server Setup button to save changes and return to the
SampleManager Login window.
Note It is also possible to deploy the client with a list of pre-configured servers (page
126).
If a user changes the server settings for a SampleManager client, the servers.xml file is
stored in the following location:
C:\Users\<UserName>\AppData\Roaming\Thermo Fisher Scientific
Inc\SampleManager\<version>
Where <UserName> is the Windows user name of the current user, and <version> is the
SampleManager version number. This copy of servers.xml is specific to the current user
and client workstation.
You can create a copy of servers.xml that will be common to all users of the
SampleManager client on a workstation.
1. Create a servers.xml file that contains the server information you want to use.
2. Place a copy of the servers.xml file in the following location on the client PC:
C:\ProgramData\Thermo Fisher Scientific
Inc\SampleManager\<version>
3. If you want to prevent users changing the server settings, make the servers.xml file
read-only.
<Servers>
<Server>
<Name>Production</Name>
<Type>Remote</Type>
<MachineName>ukalt-production</MachineName>
<Port>56100</Port>
<InstanceName>Default</InstanceName>
<UseProxy>False</UseProxy>
</Server>
</Servers>
– Local – The client will connect to the default SampleManager Server instance
hosted on the current machine. The default instance information is stored in the
Windows registry.
– Remote – The connection details are defined in the MachineName, Port, and
InstanceName elements.
• MachineName – The name of the server where the instance is installed.
• Port – The port number for the instance.
Upgrading SampleManager
This chapter describes the procedure for upgrading to SampleManager 12.2 from one of
the following versions:
• SampleManager LIMS 12.1
• SampleManager LIMS 12.1 SP1
• SampleManager LIMS 12.1 SP2
The instructions in this chapter assume that you understand the basic principles of the
Windows operating system and are familiar with the use of file editors.
The upgrade of SampleManager differs from site to site depending on the hardware
configuration and other usage of the machine on which it is being installed. The
procedures described in this chapter provide one method of upgrade only, and different
sites should proceed according to company standard practices.
CAUTION Before starting the upgrade procedure, make a full backup of your
SampleManager system. In particular, make sure that you have backup copies of any
files that need manual upgrading, for example user-modified versions of structure.txt
and message.txt.
Contents
• Prerequisites
• Upgrading SampleManager Server
• Manual Upgrade Procedures
• Upgrading SampleManager Clients
• Upgrading the Password Encryption
• New Menu Items
• Fixing Form Upgrade Errors
• Entity-Specific Changes
• Report Designer
Prerequisites
Before you upgrade SampleManager, make sure that your database and application server
are ready for the upgrade process:
3. Make sure that you have installed all the updates for the Windows operating system
on your servers.
4. Make sure that the Microsoft .NET Framework 4.6.2 is installed on the server where
you will install SampleManager Server.
The installer for the required version of the Microsoft .NET Framework is included
in the following folder of the SampleManager installation kit:
..\SampleManager 12.2\Server\Redistributables
5. Make sure that the Microsoft Visual C++ 2017 Redistributable is installed on the
server where you will install SampleManager Server.
The installer for the Microsoft Visual C++ 2017 Redistributable is included in the
following folder of the SampleManager installation kit:
..\SampleManager 12.2\Server\Redistributables
6. Check that the database account SampleManager uses has all the security
permissions required for SampleManager LIMS 12.2. See the following chapters for
more information:
• Oracle Setup (page 223)
• SQL Server Setup (page 233)
7. Check whether the instance that you want to upgrade is part of an application server
cluster:
a. On the server that hosts your SampleManager instance, open the Registry
Editor.
b. Navigate to the following registry key:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\
LabSystems\SampleManager Server\smplock<instance_name>
Where <instance_name> is the name of the instance.
c. Examine the use_cluster value. If use_cluster is true, the instance is part of an
application server cluster.
Files containing user modifications must be upgraded manually during the upgrade
process.
1. Create a full backup of your SampleManager instance, including the database and
the Thermo\SampleManager\Server\<instance_name> folder.
Keep a copy of the original structure.txt file in an accessible location, as you will
require it when you upgrade the database.
2. Disable the following services for the instance:
• smptq<instance_name>
• smpwcf<instance_name>
• All batch services for the instance. Batch service names use the following naming
convention:
smpbatch<instance_name>_<program_name>
The files for SampleManager Server 12.2 will be installed in the following folder by
default:
C:\Program Files (x86)\Thermo\SampleManager\12.2
Note If you choose to install the Thermo Licensing Server component, it will be
upgraded if necessary.
4. Run the Upgrade Server Instance Wizard.
5. Upgrade structure.txt manually if it differs from the default structure.txt file for the
original SampleManager version.
If the Upgrade Server Instance Wizard detects that the structure.txt file for the
instance is not the same as the default structure.txt file for the version that you are
upgrading from, the upgrade process will pause and prompt you to upgrade the file
manually.
Some files, such as message.txt and VGL reports, might contain user modifications
specific to your installation.
If these files contain modifications, the Upgrade Server Instance Wizard will not
overwrite them. The wizard will inform you that they have been modified and
prompt you to upgrade them manually.
8. Restart the timerqueue service and batch services that you suspended in step 2.
In the following diagram, Application Server 1 hosts the primary instance in the
application server cluster and Application Server 2 hosts a secondary instance. All the
instances in an application server cluster have the same instance name.
2. Locate the shared files for the application server cluster. If you do not have a record
of the shared folder locations, you can obtain this information from the Windows
registry of one of the servers that hosts an application server instance:
a. On the server that hosts your SampleManager instance, open the Registry
Editor.
b. Navigate to the following registry key:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\
LabSystems\SampleManager Server\smplock<instance_name>
Where <instance_name> is the name of the instance.
c. Examine the smp$archivefiles value. This value contains the location of the
shared Archive folder for the instance. All the shared folders are normally in the
same location.
3. Create a full backup of the database and all the shared folders.
Keep a copy of the original structure.txt file in an accessible location, as you will
require it when you upgrade the database.
4. On each server that hosts an instance in the application server cluster, disable all the
services for the instance:
• SMDaemon<instance_name>
• smplock<instance_name>
• smp<instance_name>
• smptq<instance_name>
• smpwcf<instance_name>
• All batch services for the instance. Batch service names use the following naming
convention:
smpbatch<instance_name>_<program_name>
5. On each server that hosts an instance in the application server cluster, install the
latest version of the SampleManager server software.
The files for SampleManager Server 12.2 will be installed in the following folder by
default:
C:\Program Files (x86)\Thermo\SampleManager\12.2
Note If you choose to install the Thermo Licensing Server component, it will be
upgraded if necessary.
6. Choose one instance to upgrade in the application server cluster.
7. On the server that hosts the instance you have chosen to upgrade, start the following
services:
• SMDaemon<instance_name>
• smplock<instance_name>
• smp<instance_name>
8. Run the Upgrade Server Instance Wizard.
Some files, such as message.txt and VGL reports, might contain user modifications
specific to your installation.
If these files contain modifications, the Upgrade Server Instance Wizard will not
overwrite them. The wizard will inform you that they have been modified and
prompt you to upgrade them manually.
12. For the instance that you have upgraded, restart the other services that you
suspended in step 4.
14. Upgrade each of the remaining application server instances in the cluster one at a
time:
a. On the server that hosts the application server instance, install the latest version
of the SampleManager server software.
b. Use the Delete Server Instance Wizard to remove the old version of the instance:
• Oracle – Removing a SampleManager Instance (page 55)
The Database prompt shows the Oracle Net Service Name of the database that your
instance connects to.
a. Enter the password for the SYS account of the selected database.
The wizard uses the SYS user and corresponding password for system
administration operations during the upgrade process. The SYS password will be
used to connect to Oracle during the upgrade process, but will not be stored or
cached by SampleManager.
b. If you cannot supply the SYS password for your Oracle database, select I don't
know the SYS password. Please let me continue. Make sure the Oracle
account that the instance uses to connect to the database has all the required
permissions (page 227) before you proceed.
c. Click Next to continue.
5. Confirm Details
a. Check that the details shown for the instance are correct.
b. Click Next to start the upgrade procedure.
The instance upgrade process pauses to let you perform a manual upgrade of the
structure.txt file.
a. If you want to stop the instance upgrade process until you have upgraded your
structure.txt file, click Cancel. You can start the Upgrade Server Instance
Wizard again later to resume the upgrade process. For more details, see
Upgrading structure.txt (page 145).
b. If you want to upgrade your structure.txt file immediately, follow the
instructions in Upgrading structure.txt (page 145) without closing the wizard.
c. When you have applied all the modifications to the structure.txt file for the
instance, select the check box at the bottom of the page.
d. Click Next to continue.
• Abort – Stops the upgrade process. You can run the Upgrade Server
Instance Wizard again later.
• Retry – Resumes the upgrade process after you have modified your copy of
structure.txt. The updated copy of structure.txt is checked and if problems
are identified, the upgrade process will pause again.
Fixing Character Set Rendering Issues for an Oracle Instance with a Database that Contains
Multiple Languages
This section applies if you are upgrading a SampleManager instance that matches all the
following criteria:
• The database is Oracle.
• The database contains SampleManager data in more than one language.
• Some or all characters in existing SampleManager data are not rendered correctly
when viewed in a SampleManager 12.2 client after your upgrade.
The character rendering issue occurs because SampleManager dynamically assigns a code
page that does not match the code page of the SampleManager application server that
created the data.
1. On the server that hosts your SampleManager instance, open the Registry Editor.
To restore the license server using the Windows Uninstall or Change a Program
window
1. To uninstall the Thermo Licensing Server, use the Windows Uninstall or change a
program window.
2. In a Windows Explorer, open the Thermo Licensing Server folder and make a
backup copy of the .lic license file.
3. In the Thermo Licensing Server folder, delete all files except the .lic license file.
5. To install the Thermo Licensing Server, follow the installation instructions on the
installation wizard.
The license server should now deploy correctly.
If the problem is not resolved by restoring the license server using the Windows Uninstall
or Change a Program window, you must restore the license server using
ThermoLicensingServerSetup.exe.
6. To install the Thermo Licensing Server, follow the installation instructions on the
installation wizard.
If a SampleManager WCF service for the instance does not exist, the upgrade procedure
creates one. If you are upgrading from a version of SampleManager 10.0 that did not use
a SampleManager WCF service, you must reconfigure any connections to the instance
that used the old LIMSML Web service and COM+ interface to connect through the
SampleManager WCF service. The WCF service implements the same
ILIMSWebService interface as the LIMSML Web service, so any external applications
developed to communicate with the LIMSML Web service will work in the same way
with the WCF service.
When the upgrade is complete, restart the SampleManager WCF service to make sure
that it recognizes the changes to the database structure.
This section describes the processes by which you can upgrade these files manually.
Required Tools
We recommend that you use a file comparison tool to merge existing versions of
SampleManager files with the corresponding SampleManager 12.2 versions.
Note All the SampleManager files that might need to be edited are text files, and can
be edited using any standard text editor, such as Windows Notepad.
Upgrading structure.txt
The database schema file, structure.txt, is subject to the most common user
modifications, so it often needs upgrading manually. See Required Tools (page 144) for
information about tools that can be used for the manual upgrade.
You must create a version of structure.txt file for your instance that includes:
• The customizations contained in the original copy of structure.txt for your instance
• The changes made to the default structure.txt for SampleManager 12.2
The new structure.txt file will be used to build the database structure for your upgraded
SampleManager instance.
There are many significant differences between the default structure.txt files for older
versions of SampleManager and SampleManager 12.2. The simplest way to upgrade
structure.txt is usually to transfer the modifications in the current structure.txt for the
instance into a copy of the default structure.txt file for SampleManager 12.2.
The following version-specific files will be created in the folder during the automatic
upgrade procedure:
• structure_<original_version>.txt
A copy of the default structure.txt for the version of the product that you are
upgrading from.
• structure_122.txt
A copy of the default structure.txt for SampleManager 12.2.
1. Use a file comparison tool to compare the version of structure.txt for your instance
with the standard version of structure.txt for SampleManager 12.1.
The standard version of structure.txt for SampleManager 12.1 can be found here:
<instance_root>\Upgrade\12.1 to 12.2\structure_121.txt
3. Save the modified version of the SampleManager 12.2 structure.txt file to the
following file path:
<instance_root>\data\structure.txt
Where:
• <instance_root> is the root folder of your instance
• <original_version> is the version you are upgrading from
This file contains a list of all the files that could not be overwritten by the upgrade
process. A file cannot be overwritten when the existing version of the file is not the same
as the original file distributed with SampleManager.
Notes Files in the Imprint folder of the instance can be ignored. These files are
updated automatically by the upgrade process.
• The distribution versions of the files from the SampleManager version you are
upgrading from can be found by default in:
C:\Program Files
(x86)\Thermo\SampleManager\12.2\Upgrade\<original_version>
Use a file comparison tool to compare each modified file with the corresponding
SampleManager 12.2 version. Merge the changes to create a version of the file that
contains:
• All user modifications made to the original version for the instance, compared to the
standard file distributed with the version of SampleManager you are upgrading from.
AND
• All modifications made between the standard file in the version of SampleManager
you are upgrading from and the SampleManager 12.2 version.
Note Rather than editing the original version of the file for the instance, it is often
easier to copy the SampleManager 12.2 distribution version to the instance folder and
reapply the user modifications. In this case, you must remove the read-only attribute
from the copied file.
To identify the changes that you must make to your result_entry_messages.txt file to
bring it in line with SampleManager 12.2 requirements, compare the following files:
• The existing copy for your instance:
<instance_root>\Message\result_entry_messages.txt
To identify the changes made to the default versions of the file between the version of
SampleManager you are upgrading from and SampleManager 12.2, compare the
following files:
• The unmodified SampleManager 12.2 version:
C:\Program Files
(x86)\Thermo\SampleManager\12.2\Message\result_entry_messages.t
xt
• The unmodified copy for the version of SampleManager you are upgrading from:
C:\Program Files
(x86)\Thermo\SampleManager\12.2\Upgrade\<original_version>\Mess
age\result_entry_messages.txt
Edit your version of the file, so that it includes changes from all three of these difference
checks.
If your instance uses these features, you can install a version of the SampleManager
desktop client that supports them.
Use the Programs and Features tool in the Windows Control Panel to uninstall the
client.
1. In a text editor, open a backup copy of the structure.txt file that was created before
you upgraded the instance.
2. Find the section that defines the PASSWORD table:
table password;
field identity
links_to personnel.identity
used_for unique_key;
field cryptpass datatype identity;
field expires datatype date;
field frozen
datatype boolean
true_word 'Frozen'
false_word 'Active'
default 'Active' ;
field attempts
datatype integer
default 0 ;
field last_login datatype date;
3. If the cryptpass field definition matches the following example, the field length is 10,
which is the default length for an identity field:
field cryptpass datatype identity;
If the cryptpass field length is 10, the default registry settings match the values
required for your instance and no further changes are necessary.
4. If the cryptpass field length is not 10, make a note of the length value. For example,
the following definition specifies the field length as 20:
field cryptpass datatype identity (20);
5. If the cryptpass field length is not 10, you must update the registry settings for the
instance before users can connect:
a. On the SampleManager application server, open the Registry Editor.
b. Navigate to the registry key for your SampleManager instance:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\
LabSystems\SampleManager Server\<instance_name>
c. Set the LoginAllowLegacy value to True.
d. Set the LoginCryptLength value to the value that you noted in step 4.
SampleManager has new configuration items that let you define complexity rules for
passwords. If necessary, define the complexity rules before your users reset their
passwords. For more information, see the "Electronic Signatures" chapter in the
SampleManager LIMS System Administration Guide.
When you view the SM12.2 menu in Customize mode, the SM12.2 > View menu
contains two Quick Launcher options. One of the Quick Launcher options is visible in
the desktop client and the other is visible in the web client.
For information about customizing the structure of the main menu, see the "Toolbars
and Menus" chapter in the SampleManager LIMS Configuration Guide.
If a form definition in your instance includes custom controls with names that match
default controls in the new version of the form, the form compilation process reports
errors similar to the following example:
Personnel.cs(1202,25): error CS0102: The type
'Thermo.SampleManager.Library.FormDefinition.FormPersonnel' already
contains a definition for 'SignatureBoxControlName'
Personnel.cs(1132,25): (Location of symbol related to previous error)
Personnel.cs(1208,25): error CS0102: The type
'Thermo.SampleManager.Library.FormDefinition.FormPersonnel' already
contains a definition for 'SignatureBoxControlLabel'
Personnel.cs(1138,25): (Location of symbol related to previous error)
Personnel.cs(1213,21): error CS0102: The type
'Thermo.SampleManager.Library.FormDefinition.FormPersonnel' already
contains a definition for 'SignatureBox'
Personnel.cs(1143,21): (Location of symbol related to previous error)
Personnel.cs(1265,25): error CS0102: The type
'Thermo.SampleManager.Library.FormDefinition.FormPersonnel' already
contains a definition for 'SignatureButtonControlName'
Personnel.cs(1090,25): (Location of symbol related to previous error)
4. Right-click and select Tools > Import Form(s). The Form Import window appears.
5. Navigate to the Form folder for the SampleManager LIMS server application. By
default this folder is found at the following location:
6. Select the .frm file for the form that caused the error.
7. Click Open. SampleManager imports the default definition of the form for
SampleManager LIMS 12.2.
For property sheet forms, we recommend that you use the Tools > Extend option to
add custom controls to separate overlay pages. This mechanism preserves your
customizations when the forms are upgraded.
Entity-Specific Changes
This section describes significant changes to SampleManager entities that occur after
upgrading to SampleManager12.2.
Rack Templates
The Rack Template property sheet has been updated to relocate the settings related to
the structure and appearance of rack templates. Therefore, the following Rack Template
property sheet pages are only available in rack templates created in SampleManager 12.1
or earlier:
• Rack Layout
• Status Icons
• Expression Icons
• Preview Layout
For more information about these pages, see "Sequences" in the SampleManager LIMS
12.1 Laboratory Execution Guide.
The Preview Layout page has been directly replaced with the Plate Preview page, which
contains the same information. The new locations of the settings that were on the Rack
Layout, Status Icons, and Expressions Icons pages are listed in the table:
Structure of the rack Rack Layout page Plate Type and Plate
Appearance entities
Order in which the rack Rack Layout page Plate Fill Order entity
cells are populated
You can specify the plate type, plate appearance, and plate fill order for a rack template
on the General page of the Rack template property sheet. For more information about
plate types, plate appearances, and plate fill orders, see "Plates" in the SampleManager
LIMS 12.2 Laboratory Execution Guide.
Report Designer
SampleManager Report Designer now supports the use of expressions for binding
controls to data and applying conditional formatting.
Expression binding is the default mechanism that is used by all report designs created
from SampleManager 12.1 SP2 onwards.
You can convert report designs that use the data binding mechanism to use the new
expression binding mechanism. Before you convert your report designs, back up the
.repx report design files in the smp$textfiles folder of your SampleManager instance.
There is no mechanism to convert a report design from expression bindings to data
bindings.
1. Open the report design in the Report Designer. The following message appears:
The XtraReport contains bindings. Do you want to convert them to expressions?
2. Click Yes to convert the report design to use expressions, or No to retain the original
data bindings.
3. After you convert the report design, validate the report template. If the validation
fails, either restore the original version of the report design from the backup file, or
correct the issues in the current version.
From SampleManager LIMS version 12.2, SampleManager uses Unicode to handle text
within the application. To support Unicode, the web application server requires an
updated DLL for the encryption functionality.
From SampleManager LIMS 12.2, LIMS Reporter and Imprint are no longer shipped
with SampleManager. The explorer folders, configuration items, and menu options
related to Imprint and LIMS Reporter reports are only available in instances that were
upgraded from an earlier version of SampleManager. SampleManager Report Designer is
the standard mechanism for generating reports. This chapter applies when you are
moving an existing SampleManager instance that uses InfoMaker reports to a new server.
For more information, see the Reports chapters in the SampleManager LIMS System
Administration Guide.
Contents
• Connections Between LIMS Reporter and the
Database
• Installation Procedures for SampleManager on
Oracle
• Installation Procedures for SampleManager on SQL
Server
• Installing LIMS Reporter
• Setting up a Database Profile
• Producing Reports in PDF Format
Figure 7-2. Connection between LIMS Reporter and a SampleManager SQL Server
database
The required character set is obtained from the currently active code page on the
machine where the LIMS Driver is running. If the currently active code page does not
match the code page of the system used to enter the data, the characters might not be
rendered correctly.
1. If your PC has a 32-bit operating system, from the Windows Control Panel, open
Administrative Tools and then run the Data Sources (ODBC) application.
On 64-bit operating systems, there are separate ODBC Data Source Administrators
for 32-bit and 64-bit ODBC data sources. SampleManager uses 32-bit data sources.
To open the 32-bit ODBC Data Source Administrator, run the following
application:
c:\windows\SysWow64\odbcad32.exe
The Create New Data Source window appears, showing a list of available drivers.
4. Select the Oracle ODBC Driver that corresponds to your Oracle installation, for
example, Oracle in OraClient11g_home1_32bit.
Note The Oracle ODBC Driver is not installed as part of the standard Oracle Net
Client installation. Use one of the following methods to install the Oracle ODBC
driver:
• Perform a custom installation of Oracle Net Client and include the Oracle
ODBC Driver in the list of components to install
• Download the Oracle ODBC Driver from the Oracle website
5. Click Finish. The Oracle ODBC Driver Configuration window appears.
6. In the Data Source Name field, enter a name for the data source. The name must be
of the form Ora<hostname><SID>, for example:
OraHostPCSMDB
Where:
• HostPC is the name of the host PC
• SMDB is the Oracle System ID of the database
7. In the Description field, enter a short description for the data source.
8. In the TNS Service Name list, choose the Net Service Name of the database
associated with your SampleManager instance.
1. If your PC has a 32-bit operating system, from the Windows Control Panel, open
Administrative Tools and then run the Data Sources (ODBC) application.
On 64-bit operating systems, there are separate ODBC Data Source Administrators
for 32-bit and 64-bit ODBC data sources. SampleManager uses 32-bit data sources.
To open the 32-bit ODBC Data Source Administrator, run the following
application:
c:\windows\SysWow64\odbcad32.exe
The Create New Data Source window appears, showing a list of available drivers.
LimsHostPCSMDB
Where:
• HostPC is the name of the host PC
• SMDB is the Oracle System ID of the database
6. In the Description field, enter a short description for the data source.
7. In the Oracle Source field, select your Oracle DBC data source (page 164).
8. Click OK to save the data source and close the LIMS Setup dialog box.
The new data source appears in the ODBC Data Source Administrator.
2. Set up a SQL Server ODBC Data Source (page 164) that connects to your
SampleManager database.
3. Set up a SampleManager ODBC data source (page 165) that connects to the SQL
Server ODBC data source created in step 2.
4. Install LIMS Reporter (page 166).
1. If your PC has a 32-bit operating system, from the Windows Control Panel, open
Administrative Tools and then run the Data Sources (ODBC) application.
On 64-bit operating systems, there are separate ODBC Data Source Administrators
for 32-bit and 64-bit ODBC data sources. SampleManager uses 32-bit data sources.
To open the 32-bit ODBC Data Source Administrator, run the following
application:
c:\windows\SysWow64\odbcad32.exe
6. In the Server field, select the SQL Server that contains the target SampleManager
database.
7. Click Next.
8. Select the authentication method that SQL Server will use for the connection:
• With integrated Windows authentication – SQL Server will use the Windows
account of the currently logged-in user that is running the LIMS Reporter. If
you select this option, the Windows account for each user who will generate
reports must be granted appropriate access to the SQL Server database.
• With SQL Server authentication using a login ID and password entered by
the user – Enter a SQL Server login ID and password for the data source to use.
If you select this option, the SQL Server must have been configured to allow
SQL Server authentication.
9. Click Next.
10. Select the Change the default database to check box and select the database
associated with your target SampleManager instance.
11. Click Next.
The new data source appears in the ODBC Data Source Administrator window.
1. If your PC has a 32-bit operating system, from the Windows Control Panel, open
Administrative Tools and then run the Data Sources (ODBC) application.
On 64-bit operating systems, there are separate ODBC Data Source Administrators
for 32-bit and 64-bit ODBC data sources. SampleManager uses 32-bit data sources.
To open the 32-bit ODBC Data Source Administrator, run the following
application:
c:\windows\SysWow64\odbcad32.exe
3. Click Add.
The Create New Data Source window appears, showing a list of available drivers.
5. In the Data Source Name field, enter a name for the data source.
6. In the Description field, enter a short description for the data source.
7. In the Database Source field, select your SQL Server ODBC data source (page 164).
8. Click OK to save the data source and close the LIMS Setup dialog box.
The new data source appears in the ODBC Data Source Administrator.
1. In Windows Explorer, open the root folder for the LIMS Reporter kit.
2. Double-click Autorun.exe.
The only required component is the InfoMaker product itself; SampleManager does
not require SQL Anywhere.
After LIMS Reporter is installed, you must set up a database profile to connect to your
SampleManager ODBC data source.
The Database Profiles window appears, showing a list of installed database interfaces.
3. Select the ODB ODBC interface, and click New to create a new profile.
The Database Profile Setup window appears.
6. Select the new profile, and click Connect to test the connection.
7. If you selected the SampleManager ODBC data source in step 4, the
SampleManager Login Details dialog box appears, prompting for login details for use
with the SampleManager ODBC data source. Enter a SampleManager username and
password, and click OK.
8. If you are connecting to a SampleManager Oracle database, the Oracle ODBC
Driver Connect dialog box appears, prompting for login details for use with the
Oracle ODBC data source. Enter the Oracle username and password for your
SampleManager instance, and click OK.
You might need to contact your Oracle administrator for these details. Unless you
create a new SampleManager ODBC data source, you should not need to enter these
details again.
9. If you are connecting to a SampleManager SQL Server database, the SQL Server
ODBC Driver Connect dialog box appears, prompting for login details for use with
the SQL Server ODBC data source. Enter a suitable username and password for
your SQL Server database, and click OK.
You might need to contact your SQL Server administrator for these details. Unless
you create a new SampleManager ODBC data source, you should not need to enter
these details again.
10. LIMS Reporter connects to your SampleManager database. From the main menu,
select Tools > Database Painter to show the details of the database.
The Database window appears. See the documentation provided with LIMS
Reporter for more information.
When you next run LIMS Reporter and select Tools > Database Painter from the main
menu, the connection defined by the database profile will be used. If your database
profile uses the SampleManager ODBC data source, you will be prompted for a
SampleManager username and password.
Note If you are connecting to a SampleManager database for a first time, you might
be prompted for Oracle or SQL Server database login details. After a database profile
has been set up and you have connected for the first time, you should not be
prompted for these details again.
2. Install GhostScript (page 169) and add an appropriate link to the Path environment
variable (page 169).
http://www.adobe.com/products/reader/
Installing GhostScript
GhostScript enables InfoMaker to save reports in PDF format.
http://www.ghostscript.com/
If the SampleManager server has a 64-bit operating system, download and install both
the 32-bit and 64-bit versions of GhostScript.
After you have updated the Path environment variable, the PC must be rebooted.
2. Before you change the Path variable, we recommend that you make a copy:
a. In the System variables area of the Environment Variables window, select the
Path variable and click Edit.
The Edit System Variable dialog box appears.
b. In the Edit System Variable dialog box, select the contents of the Variable value
field.
c. Press CTRL+C to copy the details to the Windows clipboard.
d. Click Cancel to close the Edit System Variable dialog box.
e. In the System variables area of the Environment Variables window, click New.
The New System Variable dialog box appears.
f. In the Variable Name field, enter an appropriate name, for example, Path_copy.
g. In the Variable Value field, paste the copied details.
h. Click OK to accept the new entry.
3. In the System variables area of the Environment Variables window, select the Path
variable.
4. Click Edit.
5. Add the location of the gswin32.exe file to the list of locations in the Variable Value
field. Each value in the list is separated by a semicolon. The default location is:
C:\Program Files\gs\gs<version>\bin
9. Click OK to save the change and close the System Properties window.
10. Close down all active programs and reboot the system.
Note The name of the printer must be exactly as shown, with the same spaces and
capitalization.
If the PDF output appears in black and white, check that the Printer Preferences for the
Sybase DataWindow PS printer are configured to produce color output.
Note The PDF report generation process requires a Windows user account with
sufficient permissions to create and save the .pdf file. If errors are reported when
SampleManager attempts to save the .pdf file, set the Log On As properties of the
smdaemon service for the instance to use an account with administrator rights.
For more information, see the "Chromeleon Link" chapter in the SampleManager LIMS
Configuration Guide.
Contents
• Prerequisites
• Installing Chromeleon Link Web API
• Installing SampleManager Chromeleon Interface
• Chromeleon Link Add-In
Prerequisites
CAUTION To prevent potential loss of data, make a full backup of your system
before installing the Chromeleon link components.
Make sure all the following conditions are satisfied before you install the Chromeleon
Link components:
• SampleManager LIMS is installed and running correctly.
• Chromeleon CDS is installed and running correctly.
See the SampleManager LIMS 12.2 Release Notes for information about the version
of Chromeleon CDS required for the SampleManager LIMS Chromeleon Link
functionality.
• The Microsoft .NET Framework 4 is installed on the Chromeleon CDS application
server.
• The Microsoft .NET Framework 4.5.2 is installed on the Chromeleon CDS
application server.
Note The authentication and configuration settings for the Chromeleon Link Web
API are stored as an encrypted string and cannot be edited after installation. To
change the values after installation, repeat the installation process.
1. Make sure that all users are logged out of Chromeleon CDS.
7. Destination Folder
a. If you want to change the location where Thermo SampleManager Chromeleon
Link Web API will be installed, click Browse and select the location.
b. Click Next.
8. Authentication
a. If User Mode is enabled on your Chromeleon CDS, select Enable User Mode.
b. If User Mode is enabled on your Chromeleon CDS, enter the name and
password of the Chromeleon CDS user account you want the Chromeleon Link
to use.
If User Mode is enabled and you do not specify a Username and Password, the
Chromeleon CDS user name will be obtained from the PERSONNEL record
for the SampleManager user associated with each session. Users will be
prompted to enter their Chromeleon password when they perform a task that
uses the Chromeleon Link Web API.
c. Make a note of the information you have entered on this page. The
authentication information is stored as an encrypted string when the
Chromeleon Link Web API is installed.
d. Click Next.
9. Service Configuration
a. Enter a name for the Windows service that will be created for the Thermo
SampleManager Chromeleon Link Web API.
b. Specify the port that the service will use. The default value is 8082.
c. If you want the Chromeleon Link to use the https protocol, select Enable
HTTPS.
If Enable HTTPS is cleared, the Chromeleon link will use the HTTP protocol.
d. Make a note of the information you have entered on this page. The
configuration information is stored as an encrypted string when the Chromeleon
Link Web API is installed.
e. Click Next.
11. Completed the SampleManager Chromeleon Link Web API Setup Wizard
Click Finish.
5. Enter the login credentials of the account you want the service to use.
6. Click OK.
If the account you specified in step 5 does not have administrator rights on the
server, the service fails to start and the following error appears in the event log:
8. To resolve the error, grant the user account permission to listen on the Chromeleon
Web API port:
a. Log in to the server as an administrator.
b. Open a command prompt.
c. Enter the following command:
netsh http add urlacl url=<proto>://*:<port>/ user=<User/Group>
listen=yes
Where:
Note The configuration settings for the SampleManager Chromeleon Interface are
stored as an encrypted string and cannot be edited after installation. To change the
values after installation, repeat the installation process.
1. Make sure that all users are logged out of Chromeleon CDS.
7. Destination Folder
a. If you want to change the location where SampleManager Chromeleon Interface
will be installed, click Browse and select the location.
b. Click Next.
8. Configuration
a. Enter the username and password of the SampleManager user that you want the
SampleManager Chromeleon Interface to use. The username setting is
mandatory.
b. In the Web API Address prompt, specify the address, including the port
number, of the REST interface of the SampleManager WCF service for the
SampleManager LIMS instance that you want to connect to. This setting is
mandatory.
For example:
http://localhost:56105
c. In the Chromeleon Server ID prompt, specify the identity of the Chromeleon
entity in SampleManager LIMS that you want to use as the default when the
interface searches for instruments and analyses in SampleManager. This value is
optional.
d. If you want to disable Ready Check warnings that occur when multiple
instruments or analyses match mapping criteria, select Allow Multiple
Mapping. The default setting is False.
e. Make a note of the information that you have entered on this page. The
configuration settings are stored as an encrypted string when the
SampleManager Chromeleon Interface is installed.
f. Click Next.
11. Clear any Add-In functions that you do not want to activate and click OK. By
default, all Add-In functions are selected. For more information about the Add-In
Functions, see the "Chromeleon Link" chapter in the SampleManager LIMS
Configuration Guide.
If you chose not to activate an Add-In function that you need later, you must
reinstall SampleManager Chromeleon Interface and select the desired Add-In
function.
12. Make sure that Chromeleon CDS has detected the SampleManager Chromeleon
Interface add-in:
a. Start Chromeleon CDS and log in.
b. Launch the eWorkflow Wizard. For detailed information about this wizard, see
the Chromeleon CDS documentation.
c. On the Sample Configuration page of the wizard, make sure that there is a
Select Batch button in the upper right pane.
If the Select Batch button is visible, Chromeleon CDS has detected the
SampleManager Chromeleon Interface add-in. The installation process is
complete.
d. If the Select Batch button is not visible, close the eWorkflow Wizard.
e. Close Chromeleon CDS.
f. In Windows Explorer, delete the following folder and all its subfolders:
C:\ProgramData\Dionex\Chromeleon\Addins
Chromeleon will recreate the Addins folder next time it starts. This step makes
Chromeleon CDS detect the SampleManager Chromeleon Interface add-in.
2. Open the list of applications and select Thermo Chromeleon 7 > Administration
Console.
3. Expand Organizational Units and Global. (only required if Organizational Units are
enabled)
5. From the A sequence will be ready for LIMS transfer list, select the desired option.
Available options are:
• never
• when the sequence is submitted
• when the sequence is reviewed
• when the sequence is approved
When the electronic signature of a sequence has the status selected, the
SampleManager Chromeleon Interface sets the Send Approved flag of the sequence
in SampleManager LIMS to Yes. If the communication between Chromeleon CDS
When the Data Manager functionality stores data, it packages all the original files
associated with a data set into a single zip file that is stored in a specified location on the
Data Manager server. During the packaging process, Data Manager can convert the
original data into Generalized Analytical Markup Language (GAML), a neutral format
that offers long-term data preservation independent of the original instrument software.
You can configure Data Manager to extract information from the data during the
conversion process. The extracted information is stored as metadata linked to the data
package, which you can use to search archived data in future.
The SampleManager entity types that support the Data Manager functionality are
included in the core SampleManager Server installation. The Data Manager functionality
also requires a set of Windows services and supporting applications, such as file
converters, which must be installed separately on the appropriate machines in your
SampleManager system. This chapter describes the installation of the Data Manager
components. For information about configuring and using the Data Manager feature, see
the "Data Manager" chapters in the SampleManager LIMS Configuration Guide.
Contents
• Prerequisites
• Install and Configure Data Manager Components
Overview
• Run the Data Manager Install Utility
• Install the Data Manager Data Provider Service
• Data Manager Components
• Install Data Manager Components
Prerequisites
Before you install and configure the Data Manager components, make sure of the
following:
• SampleManager is successfully installed and working.
• All users have logged out of SampleManager.
• You have obtained and installed a license for the Data Manager capture sources that
you intend to use. If you do not have the correct license, the Data Manager feature
will not work correctly. For more information about licenses, see the
"Post-Installation Tasks" chapter in the SampleManager Installation Guide. For more
information about capture sources, see "Data Manager Packaging Configuration" in
the SampleManager LIMS Configuration Guide.
CAUTION To prevent potential loss of data, we recommend that you make a full
backup of your system before you install the Data Manager components.
Logging out and stopping processes makes certain that SampleManager updates correctly
when processes restart and users log in.
To assure a successful installation, perform these procedures and steps in the order they
appear.
Multiple SampleManager instances on your server can share a single set of Data
Manager components. Do not repeat this step for each SampleManager instance.
To upgrade the Data Manager components, follow the steps for a new installation in this
chapter.
Note After installation of a new version of Data Manager is complete, the previous
versions will not work.
If you are upgrading from a previous version of Data Manager, run the following steps to
adjust the settings on a few menu items.
1. From the SampleManager Navigator, select System Folders > Global Table
Defaults.
2. In the Explorer, right-click Data Package and select Table Defaults > Modify. The
Table Defaults window appears.
1. Log in to the SampleManager instance that you want to use the Data Manager
functionality.
2. From the main menu, select File > Run. The Run window appears.
3. Enter GRL $DM_INSTALL and click OK. A message appears that asks if you want
to compile the Data Manager VGL Reports.
4. Click Yes.
1. In Windows Explorer, navigate to the Exe folder for the SampleManager instance.
The default path for this folder is:
C:\Thermo\SampleManager\Server\<instance>\Exe
Where <instance> is the name of your SampleManager instance.
2. Right-click InstallDataManagerDataProviderWindowsServiceNoStart.bat and
select Run as Administrator.
A Command prompt window opens and messages appear as the installation
progresses. When the process completes, the message "Press any key to continue"
appears.
3. Check the window for errors, and then press any key to close the window.
– Upload .zip files from the agent computer to the server computer.
– Download .zip files from the server computer to the agent computer.
– Create .zip file checksums.
– Remap existing data packages.
For descriptions of the security and configuration items that are installed with the Data
Manager module, see "Data Manager Configuration Items" in the "Configuration"
chapter in the SampleManager LIMS Configuration Guide.
Note The instructions in this section describe how to install Data Manager
components on a 64-bit Windows system. If you are installing on a 32-bit system,
amend the installation path.
3. Click Setup.
A progress bar appears as the necessary files are unzipped for the installation process.
When the files are ready for installation, the Data Manager InstallShield Wizard runs
and the Preparing Setup page appears.
When the preparation has completed, the Welcome page appears.
Figure 9-2. InstallShield Wizard – Welcome page
5. When you have read the terms and conditions on the License Agreement page,
accept the terms of the license agreement, and click Next to continue.
6. Accept the default location for the software installation, or browse for an alternative
location. The default destination folder is:
C:\Program Files (x86)\Thermo\Data Manager
When the installation is complete, the InstallShield Wizard Complete page appears.
Figure 9-8. InstallShield Wizard – Complete page
11. Click Finish to close the InstallShield Wizard. The InstallShield Wizard for the
Envision GAML Viewer opens. See Install the Envision GAML Viewer on page 197
for details.
Note The InstallShield Wizard for the Envision GAML Viewer opens automatically
at the end of a standard Data Manager Client installation.
1. After successful completion of the Data Manager installation, the Welcome page of
the Envision GAML Viewer InstallShield Wizard appears. Click Next to continue.
Figure 9-9. InstallShield Wizard – Welcome page
2. When you have read the terms and conditions of the License Agreement, accept the
terms in the license agreement, and then click Next to continue.
3. Accept the default location for the software installation, or browse for an alternative
location. The default destination folder is:
C:\Program Files (x86)\Thermo\Envision
The Installing GRAMS Envision Viewer page appears, showing the progress of the
installation.
Figure 9-13. InstallShield Wizard – Installing GRAMS Envision Viewer page
When the installation is complete, the InstallShield Wizard Complete page appears.
6. Click Finish to close the InstallShield Wizard. The InstallShield Wizard for the
GRAMSShellHandlers64 component opens. See Install the
GRAMSShellHandlers64 Component (page 199) for details.
If you install the GAML Viewer on a 32-bit Windows system, the 32-bit version of
the GRAMS Shell Extension Handlers component is installed instead of
GRAMSShellHandlers64. The InstallShield Wizard for GRAMS Shell Extension
Handlers contains the same pages as the InstallShield Wizard for
GRAMSShellHandlers64.
To install GRAMSShellHandlers64
1. After successful completion of the GAML Viewer installation, the Welcome page of
the GRAMSShellHandlers64 InstallShield Wizard appears. Click Next to continue.
Figure 9-14. InstallSheld Wizard – Welcome page
2. When you have read the terms and conditions of the License Agreement, accept the
terms in the license agreement, and then click Next to continue.
When the installation is complete, the InstallShield Wizard Complete page appears.
4. Click Finish to close the InstallShield Wizard. The InstallShield Wizard for the
GRAMS converters opens. See Install the GRAMS Converters on page 202 for
details.
Note The InstallShield Wizard for the GRAMS converters opens automatically at
the end of a standard Data Manager installation.
1. After successful completion of the Data Manager installation, the Welcome page of
the GRAMS Converters Package InstallShield Wizard appears. Click Next to
continue.
Figure 9-18. InstallShield Wizard – Welcome page
3. The Ready to Install the Program page appears. Click Install to start the installation
process.
Figure 9-20. InstallShield Wizard – Ready to Install the Program page
In some situations, the following type of message might appear during the
installation.
Figure 9-22. InstallShield Wizard – Files In Use message
When the installation of the GRAMS converters is complete, the final page of the
InstallShield Wizard appears.
Figure 9-23. InstallShield Wizard Completed page
5. On the License Agreement page, accept the terms of the license agreement and click
Next.
6. On the Setup Type page, select a setup type and click Next.
Figure 9-25. Setup Type page
8. When the installation completes, the Completed page appears. Click Finish.
Figure 9-27. Bruker CompassXtract installation completed
1. From the Windows Start menu, select Thermo Data Manager > Data Manager
Configuration.
3. In the Messaging Service Port Number field, enter the port number for the
Messaging service.
4. Click Save.
5. If necessary, use the buttons to the right of the Service Status field to start, restart, or
stop the Messaging service.
If your application server has multiple SampleManager instances that use the Data
Manager functionality, each SampleManager instance requires its own Data Provider.
Note The Data Manager Configuration window only shows the configurations that
are installed on the system where the tool is run. If you run this tool on a client
system, you will not see the windows for the Messaging, Provider, Server, and Agent
items.
1. From the Windows Start menu, select Thermo Data Manager > Data Manager
Configuration.
The Data Manager Configuration window appears.
3. In the Port Number field, enter the port number for communication with the Data
Manager server. Each SampleManager Data Provider must have a unique Port
Number.
4. Make a note of the Port Number you have specified for the instance. You will need
this value when you configure the Data Manager Server.
5. In the Messaging Host Name field, enter the messaging host name.
6. In the Messaging Port Number field, enter the messaging port number.
The Service Status field shows the status of the Data Provider.
7. Click Save.
8. If necessary, use the buttons to the right of the Service Status field to start, restart, or
stop the Data Provider.
1. From the Windows Start menu, select Thermo Data Manager > Data Manager
Configuration.
The Data Manager Configuration window appears.
4. In the Data Provider property, click the ellipsis button . The SMDataProvider
Collection Editor appears.
Figure 9-31. SMDataProvider Collection Editor
8. In the Data Manager Configuration window, the Service Status field shows the
status of the Data Manager server. If necessary, use the buttons to the right of the
Service Status field to start, restart, or stop the Data Manager server.
1. From the Windows Start menu, select Thermo Data Manager > Data Manager
Configuration.
3. In the Application Settings tab, select one of the following options from the Default
Endpoint list:
• TCP
• HTTP
This option defines the default endpoint to use if more than one endpoint is
available.
4. If applicable, in the Data Manager Server Host Name field, enter the host name of
the Data Manager server.
5. If applicable, in the Data Manager Server TCP Port Number field, enter the TCP
port number of the Data Manager server.
6. If applicable, in the Data Manager Server HTTP Port Number field, enter the
HTTP port number of the Data Manager server.
Note The Data Manager TCP Port Number and Data Manager HTTP Port
Number fields are only used when the server is accessed through the Data Manager
API.
7. In the Data Manager Server Name format field, select Hostname Only (default
setting) or Fully Qualified Domain Name.
Note The fully qualified domain name is useful in environments where there are
multiple domains that contain computers with the same name.
8. Click Save.
The packaging agent scans the folders specified in the packaging rules defined for the
agent computer, searching for key files to package. The packaging agent can also locate
and delete previously packaged files, based on the criteria set in the packaging schedule
specified in each packaging rule.
For more information, see the "Extracting Data" chapter of the Data Manager User
Guide.
3. In the Services window, double-click the Data Manager Packaging Agent entry.
8. In the Confirm Password field, reenter the password, and then click OK.
The Data Manager Packaging Agent parameter values (username, password, or database)
are configured using the Data Manager Packaging Agent Configuration window. See
Configure the Packaging Agent on page 217 for details.
1. From the Windows Start menu, select Thermo Data Manager > Data Manager
Configuration.
3. In the Application Settings tab, enter the following connection information for the
Data Manager server:
• Default Endpoint – Enter the default endpoint to use if more than one endpoint
is available. Available values are: TCP or HTTP.
• Data Manager Server Host Name – Enter the host name of the Data Manager
server.
• Data Manager Server TCP Port Number – If applicable, enter the TCP port
number of the Data Manager server.
• Data Manager Server HTTP Port Number – If applicable, enter the HTTP port
number of the Data Manager server.
• Data Manager Server Name Format – Enter Hostname Only (this option is the
default setting). If necessary, you can change the Data Manager Server Name
format to "Fully Qualified Domain Name", to include the domain name as part
of the server name. Including the server name can be useful in environments
where there are multiple domains that contain computers with the same name.
4. Enter the connection details for the Data Manager Messaging service:
• Messaging Host Name – Enter the host name for connecting to the Data
Manager Messaging service.
• Messaging Port Number – Enter the port number for connecting to the Data
Manager Messaging service.
The Service Status field shows the status of the Packaging Agent.
5. Click Save.
6. If necessary, use the buttons to the right of the Service Status field to start, restart, or
stop the Packaging Agent.
Note System Tracing is NOT one setting that is read by all the systems. System
Tracing must be configured for each system that contains one or more of the following
Data Manager components: Data Manager Server, Data Manager Agent, and Data
Manager Client.
1. From the Windows Start menu, select Thermo Data Manager > Data Manager
Configuration.
The Data Manager Configuration window appears.
2. In the Configurations pane, select System Tracing.
Figure 9-35. Data Manager Configuration window – System Tracing
3. In the Application Settings tab, set the following values for the Data Manager
Tracing section:
a. Trace Level – Enter the trace level for log file production, the following values
are available: Error, Warn, Info, and Debug.
b. Trace File – Enter the path to the location where the log files will be stored.
Browse to locate the correct destination for the files.
c. Maximum File Size – Enter the maximum permitted file size (in Mb) for a
single log file.
4. In the GRAMS Converter and Component Tracing section, set the following values:
a. Trace Level – Enter the trace level for log files produced by the GRAMS
converters, or any associated components. The following values are available: (0)
Errors, (1) Warnings, (2) Information, (3) Debug, and (4) Verbose.
b. Trace File – Enter the path to the location where the log files will be stored.
Browse to locate the correct destination for the files.
For each Data Manager Client system, perform the following steps to license the
GRAMS Envision viewer
1. From the Windows Start menu, select Thermo GRAMS Suite > Envision.
The License Failure dialog box appears for the first installation of GRAMS Envision.
Figure 9-36. License Failure dialog box
When Envision has started, select Help > About GRAMS Envision.
4. Select Specify License Server, enter the name of the license server, and click OK.
The Instrument Data File Converters Help is located in the following folder of the
SampleManager LIMS installation kit:
Oracle Setup
This chapter outlines the installation and configuration of Oracle 12c on a 64-bit
Windows server before installing SampleManager.
For detailed information about installing and configuring Oracle, see the documentation
provided with Oracle. For more information about how SampleManager uses an Oracle
database, see the "Data Storage and Handling in Oracle" chapter in the SampleManager
LIMS System Administration Guide.
Contents
• Installing and Configuring Oracle for Use with
SampleManager
• Configuring a Connection from the Oracle NET
Client to the Oracle Server
• Installing the Oracle ODBC Driver
• Example Installation and Configuration
The basic procedure for installing and configuring Oracle for use with SampleManager
is:
4. Create a tablespace in the new database that will contain your SampleManager data.
If you can supply the sys account password to the SampleManager Add Server
Instance wizard, you can skip this step and let the Add Server Instance wizard create
the tablespace.
5. Create a user in the new database that SampleManager Server will use.
If you can supply the sys account password to the SampleManager Add Server
Instance wizard, you can skip this step and let the Add Server Instance wizard create
the user.
6. If an Oracle Net Listener was not created during the Oracle installation process,
create a Listener.
7. Make a note of the port number used by the Listener on the Oracle database server.
8. Install the 32-bit Oracle Net Client on the machine that will host the
SampleManager server software. Make sure that the 32-bit Oracle ODBC driver is
included in the installed components, as it is required by LIMS Reporter.
You must install a 32-bit Oracle Net Client on the application server PC, even if the
application server PC is also hosting the Oracle database. Without a 32-bit Oracle
Net Client, the SampleManager server instance will not be able to access its Oracle
database.
9. Configure a connection between the 32-bit Oracle Net Client that you installed in
step 5, and the Oracle Net Listener for the Oracle database server.
12. Configure the security of your Oracle database to grant access to the account that
will be used by LIMS Reporter to generate reports from the database.
13. Install LIMS Reporter and create the ODBC data sources required to connect to
your database.
14. Create a database profile that connects LIMS Reporter to your SampleManager
database in Oracle.
We recommend that you set the OPEN_CURSORS parameter to 700. For more
information, see your Oracle documentation.
Creating a Tablespace
A SampleManager instance requires a tablespace for its data.
If you can supply the sys account password during the instance creation process, the
SampleManager Add Server Instance wizard can create the tablespace for you. Otherwise,
you must create the tablespace before you create the instance.
Use the Oracle tools to create a tablespace. The following SQL statement creates a
suitable tablespace:
create tablespace VGSM_DB
datafile 'filename'
SIZE 100M REUSE
AUTOEXTEND ON NEXT 50M
MAXSIZE 500M;
Where filename is the path and file name of the file associated with the tablespace.
The default tablespace for tables in the SampleManager instance is defined in the
table_defaults section of the structure.txt file for your instance. For example:
table_defaults
oracle_location 'VGSM_DB' ;
If your instance will use a single tablespace in the Oracle database for all SampleManager
data, the Add Server Instance wizard can update the table_defaults section of
structure.txt to match the tablespace name you supply to the wizard. If you create
multiple tablespaces for your SampleManager data, you must edit structure.txt manually
to specify the default tablespace and the tablespace for individual tables and indexes
before running the Add Server Instance wizard.
You can use the oracle_location attribute in a table definition in structure.txt to specify
the tablespace that the table will be created in. For example:
TABLE my_table;
ORACLE_LOCATION 'MYTBLS_DB';
The oracle_specific attribute can be used to add further parameters to a table or index
definition for use by the Oracle database, such as a storage clause.
For more information about customizing the database using structure.txt, see the
"Customizing the Database Structure" chapter in the SampleManager LIMS
Configuration Guide.
Creating a User
The SampleManager instance requires an Oracle user account to connect to the database.
If you can supply the sys account password during the instance creation process, the
SampleManager Add Server Instance wizard can create the user for you. Otherwise, you
must create the user before you create the instance.
Use the Oracle tools to create the user in the database that your SampleManager will use.
Grant the following privileges to the user:
• CREATE SEQUENCE
• CREATE SESSION
• CREATE TABLE
• CREATE VIEW
• SELECT_CATALOG_ROLE
Give the user an unlimited quota on the tablespaces that will contain the
SampleManager data.
The following example shows the SQL statements generated by the SampleManager
Setup Wizard when it creates an Oracle user:
GRANT CREATE SESSION TO VGSM IDENTIFIED BY VGSM;
CREATE PROFILE VGSM LIMIT FAILED_LOGIN_ATTEMPTS UNLIMITED
PASSWORD_LIFE_TIME UNLIMITED;
ALTER USER VGSM PROFILE VGSM;
ALTER USER VGSM QUOTA UNLIMITED ON VGSM_DB DEFAULT TABLESPACE VGSM_DB;
GRANT CREATE TABLE TO VGSM;
GRANT CREATE VIEW TO VGSM;
GRANT CREATE SEQUENCE TO VGSM;
GRANT SELECT_CATALOG_ROLE TO VGSM;
In the example, the user is called VGSM. The tablespace that stores the SampleManager
data is called VGSM_DB. This example creates a profile called VGSM that specifies an
unlimited number of failed login attempts and unlimited password lifetime. The VGSM
profile is assigned to the VGSM user.
After the Oracle Net Client is installed, you must configure its connection to your
Oracle Server database:
• Configuring Naming Methods (page 228)
• Creating a Local Net Service Name (page 229)
Note If the database that SampleManager will use is a pluggable database (PDB) in
a multitenant container database (CDB), the connection must target the PDB. For
more information about multitenant architecture in Oracle 12c, see your Oracle
documentation.
1. From the Windows Start menu, run the Oracle Net Configuration Assistant.
The default location for this option is Oracle - [home name] > Configuration and
Migration Tools > Net Configuration Assistant.
The Welcome page of the Oracle Net Configuration Wizard appears again.
To create a Local Net Service Name, and then test its connection to the database
1. From the Windows Start menu, run the Oracle Net Configuration Assistant.
The default location for this option is Oracle - [home name] > Configuration and
Migration Tools > Net Configuration Assistant.
4. Enter the Service Name of your database and click Next to continue. If your
database is a pluggable database (PDB) in a multitenant container database (CDB),
enter the name of the service associated with the PDB. For more information about
multitenant architecture in Oracle 12c, see your Oracle documentation.
The Net Service Name Configuration, Select Protocols page appears.
8. The Oracle Net Configuration Assistant tries to connect to the specified database
using the information you supplied, and displays the results on the next page.
The Net Service Name Configuration, Net Service Name page appears.
10. Enter a name for the Net Service Name, and click Next.
11. We recommend that the Net Service Name is the same as the service name of your
database. You set the database service name on the Service Name page of the wizard.
12. The next page asks whether you want to configure another net service name. If you
want to connect to more servers, select Yes and click Next to repeat the process.
Otherwise, select No and click Next to continue.
The Net Service Name Configuration Done page appears.
13. Click Next to continue.
The Welcome screen of the Oracle Net Configuration Assistant appears again.
3. On the Specify Installation Location page, set the Software Location prompt to the
existing Oracle client folder.
4. On the Available Product Components page, select the Oracle ODBC Driver check
box.
5. Accept the default settings on the remaining pages of the wizard to install the Oracle
ODBC driver.
If more than one Oracle ODBC driver is installed on the application server,
SampleManager will automatically use the latest version.
The Local Net Service Name defines the connection to the database on computer A.
For detailed information about installing and configuring SQL Server, see the
documentation provided with SQL Server. For more information about how
SampleManager uses a SQL Server database, see the "Data Storage and Handling in SQL
Server" chapter in the SampleManager LIMS System Administration Guide.
Contents
• Installing and Configuring SQL Server for Use with
SampleManager
• Configuring SQL Server Security
• Recommended Database Options
The basic procedure for installing and configuring SQL Server for use with
SampleManager is:
1. Install SQL Server on your database server.
2. Create a new database that will be used to store the data for a SampleManager
instance.
5. If the application server is a different machine than the database server, install the
SQL Server Client Tools Connectivity feature on your application server.
6. If the application server is a different machine than the database server, make sure
that the SQL Server Client Tools on the application server can connect to the SQL
Server database that SampleManager will use.
7. Install SampleManager Server on your application server.
8. Create a SampleManager instance that uses the SQL Server database created in step
2.
10. Use the create_structure and convert_table utilities to alter the SampleManager table
definitions in the SQL Server database so that they use the filegroups and partitions
specified in structure.txt.
Note Convert_table must be run from the command line using the rebuild or
newtable mode if you have changed any table properties that are read-only in SQL
Server, such as the filegroup used to store the table data.
For more information, see the "Customizing the Database Structure" chapter in the
SampleManager LIMS Configuration Guide.
In SampleManager versions older than SampleManager 12.2, the default value of the
sqlserver_use_nvarchar attribute in the structure.txt database definition file was FALSE.
When sqlserver_use_nvarchar is FALSE, fields in the SampleManager database that store
strings have the text datatype. Strings are stored as non-Unicode characters. The Imprint
reporting tool for LIMS Reporter (page 157) is not compatible with
sqlserver_use_nvarchar being set to True. LIMS Reporter is not included in the
SampleManager installation kit and is only available in upgraded SampleManager
instances.
If you are creating a SQL Server database that will contain data created in a
SampleManager instance that did not store strings as Unicode, or if you require LIMS
Reporter, configure your database to store strings as non-Unicode characters.
3. Use the create_structure and convert_table utilities to alter the SampleManager table
definitions in the SQL Server database so that they use the filegroups and partitions
specified in structure.txt.
Note Convert_table must be run from the command line using the rebuild or
newtable mode if you have changed any table properties that are read-only in SQL
Server, such as the filegroup used to store the table data.
For more information, see the "Customizing the Database Structure" chapter in the
SampleManager LIMS Configuration Guide.
SampleManager security features, such as groups and roles, are managed by the
SampleManager server when connecting through the SampleManager client, and by the
SampleManager ODBC data source when connecting through LIMS Reporter. Logins
used to connect to the SQL Server database require the minimum permissions described
in the following sections:
• Permissions Required to Create a New SampleManager Instance in the Database
(page 238)
• Permissions for Connecting through SampleManager Client (page 238)
• Permissions for Connecting through SQL Server ODBC Data Source (page 239)
Details of any logins that allow connection to the SQL Server database must be kept
secure to prevent users from bypassing the SampleManager security settings and
changing records in the database directly.
These roles allow the SampleManager Add Server Instance wizard to create a new
SampleManager instance.
If you want to use the Windows LocalSystem account to create your SampleManager
instance database, add the roles to the NT AUTHORITY\SYSTEM login in SQL Server
Management Studio.
Database permissions:
• CREATE TABLE
• CREATE VIEW
ANSI_NULLS ON
ANSI_PADDING ON
ANSI_WARNINGS ON
ARITHABORT ON
QUOTED_IDENTIFIER ON
CONCAT_NULL_YIELDS_NULL ON
NUMERIC_ROUNDABORT OFF
ALLOW_SNAPSHOT_ISOLATION ON
READ_COMMITTED_SNAPSHOT ON
Index
A G
Add Server Instance Wizard GhostScript
Oracle, 26 adding to the Path, 169
SQL Server, 66 installing, 169
Adobe Acrobat Reader
installing, 169
Adobe PostScript printer driver
I
InfoMakersee LIMS Reporter, 157
installing, 172
architecture, 2 installation
overview, 15
instances
C connecting to, 119
Chromeleon Link, 173 creating, 26, 66
Chromeleon Link AddIn, 183 deleting, 55, 93
Chromeleon Link Web API, 175 managing connections, 123, 124
ClickOnce deployment, 107 proxy login, 121
client side reporting, 160, 164
cross tab reports, 118 L
licensing
D installation details file, 100, 101
database profile installing licenses, 101
connecting to the database, 168 installing Thermo Licensing Server, 25, 65, 98
setup, 166 LIMS Reporter
Delete Server Instance Wizard database profile, 166
Oracle, 55 installing, 157, 166
SQL Server, 93 installing on client, 160, 164
deployment, 5 installing on server, 160, 163
example Oracle 64-Bit configuration, 231 PDF reports, 168, 172
pre-configured servers, 123, 126 LMTOOLS, 100
F M
firewall settings, 105 manage servers window, 124
FLEXnet licensing, 25, 65, 98 manual upgrade, 144, 146
LMTOOLS, 100 identifying files, 146
message.txt, 148
required tools, 144
T
tab reports, 118
Thermo Licensing Server, 25, 98
timezone settings, 105
U
upgrade.log, 146
upgrading, 129
manual procedures, 144, 146
menu items, 151
message.txt, 148
SampleManager client, 149
SampleManager remote services, 144
SampleManager server, 129, 131
structure.txt, 145