How to check your NOMS SOVN STVN VSN application version

There are three steps in working out what version of a NOMS/SOVN/STVN/VSN application you have.

  1. Identify the platform.
  2. Locate the version information.
  3. Decode the build number.

Note: To check which version of the ABAP Add-On you have installed, see this wiki article.

Identify Platform

The first step in determining how to find out what application version you have installed is to identify what platform the application is deployed under.  The URL used to access the application is probably the quickest way to do this, but if you only have access to the file system and know where the application is installed this can also be used to determine the platform.

Platform URL Ends In Application Installation Location
.NET
.aspx
Not under J2EE path*
JAVA .jsp Under J2EE path*

* e.g. A J2EE (Java 2 Platform, Enterprise Edition) path would be something like - "D:\usr\sap\CED\J00J2EE\cluster\apps\Nakisa\OrgChart"

Locate Version Info

File System

In all application versions, there is a file that can be found in the "root" folder of the application called 'ProductVersion' (the case of this file name may vary between versions).  This file contains the information we're after.

For different versions of the application, the content of the file not only differs, but also the structure and format.  The key piece of information we are looking for however is easily identifiable.  The first line always holds the 'Build Version' which is what we need to determine the version of the deployed application.

The table below shows some example file structures.

NOMS 3.0 Application

Build Version: 2.8.21.1
Build Date: 21/03/2008 13:24


Build Version 0702027800
Build Date 20120328 0705Target Platform: Netweaver

Administrator Console

Using the Administrator Console, you can access version information without having direct access to the file system.

  • Login to Admin Console.
  • Select a build and click the 'Load' button.
  • Once the welcome page has loaded, version information will be displayed.

The version information not only includes the build version number (which is what denotes the exact version we're on), but also the version of the application (e.g. 3.0 OrgChart) and the service pack level.

Decode a Build Number

Platform: JAVA

Application Versions = STVN 2.1 / STVN & SOVN 3.0
Build version numbers for Java based applications are defined as a ten digit number.

Build version Number
DigitsDescriptionNotes
1-2Major Version Level061 = 2.1
070 = 3.0
3Minor Version Level
4Service Pack Level
5-8Build Level
9-10Not UsedAlways set as "00"

The following table shows how to decode a build version number of "0702027800".

ValueExplanation
07The application is version 3.0.
0
2The application is at service pack level 2.
0278The application is using the 278 product build.
00-

Platform: .NET

Application Versions = NOMS / STVN 1.0 / STVN 1.1 / STVN 2.0 / STVN 2.1

Build version numbers for .NET based applications are defined as a dotted-quad (four numbers separated by three periods).  The first two numbers of the dotted-quad identify which application version is being used.  The table below provides a breakdown of the product version and the build version number with an example in each case.

Product VersionDotted-Quad FormatExample
NOMS 20072.8.x.x2.8.25.5
STVN 1.02.9.x.x2.9.44.2
STVN 1.1
STVN 2.03.0.x.x3.0.10.2
STVN 2.0 SP15.1.x.x5.1.40.1
STVN 2.0 SP2
STVN 2.0 SP3
STVN 2.16.0.x.x6.0.67.1

Labels

noms noms Delete
vsn vsn Delete
nakisa nakisa Delete
sovn sovn Delete
stvn stvn Delete
version version Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.