Weka4WS version 2.0 has been released today. This is an update to our earlier 1.0 release, and includes several new features release as well as numerous bugfixes.
New features:
- Knowledge Flow front-end also extended to support remote data mining;
- code updated to the 3.4.12 book version of Weka (12th of December 2007);
- the client side of the application can now run also on Windows machines;
- proxy credentials may now be created inside the client application: a dedicated window may be called at any time both in Explorer and Knowledge Flow and will automatically pop up at startup if the credentials are not available or have expired;
- added pull-style message delivery mechanism for clients to whom notifications cannot be delivered (e.g. because they are behind a firewall): the client now starts by default in pull-mode (that is it checks for the result availability every 10 seconds) and requests a notification dispatch to the server: if it subsequently receives a notification then the client switches to push-mode (that is it waits for a result availability notification), otherwise it stays in pull-mode;
- improved hosts checking now including, besides the Globus Container and GridFTP availability check, also user permissions check, Weka4WSService deployment check, versions compatibility check between client and service;
- possibility to extend the memory available for the virtual machine by running the ‘weka4ws.sh’ (or ‘weka4ws.bat’ on Windows) script and passing as first argument the amount of RAM (in MB) to be used. For example running
weka4ws.sh 2048
will run Weka4WS setting the maximum Java heap size to 2048MB.