...
A outstanding change request for persistent state management is recognized and accepted by the OpenMI Association Technical Committee as a required change for version 2 of the OpenMI Standard...
...
A major part of the document consists of XML templates for a wide range of data types. It is our understanding that relatively few of these are used in practice and that these are simply made available to ensure a general system.
This assumption is correct - see also G.1.1
...
On what platform is the system running (Windows, Linux or other)?
The DELFT-FEWS system has been developed in JAVA and is platform independent. However, in the configuration of NFFS, all runs of forecasting modules are executed on dedicated servers. Presently, these are Windows systems.
...
we have only used this on Windows and Linux systems.
...
What is the module adapter (script, bat-file, win32dll, win exe, or other)? There are no technology specifications for the adapter.
There is no specific requirement for the module adapter. The only requirement is that it can communicate through the XML file formats. The use of standard methods for reading and writing XML files, based on the schemas provided is highly recommended. This not only reduces implementation efforts but also guarantees compatibility. The general adapter currently allows the external module to be run either as an executable, or as a Java method. A minor extension will allow running of DLL's. Batch files are not recommended as the General Adapters monitors return codes from the external module. These are not always correctly passed in Batch files, and as such ungraceful failure of a module is not easily identified.
...
How does the module adapter and the general adapter communicate (win32 API, files, or other)?
The general adapter initiates the executable, Java method (or DLL) through the system/Java calls. Arguments may be passed when required, though these must be static. The general adapter may also be used to set environment variables for the module where required.
The module normally runs in a dedicated directory (tree). a A working directory can be configured to act as the root of the module run.
...
Figure 1 on page 4-1 indicates that all communication between the NFFS system and the system that is delivered by a model supplier goes through the Module adapter. I this a correct assumption and can everything under the blue line be considered as a black box ?. If so, is it possible to describe the specific requirements to such a black box ?
This is correct. The most specific requirement is that the module must not have any manual interaction. This would preclude running the module in a distributed system.
...