Starting a Development Server

In this Lesson

You will learn how to start and stop the development SxServer.

Concepts

The Soiree plugin contributes five buttons to the Eclipse toolbar that are used to control the development server.



We will look at each of the controls before we start your server.

  1. SxServer IP Address
    This control is used to override the server’s IP address that is specified in the Server definition. This becomes useful if you are running the development server on a computer whose IP address changes frequently and you are connecting to it using external devices.



    If you select an override it stays in effect until you remove it.



  2. Start SxServer



    This is a split button. If you select the small down arrow to right of the button it displays all of the Server items that are defined in your Eclipse workspace. You start a server by selecting it from the list.



    Tip
    The server configuration you select stays in effect until you change it. So, after you start a server you can restart the same one next time by simply pressing the Start button.
  3. Start SxServer (Debug)
    This is a split button that works just like the Start SxServer button except that it starts SxServer in debug mode. This allows you to use the Eclipse debugger on the Java classes that you create.



  4. Shut down SxServer
    This requests the SxServer to shut down. (But you already knew that didn’t you?)



  5. Restart SxServer
    This will stop and then restart in the same mode in which it was last started.



  6. Automatic SxServer Restart
    If SxServer is running when you modify an Sx Item which is used by the server, such as a scene definition, the SxServer will automatically be restarted. This allows the server to become aware of the modified item.

Start A Server

In this exercise you will start the server you created for the Party project.

  1. Start the Derby database if it is not already running.
  2. Use the Start SxServer control to display the list of available servers and then select PartyServer



  3. If the server starts successfully you should see something like this in the Java console



  4. If you have not yet configured the com.seronix.soiree.connect.System database connection then you may see something like this in the Java console. If that happens then go back to Creating a Database Connection lesson and complete the last exercise in that lesson.




    If you have not yet started the Derby database database then you may see something like this in the Java console. If that happens then start the Derby database before starting SxServer.



  5. Use the Stop SxServer control to stop SxServer



    The Java console should indicate that the server has stopped.



    If SxServer is not running when you attempt to stop it you will receive this message



You now have a server that can be used to run your Solution.