Issue by starting AdminUI at boot time in Linux machine

Products

• SITEMINDER

Issue/Introduction

Running AdminUI, this one can't start properly at boot time. Starting it manually after the boot of the machine, a command line needs to be open and maintained open until the next reboot of the machine. How to avoid that, and make the AdminUI starting properly at boot time?

 

Resolution

To start it manually or at boot time automatically as root following these:

1. Leaving a program running when closing a command line:
   
   When launching a program in PuTtY SSH session on Linux box, and unfortunatly, needing to leave it, without interruption of the execution of the program, use the disown command to make your program not get the SIGHUP when closing the session and keep it running in the background:
   
   1 - Hit "ctrl+z" to pause the program and get back to the shell;
2 - Type "bg" to run it in the background;
3 - Type "disown -h [job-spec]" where [job-spec] is the job number.
   
   To illustrate when starting the AdminUI:
   
   as root:
   
   # cd /{home_AdminUI}/bin/
# ./standalone.sh
"ctrl+z"
# bg
# disown -h %1
   
   and then, close the command line.
   
   On another command line, check if the AdminUI is still running in memory:
   
   # ps auxww | grep adminui
root        1509  139 74.3 5335688 1352892 ?     Sl   11:19   3:55 /{home_AdminUI}/runtime/bin/java -D[Standalone] -server -Djdk.tls.ephemeralDHKeySize=2048 -Xms1024m -Xmx1536m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dcom.sun.jersey.server.impl.cdi.lookupExtensionInBeanManager=true -Djavax.net.ssl.keyStore=/{home_AdminUI}/standalone/configuration/keyStore.jks -Djavax.net.ssl.keyStoreType=jks -Djavax.net.ssl.keyStorePassword=changeit -Djavax.net.ssl.trustStore=/{home_AdminUI}/standalone/configuration/trustStore.jks -Djavax.net.ssl.trustStoreType=jks -Djavax.net.ssl.trustStorePassword=changeit -Dcom.sun.jndi.ldap.object.disableEndpointIdentification=true -Dcom.ca.largestore=false -Dorg.jboss.boot.log.file=/{home_AdminUI}/standalone/log/server.log -Dlogging.configuration=file:/{home_AdminUI}/standalone/configuration/logging.properties -jar /{home_AdminUI}/jboss-modules.jar -mp /{home_AdminUI}/modules org.jboss.as.standalone -Djboss.home.dir=/{home_AdminUI} -Djboss.server.base.dir=/{home_AdminUI}/standalone -c standalone-full.xml -b 0.0.0.0 -Dnete.j2ee.vendor=jboss -Djboss.as.management.blocking.timeout=900
   
   
2. Use systemctl config file to make the AdminUI stopping and starting as root at boottime (1).

 

Additional Information

 

1. Systemctl conf to start and stop the AdminUI and the Policy Server