The usual way to do this is to use appletviewer. First you must
view an applet (just to bring up appletviewer) and edit properties to allow
network connections to any host. Next type: appletviewer http://myhost.foo.bar/DOGMA/NodeCon.html
(assuming you have
your dmaster\html directory on your master node served as http://myhost.foo.bar/DOGMA/).
Note that Java Plug-In should enable any browser to participate in DOGMA as long as you have used the Plug-In html converter on NodeCon.html. So far, Plug-In seems to work, but not entirely cleanly for DOGMA.
Step 1
Create the Group file: dogc SkelElement
(Do NOT include package names)
Step 2
Compile the application: makeall
Or for each file you wish to compile type: makeone <file to compile>(Do
NOT include package names).
(If you have multiple DOG applications in a directory they must ALL
have had dogc run on the group interface file before they will compile
using makeall.)
Step 3
Create and compile the remote stubs and skeletons. makermi dogma.examples.SkelElementImpl
(Be sure to INCLUDE package names)
From the DOGMA system prompt type: runMPI <MPI application> <numNodes> <args...>
or
To specify nodes in a process file:
From the DOGMA system prompt type: runMPIP <proc file name>
See the process file example.
DOGMA now redirects stdout and stderr from nodes to the SysCon. Screen-saver and browser based nodes, however, do not have stdout and stderr redirected. For this reason, the use of System.out is discouraged in DOGMA applications. Instead, MPIApplication.out and ElementImpl.out should be used. (So applications may simply use out.println() instead of System.out.println().)
Also, development should rarely take place on screen-saver or browser
based nodes. This is for two reasons: 1) the class unloading limitation
of the JVM means that nodes must be restarted every time application code
is revised, and starting these nodes is usually less convenient than starting
regular nodes. 2) stdout and stderr are not redirected for these
nodes (due to security limitations). Note that the "out" member of
both ElementImpl and MPIApplication will redirect output, but Exception.printStackTrace()
and its relatives will not on browser-based nodes.