Typically you will need to use the Create Web Interface… commands from both the Editor and Results programs in order to create a useful web interface. The development of such an interface is likely to be an iterative process and so both commands maintain the last output of the other automatically so you don’t have to repeat both steps each time.
This information persists in a file called export.xml in the target output folder, and this file also maintains the generated unique model identifier required for the master configuration file on the server. Thus the identifier will remain unchanged between successive exports unless you intentionally delete it from the .xml file (which can be edited with care in a text editor), delete the .xml file as a whole (to start over) or export to a different output folder (which will have no .xml file or a different one).
The remaining export files are divided between two separate offline and online sub-folders of the target output folder in order to make it obvious which files should be uploaded to the corresponding offline and online folders on the server (which are intentionally separate to avoid the internal model files being accessible via the web).
Separation of exported offline model data and online web content
The STEM model .dtl and .cnf files and corresponding WebServiceModelConfig.txt file are intended to be uploaded to the offline folder which is only accessed via the controlled interface of the eSTEM web service. The front-end web content is uploaded to the online folder and served via standard web-server components. The server-side aspect of this is described in detail in 8.4 Configuring individual models on the eSTEM server.
The generated web interface will communicate with the eSTEM application ‘out of the box’ but may also serve as a reference or starting point for suitably skilled users or third-party web developers intending to develop their own custom web-interface logic.