IBM SPSS Modeler Stream Limitations
When you work with streams in the IBM® SPSS® Deployment Manager, the system has the following constraints:
- Naming. If the node name, label, and type are the same, you cannot schedule a job for execution because a conflict arises.
- Scripting. If a stream script contains overrides for a specific node—for example, the script sets the output location for a graph—the script supersedes any conflicting user-specified values defined in Deployment Manager.
- Supernodes. Execution of an IBM SPSS Modeler job step corresponds to the processing and execution of all top-level terminal nodes in the stream. If any terminal node is a terminal supernode, the terminal nodes within that supernode execute recursively. In contrast, if source or process supernodes, which are by definition non-terminal, contain terminal nodes, those nodes do not execute. The terminal nodes in the non-terminal supernodes do appear in Deployment Manager but are not processed during execution of the step.
- Parameters. Parameters defined for supernodes cannot have the same name as parameters defined for a stream. The names must be unique.
- Text Analytics node restrictions. You cannot use the SPSS Modeler Text Analytics File List or Web Feed nodes for scoring within an IBM SPSS Collaboration and Deployment Services - Scoring configuration.
In addition to the items listed above, there are the following specific constraints.
- No unlock checkbox is available when you store a stream in the IBM SPSS Collaboration and Deployment Services repository. Unlock is the default when storing streams. To lock or unlock an object, choose , navigate to the object, and right-click on its name to display the context menu.
- In Deployment Manager, when you run a job that contains a stream with an Evaluation node set to produce a Gains graph, the graph output may be incomplete if the system is running under Oracle Weblogic 11g using the Oracle JRockit JRE. To avoid this problem, use the IBM JRE.