Systemwalker Runbook Automation Reference Guide

1.3.4 ssoclservicectl (Interstage Single Sign-On Start and Stop Command)

Description

The following services of Interstage single sign-on are started and stopped on a Management Server.

• Interstage Management Console

• Interstage HTTP Server (Note 1 )

• The repository of Interstage Directory Service (Note 2)

  Note 1) All Web servers that are configured on the machine are affected.

  Note 2) Only SSO repository can be operated. Check the SSO repository by the repository name in [Repository server detailed setting] of [environment setting tab] of Security >> Single sign-on >> Authentication base >> Repository server in Interstage Management console. However, when Interstage management console is stopped, it can't be checked. Therefore, check it while Interstage Management Console is started.

Synopsis

ssoclservicectl {start|stop}

Options

start

Specify to start the service. It can't be specified at the same time when stop option is specified.

stop

Specify to stop the service. It can't be specified at the same time when start option is specified.

Return Values

0:

Normal termination

2:

Abnormal termination

Command Location

[Windows]

<Systemwalker Runbook Automation installation directory>\sso\bin
Note: The default location is C:\Fujitsu\Systemwalker\SWRBAM

[Linux]

/opt/FJSVswrbam/sso/bin

Privilege Required/Execution Environment

[Windows]

• This command requires administrator privileges. When using Windows Server 2008 operating system, run as an administrator.

• This command can be executed on a Management Server.

[Linux]

• This can only be executed by a system administrator (superuser).

• This command can be executed on a Management Server.

Note

• Do not execute this command multiple times simultaneously.

• Execute this command in the environment created by 1.2.2 ssoclsetup (Interstage Single Sign-on Setup Command).

• When the service is stopped by this command, Interstage management console is also stopped

• When there are any services which failed to start or stop after this command was executed, solve the problem by checking the message or the message output in the log of the system. Then, execute the command again.

• When the services started by the command are already started, the message that it has been started is output.

• When the services stopped by the command is already stopped, the message that it has been stopped is output.