Introduction

The models created with the Berkeley Studio can be published to a Berkeley Webserver. This manual describes the use of the Berkeley Webserver. The Webserver can serve a model as HTML, but may also send JSON-messages. Besides this, a model can also be developed to be used in the SOAPserver. A model such as that has no user interaction, but mereley a (SOAP) question and a (SOAP) answer with which the model can work.

The server opens a port (see settings) on the server, just like IIS or Apache. It does not need other software like Java, Apache or IIS.

The files the Webserver needs are:

  • BBWebserver.exe (the main program)
  • bbweb.ini (the Webserver’s settings, overriden by BBWebServer.ini if present)
  • datasources.xml (data sources definition)
  • login.xml (users, models and access rights)
  • login.xsl (used for the administration over the web)
  • report.xsl (used in the default report generation)
  • mdl_io.dll (to convert models of older versions)
  • gds32.dll (used for accessing Firebird and Interbase databases)
  • libeay32.dll (used for communication over https)
  • libssl32.dll (used for communication over https)
  • ssleay32.dll (used for communication over https)

Besides this there are two subdirectories, html and dot.

The html-directory contains the HTML templates, CSS stylesheets, images and JavaScript files for the webpages served by the Webserver.

The dot directory houses software to serve a visual representation of the flow of the model.

Accessing the models published to the Webserver is possible by logging in on the website the Webserver generates. It is important that there is a user with access to the specific model. How to go about that you may find [here](/what-does-that-button-do-in/the webserver/users/). The server can also use a template which is a just an already existing case . A different case can be created using that template, meaning all values will be copied into the new case.

Models can also be accessed directly by combining the user name, password and possibly the model name in the URL, e.g.:

  • Open the model overview: http://127.0.0.1/open?username=testuser&password=testuser

  • Open a specific case: http://127.0.0.1/open?modelname=testmodel&username=testuser&password=testuser&caseindex=-1

  • Start the model using a template http://localhost:81/?modelname=bb&username=demo&password=demo&templateindex=123

  • Start the model using a template and forcing a caseindex, if the case already exixts, the templateindex will be ignored http://localhost:81/?modelname=bb&username=demo&password=demo&caseindex=25&templateindex=123

  • Settings in BBWebServer.ini and user administration in login.xml may be reloaded remotely: http://127.0.0.1/reloadsettings

In the second example the parameter caseindex=-1 forces the server to create a unique case; each session will then be saved on the server. This may or may not be desired, depending on the circumstances.

Enjoy the Berkeley Webserver!