This documentation supports the 9.0 version of BMC Atrium Single Sign-On, which is in "End of Version Support." However, the documentation is available for your convenience. You will not be able to leave comments.

Click here to view the documentation for a supported version of Remedy Single Sign-On.

Stopping and restarting the BMC Atrium Single Sign-On server

This section describes how to stop and restart the BMC Atrium Single Sign-On server on Microsoft Windows, UNIX, and Linux.

Stopping and restarting on Windows

  1. From the desktop of the application server host, use the Control Panel to go to the Administrator Tools' Component Services dialog box.
  2. Expand the Services folder.
  3. Select BMC Atrium SSO.
  4. Click Stop.
  5. To restart BMC Atrium Single Sign-On, click Start.

Stopping and restarting on UNIX or Linux

Ensure that your Java processes are stopped before restarting BMC Atrium Single Sign-On. Start the UNIX or Linux services by performing the following steps:

  1. Navigate to the <installationDirectory>/AtriumSSO/bin directory.
  2. To shut down the services, type the following command:

    shutdown-sso.sh
  3. To start the services, type the following command:

    startup-sso.sh

Enabling debug option while starting the server on UNIX or Linux

By default, the debug logs are disabled and nohup is not captured and stored. If you want to store nohup output, you must restart the server by performing the following steps:

  1. Navigate to the <installationDirectory>/AtriumSSO/bin directory.
  2. To shut down the services, type the following command:

    shutdown-sso.sh
  3. To start the services, type the following command:

    startup-sso.sh debug

Note

When the server is started with the 'debug' option, the nohup output will be captured and sent to the nohup.out file. You must monitor the nohup file size as the there is no provision of creating a new log file when the file grows beyond a certain size.

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Javier Prieto sabugo

    We have an SSO 9.0.00 instance running on a Linux machine.

    I see a significative difference, when the SSO is installed on a Windows machine, the tomcat Service is deployed with Start -> Automatic. Meaning that the service is allways going to start after a restart of the machine.

    This is not happening in the Linux distribution:

    • Is there any reason because of this difference between both Operative Systems?
    • Could it be part of the documentation (configuration, post-installation activities) the description on how to deploy this auto-start/stop scripts?

     

     

    Aug 26, 2016 04:35
  2. Punam Saxena

    Hi Javier Prieto sabugo,

    The RSSO Customer Support team can help you with this issue. To contact Customer Support, click here.

    Regards,

    Punam

    Aug 26, 2016 06:30