- Persistent Components
-
Some components might require that their runtime representation (the
Executor) remain persistent in memory, allowing multiple repeated calls
to the same object. The persistence might be used to increase performance
by not having to continually start an application. Alternatively, the
persistence might be implemented out of necessity; for example, to maintain
information from execution to execution. You can implement persistence
by defining the reusePolicy property in the Descriptor to be “any”
and maintaining a handle to any relevant objects. If the reusePolicy
for your component indicates that it is to be persistent, Isight
will not destroy the Executor until the SIMULIA Execution Engine
station is shut down (or the end of a job for local execution) when connected
to a SIMULIA Execution Engine.
- Exception Handling
-
See Component Development Reference for information on proper
exception handling in Isight.
- Logging
-
See Component Development Reference for information on how
to send messages to the Isight
Log from your Executor.
- File Parameters
-
If your component requires interaction with files that must be made
known to Isight
(e.g., to be passed to/from other components), you will most likely need
to represent them using File Parameters. For more information on programming
with file parameters, see File Parameters Reference.
|