SSC Web Server
The SSC web server runs on the SunSystems application server and is used to pass data into and out of SunSystems. Both input and output data formats are in SSML (XML variant). The user can connect to the web server across an intranet or the internet, allowing the user to select methods and enter data or specify input payloads for SSC to process. The resulting output
payload is returned to the web front end in SSML format.
Deployers Workbench
The Deployers Workbench is used by SSC implementors to monitor transactions being entered through SSC (or Transfer Desks) in real time. Users can also add and maintain SSC licenses and set up email notifications for expired or nearly expired licenses. New components can be installed or updated, and payload definitions can be tuned according to the SunSystems installation by marking specific nodes/leaves as unused. For example, where analysis dimensions and value labels differ from installation to installation.
Adminstrators Workbench
The Administrators Workbench is used by systems administrators to perform the same tasks as the Deployers Workbench but it does not allow the tuning of payload definitions.
User Manager
The User Manager is used by systems administrators to add new SSC users. The user name is used for SSC input payloads and to create new SunSystems users.

Software Requirements
Microsoft Windows NT version 4.0 with Service Pack 6a is required for the SunSystems Connect and Automation Desk installation. Please contact your regional support representative to ascertain the support status before upgrading to a new Windows NT service pack.
Where a third party application is written that makes a SOAP call to SSC, the machines on which it is run must have the correct version of all the necessary supporting software installed. For example, the correct Microsoft SOAP Toolkit.
Installing SSC
SSC and Automation Desk are separately purchasable modules and require a valid serialization in order to use them. The SSC serialization must specify the maximum number of SSC connections allowed.
Upon installing SunSystems, the Connect Server is started automatically by the installation and no further settings are required. The Server starts up automatically upon restarting your server.
Note: SunSystems Connect functionality comprises:

User Manager and Component Manager can only be run on a server with the client installed on it. Therefore, they cannot be run on the client on a client only installation. Property Editor can be run on a client installation, however, a number of properties are not applicable.
SSC Layout
SSC is installed into the subdirectory ssc in the SunSystems 5 program directory.
See the subsection Default Directory Structure and Application Files in Installing SunSystems 5 for further details on SSC and Transfer Desk.
Configuring SSC
Once SSC is installed on the server you must use the User Manager tool to add all relevant user names and passwords to SSC. See the User Manager topic in the SunSystems Connect help for further details.
Securing SSC
Additional security measures are the responsibility of the web site or integration developers.
There are four areas of security that must be addressed when setting up SSC:
The Tomcat Keystore File
The tomcat keystore file holds the X.509 certificate that defines the encryption keys for secure sockets. By default it is called SUNSYSTEMS5\ssc\tomcat.keystore, where SUNSYSTEMS5 is the name of your SunSystems program root directory.
The file that is included with SSC is password protected and has a default password of 'changeit'.
However, the password protection is of limited use in that, because the application must gain access to the password, the password is specified in clear text within the property files. In this instance, it is recommended that you improve the protection of this file using Windows NT Access Control.