Web Migration Guide
There are multiple methods to migrate your existing models from the desktop version to the web version of Expertsystemen.
Method 1: use publishing
This is the easiest, most failsafe, and therefore prefered way. It allows you to only migrate models and libraries that are still of interest.
Since the web version of xxllnc Expertsystemen is in fact a webserver on steroids, you can simply publish models and libraries from the confines of the Desktop Studio, using either [File > Publish] (see the Guided Tour) or [File > Server Publish] (to publish global libraries). Simply create a server entry using the address of the web version and be on your merry way.
Method 2: export and import zipfiles
This is a viable option if you have no access to the Desktop version. It involves exporting a model as zipfile from an existing development or test server and then importing it into the web version of Expertsystemen.
You can create a zipfile for any model that has Allow downloading this model and its resources checked in the Webadmin, and then upload it again from the File tab.
See ZIP for the entire process.
NOTE Do not Zip your local folder from a Desktop Studio, to try and upload that. It would include deploy directories, and be rejected on upload.
Method 3: mass-copy over data from an existing server
This method involves just copying over all data from an existing test or development server to the server running the modeling environment and can only be undertaken by someone with access to both servers. It can only be done at the start of a migration.
It may also require some tweaking of settings.
This method is out of the question if there are local libraries in use on the development or test server. Since the web version does not and will not support those, these will be inaccessible using this method.
Method 4: upload local files from a folder
This is the least desirable method.
You could also upload the local models and their assets to the web version of the
Studio. This does require a very clean working directory. Having multiple .mdl
files within your folder for instance gets you instant rejection.
Note however that his will not contain global libraries used by the model. You’d have to upload those separately. Local libraries will be converted to global ones if included.
Choose Upload model folder, pick the root folder of a model, and start uploading.
Do not upload just a .mdl except for in the simplest of cases. Needed assets won’t be uploaded. Which may cause the model to stop working correctly.