Release Notes
PulseNET Enterprise 3.1.0
PulseNET is a software application used for monitoring devices in Industrial Communications
networks. Each device that PulseNET monitors serves a specific function in the network. These
functions may include acting as a bridge, router, access point/base station, or remote/subscriber. The devices can be widely dispersed geographically and are able to operate with different bandwidths, depending on radio type and frequency. For additional information on
specific Industrial Communications products, refer to the GE MDS website:
http://www.gedigitalenergy.com/Communications/
PulseNET Base is intended for small-scale operations with a need to monitor up to 500 devices. PulseNET Enterprise is intended for large-scale operations with a need to monitor up to
25,000 devices.
These Release Notes provide:
• A list of new and updated features
• Workarounds for any known issues
• Late-breaking news about the software
Consult this document before installation since it contains updated information and procedures that may be more recent than those in earlier PulseNET guides.
MDS 06-6560A01
PulseNET Enterprise
Release Notes
New In This Release
Platform Support
• Retirement of 32-bit support—As of January 1, 2015, PulseNET installers will no longer be
available for download for 32-bit operating systems. For customers with special needs,
please contact GE MDS PulseNET Support. Customers who need to migrate from 32- to
64-bit platforms can follow the step-by-step migration procedure explained below.
Operation and Administration
• AP failover messages now reported in the Audit Log—Previously, failover messages for redundant APs generated alerts, but now they are also reported in the Audit Log. [PNDEV-40]
• Notification spinner during firmware upload—For large firmware image files there is now
a spinner to note that the upload is occurring. [PNDEV-45]
• MAC address change notification—Previously, MAC address change events generated
alerts, but now they are also capable of issuing notifications. [PNDEV-50]
• Improved Google Mapping of collocated devices—New grouping icons have been added
which show collocated devices by expanding the device set with identical GPS coordinates. [PNDEV-54]
• SD Passphrase Push Enhancements—Previous passphrases are now stored in encrypted
format, allowing administrators to review or recover used passphrases. [PNDEV-88 & 234]
• Serial Terminal Type now configurable on a port-by-port basis—Previously, serial terminal
type settings were global. Now the type of serial connection is configurable on a portby-port basis. [PNDEV-95 & 213]
• Ability to add new device groups during the authorization process—Previously, newly discovered devices could only be assigned to existing device groups. Now if the appropriate device group does not yet exist, it can be created during the authorization process.
[PNDEV-174]
• Firmware Push filtering for iNET radios with newer firmware—Since newer iNET devices
should not receive firmware versions earlier than rev 8.0.0, the firmware push interface
does not list newer devices as candidates for older firmware images. [PNDEV-214]
• Allow duplicate snmpv3 usernames with different passwords—Previously, both the username and password were required to be unique. Now a single user account is allowed
multiple times as long as the passwords are unique. [PNDEV-215]
• SD Master Station management—PulseNET is now capable of monitoring and managing
the current release of the GE MDS SD Master Station. [PNDEV-222]
• New Orbit MCR 900 management features—The Orbit MCR 900 is now supported in
PulseNET, with new user interface and data collection functionality. [PNDEV-225]
2
PulseNET Enterprise
Release Notes
• SD network address parameter now displayed—The SD radio network address value is
now displayed as a configuration parameter in the radio detail display. [PNDEV-232]
• Tab labels now identify AP/Master as well as Remote/Subscriber—Since different GE MDS
radio models use varying terms to describe the radio’s roles, the Summary tabs now
reflect that both terms can apply to radios under those tabs. [PNDEV-233]
• Discovery and Collection Improvements—Improved discovery and collection to avoid
“read” lock issues. [PNDEV-269]
• IP address now displayed on firmware push device list—The radio IP address is now shown
on the list of devices in the firmware push display. [PNDEV-277]
• Device model now displayed on the topology explorer popup—The radio device model has
been added to the Topology Explorer popup display. [PNDEV-278]
• Orbit radios now show in the All Device Detail report—Previously, Orbit radios were not
included in the All Device Detail report. They are now available in the report output.
[PNDEV-279]
• New Merc 3650 AP Frequency Report—A new report shows Mercury 3650 AP radios and
the frequency they are using. [PNDEV-280]
• iNET Terminal Server to TransNET Master Topology—Improvements to the topology display for iNET radios being used as terminal servers for connecting TransNET Master
radios. [PNEE-180]
Installation and Upgrade
Customers currently using PulseNET version 3.0.0 or above will be able to upgrade directly to this new release using the upgrade package (Windows ZIP or Linux TAR archive).
For initial considerations and step-by-step directions, see the “Upgrading PulseNET”section in the Installation Guide. For detailed assistance, please contact GE MDS PulseNET
Support.
Customers who require a fresh PulseNET install or who are currently using a PulseNET
version prior to 3.0.0 should first install the 3.0.0 version using the executable installer
(Windows EXE or Linux BIN). Once 3.0.0 has been installed, the 3.1.0 upgrade process
can be followed as described above.
Migrating from 32-bit to 64-bit machines
The following migration process can be followed in order to move an existing PulseNET
installation from a 32-bit platform to a 64-bit machine.
1 Shut down the PulseNET services on the existing 32-bit machine.
2 Backup the current PulseNET installation directory structure on the 32-bit machine.
3 Copy the backup file from the old 32-bit machine to the new 64-bit machine.
3
PulseNET Enterprise
Release Notes
4 Expand/restore the 32-bit PulseNET directory structure to create the same structure on
the new 64-bit machine.
5 Obtain a 64-bit installer for the version of PulseNET to which you want to upgrade.
6 Run the 64-bit installer for the target PulseNET version, which will upgrade the application binaries.
7 If on a Windows platform, manually install the Windows services using the procedure
described in the PulseNET Install Guide (PulseNET p.15ff, PulseNET Enterprise p.22ff).
8 Start the PulseNET services on the new 64-bit machine and verify that the upgrade is
taking place normally.
9 Apply a new license key to the PulseNET instance now running on the 64-bit machine.
If PulseNET will not start, call GE MDS PulseNET Support for assistance. It may be necessary to install an independent 64-bit version of PulseNET and copy the jre folder to the
jre folder of the migrated system.
Topology Explorer GIS Mapping
Mapping of collocated devices is typically a challenge, but
in this release of PulseNET a new grouping icon shows how
many devices are collocated at identical GPS coordinates.
By clicking on the grouping icon, you can drill in to the specific site. One more click will expand the set of collocated
devices to show you each individual device with those GPS
coordinates, as shown below. Clicking on an individual device icon will display its summary information.
4
PulseNET Enterprise
Release Notes
SD Passphrase Management
The previous release of PulseNET allowed administrators to change the security passphrases on SD master radios and their downstream remotes. In this new release of
PulseNET, the administrator is able to click Display Passphrase History to review the list
of passphrases that have been used on a particular SD network (master and associated
remotes). This is the only place in PulseNET where a privileged user is allowed to view
an unencrypted passphrase.
A privileged administrator is also allowed to edit the passphrase history by deleting
previous passphrases that PulseNET should no longer remember. This is helpful because
PulseNET will not permit passphrases to be reused, so deleting previous passphrases
from PulseNET allows the use or recovery of a previous passphrase on the network.
Non-privileged users are allowed to see that a new passphrase has been pushed
throughout the network, but they are never allowed to see the unencrypted passphrases. The Audit Log tab on a specific device will indicate whether a new passphrase
has been pushed.
5
PulseNET Enterprise
Release Notes
DLINK Seedfile Features
In previous versions of PulseNET, the terminal type could be set on a global basis and
applied to every terminal server and port. However, each port on a terminal server may
need to be configured independently with different settings. In this new release of
PulseNET you can set the terminal type on a port-by-port basis. You are also allowed to
add several terminal server IP addresses through the wizard, as long as those terminal
servers use the same port number, discovery method, sleep mode, and terminal type.
This new version of PulseNET makes it easier to manage lists of terminal server settings
by giving you the ability to Import and Export your seedfile settings to comma delimited files.
6
PulseNET Enterprise
Release Notes
Adding Device Groups During Authorization
During the device discovery and authorization
process, the new devices must be assigned to a
device group. In previous releases of PulseNET,
the device group could be chosen only from the
list of existing device groups. In this new release
of PulseNET a new device group can be created
if one did not previously exist for the newly discovered device. Click the New Subgroup button
to create the new device group that is required
for the newly discovered device, as shown below.
SNMP v3 Usernames with Multiple Credentials
In previous versions of PulseNET, the SNMP v3 usernames were required to be unique,
even if a particular username had multiple SNMP v3 credentials available. In this new
release of PulseNET you are allowed to create multiple credentials for a single username, as shown below.
Orbit MCR 900 Support
In the previous version of PulseNET, the Orbit Platform devices were shown on the Summary display, but distinguishing between the varying roles was more difficult. In this
7
PulseNET Enterprise
Release Notes
new release of PulseNET, there is a new Summary display filter that allows you to select
which types of devices you want to see in the table. You may show all of the LAN devices or you may choose specific sets of devices to include in the display, as shown
below.
In this new release of PulseNET, you will see a blue arrow icon on the Orbit MCR 900 nx
interface, which allows you to navigate to the detailed information for this interface.
Orbit 900 Access Point
The Orbit 900 Access Point shows an interface type of “900 Access Point”.
The Orbit 900 Access Point display for the nx interface has four tabs containing information. The Performance tab shows graphs for interface throughput and error counts.
8
PulseNET Enterprise
Release Notes
The Status tab includes the Administrative and Operational status of the 900 nx interface, while the Configuration tab displays the current modem in use and the device
mode setting.
The Remotes Connected tab provides the device count, followed by specific device
details in tabular form (if the connected remotes have been discovered and authorized
in PulseNET).
Orbit 900 Remote
The Orbit 900 Remote or Store-and-Forward device allows you to click the blue icon on
the 900 nx interface table to navigate to additional details about that interface.
9
PulseNET Enterprise
Release Notes
The Orbit 900 nx interface Status and Configuration tabs display the same type of information that was available for Access Points. The Performance tab shows graphs for
the following metrics:
• Received Signal Strength Indicator (RSSI)
• Link Quality Index (LQI)
• Interface throughput (In/Out)
• Interface errors (In/Out)
The Orbit 900 Remote nx interface display also shows the upstream Access Point to
which this remote is associated.
SD Master Station Support
Early releases of the SD Master Station were supported in previous versions of PulseNET.
In this new version of PulseNET the next release of the SD Master Station is also supported. These devices will now be discovered and authorized as Master Stations. The
PulseNET Summary display will clearly identify them as such.
10
PulseNET Enterprise
Release Notes
The PulseNET Access Point/Master detail display shows configuration parameters, including the name of the currently active radio, which is usually identified by either the
letter “A” or “B”.
The Remotes/Subscribers Connected tab displays information and drilldown links for all
downstream devices.
11
PulseNET Enterprise
Release Notes
If an SD Master Station failover occurs, an alert will be generated in PulseNET indicating
that a failover has been detected and showing which radio is now active.
The detail display for each of the downstream devices will show the SD Master Station
“parent” to which that remote is associated.
12
PulseNET Enterprise
Release Notes
Known Issues and Workarounds
• SD radios with firmware version 4.1.5 or earlier using “Packet with MAC” mode should
not be configured for passive data collection. Upgrade the SD firmware to avoid potential issues with passive data collection.
• Mercury 5800 radios with firmware version lower than 3.2.6 will not provide the new PA
Temperature metric to PulseNET. Upgrade the Mercury firmware to avoid this condition.
• If you add a master device or replace a master device in a Cold Redundant Cluster, any
previously defined maintenance windows for the cluster will no longer be available.
• When monitoring 9810 devices, the radio’s RTU simulator must be off in order for
PulseNET to collect radio performance data.
• The current release of the SD Master Station does not support bulk passphrase changes.
• Orbit devices must have firmware version 2.0.9 or greater for PulseNET to manage all
of the currently available interface types. Initially the Orbit radios do not have a default
device name, and radios without a device name will not be displayed on the Firmware
Detail report. This should be remedied in Orbit firmware release 3.0.3.
• Radio frequencies for the Mercury 3650 are truncated to a whole number. The decimal
portion of the frequency will be added in the next PulseNET release.
For More Information
If you have questions regarding PulseNET installation or operation, please contact GE
MDS Support.
Phone: 585-241-5510
Fax: 585-242-8369
Email: gemds.techsupport@ge.com
Website: www.gemds.com
13
Quest Copyright Notice
© 2014 Quest Software, Inc.
ALL RIGHTS RESERVED.
Patents
This product is protected by U.S. Patents #7,979,245 and
#8,175,862. Additional patents pending.
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 photocopying and recording, for any purpose other than the
purchaser’s personal use without the written permission of
Quest Software, Inc.
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 Software’s
trademarks, please see http://www.quest.com/legal/
trademark-information.aspx. Other trademarks and registered trademarks are property of their respective owners.
The information in this document is provided in connection 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 AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY
WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED, OR
STATUTORY WARRANTY RELATING TO ITS PRODUCTS, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, 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) ARISING 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 warranties 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 commitment to update the information contained in this document.
Third Party Contributions
MDS PulseNET contains some third party components. For
a complete list, see License Credits below.
If you have any questions regarding your potential use of
this material, contact:
About Quest Software, Inc.
Established in 1987, Quest Software (Nasdaq: QSFT) provides 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 access management, monitoring, and user workspace management 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.
Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656
www.quest.com
email: legal@quest.com
The majority of GE MDS radios deployed since 1985 are still
installed and performing within our customers' wireless
networks. That’s because we design and manufacture our
products in-house, according to ISO 9001, which allows us
to control and meet stringent global quality standards.
Refer to our web site for regional and international office
information.
Thanks to our durable products and comprehensive solutions, GE MDS is the wireless leader in industrial automation—including oil and gas production and transportation,
water/wastewater treatment, supply, and transportation,
electric transmission and distribution, and many other utility 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 expect 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, reliable 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 Customer 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 customer’s 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 using 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 Agreement 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
ehcache 2.3.0 — Apache License 2.0
Ext JS 2.2 — Common Developer & License (CDDL) 1.0
FasterXML ClassMate 0.8.0 — Apache License 2.0
Findbugs 1.3.9 — GNU Lesser General Public License 2.1
FreeMarker 2.3.10 — BSD License 4.4
Ganymed SSH-2 for Java build 250 — Ganymed SSH-2 for Java License
Geronimo 1.1 — Apache License 2.0
Geronimo 1.4 — Apache License 2.0
Gif89Encoder 1.0 — ACME Labs Freeware License 1.0
GlassFish javax.el — CDDL + GPLv2 with classpath exception
Google Diff, Match and Patch 20110725— Apache License 2.0
google-collections 1.0 — Apache License 2.0
google-maps-utility-library-v3 — Apache License 2.0
Granados 2.0.0 — Apache License 1.1
Groovy 1.5.7 — Apache License 1.1
Groovy 1.7.6 — Apache License 2.0
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
OverlappingMarkerSpiderfier for Google Maps API v3 — MIT License
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
SNMP4j 2.1.0 — Apache License 2.0
Spring Security 2.0.4 — Apache License 2.0
spring-framework 1.2.7 — Apache License 1.1
StAX 1.0 — Apache License 1.1
StringTemplate 4.0.2 — BSD-style license
Struts Framework 2.0.14 — Apache License 2.0
Trilead SSH for Java Build 213 — Trilead SSH for Java
Trilead SSH for Java build213-svnkit-1.3 — Trilead SSH for Java
VI Java API 5.1 — BSD - VI Java
VServ TCP/IP — Apache License 2.0
Wiseman 1.0 — Apache License 1.1
Woden 1.0 — Apache License 2.0
Woodstox 4.0.8 — Apache License 2.0
Xalan Java 2.7.1 — Apache License 1.1
XMLUnit 1.0 — BSD License 4.4
zlib 1.2.3 — zlib License 1.2.3
Download PDF