README for the HP Neoview Transporter Java Client (R2.5)

Checking Version Compatibility
Before installing the client product, you must check that the product is compatible with the
version of the Neoview release installed on the Neoview platform.
For all client products, refer to the Neoview Client and Platform Compatibility Reference for version
compatibility information. This document is available at http://www.hp.com/go/neoviewdocs.
Getting the Version of an Installed Client Product
If you already have the client product installed on your workstation, follow these steps:
• For supported UNIX-based platforms, use the command: jtrans.sh -version
• For Windows systems, use the command: jtrans.bat -version
Installation of the Neoview Transporter Java Client
NOTE: If you plan to install multiple client products, the Neoview Windows Client Package
provides a collection of Windows drivers and tools that you can install collectively to save time.
For more information, refer to the README for the HP Neoview Windows Client Package
available at http://www.hp.com/go/neoviewdocs.
These installation instructions apply to Neoview Release 2.5 and subsequent updates of the
product until otherwise indicated by a replacement README.
NOTE: These instructions do not necessarily apply to updates earlier than the client update
number shown on the title page of this document.
As of Neoview Release 2.4, the Transporter API components are included in the Transporter
installation.
• Installation Package
• Installation Requirements
• Installation Instructions
Installation Package
The Neoview Transporter Java Client is available as a downloadable JAR file,
HP_Neoview_Transporter_Java_Client_Vx.y.z_nnnnnn_nnn.jar.
Vx.y.z
Is the version assigned to the client product, such as V2.5.0. This number reflects
the version of the client product and might not be the same as the Neoview
release version. The client product version includes the major Neoview release
number, x.y, and the client update number, z.
The client update number is 0 the first time that the client product is issued for
a major Neoview release, such as Release 2.5. The update number then increases
by one for each update of the client product for the major Neoview release. For
example, V2.5.0 is the first release of the client product for Neoview Release
2.5, and V2.5.1 is the first client update for Neoview Release 2.5.
The client product version remains in sync with the major Neoview release,
such as Release 2.5, but only if the client product is changing (that is, has defect
repair or new features) for the release. If a client product is not changing, it
retains its current client product version.
Client products can be changed independently of a minor Neoview release,
such as R2.4 SP2 or R2.4.2. Each update of a client product increases the update
number of the client product version. Because the client update numbers increase
Checking Version Compatibility 5