There are three steps in working out what version of a NOMS/SOVN/STVN/VSN application you have.
- Identify the platform.
- Locate the version information.
- Decode the build number.
Note: To check which version of the ABAP Add-On you have installed, see this wiki article.
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.
URL Ends In
Application Installation Location
Not under J2EE path*
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
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.
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
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|
|1-2||Major Version Level||061 = 2.1|
070 = 3.0
|3||Minor Version Level|
|4||Service Pack Level|
|9-10||Not Used||Always set as "00"|
The following table shows how to decode a build version number of "0702027800".
|07||The application is version 3.0.|
|2||The application is at service pack level 2.|
|0278||The application is using the 278 product build.|
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 Version||Dotted-Quad Format||Example|
|STVN 2.0 SP1||5.1.x.x||22.214.171.124|
|STVN 2.0 SP2|
|STVN 2.0 SP3|