How to start WAS Liberty as a Windows service for CLM 6.0.1?
WAS Liberty has replaced Apache Tomcat as the out of the box application server. It was well documented how to start Tomcat as a Windows service. There is no equivalent documentation for WAS Liberty. Searching Google has not returned any useful results.
Has anyone figured out how to do this?
Accepted answer
Just to add more more information to Shubjit's answer.
There is already a RFE for Liberty fo running it as a Windows service: https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=29865
As Shubjit pointed out, using Apache Commons Daemon is an option. Here is what I did to create the service using Apache Commons Daemon to run CLM 601 in Liberty, I hope it helps:
1. Download the binaries for Windows from http://www.apache.org/dist/commons/daemon/binaries/windows/
2. Unzip the downloaded file
3. Run the following script to create a Manual service. You need to change the values in the variables, and you might need to change other values too (e.g. --Startup if you want this service to be automatic):
There is already a RFE for Liberty fo running it as a Windows service: https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=29865
As Shubjit pointed out, using Apache Commons Daemon is an option. Here is what I did to create the service using Apache Commons Daemon to run CLM 601 in Liberty, I hope it helps:
1. Download the binaries for Windows from http://www.apache.org/dist/commons/daemon/binaries/windows/
2. Unzip the downloaded file
3. Run the following script to create a Manual service. You need to change the values in the variables, and you might need to change other values too (e.g. --Startup if you want this service to be automatic):
@echo off set DAEMON_EXEC="C:\commons-daemon-1.0.15-bin-windows\amd64\prunsrv.exe"
set SERVER_START_COMMAND="C:\CLM\6.0.1\server\server.startup.bat"
set SERVER_START_COMMAND_PATH="C:\CLM\6.0.1\server"
set SERVER_STOP_COMMAND="C:\CLM\6.0.1\server\server.shutdown.bat"
set SERVER_STOP_COMMAND_PATH="C:\CLM\6.0.1\server"
set LOG_PATH="C:\CLM\6.0.1\server\logs\daemon"
set SERVICE_NAME=CLM601_LIBERTY
set SERVICE_DISPLAY_NAME="CLM 6.0.1 running in Liberty Profile"
set SERVICE_DESCRIPTION="CLM 6.0.1 running in Liberty Profile"
set INSTALL_SERVICE_COMMAND=%DAEMON_EXEC% //IS//%SERVICE_NAME% --Startup=manual --DisplayName=%SERVICE_DISPLAY_NAME% --Description=%SERVICE_DESCRIPTION% ++DependsOn=Tcpip --LogPath=%LOG_PATH% --StdOutput=auto --StdError=auto --StartMode=exe --StartPath=%SERVER_START_COMMAND_PATH% --StartImage=%SERVER_START_COMMAND% --StopMode=exe --StopPath=%SERVER_STOP_COMMAND_PATH% --StopImage=%SERVER_STOP_COMMAND%
%INSTALL_SERVICE_COMMAND%
Comments
1 vote
5 other answers
Hi Jeffery
I found this forum link and there is a user who has confirmed that it works.
Comments
Can't seem to comment on this topic so asking a question in the answer box. The Apache document says the following:
Both Win32 and UNIX like platforms are supported. For Win32 platforms use procrun. For UNIX like platforms use jsvc.
Has anyone used this on a 64x windows system
Comments
As I said above, I have tried Apache Daemon with multiple versions 6.0.5 - 6.0.6.1 and while it works in terms of creating a Windows service that can be started and stopped, my experience was that there is definitely a problem cleanly stopping liberty and the apps running in it during Windows shutdown.
What seems to happen is that Windows is so keen to shutdown quickly that it waits a nominal 12 seconds then carries on shutting down. On my VM, manually stopping the service takes about 25s for Liberty to exit and release RAM, watching Task Manager. From the same starting point with the service running I can restart Windows in 15s - this has to be stopping Liberty and DB2 dead, in the middle of whatever it was doing.
This is a hazard for at least DOORS Next Generation, which on subsequent startup often complains that the app wasn't cleanly shutdown - and if it wasn't cleanly shutdown this is risking index corruption which might require a full reindex. And of course running Liberty as a service is formally not supported.
As a result I'd avoid Apache Daemon on any production/staging environment which might have non-admin-initiated server shutdown/restarts.
Be great if anyone can tell me how to configure Windows to be more patient?
A MUCH easier way is to use the WIndows task panels. This requires no external tool, libraries, or shell scripts.
I've documented that here:
Comments
I need help windows service for CLM 6.0.1is not working properly.
https://validedge.com/err-connection-timed-out/
Comments
