Is there a process for starting and stopping CLM services when servers are rebooted?
Is there a need to ensure that the services are stopped prior to server reboot or just make sure they have come up after the reboot? Currently we just ensure the services are up, but the project has not reached SIT and Prod yet. I want to make sure that the tools are working smoothly before the impact becomes greater. Our environment consists of the full CLM 6.03 suite - JTS, CCM, GC, RS, RELM, LDX, RDNG, RQM, DCC, LQE, RLKS |
Accepted answer
I recommend to shutdown the apps within the normal server shutdown process.
A S selected this answer as the correct answer
Comments On Windows, you have the services with the start/stop scripts and this controls a proper shutdown of the app. Yes, on Windows host configuring the Jazz Team Server to run as a Windows service is the safer mode to have the application properly started/stopped within OS.
A S
commented Sep 10 '17, 10:26 a.m.
Thank you Guido, Servizi and Daniel.
SEC Servizi, a question - pardon my ignorance here. If the JTS server becomes a Windows service, does it automatically shut down cleanly when rebooting the Windows server?
SEC Servizi
commented Sep 11 '17, 3:11 a.m.
Yes, it does. |
One other answer
I'm using following apache deamon to register and start stop the service:
@echo on |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
I don't know what the 'official' answer will be from IBM - but my experience has been that you are better off to gracefully shutdown all server apps before shutting down the server(s) hosting the apps.
The risk of not shutting down the applications properly is getting the index corrupted. It will be costly to rebuild indexes for applications with large repositories, particularly for CCM and RM - it can take hours if not days.