Gazelle Installation Linux
- 1 Gazelle: Linux specific Installation
- 2 Required Packages
- 3 Gazelle Software
- 4 Database Installation
- 5 Configuration
- 6 Contractual Information
- 7 Starting Gazelle Servers
Gazelle: Linux specific Installation
These instructions describe how to install the Gazelle software on Linux platform.
Gazelle requires software packages for runtime support. You will need to install/configure these.
Standard OS Packages
- Install/configure an SMTP server. Gazelle will need to connect to a server to distribute email. Gazelle does not need to receive inbound email. You can send that to your standard, administrator accounts.
- See the notes below on configuration values. Gazelle is hard-coded today to use an SMTP server on the host system that is running the Gazelle software. In the future, that should be changed to allow a different host for the SMTP server.
- Install/configure postgresql server
- Install sudo
apt-get install sudo
- Download and install Java SDK 6 (1.6.0_16)from java.sun.com. You do not need the Netbeans software. Do not use version 1.5 or lower.
- Download and install JBoss AS 5.1.0 GA. Use this version. Do not substitute an older or newer version.
- Download and install JBoss Seam 2.2.0 GA (this version only)
- Download and install JBoss Richfaces UI 3.3.0 GA (this version only)
Work on this
The following instructions describe how to install the Mirth software.
- Download Mirth from http://sourceforge.net/project/showfiles.php?group_id=162856
- Uncompress the downloaded Mirth file on the server. For example, /opt/mirth
- Mirth use port 8080 for its web application. To solve the conflict with default web application port in Tomcat,go to the directory where you uncompress Mirth software, edit mirth.properties in the conf directory, for example, change http.port=8080 to http.port=8088.
- Open a console and run mirth.sh
- Open web browser with http://localhost:8088 and click on "Launch Mirth Administrator" button
- Accept "open with webstart" and follow the instructions.
- Once Mirth Console come up, login as admin/admin
- Download File:Example-mirth-config.zip and uncompress the zip file so that you can select individual configuration file in the next step.
- On Mirth console, select Channels and import channel by File:Example-mirth-config.zip selecting existing channel configuration files.
- The example mirth configuration file names tell you what is configured. For example, "OP Listening on 2100.xml" is for client to send a message to the Order Placer using port 2100.
- For our development purpose, we use Nule as a HL7 client application to send message to Mirth over LLP.
- Download GazelleXX.ear from
Hard Coded Configuration
These values are hard-coded in the Gazelle application. You will need to use these values for now:
Database Configuration Entries
Your version of Gazelle is customized according to your site parameters. There will be a web-based application for changing configuration values. As of now, you will edit the database by hand:
psql gazelle-db update cmn_application_preference set preference_value = 'X' where preference_name = 'Y';
The table below shows values that you would consider changing. The second table show values you would not change without consulting with the Gazelle developers.
|Class||Preference Name (Y)||Default Value (X)|
Network Configuration Parameters
You will need to create an entry for network configuration in your database. This entry is tied to your testing session. The table to modify is tm_network_config_for_session. The table below shows the columns you need to populate with example values
|id||integer: unique identifier for this row. You have to enter a value||2|
|last_changed||timestamp: The date/time this row was changed||When doing an insert, use the value 'now'. Database will insert a proper timestamp.|
|last_modifier_id||character: Login name of the last person to change (you!!)||epoiseau|
|dns_address||character: IP address of DNS server||172.20.175.253|
|ip_range_high||character: Upper range of IP addresses to assign for this session||172.20.170.254|
|ip_range_low||character: Lower range of IP addresses to assign for this session||172.20.170.100|
|subnet_mask||character: From network administration 101||255.255.255.0|
|testing_session_id||integer: References tm_testing_session.id||5|
|dns_header||character: Data to be included as header in DNS configuration generated by Gazelle||
; ; BIND data file for local loopback interface ; $TTL 604800 @ IN SOA ihe-europe.net. root.localhost. ( 1 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Negative Cache TTL ; @ IN NS ihe-europe.net. IN A 172.16.1.11 $ORIGIN ihe-europe.net. ; ; ; ntp IN A 172.16.1.11 dns IN A 172.16.1.11 proxy IN A 172.16.1.12 printer IN A 172.16.1.13 central-archive IN A 172.16.1.11 central IN A 172.16.1.11 ris-mall IN A 172.16.1.15 rismall IN A 172.16.1.15 gazelle IN A 172.16.1.16 geneva IN A 172.16.1.17 ihe231 IN A 172.16.1.11
|host_header||character: Data that goes at the top of the host name table generated by Gazelle. These are typically hosts that are used as part of testing scenarios provided by connectathon management. Or, they might be a printer IP address or the address of an SMTP server.||
172.16.1.11 ntp dns 172.16.1.17 proxy 172.16.1.13 printer 172.16.1.14 central-archive central 172.16.1.15 rismall ris-mall 172.16.1.16 gazelle 172.16.1.17 geneva 172.16.1.18 maki
|domain_name||character: Default domain_name used when generate fully qualified domain names. This is a network domain name and has nothing to do with a Microsoft Windows domain. This is not www.ihe.net, nor is it www.ihe-europe.net. This is the value used as part of the search process in DNS.||ihe.net|
You will also need to edit an HTML page that describes some of the network/test settings that are hard to represent with database entries. As an Administrator, use the Gazelle Web GUI and select Configurations -> Network Configuration Overview. Use the sample that is already provided, and update the HTML using the editor provide. This page provides some settings are not in the database. Some of the settings do mirror items in the database, so make sure they are consistent.
Gazelle has an administrative page that will allow you to configure preferences for this installation of Gazelle. Once you have logged in with adminstrator rights, you can select "Admnistration -> Application Preferences". From this page, set the values for:
- Application Values
- Application URL
- Application Name (default is Gazelle)
- Admin Name
- Admin Email
- Time Zone
- Zone (check with developers for a list of allowed values)
- History Account Email (do not change)
- Issue Tracker URL (do not change)
- Release Notes URL (discuss with developers)
- Financial Values
- Fee for first system
- Fee for each additional system
- Fees per domain
- VAT (enter 0 if not applicable)
- Test Engine
- ActiveBPEL Server URL
- Files/Paths Management
- Application Root path
- Data path
- Reports path
- Binaries path
The default Gazelle installation will have testing sessions that you will not use. You need to configure for your testing sessions. Login to Gazelle with administrative rights.
- Select Administration -> Manage Sessions
- Lower left part of the page, select Show all
- Disable any sessions you do not wish the users to see. You do that by double clicking on that session.
- Add one or more sessions for this instance of Gazelle. You will need configuration parameters such as the name of the event, start/end dates, registration deadline...
- Enable your event by double clicking on it when appropriate.
Gazelle will generate a application/contract for you, but the current version does this with files that are part of the source code. Request that the software provider edit the file TestManagement-ui/WebContent/financial/contract.xhtml to generate the proper language.