Go backward to Embedding Mathematica
Go up to Building CONCERT Instruments
Summarizing the discussion of the previous session, integrating Mathematica as a concert instrument involves the following tasks:
Furthermore a corresponding Mathematica library has to be provided that handles the datatype "network file" with the corresponding operations by communication with the database interface program.
Ultimately the central part of the control interface (the only part interacting with the instrument running on other machines) may be taken by the interface class itself.
The consistent organization of the locations where the native code involved in such a Mathematica session (Mathematica frontend, Mathematica kernel, MathLink libraries) may become a difficult problem in distributed heterogeneous environments. One possibility is to let the administrator of the corresponding host take care of this task (by placing the code in standard locations or denoting the locations by environment variables).
Another possibility is to let the Java interface class load the (appropriate variant of the code) from the global database. While technically feasible and organizationally advisable, this in general imposes problems with license contracts of commercial software packages (such as Mathematica). Consequently both solutions should be supported.