0% found this document useful (0 votes)
945 views

Mesa Install w32 Binary

Uploaded by

$rinivas varma
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
945 views

Mesa Install w32 Binary

Uploaded by

$rinivas varma
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 16

MESA Software

Installation Guide
MS Windows Binary Version

Electronic Radiology Laboratory


Mallinckrodt Institute of Radiology
510 South Kingshighway Blvd.
St. Louis, MO 63110
314.362.6965 (Voice)
314.362.6971 (Fax)

Version 10.9.0
14-November-2006
MESA Installation: Windows Binary

1 Introduction..............................................................................................................1
1.1 Target Directory...........................................................................................1
1.2 Storage Directory .........................................................................................2
1.3 Disk Space ...................................................................................................2
1.4 Uninstalling Previous Versions....................................................................2
2 MESA Internal Software Packages..........................................................................4
2.1 MIR Central Test Node (CTN) Software.....................................................4
2.2 HL7IMEXA .................................................................................................4
2.3 Microsoft SQL Server..................................................................................4
2.4 Xerces C.......................................................................................................4
2.5 Apache Tomcat Web Server ........................................................................5
2.6 ImageMagick ...............................................................................................5
3 Installation from Compiled Binaries........................................................................6
3.1 Database Installation....................................................................................6
3.2 Perl Installation ............................................................................................7
3.3 Install Java ...................................................................................................7
3.4 Apache Tomcat Installation .........................................................................8
3.5 OpenLDAP ..................................................................................................8
3.6 Agfa/Philips DVT ........................................................................................9
3.7 ImageMagick ...............................................................................................9
3.8 MESA Installation .......................................................................................9
4 Build Databases .....................................................................................................11
5 Install the MESA Storage Directory ......................................................................11
6 Runtime Notes .......................................................................................................13
7 Installation Test: MESA Class A Tests .................................................................14
7.1 MESA Test 1: Installation Test..................................................................14
MESA Software Installation: Windows Binary
______________________________________________________________________________

1 Introduction
This document describes the installation procedure for MESA software for select MS Windows
systems (NT 4.0, Windows 2000). Users reading this document have chosen to install the MESA
software using pre-compiled binaries. Installation instructions for Unix binaries or from source
code are found in other documents.

Check Task # Task Section


mark Reference (this
document)
1 Verify operating system compatibility for MESA test
tools
2 Decide upon the target directory structure you will
use (or use defaults)
3 Verify available disk space
4 Verify previous versions of MESA test tools are not
installed
5 Install Microsoft SQL Server (server license, not
client)
6 Create SQL ODBC logins and passwords
7 Install PERL
8 Install PERL module - date
9 Install the Sun Java 2 Software Development Kit
10 Install MESA Test Tool software and scripts
(includes necessary CTN software)
11 Build SQL database tables
12 Install the MESA Storage files
13 Create Environment Variables
14 Begin executing test scripts by referring to IHE Test
Plan documents

1.1 Target Directory


MESA is designed to be installed in a target directory specified at build time. We use the
environment variable MESA_TARGET for this directory; the default value is D:\mesa for
Windows NT and Windows 2000 systems. Once the installation procedure is complete, all
software depends only on executables, configuration files, data files in the target directory and
files in the storage directory (see 1.2).

The target directory contains these subdirectories:


bin The compiled executable programs
db Files for controlling database operations (Radiology base)
lib Shared libraries loaded at runtime

_____________________________________________________________________________

-1-
Version 10.9.0 14-Oct-2006
MESA Software Installation: Windows Binary
______________________________________________________________________________

logs Logfiles for all MESA server applications


runtime Configuration files for applications
mesa_tests Scripts/data for test protocol
webmesa A holding directory used for the second stage of the installation
process.

1.2 Storage Directory


The MESA storage directory is used to store messages and datasets received from peer
applications. For example, the MESA Image Manager will store images received from
modalities in this directory. The default for this is D:\mesa\storage.
The location of this directory is recorded in the environment variable MESA_STORAGE. We
separate this from the target directory to give you more control over disk partitions on your
system. The space required for this directory depends on the tests you perform; 100 slices of CT
data require much more space than one small Nuclear Medicine study.

1.3 Disk Space


Users installing the MESA software will need to be aware of the disk requirements for the
system. The table below summarizes the disk requirements for various parts of the system. If
you want to use the default target directory and you have insufficient disk space in that partition,
you can use soft links in the file system.

Operating System Software Space (MB)


Windows XP, 2000, 2000 Server Perl 30
Windows XP, 2000, 2000 Server SQL Server 200
Windows XP, 2000, 2000 Server Java JDK 55
Windows XP, 2000, 2000 Server MESA Installation in target directory 50
Windows XP, 2000, 2000 Server MESA Source Code when compiled (can be 175
deleted after installation)

1.4 Uninstalling Previous Versions


There are no incremental upgrades to the MESA software. Each installation writes over the top
of the previous installation (unless you choose to retain the old version in a separate directory).
To remove a previous version:
• cd %MESA_TARGET%\db
• perl drop_mesa_tables.pl <sa login> <sa password> <server>
• Use Windows Explorer to delete all directories in %MESA_TARGET%

The first two steps remove existing MESA databases. The parameters <sa login> and <sa
password> refer to the system administrator account for SQL Server. The <server> parameter is
passed to the isql command and identifies the server name. If you are using interactive SQL
(isql) with these parameters, the syntax is:

_____________________________________________________________________________

-2-
Version 10.9.0 14-Oct-2006
MESA Software Installation: Windows Binary
______________________________________________________________________________

isql –U <sa login> -P <sa password> -S <server>


For example:
isql –U ctn –P ctn –S TBALL

The last step removes the installed binaries, libraries and data files.

_____________________________________________________________________________

-3-
Version 10.9.0 14-Oct-2006
MESA Software Installation: Windows Binary
______________________________________________________________________________

2 MESA Internal Software Packages


The MESA libraries and applications are built on top of several other software packages. This
section only describes those packages that are compiled into the MESA software. Sections 4 and
5 will describe other software packages (compilers) used to build MESA.

2.1 MIR Central Test Node (CTN) Software


The MIR Central Test Node (CTN) software is a public domain DICOM implementation that
was originally funded by the RSNA and is maintained by MIR. This software is written in the
“C” programming language and provides libraries that support various parts of the DICOM
Standard or natural applications of the DICOM Standard. These include Information Object
creation, encoding and parsing, network operations, DIMSE services and network operations.
The CTN software also provides a number of simple test programs (transmit this image) and
more complete applications (image server).

An extension to the CTN software called JAVACTN is used by the MESA software. A small set
of Java classes are used to support some DICOM operations, such as Information Object
manipulation. This software uses the Java Native Interface (JNI) to provide access to the CTN C
libraries.

The CTN software requires some updates to satisfy the MESA design goals. An updated version
of the CTN software is included with the MESA distribution.

2.2 HL7IMEXA
HL7IMEXA is a table-driven HL7 message builder/parser that has its origins at Columbia
University. The Columbia implementation was called HL7IMEX. The software was modified
by Allen Rueter of MIR and renamed HL7IMEXA. This software is written in the “C” language
and supports message building and parsing, but no network operations. Minor changes are made
to this package to support the C++ environment used by MESA and to correct some runtime
problems.

2.3 Microsoft SQL Server


This relational database is a commercial product from the Microsoft Corporation. This is the
database used by the MESA tools for Windows NT 4.0 and 2000 Server installations. This is a
licensed product from Microsoft and requires the user to obtain the appropriate software and
licenses. This software is not provided with the MESA tools and must be purchased separately.
The MESA tools support SQL Server 7.0 under Windows NT 4.0 and SQL Server 2000 under
Windows 2000 Server.

2.4 Xerces C
Xerces C is a library maintained by the Apache foundation used to parse XML data. Quoting
from the Apache web page:

_____________________________________________________________________________

-4-
Version 10.9.0 14-Oct-2006
MESA Software Installation: Windows Binary
______________________________________________________________________________

Xerces (named after the Xerces Blue butterfly) provides world-class XML parsing
and generation. Fully-validating parsers are available for both Java and C++,
implementing the W3C XML and DOM (Level 1 and 2) standards, as well as the de
facto SAX (version 2) standard. The parsers are highly modular and configurable.
Initial support for XML Schema (draft W3C standard) is also provided

2.5 Apache Tomcat Web Server


The Apache Tomcat web server is maintained by the Apache foundation (www.apache.org). This
web server is designed to support Java servlets and provides the mechanism we use for web
applications.

2.6 ImageMagick
ImageMagick®, version 6.3.0, is a software suite to create, edit, and compose bitmap images. It
can read, convert and write images in a variety of formats (about 100) including GIF, JPEG,
JPEG-2000, PNG, PDF, PhotoCD, TIFF, and DPX. Use ImageMagick to translate, flip, mirror,
rotate, scale, shear and transform images, adjust image colors, apply various special effects, or
draw text, lines, polygons, ellipses and Bézier curves.
This software is found at http://www.imagemagick.org/script/index.php. Not all tests require this
software; please refer to the installation instructions in this document and the test instructions for
specific actors.

_____________________________________________________________________________

-5-
Version 10.9.0 14-Oct-2006
MESA Software Installation: Windows Binary
______________________________________________________________________________

3 Installation from Compiled Binaries

3.1 Database Installation

3.1.1 Microsoft SQL Server Installation: Windows XP, Windows 2000,


Windows 2000 Server
The MESA software is tested with Microsoft SQL Server 7.0 and SQL Server 2000. The MS
SQL Server product provides a setup tool that guides you through the installation process. When
the installation is complete, you will be able to interact with the server using interactive SQL and
their GUI-based management tools. The MESA software communicates with the server using
ODBC, and your PC must be configured to use that channel.

Before configuring the ODBC driver, you need to add a login to the Microsoft SQL Server
system. This login is the login/password used by our software to connect to tables. You could
use an existing acount; the example we use is the account ctn with the password ctn. This is an
account managed by SQL Server and not Windows. Use the SQL Server Enterprise Manager to
add this new login (ctn/ctn if you follow our example).

Open the Control Panel folder and then open ODBC. For 2000 Server, you will find the ODBC
control under Administrative Tools in the Control Panel. Select the "System DSN" tab. There
will be a list of system data sources. There should be one called LocalServer which uses the
SQL Server driver. This entry is created by the SQL Server installation procedure. Our server is
configured with these values (set by the SQL Server setup program). You can choose a different
login ID and password. The runtime notes will tell you how to communicate your values to the
MESA software.

Variable Value
Name LocalServer
Description <blank>
Which server local
Verify authenticity by … SQL Server authentification
Login ID ctn
Password ctn

The MESA software runs on the same machine as the SQL Server, so we use the local
connection. We do not use the trusted connection option, but you might decide to do so
depending on how you want to configure your system.
The database software uses the environment variable SQL_ACCESS to determine the 3
parameters needed to establish the connection to the SQL database. The format of this variable
is:
<server name>:<login>:<password>
We use this at our site: LocalServer:ctn:ctn

_____________________________________________________________________________

-6-
Version 10.9.0 14-Oct-2006
MESA Software Installation: Windows Binary
______________________________________________________________________________

If you do not define this environment variable, the LocalServer:ctn:ctn values are used by
default. You might choose to use a different login name or password or a different scheme. If
you choose to use the Trusted Server feature of the system, you can leave the login and password
values blank in the SQL_ACCESS variable: "LocalServer:::".
The SQL Server has security features that allow the administrator to restrict access to tables in
the database. You may find that you need to open up access to get the MESA software to
operate properly. If the MESA applications complain about access privileges, you will need to
use the SQL Enterprise Manager to give you access rights to the databases (insert, delete). There
are several methods for allowing access. One simple method is to activate the Manage pulldown
(in SQL Enterprise Manager) and select logins. For the login that you are using, alias that login
as dbo (stands for database owner) for the databases you are using. That should give you the
privileges you need. We also suggest you read the SQL Server documents to understand their
security features (they will certainly explain them better than we can).

3.2 Perl Installation


Perl is available for Win32 systems at http://www.activestate.com. We are using ActivePerl 5.6
on our systems. The Active State distribution comes in two versions. One requires the MSI
installer and the other version has no uninstall feature. If either version is unacceptable to you,
you can build the perl from source. Use the stable version (5.6 as of this document) that can be
found at www.perl.org. We have installed this version in D:\perl.
The MESA distribution page contains a zip file with a version of perl that we compiled in our
laboratory. You may also install this version of perl (5.6) by unzipping it in the appropriate
directory.

3.2.1 Additional Perl Modules


Version 8.0.0 of the MESA tools uses additional Perl modules. These can be found on the web
distribution page. Install as follows:
Date/Manip.pm No need to install; included in mesa_tests/actors/rad/common/scripts. If
you find a conflict with your perl installation (perl already has this
module), remove the MESA copy.

3.3 Install Java


Install the Sun Java 2 Software Development Kit (JDK) for version 5.0 or higher. The JRE is not
sufficient. You need to obtain this from the Sun web server: www.java.sun.com. We are not
allowed to redistribute the JDK.
Sun publishes several different versions of the JDK. As of Nov, 2006, we are using JDK 5.0
Update 9. Other versions would work, but will include more software than is required. We are
specifically not using:
• JDK with NetBeans
• JDK with Java EE
• JRE
• Java Source Code
_____________________________________________________________________________

-7-
Version 10.9.0 14-Oct-2006
MESA Software Installation: Windows Binary
______________________________________________________________________________

3.4 Apache Tomcat Installation


The Apache Tomcat server is used by the MESA Information Source actor to supply summary
information and documents in response to RID queries. Install version 5.0.28 or higher. The
installation file that we provide is a Windows installation program from the apache site that is
ready for installation.

The table below lists the installation directories that we use for testing. These values are not
required, and you might choose different directories.

Table 3.4-1 Tomcat Installation Directories


System Director
Windows 2000 C:\tomcat\Jakarta-5.0.28

3.4.1 JDBC Installation


The RID tests use Java servlets communicating with the SQL Server database through a JDBC
connection. This requires the installation of the JDBC driver from Microsoft. The software
version that you will need is
SQL Server 2000 Driver for JDBC Service Pack 1
You can find this software on the Microsoft website. Follow these steps on the Microsoft web
page:
1. Select Downloads (left flap)
2. Select Drivers (left flap)
3. In the search page, enter JDBC for the Keyword and select “Go”
4. You should see the list of drivers

We are testing with Service Pack 3.

Install the software per Microsoft’s instructions. On our system, the software is installed in
C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC. That installation directory is not
important.

Copy the 3 jar files in the JDBC distribution lib directory to %TOMCAT_HOME%\common\lib.
These three files are:
• msbase.jar
• mssqlserver.jar
• msutil.jar

3.5 OpenLDAP
OpenLDAP for PWP tests has been tested only on RedHat Linux systems. Contact the Project
Manager for Internet testing.

_____________________________________________________________________________

-8-
Version 10.9.0 14-Oct-2006
MESA Software Installation: Windows Binary
______________________________________________________________________________

3.6 Agfa/Philips DVT


The DICOM Validation Tool (DVT) is a software utility and a set of .NET components that will
assist in testing DICOM conformance. MESA will use DVT to validate DICOM objects. You
can download DVT at http://www.dvtk.org.

Install DVT by double-click on the downloaded exe file and follow the instructions. Install DVT
in the default directory.

3.7 ImageMagick
The ImageMagick software is found at http://www.imagemagick.org/script/index.php. This
software is currently used to support tests of Acquisition Modalities in the NMI profile. Do not
install this software unless that is relevant to your system.
The ImageMagick web site provides 4 binary installation versions. We chose this following
version:
ImageMagick-6.3.0-5-Q16-windows-static.exe
Follow their installation instructions. Make sure the PATH variable is updated with the path to
the ImageMagick executables. The MESA scripts make no assumptions about the location of the
software and rely on the PATH variable.

3.8 MESA Installation


The pre-compiled version of MESA software is distributed as a zip file. This software can be
installed using a normal account with no system privileges. All software is installed in the target
directory (%MESA_TARGET%) and no files are installed in any system directories. No
changes are made to the Registry.

Open the zip archive for the MESA binary distribution. Extract the files to the MESA default
directory (D:\mesa). You may choose a different disk (and/or path); just be sure to adjust the
direct names given below and to set the runtime environment when you use the software.

3.8.1 Completion for Sites Requiring Tomcat (e.g., RID Profile)


Complete the installation by copying MESA files to the Tomcat directory. You need to set the
environment variables TOMCAT_HOME and MESA_TARGET appropriately. In the directory
%MESA_TARGET%\webmesa\mesa-iti:

1. Edit the file web_w32_sqlserver.xml (use notepad).


2. Find the two different initialization parameters whose param-name is logPath. Change the
first part of the param-value from D:\mesa to the directory where the MESA software is
installed (i.e., the value for %MESA_TARGET%). Leave the segment that says
\logs\info_src.log as is.

_____________________________________________________________________________

-9-
Version 10.9.0 14-Oct-2006
MESA Software Installation: Windows Binary
______________________________________________________________________________

3. Find the two different initialization parameters whose param-name is jdbcConnectURL.


Change the values for ServerName, User and Password in the URL to appropriate values for
your system. If you use our normal conventions, these values would be LocalServer, ctn, ctn.
4. Find the one initialization parameter whose param-name is imagePath. Change the param-
value to the partition and directory where you have chosen to install the MESA storage data.
The default value is D:\mesa\storage.
5. To complete this installation step:
cd %MESA_TARGET%\webmesa\mesa-iti
install.bat

_____________________________________________________________________________

- 10 -
Version 10.9.0 14-Oct-2006
MESA Software Installation: Windows Binary
______________________________________________________________________________

4 Build Databases

The installation procedure assumes you will build databases needed for all MESA tests. The first
step is to create 10 databases for the various MESA actors/simulators. Use the SQL Enterprise
Manager to create the following databases:

adt expmgr rpt_manager


ordplc exprcr syslog
ordfil imgmgr xref_mgr
mod1 wkstation info_src
mod2 rpt_repos pd_supplier

Each database should be at least 5 MB in size. For each database, add the SQL server account
configured in section 5.2 above as a db_owner. This will allow you to add and remove tables.
Once the databases have been built, you need to create the tables in the databases. Use a DOS
window and set the directory to %MESA_TARGET%\db. Execute the perl script:
perl create_mesa_tables.pl <login> <password> <server>

In the example that we use, login and password are both “ctn”. As mentioned previously, the
login that you choose will need db_owner rights to create tables in the database. The server
parameter is passed with the –S switch to isql; it is the name you have given your SQL server.

4.1.1 Load Databases with Test Data


The ITI tests require some initial data in the SQL database. There are two SQL files to load with
this test data. You can load these using the command line, SQL interpreter (isql) or the SQL
Query Analyzer. The data should be loaded into the info_src table:
isql –S <server> -Ulogin –Ppassword –D info_src < load_rid_data.sql
isql –S <server> -Ulogin –Ppassword –D info_src < load_doc_reference.sql

5 Install the MESA Storage Directory


The MESA storage directory is separate from the MESA_TARGET directory. We distribute
separate zip files for installation. Use the table below to determine which files are appropriate for
your installation.

Table 5.1-1 MESA Storage Files


Storage File Name
MESA Tests
MESA-storage-A (version)
All
Radiology/Mammography MESA-storage-B (version)

To create the storage directory:


1. Set the environment variable $MESA_STORAGE
_____________________________________________________________________________

- 11 -
Version 10.9.0 14-Oct-2006
MESA Software Installation: Windows Binary
______________________________________________________________________________

2. Create the top level storage directory


3. mkdir %MESA_STORAGE%
4. Install the MESA-A storage files (all domains)
5. Install the MESA-B storage files (if necessary)
6. Edit the file %MESA_STORAGE%\ecg\ecg20304.xml. This file has URLs that refer to the
server info-src. Replace the server name with the name of the system running the Tomcat
server in all URLs, or make a hostname entry to map the name info-src to that system.

_____________________________________________________________________________

- 12 -
Version 10.9.0 14-Oct-2006
MESA Software Installation: Windows Binary
______________________________________________________________________________

6 Runtime Notes
There are environment variables that need to be set when you run the test scripts. These are
discussed in previous sections of the document and listed again in the table below.

Variable Value
D:\mesa (or another value of your choosing)
MESA_TARGET
MESA_STORAGE D:\mesa\storage (or another value of your
choosing)
PATH should include %MESA_TARGET%\bin and the
path to perl
JAVA_HOME D:\jdk1.3 (or another value of your choosing)
JAR_DIRECTORY %MESA_TARGET%\lib
MESA_SQL_LOGIN ctn (or other login of your choosing)
MESA_SQL_PASSWORD ctn (or other password of your choosing)
SQL_ACCESS LocalServer:ctn:ctn (consistent with values
above)
MESA_OS WINDOWS_NT (use this value; do not substitute,
even on XP and 2000 systems)

_____________________________________________________________________________

- 13 -
Version 10.9.0 14-Oct-2006
MESA Software Installation: Windows Binary
______________________________________________________________________________

7 Installation Test: MESA Class A Tests


Beginning with the 10.3.0 release, we have added an installation test to make sure that variables
are set properly and the databases are installed. All actors tested with the MIR MESA software
should run the tests documented in this section:

7.1 MESA Test 1: Installation Test


MESA Test 1 examines environment variables, some folders in the MESA_STORAGE area and
checks that the databases can be opened by the MESA applications.

7.1.1 Instructions
To run this test, follow these steps using a DOS window or terminal emulator:
1. Set the current directory to $MESA_TARGET/mesa_tests/common/actors/all
2. Run the test script as follows:
perl 1/eval_1.pl

7.1.2 Evaluation
The output of test 1 will be stored in 1/grade_1.txt. Examine the file. There will be several
warning messages. The installation test is complete when the grade_1.txt file contains no error
messages.

When the grade_1.txt file shows no error messages, submit that file to the Project Manager for
evaluation.

_____________________________________________________________________________

- 14 -
Version 10.9.0 14-Oct-2006

You might also like