SuperSocket Service Manager (ServerManager)

What SuperSocket Service Manager?

SuperSocket Service Manager is a allows you to manage and monitor your SuperSocket server program components on the client with a graphical interface.

Configuration server manager on the server side

In fact, Server Manager is an independent SuperSocket AppServer. Let the work, the first thing you should determine the following assemblies exist in your working directory:

SuperSocket.ServerManager.dll (compiled from the source code directory "Management \ Server")

SuperSocket.WebSocket.dll (compiled from the source code directory "Protocols \ WebSocket")

Then you need to combine it with other server instances you want to monitor configured together:

<superSocket isolation="Process">

    <servers>

      <server name="ServerA"

              serverTypeName="SampleServer"

              ip="Any" port="2012">

        <commandAssemblies>

          <add assembly="SuperSocket.QuickStart.SampleServer.CommandAssemblyA"></add>

          <add assembly="SuperSocket.QuickStart.SampleServer.CommandAssemblyB"></add>

        </commandAssemblies>

      </server>

      <server name="ServerB"

              serverTypeName="SampleServer"

              ip="Any" port="2013">

        <commandAssemblies>

          <add assembly="SuperSocket.QuickStart.SampleServer.CommandAssemblyB"></add>

          <add assembly="SuperSocket.QuickStart.SampleServer.CommandAssemblyC"></add>

        </commandAssemblies>

      </server>

      <server name="ManagementServer"

              serverType="SuperSocket.ServerManager.ManagementServer, SuperSocket.ServerManager">

        <listeners>

          <add ip="Any" port="4502" />

        </listeners>

        <users>

          <user name="kerry" password="123456"/>

        </users>

      </server>

    </servers>

    <serverTypes>

      <add name="SampleServer"

           type="SuperSocket.QuickStart.ServerManagerSample.SampleServer, SuperSocket.QuickStart.ServerManagerSample" />

    </serverTypes>

</superSocket>

In the above configuration, ServerA and ServerB are ordinary server instance you want to monitor. In addition, you need to add a server node server instance of type "SuperSocket.ServerManager.ManagementServer, SuperSocket.ServerManager" of. As you can see, this child node server instance under the "users" are defined to allow connection to the server's user name and password.

If you use the Silverlight client to connect to this server manager, you should also add a policy server node in the configuration:

<server name="SilverlightPolicyServer"

          serverType="SuperSocket.Facility.PolicyServer.SilverlightPolicyServer, SuperSocket.Facility"

          ip="Any" port="943"

          receiveBufferSize="32"

          maxConnectionNumber="10"

          policyFile="Config\Silverlight.config"

          clearIdleSession="true">

</server>

Normally you do not have to be concerned about the status of the policy server, so you'd better policy server name is added to the excludedServers property manager server configuration, so, Silverlight policy server does not appear in the Server Manager client.

excludedServers="SilverlightPolicyServer"