Skip to main content
Skip table of contents

Start SuperADMIN and SuperSERVER

Typically, you will want to start SuperADMIN and SuperSERVER using a Windows Service. This will ensure that both components start automatically when the machine starts.

If you choose the Complete installation option, then the installation process will create a default Windows Service called SuperSTAR that is configured to start SuperADMIN Server and SuperSERVER when Windows starts.

If you want to change this service, or if you need to create the service because you did not create it during installation, then you can use the supplied SuperSERVICE Manager tool.

You can also start the components manually. This option is described in more detail below.

 However you choose to start the components, they must be started in a specific order:

  1. SuperADMIN server must be started first.
  2. SuperSERVER can only be started once SuperADMIN server is running.
  3. Once both SuperADMIN server and SuperSERVER are running, you can start any of the clients. This includes the SuperADMIN console (used for configuring things like the server, database catalogue, and user permissions) and the end user clients, such as SuperCROSS and SuperWEB2.

Manually Starting the SuperADMIN Server and SuperSERVER

Start SuperADMIN Server Manually

There are a number of ways you can manually start SuperADMIN Server. Do one of the following:

Windows Start MenuWindows ExplorerCommand Prompt

Go to the Windows Start Menu and select SuperSTAR > SuperADMIN > SuperADMIN Server.

Open Windows Explorer and browse to the server directory within the SuperADMIN program data directory (in a default installation this will be C:\ProgramData\STR\SuperADMIN\server), then double-click server.bat:

Open a command prompt and change to the server directory within the SuperADMIN program data directory, then execute server.bat:

When SuperADMIN displays the message All Services started this indicates that it has started correctly:

Do not close this window. If you do, this will stop SuperADMIN server.

Start SuperSERVER Manually

Once you have started SuperADMIN server, you can start SuperSERVER. Do one of the following:

Windows Start MenuWindows ExplorerCommand Prompt

Go to the Windows Start Menu and select SuperSTAR > SuperSERVER SA > SuperSERVER.

Open Windows Explorer and browse to the SuperSERVER program files directory (in a default installation this will be C:\Program Files\STR\SuperSERVER SA), then double-click scsa.exe:

Open a command prompt and change to the SuperSERVER program files directory, then execute scsa.exe:

 When SuperSERVER displays the message Accepting CORBA Client Requests this indicates that it has started correctly:

Do not close this window. If you do, this will stop SuperSERVER.

SuperSERVER Command Line Options

SuperSERVER has some (optional) command line options. You will need to use these if you are using non standard ports, or if the SuperADMIN server is running on a different machine to SuperSERVER.

OptionSpecifies...
-a [<host>][:<port>]

The address of the SuperADMIN server. Either the host, port, or both can be specified. For example:

TEXT
scsa.exe -a thesuperadminserver:9220
-p <port>
The port used for incoming connections to SuperSERVER.
-c <codepage>

The codepage identifier to use. You may need to change this if the locale of the machine running SuperSERVER uses a language with characters not supported by the default codepage (1252).

See this list of codepage identifiers for help determining the appropriate codepage for your deployment. Please note that SuperSERVER currently only supports ANSI and OEM codepages.

--log-corba <file>
A file to log CORBA information to.
-t
The timeout for attempting to connect to SuperADMIN (in seconds).

You can also use the options -h to display help information and -v to display version information.

Next Steps...

Now that you have started both SuperADMIN server and SuperSERVER, you can start the SuperADMIN console, or start one of the clients.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.