M
Matt Baker
Guest
Some instructions: open a command shell with elevated privileges start a proenv session: proenv>c:\progress\openedge120\bin\proenv Check OEM service status: proenv>%OEM%\bin\tcman service status Stop OEM proenv>%OEM%\bin\tcman service stop or proenv>fathom -stop using an editor open %OEM%\bin\fathom_setenv.bat add in the set PROMSGS = Save the file and exit unregister the service proenv>%OEM%\bin\tcman service unregister re-register the service (the two environment variable lines restore the human readable name and description...the can be anything really, or left out if you don't care) proenv>set PR_DISPLAYNAME=OpenEdge Management Service for OpenEdge 12.0 proenv>set PR_DESCRIPTION=OpenEdge Management Service for OpenEdge 12.0 proenv>%OEM%\bin\tcman service fathom_12.0 register start OEM proenv>%OEM%\bin\tcman service start or proenv>fathom -start tcman uses Tomcat's windows registry tool to register services. OEM uses PAS as it's webserver foundation and can take advantage of this. But when tcman does the registration the environment variables and system properties are all copied into the windows register, which requires registration if anything is changed.
Continue reading...
Continue reading...