Changes between Version 36 and Version 37 of WikiStart


Ignore:
Timestamp:
06/26/19 13:51:35 (5 years ago)
Author:
wouter
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v36 v37  
    11[[PageOutline]]
    2 = Genius2 RunServer
    3 This is the homepage of the Genius2 run server.
     2= GeniusWeb RunServer
     3This is the homepage of the GeniusWeb run server.
    44
    5 The Genius2 main page is [https://tracinsy.ewi.tudelft.nl/trac/Genius2 here].
     5The GeniusWeb main page is [https://tracinsy.ewi.tudelft.nl/trac/Genius2 here].
    66
    77The run server can run sessions and tournaments as specified.
     
    99== Installation
    1010* Install your apache-tomcat 8 installation ​https://tomcat.apache.org/download-80.cgi. You can re-use an existing installation.
    11 * Download the runserver war file from [http://artifactory.ewi.tudelft.nl/artifactory/webapp/#/artifacts/browse/tree/General/libs-release-local/genius2/runserver the artifactory]. Go into the latest version of the runserver and download (right click) the war file. NOTICE: your browser must have cookies enabled to access the artifactory.
     11* Download the runserver war file from [http://artifactory.ewi.tudelft.nl/artifactory/webapp/#/artifacts/browse/tree/General/libs-release-local/geniusweb/runserver the artifactory]. Go into the latest version of the runserver and download (right click) the war file. NOTICE: your browser must have cookies enabled to access the artifactory.
    1212* Copy the downloaded war file into the tomcat webapps directory
    1313* (Re)start tomcat
     
    6565TODO clarify what is MUST
    6666
    67 This section deals with the communication protocols with the runserver. These may be relevant when you need to communicate directly with it, e.g. when you build your own GUI or start up your own sessions and tournaments from a script. Other implementations of a runserver should adhere to the same communication protocols to ensure compatibility with genius2.
     67This section deals with the communication protocols with the runserver. These may be relevant when you need to communicate directly with it, e.g. when you build your own GUI or start up your own sessions and tournaments from a script. Other implementations of a runserver should adhere to the same communication protocols to ensure compatibility with GeniusWeb.
    6868
    6969=== Run Negotiation
    70 This section describes the [source:/src/main/java/genius2/runserver/RunNego.java RunNego] service. It is available at {{{http:..:8080//runserver/run}}}.
     70This section describes the [source:/src/main/java/geniusweb/runserver/RunNego.java RunNego] service. It is available at {{{http:..:8080//runserver/run}}}.
    7171This service starts up and runs a complete Nego (session or tournament) when it is accessed (http get or post).
    72 To start a negotiation, the http get must include a JSON-serialized [https://tracinsy.ewi.tudelft.nl/trac/Genius2/browser/protocol/src/main/java/genius2/protocol/NegoSettings.java genius2.protocol.NegoSettings] object. All details are in the javadocs, here we discuss it only briefly.
     72To start a negotiation, the http get must include a JSON-serialized [https://tracinsy.ewi.tudelft.nl/trac/Genius2/browser/protocol/src/main/java/geniusweb/protocol/NegoSettings.java geniusweb.protocol.NegoSettings] object. All details are in the javadocs, here we discuss it only briefly.
    7373
    7474After session is started, popup shows the negotiation ID. The ID starts with the name of the protocol (SAOP, APP) followed by a serial number.