PulseNET

Installation Guide
Version 3.0.0

MDS 05-6138A01
 Table of Contents
Planning Your Installation 4
System Requirements 4
Monitoring up to 25 Devices 4
Monitoring 25 to 500 Devices 4
Web Browser and Web Client Support 4
Operating System (OS) Support 5
TCP/UDP Ports Required 5
Device Support 6
Network Requirements 7

Installing PulseNET 8
Initial Considerations 8
Installing PulseNET on Windows 8
Step 1: Running the Installer 9
Step 2: Introduction 9
Step 3: Transaction Product Agreement 9
Step 4: Installation Type 9
Step 5: Install Folder 10
Step 6: Shortcut Location 10
Step 7: PulseNET Service 11
Step 8: Pre-Installation Summary 11
Step 9: PulseNET Installation 12
Step 10: Secure Server Settings 12
Step 11: PulseNET Ports Configuration 13
Step 12: PulseNET Server Startup 13
Step 13: Software Installation Finish 14
Step 14: Software Configuration 14
Step 15: Verification 14
Manually Installing PulseNET as a Windows Service 15
Installing PulseNET on Linux 15
Step 1: Running the Linux Installer 16
Steps 2 through 9: 16
Steps 10 through 13: 17
Step 13a: Configure Agent Manager Privileges for Linux 17
Step 13b: Configure PulseNET to Auto-Start at Boot Time 18
Step 14: Software Configuration 19
Step 15: Verification 19
Importing a Network Security Certificate 19
Uninstalling PulseNET 20
Quick Reference Chart for Windows Installation 23
Quick Reference Chart for Linux Installation 24

Upgrading PulseNET 25
Preparing to Upgrade 25
Upgrading PulseNET with Installer 25
Upgrading PulseNET from Archive File 28
Quick Reference Chart for Windows Upgrade 29
Quick Reference Chart for Linux Upgrade 30
Running PulseNET 31
Starting PulseNET 31
Stopping PulseNET 32
Logging in to PulseNET 33
Planning Your Installation 1

System Requirements
Before installing PulseNET, ensure that your system meets the following hardware and soft-
ware requirements.

Monitoring up to 25 Devices
CPU Dual Core CPU at 1.6 GHz
This table shows the minimum system require-
Memory 4 GB of available RAM
ments for PulseNET to monitor up to 25 devices.
Disk Space 30 GB of available storage

Monitoring 25 to 500 Devices

CPU Dual Core CPU at 2.2 GHz
This table shows the minimum system require-
Memory 8 GB of available RAM
ments for PulseNET to monitor from 25 to 500
Disk Space 60 GB of available storage
devices.

Web Browser and Web Client Support

Browser Type Version
Internet Explorer 8 8.x or newer
Firefox 16.x or newer
Safari (Mac OS X only) 6.x or newer
Chrome 22.x or newer

NOTE PulseNET supports a maximum of 25 web clients at one time.

 PulseNET Installation Guide
Planning Your Installation
5
Operating System (OS) Support
PulseNET is supported on the following operating systems.
Hardware 32-bit 64-bit
Operating System Version
Architecture Installer Installer
Server 2003 IA-32 yes N/A
Server 2008
Server 2012 x86_64 yes yes
Server 2008 R2
Microsoft Windows x86_64 no yes
Server 2012 R2

Windows 7 Pro IA-32 yes N/A

(or above) x86_64 yes yes
AS/AE 4.x IA-32 yes N/A
RedHat Enterprise Linux AP/Server 5.x
6.x x86_64 yes yes
9 IA-32 yes N/A
Novell SuSE Linux
10
Enterprise Server x86_64 yes yes
11
5.x
CentOS Linux x86_64 no yes
6.x
Ubuntu Server 14.04 LTS x86_64 no yes

NOTE PulseNET support for 32-bit operating systems will be retired at the end
of 2014. A migration procedure will be provided to assist customers with moving
from existing 32-bit systems to new 64-bit systems.

TCP/UDP Ports Required

The PulseNET server requires the following ports:

Function Access Port Number(s)

HTTP External 8080
HTTPS External 8443
JNDI RMI Internal 1098
JNDI JNP Internal 1099
JRMP Invoker Internal 4444
Pooled Invoker Internal 4445
Unified Invoker Internal 4448
Corba ORB Internal 3528
 PulseNET Installation Guide
Planning Your Installation
6
MySQL Internal 13306
MySQL default External 3306
Oracle default External 1521
SQL Server default External 1433
QP5 Server Internal 8448
JNDI UDP Group Internal N/A
Cluster Multicast External N/A
SNMP 161
ICMP Yes
TFTP External 69
Telnet External 23

Internal: This port is only used internally on the

PulseNET server.

External: This port communicates with other sys-

tems. If a firewall is implemented, this port must be
allowed for proper communication.

Device Support
PulseNET can monitor the following devices:

Device Type Minimum Firmware Version

EntraNET 3.0.7
iNET-900 6.9.1
iNET-II 2.9.1
MDS Intrepid 1.9.00 b1730
Mercury 900 3.7.3
Mercury 1800 3.0.6
Mercury 3650 Rev D 3.7.3
Mercury 3650 Rev E 3.2.6
Mercury 5800 3.0.6
Orbit MCR 3G/4G 2.0.0
SD Master and Remote 4.1.5
TransNET 900 Master,
Extension, and Remote
3.2.3
(including Store and
Forward devices)
WiYZ 1.5.5 only
x790 Master 2.2.1
x710 Remote 3.7.1
 PulseNET Installation Guide
Planning Your Installation
7
Network Requirements
In order for PulseNET to operate correctly on your system, ensure that you have a static
host name and that the IP address can be resolved consistently using that host name.
 Installing PulseNET 2

Initial Considerations
PulseNET should run on a dedicated machine because it will process and store large
volumes of data. Before beginning your installation, verify that you have full admin-
istrator access to your servers operating system. From a network perspective, ensure
that the machines host name can be resolved and that reverse lookup also correctly
identifies your server.
The following stages are involved in installing and configuring PulseNET:
Stage 1: Install the PulseNET application
Stage 2: Configure the PulseNET server
Stage 3: Start the PulseNET server and log in
After the installation completes, you will probably want to change the default PulseNET
administrator account password. The default user name and password (admin/admin)
will initially be used to log in to the browser interface and use PulseNET command-line
tools with administrator privileges. It is strongly recommended that you change the
default password for this account after installation.

Installing PulseNET on Windows

When all system requirements are in place, you are ready to install. Verify that your
machine(s) meet the minimum system requirements for the number of devices your
instance of PulseNET will be monitoring.
The IATEMPDIR or TEMP environment variable should be set to a location with sufficient
space for the self-extracting installer to store the PulseNET installation programs. Spe-
cific requirements are described in the document available at: http://support.install-
shield.com/kb/view.asp?articleid=Q000054
 PulseNET Installation Guide
Installing PulseNET
9
The installation process offers two installation options:
Standard This option accepts all of the defaults and installs a standalone instance of
PulseNET using an embedded MySQL database.
Custom Using this option, you can modify the installer defaults.

Step 1: Running the Installer

1 Locate the PulseNET install executable file on your
computer and right-click. In the menu that appears,
click the command Run as administrator. This is vital
to insure proper installation and to help avoid permis-
sion issues later.
2 The installation will automatically begin as soon as the installer has finished loading.

Step 2: Introduction

The Introduction screen provides an overview of the installation steps. Each installation
screen includes a Previous button so you can go back and adjust the specified informa-
tion as needed. Click Next after reading the contents of the Introduction screen.

Step 3: Transaction Product Agreement

Read the Transaction Product Agreement statement and Accept the terms of the agree-
ment. If you decline, the PulseNET installer will close. Click Next.

Step 4: Installation Type

1 Choose Standard Install or
Custom Install.
The Standard option accepts all of
the defaults and installs a stand-
alone instance of PulseNET with an
embedded MySQL database using
the default directories.
The Custom option allows you to
modify the installer defaults.
2 Click Next.

If you chose Standard Install, skip to Step 12. In Standard mode the installer will show
the installation progress and then advance directly to this step.
 PulseNET Installation Guide
Installing PulseNET
10
Step 5: Install Folder
1 Custom Install Only: Choose the location where you want to install PulseNET. You can
accept the default location or click Browse to navigate to another location.

If you have a previous version of PulseNET installed and you choose its install folder, you
are prompted to indicate whether you want to upgrade that version or install a new
version without upgrading. See Upgrading PulseNET.
2 Click Next.

Step 6: Shortcut Location

1 Custom Install Only: Choose where you want to create product icons.
To create shortcuts for all PulseNET users, select Create Icons for all Users.

2 Click Next.
 PulseNET Installation Guide
Installing PulseNET
11
Step 7: PulseNET Service

NOTE If you do not see this option, you may not have run the installer as an ad-
ministrator, as described in Step 1. If that is the case, abort the install and restart.
1 Custom Install Only: To run PulseNET as a Windows service (highly recommended), select
Enable PulseNET as a Service. (Be aware that this is not an option if you are installing
on Linux. You can manually set PulseNET to run at boot time after installing.)

2 Click Next once. There will be a pause while PulseNET builds the installation summary.

Step 8: Pre-Installation Summary

1 Custom Install Only: Review the installation information.
2 To edit any installation parameters, click Previous and make your changes.

3 When you are satisfied with the parameters of your installation, click Install.
 PulseNET Installation Guide
Installing PulseNET
12
Step 9: PulseNET Installation

PulseNET installs the files into the specified directory.

For Standard installation, the default installation directory is C:\GE_MDS\PulseNET.

For Custom installation, the program is installed in the directory you specified in Step 5.

Step 10: Secure Server Settings

1 To run PulseNET in secure mode (HTTPS) only, select the Secure Server (HTTPS Only)
check box. Otherwise, leave the box unchecked to allow the server to run in both public
and secure modes.

NOTE To set up the system to use HTTPS, you must also generate a key pair
(security certificate) in the PulseNET keystore. For information about how to do
this, see Importing a Network Security Certificate.
2 Click Next.
 PulseNET Installation Guide
Installing PulseNET
13
Step 11: PulseNET Ports Configuration

The PulseNET Ports Configuration screen displays default ports that you can assign.
1 If you want to apply the default values, click Next. Otherwise, configure the desired
server port numbers. If you have changed any of the values and want to revert back to
the defaults, click Defaults.

2 Click Next.

NOTE If there are port assignment conflicts, an error message dialog appears.
Click Review Ports to return to the PulseNET Ports Configuration screen and
resolve the conflicting ports, or choose Ignore, then Continue to continue with the
installation without resolving the port conflicts.

Step 12: PulseNET Server Startup

If you enabled PulseNET to run as a Windows service in Step 7, this screen will not ap-
pear. Skip ahead to Step 13.
If you did not enable PulseNET to run as a Windows service, the PulseNET Server Startup
step provides you with the option to start PulseNET from the installer.
If you want the installer to start a one-time instance of PulseNET immediately, leave the
Run Now check box selected. If you do not want the installer to auto-start PulseNET
(for example, if you want to manually set up PulseNET to run as a service), deselect the
Run Now check box. Click Next.
 PulseNET Installation Guide
Installing PulseNET
14
Step 13: Software Installation Finish

Click Done to close the installer and move on to the software configuration stage. Al-
though the installer has been closed, full installation has not yet been completed, be-
cause software configuration must now occur.

If you enabled PulseNET to run as a service (Step 7) or selected Run Now (Step 12),
PulseNET will start in the background.

Step 14: Software Configuration

The software configuration process will continue in the background for up to thirty min-
utes. Proceed to Step 15 to verify that PulseNET has started and is continuing its internal
configuration tasks.

NOTE During the initial startup, a command prompt window may open. Do
not close the command window. It will close automatically when PulseNET is
stopped. This is most likely to occur on Windows 7 or 2008 R2.

Step 15: Verification

If you did not select Run Now in Step 12, start the PulseNET service (see Starting
PulseNET). Wait for the software configuration process described in Step 14 to finish
(this could take up to thirty minutes), then continue with the verification.
 PulseNET Installation Guide
Installing PulseNET
15
To verify that the PulseNET service is running:
1 Open the Windows Task Manager.
2 Click the Show processes from all users button at the lower left.
3 Verify that the following processes are running:
fms.exe the Foglight main
launcher (this will appear al-
most immediately)
mysqld.exe the MySQL
database engine (this will vary
based on the chosen database)
fglam.exe the Foglight
embedded agent manager (this may take several minutes to appear)

NOTE Until these main processes are running, you will not be able to log in to
the PulseNET interface. Even after login is enabled, initial configuration will con-
tinue behind the scenes, so leave PulseNET running in order to avoid issues that
result from an incomplete installation.

Manually Installing PulseNET as a Windows Service

If you selected a Standard install, or if you chose not to have PulseNET installed to run
as a service, you can subsequently install PulseNET as a Windows service either from the
Start menu or from the command line.
To install the PulseNET service from the Start menu:
Navigate to Start > Programs > GE MDS > PulseNET 3.0 > Windows Service > Install
Service For PulseNET.

To install the PulseNET service from the command prompt:

Open a command window by right-clicking on the Command Prompt icon and select-
ing Run as administrator.
Type <pulsenet_home>\bin\fms -i

Installing PulseNET on Linux

It is best practice on Linux platforms to create a non-administrator user account (for
example, pulsenet) so that PulseNET does not run with full root system privileges. If
you are installing PulseNET with the embedded MySQL database, the installer and the
PulseNET application must be able to write to the directory where the MySQL socket is
located. By default, the MySQL socket is installed in the /tmp directory, which is usually
 PulseNET Installation Guide
Installing PulseNET
16
world-writable on Linux. If necessary, change the permissions on the MySQL socket
directory to allow read-write permission.
From a network perspective, you must define an IPv4 entry for localhost in the /etc/
hosts file prior to installing or the installer will not be able to start the embedded da-
tabase and the installation will fail. To prevent this, add an IPv4 entry for localhost in the
/etc/hosts file prior to installing. It is also a good practice to add your servers static
host name and network IP address to the /etc/hosts file to ensure proper name
resolution.
127.0.0.1 localhost.localdomain localhost
10.0.0.45 PNhostName

Step 1: Running the Linux Installer

1 Log on to your Linux server with the special non-root PulseNET user account you cre-
ated.
2 Open a terminal window and navigate to the directory containing the PulseNET install
file on your computer.
3 Make sure that the install binary has execute permission. If it does not, then change the
permission mode to add execute permission: chmod +x <filename>
rwxr-xr-x pulsenet pulsenet PulseNET-3_0_0-install_linux-x86_64.bin
4 Run the installer binary in order to begin the installation.

Be aware that on headless machines or servers without a GUI, the PulseNET installer will
determine that Console Mode should be used, and a text-based install program will
be displayed.

Steps 2 through 9:

Follow the installation steps given previously for a Windows install. The displays pro-
vided by the PulseNET install for Linux correspond to the ones shown for Windows. If
you selected a Standard Install, do Steps 2 through 4 and then go to the next section,
Steps 10 through 15. If you selected a Custom Install, do Steps 2 through 9, skipping
step 7 in the list of Windows steps.
 PulseNET Installation Guide
Installing PulseNET
17
Steps 10 through 13:

Standard Install: You should see the display in Step 13 where you can click the Done
button to exit the installer.
Custom Install: Follow Steps 10 through 13, skipping Step 12 shown for a Windows in-
stall. Click the Done button in Step 13 to exit the installer.

Step 13a: Configure Agent Manager Privileges for Linux

On Linux systems, certain agents require elevated system privileges in order to gather
metrics. This is achieved by configuring the Agent Manager to launch agents with root
privileges. You will be using an external application like sudo or setuid_launcher to give
the agents the required access. Follow the steps below before you start PulseNET on a
Linux server.
To use setuid_launcher to configure the agents:
1 On the server where the Agent Manager is installed, open a terminal window and navi-
gate to <pulsenet_home>/fglam/state/default/config/.
2 Open the fglam.config.xml file in a text editor.
3 Edit the <path> element under <secure-launcher> to point to your local se-
tuid_launcher executable. This executable is typically located in <pulsenet_home>/
fglam/bin/setuid_launcher.

4 Become the root user and use the chown root setuid_launcher command to
change the ownership to root.
5 Use the chmod u+s setuid_launcher command to set the sticky bit on this pro-
gram. This permits agents that need root privileges to be run as the root user without
requiring the administrator password.

To use sudo to configure the agents:

1 On the server where the Agent Manager is installed, open a terminal window and navi-
gate to <pulsenet_home>/fglam/state/default/config/.
2 Open the fglam.config.xml file in a text editor.
3 Edit the <path> element under <secure-launcher> to point to the sudo execut-
 PulseNET Installation Guide
Installing PulseNET
18
able. This executable is typically located in /usr/bin/sudo.
4 Become the root user and configure the sudoers file on your system to allow the fol-
lowing commands to be run as root by your PulseNET user account without requiring
a password.
<pulsenet_home>/fglam/client/*/bin/fog4_launcher
<pulsenet_home>/fglam/client/*/bin/udp2icmp
It is best practice to use a wildcard (*) for the version-specific Agent Manager so that
you avoid updating the sudoers file for each version in release, in the event you upgrade
the Agent Manager or the agents. A possible sudoers configuration might include the
following:
Cmnd_Alias PULSENET = <pulsenet_home>/fglam/cli-
ent/*/bin/fog4launcher, <pulsenet_home>/fglam/cli-
ent/*/bin/udp2icmp
pulsenet ALL = NOPASSWD: PULSENET
For sudo configuration, refer to the manual page or documentation for your specific
version of Linux. The agents should now be able to ping devices for discovery and begin
data collection.

Step 13b: Configure PulseNET to Auto-Start at Boot Time

On the server where PulseNET is installed, become the root user and open a terminal
window.
1 Navigate to <pulsenet_home>/scripts/init.d/ and move into the subdirec-
tory for your specific operating system family.
For example: cd RedHat
2 Copy the pulsenet file into the directory on your
server where startup scripts are stored.
For example: cp pulsenet /etc/init.d/
3 Edit the sample pulsenet file to include paths and
commands that are specific to your version of Li-
nux.
4 Using the appropriate commands on your version
of Linux, configure the pulsenet script to run at sys-
tem boot time.
For example: chkconfig pulsenet on (RedHat)
5 Again using the appropriate commands on your
version of Linux, run the pulsenet script to start the
PulseNET service on your system.
For example: service pulsenet start (Red-
Hat)
 PulseNET Installation Guide
Installing PulseNET
19
Step 14: Software Configuration

After the PulseNET service has been started, the software configuration process will
continue in the background for up to thirty minutes. Proceed to Step 15 to verify that
PulseNET has started and is continuing its internal configuration tasks.

Step 15: Verification

At this point you should see the PulseNET processes begin to run as the system auto-
matically continues its final steps to configure PulseNET internally. This may take up to
thirty minutes to complete, after which you will be able to verify that PulseNET is ready
for use by checking the system process table for all of the required processes.

Importing a Network Security Certificate

After completing all the installation steps, a running PulseNET server is capable of com-
municating using HTTP and HTTPS protocols. If you selected Secure Server (HTTPS only)
during Step 10 of your installation, PulseNET disables HTTP and only provides secure
communication using the HTTPS protocol. During the installation process PulseNET ap-
plied a self-signed certificate which is typically not recognized as valid by most web
browsers. Until a valid security certificate is installed, each user may notice a web
browser warning message when attempting to connect securely to PulseNET. Users can
ignore this browser warning and proceed to use PulseNET.
In order to eliminate this warning message and provide more robust web server secu-
rity, a valid security certificate must be installed for PulseNET. Security certificates can
be purchased through any of several commercial vendors, or many companies have a
system for generating their own internally valid security certificates.
Use the Java keytool utility included with PulseNET to create, import, and export cer-
tificates. This utility can be found in <pulsenet_home>\jre\bin\keytool. The
PulseNET web server keystore is located at the following path:
 PulseNET Installation Guide
Installing PulseNET
20
<pulsenet_home>\server\default\conf\tomcat.keystore
(default password: nitrogen)
1 Delete the existing self-signed key from the tomcat.keystore using the following com-
mand:
<pulsenet_home>\jre\bin\keytool
-keystore <pulsenet_home>\server\default\conf\tomcat.keystore
-storepass nitrogen -delete -alias tomcat
2 Create a new private key under the tomcat alias using the following command. This
private key will then be included in the CSR file in the next step:
<pulsenet_home>\jre\bin\keytool
-keystore <pulsenet_home>\server\default\conf\tomcat.keystore
-storepass nitrogen -genkey -alias tomcat
3 Generate a Certificate Signing Request (CSR) using the following command. This CSR file
will contain the new private key as well as other information about the PulseNET server:
<pulsenet_home>\jre\bin\keytool
-keystore <pulsenet_home>\server\default\conf\tomcat.keystore
-storepass nitrogen -certreq -alias tomcat
-file <your-name-for-the-cert-signing-request>.csr
You can use any filename you choose. This file must be sent to a Certification Authority
(CA), which could be a commercial certificate provider or your own internal IT depart-
ment. The CA will generate a valid SSL certificate for you and provide you with one or
more files containing the certificate.
4 After you receive the official certificate, import it into the tomcat.keystore using the
following command:
<pulsenet_home>\jre\bin\keytool
-keystore <pulsenet_home>\server\default\conf\tomcat.keystore
-storepass nitrogen -import -trustcacerts -alias tomcat
-file <name-of-official-signed-certificate>.crt
When prompted to specify the keystore password, type nitrogen.

Uninstalling PulseNET
As with most commercial software, PulseNET has an uninstall pro-
gram that can be used to remove the software. There are still a few
steps that must be accomplished outside of this uninstall program in
order to completely remove PulseNET from the machine. The simple
process listed below can be used to uninstall PulseNET manually.
 PulseNET Installation Guide
Installing PulseNET
21
To uninstall PulseNET for Windows:
1 Stop the PulseNET service using the appropriate method for your server.
To stop a standalone server running PulseNET as a Windows service, nav-
igate to the Services menu, click on PulseNET, and click Stop the service.
Keep this window open to later verify that the service was successfully
stopped.
To stop a standalone server not running as a Windows service, see Stop-
ping PulseNET.

2 To delete the service file, navigate to the Start Menu and locate the Command Prompt
window. Right-click and choose the option to Run as administrator.
Then type one of the following
commands:
sc delete <ser-
vice name>
<pulsenet_home>\
bin\fms -r
The default service name is
PulseNET.
3 To delete the program, nav-
igate to the GE_MDS folder,
right-click, and choose De-
lete. Because of the size of the
GE_MDS folder, you may want
to shift-delete to get rid of it
permanently instead of simply
sending it to the recycle bin.
 PulseNET Installation Guide
Installing PulseNET
22
4 To delete the shortcuts, open the Start Menu and locate the GE_MDS folder there. Right-
click and choose Delete. Shortcuts installed on the desktop may need to be deleted
manually.

5 Return to the Services window used in Step 1 above and refresh the list. PulseNET
should disappear from the list of current services, verifying that it has been deleted.
6 Occasionally, a PulseNET installation log will be placed outside of the GE_MDS folder.
Check the parent directory (for example, C:) and delete this log file if it exists.

PulseNET should be completely uninstalled from your Windows machine.

To uninstall PulseNET for Linux:
1 Stop the PulseNET service using one of the methods appropriate to your version of Li-
nux. See Stopping PulseNET.
2 Navigate to the location where your <pulsenet_home> directory was installed. Re-
move the <pulsenet_home> directory tree. For example: rm -r GE_MDS
3 If you configured PulseNET to automatically start at boot time, remove the PulseNET
service. For example: chkconfig --del pulsenet (RedHat)
4 If you created shortcuts at install time, navigate to the location where they were placed
and remove them.

Quick Reference Chart for Windows Installation
Windows Install
Step 1: Running as Admin
Step 2: Introduction
Step 3: Agreement
Step 4: Standard vs. Custom
Step 5: Directory
Step 6: Shortcuts
Step 7: Enable as a Service
Step 8: Summary
Step 9: Install Progress
Step 10: Secure HTTPS
Step 11: Port Configuration
Step 12: Run Now
Step 13: Finish/Startup
Step 14: Configuration
Step 15: Verification
Log in to PulseNET
Apply License
PulseNET Installation Guide
Installing PulseNET
23
Standard Custom
P P
P P
P P
Standard Custom
(GE_MDS/PulseNET) P
(Start menu only) P
(not enabled) P
(not shown) P
P P
(HTTP and HTTPS) P
(Standard ports) P
P P
P P
P P
P P
P P
P P
 PulseNET Installation Guide
Installing PulseNET
24
Quick Reference Chart for Linux Installation

Linux Install Standard Custom

Step 1: Running Linux Installer P P
Step 2: Introduction P P
Step 3: Agreement P P
Step 4: Standard vs. Custom Standard Custom
Step 5: Directory (GE_MDS/PulseNET) P
Step 6: Shortcuts (Start menu only) P
Step 7: Enable as a Service (not shown) (not shown)
Step 8: Summary (not shown) P
Step 9: Install Progress P P
Step 10: Secure HTTPS (HTTP and HTTPS) P
Step 11: Port Configuration (Standard ports) P
Step 12: Run Now (not shown) (not shown)
Step 13: Finish P P
Step 13a: Agent Manager Priv. P P
Step 13b: Auto-start config P P
Step 14: Configuration P P
Step 15: Verification P P
Log in to PulseNET P P

Apply License P P
 Upgrading PulseNET 3

Preparing to Upgrade
Before upgrading PulseNET, complete the following steps:
1 Review the list of installation considerations given in Planning Your Installation.
2 Stop the running instance(s) of PulseNET (see Stopping PulseNET), but leave any exter-
nal databases running.
3 Insure that your PulseNET machine has enough disc space to store both the old and
new versions of PulseNET.
4 Create a backup of the previous version.
For PulseNET installs running an embedded database, copy the GE_MDS
folder to GE_MDS_<time stamp>.
For PulseNET installs running an external database, have your database
administrator create a back up of the external database. Then copy the
GE_MDS folder to GE_MDS_<time stamp>.
5 Be aware that new license-checking features in PulseNET will require you to obtain a
new license key after the upgrade. Directions for this are given in Step 12 below.

Upgrading PulseNET with Installer

1 For Linux installs only: Verify that you are logged in as the non-root PulseNET user.
2 Verify that all PulseNET processes have been stopped.
For Windows, type the following command: tasklist /v | find "GE_MDS"
For Linux, type the following command: ps -ef | grep GE_MDS

NOTE The default installation folder (GE_MDS) is included in the command

above. If PulseNET was installed in an alternate location on your machine, substi-
tute the appropriate folder name. If PulseNET was running as a daemon, this com-
mand displays that information instead of the path to the installation executable.
 PulseNET Installation Guide
Upgrading PulseNET
26
3 If you have customized the PulseNET server configuration files (such as <pulsenet_
home>\config\server.config, <pulsenet_home>\config\log.config, or
<pulsenet_home>\server\default\conf\jacorb.properties), then back up
these files so that you can verify that the correct ports are configured after the up-
grade is completed.
If you have not customized these files, proceed to the next step.
4 PulseNETs Java Runtime Engine (JRE) is replaced during the upgrade. Any existing se-
curity certificates are retained in <pulsenet_home>\jre\lib\security\ca-
certs.bak. To restore your security certificates after upgrading PulseNET, rename
cacerts.bak to cacerts.
5 Follow the steps outlined in the Installing PulseNET section for your operating system.
After choosing between Standard
and Custom installation in Step 4
of the Installing PulseNET section,
the installer will detect the earlier
version of PulseNET and prompt you
to choose whether you want to Up-
grade or perform a New Install.
An upgrade will attempt to retain all
of your existing information. A new
install will completely overwrite the
old code and will not retain any val-
ues in your existing database. The
information in this section applies
to upgrading an existing instance of
PulseNET. For a new install, refer to the Installing PulseNET section.
Notice the warning regarding the new license key requirement for the upgraded ver-
sion. Further information is given in Step 12 below.
Make your selection and click Install. If you have a large number of devices, the data-
base upgrade may be time consuming.
 PulseNET Installation Guide
Upgrading PulseNET
27
6 Since PulseNET was previously installed and configured, the PulseNET upgrade will ap-
ply your existing settings to the new version. This means that the upgrade process will
skip to Step 13 in the Installing PulseNET section. Click Done to exit the installer.
7 If you backed up any of the configuration files mentioned in Step 3 above, compare the
customizations in those files with the settings in the new files. Determine if the custom-
izations are still necessary and, if so, reapply them to the new files.
8 For Linux installs only:
Navigate to <pulsenet_home>/fglam/bin. If a fglam.new file exists,
rename the previous file to fglam.old and then rename the .new file
to fglam
Navigate to <pulsenet_home>/fglam/bin/setuid_launcher. If
a setuid_launcher.new file exists, rename the previous file to setuid_
launcher.old and then rename the .new file to setuid_launcher
Configure the Agent Manager privileges by following the detailed instruc-
tions provided in Step 13a of the Installing PulseNET for Linux section.
9 Even though the new version has been installed, the upgrade process must finish con-
figuring PulseNET. This will occur automatically when PulseNET is started.
For Windows, start the PulseNET Windows Service or type <pulsenet_home>\bin\
fms.exe
For Linux, run the PulseNET service startup command appropriate to your operating
system (for example: service pulsenet start) or type <pulsenet_home>/bin/
fms --start
10 After starting PulseNET, it can take up to thirty minutes for the remaining configuration
steps to complete automatically. You can monitor the behind-the-scenes configuration
by opening the Management Server log and periodically refreshing your view.
When the MySQL database is upgraded, you may notice warnings such as Starting
crash recovery in the log file during startup. These types of messages are normal
and can be safely ignored.
11 Log in to PulseNET through the browser interface, which is described in Logging in to
PulseNET. The first user to log in to PulseNET after an upgrade must be an administrator
(default: admin).
12 Navigate to Administration > Licensing > Manage Licenses. You will notice that your
previous PulseNET license has expired, regardless of the expiration date listed. This was
done automatically because the new license-checking features in PulseNET require an
updated license key to be applied after an upgrade.
 PulseNET Installation Guide
Upgrading PulseNET
28
To obtain a new license key from GE MDS, follow the licensing process given in the
Working with Licenses section in the Administration Guide.
13 Migrate any previously authorized devices from the expired license to the new license.
For detailed instructions, see Migrating Authorized Devices from an Expiring License to
a New License in the Administration Guide.

If you experience unusual or unexpected browser interface behavior (for example, un-
usual page layout) after upgrading, try logging out of PulseNET, clearing the browsers
cache, restarting the browser, and then logging back in to PulseNET. In most cases, this
will correct the problem. In rare cases, proxies and firewalls inappropriately cache JavaS-
cript, and therefore you may need to clear their caches as well.
After upgrading, the embedded Agent Manager should start automatically by default.
However, if the Agent Manager does not start automatically, you can edit the server.
config file to match the following example: server.fglam.embedded = true

Upgrading PulseNET from Archive File

Sometimes upgrades for PulseNET minor releases or hotfixes may be packaged in a
small archive fileZIP files for Windows and TAR files for Linux. Follow the steps below
to apply the updated components to your existing PulseNET installation.
1 Extract the contents of the ZIP/TAR archive to a directory of your choice.
2 Select the upgrade folder and the upgrade.bat or upgrade.sh files and copy them to
your <pulsenet_home> directory.
3 Run the upgrade.bat (Windows) or upgrade.sh (Linux) programs to begin the upgrade
process.
4 Verify that the correct PulseNET version numbers are displayed in the text listing:
2.6.0 > 3.0.0 (for example)
5 Type 1 and Return to begin the upgrade.
6 After the script completes, verify that the upgrade finished by navigating to the
<pulsenet_home>\upgrade\cartridge folder to see whether a .car file exists
there.
7 In order to apply the new cartridge files you must restart the PulseNET service.
8 Once PulseNET has been restarted, allow approximately thirty minutes for the back-
ground software configuration tasks to complete.
9 Verify that the new version has been applied by logging in to PulseNET and navigating
to the About link in the lower right corner of the web interface. The Product Informa-
tion field should display the new PulseNET version number.

Quick Reference Chart for Windows Upgrade
Note: Steps 1 and 8 of the Upgrading PulseNET section only apply to Linux installs and
are not included in the Windows Upgrade chart.
Windows Upgrade Standard
Step 2: PulseNET Stopped
Step 3: Back Up Customizations
Step 4: Back Up Security Cert.
Steps 5 & 6: Installation Steps
1) Running Installer
2) Introduction
3) Agreement
4a) Standard vs. Custom
4b) UPGRADE
5) Directory
6) Shortcuts
7) Enable as a Service
8) Summary
9) Install Progress
10) Secure HTTPS
13) Port Configuration
14) Run Now
15) Finish
Step 7: Reapply Customizations
Step 9: Start Service
Step 10: Software Configuration
Step 11: Log in to PulseNET
Step 12: Apply License
Step 13: Migrate Devices
PulseNET Installation Guide
Upgrading PulseNET
29
Custom
P P
P P
P P
P P
P P
P P
Standard Custom
Upgrade Upgrade
P P
P P
P P
P P
P P
P P
P P
P P

Quick Reference Chart for Linux Upgrade
Linux Upgrade Standard
Step 1: Log in as Non-root User
Step 2: PulseNET Stopped
Step 3: Back Up Customizations
Step 4: Back Up Security Cert.
Steps 5 & 6: Installation Steps
1) Running Installer
2) Introduction
3) Agreement
4a) Standard vs. Custom
4b) UPGRADE
5) Directory
6) Shortcuts
7) Enable as a Service
8) Summary
9) Install Progress
10) Secure HTTPS
13) Port Configuration
14) Run Now
15) Finish
Step 7: Reapply Customizations
Step 8: Rename and Configure
Step 9: Start Service
Step 10: Software Configuration
Step 11: Log in to PulseNET
Step 12: Apply License
Step 13: Migrate Devices
PulseNET Installation Guide
Upgrading PulseNET
30
Custom
P P
P P
P P
P P
P P
P P
P P
Standard Custom
Upgrade Upgrade
P P
P P
P P
P P
P P
P P
P P
P P
P P
Running PulseNET 4

Starting PulseNET
Windows: Choose one of the methods listed below.
If PulseNET is installed to run as a service, go to the Services application, select PulseNET
from the list, and click Start Service.
If you installed the startup icon in the default location (Windows),
navigate to Start > Programs > GE MDS > PulseNET 3.0 > Start
PulseNET.
Double-click the Start PulseNET shortcut on the desktop.
Open a command window and navigate to the directory <pulsenet_home>\bin
and execute the following command: fms.exe -s
When PulseNET starts successfully, the following message appears in the command
window: PulseNET startup completed.
Additional fms commands:

Command Represents Description

-s start Starts PulseNET (this is assumed if no command is
specified).
-n name Provides a unique name for this instance of PulseNET.
-j jvm-argument Sets an option to be passed directly to the Java VM.
Can be used to set more than one VM option.
-v version Displays the version number for this program and
exits.
-h help Shows this information and exits.
-b start-service Starts the service.
-r remove-service Stops and removes the service.

IMPORTANT During the initial startup, an Agent Manager command prompt

window may open. Do not close the command window. The window closes when
the server is shut down. This is most likely to occur on Windows 7 or 2008 R2.
 PulseNET Installation Guide
Running PulseNET
32
Be aware that the embedded Agent Manager starts automatically with the PulseNET
service. When that happens, WARN messages like the following may appear in the log
file for the PulseNET Agent Manager. These WARN messages can safely be ignored.
Could not find an acceptable JRE in <pulsenet_home>\fglam\jre
The path <pulsenet_home>\fglam\jre does not exist or is not a directory

Linux: Choose one of the methods listed below.

If PulseNET has been configured to run at boot time, use the method appropriate to
your version of Linux to start the running service. For example:
service pulsenet start (on RedHat)
If PulseNET shortcuts were created at install time, double-click the shortcut to start
PulseNET.
Open a terminal window and navigate to <pulsenet_home>/bin and execute the
following command: fms -s
The additional fms command options in the Windows list above can be used on Linux.

Stopping PulseNET
Windows: Choose one of the methods listed below.
If PulseNET is running as a service, go to the Services application, select PulseNET from
the list, and click Stop Service.
If you installed the startup icon in the default location (Windows), navigate to Start >
Programs > GE MDS > PulseNET 3.0 > Stop PulseNET.
Double-click the Stop PulseNET icon on the desktop.
Type Ctrl-C on the command window in which PulseNET started.
Navigate to the directory <pulsenet_home>\bin and execute the following com-
mand: fms -q

Linux: Choose one of the methods listed below.

If PulseNET has been configured to run at boot time, use the method appropriate to
your version of Linux to stop the running service. For example:
service pulsenet stop (on RedHat)
If PulseNET is running in a terminal window, type Ctrl-C to stop PulseNET.
If PulseNET shortcuts were created at install time, double-click the shortcut to stop
PulseNET.
 PulseNET Installation Guide
Running PulseNET
33
Logging in to PulseNET
NOTE PulseNET must be running before you can log in.

To log in from the Windows Start Menu:

1 If the program was installed in the default location, navigate to Start > Programs > GE
MDS > PulseNET 3.0 > PulseNET Console.
2 In the web browser that appears, type a valid User name and Password in the appropri-
ate fields, then click the Login button.

To log in directly with a Web browser:

1 Open a Web browser and type the
following URL: http://<host-
name>:<port>
where <hostname> is the name
of the machine where PulseNET is
installed and <port> is the HTTP or
HTTPS port specified during instal-
lation (the defaults are 8080 and
8443).
2 Enter a valid User name and Pass-
word and click Login.

After you log in to PulseNET, refer to the Administration Guide to complete additional
PulseNET configuration steps and licensing.
 Index
A
Agent Manager
Configuring for Linux 17

I
Installation
Considerations 8
For Linux 15
For Windows 8

L
Logging in to PulseNET 33

N
Network Security Certificates 19

S
Starting PulseNET
For Linux 32
For Windows 31
Stopping PulseNET
For Linux 32
For Windows 32
Supported
Databases 5
Devices 6
Operating Systems 4
TCP/UDP Ports 5
Web Browsers 6
System Requirements 4

U
Uninstalling 20
For Linux 22
For Windows 21
Upgrading
Preparation 25
With Archive File 28
With Installer 25

W
Windows Service, manual installation 15
Quest Copyright Notice
2014 Quest Software, Inc.
ALL RIGHTS RESERVED.
This guide contains proprietary information protected by
copyright. The software described in this guide is furnished
under a software license or nondisclosure agreement. This
software may be used or copied only in accordance with
the terms of the applicable agreement. No part of this
guide may be reproduced or transmitted in any form or
by any means, electronic or mechanical, including pho-
tocopying and recording, for any purpose other than the
purchasers personal use without the written permission of
Quest Software, Inc.
The information in this document is provided in connec-
tion with Quest products. No license, express or implied, by
estoppel or otherwise, to any intellectual property right is
granted by this document or in connection with the sale of
Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS
AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREE-
MENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY
WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED, OR
STATUTORY WARRANTY RELATING TO ITS PRODUCTS, IN-
CLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PUR-
POSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST
BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL,
PUNITIVE, SPECIAL, OR INCIDENTAL DAMAGES (INCLUDING,
WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS,
BUSINESS INTERRUPTION, OR LOSS OF INFORMATION) ARIS-
ING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT,
EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES. Quest makes no representations or war-
ranties with respect to the accuracy or completeness of
the contents of this document and reserves the right to
make changes to specifications and product descriptions
at any time without notice. Quest does not make any com-
mitment to update the information contained in this doc-
ument.
If you have any questions regarding your potential use of
this material, contact:
Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656
www.quest.com
email: legal@quest.com
Refer to our web site for regional and international office
information.
Patents
This product is protected by U.S. Patents #7,979,245 and
#8,175,862. Additional patents pending.
Trademarks
Quest, Quest Software, the Quest Software logo, Foglight,
IntelliProfile, PerformaSure, Spotlight, StealthCollect, TOAD,
Tag and Follow, Vintela Single Sign-on for Java, vOPS, and
vFoglight are trademarks and registered trademarks of
Quest Software, Inc in the United States of America and
other countries. For a complete list of Quest Softwares
trademarks, please see http://www.quest.com/legal/
trademark-information.aspx. Other trademarks and regis-
tered trademarks are property of their respective owners.
Third Party Contributions
MDS PulseNET contains some third party components. For
a complete list, see License Credits below.
About Quest Software, Inc.
Established in 1987, Quest Software (Nasdaq: QSFT) pro-
vides simple and innovative IT management solutions
that enable more than 100,000 global customers to save
time and money across physical and virtual environments.
Quest products solve complex IT challenges ranging from
database management, data protection, identity and ac-
cess management, monitoring, and user workspace man-
agement to Windows management. For more information,
visit www.quest.com.
About GE MDS
Over two decades ago, GE MDS began building radios for
business-critical applications. Since then, we have installed
thousands of radios in over 110 countries. To succeed, we
overcame impassable terrain, brutal operating conditions,
and disparate, complex network configurations. We also
became experts in wireless communication standards and
system applications worldwide. The result of our efforts is
that today, thousands of utilities around the world rely on
GE MDS-based wireless networks to manage their most
critical assets.
The majority of GE MDS radios deployed since 1985 are still
installed and performing within our customers' wireless
networks. Thats because we design and manufacture our
products in-house, according to ISO 9001, which allows us
to control and meet stringent global quality standards.
Thanks to our durable products and comprehensive solu-
tions, GE MDS is the wireless leader in industrial automa-
tionincluding oil and gas production and transportation,
water/wastewater treatment, supply, and transportation,
electric transmission and distribution, and many other util-
ity applications. GE MDS is also at the forefront of wireless
communications for private and public infrastructure and
online transaction processing. Now is an exciting time for
GE MDS and our customers as we look forward to further
demonstrating our abilities in new and emerging markets.
As your wireless needs change, you can continue to ex-
pect more from GE MDS. We'll always put the performance
of your network above all. Visit us at www.gemds.com for
more information.
GE MDS ISO 9001 Registration
GE MDS adheres to the internationally-accepted ISO 9001
quality system standard.
To GE Customers
We appreciate your patronage. You are our business. We
promise to serve and anticipate your needs. We will strive
to give you solutions that are cost effective, innovative, re-
liable and of the highest quality possible. We promise to
build a relationship that is forthright and ethical, one that
builds confidence and trust. Data sheets, frequently asked
questions, application notes, firmware upgrades and other
updated information is available on the GE MDS Web site
at www.gemds.com.
Manual Revision and Accuracy
This manual was prepared to cover a specific version of our
product. Accordingly, some screens and features may differ
from the actual version you are working with. While every
reasonable effort has been made to ensure the accuracy of
this guide, product improvements may also result in minor
differences between the manual and the product shipped
to you. If you have additional questions or need an exact
specification for a product, please contact our Custom-
er Service Team using the information at the back of this
guide. In addition, manual updates can often be found on
the GE MDS Web site at www.gemds.com.
About End 2 End Technologies
End 2 End (E2E) Technologies offers a unique combination
of wireless communications and information technology
expertise. We improve efficiency, reduce risk and lower the
cost of industrial field operations via modernization and
management of our customers wireless communications
networks. From initial planning through lifecycle support
we assist your team in adopting a wireless solution that
keeps communication costs low while maximizing network
reliability and performance. Visit us at www.e2etechinc.
com for more information.
In case of difficulty...
If you have problems, comments, or questions pertaining
to the MDS PulseNET application, please contact GE MDS
via one of the methods below:
Phone: 585-241-5510
Email: gemds.techsupport@ge.com
Fax: 585-242-8369
Website: www.gemds.com
License Credits
MDS PulseNET contains several third party components us-
ing open source licenses (copies of which can be found at:
http://www.quest.com/legal/third-party-licenses.aspx).
Proprietary:
Dlink Copyright GE MDS, LLC.
InstallAnywhere 8.0 Common Public License 1.0
MILLER-394729 Map 1.0 Map Resources Extended Use License Agree-
ment 1.0
Open Source:
[ini4j] 0.5 Apache License 2.0
Annotations 9.0.1 Apache License 2.0
ANTLR 2.2.7 ANTLR License 2
ANTLR 2.2.7.6 BSD License 4.4
ANTLR 3.1.3 ANTLR License 3
Apache 2.0.5.4 Apache License 1.1
Apache Commons 1.0 Apache License 1.1
Apache Commons 1.1 Apache License 1.1
Apache Commons 1.2 Apache License 1.1
Apache Commons 2.4 Apache License 2.0
Apache Commons Codec 1.4 Apache License 2.0
Apache Commons IO 1.4 Apache License 2.0
Apache Commons IO 2.0.1 Apache License 2.0
Apache Commons Validator 1.4.0 Apache License 2.0
Apache log4net 1.2.10 Apache License 1.1
Apache POI 3.7 Apache License 1.1
Apache Taglibs 1.1.0 Apache License 2.0
Apache Velocity 1.5 Apache License 1.1
args4j 2.0.16 MIT License
arsys-api 7.5 Apache License 2.0
Axiom 1.2.12 Apache License 2.0
Axis 1.4 Apache License 2.0
Axis2 1.6.1 Apache License 2.0
BCEL 5.0 Apache License 1.1
BCEL 5.1 Apache License 2.0
BeanShell 1.3.0 GNU Lesser General Public License 2.1
Boost 1.33.1 Boost Software License 1.0
Bouncy Castle 145 Bouncy Castle 1.5
Codemodel 2.4 2 Common Developer & Distribution License (CDDL) 1.0
com.oreilly.servlet 2008 Artistic License 1.0
Commons Logging 1.1 Apache License 1.1
commons-cli 1.2 Apache License 2.0
commons-codec 1.7 Apache License 2.0
commons-compress 1.2 Apache License 2.0
commons-digester 2.1 Apache License 2.0
commons-discovery 0.2 Apache License 2.0
commons-httpclient 4.0 Apache License 2.0
commons-httpclient 4.1.1 Apache License 2.0
commons-io 3.1 Apache License 2.0
commons-modeler 2.0.1 Apache License 2.0
commons-net 3.2 Apache License 2.0
commons-pool 1.2 Apache License 1.1
DWR 2.0 rc2 Apache License 1.1
 ehcache 1.3.0 Apache License 2.0 SNMP4j 2.1.0 Apache License 2.0
ehcache 2.3.0 Apache License 2.0 Spring Security 2.0.4 Apache License 2.0
Ext JS 2.2 Common Developer & License (CDDL) 1.0 spring-framework 1.2.7 Apache License 1.1
FasterXML ClassMate 0.8.0 Apache License 2.0 StAX 1.0 Apache License 1.1
Findbugs 1.3.9 GNU Lesser General Public License 2.1 StringTemplate 4.0.2 BSD-style license
FreeMarker 2.3.10 BSD License 4.4 Struts Framework 2.0.14 Apache License 2.0
Ganymed SSH-2 for Java build 250 Ganymed SSH-2 for Java License Trilead SSH for Java Build 213 Trilead SSH for Java
Geronimo 1.1 Apache License 2.0 Trilead SSH for Java build213-svnkit-1.3 Trilead SSH for Java
Geronimo 1.4 Apache License 2.0 VI Java API 5.1 BSD - VI Java
Gif89Encoder 1.0 ACME Labs Freeware License 1.0 VServ TCP/IP Apache License 2.0
GlassFish javax.el CDDL + GPLv2 with classpath exception Wiseman 1.0 Apache License 1.1
Google Diff, Match and Patch 20110725 Apache License 2.0 Woden 1.0 Apache License 2.0
google-collections 1.0 Apache License 2.0 Woodstox 4.0.8 Apache License 2.0
Granados 2.0.0 Apache License 1.1 Xalan Java 2.7.1 Apache License 1.1
Groovy 1.5.7 Apache License 1.1 XMLUnit 1.0 BSD License 4.4
Groovy 1.7.6 Apache License 2.0 zlib 1.2.3 zlib License 1.2.3
groovy-wslite 1.0.0 Apache License 2.0
Gson 1.5 Apache License 2.0
Guava 13.0.1 Apache License 2.0
HBA API 2.2.1 Storage Networking Industry Assoc (SNIA) License 1.1
Hibernate 3.2.4 sp1 GNU Lesser General Public License 2.1
Hibernate Validator Apache License 2.0
hybrid labs beautifier 1.1.7 Apache License 1.1
Java SMI Parser Apache License 2.0
javax.el-api CDDL + GPLv2 with classpath exception
javax.validation Apache License 2.0
j-interop 2.03 GNU Lesser General Public License 2.1
j-interop 2.08 GNU Lesser General Public License 2.1
JACOB (Java Com-Bridge) 1.13 GNU Lesser General Public License 2.1
JACOB (Java Com-Bridge) 1.15 M2 GNU Lesser General Public License 2.1
JAX-WS 2.1.3 Common Developer & Distribution License (CDDL) 1.0
JAXB 2.1.5 Common Developer & Distribution License (CDDL) 1.0
JAXB 2.2.3u1 Common Developer & Distribution License (CDDL) 1.1
jaxb-api 2.1 Common Developer & Distribution License (CDDL) 1.0
jaxb-impl 2.1.3 Common Developer & Distribution License (CDDL) 1.0
jaxen 1.1 Apache License 1.1
JBoss 4.2.3_GA 2 GNU Lesser General Public License 2.1
JBoss Logging GNU Lesser General Public License 2.1
JCIFS 1.3.0 GNU Lesser General Public License 2.1
JCIFS 1.3.12 GNU Lesser General Public License 2.1
JCIFS 1.3.14 GNU Lesser General Public License 2.1
JDOM 1.0 JDOM License 1.11
jettison 1.2 Apache License 2.0
Jetty 6.1.26 Apache License 2.0
Jetty 7 Eclipse Public License 1.0
Jibx 1.1 BSD License 4.4
Jibx 1.2.2 BSD License 4.4
Jibx 1.6a BSD License 4.4
JRadiusClient 2.0.0 GNU Lesser General Public License 2.1
Json-lib 2.2.1 Apache License 2.0
Json.NET 3.5 release 8 MIT License
JSR-305 BSD-style license
jTDS SQL Server Driver 1.2 GNU Lesser General Public License 2.1
JUnit 4.8.1 Common Public License 1.0
JUnit 4.8.2 Common Public License 1.0
Log4J 1.2.13 Apache License 2.0
Log4J 1.2.14 Apache License 1.1
Log4Net.dll 1.2.9.0 Apache License 2.0
NpgSql 2.0.10 NpgSql License 2.0.8
oAW 4.2 GNU Lesser General Public License 2.1
OpenSymphony OSCore 2.2.7 Apache License 1.1
OpenSymphony Quartz Scheduler 1.6.1 Apache License 1.1
OpenSymphony SiteMesh 2.2.1 Apache License 1.1
OpenSymphony XWork 2.0.4 Apache License 1.1
Perf4j 0.9.13 Apache License 2.0
PostGreSQL 9.1 PostgreSQL License
Quartz Scheduler 1.6.5 Apache License 2.0
RemCom 1.2 BSD Simple License
Rome 0.8 Apache License 1.1
SAAJ 1.3 Common Developer & Distribution License (CDDL) 1.0
Saxon-B 8 Mozilla Public License (MPL) 1.1
Saxon-B 9.1 Mozilla Public License (MPL) 1.0
saxpath 1.0 Jaxen license
SLF4j MIT License
slf4j - Simple Logging Facade for Java 1.6.1 slf4j license