When you run a fragment in StreamBase Studio, Studio assigns each fragment a node and cluster name, following a defined naming pattern.
For EventFlow fragments, Studio's default node name is:
projectis the Studio project's name,
moduleis the basename of the primary EventFlow module in the fragment, and
nnis an integer sequence number for this fragment, if more than one instance is running.
For LiveView fragments, Studio's default node name is:
projectis the Studio project's name, and
nnis an integer sequence number for this fragment if more than one instance is running.
For both EventFlow and LiveView fragments, Studio's default cluster name is your system login name. This keeps your Studio-launched nodes in a separate cluster from other colleagues using StreamBase in the same subnet.
You can customize these defaults as follows:
When using the epadmin command to
install a node on the command line, you assign
a name to the node with the nodename parameter, using
Do not re-use any node name currently in use, including any node names assigned by Studio launches. The cluster name is your system login name by default, but can be any string. For example:
epadmin install node nodename=B.sbuser application=...
If not specified, the default node name is
hostname is the return value from the hostname command, and where the cluster name is the
literal string "
The application archive being installed can declare one or more node names in the NodeDeploy > nodes > name object of a HOCON configuration file of type c.t.ep.dtm.c.node. In this case, you must use one of the configuration-declared node names when installing that application archive with epadmin.