I have already expressed my joy in several articles here that Sametime now works without the WebSphere Application Server (WAS) and without Db2. And that because of this fundamental change there were some gaps in the short term, which all could be closed/repaired quickly and easily. This article also fits into this category:
In the past, the wasservice.sh shell script made let you install services for everything (except the Db2 instance) under Linux. This way Sametime was started automatically when the operating system was started. But without WAS there is no wasservice.sh.
For the Sametime Community Server, which runs as a task in the Domino server, there is a proven option, although not published by HCL: Domino on Unix/Linux Start Script by Daniel Nashed.
But for the new Sametime Proxy Server there is no such thing yet. Not officially. In response to the question of What is the best practice to start Sametime in Linux / RHEL 7.8 automatically on boot up? Anthony Payne, HCL created a systemd configuration: Sametime v11 on Linux - How to create a service for the Sametime Proxy.
For myself, I
For me I have made a few small adjustments:
- User, group and service are called
sametimeproxy. I find this more suitable than
- As a dependency I added
syslog.targetto ensure that this service is already running.
PIDFile=/opt/hcl/sametimeproxy/temp/tomcat.pidI specify that the process ID of the Tomcat server should be stored in this file.
Restart=on-failureI tell the service to restart automatically in case of a crash or unclean exit.
- I refer to the new OpenJDK with
Environment="JAVA_HOME=/opt/hcl/sametimeproxy/openjdk"instead of the IBM JDK 8.
The remaining commands for preparation and post processing only need to be adapted to the name change.
root (or with
adduser -m -U -d /opt/hcl/sametimeproxy -s /bin/false sametimeproxy
chown -R sametimeproxy:sametimeproxy /opt/hcl/sametimeproxy
systemctl enable sametimeproxy
systemctl start sametimeproxy
systemctl stop sametimeproxy
Anthony writes in his answer, that with version 11.5 a corresponding start script should be included in the installation again.