after wasting a decent amount on installing the ODM Server Component as a service on a Windows 2008 Server i want to provide my findings and a solution to it.
ODM depends on MS JAVA. Infor states in the readme in the ODM installer, that it's not dependent on it and one can use the SUN/Oracle JVM. This is wrong. The service wrapper (executable that the OS is triggering - after being triggered it starts up the JVM) is dependend on the MS JVM, so you will never be able to run ODM as a service. See the following incidents #726548, #691501, #719526
Infor is always suggesting to install MS JVM, this is not a viable fix, as it isn't supported anymore. See: http://www.microsoft.com/About/Legal.../Java/FAQ.aspx
Install ODM, Process fails to setup a working service. Download a different Service Wrapper. http://forge.ow2.org/projects/javaservice/
. This wrapper resembles the broken one infor is using. It even exists in a 64 Bit Version.
Generate a own "Installer" -
@rem echo off
set JVMDLL="C:\Program Files\Java\jre6\bin\server\jvm.dll"
set JVMCLSPATH="C:\Program Files (x86)\Infor\ERP LN ODM Vault Server\dmfsvs"
set PARAM="C:\\Program Files (x86)\\Infor\\ERP LN ODM Vault Server\\dmfsvs\\com\\vault\\properties\\ODMService-ERPTEST.properties"
set STDOUT="C:\Program Files (x86)\Infor\ERP LN ODM Vault Server\dmfsvs\out_ODMService-ERPTEST.txt"
set STDERR="C:\Program Files (x86)\Infor\ERP LN ODM Vault Server\dmfsvs\err_ODMService-ERPTEST.txt"
@echo . Using following version of JavaService executable:
@echo Installing service... Press Control-C to abort
%JSEXE% -install %SERVICENAME% %JVMDLL% -Djava.class.path=%JVMCLSPATH% -ea -start %STARTCLASS% -params %PARAM% -out %STDOUT% -err %STDERR%
%JSEXE% -queryconfig %SERVICENAME%
Just maintain the Parameters on the script to relate to your prior installation.
For a manual Startup you will need a different startup script like this.
rem Second parameter of the following command line is a location
rem of a properties file in the Vault Server classes tree.
rem Extension of this file must be "properties".
echo Vault Server has been started with the "Server4001.properties" parameters file.
echo See output of the Vault Server in the log file.
echo To stop the Vault Server just close this window.
echo And now You can minimize the window...
java com.vault.server.VaultServer com\vault\properties\ODMService-TURING.properties
Please exchange the properties scripts, they are per default called Server4001 or Server2001. I changed it to the names of the environments for which they are responsible. Naming it with ports is somewhat dangerous.
In my case after setup the Service ODMService-ERPTEST exists in the Control Panel - Services.
Hope this helps, fixing it like the support does is quick and dirty.