Question & Answer
Question
How do I use the FileNet P8 Content Engine (CE) Version Tools?
Cause
Engineering often requires information regarding the exact P8 release version installed on the CE. This information assists in issue investigation by providing details about the customer environment. Engineering can also use this information when setting up a test system for problem duplication, or to determine whether a similar issue has been addressed in a later software release version.
Answer
Content Engine has three separate version tools. One is a wizard-based graphical user interface tool that prompts for required input. The other two are command-line tools, one for Windows-based files, and the other for Java-based files. All are installed by default in the \Program Files\FileNet\Content Engine directory when the CE software is installed.
CE wizard-based tool: The versionCE.exe program can be launched either from Windows Explorer or the Windows command prompt. The following input is required:
Output File Path.
Option to Append or Overwrite if the output file already exists.
Option to display All Properties or only the Primary properties version information.
Option to specify the output file format as .csv or .txt.
Option to include the file Byte Count Info (file sizes) in the output
By default, the output file will be in .csv format and named CEVersion.csv. This wizard-based tool simply provides an interface to run the command-line version tools described below.
CE command-line tool for Windows-based files: The versionWinDir.exe tool generates a list of the software versions of the CE .exe, .dll and .ocx files. It is run using the following options and syntax:
versionWinDir.exe -d <dir_search_path> -o <output_file_path.ext> -a [Append|Overwrite_flag] -b [ByteCount_flag] -p [AllProperties|Subset_flag]
Full path names must be provided for the <dir_search_path> (source directory) and the <output_file_path.ext> (output file), and both must be delimited by double quotes. The output file name requires a .csv or .txt extension. The flag options are binary True or False options. For example, run the following command to produce all option outputs:
versionWinDir.exe -d “C:\Program Files\FileNet\Content Engine” -o “C:\temp\CEVer_server1.csv” -a True -b True -p True
CE command-line tool for Java-based files: Use the versionCE.jar tool to determine the software versions of the Content Engine .jar files. It is run using the following options and syntax:
java -cp versionCE.jar com.filenet.versionCE.versionJar <jar_file_name> <output_file>
NOTE:
Full path names must be provided for <jar_file_name> and <output_file>, and both must be delimited by double quotes.
Add the “C:\Program Files\FileNet\Content Engine\_jvm\bin” folder to the system Path variable before attempting to run versionCE.jar.
Run versionCE.jar from the directory where the .jar files and versionCE.jar re located; this is usually C:\Program Files\FileNet\Content Engine\.
For example:
java -cp versionCE.jar com.filenet.versionCE.versionJar “C:\Program Files\FileNet\Content Engine\pe.jar” “C:\temp\CEVer_pejar.txt”
Data to collect: Output generated by the above commands.
For more information: Refer to the “FileNet P8 Version Tools Technical Notice” found on the http://www-306.ibm.com/software/data/content-management/filenet-product-family/support.html website.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21394309